[GROW] Re: Call for adoption: draft-liu-grow-bmp-over-quic-06 (Ends 2026-04-10)

[梁艳荣 <[e-mail]>]

Hi WG,

I support WG Adoption of the draft.
This document defines sensible and secure transport for BMP using QUIC, which solves TCP head-of-line blocking, improves security with native TLS, and enhances connection resilience. The multi-stream mapping mechanisms are practical and well-suited for large-scale route monitoring deployments.
We believe this draft is useful and necessary for the evolution of BMP. We support its further development and progression in the working group.

Best regards,
Yanrong Liang

-----Original Message-----
From: Job Snijders via Datatracker <[e-mail]>
Sent: Saturday, March 28, 2026 2:18 AM
To: [e-mail]; [e-mail]; [e-mail]
Subject: [GROW] Call for adoption: draft-liu-grow-bmp-over-quic-06 (Ends 2026-04-10)

This message starts a grow WG Call for Adoption of:
draft-liu-grow-bmp-over-quic-06

This Working Group Call for Adoption ends on 2026-04-10

Abstract:
   The BGP Monitoring Protocol (BMP) provides a convenient interface
   for obtaining route views by monitoring BGP sessions. BMP operates
   over TCP and is unidirectional (from client to server). QUIC
   provides multiple simultaneous streams to carry data in one
   direction, enabling much better efficiency and performance for both
   peers, in particular unidirectional streams can provide reverse data
   protection for the sender. QUIC also provides shorter handshake and
   includes TLS. This document describes how to use BMP over the QUIC
   transport protocol, named BMPoQUIC.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the grow WG. Comments to explain your preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
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].

Thank you.
[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-liu-grow-bmp-over-quic/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-liu-grow-bmp-over-quic-06

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-liu-grow-bmp-over-quic-06