IETF Logo Mail Archive

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

"Darren Dukes (ddukes)" <ddukes@cisco.com> Mon, 27 May 2019 17:22 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 13F08120043 for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 10:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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 header.b=QS7qYwPy; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=IvbMLSs1
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 vPC-3--WGQqr for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 10:22:21 -0700 (PDT)
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 EF162120006 for <ipv6@ietf.org>; Mon, 27 May 2019 10:22:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4796; q=dns/txt; s=iport; t=1558977741; x=1560187341; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=slgp2Iw5oXl3LWfYi3usKl6YT7v/tqQaBL56iewT9E4=; b=QS7qYwPyYkLYuwbqy9a+c6GyvIL3S8zgECyXI4UmC0wmixhBcPE24HTz WoO4QEWGnchLl7ObUK7WIFnJt4jZFzedA71BcgCQK2PeVMvkSTpXr/mKE rRIZkNLG5eBSSgAlqGw0SAUZhnwAcQLclmPKTKzmV4L6tA8HASrUpyDmV Y=;
IronPort-PHdr: 9a23:rJUTTR21iYXM2ZWEsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxGOt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQBUHmL/PxRyc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BJAADHG+xc/5ldJa1lHAEBAQQBAQcEAQGBUQcBAQsBgT1QA2lVIAQLKAqECYNHA4RSiieCMiWJQYwUgVaBLoEkA1QJAQEBDAEBGA0IAgEBhEACF4I/IzQJDgEDAQEEAQECAQRtHAyFSgEBAQMBAQEQCwYRDAEBLAsBBAcEAgEIEQQBAQECAiMDAgICHwYLFAEICAIEDgUigwABgWoDDg8BAgydCAKBOIhfcYEvgnkBAQWCR4I0DQuCDwMGgQwoAYRohmoXgUA/gREnDBOCTD6CGkcBAQIBgV6DCjKCJoskJIJEmg49CQKCDYY0iH2DZBQHgUpVhmaLf4FFjBCHYIFajRwCBAIEBQIOAQEFgU84gVdwFRohKgGCQYIPg3CFFIU+AXIBAYEnjFsBgSABAQ
X-IronPort-AV: E=Sophos;i="5.60,519,1549929600"; d="scan'208";a="565546967"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 May 2019 17:22:18 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x4RHMINJ030570 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 27 May 2019 17:22:18 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 27 May 2019 12:22:18 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 27 May 2019 13:22:17 -0400
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 27 May 2019 12:22:17 -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=slgp2Iw5oXl3LWfYi3usKl6YT7v/tqQaBL56iewT9E4=; b=IvbMLSs1Y0qdCIVpXlC3WtUa+9rnZSuMgfXQp6NPrvSrODOwTBIXPWx449p6q34aXQ1Hl/0bwEgoTJltbLI7zKweTr/RQ8iJrBsbGOKRRPGPOolsejSeRYxwOrwIAfZ5+7Sx/R1BwIdHdpqNnKYFqNQSNhJIgEV/cAq6GuFZjhU=
Received: from DM6PR11MB3516.namprd11.prod.outlook.com (20.177.220.141) by DM6PR11MB3241.namprd11.prod.outlook.com (20.176.120.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.18; Mon, 27 May 2019 17:22:16 +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.021; Mon, 27 May 2019 17:22:16 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>
CC: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
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/m07qyXEqVGUt8jQpJGaZ+8b+AgABObYA=
Date: Mon, 27 May 2019 17:22:16 +0000
Message-ID: <E5ED231C-2592-4D5F-9FA5-CA3D97994BE8@cisco.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com> <C7C2E1C43D652C4E9E49FE7517C236CB0260698D@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB0260698D@dggeml529-mbx.china.huawei.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.53]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 95b90c58-b1d6-4ff1-8f27-08d6e2c7dd96
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM6PR11MB3241;
x-ms-traffictypediagnostic: DM6PR11MB3241:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <DM6PR11MB3241AB074E77E28DC9E75517C81D0@DM6PR11MB3241.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0050CEFE70
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39860400002)(346002)(396003)(136003)(376002)(199004)(13464003)(189003)(51914003)(8676002)(6436002)(81166006)(81156014)(6486002)(66556008)(66476007)(8936002)(66446008)(102836004)(2906002)(64756008)(966005)(5660300002)(305945005)(86362001)(54906003)(14454004)(91956017)(73956011)(76116006)(478600001)(66946007)(316002)(71200400001)(99286004)(36756003)(25786009)(11346002)(6116002)(256004)(3846002)(4743002)(6506007)(26005)(229853002)(53546011)(7736002)(186003)(6916009)(4326008)(66066001)(6512007)(76176011)(6246003)(71190400001)(83716004)(53936002)(486006)(33656002)(68736007)(82746002)(2616005)(6306002)(476003)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3241; H:DM6PR11MB3516.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: MbR1wo8y8pcjhkJAEgTovDnP10Maz5QCRM/8OVrgPgKiXEV4yaEQhRjvuIuuFScwJBdZVc1gSJFVMkgHDvZrx83Vym/XjYc+XmUgGS6VOC5YhK5S7+lo6w9CvcC8UGiE1f+KMHiW8ZNjcLj5fdeFM6BBYWYTi3DjHwjDKkwvwoB8GgStrwbsA+tQGm9SurKjYdaLPhHMHEPApy8teMQcLa9PQBUA0uPiEZCEKHxNoMcifewFT0ygzJWX+K/xmvnICrNmreJx4YE7dEi/x9g/WpdWWSRx3cgqOpRxPICBYYwWxr//y1GrnRVmEezXnMgx4Ka0qMfDeI5quZWbkhfypWEVLFK5fjmX9KSAnuWZokMIpLEY13YKJXICAbog8LEs12MZ8yY5uCOye+SLH5G5MwkgaSOD/2xRH2APaecalik=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C175C64A611CF242AAB319272CB7161F@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 95b90c58-b1d6-4ff1-8f27-08d6e2c7dd96
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 May 2019 17:22:16.2135 (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: DM6PR11MB3241
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pe1CuO1bxe1sQDyItW6Uk5AVrY0>
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: Mon, 27 May 2019 17:22:23 -0000

Hi Cheng, thanks for the support, I have a couple comments inline.


> On May 27, 2019, at 8:41 AM, Chengli (Cheng Li) <chengli13@huawei.com> wrote:
> 
> Support. Many thanks to authors for their contributions! I agree that we should specify how the AH works with SRH in other drafts. 
> 
> But I can NOT find any text of describing Hdr Ext Len is not mutable in RFC8200. 
> Hdr Ext Len SHOULD be mutable, otherwise, use cases like incremental SRv6 IOAM[1] can not work. 

draft-ali-6man-spring-srv6-oam-01 actually reserves TLV at an SR Source node for use by segment endpoint nodes, so it doesn’t change the size of TLVs (see 4.4.2.1 and 4.4.2.2 of that draft).

> All the use cases of inserting or deleting new TLV, or updating TLV with new length value are not allowed if Hdr Ext Len is not mutable. 

Use cases you’re thinking of should be able to use a method similar to that in draft-ali-6man-spring-srv6-oam, I would be interested to hear about them.

Thanks
  Darren

> 
> I think it is a limitation to SRv6 that we should avoid it definitely.
> 
> 
> Best Regards,
> Cheng
> 
> [1]. https://tools.ietf.org/html/draft-ali-6man-spring-srv6-oam-01#section-4.4.1
> 
> -----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>
> Cc: Bob Hinden <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
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email