Hi Chris, On Sep 2, 2014, at 5:12 PM, Chris Bowers wrote: > Has there been any discussion about how to carry both IPv6 and IPv4 packets > with SPRING/SR MPLS labels? From what I can tell, neither > draft-filsfils-spring-segment-routing-04 nor > draft-filsfils-spring-segment-routing-mpls-03 addresses this scenario.
sid's are assigned to ip addresses (e.g. intf addresses). A node having two loopbacks (v4/v6) will have a sid for the ipv4 address and another one for the ipv6. Then you compute your spt's or explicit paths based on your af-topology and you pick the right sid's stack. > In the context of shortest-path forwarding using Node-SID labels, there would > seem to be two main approaches to consider. One could distinguish between > IPv6 and IPv4 packets by using two different Node-SID labels for the same > node. correct. this is same as above: one sid per address (one for v4 and one for v6). s. > Or one could use IPv6 and/or IPv4 Explicit Null labels pushed on the bottom > of the label stack by the SR ingress router. > > Do the authors of these drafts or other working group participants have an > opinion on the best way to address this scenario? > > Thanks, > Chris > > > > _______________________________________________ > spring mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
