%% You should probably cite rfc8354 instead of this I-D. @techreport{ietf-spring-ipv6-use-cases-00, number = {draft-ietf-spring-ipv6-use-cases-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-spring-ipv6-use-cases/00/}, author = {John Jason Brzozowski and John Leddy and Ida Leung and Stefano Previdi and Mark Townsley and Christian Martin and Clarence Filsfils and Roberta Maglione}, title = {{IPv6 SPRING Use Cases}}, pagetotal = 12, year = 2014, month = may, day = 13, abstract = {Source Packet Routing in Networking (SPRING) architecture leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with SPRING header. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to the SPRING node or global within the SPRING domain. SPRING allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SPRING domain. The objective of this document is to illustrate some use cases that need to be taken into account by the Source Packet Routing in Networking (SPRING) architecture.}, }