Jeffrey, all, I’m not aware of any IPR relevant to this document. Thanks. Jorge
From: Jorge Rabadan (Nokia) <[email protected]> Date: Thursday, April 30, 2026 at 10:38 AM To: Zhaohui Zhang <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: Call for adoption: draft-rbickhart-evpn-ip-mac-proxy-adv-06 (Ends 2026-05-12) Hi all, As a co-author, I support this work for WG adoption. This specification has multiple implementations from different vendors, all deployed in production networks, and has been validated in public interoperability events (EANTC). It also meaningfully speeds up convergence in Ethernet Segment failure scenarios. The implementation maturity and demonstrated interoperability make this ready for WG adoption. Thank you, Jorge From: Zhaohui Zhang via Datatracker <[email protected]> Date: Tuesday, April 28, 2026 at 1:39 PM To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Call for adoption: draft-rbickhart-evpn-ip-mac-proxy-adv-06 (Ends 2026-05-12) 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-rbickhart-evpn-ip-mac-proxy-adv-06 This Working Group Call for Adoption ends on 2026-05-12 Abstract: This document specifies procedures for EVPN PEs connected to a common multihomed site to generate proxy EVPN MAC-IP advertisements on behalf of other PEs to facilitate preservation of ARP/ND state across link or node failures. 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. Jeffrey and BESS co-chairs [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-rbickhart-evpn-ip-mac-proxy-adv/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-rbickhart-evpn-ip-mac-proxy-adv-06 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-rbickhart-evpn-ip-mac-proxy-adv-06
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
