Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]
Zhuangshunwan <zhuangshunwan@huawei.com> Sun, 05 May 2019 02:34 UTC
Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 820101200FF; Sat, 4 May 2019 19:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ZDO0Xr4CoxeZ; Sat, 4 May 2019 19:34:38 -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 854E0120086; Sat, 4 May 2019 19:34:38 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8C7F89A28180B75D6048; Sun, 5 May 2019 03:34:36 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sun, 5 May 2019 03:34:36 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Sun, 5 May 2019 10:34:27 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>
Thread-Topic: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]
Thread-Index: AdT/U+X6vdEwlS9uQBGKy//tUsGZZgDlxEGw
Date: Sun, 05 May 2019 02:34:27 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858E5B82CD6@NKGEML515-MBX.china.huawei.com>
References: <001b01d4ff54$31784b90$9468e2b0$@ndzh.com>
In-Reply-To: <001b01d4ff54$31784b90$9468e2b0$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.202.166]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858E5B82CD6NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/vZXfQU187cUfRaUO3kA9z68XXnE>
Subject: Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2019 02:34:41 -0000
Support! Thanks, Shunwan From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares Sent: Tuesday, April 30, 2019 8:57 PM To: idr@ietf.org Cc: draft-ietf-idr-segment-routing-te-policy@ietf.org Subject: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019] This begins a 2 week call for early allocation for draft-ietf-idr-segment-routing-te-policy-05.txt . https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/ Please note that in this draft in section 8.1-8.3 to some values with existing early allocation, but in sections 8.3 there are 3 values: (ENLP sub-TLV, Priority sub-TLV, and Policy Name sub-TLV) that need early assignment. Section 8.4, 8.5 and 8.6 define new registries which do not need early allocation. Please comment early and often on early allocation. The authors have indicated their preference for values on this email list. The authors have indicated that they have 3+ implementations which need these values in order to complete the IDR implementation requirements. Cheerily, Susan Hares
- [Idr] Early Code Point Allocation for draft-ietf-… Susan Hares
- Re: [Idr] Early Code Point Allocation for draft-i… Ketan Talaulikar (ketant)
- Re: [Idr] Early Code Point Allocation for draft-i… Kausik Majumdar (kmajumda)
- Re: [Idr] Early Code Point Allocation for draft-i… Paul Mattes
- Re: [Idr] Early Code Point Allocation for draft-i… Dhanendra Jain
- Re: [Idr] Early Code Point Allocation for draft-i… Nandan Saha
- Re: [Idr] Early Code Point Allocation for draft-i… stefano previdi
- Re: [Idr] Early Code Point Allocation for draft-i… Zafar Ali (zali)
- Re: [Idr] Early Code Point Allocation for draft-i… Gaurav Dawra
- Re: [Idr] Early Code Point Allocation for draft-i… Zhuangshunwan
- Re: [Idr] Early Code Point Allocation for draft-i… Lizhenbin
- Re: [Idr] Early Code Point Allocation for draft-i… Przemyslaw Krol
- Re: [Idr] Early Code Point Allocation for draft-i… Ketan Talaulikar (ketant)
- Re: [Idr] Early Code Point Allocation for draft-i… Dhanendra Jain