A new version has been posted which addresses all outstanding comments.

Specifically comments from:

Ben Campbell
Adam Roach
Kathleen Moriarty

   Les


> -----Original Message-----
> From: spring [mailto:[email protected]] On Behalf Of internet-
> [email protected]
> Sent: Thursday, January 25, 2018 1:26 AM
> To: [email protected]
> Cc: [email protected]
> Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-15.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-15.txt
>       Pages           : 31
>       Date            : 2018-01-25
> 
> 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-15
> https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-15
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-15
> 
> 
> 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 mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/spring

_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to