[radext] Fwd: New Version Notification for draft-dekok-radext-reverse-coa-01.txt

[Alan DeKok <[e-mail]>]

  Updated with minimal changes.

> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-dekok-radext-reverse-coa-01.txt
> Date: July 27, 2023 at 3:33:14 PM PDT
> To: "Alan DeKok" <[e-mail]>, "Vadim Cargatser" <[e-mail]>
> 
> 
> A new version of I-D, draft-dekok-radext-reverse-coa-01.txt
> has been successfully submitted by Alan DeKok and posted to the
> IETF repository.
> 
> Name:		draft-dekok-radext-reverse-coa
> Revision:	01
> Title:		Reverse CoA in RADIUS
> Document date:	2023-07-27
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/archive/id/draft-dekok-radext-reverse-coa-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-dekok-radext-reverse-coa/
> Html:           https://www.ietf.org/archive/id/draft-dekok-radext-reverse-coa-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dekok-radext-reverse-coa
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-dekok-radext-reverse-coa-01
> 
> 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.
> 
> 
> 
> 
> The IETF Secretariat
> 
>