[radext] I-D Action: draft-ietf-radext-coa-proxy-03.txt

internet-drafts@ietf.org Fri, 06 April 2018 18:16 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: radext@ietf.org
Delivered-To: radext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0497126BF7; Fri, 6 Apr 2018 11:16:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: radext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152303856167.3845.5897244065847675761@ietfa.amsl.com>
Date: Fri, 06 Apr 2018 11:16:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/KJxeofI53VH--Zmk9fjkKimpKZU>
Subject: [radext] I-D Action: draft-ietf-radext-coa-proxy-03.txt
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.22
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2018 18:16:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the RADIUS EXTensions WG of the IETF.

        Title           : Dynamic Authorization Proxying in Remote Authorization Dial-In User Service Protocol (RADIUS)
        Authors         : Alan DeKok
                          Jouni Korhonen
	Filename        : draft-ietf-radext-coa-proxy-03.txt
	Pages           : 16
	Date            : 2018-04-06

Abstract:
   RFC 5176 defines Change of Authorization (CoA) and Disconnect Message
   (DM) behavior for RADIUS.  Section 3.1 of that document suggests that
   proxying these messages is possible, but gives no guidance as to how
   that is done.  This specification corrects that omission for
   scenarios where networks use Realm-based proxying as defined in
   [RFC7542].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-radext-coa-proxy/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-radext-coa-proxy-03
https://datatracker.ietf.org/doc/html/draft-ietf-radext-coa-proxy-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-radext-coa-proxy-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/