idnits 2.17.1 draft-aboba-radius-rfc2869bis-22.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3579 5 Title: RADIUS (Remote Authentication Dial In User 6 Service) Support For Extensible Authentication 7 Protocol (EAP) 8 Author(s): B. Aboba, P. Calhoun 9 Status: Informational 10 Date: September 2003 11 Mailbox: bernarda@microsoft.com, pcalhoun@airespace.com 12 Pages: 46 13 Characters: 104469 14 Updates: 2869 16 I-D Tag: draft-aboba-radius-rfc2869bis-22.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3579.txt 20 This document defines Remote Authentication Dial In User Service 21 (RADIUS) support for the Extensible Authentication Protocol (EAP), an 22 authentication framework which supports multiple authentication 23 mechanisms. In the proposed scheme, the Network Access Server (NAS) 24 forwards EAP packets to and from the RADIUS server, encapsulated 25 within EAP-Message attributes. This has the advantage of allowing the 26 NAS to support any EAP authentication method, without the need for 27 method-specific code, which resides on the RADIUS server. While EAP 28 was originally developed for use with PPP, it is now also in use with 29 IEEE 802. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.