Hi Nitsan, In case it helps, in my view, RFC9784 defines a virtual ES as a set of EVCs – instead of a set of links (RFC7432). So if you map your definition of EVC in the example below (PW,VLANi) to a virtual ES, I think all the procedures would apply.
Let us know if that is not the case. My two cents.. Jorge From: Nitsan Dolev <[email protected]> Date: Wednesday, May 14, 2025 at 11:09 AM To: [email protected] <[email protected]>, [email protected] <[email protected]>, Jorge Rabadan (Nokia) <[email protected]>, Ali Sajassi (sajassi) <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Cc: Alexander Vainshtein <[email protected]>, Michael Gorokhovsky <[email protected]>, Roger David <[email protected]>, Ron Sdayoor <[email protected]>, Egon Haparnass <[email protected]>, Rotem Cohen <[email protected]> Subject: Clarification needed on draft-ietf-bess-evpn-virtual-eth-segment-19 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. Dear draft-ietf-bess-evpn-virtual-eth-segment-19 co-authors, I will appreciate your opinion on the following question: Section 1.3 of this draft explains the vESes in Access MPLS networks, Where the model described in figure 2 (Quoted below) seems to refer to every single PW as a "single AC". One of the implementations by one of the vendors uses a single PW with a bundle of N VLANS between CE and PE device, where the PE that terminates the PW maps every VLAN to a different EVI/BD instance, i.e. every {PW,VLANi} combination is a different "AC". This is an interesting interpretation but IMHO it does not exactly come to terms, OR not clearly derived, from the description in Section 1.3. If this interpretation is acceptable, I suggest that this option shall also be described in the draft (or in a new RFC***-bis) of this proposed standard. Looking forward to your response, Nitsan Dolev Ribbon Communications MPLS Aggregation Network +-----+ +-----------------+ | CE11|EVC1 | | +-----+ \ +AG1-+ PW1 +-+---+ Cust. A -0----|===========| | +-----+ | ---+===========| | +-------+ +---+ | CE12|EVC2-0/ | PW2 /\ | PE1 +---+ | | | +-----+ ++---+ /=||=| | | +---+PE3+- | //=||=| | |IP/MPLS| | | \ +---+ | // \/ +-+---+ |Core | +---+ \-+ | +-----+EVC3 | PW3// LSP1 | |Network| |CE4| | CE13| \+AG2-+==// | | | +---+ | | +-----+ 0 |==/PW4 /\ +-+---+ | | | | /-+ | 0 |==PW5===||=| | | +---+PE4+-/ +---+ +-----+ /++---+==PW6===||=| PE2 +---+ | | | | CE14|EVC4 | \/ | | +-------+ +---+ +-----+ | LSP2+-+---+ Cust. C +-----------------+ /\ || EVCs <--802.1Q--> <-----MPLS Agg----> <--- EVPN Network ---> <-802.1Q-> Figure 2: Dual-Homed and Single-homed Network on MPLS Aggregation networks Disclaimer 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 -- [email protected] To unsubscribe send an email to [email protected]
