[rbridge] Consensus Check: Configure ports to disable endstationtraffic

[Caitlin Bestler]

> -----Original Message-----
> From: rbridge-bounces at postel.org [mailto:rbridge-bounces at postel.org]
On
> Behalf Of Anoop Ghanwani
> Sent: Monday, January 07, 2008 11:14 AM
> To: Eastlake III Donald-LDE008; Rbridge at postel.org
> Subject: Re: [rbridge] Consensus Check: Configure ports to disable
> endstationtraffic
> 
> 
> This certainly makes sense is what I tend to
> think of as a TRILL "core" port.   On such a
> port, we would never see non-TRILL encap'ed
> frames (other than the usual exceptions such
> as BPDUs and other link layer control traffic).
> 
> I wonder if it makes sense to also have a
> configuration for a TRILL "edge" port -- one
> where we are configured to never send TRILL
> encap'ed traffic because we don't intend for
> it to be used as a transit link (even though
> connectivity may exist to another RBridge
> for redundancy purposes).
> 

This is certainly something specialized implementations
SHOULD be allowed to do.

The physical ingress/egress point for a chassis could
be given RBridge functionality, and it would certainly
be in a position to know what sort of networking functionality
was allowed in the internal slots.