[Idr] Re: Adoption call for IANA Registrations for the BGP Finite State Machine (FSM) (ending 31 May, 2024)

Jeffrey Haas <jhaas@pfrc.org> Fri, 31 May 2024 14:53 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0602C14F71F for <idr@ietfa.amsl.com>; Fri, 31 May 2024 07:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 Bj1y3dKyr5H2 for <idr@ietfa.amsl.com>; Fri, 31 May 2024 07:53:10 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0683DC14F706 for <idr@ietf.org>; Fri, 31 May 2024 07:53:09 -0700 (PDT)
Received: from smtpclient.apple (172-125-100-52.lightspeed.livnmi.sbcglobal.net [172.125.100.52]) by slice.pfrc.org (Postfix) with ESMTPSA id 553C11E039; Fri, 31 May 2024 10:53:09 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_17D8B6DA-5C8E-489B-85A8-B39C93584609"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CAH6gdPzHHRpzYN0Aqpu5Lc9rnccEr3t+F16+DgKih=__kJMWuA@mail.gmail.com>
Date: Fri, 31 May 2024 10:53:08 -0400
Message-Id: <F2BD6765-FD7E-4D19-B29E-76C421A1AB73@pfrc.org>
References: <20240524143725.GA24975@pfrc.org> <CAH6gdPwOzPj=GVS4xc3xofLfcm26hBUJ89r-qT3WyVAwo59vZw@mail.gmail.com> <80FC406B-F478-4913-8BC2-07C671BEB8C0@pfrc.org> <CAH6gdPzHHRpzYN0Aqpu5Lc9rnccEr3t+F16+DgKih=__kJMWuA@mail.gmail.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>
X-Mailer: Apple Mail (2.3696.120.41.1.8)
Message-ID-Hash: DYGFDHKW7LVDFKPVK5BHJVDSPLGF6C54
X-Message-ID-Hash: DYGFDHKW7LVDFKPVK5BHJVDSPLGF6C54
X-MailFrom: jhaas@pfrc.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idr@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: Adoption call for IANA Registrations for the BGP Finite State Machine (FSM) (ending 31 May, 2024)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/B8Hc3jIvlnU4H0BQhjRdXhxFPGo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Thanks, Ketan.

At the moment, the text reads:
"IANA is requested to create a new registry, titled, "BGP-4 Finite State Machine (FSM) Elements"

The intent of the text is a new top-level registry.  If you think this is unclear intent and have better suggested wording, that may help.

Where the registry lives, including as a sub-registry under the existing BGP registries, is within scope of discussion before publication.

-- Jeff


> On May 29, 2024, at 9:57 AM, Ketan Talaulikar <ketant.ietf@gmail.com> wrote:
> 
> Hi Jeff,
> 
> Just to be clear, I am not suggesting/proposing that this be added in the existing BGP Parameters registry group. I can understand the reasons to separate this out in its own registry group. Perhaps the text could clarify.
> 
> I will review and provide further comments on the github link as the document progresses.
> 
> Thanks,
> Ketan
> 
> 
> On Wed, May 29, 2024 at 6:51 PM Jeffrey Haas <jhaas@pfrc.org <mailto:jhaas@pfrc.org>> wrote:
> Ketan,
> 
> 
>> On May 29, 2024, at 12:22 AM, Ketan Talaulikar <ketant.ietf@gmail.com <mailto:ketant.ietf@gmail.com>> wrote:
>> I support the adoption of this document. It will be helpful to ensure consistency and clarity as FSM updates are undertaken.
>> 
>> A few (non-blocking) review comments:
>> 1) I assume this will be parked under the existing BGP Parameters registry? Or is "BGP-4 Finite State Machine (FSM) Elements" to be read as "BGP-4 Finite State Machine (FSM) Parameters" ?
> 
> That's not the current proposal, but you're the second to make this comment.
> 
>> 2) I believe it is necessary to specify the range of each of those registries and reserve 0 as invalid.
>> 3) The allocation policy needs to updated as "IETF Review" per https://datatracker.ietf.org/doc/html/rfc8126#section-4.8 <https://datatracker.ietf.org/doc/html/rfc8126#section-4.8> - additionally, perhaps we should indicate that updates are only possible via Standards Track or Experimental RFCs from the IDR WG?
> 
> I've added this to the pending -02 commit.  Please review.
> 
> https://github.com/ietf-wg-idr/draft-ietf-idr-bgp-fsm-iana/commit/34a8d2b57057413a67d58eefc5afb16cc83d5a69 <https://github.com/ietf-wg-idr/draft-ietf-idr-bgp-fsm-iana/commit/34a8d2b57057413a67d58eefc5afb16cc83d5a69>
> 
> The proposed designated experts along with IETF review are the IDR chairs.
> 
> -- Jeff
>