Skip to main content

Reverse CoA in RADIUS

Document Type Replaced Internet-Draft (radext WG)
Expired & archived
Authors Alan DeKok , Vadim Cargatser
Last updated 2023-10-25 (Latest revision 2023-07-27)
Replaced by draft-ietf-radext-reverse-coa
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-radext-reverse-coa
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This document defines a "reverse change of authorization (CoA)" path for RADIUS packets. This specification allows a home server to send CoA packets in "reverse" down a RADIUS/TLS connection. Without this capability, it is impossible for a home server to send CoA packets to a NAS which is behind a firewall or NAT gateway. The reverse CoA functionality extends the available transport methods for CoA packets, but it does not change anything else about how CoA packets are handled.


Alan DeKok
Vadim Cargatser

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)