Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

"Darren Dukes (ddukes)" <ddukes@cisco.com> Fri, 24 May 2019 15:41 UTC

Return-Path: <ddukes@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 945441202F7 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2019 08:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, URIBL_BLOCKED=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 header.b=h+WRIwyj; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=TjvxlV6z
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 yEDQvbxuoNwO for <ipv6@ietfa.amsl.com>; Fri, 24 May 2019 08:41:46 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3A67120096 for <ipv6@ietf.org>; Fri, 24 May 2019 08:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=42613; q=dns/txt; s=iport; t=1558712506; x=1559922106; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=i+3cRpnv8+gD4lbuyO6uoVaydBYbE9rXvXMO+P7+Xrs=; b=h+WRIwyjgg7EyH+cjvYTwP9Sw+3plSdBj8Qhdmgqvf3EuO1rFy3Z71Uy DwNLep1RQId0xAevcylxx242r8jlCvzBSjlao6K8W+HCJ/4R6CSfdWhRp zbWs6Kv4nduERlVQ/a8oiZAziHvB/N5QNf7K7YDsaawyGsFHxaMt14rJ7 E=;
IronPort-PHdr: 9a23:frvjHx89cq6l8f9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+/bR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVcKJFE72N9bhbjcxG4JJU1o2t3w=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BIAAClD+hc/4kNJK1bChwBAQEEAQEHBAEBgVEHAQELAYEOL1ADaVUgBAsoCodQA4RSiiWCV4lAjBSBVoEugSQDUAQJAQEBDAEBGAEKCgIBAYRAAoI/IzQJDgEDAQEEAQECAQRtHAyFSgEBAQEDAQEQCyMBASwLAQsEAgEIEQQBASEBBgchBgsUCQgCBA4FIoMAAYEdTQMdAQIMA5p6AoE4iF+CIIJ5AQEFgTIBg1gNC4IPAwaBNAGEaIZqF4FAP4ERJx+CTD6CGkcBAQOBM1iDD4Imi0UJhxuII40CPQkCgg2FW1iER4Q1g2MbgUpVhmOEAId6gUWMCodegViNFQIEAgQFAg4BAQWBTziBV3AVGiEqAYJBgg8MF4NNhRSFPgFyAYEojEMBgSABAQ
X-IronPort-AV: E=Sophos;i="5.60,507,1549929600"; d="scan'208,217";a="280974959"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 May 2019 15:41:44 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x4OFfiWH025458 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 24 May 2019 15:41:44 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 24 May 2019 10:41:43 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 24 May 2019 11:41:42 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 24 May 2019 10:41:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Q11iCSNCXotSVv9dO/8bYWCc5kxJodtMYEncQsdL1LE=; b=TjvxlV6z5Bq4Pj2gbzXXH2gSDzMUAY0sUUz0/1qj/7M5MDLM0y3qP4mV2cwCMz2N82ix0EWZ8BZgco0+/pPBUt1iCNyMtU480jBS74JIKZZ0it32D1rZvAgfCRch1/t9xYkhR1BIY+vss+TgNLnI4pJ8xrnmCF124tYzF4FGGHc=
Received: from DM6PR11MB3516.namprd11.prod.outlook.com (20.177.220.141) by DM6PR11MB3644.namprd11.prod.outlook.com (20.178.230.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.15; Fri, 24 May 2019 15:41:41 +0000
Received: from DM6PR11MB3516.namprd11.prod.outlook.com ([fe80::d59f:9fbe:1f8b:bac7]) by DM6PR11MB3516.namprd11.prod.outlook.com ([fe80::d59f:9fbe:1f8b:bac7%7]) with mapi id 15.20.1922.016; Fri, 24 May 2019 15:41:41 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Tom Herbert <tom@herbertland.com>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Index: AQHVEKPvir/m07qyXEqVGUt8jQpJGaZ4ZvIAgAA/BgCAAIxxAIAAE/wAgAEmrYA=
Date: Fri, 24 May 2019 15:41:41 +0000
Message-ID: <1D2064A4-ECB2-410C-AC9A-A47B99C190DA@cisco.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com> <16253F7987E4F346823E305D08F9115AAB8AB6E2@nkgeml514-mbx.china.huawei.com> <329C76F8-7D1B-4D26-8F38-B8894505487F@gmail.com> <196ada08-4c0e-de11-ebb9-2ca70ab6f42d@gmail.com> <CALx6S34O8rMtG5_=stR=pb_oEEEsO4RRGm7spnf41O6cs2rPPA@mail.gmail.com>
In-Reply-To: <CALx6S34O8rMtG5_=stR=pb_oEEEsO4RRGm7spnf41O6cs2rPPA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [161.44.192.75]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5e236c07-b3e8-49b7-6257-08d6e05e515e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:DM6PR11MB3644;
x-ms-traffictypediagnostic: DM6PR11MB3644:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <DM6PR11MB36445BA575F5562291DE32BCC8020@DM6PR11MB3644.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0047BC5ADE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(396003)(376002)(366004)(39860400002)(189003)(199004)(13464003)(66476007)(66556008)(64756008)(66446008)(6506007)(66946007)(53546011)(6916009)(186003)(68736007)(2906002)(26005)(73956011)(25786009)(53936002)(6246003)(606006)(54896002)(6306002)(4326008)(102836004)(86362001)(486006)(6486002)(2616005)(446003)(11346002)(76176011)(229853002)(476003)(4743002)(6512007)(3846002)(6116002)(76116006)(91956017)(6436002)(236005)(53946003)(66066001)(14454004)(5660300002)(256004)(14444005)(316002)(478600001)(99286004)(54906003)(966005)(82746002)(33656002)(36756003)(71190400001)(71200400001)(83716004)(81166006)(81156014)(8676002)(7736002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3644; H:DM6PR11MB3516.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 2M925YXqb9sQMZz5HSj2nrYDWgSJAInjcc1hJiqyhLDblYhei6Zdrx91K+WpwWXRTyTuu6WUERdLPcTq/eDar3NSc1ls5EuH1jHq2BrBEOGlhskia6ZfSQNSMM3qEcPANIO4PWYPxFuJLm1rQ/gQrWvaTJ1nJ+4NFz8YUoswBZshrX5Z+fm8GnchXUWJD9k0S/dCOx7yziq103+RVkkkOm9A9XGaSjs+rq9b19g4sDGjm3+4e9A79RjrSn9tgHewKjcIkG4bFwaPE/Ee82ayNhTDNdzUdszevMBI2Atz43l1IjeOsBiUgAtZUbbGHyv9MLDMx/JmR904GgRsZHbty04OZ5ho8581A2P9ARK/1qhpen2T1Mvt8FRu9QHmLZNmfUAUe4BYSKFqd6YzKGx9CBavkb8Zjp/PcvtZFqiMGZs=
Content-Type: multipart/alternative; boundary="_000_1D2064A4ECB2410CAC9AA47B99C190DAciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5e236c07-b3e8-49b7-6257-08d6e05e515e
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2019 15:41:41.3563 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ddukes@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3644
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.20, xch-rcd-010.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BSbQOGxqCzyONNR2mB2E00fmmhY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 24 May 2019 15:41:50 -0000

Tom, the action requested by the WG was to restore the text from rev 17. that was done.

Now you appear to have an editorial comment to change that restored text to be something slightly different that you find more precise.  Is that correct?

Darren

On May 23, 2019, at 6:06 PM, Tom Herbert <tom@herbertland.com<mailto:tom@herbertland.com>> wrote:

On Thu, May 23, 2019 at 1:55 PM Brian E Carpenter
<brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:

On 24-May-19 00:32, Bob Hinden wrote:
Jingrong,

On May 23, 2019, at 4:47 AM, Xiejingrong <xiejingrong@huawei.com<mailto:xiejingrong@huawei.com>> wrote:

Support WGLC.

Some minor/editorial nits:
(1) Below text in section 2 is irrelevant and incorrect, because there is no 'mutable' or 'mutability' word in RFC8200.

The w.g. chairs concluded that the consensus of the 6man w.g. was that the the mutability of the SRH fields be specified.  See:

 https://mailarchive.ietf.org/arch/msg/ipv6/jBpmjGZd77ZRHKOKUF6Hsbcc0is

That makes it both correct and relevant.

To be even more clear, RFC8200 does not use the word mutable, but it
does deal with the mutability of options:
"The third-highest-order bit of the Option Type specifies whether or
not the Option Data of that option can change en route to the
packet's final destination."

That makes one wonder why the text from RFC8200 wasn't directly
adapted for use here. For instance, this could read:

"The highest-order bit of the TLV type specifies whether or not the
TLV data of that option can change en route to the packet's final
destination.

      0 - TLV data does not change en route

      1 - TLV data may change en route"

but the current text reads:

"TLVs may change en route at each segment.  To identify when a TLV
type may change en route the most significant bit of the Type has the
following significance:

     0: TLV data does not change en route

     1: TLV data does change en route"

I believe the intent here is that TLV data may change in route why the
high order bit is set in the type, so the phrase " TLVs may change en
route" is imprecise, only TLV data can change not type or length (if
this is not the intent please let us know). The additional text about
mutability in section 4.3.1 does nothing to bring clarity on this.

Tom

Regards
  Brian



Regards,
Bob



 In the SRH, the Next Header, Hdr Ext Len, and Routing Type fields are
 defined in Section 4.4 of [RFC8200] as not mutable.  The Segments
 Left field is defined as mutable in Section 4.4 of [RFC8200].

 Some of the other fields of the SRH change en route (i.e. they are
 mutable).  The SRH is processed as defined in Section 4.3 of this
 document, and uniquely per SID type.  The mutability of the remaining
 fields in the SRH (Flags, Tag, Segment List, Optional TLVs) are
 defined in that section, in the context of segment processing.

(2)the "or No Next Header" in the title of section 4.3.1.2 is irrelevant.
4.3.1.2.  Upper-layer Header or No Next Header

Thanks,
Jingrong

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Bob Hinden
Sent: Wednesday, May 22, 2019 9:40 PM
To: IPv6 List <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Cc: Bob Hinden <bob.hinden@gmail.com<mailto:bob.hinden@gmail.com>>
Subject: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

Hello,

This message starts a new two week 6MAN Working Group Last Call on advancing:

     Title           : IPv6 Segment Routing Header (SRH)
     Authors         : Clarence Filsfils
                       Darren Dukes
                       Stefano Previdi
                       John Leddy
                       Satoru Matsushima
                       Daniel Voyer
    Filename        : draft-ietf-6man-segment-routing-header-19.txt
    Pages           : 32
    Date            : 2019-05-21

  https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header

as a Proposed Standard.

This document was in an extended last call that started in March of 2018.   An issue tracker was set up, and eight new versions of the draft were produced and discussed on the list and at face to face 6man sessions.   All of the issues in the tracker have been closed.  The chairs believe it is ready to advance, but given the number of changes and the time that elapsed, a new w.g. last call is warranted.  Please review the new document.

Our thanks to the authors/editors and the working group for the work on this document.

Substantive comments and statements of support for publishing this document should be directed to the mailing list. Editorial suggestions can be sent to the author.  This last call will end on 5 June 2019.

Thanks,
Bob & Ole




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

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


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

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