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


        RFC 2882

        Title:      Network Access Servers Requirements: Extended
                    RADIUS Practices
        Author(s):  D. Mitton
        Status:     Informational
        Date:       July 2000
        Mailbox:    dmitton@nortelnetworks.com
        Pages:      16
        Characters: 31431
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-nasreq-ext-radiuspract-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2882.txt


This document describes current practices implemented in NAS products
that go beyond the scope of the RADIUS RFCs 2138, 2139. The
purpose of this effort is to give examples that show the need for
addressing and standardizing these types of ad-hoc functions.  Since
many of these features require a matching server support component,
the ability to deploy and manage interoperable NAS and AAA server
products is severely hindered.
 
These practices are documented here to show functions that are
obviously desired in developing future AAA protocols for NAS
deployment. 

This document is a product of the Network Access Server Requirements
Working Group of the IETF.

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.