<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yl-radext-quic-transport" target="https://datatracker.ietf.org/doc/html/draft-yl-radext-quic-transport-04">
   <front>
      <title>RADIUS over QUIC</title>
      <author initials="" surname="Yue" fullname="Shengnan Yue">
         <organization>China Mobile</organization>
      </author>
      <author initials="C." surname="Lin" fullname="Changwang Lin">
         <organization>New H3C Technologies</organization>
      </author>
      <author initials="F." surname="Yang" fullname="Feng Yang">
         <organization>China Mobile</organization>
      </author>
      <date month="May" day="12" year="2026" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-yl-radext-quic-transport-04" />
   
</reference>
