[rbridge] Consensus Check: Egress processing of unicast not locallyknown

[Anoop Ghanwani]

I'm not sure why the case of "MAC address could
not be on that link" needs to be called out at all.
That is an access control issue.  But I am OK
with having it if someone really feels strongly
about it.

Anoop 

> -----Original Message-----
> From: rbridge-bounces at postel.org 
> [mailto:rbridge-bounces at postel.org] On Behalf Of Eastlake III 
> Donald-LDE008
> Sent: Tuesday, October 02, 2007 8:25 PM
> To: Rbridge at postel.org
> Subject: [rbridge] Consensus Check: Egress processing of 
> unicast not locallyknown
> 
> This is a check via the mailing list to confirm or refute an 
> apparent consensus from the minutes of the Chicago meeting 
> for a change from protocol draft -05:
> 
>    Egress RBridges that receive a known unicast TRILL data frame whose
>    inner destination address is not known locally should send the
>    native form of the frame out on every link for which the RBridge
>    is DRB for the frame's VLAN unless it knows that an end station
>    with that MAC address could not be on that link. (For example,
>    there is a layer-2 registration procedure for end stations on that
>    link and the destination MAC address in question is not
>    registered.) This is a local decision. No "error" message will be
>    defined for this condition at this time.
> 
> If no particular controversy arises over this in the next two 
> weeks, we will declare it to be the working group consensus.
> 
> Thanks,
> Donald & Erik
> 
> _______________________________________________
> rbridge mailing list
> rbridge at postel.org
> http://mailman.postel.org/mailman/listinfo/rbridge
>