Re: [spring] I-D Action: draft-ietf-6man-segment-routing-header-13.txt

"Darren Dukes (ddukes)" <ddukes@cisco.com> Wed, 23 May 2018 15:05 UTC

Return-Path: <ddukes@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5471270A0; Wed, 23 May 2018 08:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 M-vLiwoUQjjq; Wed, 23 May 2018 08:05:18 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA7B412E055; Wed, 23 May 2018 08:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=66168; q=dns/txt; s=iport; t=1527087914; x=1528297514; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EeluXXLg7jPlLTqjmf8GTEFozRYIAyTLtcR6KEuuxLA=; b=INRJ1YnEYy/ocW3e2XsRaYWcC6LROPYU7f9PIiyAH2JdBzCCk7o94MA2 Lg48CY+yfuwrecRNksU40BCldcAgSKMynyCHwlJYKvSC9nzD7kZjCetPJ KWYPDwDutOvzqS7YFz5C1nBlLtdY6RpE8V7HvqkFnzRMDpnM1P6UzSg2+ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A3AgCRggVb/4ENJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJOSytifSgKg22UaIFYgTCTNxSBYQMLGAEMB4RAAheCDiE1FwECAQEBAQEBAmwcDIUpAgQBASEKQQsQAgEIEiYBBgMCAgIlCxQDDgIEAQ0FgyICgRtkD6o9ghyEWINsgXwUiCKBVD+BECMMgl2DEQEBAgEBFoEjC1aCQjCCJAKHIiGRFwkChWiIb4E5PoMxh1mJZYZzAhETAYEkAR4DM4FScBUaISoBghgJghcXegECh1yFPm+BFYstAYEXAQE
X-IronPort-AV: E=Sophos;i="5.49,433,1520899200"; d="scan'208,217";a="118301931"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 May 2018 15:05:13 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w4NF5D1H029989 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 May 2018 15:05:13 GMT
Received: from xch-aln-017.cisco.com (173.36.7.27) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 23 May 2018 10:05:13 -0500
Received: from xch-aln-017.cisco.com ([173.36.7.27]) by XCH-ALN-017.cisco.com ([173.36.7.27]) with mapi id 15.00.1320.000; Wed, 23 May 2018 10:05:13 -0500
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: IPv6 List <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>
CC: "cf(mailer list)" <cf@cisco.com>
Thread-Topic: I-D Action: draft-ietf-6man-segment-routing-header-13.txt
Thread-Index: AQHT8p27llJU4axrCkKis74Qm/mh/KQ9vXsA
Date: Wed, 23 May 2018 15:05:13 +0000
Message-ID: <A74D6107-0128-47D3-8439-9879BD44EFA5@cisco.com>
References: <152708369770.27129.9109668605935312444@ietfa.amsl.com>
In-Reply-To: <152708369770.27129.9109668605935312444@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.173]
Content-Type: multipart/alternative; boundary="_000_A74D6107012847D384399879BD44EFA5ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/SJUcxRDyOblekjFIph4S8ghircU>
Subject: Re: [spring] I-D Action: draft-ietf-6man-segment-routing-header-13.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 15:05:21 -0000

Hello Working Group participants.

As per the guideline received from the 6man chairs before London, we have been improving the document in terms of focus, structure and clarity.

The first step accomplished with rev12 is now complemented with rev13.

- Simplify the introduction and avoid duplication by relying on the definition of key terms from the Segment Routing Architecture
- Define the SRH immediately following the introduction
- Define SR node roles
- Group packet processing into a single section
‑ END.X SRv6 SID is removed for definition in future document
- Group packet processing into a single section
- Added an illustrations section for example processing.
- The remaining sections were left relatively untouched, with some small edits for consistent terminology.

The authors believe this revision 13 gives us the right structure to tackle the remaining open issues in revision 14.

Thanks for your continued review, constructive feedback and help.

Darren and Clarence

On May 23, 2018, at 9:54 AM, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance WG of the IETF.

       Title           : IPv6 Segment Routing Header (SRH)
       Authors         : Stefano Previdi
                         Clarence Filsfils
                         John Leddy
                         Satoru Matsushima
                         Daniel Voyer
Filename        : draft-ietf-6man-segment-routing-header-13.txt
Pages           : 29
Date            : 2018-05-23

Abstract:
  Segment Routing can be applied to the IPv6 data plane using a new
  type of Routing Extension Header.  This document describes the
  Segment Routing Extension Header and how it is used by Segment
  Routing capable nodes.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-13
https://datatracker.ietf.org/doc/html/draft-ietf-6man-segment-routing-header-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-segment-routing-header-13


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/

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------