%% You should probably cite draft-ietf-radext-reverse-coa instead of this I-D. @techreport{dekok-radext-reverse-coa-01, number = {draft-dekok-radext-reverse-coa-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-dekok-radext-reverse-coa/01/}, author = {Alan DeKok and Vadim Cargatser}, title = {{Reverse CoA in RADIUS}}, pagetotal = 10, year = 2023, month = jul, day = 27, abstract = {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.}, }