Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)
draft-chiba-radius-dynamic-authorization-20

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3576.
Authors Murtaza Chiba , Gopal Dommety , Mark Eklund , David Mitton , Dr. Bernard D. Aboba
Last updated 2015-10-14 (Latest revision 2003-05-16)
RFC stream Independent Submission
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Stream ISE state (None)
Consensus boilerplate Unknown
Document shepherd (None)
IESG IESG state Became RFC 3576 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Randy Bush
Send notices to (None)
Email authors IPR References Referenced by Nits Nits v3 Search email archive
draft-chiba-radius-dynamic-authorization-20 
A new Request for Comments is now available in online RFC libraries.

        RFC 3576

        Title:      Dynamic Authorization Extensions to Remote
                    Authentication Dial In User Service (RADIUS)
        Author(s):  M. Chiba, G. Dommety, M. Eklund, D. Mitton,
                    B. Aboba
        Status:     Informational
        Date:       July 2003
        Mailbox:    mchiba@cisco.com, gdommety@cisco.com,
                    meklund@cisco.com, david@mitton.com,
                    bernarda@microsoft.com
        Pages:      30
        Characters: 70027
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-chiba-radius-dynamic-authorization-20.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3576.txt

This document describes a currently deployed extension to the Remote
Authentication Dial In User Service (RADIUS) protocol, allowing
dynamic changes to a user session, as implemented by network access
server products.  This includes support for disconnecting users and
changing authorizations applicable to a user session.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.