Hi Sasha, There is no section 8.3.2.1 in 7432bis, so I assume you are referring to section 8.3.1.2. Furthermore, I don’t see any contradiction between section 8.3.1.2 and the last bullet of section 19. Section 8.3.1.2 talks about P2MP LSP in general (i.e., using mLDP or RSVP-TE) and section 19 talks about BIER tunnel. To make this point clear, I will change “P2MP/BIER” to “P2MP BIER”.
Cheers, Ali From: Alexander Vainshtein <[email protected]> Date: Monday, August 18, 2025 at 9:08 AM To: Jeffrey (Zhaohui) Zhang <[email protected]>, [email protected] <[email protected]> Cc: BESS <[email protected]> Subject: Re: RFC 9573 and draft-ietf-bess-rfc7432bis Jeffrey, Lots of thanks for your email and for the useful pointer. At the same time, it seems that Section 8.3.2.1 of 7432bis and the last bullet of Section 19 of the same draft present contradictory approaches to allocation of ESI labels without even mentioning each other as the alternatives. Hopefully, it would not be too difficult for the authors to address this contradiction (e.g., by simply adding appropriate cross-references. My 2c, Sasha Regards, Sasha Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Jeffrey (Zhaohui) Zhang <[email protected]> Sent: Monday, August 18, 2025 6:00:14 PM To: Alexander Vainshtein <[email protected]>; [email protected] <[email protected]> Cc: BESS <[email protected]> Subject: [EXTERNAL] RE: RFC 9573 and draft-ietf-bess-rfc7432bis Hi Sacha, Since RFC9573 comes before RFC7432bis, we can’t say that RFC9573 updates RFC7432bis. However, draft-ietf-bess-rfc7432bis does have https://datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-13#name-use-of-domain-wide-common-b that refers to the DCB draft (yes, RFC9573 should be used instead). Thanks. Jeffrey Juniper Business Use Only From: Alexander Vainshtein <[email protected]> Sent: Sunday, August 17, 2025 11:12 AM To: [email protected] Cc: BESS <[email protected]> Subject: [bess] RFC 9573 and draft-ietf-bess-rfc7432bis Importance: High [External Email. Be cautious of content] Hi all, I have looked up Section 8.3.1.2 of the 7432bis draft<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-bess-rfc7432bis-13*section-8.3.1.2__;Iw!!NEt6yMaO-gk!EOI9UUW6IT3m9U7TYxsCvI04mJg6RopeuA-syM_Sa98f6Vy4KlMrDGCedNXZqGhTGB9bhsGvh0VGRnuZx0FST2mwNs2pdRoh$>, and it looks the same as the namesake section of RFC 7432<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/rfc7432*section-8.3.1.2__;Iw!!NEt6yMaO-gk!EOI9UUW6IT3m9U7TYxsCvI04mJg6RopeuA-syM_Sa98f6Vy4KlMrDGCedNXZqGhTGB9bhsGvh0VGRnuZx0FST2mwNka1QUbd$>: both documents assume that, in the case of P2MP LSPs being used for delivery of BUM traffic in EVPN, ESI labels are upstream-allocated from appropriate context label spaces. However, RFC 7432 has been updated by RFC 9573<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/rfc9573__;!!NEt6yMaO-gk!EOI9UUW6IT3m9U7TYxsCvI04mJg6RopeuA-syM_Sa98f6Vy4KlMrDGCedNXZqGhTGB9bhsGvh0VGRnuZx0FST2mwNoLhl_65$> with regard to allocation of ESI labels: these labels can be allocated from the Domain Common Block (DCB) per MH ES by an external management entity and not from the contest-specific label space. Such usage MUST be indicating by setting the DCB Flag in the PTA in the IMET (EVPN Type 3) route. The metadata for RFC 7432 explicitly states that it is updated by RFC 9573 – but this update seems to be ignored in the 7432bis draft. What, if anything, did I miss? Regards, and lost of thanks in advance, Sasha 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]
