Ooof. Yes, this seems to be correct (but I wouldn't mind someone else confirming) — what I don't know is how we get the IANA registry updated — can an errata do this (with a note to the IANA), or does it need a new document ? I'll email the IANA and ask…
W On Sun, Oct 30, 2022 at 8:32 AM, RFC Errata System < [email protected]> wrote: > The following errata report has been submitted for RFC7854, > "BGP Monitoring Protocol (BMP)". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid7194 > > -------------------------------------- > Type: Technical > Reported by: Ahmed Elhassany <[email protected]> > > 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. > > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please use > "Reply All" to discuss whether it should be verified or rejected. When a > decision is reached, the verifying party can log in to change the status > and edit the report, if necessary. > > -------------------------------------- > 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
