Hello All
Thanks to the author for this draft. I reviewed draft-ietf-grow-bmp-tlv-22. I support the publication as it helps to make the BMP messages flexible. However, I have some commented and would like to hear authors comments. Would like those be taken care in final publication. 1. Section 5.2.3 (Stateless Parsing TLV): which capabilities are sent. The text says the capabilities "are all carried in Stateless Parsing TLVs, regardless of their type" and that each capability MUST be in a separate TLV. It is not clear whether an exporter that sends this TLV has to send every capability that matters for parsing. The receiver behavior is only defined for the case where no such TLV is present (use the Peer Up OPENs). A receiver cannot tell, when at least one TLV is present, whether the capabilities that are not listed are not negotiated or should still be taken from the Peer Up. Please state which it is. 2. Section 5.2.3 (Stateless Parsing TLV): meaning of the value. The text says the value is the capability "encoded exactly as it would be in the BGP OPEN of the session". A BGP speaker has two OPENs for a session (sent and received), and the ADD-PATH Send/Receive value describes the ability of the OPEN's sender. For a Route Monitoring message, the Path Identifiers are present depending on both sides (the peer's Send and the local Receive for Adj-RIB-In, the opposite for Adj-RIB-Out), and the TLV has no marker for which OPEN it came from. Please clarify whether the value is the effective state for the direction of the monitored RIB or the capability from one specific OPEN. It would be sufficient to say that an exporter includes the ADD-PATH capability for an AFI/SAFI only when Path Identifiers are used for that AFI/SAFI in the monitored RIB, and that the Send/Receive value can then be ignored by the receiver, as RFC 9069 section 5.2 does for the Loc-RIB Peer Up. 3. Section 6, first paragraph. The paragraph describes the case of a BGP message up to 65535 octets (RFC 8654) that "may cause a BMP PDU ... to overflow", but no procedure is given. Please say what an exporter should do when the UPDATE plus the TLVs do not fit (for example the 16-bit TLV Length or the 15-bit NLRI Index), and what a station should do when it receives such a message. Editorial comments - Figures 6, 7 and 8 show "Type (2 octets)" without the E-bit defined in section 4.1. - Figure 9 (Appendix A) shows the two Group TLVs as type=2; section 5.2.1 defines the Group TLV as type 1 (type 2 is the VRF/Table Name TLV). - Figure 9 shows the Stateless Parsing TLV with length=0x0005. The value is 6 octets (capability code 1, capability length 1, AFI 2, SAFI 1, value 1), so the length should be 0x0006. - Sections 5.6.1.1.2 and 5.6.1.1.4 use lower-case "must" where the other sections use "MUST" for the same rule. Thanks Mukul ________________________________ From: Job Snijders via Datatracker <[email protected]> Date: Monday, November 2, 2026 at 5:40 PM To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [GROW] WG Last Call: draft-ietf-grow-bmp-tlv-22 (Ends 2026-11-16) 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://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-grow-bmp-tlv-22.txt__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZbAGRELU$ 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://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZFpfSWLc$ [2] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZqMYgyKM$ [3] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZ4KoEeBY$ The IETF datatracker status page for this Internet-Draft is: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-tlv/__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZwwZIe0E$ There is also an HTMLized version available at: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-tlv-22__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZkX0u1yc$ A diff from the previous version is available at: https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-grow-bmp-tlv-22__;!!NpxR!ngMkotPEn5l5f5wp5BwAHS7ipoSeztUPUCh1OdwxBz8O1RbpEXMCWGLUheAPao4CGtXJFq2VeDGZvNc6SAA$ _______________________________________________ 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]
