<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-segment-routing-mpls" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-mpls-01">
   <front>
      <title>Segment Routing with MPLS data plane</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="A." surname="Bashandy" fullname="Ahmed Bashandy">
         </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>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         </author>
      <author initials="E." surname="Crabbe" fullname="Edward Crabbe">
         </author>
      <date month="May" day="29" year="2015" />
      <abstract>
	 <t>   Segment Routing (SR) leverages the source routing paradigm.  A node
   steers a packet through a controlled set of instructions, called
   segments, by prepending the packet with an SR header.  A segment can
   represent any instruction, topological or service-based.  SR allows
   to enforce a flow through any topological path and service chain
   while maintaining per-flow state only at the ingress node to the SR
   domain.

   Segment Routing can be directly applied to the MPLS architecture with
   no change in the forwarding plane.  This drafts describes how Segment
   Routing operates on top of the MPLS data plane.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-segment-routing-mpls-01" />
   
</reference>
