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

Return-Path: <sprevidi@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3356C129556 for <ipv6@ietfa.amsl.com>; Wed, 18 Jan 2017 10:41:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYwdiIoK4OsG for <ipv6@ietfa.amsl.com>; Wed, 18 Jan 2017 10:41:03 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9578129557 for <6man@ietf.org>; Wed, 18 Jan 2017 10:41:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2488; q=dns/txt; s=iport; t=1484764862; x=1485974462; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=IwsyuT/Y+x2Mg3oWs+wIU8hjmZ8/1UXHVNj1rh9UMGw=; b=BegrMd/vqWx/Se8s7fwjWhJ+ySyxKaTgMC9IziGdaURFYoDwAet1WcwT UWoTugvBwmtiS5GYw/9XJ0Y9vdGwIKLT8Ss78G07FC57oIeni/MKQGOIT WeevsJmEOC810sFrNAUvMyUuT4qBhdMyzTp8OWDAs/IgNZMp8AfG+dF1s k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CCAQDytX9Y/5ldJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzkBAQEBAR9ggQkHg0qKCJFjH4MZkhOCCyyFdgIagWk/GAECAQE?= =?us-ascii?q?BAQEBAWMohGkBAQEDASMRQwcLAgEIGAICJgICAjAVEAIEE4h7CA6ve4IlijgBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdgQuFQIIFCIJhghV3gT2DBi2CMQWPJ4waAYZ?= =?us-ascii?q?eiwOBd1GEPYlokm4BHziBRBUYMgGGInMBh3OBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.33,250,1477958400"; d="scan'208";a="196672145"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jan 2017 18:41:01 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v0IIf1eC004631 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <6man@ietf.org>; Wed, 18 Jan 2017 18:41:01 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 18 Jan 2017 13:41:00 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Wed, 18 Jan 2017 13:41:00 -0500
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-Has-Attach:
X-MS-TNEF-Correlator:
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
>