WG, Hi! <draft-bestbar-spring-scalable-ns> advocates a couple of options for determining which slice-aggregate the packet belongs to: (a) Segment Range as Slice Selector (b) Global Identifier as Slice Selector In option (a), which is what is relevant for draft-dong-spring-sr-for-enhanced-vpn, the following is advocated:
".. multiple per slice aggregate Prefix-SIDs (Slice Prefix-SIDs) can be assigned for the same prefix such that they all share the same IGP computed path over one topology and optimized for one algorithm to allow the steering of traffic to the same prefix along a path but over different slice aggregates.." I have reviewed the latest version (rev 13) of draft-dong-spring-sr-for-enhanced-vpn and it is good to see the above point incorporated in section 2.3. Thanks to the authors for embracing this important aspect – it does significantly enhance the scaling story for the proposed solution. Regards, -Pavan On Wed, Jan 27, 2021 at 5:46 AM James Guichard < james.n.guich...@futurewei.com> wrote: > Dear WG: > > > > This message starts a 2 week WG adoption call for > https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/ > ending February 10th 2021. > > > > After review of the document please indicate support (or not) for WG > adoption to the mailing list and if you are willing to work on the > document, please state this explicitly. This gives the chairs an indication > of the energy level of people in the working group willing to work on this > document. Please also provide comments/reasons for your support (or lack > thereof) as this is a stronger way to indicate your (non) support as this > is not a vote. > > > > Thanks! > > > > Jim, Bruno & Joel > > > > > > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring >
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring