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

Loa Andersson <loa@pi.nu> Sat, 25 May 2024 17:05 UTC

Return-Path: <loa@pi.nu>
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 83835C14F5EF for <idr@ietfa.amsl.com>; Sat, 25 May 2024 10:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 mFiWSkwPGV5G for <idr@ietfa.amsl.com>; Sat, 25 May 2024 10:04:58 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9440AC14F5F3 for <idr@ietf.org>; Sat, 25 May 2024 10:04:58 -0700 (PDT)
Received: from [192.168.1.78] (c-89a4db54.1063529-0-69706f6e6c79.bbcust.telenor.se [84.219.164.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 3BBE03BCA74; Sat, 25 May 2024 19:04:57 +0200 (CEST)
Message-ID: <0d295beb-d8a4-4bef-b5f4-32d3e7acd53f@pi.nu>
Date: Sat, 25 May 2024 19:04:57 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tom petch <ietfc@btconnect.com>, Jeffrey Haas <jhaas@pfrc.org>, "idr@ietf.org" <idr@ietf.org>
References: <20240524143725.GA24975@pfrc.org> <AM0PR07MB41316B5359916DD53ED9BC3CA0F62@AM0PR07MB4131.eurprd07.prod.outlook.com>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <AM0PR07MB41316B5359916DD53ED9BC3CA0F62@AM0PR07MB4131.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: JYBKX33R6M2VLQB5ZY3AQQUOHDIZCB3Q
X-Message-ID-Hash: JYBKX33R6M2VLQB5ZY3AQQUOHDIZCB3Q
X-MailFrom: loa@pi.nu
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
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/YQrsJIOPqVOpQAlYBOSRcp-W69o>
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, working group,

inline plz.

Den 2024-05-25 kl. 11:44, skrev tom petch:
> I may go through all the names to see if they are exactly the same as in the RFC but may not have time to in the next five days.  They look ok at first reading.
>
> This thought is triggered by
> 1- the Abstract
> which contains a [reference]
> and which uses 'this draft'
> and seems inconsistent as to 'Finite State Machine' or 'finite state machine' - I think that the former is better.
>
> All of which suggests that some editing may be needed.

Agreed, but even though I'd prefer to have the reference in the Abstract 
fixed as quickly as possible, I don't see any of these comments gating 
working group adoption.

/Loa


>
> Tom Petch
>
> _______________________________________
> From: Jeffrey Haas <jhaas@pfrc.org>
> Sent: 24 May 2024 15:37
> To: idr@ietf.org
> Subject: [Idr] Adoption call for IANA Registrations for the BGP Finite State Machine (FSM) (ending 31 May, 2024)
>
> The IDR Chairs are starting a one week adoption call for the IANA
> Registrations for the BGP Finite State Machine (FSM) document:
>
> https://datatracker.ietf.org/doc/draft-hhp-idr-bgp-fsm-iana/
>
> It has been realized as part of working on current IDR documents that there
> is a need for coordinating elements from the RFC 4271 BGP FSM.  In
> particular, session attributes, and event names and numbers.
>
> Existing WG documents will receive assignment in the draft prior to the
> creation of the IANA registry to help move those documents forward in the
> publication process.  Currently, those include:
>
> draft-ietf-idr-bgp-sendholdtimer
> draft-ietf-idr-bgp-bfd-strict-mode
>
> Additionally, the registry and its maintenance will become more important if
> the Working Group takes up the task to move BGP forward in the IETF
> standards process.
>
> Please send your comments for this draft to the mailing list by 31 May, 2024.
>
> -- Jeff (for the Chairs)
>
> _______________________________________________
> Idr mailing list -- idr@ietf.org
> To unsubscribe send an email to idr-leave@ietf.org
>
> _______________________________________________
> Idr mailing list -- idr@ietf.org
> To unsubscribe send an email to idr-leave@ietf.org