Hi John, Yes, it refers to the Encapsulation Extended Community (RFC 9012: The BGP Tunnel Encapsulation Attribute (rfc-editor.org)<https://www.rfc-editor.org/rfc/rfc9012#name-encapsulation-extended-comm>)
The use of the encapsulation extended community with EVPN is introduced first in RFC8365, so I don’t think anyone implementing this would have any doubts about what extended community the RFC refers to, but yes, we should have been more accurate. My two cents.. Thanks. Jorge From: John Scudder <j...@juniper.net> Date: Friday, February 9, 2024 at 1:28 PM To: bess@ietf.org <bess@ietf.org> Cc: saja...@cisco.com <saja...@cisco.com>, ssa...@cisco.com <ssa...@cisco.com>, stho...@cisco.com <stho...@cisco.com>, Jorge Rabadan (Nokia) <jorge.raba...@nokia.com>, Alvaro Retana <aretana.i...@gmail.com>, Andrew Alston - IETF <andrew-i...@liquid.tech>, Matthew Bocci (Nokia) <matthew.bo...@nokia.com>, slitkows.i...@gmail.com <slitkows.i...@gmail.com>, Jeffrey (Zhaohui) Zhang <zzh...@juniper.net>, vrkic.de...@gmail.com <vrkic.de...@gmail.com>, John Drake <je_dr...@yahoo.com> Subject: Re: [Technical Errata Reported] RFC9135 (7684) 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. Looks right (there is no such thing as the “Tunnel Type Extended Community”). Can the authors please confirm that "Encapsulation Extended Community” is what was intended? Thanks, —John > On Oct 19, 2023, at 5:05 PM, RFC Errata System <rfc-edi...@rfc-editor.org> > wrote: > > The following errata report has been submitted for RFC9135, > "Integrated Routing and Bridging in Ethernet VPN (EVPN)". > > -------------------------------------- > You may review the report below and at: > https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid7684__;!!NEt6yMaO-gk!BLmHBk44OQyvkjJEadA8wv3hfioxIYAw61RAwOt5B4BHIUSX3RxyYxJc278dsg3rkWOe6mmNMpDq_6jTqbuS7A$<https://urldefense.com/v3/__https:/www.rfc-editor.org/errata/eid7684__;!!NEt6yMaO-gk!BLmHBk44OQyvkjJEadA8wv3hfioxIYAw61RAwOt5B4BHIUSX3RxyYxJc278dsg3rkWOe6mmNMpDq_6jTqbuS7A$> > > -------------------------------------- > Type: Technical > Reported by: Denis Vrkic <vrkic.de...@gmail.com> > > Section: 6.1 > > Original Text > ------------- > This route is advertised along with the following extended community: > > * Tunnel Type Extended Community > > Corrected Text > -------------- > This route is advertised along with the following extended community: > > * Encapsulation Extended Community > > Notes > ----- > I guess that solud be Encapsulation Extended Community (or maybe Tunnel > Encapsulation Attribute) > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC9135 (draft-ietf-bess-evpn-inter-subnet-forwarding-15) > -------------------------------------- > Title : Integrated Routing and Bridging in Ethernet VPN (EVPN) > Publication Date : October 2021 > Author(s) : A. Sajassi, S. Salam, S. Thoria, J. Drake, J. Rabadan > Category : PROPOSED STANDARD > Source : BGP Enabled ServiceS > Area : Routing > Stream : IETF > Verifying Party : IESG
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
