[Search] [pdf|bibtex] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 12           Informational
          13 14 15 16 17 18 19 20 21 22 23 24 25                        
          26 27 28 29 rfc3580                                           
A new Request for Comments is now available in online RFC libraries.

        RFC 3580

        Title:      IEEE 802.1X Remote Authentication Dial In User
                    Service (RADIUS) Usage Guidelines
        Author(s):  P. Congdon, B. Aboba, A. Smith, G. Zorn, J. Roese
        Status:     Informational
        Date:       September 2003
        Mailbox:    paul_congdon@hp.com, bernarda@microsoft.com,
                    ah_smith@acm.org, gwz@cisco.com, jjr@enterasys.com
        Pages:      30
        Characters: 66136
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-congdon-radius-8021x-29.txt

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

This document provides suggestions on Remote Authentication Dial In
User Service (RADIUS) usage by IEEE 802.1X Authenticators.  The
material in this document is also included within a non-normative
Appendix within the IEEE 802.1X specification, and is being presented
as an IETF RFC for informational purposes.

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

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.