%% You should probably cite draft-ietf-radext-reverse-coa instead of this I-D.
@techreport{dekok-radext-reverse-coa-00,
    number =    {draft-dekok-radext-reverse-coa-00},
    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/00/},
    author =    {Alan DeKok and Vadim Cargatser},
    title =     {{Reverse CoA in RADIUS}},
    pagetotal = 11,
    year =      2022,
    month =     oct,
    day =       20,
    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.},
}