[Pce] Re: 答复: New draft to update IANA registration policy

Dhruv Dhody <dd@dhruvdhody.com> Wed, 31 July 2024 03:41 UTC

Return-Path: <dd@dhruvdhody.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 A2113C180B71 for <pce@ietfa.amsl.com>; Tue, 30 Jul 2024 20:41:17 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dhruvdhody-com.20230601.gappssmtp.com
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 xomGX8hXpFeO for <pce@ietfa.amsl.com>; Tue, 30 Jul 2024 20:41:13 -0700 (PDT)
Received: from mail-oo1-xc34.google.com (mail-oo1-xc34.google.com [IPv6:2607:f8b0:4864:20::c34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C2B3C151525 for <pce@ietf.org>; Tue, 30 Jul 2024 20:41:13 -0700 (PDT)
Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-5d5d077c60aso2423498eaf.1 for <pce@ietf.org>; Tue, 30 Jul 2024 20:41:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20230601.gappssmtp.com; s=20230601; t=1722397272; x=1723002072; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=umjzzdVkvLG3aklgPsvQMbdvUh6nqzNnM6teLs5sxfM=; b=KMjXplNw3i8EFiMIxeZbsZhHigYKmZMye7uoWQ7q+Q7dkUQwjQfLJNXpxl0Qz1R/X+ +ssPZAQevWY+UEsEBAKgei2MZBVeVXbLP7L8IvvXC8JFW2tyWMXxcYuBtL85n6w/KCAv erd589VzHYDseU0mMYf1QxDNIqmb6B+d2cJLMTz4kH+WZWkCTcGMg+hoNUyU5kjXT7dB wTdYuNQXhP7lzqpYyun6F0aDIP1JMbUmLOjAYosA4K+Z3wR+FSY6O2nqIZCDnu0CWFyx Q/gb7DeHu4ElbGPHRx61J1+M0gC4bdUcPxRP30od6shcji63i5Uc8kM+RKQJj1FdiYsY 6osg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722397272; x=1723002072; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=umjzzdVkvLG3aklgPsvQMbdvUh6nqzNnM6teLs5sxfM=; b=YqulNRuce6XNQAFOoklYX7TwM4KiQn2ZuG/sKXQ4Gmnd4t/X1eb7PpURffbKhwq/uv timFbuY9ox0eYj5c72p/1uwOsPVhd0kitUQjALPoBVbPWypTO2p+uazFlxRdOECFQiWG z5YizETbX4XXIGBltUdk8fACA5llaVvNag6aB0ci/vfmaoazP/bypyIgZKjN8gCHNslL 8Pw8Bjju+cCmQf7z4b7bVfY8zpqMyj7+Su2oFJMjXLC9H1od3DzKFmuNeQ4rs8UbORGQ OtZdbHIxsxDE70mJ/IiCcr9bnxq2GrSFZItX0y6DGvADcYR7C6YYIAuRl32l2LPYdlIg dhFg==
X-Gm-Message-State: AOJu0YzSCLppTjTpp4mOllBaT1kHkqzUS8OdfsdgrroTXb1EBiXfN82l hM7bK/h9mtxqxGUoKlySEZXQPbK6WUKUV8iloNPHAQv0Tz90nHQjYHlD+SmX22pjysZG9jpA6to VazMOI0kgk+EZ+BaoZRQ1Ai8syKHXrJ6pHTQ1iSV9xFl6WHP/L1E=
X-Google-Smtp-Source: AGHT+IFvsTWhaeVGijj09WZl9O/iboqBR0Ce5NsorV2l0I+fDkytiwdH/BMI8pCTMB791Cu7RP2B/f8EeIG2cjygfDg=
X-Received: by 2002:a05:6820:811:b0:5d5:b49c:b6ed with SMTP id 006d021491bc7-5d5d0eafa82mr11330438eaf.5.1722397272366; Tue, 30 Jul 2024 20:41:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAP7zK5a4tnoG7qaRDyBmtnXDosqQnn=OibVMRo211FpwW63Mvg@mail.gmail.com> <000001dade6a$fb389520$f1a9bf60$@tsinghua.org.cn> <AM0PR07MB41317C5A88F2E33BDCD625F4A0B52@AM0PR07MB4131.eurprd07.prod.outlook.com> <CAP7zK5bzhBCoj957BOzo-LEq5N3ctdb4dVAU-3Lt0Z6MUzYaFA@mail.gmail.com>
In-Reply-To: <CAP7zK5bzhBCoj957BOzo-LEq5N3ctdb4dVAU-3Lt0Z6MUzYaFA@mail.gmail.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Tue, 30 Jul 2024 20:40:35 -0700
Message-ID: <CAP7zK5aOLVDL8deJcekUU27cAvZmpHDopk=ZgCU+sVVegTQBQw@mail.gmail.com>
To: tom petch <ietfc@btconnect.com>
Content-Type: multipart/alternative; boundary="0000000000009501e7061e82dd75"
Message-ID-Hash: IISE3JVQZP6O567FX3JNRBZ7C6VVMRVH
X-Message-ID-Hash: IISE3JVQZP6O567FX3JNRBZ7C6VVMRVH
X-MailFrom: dd@dhruvdhody.com
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: "pce@ietf.org" <pce@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] Re: 答复: New draft to update IANA registration policy
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/kdhDiYCGLcJUqfBC9I2CpPmU6CE>
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 Tom,

IANA has made the update to -

Wavelength Restriction TLV Action Values

Registry:
https://www.iana.org/assignments/pcep/

Thanks!
Dhruv

On Mon, Jul 29, 2024 at 8:32 PM Dhruv Dhody <dd@dhruvdhody.com> wrote:

> Hi Tom,
>
> On Sat, Jul 27, 2024 at 5:03 AM tom petch <ietfc@btconnect.com> wrote:
>
>> Where it says
>> 'This updates
>>     | Wavelength    |  [RFC8780]  |  |
>>     | Restriction     |    |   |
>>     | Constraint TLV  | |   |
>>     | Action Values '
>> Is this the
>> "Wavelength Restriction TLV Action Values" subregistry ]
>> of RFC8780?
>>
>>
> In the IANA page it is called "Wavelength Restriction Constraint TLV
> Action Values"
> https://www.iana.org/assignments/pcep/pcep.xhtml#wavelength-restriction-constraint-tlv-action-values
>
> RFC 8780 uses "Wavelength Restriction TLV Action Values"
> https://www.rfc-editor.org/rfc/rfc8780.html#section-8.5
>
> With a little digging I found that the keyword "Constraint" was dropped
> from the TLV name during AUTH48 but the iana was not updated. Let me take
> action on fixing this. Thanks for spotting it!
>
> Thanks!
> Dhruv
>
>
>> Tom Petch
>> ________________________________________
>> From: Aijun Wang <wangaijun@tsinghua.org.cn>
>> Sent: 25 July 2024 09:16
>>
>> 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/
>>
>