Alvaro, Please refer to following comments regarding Section 2.3 of draft-martin-spring-segment-routing-ipv6-use-cases
These sections describe the use cases of segment routing in data center network. 1. I wonder if now there is a hot discussion on using IPv6 in data center. What is the drive to introduce IPv6 into data center, lack of IP addresses? 2. Regarding "Service Function Chain", it is earlier to involve IPv6 segment routing in the field. Until now, the requirement and architecture of SFC WG is not determined yet. The solution proposed in SFC seems to prefer independent service header or reusing exiting header. Here the solution based on IPv6 segment routing seems only has relation with the use case described by SFC WG. If the SFC WG is taken into account, the requirement, architecture, the solution in SFC WG should also be taken into account. If so, binding the service chain function with a specific IP header maybe not a good choice. That is, for IPv6 segment routing, it is too early to utilize advantage of service chain. Regards, Zhenbin(Robin) > Hi! > > This message officially starts the call for adoption for > draft-martin-spring-segment-routing-ipv6-use-cases. > > Please indicate your position about adopting this use cases draft by > end-of-day on March 27, 2014. > > http://tools.ietf.org/html/draft-martin-spring-segment-routing-ipv6-us > e-ca ses > > Thanks! >From section 2.5: _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
