RFC 8559 on Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) Protocol

rfc-editor@rfc-editor.org Wed, 10 April 2019 03:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20376120633; Tue, 9 Apr 2019 20:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aq5qiB3UVsmz; Tue, 9 Apr 2019 20:57:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11AEE1205F6; Tue, 9 Apr 2019 20:57:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 02697B80EAD; Tue, 9 Apr 2019 20:57:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8559 on Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, radext@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190410035728.02697B80EAD@rfc-editor.org>
Date: Tue, 09 Apr 2019 20:57:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/W7rGNCedobQv_Dustig_aAd_9FI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 03:57:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8559

        Title:      Dynamic Authorization Proxying in the 
                    Remote Authentication Dial-In User Service (RADIUS) 
                    Protocol 
        Author:     A. DeKok,
                    J. Korhonen
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    aland@freeradius.org, 
                    jouni.nospam@gmail.com
        Pages:      21
        Characters: 48454
        Updates:    RFC 5176, RFC 5580

        I-D Tag:    draft-ietf-radext-coa-proxy-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8559

        DOI:        10.17487/RFC8559

RFC 5176 defines Change-of-Authorization (CoA) and Disconnect Message
(DM) behavior for RADIUS.  RFC 5176 also suggests that proxying these
messages is possible, but it does not provide guidance as to how that
is done.  This specification updates RFC 5176 to correct that
omission for scenarios where networks use realm-based proxying as
defined in RFC 7542.  This specification also updates RFC 5580 to
allow the Operator-Name attribute in CoA-Request and
Disconnect-Request packets.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC