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

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Wed, 18 January 2017 18:41 UTC

From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "<6man@ietf.org>" <6man@ietf.org>
Subject: Re: New Version Notification for draft-ietf-6man-segment-routing-header-04.txt
Thread-Topic: New Version Notification for draft-ietf-6man-segment-routing-header-04.txt
Thread-Index: AQHScbpI2O1w3AUU/U+EojDKCZE326E+5VQA
Date: Wed, 18 Jan 2017 18:41:00 +0000
Message-ID: <CE29ABBD-2871-4221-991A-41E9F7CD67F6@cisco.com>
References: <148476479818.1984.4276872303819042324.idtracker@ietfa.amsl.com>
In-Reply-To: <148476479818.1984.4276872303819042324.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.64.125]
Content-Type: text/plain; charset="utf-8"
Content-ID: <260ADD74B7D214488903D0E38F995E57@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/o3a0kKJUG1d2PQvULArd7omoXrg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jan 2017 18:41:05 -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, internet-drafts@ietf.org 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
>

Re: New Version Notification for draft-ietf-6man-… Stefano Previdi (sprevidi)