<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.previdi-filsfils-isis-segment-routing" target="https://datatracker.ietf.org/doc/html/draft-previdi-filsfils-isis-segment-routing-02">
   <front>
      <title>Segment Routing with IS-IS Routing Protocol</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Bashandy" fullname="Ahmed Bashandy">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Horneffer" fullname="Martin Horneffer">
         <organization>Deutsche Telekom</organization>
      </author>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         <organization>Orange</organization>
      </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         <organization>Orange</organization>
      </author>
      <author initials="I." surname="Milojevic" fullname="Igor Milojevic">
         <organization>Telekom Srbija</organization>
      </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         <organization>British Telecom</organization>
      </author>
      <author initials="S." surname="Ytti" fullname="Saku Ytti">
         <organization>TDC Oy</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Alcatel-Lucent</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Ericsson</organization>
      </author>
      <date month="March" day="21" year="2013" />
      <abstract>
	 <t>   Segment Routing (SR) enables any node to select any path (explicit or
   derived from IGPs SPT computations) for each of its traffic classes.
   The path does not depend on a hop-by-hop signaling technique (neither
   LDP nor RSVP).  It only depends on a set of &quot;segments&quot; that are
   advertised by the IS-IS routing protocol.  These segments act as
   topological sub-paths that can be combined together to form the
   desired path.

   There are two forms of segments: node and adjacency.  A node segment
   represents a path to a node.  An adjacency segment represents a
   specific adjacency to a node.  A node segment is typically a multi-
   hop path while an adjacency segment is a one-hop path.  SR&#x27;s control-
   plane can be applied to IPv6 and MPLS dataplanes.

   Segment Routing control-plane can be applied to the MPLS dataplane: a
   node segment to node N is instantiated in the MPLS dataplane as an
   LSP along the shortest-path (SPT) to the node.  An adjacency segment
   is instantiated in the MPLS dataplane as a cross-connect entry
   pointing to a specific egress datalink.

   This document describes the Segment Routing functions, a set of use
   cases it addresses and the necessary changes that are required in the
   IS-IS protocol.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-previdi-filsfils-isis-segment-routing-02" />
   
</reference>
