<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-radext-reverse-coa" target="https://datatracker.ietf.org/doc/html/draft-ietf-radext-reverse-coa-08">
   <front>
      <title>Reverse Change-of-Authorization (CoA) in RADIUS/(D)TLS</title>
      <author initials="A." surname="DeKok" fullname="Alan DeKok">
         <organization>InkBridge</organization>
      </author>
      <author initials="V." surname="Cargatser" fullname="Vadim Cargatser">
         <organization>Cisco</organization>
      </author>
      <date month="August" day="27" year="2025" />
      <abstract>
	 <t>   This document defines a &quot;reverse Change-of-Authorization (CoA)&quot; path
   for RADIUS packets.  A TLS connection is normally used to forward
   request packets from a client to a server and to send responses from
   the server to the client.  This specification allows a server to send
   CoA request packets to the client in &quot;reverse&quot; down that connection,
   and for the client to send responses to the server.  Without this
   capability, it is in general impossible for a server to send CoA
   packets to a Network Access Server (NAS) that is located behind a
   firewall or NAT.  This reverse CoA functionality extends the
   available transport methods for CoA packets, but it does not change
   anything else about how CoA packets are handled.

   This document updates RFC8559.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-radext-reverse-coa-08" />
   
</reference>
