Subject: Re: New Version Notification for draft-ietf-6man-segment-routing-header-04.txt

From: "Stefano Previdi (sprevidi)" <[email-masked]>
Date: Wed, 18 Jan 2017 18:41:00 +0000

Sorry,

I forgot to remove some “cleanup-bit” text and references from the draft. Now, hopefully, it is consistent.

thanks.
s.

> On Jan 18, 2017, at 7:39 PM, [email-masked] wrote:
> 
> 
> A new version of I-D, draft-ietf-6man-segment-routing-header-04.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-ietf-6man-segment-routing-header
> Revision:	04
> Title:		IPv6 Segment Routing Header (SRH)
> Document date:	2017-01-18
> Group:		6man
> Pages:		28
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-6man-segment-routing-header-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-04
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-segment-routing-header-04
> 
> Abstract:
>   Segment Routing (SR) allows a node to steer a packet through a
>   controlled set of instructions, called segments, by prepending an SR
>   header to the packet.  A segment can represent any instruction,
>   topological or service-based.  SR allows to enforce a flow through
>   any path (topological, or application/service based) while
>   maintaining per-flow state only at the ingress node to the SR domain.
> 
>   Segment Routing can be applied to the IPv6 data plane with the
>   addition of a new type of Routing Extension Header.  This draft
>   describes the Segment Routing Extension Header Type and how it is
>   used by SR capable nodes.
> 
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat
>