[bess] Comments about Section 7.11 of 7432bis

[Alexander Vainshtein <[e-mail]>]

Hi,
I have a couple of comments about the first two sentences in Section 7.11 of 7432bis<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09#section-7.11> "EVPN Layer 2 Attributes Extended Community":


[RFC8214<https://www.rfc-editor.org/info/rfc8214>] defines and requires this extended community ("L2-Attr"), to be included with per-EVI Ethernet A-D routes when multihoming is enabled.

Usage and applicability of this Extended community to Bridging is clarified here.

My first comment is about interpretation of RFC 8214 as defining and requiring usage of L2-Attr Extended Community with per-EVI Ethernet A-D routes advertised for "bridging" EVI.  Please note that:

  *   Construction of per-EVI Ethernet A-D routes is defined in Section 8.4.1 of RFC 7432<https://datatracker.ietf.org/doc/html/rfc7432#section-8.4.1> , and this definition does not mention attachment of L2-Attr Extended Community to these routes
  *   RFC 8214 is not marked as updating RFC 7432.

My second comment is about inclusion of L2-Attr Extended community with per-EVI Ethernet A-D routes when multi-homing is enabled. Actually, RFC 8214 requires, in the case of EVPN-VPLS instances, advertisement of per-EVI Ethernet A-D routes regardless of multihoming, and L2-Attr Extended Community may be attached to these routes. E.g., in order to enable L2-MTU check for the corresponding service instance.

May I suggest the following replacement for the quoted sentences (removed text is marked with red strikethrough font while  added text is marked with bold green italics):

[RFC8214<https://www.rfc-editor.org/info/rfc8214>] defines and requires this extended community ("L2-Attr"), to be included with per-EVI Ethernet A-D routes when multihoming is enabled advertised by EVPN-based VPWS instances.

Usage and applicability of this Extended community to Bridging EVPN instances is clarified defined here.

Regards,
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.