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

[Ketan Talaulikar <[e-mail]>]

Hello Jeff/All,

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" ?
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 - additionally,
perhaps we should indicate that updates are only possible via Standards
Track or Experimental RFCs from the IDR WG?

Thanks,
Ketan


On Fri, May 24, 2024 at 8:09 PM Jeffrey Haas <[e-mail]> wrote:

> 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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
>