RFC 4005 on Diameter Network Access Server Application

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

        RFC 4005

        Title:      Diameter Network Access Server Application
        Author(s):  P. Calhoun, G. Zorn, D. Spence, D. Mitton
        Status:     Standards Track
        Date:       August 2005
        Mailbox:    pcalhoun@cisco.com, gwz@cisco.com,
                    dspence@computer.org, dmitton@circularnetworks.com
        Pages:      85
        Characters: 198871
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-aaa-diameter-nasreq-17.txt

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

This document describes the Diameter protocol application used for
Authentication, Authorization, and Accounting (AAA) services in the
Network Access Server (NAS) environment.  When combined with the
Diameter Base protocol, Transport Profile, and Extensible
Authentication Protocol specifications, this application specification
satisfies typical network access services requirements.

Initial deployments of the Diameter protocol are expected to include
legacy systems.  Therefore, this application has been carefully
designed to ease the burden of protocol conversion between RADIUS and 
Diameter.  This is achieved by including the RADIUS attribute space to
eliminate the need to perform many attribute translations.

The interactions between Diameter applications and RADIUS specified
in this document are to be applied to all Diameter applications.  In
this sense, this document extends the Base Diameter protocol.

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
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.

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.