Hi Wen, I am thinking of adding the following paragraph as a clarification for the originating router’s IP address.
“The Originating Router’s IP address does not need to be a routable address and its purpose is to identify the originator of that EVPN route uniquely. It can be either IPv4 or IPv6 address independent of the BGP next hop address type for that NLRI and it must remain the same for all EVPN routes advertised by that PE.” Cheers, Ali From: Wen Lin <wlin=40juniper....@dmarc.ietf.org> Date: Friday, May 10, 2024 at 11:06 AM To: bess@ietf.org <bess@ietf.org>, i-d-annou...@ietf.org <i-d-annou...@ietf.org> Cc: bess@ietf.org <bess@ietf.org> Subject: [bess] Re: I-D Action: draft-ietf-bess-rfc7432bis-09.txt Thank you for the updated draft. I think we need to explicitly specify how we set the Originating Router’s IP address – when it will be to IPv6 or IPv4 address for both Ethernet Segment Route and Inclusive Multicast Ethernet Tag Route. Today, there is no mentioning about it in the draft. 7.4. <https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09#section-7.4> Ethernet Segment Route<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09#name-ethernet-segment-route> +---------------------------------------+ | RD (8 octets) | +---------------------------------------+ |Ethernet Segment Identifier (10 octets)| +---------------------------------------+ | IP Address Length (1 octet) | +---------------------------------------+ | Originating Router's IP Address | | (4 or 16 octets) | +---------------------------------------+ We need to add definition or reference for the Originating Router’s IP Address. 7.3. <https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09#section-7.3> Inclusive Multicast Ethernet Tag Route<https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09#name-inclusive-multicast-etherne> +---------------------------------------+ | RD (8 octets) | +---------------------------------------+ | Ethernet Tag ID (4 octets) | +---------------------------------------+ | IP Address Length (1 octet) | +---------------------------------------+ | Originating Router's IP Address | | (4 or 16 octets) | +---------------------------------------+ For IMET route, we have the following definition in section 11.1: “The Originating Router's IP Address field value MUST be set to an IP address of the PE that should be common for all the EVIs on the PE (e.g., this address may be the PE's loopback address). The IP Address Length field is in bits.” A router may have both IPv4 and IPv6 addresses configured for the loopback. We need to specify when IPv6 address will be used based on whether EVPN is used IPv4 or IPv6 underlay. Thanks, Wen Juniper Business Use Only From: BESS <bess-boun...@ietf.org> on behalf of internet-dra...@ietf.org <internet-dra...@ietf.org> Date: Friday, May 3, 2024 at 12:42 AM To: i-d-annou...@ietf.org <i-d-annou...@ietf.org> Cc: bess@ietf.org <bess@ietf.org> Subject: [bess] I-D Action: draft-ietf-bess-rfc7432bis-09.txt [External Email. Be cautious of content] Internet-Draft draft-ietf-bess-rfc7432bis-09.txt is now available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the IETF. Title: BGP MPLS-Based Ethernet VPN Authors: Ali Sajassi Luc Andre Burdet John Drake Jorge Rabadan Name: draft-ietf-bess-rfc7432bis-09.txt Pages: 73 Dates: 2024-05-02 Abstract: This document describes procedures for Ethernet VPN (EVPN), a BGP MPLS-based solution which addresses the requirements specified in the corresponding RFC - "Requirements for Ethernet VPN (EVPN)". This document obsoletes RFC7432 (BGP MPLS-Based Ethernet VPN) and updates RFC8214 (Virtual Private Wire Service Support in Ethernet VPN). The IETF datatracker status page for this Internet-Draft is: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-bess-rfc7432bis/__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrAUK3PyL$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-bess-rfc7432bis/__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrAUK3PyL$> There is also an HTMLized version available at: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrD-_D2Jy$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-09__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrD-_D2Jy$> A diff from the previous version is available at: https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-bess-rfc7432bis-09__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrF5Wvh7P$<https://urldefense.com/v3/__https:/author-tools.ietf.org/iddiff?url2=draft-ietf-bess-rfc7432bis-09__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrF5Wvh7P$> Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ BESS mailing list BESS@ietf.org https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/bess__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrCT0gLFF$<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/bess__;!!NEt6yMaO-gk!DQNdb1zziDhGamgqVCqazNaTWtGRyB4JfRJn_4PBJ-meIo5dUeuj3X1ZZzUL6Ak1xr3TX2QD68p6Le_VrCT0gLFF$>
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
