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

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Fri, 13 January 2017 10:25 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 5407612944F for <ipv6@ietfa.amsl.com>; Fri, 13 Jan 2017 02:25:32 -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 2Ox_PJ0cldwZ for <ipv6@ietfa.amsl.com>; Fri, 13 Jan 2017 02:25:30 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78F0E12896F for <6man@ietf.org>; Fri, 13 Jan 2017 02:25:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1776; q=dns/txt; s=iport; t=1484303130; x=1485512730; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=mJAcM2d1rqwJIFqRLJtacaLDm5P6Ii7Zh8ogHHsc908=; b=Ocw/5llz9fbQuVfVxOOAxdraZx+Op1XsBhDMSjz8W4fRdr/GJ/Fztiu6 zh5AaXu++0hnxem+rYzW4y4FF1wqYzGpbI//OhmKDUhudaMQ6GpgfFTXN z05jV1WoBV+ZWC9japtbj4Lz6hWbtZ8uyRRtTvZ5R/rXmryGRuQKtsVIc o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BlAQAmqnhY/5tdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgz8BAQEBAR9fgQkHjVGRdR+DGJISgg0shXYCghA/FAECAQEBAQE?= =?us-ascii?q?BAWMohGkBAQEDATo9AgULAgEIGB4QMiUCBA4FiHsIDrJZig4BAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEdhkWCAgiCV4IUdYE9gzOCMQEEjyCMEgGGW4p9gXdRhD2JaJJ?= =?us-ascii?q?kAR84gUQVGDIBhh9zAYdYgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.33,221,1477958400"; d="scan'208";a="192201910"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jan 2017 10:25:29 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v0DAPTu9018714 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 13 Jan 2017 10:25:29 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 13 Jan 2017 05:25:28 -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; Fri, 13 Jan 2017 05:25:28 -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-03.txt
Thread-Topic: New Version Notification for draft-ietf-6man-segment-routing-header-03.txt
Thread-Index: AQHSbYcWFbPe3FYJn0qdro5U7A6EbqE2h3yA
Date: Fri, 13 Jan 2017 10:25:28 +0000
Message-ID: <961A621F-D5A2-4757-A40A-66843825BAE5@cisco.com>
References: <148430300720.26951.2989954973688460708.idtracker@ietfa.amsl.com>
In-Reply-To: <148430300720.26951.2989954973688460708.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.233.129]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3FB16CCBE86E544CAD25186626A61A96@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TCSyS_bMwPl2FnRQtaYq5entlAw>
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: Fri, 13 Jan 2017 10:25:32 -0000

updated version with the suggested diffs by Brian.

s.


> On Jan 13, 2017, at 11:23 AM, internet-drafts@ietf.org wrote:
> 
> 
> A new version of I-D, draft-ietf-6man-segment-routing-header-03.txt
> has been successfully submitted by Stefano Previdi and posted to the
> IETF repository.
> 
> Name:		draft-ietf-6man-segment-routing-header
> Revision:	03
> Title:		IPv6 Segment Routing Header (SRH)
> Document date:	2017-01-13
> Group:		6man
> Pages:		29
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-6man-segment-routing-header-03.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-03
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-segment-routing-header-03
> 
> 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
>