As co-author I support this document for WG adoption. I’m not aware of any relevant IPR.
Thanks, Senthil. ________________________________ From: Jorge Rabadan (Nokia) <[email protected]> Sent: Thursday, September 3, 2026 9:55 AM To: Matthew Bocci (Nokia) <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: Call for adoption: draft-rabadan-bess-evpn-inter-domain-opt-b-08 (Ends 2026-09-16) Hi all, This document closes a gap in Inter-Domain EVPN networks. It specifies the behavior and fixes the resulting issues for multi-homing, mass withdraw, aliasing/backup paths, DF election, split-horizon, E-Tree, and PBB-EVPN, mainly by introducing an Egress PE Identifier sub-TLV so ingress PEs can correlate routes after inter-domain propagation. As a coauthor, I strongly support its adoption as a WG document. I’m not aware of any related IPR. Thanks, Jorge From: Matthew Bocci via Datatracker <[email protected]> Date: Wednesday, September 2, 2026 at 3:53 AM To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Call for adoption: draft-rabadan-bess-evpn-inter-domain-opt-b-08 (Ends 2026-09-16) CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. This message starts a bess WG Call for Adoption of: draft-rabadan-bess-evpn-inter-domain-opt-b-08 This Working Group Call for Adoption ends on 2026-09-16 Abstract: An EVPN Inter-Domain interconnect solution is required when two or more sites of the same Ethernet Virtual Private Network (EVPN) are connected to different IGP domains or Autonomous Systems (AS) and need to communicate. The Inter-Domain Option-B connectivity model is one of the most popular solutions for this type of EVPN connectivity. While several documents address specific aspects of this interconnect approach, none provide a comprehensive overview of how Inter-Domain Option-B connectivity affects EVPN procedures. This document examines the behavior of EVPN procedures in an Inter-Domain Option-B network and proposes solutions to the identified issues. Please reply to this message and indicate whether or not you support adoption of this Internet-Draft by the bess WG. Comments to explain your preference are greatly appreciated. Please reply to all recipients of this message and include this message in your response. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [2]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-rabadan-bess-evpn-inter-domain-opt-b/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-rabadan-bess-evpn-inter-domain-opt-b-08 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-rabadan-bess-evpn-inter-domain-opt-b-08
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
