Shraddha, As I clarified to Jingron in an earlier email in this thread, this restriction applies to Replication nodes, not to intermediate nodes on the paths between upstream and downstream replication nodes. Even if two replication nodes in an Anycast set or PeerSet have the same Replication SID, a packet sent to them using Anycast SID or PeerSet will be delivered to only one of these nodes.
We will update the text in the next revision to specify the restriction only applies to the downstream nodes. -Rishabh On Fri, Dec 9, 2022 at 4:29 AM Shraddha Hegde <shrad...@juniper.net> wrote: > Authors, > > > > I have below comment on the draft. > > > > 1. > > An Anycast SID or BGP PeerSID MUST NOT appear in segment > > list preceding a Replication SID. > > > > The replication SIDs are similar to Binding-SIDs and Binding-SIds do not > have any > > such limitation. If there is an anycast SID before Replication SID, > > The two anycast nodes should have same replication SID for the > <Replication-ID, root-id> > > pair. Intelligent controllers may be able to achieve this. The "MUST NOT" > restriction > > seems unnecessary. > > > > 2. BGP PeerSID MUST NOT appear in segment list > > preceding a Replication SID > > > > I understand this is meant to be PeerSet SID. > > These kind of restrictions don't seem necessary. > > If a multicast tree need to be built across multiple domains > > then it may use BGP PeerSetSID for the inter-domain link as long as the > same replication SID is used > > on the nodes which correspond to the PeerSetSID. > > > > Rgds > > Shraddha > > > > >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
