Hi, Rishabh: I agree with Huaimo here. You introduced the state at the Replication Node, as that also stated in your document: 2.1. SR-MPLS data planeWhen the Active Segment is a Replication SID, the processing results in a POP operation and lookup of the associated Replication state…. 2.2. SRv6 data planeIn SRv6 [RFC8986], the "Endpoint with replication" behavior (End.Replicate for short) replicates a packet and forwards the packet according to a Replication state…. For multicast services, I think there will be more Replication Nodes existing in the network, for each Replication Node, you must associate the related states to accomplish the multicast delivery. This is certainly controversial to the principles of segment routing. What you claimed in your responses(does not need any state in core nodes) is not the merits of your solution, it belong to the SR technology itself. I think your proposal can be used to achieve the multicast services delivery, but it should not be called segment routing based. Even we do not introduce the concept of “Replication Segment”, we can accomplish the same results via the PCE/PCEP, to download the related states into the transit nodes. Then, I want to know what’s necessary to define the “Replication Segment” and also this draft? Aijun Wang China Telecom On Dec 10, 2022, at 06:05, Rishabh Parekh <risha...@gmail.com> wrote:
|
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring