Jingrong, Replies inline.
1) About the distinction of Replication-ID and Replication-SID, and > their usage. > > If there is an SID block specially reserved for the P2MP Transport on each > of the Replication Node, and such SID block (on each Replication Node) is > advertised through west-east protocol like IGP/BGP, > > and then the north-south controller (like PCE) can use the > “Replication-ID” and “Node-ID” only, but don’t need to use > “Replication-SID” when populating the “Tree” information to each > “Replication Node” ? > > In that way, the Controller doesn’t need to allocate (and manage) each of > the Replication-SID (Say 1000 Replication-SID) for each Replication Node > (Say 100 nodes). > > As we try to make the distinction clear in the draft, Replication segment is a logical segment that needs to be explicitly instantiated on the node either by PCE or by some other mechanism (maybe local config?). The Replication SID has to be assigned when the Replication segment (with a Replication-ID) is created on the node. Note Replication Segments can be created and deleted over time. and So, there is no pre-allocated block of Replication SIDs that can be announced in IGP or BGP. Effectively, the entity managing Replication segments has to manage the Replication SIDs. > 2) About the Replication Segment illustration. > > The rev-04 add a section “Illustration of a Replication Segment” in > appendix, it is very clear and useful. > > To me, the “Replication State” is more like a “forwarding state”, and I > think it will be helpful to understand the whole solution if: > > a) there is a description/Illustration about the building procedure of the > “forwarding state” ---- What’s the information each Replication Node > receives from the controller, and how each node builds its own forwarding > state. > > b) there is a description/Illustration about the processing of multicast > packet on the whole path of the P2MP tree. > > Illustrations of how packets and handed on a P2MP tree built by stitching Replication segments have been added in latest revision 02 of PIM WG draft: https://datatracker.ietf.org/doc/draft-voyer-pim-sr-p2mp-policy/ We have drafts on PCEP and BGP protocol extensions to instantiate Replication segments. > > > 3) About the applicability of SR-MPLS and SRv6. > > The rev-04 says “Replication segments apply equally to both SR-MPLS and > SRv6 instantiations of Segment Routing.”. > > I am not sure if this document will cover SRv6 as well, but if it does, > then I would like to see the same level of consideration as SR-MPLS. > > > Yes, we will have the same level of details for SRv6 Replication too. -Rishabh
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
