%% You should probably cite draft-yl-radext-quic-transport-04 instead of this revision.
@techreport{yl-radext-quic-transport-03,
    number =    {draft-yl-radext-quic-transport-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-yl-radext-quic-transport/03/},
    author =    {Shengnan Yue and Changwang Lin and Feng Yang},
    title =     {{RADIUS over QUIC}},
    pagetotal = 14,
    year =      2025,
    month =     nov,
    day =       5,
    abstract =  {The Remote Authentication Dial-In User Server (RADIUS) Protocol can use the User Datagram Protocol (UDP) and the Transport Control Protocol (TCP) as its underlying transport layer. But it permits TCP to be used as a transport protocol for RADIUS only when a transport layer such as TLS or IPsec provides confidentiality and security. QUIC inherently supports encryption (using TLS 1.3), which could provide a higher level of security. And QUIC supports multiple streams over a single connection, enhancing throughput and efficiency. This document defines RADIUS over the QUIC transport protocol, named RADIUSoQUIC.},
}