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

[Claudio Jeker <[e-mail]>]

I'm late to the party but I'm very worried of this uptick of QUIC usage
for long lived connections. Nobody did any assesment about the security
of such connections and I'm certain that right now it is fairly simple
to attack long lived QUIC connections via ICMP error messages.
The current situation is in my view much worse than the various TCP
window attacks found in 2004.

This is not against adoption but more a warning that QUIC is no golden
ticket and it is unproven technology for anyhing else than short lived
HTTP sessions.

-- 
:wq Claudio

On Mon, Apr 20, 2026 at 07:37:48AM +0000, Job Snijders wrote:
> Dear all,
> 
> This document has been adopted by GROW. Thank you all for your input!
> 
> Authors, could you please submit the document named "draft-ietf-grow-bmp-over-quic-00"
> 
> Kind regards,
> 
> Job
> GROW co-chair
> 
> On Fri, Mar 27, 2026 at 11:17:43AM -0700, Job Snijders via Datatracker wrote:
> > 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
> 
> _______________________________________________
> GROW mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]