Hi all,


Finally...



The BMP TTL work might not be perfect, and I am sure there will be tons more to 
work in the future, but at this point we need to put decide that this version 
is good enough and move forward. 



This work is good for publication.



Camilo






De: Job Snijders via Datatracker <[email protected]>
Para: <[email protected]>, <[email protected]>, 
<[email protected]>, <[email protected]>
Fecha: lun, 02 nov. 2026 17:39:41 -0500
Asunto: [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://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 
mailto:[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 -- mailto:[email protected]  
To unsubscribe send an email to mailto:[email protected]
_______________________________________________
GROW mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to