Luc and all, With regard to “Erratum 5900<https://clicktime.symantec.com/3M1kZNQgXrJ86A1cYgNrTsj6H2?u=https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid5900> makes somewhat more sense”: I am not sure how much more sense it means because:
1. RFC 7432, Section 3 says: “Bridge Table: An instantiation of a broadcast domain on a MAC-VRF”. 2. RFC 7432, Section 6.2 says: a. “With this <Sasha: VLAN Bundle> service interface, an EVPN instance corresponds to multiple broadcast domains (e.g., multiple VLANs); however, only a single bridge table is maintained per MAC-VRF” and “There is a many-to-one mapping between VLANs and a MAC-VRF” b. The Ethernet Tag ID in all EVPN routes <Sasha: advertised by a VLAN Bundle EVI > MUST be set to 0” 3. Last but not least, RFC 8584 always uses the lowest VLAN in the bundle because in any case all EVPN routes advertised by a VLAN-Bundle EVI have their Ethernet Tag ID set to 0. Only VLAN-aware Bundle EVIs can elect a different DF for each of the VLANs in the bundle (see Sections 3.2 and 4.1). My 2c, Sasha Office: +972-39266302 Cell: +972-549266302 Email: [email protected] From: BESS <[email protected]> On Behalf Of Luc Andr? Burdet Sent: Tuesday, November 12, 2019 5:50 PM To: [email protected] Cc: Sean.Chen <[email protected]>; Frank Lu <[email protected]>; RFC Errata System <[email protected]> Subject: Re: [bess] [Technical Errata Reported] RFC8584 (5899) 7432 makes the clear distinction between broadcast domain and bridge table (in definitions section no less...) Concur, this erratum 5899 should be rejected. Erratum 5900<https://clicktime.symantec.com/3M1kZNQgXrJ86A1cYgNrTsj6H2?u=https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid5900> makes somewhat more sense, VLAN Bundle in 7432 6.2 is for multiple broadcast domains, so switching "VLAN Bundle services" to "multiple BDs" makes sense. Minor nit. .:|:.:|:. Luc André Burdet | Cisco Systems Canada Inc. email: [email protected]<mailto:[email protected]> | phone: +1 613 254 4814 On Tue, Nov 12, 2019 at 10:30 AM John E Drake <[email protected]<mailto:[email protected]>> wrote: I agree Sent from my iPhone > On Nov 12, 2019, at 3:10 PM, Rabadan, Jorge (Nokia - US/Mountain View) > <[email protected]<mailto:[email protected]>> wrote: > > Hi, > > I don't understand why this erratum was filed. > "Broadcast Domain" is the correct term used in RFC7432 and all the EVPN > documents. > It should be rejected. > > Thanks. > Jorge > > -----Original Message----- > From: RFC Errata System > <[email protected]<mailto:[email protected]>> > Date: Tuesday, November 12, 2019 at 4:17 PM > To: "Rabadan, Jorge (Nokia - US/Mountain View)" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, "Nagaraj, Kiran (Nokia - > US/Mountain View)" <[email protected]<mailto:[email protected]>>, > "Sathappan, Senthil (Nokia - US/Mountain View)" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, "Vigoureux, Martin > (Nokia - FR/Paris-Saclay)" > <[email protected]<mailto:[email protected]>>, "Bocci, > Matthew (Nokia - GB)" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > Cc: "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > Subject: [Technical Errata Reported] RFC8584 (5899) > > The following errata report has been submitted for RFC8584, > "Framework for Ethernet VPN Designated Forwarder Election Extensibility". > > -------------------------------------- > You may review the report below and at: > > https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid5899__;!8WoA6RjC81c!SaIWS8sh_Qv0z3EeiwJR318oBQoGXbgX9muwUkuY33c6bBXZItc9S87ssaGNDd4$<https://clicktime.symantec.com/3AgVePtCzFrAA1iE1m3ZnWm6H2?u=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid5899__%3B%218WoA6RjC81c%21SaIWS8sh_Qv0z3EeiwJR318oBQoGXbgX9muwUkuY33c6bBXZItc9S87ssaGNDd4%24> > > -------------------------------------- > Type: Technical > Reported by: Sean.Chen > <[email protected]<mailto:[email protected]>> > > Section: 1.1 > > Original Text > ------------- > BD: Broadcast Domain. An EVI may be comprised of one BD > (VLAN-based or VLAN Bundle services) or multiple BDs (VLAN-aware > Bundle services). > > Corrected Text > -------------- > BD: Bridge Domain. An EVI may be comprised of one BD > (VLAN-based or VLAN Bundle services) or multiple BDs (VLAN-aware > Bundle services). > > Notes > ----- > broadcast domain is not comprised in any services (VLAN-based or VLAN > Bundle service). > > 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. > > -------------------------------------- > RFC8584 (draft-ietf-bess-evpn-df-election-framework-09) > -------------------------------------- > Title : Framework for Ethernet VPN Designated Forwarder > Election Extensibility > Publication Date : April 2019 > Author(s) : J. Rabadan, Ed., S. Mohanty, Ed., A. Sajassi, J. > Drake, K. Nagaraj, S. Sathappan > Category : PROPOSED STANDARD > Source : BGP Enabled Services > Area : Routing > Stream : IETF > Verifying Party : IESG > > _______________________________________________ BESS mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/bess<https://clicktime.symantec.com/351JT3BC1t7RZtmoUzkhKcd6H2?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fbess> ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
