Re: [Pce] Early Code Point Allocation for draft-ietf-pce-sr-bidir-path
Cheng Li <c.l@huawei.com> Mon, 13 November 2023 10:23 UTC
Return-Path: <c.l@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBFFCC15152E for <pce@ietfa.amsl.com>; Mon, 13 Nov 2023 02:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyJotzGjAwGC for <pce@ietfa.amsl.com>; Mon, 13 Nov 2023 02:23:49 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D65C2C14CE31 for <pce@ietf.org>; Mon, 13 Nov 2023 02:23:22 -0800 (PST)
Received: from frapeml100001.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4STQQb6jgxz6K5Zc; Mon, 13 Nov 2023 18:19:35 +0800 (CST)
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by frapeml100001.china.huawei.com (7.182.85.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Mon, 13 Nov 2023 11:23:19 +0100
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2507.031; Mon, 13 Nov 2023 18:23:17 +0800
From: Cheng Li <c.l@huawei.com>
To: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
CC: Xipengxiao <xipengxiao@huawei.com>
Thread-Topic: [Pce] Early Code Point Allocation for draft-ietf-pce-sr-bidir-path
Thread-Index: AQHaEyeN4UWb9llwOUyqXHLSHB9EYbB4EFuQ
Date: Mon, 13 Nov 2023 10:23:16 +0000
Message-ID: <320fa480249246bb8db6914666fbf94d@huawei.com>
References: <b04949ef-80fb-2b7c-05d5-38818351b600@orange.com> <a2b818ce-b4b0-4a9a-86f1-2cbf377a4744@orange.com>
In-Reply-To: <a2b818ce-b4b0-4a9a-86f1-2cbf377a4744@orange.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.205.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/hvDDmFxRlbyzAYeQvqZ6iQQh-bs>
Subject: Re: [Pce] Early Code Point Allocation for draft-ietf-pce-sr-bidir-path
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2023 10:23:51 -0000
Many thanks to Dhruv and Julien! Respect, Cheng -----Original Message----- From: Pce <pce-bounces@ietf.org> On Behalf Of julien.meuric@orange.com Sent: Thursday, November 9, 2023 5:11 PM To: pce@ietf.org Subject: Re: [Pce] Early Code Point Allocation for draft-ietf-pce-sr-bidir-path Hi all, No concerns have been expressed about this early allocation. We'll thus proceed to the next step. Thanks, Dhruv & Julien On 28/07/2023 15:58, Julien Meuric wrote: > Hi WG, > > We have received a request from the authors of > draft-ietf-pce-sr-bidir-path for an early code point allocation on the > association type referred to in > https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-bidir-path-11# > name-iana-considerations > > RFC 7120 requires to meet the following criteria to proceed: > > b. The format, semantics, processing, and other rules related to > handling the protocol entities defined by the code points (henceforth > called "specifications") must be adequately described in an > Internet-Draft. > c. The specifications of these code points must be stable; i.e., if > there is a change, implementations based on the earlier and later > specifications must be seamlessly interoperable. > > If anyone believes that the draft does not meet these criteria or > believes that early allocation is not appropriate for any other > reason, please send an email to the PCE mailing list explaining why. > If the chairs hear no objections by Monday August 21st, we will kick > off the early allocation request. > > Thanks! > > Dhruv & Julien >
- Re: [Pce] Early Code Point Allocation for draft-i… julien.meuric
- Re: [Pce] Early Code Point Allocation for draft-i… Cheng Li
- [Pce] Early Code Point Allocation for draft-ietf-… julien.meuric
- [Pce] Fwd: [IANA #1290605] Early Code Point Alloc… Dhruv Dhody