IETF Logo Mail Archive

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

"Chengli (Cheng Li)" <chengli13@huawei.com> Mon, 27 May 2019 12:41 UTC

Return-Path: <chengli13@huawei.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 3AABF12015E for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 05:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 nNOsv0ZjWN3I for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 05:41:49 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EBAE1200C4 for <ipv6@ietf.org>; Mon, 27 May 2019 05:41:49 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 2A970B1B15F739D5C0C2; Mon, 27 May 2019 13:41:47 +0100 (IST)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 27 May 2019 13:41:46 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.38]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0439.000; Mon, 27 May 2019 20:41:34 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: 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: AQHVEKPuVKLJkjqSI0Wb/yFi3SOw3aZ+7BMg
Date: Mon, 27 May 2019 12:41:33 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB0260698D@dggeml529-mbx.china.huawei.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com>
In-Reply-To: <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lcLCNSwP9zJA_ojCIkH_xU4VZNE>
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 12:41:51 -0000

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. 
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. 

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
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email