I disagree. There is nothing wrong to present a use case for service chaining either in SPRING WG with draft-martin-spring-segment-routing-ipv6-use-cases or for that matter in IDR with draft-patel-raszuk-bgp-vector-routing-01 or draft-rfernando-l3vpn-service-chaining-03 at present time.
Holding work and proposals till SFC WG will deliver a new data plane encapsulation and new control plane solution while existing or shipping protocols are already providing or can be easily extended to provide service chaining seems rather like artificial politics and not a real technical IETF argument. IMO it would be much better if we would all focus on technical details of the use cases documents and proposed protocol extensions rather then enforcing serialization delay of work between various WGs. Regards, R. On Mon, Mar 24, 2014 at 6:29 PM, Yakov Rekhter <[email protected]> wrote: > Alvaro, > >> 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-use-ca > ses >> >> Thanks! > > Section 2.3 (IPv6 Segment Routing in the Data Center) of > draft-martin-spring-segment-routing-ipv6-use-cases talks about using > Segment Routing for service chaining. > > Please note that the SFC WG charter calls for the SFC WG to determine > the data plane behavior and the requirements on the control plane > in support of service chaining. Therefore, until the SFC WG determines > the data plane behavior and the control component requirements for > service chaining, presenting service chaining as a use case for IPv6 > Segment Routing header is premature. > > Yakov. > > _______________________________________________ > spring mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
