[Pce] 答复: New draft to update IANA registration policy
Aijun Wang <wangaijun@tsinghua.org.cn> Thu, 25 July 2024 08:16 UTC
Return-Path: <wangaijun@tsinghua.org.cn>
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 0485FC180B6F for <pce@ietfa.amsl.com>; Thu, 25 Jul 2024 01:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 YDhE-TVm95Lc for <pce@ietfa.amsl.com>; Thu, 25 Jul 2024 01:16:54 -0700 (PDT)
Received: from mail-m49198.qiye.163.com (mail-m49198.qiye.163.com [45.254.49.198]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB418C16941B for <pce@ietf.org>; Thu, 25 Jul 2024 01:16:51 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.76]) by smtp.qiye.163.com (Hmail) with ESMTPA id 8015B7E00D3; Thu, 25 Jul 2024 16:16:42 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Dhruv Dhody' <dd@dhruvdhody.com>, pce@ietf.org
References: <CAP7zK5a4tnoG7qaRDyBmtnXDosqQnn=OibVMRo211FpwW63Mvg@mail.gmail.com>
In-Reply-To: <CAP7zK5a4tnoG7qaRDyBmtnXDosqQnn=OibVMRo211FpwW63Mvg@mail.gmail.com>
Date: Thu, 25 Jul 2024 16:16:41 +0800
Message-ID: <000001dade6a$fb389520$f1a9bf60$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01DADEAE.095C9870"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKLgjfZn2sjxdQC/nZ6xF06mHtCs7Clzu5Q
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlDQ0xNVkpDHU0fTR5NQ0weGVYeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxNWVdZFhoPEhUdFFlBWU9LSFVKS0lPT09IVUpLS1 VKQktLWQY+
X-HM-Tid: 0a90e8f6bc6f03a2kunm8015b7e00d3
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Mhw6MCo6GjIrKkNRNU4ePT8p FSEKCk5VSlVKTElKQ0JOT0tIS05KVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxNWVdZCAFZQUpJQ0pNNwY+
Message-ID-Hash: IBIQF64BRAM5BWHDEIXONF3BPGCVCTPA
X-Message-ID-Hash: IBIQF64BRAM5BWHDEIXONF3BPGCVCTPA
X-MailFrom: wangaijun@tsinghua.org.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] 答复: New draft to update IANA registration policy
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/OzUHYD1XgNYmHYr0_kY9B6C4I-g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
Hi, Dhruv: Thanks for your quick draft. I think IETF review is enough because the required RFCs needs to be passed all the same stages Although there maybe some different criteria, the related RFCs can assure the interoperability of protocol from different vendors. The document is written clearly. If there is no objection, we can move it faster to be published. Best Regards Aijun Wang China Telecom 发件人: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] 代表 Dhruv Dhody 发送时间: 2024年7月23日 5:19 收件人: pce@ietf.org 主题: [Pce] New draft to update IANA registration policy Hi, I have written a small draft to update the registration policy for all "standards action" to "IETF review" for PCEP registry. https://datatracker.ietf.org/doc/draft-dhody-pce-iana-update/ The approach that the draft currently takes is to make a blanket change to IETF-review for all "standards action" registry to allow experimental track documents to request allocation. There are some registries where the space is tight but IMHO IETF-review is fine -- our WG and LC process should be enough to handle the case of less bits which ideally require creating a new field/registry as we did in the past for LSP object flags! Thoughts? It might be a good idea to move this quickly as John suggested in his AD review of Native-IP draft [1]. Thanks! Dhruv [1] https://mailarchive.ietf.org/arch/msg/pce/xBn2_9E9vy6h5AnYEMMf3I9vbqM/
- [Pce] New draft to update IANA registration policy Dhruv Dhody
- [Pce] 答复: New draft to update IANA registration p… Aijun Wang
- [Pce] Re: 答复: New draft to update IANA registrati… Samuel Sidor (ssidor)
- [Pce] Re: 答复: New draft to update IANA registrati… Dhruv Dhody
- [Pce] Re: 答复: New draft to update IANA registrati… Samuel Sidor (ssidor)
- [Pce] Re: 答复: New draft to update IANA registrati… Dhruv Dhody
- [Pce] Re: 答复: New draft to update IANA registrati… Dhruv Dhody
- [Pce] Re: 答复: New draft to update IANA registrati… tom petch
- [Pce] Re: 答复: New draft to update IANA registrati… tom petch