Hi all, We've updated the header for the BMP Peer Down Reason Codes registry to read as follows:
BMP Peer Down Reason Codes Expert(s): John G. Scudder, Rex Fernando (rex), Stephen Stuart Reference: [RFC7854][RFC Errata 7194] Range Registration Procedures 0-127 Standards Action 128-250 Specification Required 251-254 Experimental Use We've also renumbered these registry entries to match: 7-250 Unassigned 251-254 Experimental [RFC7854][RFC Errata 7194] 255 Reserved [RFC7854][RFC Errata 7194] Please see https://www.iana.org/assignments/bmp-parameters thanks, Amanda Baber IANA Operations Manager On Thu Nov 03 11:18:03 2022, [email protected] wrote: > The following errata report has been verified for RFC7854, > "BGP Monitoring Protocol (BMP)". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7194 > > -------------------------------------- > Status: Verified > Type: Technical > > Reported by: Ahmed Elhassany <[email protected]> > Date Reported: 2022-10-30 > Verified by: Warren Kumari (Ops AD) (IESG) > > Section: 10.8 > > Original Text > ------------- > Information type values 0 through 32767 MUST be assigned using the > "Standards Action" policy, and values 32768 through 65530 using the > "Specification Required" policy, defined in [RFC5226]. Values 65531 > through 65534 are Experimental, and values 0 and 65535 are Reserved. > > Corrected Text > -------------- > Information type values 0 through 127 MUST be assigned using the > "Standards Action" policy, and values 128 through 250 using the > "Specification Required" policy, defined in [RFC5226]. Values 251 > through 254 are Experimental, and values 0 and 255 are Reserved. > > Notes > ----- > In Section 4.9 Peer Down Notification. The "Reason" field is defined > as one octet, while the IANA consideration section is defining values > as 2-octets range. This errata suggests updating the IANA registry, > instead of the size of the "Reason" field in the Peer Down > Notification message to avoid breaking existing implementations that > use one-octet reason. > > [WK]: See thread https://mailarchive.ietf.org/arch/msg/grow/s- > qcQpAkFVK3beirNYqY4MYfbFw/ for tracking. IANA has confirmed that they > can update registries from verified errata. > > -------------------------------------- > RFC7854 (draft-ietf-grow-bmp-17) > -------------------------------------- > Title : BGP Monitoring Protocol (BMP) > Publication Date : June 2016 > Author(s) : J. Scudder, Ed., R. Fernando, S. Stuart > Category : PROPOSED STANDARD > Source : Global Routing Operations > Area : Operations and Management > Stream : IETF > Verifying Party : IESG _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
