<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-problem-statement" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-problem-statement-04">
   <front>
      <title>SPRING Problem Statement and Requirements</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         </author>
      <author initials="M." surname="Horneffer" fullname="Martin Horneffer">
         </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         </author>
      <date month="April" day="27" year="2015" />
      <abstract>
	 <t>   The ability for a node to specify a forwarding path, other than the
   normal shortest path, that a particular packet will traverse,
   benefits a number of network functions.  Source-based routing
   mechanisms have previously been specified for network protocols, but
   have not seen widespread adoption.  In this context, the term
   &#x27;source&#x27; means &#x27;the point at which the explicit route is imposed&#x27; and
   therefore it is not limited to the originator of the packet (i.e.:
   the node imposing the explicit route may be the ingress node of an
   operator&#x27;s network).

   This document outlines various use cases, with their requirements,
   that need to be taken into account by the Source Packet Routing in
   Networking (SPRING) architecture for unicast traffic.  Multicast use-
   cases and requirements are out of scope of this document.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-problem-statement-04" />
   
</reference>
