[Pce] 答复: Roman Danyliw's Discuss on draft-ietf-pce-pcep-extension-native-ip-35: (with DISCUSS and COMMENT)
Aijun Wang <wangaijun@tsinghua.org.cn> Fri, 23 August 2024 07:32 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 7CD95C14F6A7; Fri, 23 Aug 2024 00:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=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_BLOCKED=0.001, 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 KINhXWZP6vgq; Fri, 23 Aug 2024 00:32:29 -0700 (PDT)
Received: from mail-m12818.netease.com (mail-m12818.netease.com [103.209.128.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FAE1C14F6AA; Fri, 23 Aug 2024 00:32:20 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.76]) by smtp.qiye.163.com (Hmail) with ESMTPA id 59FCD7E0124; Fri, 23 Aug 2024 15:32:02 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Roman Danyliw' <rdd@cert.org>, 'The IESG' <iesg@ietf.org>
References: <172433930732.2565745.5922745396234290818@dt-datatracker-6df4c9dcf5-t2x2k>
In-Reply-To: <172433930732.2565745.5922745396234290818@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Fri, 23 Aug 2024 15:32:01 +0800
Message-ID: <008601daf52e$8bca90a0$a35fb1e0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHwBwquTDIHjWcQv1XAUH16UUsCarIKTgEg
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVkaHkhNVk9MGEkaTkJIQ0tMH1YeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxNWVdZFhoPEhUdFFlBWU9LSFVKS0lPT09IVUpLS1 VKQktLWQY+
X-HM-Tid: 0a917e26439b03a2kunm59fcd7e0124
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6PhQ6Qxw*NDI5NCMICxQRKjhD SUwKCUxVSlVKTElPSEJDSElISUNCVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxNWVdZCAFZQU9OQkw3Bg++
Message-ID-Hash: L2PVIXQ5KZAIOIMBU3JRXLRNTHZ53NU4
X-Message-ID-Hash: L2PVIXQ5KZAIOIMBU3JRXLRNTHZ53NU4
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
CC: draft-ietf-pce-pcep-extension-native-ip@ietf.org, pce-chairs@ietf.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] 答复: Roman Danyliw's Discuss on draft-ietf-pce-pcep-extension-native-ip-35: (with DISCUSS and COMMENT)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/PvTm9MkUemGxyi7RnFYXwsGC6yc>
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, Roman: Thanks for your suggestions. I have updated the "SHOULD" in these sections to "MUST", to eliminate the ambiguity. I have parsed all the content of this document and update "SHOULD" with "MUST" selectively according to their necessity. The updated draft will be uploaded soon to reflect the above changes. Best Regards Aijun Wang China Telecom -----邮件原件----- 发件人: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] 代表 Roman Danyliw via Datatracker 发送时间: 2024年8月22日 23:08 收件人: The IESG <iesg@ietf.org> 抄送: draft-ietf-pce-pcep-extension-native-ip@ietf.org; pce-chairs@ietf.org; pce@ietf.org 主题: [Pce] Roman Danyliw's Discuss on draft-ietf-pce-pcep-extension-native-ip-35: (with DISCUSS and COMMENT) Roman Danyliw has entered the following ballot position for draft-ietf-pce-pcep-extension-native-ip-35: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-native-ip/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- In -35 a number of changes to the IANA considerations were introduced. Specifically, various "shoulds" were replaced with "SHOULDs". This has created ambiguity in the following: -- Section 13.4, The reference for the new Error-type/value SHOULD be set to this document. -- Section 13.5 Each bit SHOULD be tracked with the following qualities: -- Section 13.6 Each value SHOULD be tracked with the following qualities: value, meaning, and defining RFC. -- Section 13.7 Each value SHOULD be tracked with the following qualities: -- Section 13.8 Each bit SHOULD be tracked with the following qualities: What isn't clear when IANA would choose not to track these qualities or set the values. Why create this ambiguity? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Mallory Knodel for the GENART review. Thank for addressing my COMMENT feedback and initial DISCUSS position. _______________________________________________ Pce mailing list -- pce@ietf.org To unsubscribe send an email to pce-leave@ietf.org
- [Pce] Roman Danyliw's Discuss on draft-ietf-pce-p… Roman Danyliw via Datatracker
- [Pce] 答复: Roman Danyliw's Discuss on draft-ietf-p… Aijun Wang
- [Pce] Re: Roman Danyliw's Discuss on draft-ietf-p… John Scudder
- [Pce] Re: Roman Danyliw's Discuss on draft-ietf-p… Roman Danyliw