Reverse Change-of-Authorization (CoA) in RADIUS/(D)TLS
draft-ietf-radext-reverse-coa-08

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-radext-reverse-coa@ietf.org, paul.wouters@aiven.io, radext-chairs@ietf.org, radext@ietf.org, rfc-editor@rfc-editor.org, valery@smyslov.net
Subject: Protocol Action: 'Reverse Change-of-Authorization (CoA) in RADIUS/(D)TLS' to Proposed Standard (draft-ietf-radext-reverse-coa-08.txt)

The IESG has approved the following document:
- 'Reverse Change-of-Authorization (CoA) in RADIUS/(D)TLS'
  (draft-ietf-radext-reverse-coa-08.txt) as Proposed Standard

This document is the product of the RADIUS EXTensions Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-radext-reverse-coa/

Ballot Text

Technical Summary

   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.

Working Group Summary

   The consensus was strong, but from a very small group of people.

Document Quality

    There are several implementations of the described technology (some using
    vendor-specific attributes):
  - FreeRADIUS
  - Cisco
  - Aruba



Personnel

   The Document Shepherd for this document is Valery Smyslov. The
   Responsible Area Director is Paul Wouters.

RFC Editor Note