Hi all,
I would appreciate an answer to my question about a certain aspect of Section 
8.2.1 of the 7432-bis 
draft<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-07#section-8.2.1>
 that discusses construction of the per-ES Ethernet A-D (EVPN Type 1) route.

  1.  This section says that "The ESI Label extended community MUST be included 
in the route".
  2.  It also says (in Section 8.2.1.1) that "The set of Ethernet A-D routes 
per ES MUST carry the entire set of RTs for all the EVPN instances to which the 
Ethernet segment belongs".  (The need to advertise a set of per-ES Ethernet A-D 
(EVPN Type 1) routes for a given MH ES (rather than a single such route pe ES) 
presumably arises when the number of Route Targets to be advertised for this MH 
ES exceeds the common limit on the size of the BGP UPDATE message or an 
implementation-specific on the number of Extended Communities that can be 
carried in a single UPDATE message).

I would like to understand, whether, in the case when multiple per-ES Ethernet 
A-D routes are advertised for the same MH ES, the ECI Label Extended Community 
MUST be attached to each of these routes.  IMHO and FWIW #1 above suggest that, 
but an explicit statement would be most helpful.

I also assume that, if the ECI Label Extended Community is attached to all the 
per-ES Ethernet A-D routes in the set, it MUST carry the same flags and the 
same Label value - is this correct? If yes, could this be explicitly specified 
in the draft?

Your feedback would be highly appreciated.

Regards, lots of thanks in advance, and best New Year wishes,
Sasha

Disclaimer

This e-mail together with any attachments may contain information of Ribbon 
Communications Inc. and its Affiliates that is confidential and/or proprietary 
for the sole use of the intended recipient. Any review, disclosure, reliance or 
distribution by others or forwarding without express permission is strictly 
prohibited. If you are not the intended recipient, please notify the sender 
immediately and then delete all copies, including any attachments.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Reply via email to