@techreport{rosomakho-httpbis-h3-unbound-data-02,
    number =    {draft-rosomakho-httpbis-h3-unbound-data-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-rosomakho-httpbis-h3-unbound-data/02/},
    author =    {Yaroslav Rosomakho and David Schinazi},
    title =     {{Unbound DATA for CONNECT in HTTP/3}},
    pagetotal = 8,
    year =      2026,
    month =     aug,
    day =       26,
    abstract =  {This document defines a new HTTP/3 frame type, UNBOUND\_DATA, and a corresponding SETTINGS parameter that enables endpoints to negotiate its use. When an endpoint sends an UNBOUND\_DATA frame on a CONNECT request or response stream, it indicates that all subsequent octets on that stream are interpreted as tunneled bytes. This applies both to octets transmitted after CONNECT or extended CONNECT. The use of UNBOUND\_DATA removes the need to encapsulate each portion of the data in DATA frames, reducing framing overhead and simplifying transmission of long-lived CONNECT tunnels.},
}