IETF Logo Mail Archive

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

Xiejingrong <xiejingrong@huawei.com> Thu, 23 May 2019 08:47 UTC

Return-Path: <xiejingrong@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 69BBC120173 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2019 01:47:31 -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 SmJf6rsz8hjB for <ipv6@ietfa.amsl.com>; Thu, 23 May 2019 01:47:29 -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 075F212010F for <ipv6@ietf.org>; Thu, 23 May 2019 01:47:29 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 6C7F330C965B0A0E993B; Thu, 23 May 2019 09:47:27 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 23 May 2019 09:47:27 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Thu, 23 May 2019 16:47:12 +0800
From: Xiejingrong <xiejingrong@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: AQHVEKPthmHogUcYekiOaMYFQJa/TqZ4ZXaw
Date: Thu, 23 May 2019 08:47:12 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8AB6E2@nkgeml514-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.111.217.214]
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/Foy8NMpT-M-esRCAUVxRwq4Cx6c>
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: Thu, 23 May 2019 08:47:32 -0000

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.

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