IETF Logo Mail Archive

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

Jeffrey Haas <jhaas@pfrc.org> Sat, 25 May 2024 18:46 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 DF229C14F5EC for <idr@ietfa.amsl.com>; Sat, 25 May 2024 11:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 u7KhIyI4Wf8g for <idr@ietfa.amsl.com>; Sat, 25 May 2024 11:46:18 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id D787AC14F5E6 for <idr@ietf.org>; Sat, 25 May 2024 11:46:18 -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 C62871E039; Sat, 25 May 2024 14:46:17 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_209D6A1D-B74A-487F-BCAC-556616AF2EBF"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.8\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <AM0PR07MB4131CB3BA4A919309CB0D18DA0F62@AM0PR07MB4131.eurprd07.prod.outlook.com>
Date: Sat, 25 May 2024 14:46:16 -0400
Message-Id: <10D9D5EF-1B50-49FE-8991-89EF4643A235@pfrc.org>
References: <20240524143725.GA24975@pfrc.org> <AM0PR07MB41316B5359916DD53ED9BC3CA0F62@AM0PR07MB4131.eurprd07.prod.outlook.com> <AM0PR07MB4131CB3BA4A919309CB0D18DA0F62@AM0PR07MB4131.eurprd07.prod.outlook.com>
To: tom petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.3696.120.41.1.8)
Message-ID-Hash: NWIXM7HHU44POEJYEPQ6ARNKU5WQGDQH
X-Message-ID-Hash: NWIXM7HHU44POEJYEPQ6ARNKU5WQGDQH
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" <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/2rVtbgXV759rL8tsFVhXT349q9c>
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>

Tom,


> On May 25, 2024, at 6:04 AM, tom petch <ietfc@btconnect.com> wrote:
> 
> Another separate thought.
> 
> IANA list registries by alphabetic order which means that when the names are inconsistent, then so is the ordering.  BGP is an examplar for this.
> 
> The name chosen here will tuck this registry out of sight of the other, related BGP registries which means no-one will find it, or at least, not without a helping hand:-(
> 
> Or perhaps it should be a sub-registry of one of the existing ones.

https://github.com/ietf-wg-idr/draft-ietf-idr-bgp-fsm-iana/issues/5 <https://github.com/ietf-wg-idr/draft-ietf-idr-bgp-fsm-iana/issues/5>


You have a good point.  I don't currently have a strong opinion as to whether this should be a top-level registry or simply moved under the existing bgp parameters registry.  I've opened the issue to ensure we conclude on this point prior to publication.

-- Jeff

v2.34.0 | Report a Bug | By Email | System Status