Hi all, As a co-author, I support this document for WG adoption. The use of this specification is necessary to ensure the correct operation of first-hop security mechanisms in EVPN networks. Not aware of any related IPR.
Thanks. Jorge From: Zhaohui Zhang via Datatracker <[email protected]> Date: Thursday, March 5, 2026 at 12:45 PM To: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Call for adoption: draft-sajassi-bess-evpn-first-hop-security-05 (Ends 2026-03-25) 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-sajassi-bess-evpn-first-hop-security-05 This Working Group Call for Adoption ends on 2026-03-25. An extra is given in consideration of IETF25. Abstract: The Dynamic Host Configuration Protocol (DHCP) snoop database stores valid IPv4-to-MAC and IPv6-to-MAC bindings by snooping on DHCP messages. These bindings are used by security functions like Dynamic Address Resolution Protocol Inspection (DAI), Neighbor Discovery Inspection (NDI), IPv4 Source Guard, and IPv6 Source Guard to safeguard against traffic received with a spoofed address. These functions are collectively referred to as First Hop Security (FHS). This document proposes BGP extensions and new procedures for Ethernet VPN (EVPN) will distribute and synchronize the DHCP snoop database to support FHS. Such synchronization is needed to support EVPN host mobility and multi-homing. 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-sajassi-bess-evpn-first-hop-security/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-first-hop-security-05 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-sajassi-bess-evpn-first-hop-security-05 Thanks. BESS Chairs
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
