[rfc-dist] RFC 3539 on Authentication, Authorization and Accounting (AAA) Transport Profile

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Fri, 20 Jun 2003 16:07:34 -0700


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

        RFC 3539

        Title:      Authentication, Authorization and Accounting (AAA)
                    Transport Profile
        Author(s):  B. Aboba, J. Wood
        Status:     Standards Track
        Date:       June 2003
        Mailbox:    bernarda@microsoft.com, jonwood@speakeasy.net
        Pages:      41
        Characters: 93110
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-aaa-transport-12.txt

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

This document discusses transport issues that arise within protocols
for Authentication, Authorization and Accounting (AAA).  It also
provides recommendations on the use of transport by AAA protocols.
This includes usage of standards-track RFCs as well as experimental

This document is a product of the Authentication, Authorization and
Accounting Working Group of the IETF.

This is now a Proposed Standard Protocol.

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
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <030620160534.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3539

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <030620160534.RFC@RFC-EDITOR.ORG>