Hi all, The text has improved a lot over the last couple of revisions, thank you authors. Appreciating that people want to push this forward, I'm still wondering about a few things:
- The BGP OPENs in the PeerUp are not in TLVs while BGP PDUs everywhere else are. Perhaps not a show stopper, but a somewhat annoying inconsistency. - The new timestamps TLVs are all 32bit, seconds since 1970. There was discussion about timestamp precision but I don't recall whether the year2038 problem was part of that discussion? If this isn't a problem, perhaps a few sentences explaining that would be worthwhile to prevent confusion. - While we don't have hard running code requirements in GROW, documents like these would surely benefit from them. Do we have an idea of current implementations that interop based on the latest text, and should there be an overview of that in the text? The IESG might appreciate that, and given that the Path Marking draft has an overview that will apply to this draft as well, this seems to be low hanging fruit. Then some nits: - sec 4.3 On indexing NLRI in path attributes, it says 'this includes MP_UNREACH_NLRI and MP_REACH_NLRI'. Shouldn't that be 'limited to MP_UNREACH_NLRI and MP_REACH_NLRI'? If new path attributes are defined that somehow carry NLRI, they will affect the indexing according to the current text. - sec 5.6.3, last paragraph 'first bit of second byte will be 8' This was confusing to me, perhaps say 'will be Flag 8'. Thanks, luuk On Mon 2 Nov 2026, 14:39, Job Snijders via Datatracker wrote: > This message starts a WG Last Call for: > draft-ietf-grow-bmp-tlv-22 > > This Working Group Last Call ends on 2026-11-16 > > Abstract: > Most of the BGP Monitoring Protocol (BMP) message types make > provision for data in Type, Length, Value (TLV) format. However, > Route Monitoring messages (which provide a snapshot of the monitored > Routing Information Base) Stats Reports (which supply periodical > counters) and Peer Down messages (which indicate that a peering > session was terminated) do not. Supporting (optional) data in TLV > format across all BMP message types provides consistent and > extensible structures that would be useful in the various use cases > where conveying additional data to a monitoring station is required. > This document updates RFC 7854 [RFC7854] to support TLV data in all > message types and defines some essential TLVs. > > Additionally, this document introduces support for enterprise- > specific TLVs in the BGP Monitoring Protocol by defining an > Enterprise Bit (E-bit) that allows usage of per-vendor Type values. > > File can be retrieved from: > https://www.ietf.org/archive/id/draft-ietf-grow-bmp-tlv-22.txt > > Please review and indicate your support or objection to proceed with the > publication of this document by replying to this email keeping [email protected] > in copy. Objections should be explained and suggestions to resolve them are > highly appreciated. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [1]. > Appropriate IPR disclosures required for full conformance with the provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Kind regards, > > Job > > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-tlv/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-22 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-tlv-22 > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
