Timothy, Replies inline @ [RP] Thanks, Rishabh.
On Thu, Oct 30, 2025 at 6:41 AM Timothy Winters via Datatracker < [email protected]> wrote: > Document: draft-ietf-bess-mvpn-evpn-sr-p2mp > Title: Multicast and Ethernet VPN with Segment Routing P2MP and Ingress > Replication Reviewer: Timothy Winters Review result: Ready with Issues > > I am an assigned INT directorate reviewer for > draft-ietf-bess-mvpn-evpn-sr-p2mp. > These comments were written primarily for the benefit of the Internet Area > Directors. Document editors and shepherd(s) should treat these comments > just > like they would treat comments from any other IETF contributors and resolve > them along with any other Last Call comments that have been received. > > For more details on the INT Directorate, see > https://datatracker.ietf.org/group/intdir/about/ > <https://datatracker.ietf.org/group/intdir/about/>. > > Summary: I previously reviewed this document, -09. The diff between the > document was fairly large so I just re-read the entire document. I think > it's > ready, I've asked a couple of questions below I think it might be worth > thinking about and potentially answering in the document. > > Comments: > Section 3.2.2 > Has the following: > An egress PE MUST NOT install the SRv6 Multicast Service SID in its > Forwarding > Information Base (FIB) i.e. it MUST NOT forward packets based on the > Locator > portion of the SRv6 Multicast Service SID. > > I would strongly recommend explaining why this is needed, I think I know, > but > it would be helpful in understanding the need when implementing this. > [RP] I assume you meant Section 3.2.1.1.2 in version 16. As you might have realized, this SID is only used to derive the MVPN context on egress PE (on shared SRv6 P2MP P-tunnel). It has no significance on the ingress PE. I have added this explanation in the text. > Section 3.3.2 > "The SRv6 Multicast Service SID MUST be routable within the AS of the > egress > PE." > > What happens if it's not? > > [RP] In this case i.e. MVPN with IR over SRv6, is the SRv6 Multicast Service SID (more specifically the LOC portion of the SID) that takes the packet from an ingress PE to an egress PE. If the LOC is not routable, then the packet will not reach the egress PE. This is similar to other SRv6 SID behaviors like End.DT4/6, End.DT2M etc. > NIT: > > https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-evpn-sr-p2mp-16#section-4.1.1.1.2 > > Third paragraph "Tthe" > [RP] Fixed. > > Based on my review, if I was on the IESG I would ballot this document as NO > OBJECTION. > > > _______________________________________________ > BESS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
