Hi David, For (2), we believe no change is needed in the IANA registry; U+002D HYPHEN-MINUS is correct. (The non-breaking hyphen was used in the XML source for presentation purposes in the TXT output.)
Thank you. Megan Ferguson RFC Production Center > On May 22, 2026, at 4:58 PM, David Dong via RT <[email protected]> > wrote: > > Hi, > > We've completed the reference updates for the registrations in RFC 9972, but > we had two questions/comments: > > 1) What should we do about the remaining early allocations for stat types 24 > and 25? > > 24 Number of routes currently in per-AFI/SAFI selected as primary route. > (TEMPORARY - registered 2024-10-18, extension registered 2025-09-23, expires > 2026-10-18) [draft-ietf-grow-bmp-bgp-rib-stats-16] > 25 Number of routes currently in per-AFI/SAFI selected as a backup route. > (TEMPORARY - registered 2024-10-18, extension registered 2025-09-23, expires > 2026-10-18) [draft-ietf-grow-bmp-bgp-rib-stats-16] > > Previously, we were instructed to keep these two early allocations with a > reference to draft-ietf-grow-bmp-bgp-rib-stats-16, with the expectation that > they were going to be moved to a different document > (draft-ietf-grow-bmp-path-marking-tlv). > > 2) It looks like in the html version of RFC 9972 the character encodings of > the hyphens in the term "Adj-RIB-In" (and "Adj-RIB-Out") differs from the txt > version (for all but one instance each, not counting a reference link). We've > listed in the registry the character from the txt version (U+002D > hyphen-minus). Please let us know if we need to correct this. > > txt: > Adj-RIB-In > Adj-RIB-Out > (U+002D HYPHEN-MINUS) > > html: > Adj‑RIB‑In > Adj‑RIB‑Out > (U+2011 NON-BREAKING HYPHEN) > > Thanks! > > Best regards, > > David Dong > IANA Services Sr. Specialist > > On Tue May 19 22:37:03 2026, [email protected] wrote: >> A new Request for Comments is now available in online RFC libraries. >> >> >> RFC 9972 >> >> Title: Advanced BGP Monitoring Protocol (BMP) >> Statistics Types >> Author: M. Srivastava, Ed., >> Y. Liu, >> C. Lin, Ed., >> J. Li >> Status: Standards Track >> Stream: IETF >> Date: May 2026 >> Mailbox: [email protected], >> [email protected], >> [email protected], >> [email protected] >> Pages: 15 >> Updates/Obsoletes/SeeAlso: None >> >> I-D Tag: draft-ietf-grow-bmp-bgp-rib-stats-17.txt >> >> URL: https://www.rfc-editor.org/info/rfc9972 >> >> DOI: 10.17487/RFC9972 >> >> The BGP Monitoring Protocol (BMP) described in RFC 7854 defines >> statistics message types to observe events that occur on a monitored >> router. This document defines new statistics types to monitor BMP >> Adj-RIB-In and Adj-RIB-Out Routing Information Bases (RIBs). >> >> This document is a product of the Global Routing Operations Working >> Group of the IETF. >> >> This is now a Proposed Standard. >> >> STANDARDS TRACK: This document specifies an Internet Standards Track >> protocol for the Internet community, and requests discussion and >> suggestions >> for improvements. Please refer to the current edition of the Official >> Internet Protocol Standards (https://www.rfc-editor.org/standards) >> for the >> standardization state and status of this protocol. Distribution of >> this >> memo is unlimited. >> >> This announcement is sent to the IETF-Announce and rfc-dist lists. >> To subscribe or unsubscribe, see >> https://www.ietf.org/mailman/listinfo/ietf-announce >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >> >> For searching the RFC series, see https://www.rfc-editor.org/search >> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk >> >> Requests for special distribution should be addressed to either the >> author of the RFC in question, or to [email protected]. >> Unless >> specifically noted otherwise on the RFC itself, all RFCs are for >> unlimited distribution. >> >> >> The RFC Editor Team > _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
