[spring] I-D Action: draft-ietf-spring-segment-routing-14.txt

internet-drafts@ietf.org Wed, 20 December 2017 22:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: spring@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151380956937.12753.5128198652541730018@ietfa.amsl.com>
Date: Wed, 20 Dec 2017 14:39:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/vzsPY_l8vG2ziSnZdsLkAa64eQg>
Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

        Title           : Segment Routing Architecture
        Authors         : Clarence Filsfils
                          Stefano Previdi
                          Les Ginsberg
                          Bruno Decraene
                          Stephane Litkowski
                          Rob Shakir
	Filename        : draft-ietf-spring-segment-routing-14.txt
	Pages           : 31
	Date            : 2017-12-20

Abstract:
   Segment Routing (SR) leverages the source routing paradigm.  A node
   steers a packet through an ordered list of instructions, called
   segments.  A segment can represent any instruction, topological or
   service-based.  A segment can have a semantic local to an SR node or
   global within an SR domain.  SR allows to enforce a flow through any
   topological path while maintaining per-flow state only at the ingress
   nodes to the SR domain.

   Segment Routing can be directly applied to the MPLS architecture with
   no change on the forwarding plane.  A segment is encoded as an MPLS
   label.  An ordered list of segments is encoded as a stack of labels.
   The segment to process is on the top of the stack.  Upon completion
   of a segment, the related label is popped from the stack.

   Segment Routing can be applied to the IPv6 architecture, with a new
   type of routing header.  A segment is encoded as an IPv6 address.  An
   ordered list of segments is encoded as an ordered list of IPv6
   addresses in the routing header.  The active segment is indicated by
   the Destination Address of the packet.  The next active segment is
   indicated by a pointer in the new routing header.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-spring-segment-routing-14
https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[spring] I-D Action: draft-ietf-spring-segment-ro… internet-drafts