Eric and all, I do not think that this Erratum reflects any real issue. Technical or editorial, with RFC 4364..
The original text in the RFC, IMHO and FWIW, simply means that the VPN architecture does not require a dedicated SAFI for routes with the NLRI comprised by an 8-octet RD followed by an IP prefix but not containing any labels. At the same time Section 10 discussed both advertisement of unlabeled IP routes (in what is known as Inter-AS Option A) and labeled IP routes (in what is known as Inter-AS Option C). RFC 4264 (and its predecessor RFC 2547) have been implemented for many years and widely deployed. There are multiple deployments in the fields where implementations by different equipment vendors successfully interoperate. AFAIK during all these years the text in question has never been misinterpreted causing interoperability issues. I suggest rejecting the Erratum. Regards, Sasha -----Original Message----- From: BESS <bess-boun...@ietf.org> On Behalf Of Eric Vyncke (evyncke) Sent: Thursday, August 3, 2023 3:57 PM To: bess@ietf.org Subject: [EXTERNAL] [bess] Errata 7180 on RFC 4364 BGP/MPLS IP Virtual Private Networks (VPNs) As the L3VPN activities have been transferred to the BESS WG, I would appreciate feedback from the BESS WG on this errata. https://clicktime.symantec.com/15siKzyo3CizY1LdsHeqv?h=osVKgJrEFlcW2bC1ypy5YVa-gwTFAL57vb6sQp0DhDE=&u=https://clicktime.symantec.com/15sM1HB9ZpAML5YT8bq46?h=HWRSOoaNbU7qgBs842MyqB5JpChoAwWy9kXqPFoTOO8=&u=https://www.rfc-editor.org/errata_search.php?eid%253D7180 The section 4.3.4 text " Note that this VPN architecture does not require the capability to distribute unlabeled VPN-IPv4 addresses." Is suggested to be replaced by " Note that this VPN architecture does not require the capability to distribute unlabeled IPv4 addresses. With the errata reporter note: From my understanding, VPN-IPv4 addresses are necessarily labeled, but IPv4 adresses are not indeed. Section 10 seems to confirm the error by using the correct term: "distribute unlabeled IPv4 addresses to each other." Thanks in advance for your review, -éric _______________________________________________ BESS mailing list BESS@ietf.org https://clicktime.symantec.com/15siFAnWab3Q84WiKjFhJ?h=53eKMniWfdoGr2W_7YyC6ocyKCO4MPcOP-V1oSAeyjQ=&u=https://clicktime.symantec.com/15sLvSys7CUkv8iXb3RuU?h=suzmpcLHxwQqYp9qsTJ_9tNLlvAqgDDz89Th_sNvugw=&u=https://www.ietf.org/mailman/listinfo/bess Notice: 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.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess