[Pce] 答复: Re: Adoption Poll of draft-dhody-pce-iana-update

Aijun Wang <wangaijun@tsinghua.org.cn> Tue, 27 August 2024 07:48 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 C948BC14F68F; Tue, 27 Aug 2024 00:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 lKf7-0njnvqN; Tue, 27 Aug 2024 00:48:23 -0700 (PDT)
Received: from mail-m244.xmail.ntesmail.com (mail-m244.xmail.ntesmail.com [45.195.24.4]) (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 053D8C14F75F; Tue, 27 Aug 2024 00:48:20 -0700 (PDT)
Received: from LAPTOP09T7970K (unknown [219.142.69.76]) by smtp.qiye.163.com (Hmail) with ESMTPA id 4F4A97E01A4; Tue, 27 Aug 2024 15:48:13 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Dhruv Dhody' <dd@dhruvdhody.com>, pce@ietf.org
References: <cf19c561-2070-4f5d-a759-d1dc6faaf65f@orange.com> <849e2faa-d2b5-4917-9f91-30014147d48b@orange.com> <CAP7zK5Ys05cBgU2=UZGEOBB3=U6VG+OVd1TjWL_AWtW_Nkyrqw@mail.gmail.com>
In-Reply-To: <CAP7zK5Ys05cBgU2=UZGEOBB3=U6VG+OVd1TjWL_AWtW_Nkyrqw@mail.gmail.com>
Date: Tue, 27 Aug 2024 15:48:12 +0800
Message-ID: <005701daf855$78263750$6872a5f0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01DAF898.864BC140"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHTRUSDp+Czj7LbxqbwIZ4tKbwfNwDaAr5BAZ/IMSmyNkv64A==
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFKTEtLSjdXWS1ZQUlXWQ8JGhUIEh9ZQVlDQk9PVh5CSx4fQkIeGh9PHlYeHw5VEwETFh oSFyQUDg9ZV1kYEgtZQVlJSkJVSk9JVU1CVUxNWVdZFhoPEhUdFFlBWU9LSFVKS0hJTEJLVUpLS1 VKQktLWQY+
X-HM-Tid: 0a9192ce841b03a2kunm4f4a97e01a4
X-HM-MType: 10
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6MCo6SSo*MzIxDhIwDDhNOhgV MEpPCQtVSlVKTElPTE9PQ0JPSkNKVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxNWVdZCAFZQUlPQ05CNwY+
Message-ID-Hash: JF46YBXVLPATKFUNXRIAN4VGCZNU42C3
X-Message-ID-Hash: JF46YBXVLPATKFUNXRIAN4VGCZNU42C3
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-dhody-pce-iana-update@ietf.org, draft-farrel-pce-experimental-errors@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] 答复: Re: Adoption Poll of draft-dhody-pce-iana-update
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/2qow-3PeFfgEQ56lxmsYsoWmcwU>
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:

 

I support the forward this draft in fast track. Some comments are bellows for your reference:

 

1)     Should the two paragraphs within the “Abstract” be connected via some conjunction, for example, “On the other hand” etc. to make the conversion more smooth?

2)     Should the table 2 in section 3, add one line to describe the Error-Type 0-251, and their corresponding Error-Value?, to cover all the possibility?

The final format of table 2 should be looked like the followings:

 

+============+==================+==================+============+       

|        Error-Type     |                 Meaning               |            Error-value               |           Reference    |    

+============+==================+==================+============+       

| 0-251                     |                  IETF Review         |                  0-255                  |        RFC5440        |     

| 252-255                |           Experimental Use       |                  0-255                  |          [this.I-D]       |    

|                              |                                             |          Experimental Use        |                               |

+----------------+------------------------+------------------------+----------------+

 

Best Regards

 

Aijun Wang

China Telecom

 

发件人: forwardingalgorithm@ietf.org [mailto:forwardingalgorithm@ietf.org] 代表 Dhruv Dhody
发送时间: 2024年8月22日 11:42
收件人: pce@ietf.org
抄送: draft-dhody-pce-iana-update@ietf.org; draft-farrel-pce-experimental-errors@ietf.org
主题: [Pce] Re: Adoption Poll of draft-dhody-pce-iana-update

 

Hi WG,

 

Please find a proposed update that merges draft-farrel-pce-experimental-errors - https://ietf-wg-pce.github.io/draft-ietf-pce-iana-update/draft-ietf-pce-iana-update.html

Diff: https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-pce-iana-update <https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-pce-iana-update&url_2=https://ietf-wg-pce.github.io/draft-ietf-pce-iana-update/draft-ietf-pce-iana-update.txt> &url_2=https://ietf-wg-pce.github.io/draft-ietf-pce-iana-update/draft-ietf-pce-iana-update.txt

 

Please let us know if you have an objection to this update. Authors will post the revision in the datatracker next week and will request Julien to move this I-D quickly. 

Feel free to also provide your comments and edits. 

 

Thanks! 

Dhruv & Adrian

 

On Mon, Aug 19, 2024 at 2:59 PM <julien.meuric@orange.com <mailto:julien.meuric@orange.com> > wrote:

Hi all,

We have clear support and no objection on adopting this small I-D: it is 
now a PCE WG item.

@Authors: please re-submit the draft as draft-ietf-pce-iana-update-00.

@Authors of draft-farrel-pce-experimental-errors: please talk to the 
authors of the aforementioned I-D to consider adding your proposal as a 
contribution into this new WG effort.

Thank you,

Julien


Le 30/07/2024 à 10:36, julien.meuric@orange.com <mailto:julien.meuric@orange.com>  a écrit :
> Hi all,
>
> In his review of the "native IP" draft, John suggested to consider 
> adjusting to "IETF Review" the allocation policy of some of the PCEP 
> registries currently using "Standards Action". Dhruv has submitted 
> draft-dhody-pce-iana-update to quickly resolve this concern and bring 
> higher consistency among PCEP registries.
>
> As a result, does the WG support the adoption of 
> draft-dhody-pce-iana-update [1] as a WG item? Please, share your 
> feedback using the PCE mailing list and include your rationale in case 
> you're opposed.
>
> Thanks,
>
> Julien
>
>
> [1] https://datatracker.ietf.org/doc/draft-dhody-pce-iana-update/
_______________________________________________
Pce mailing list -- pce@ietf.org <mailto:pce@ietf.org> 
To unsubscribe send an email to pce-leave@ietf.org <mailto:pce-leave@ietf.org>