idnits 2.17.1 draft-aboba-radius-iana-07.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 3575 5 Title: IANA Considerations for RADIUS 6 (Remote Authentication Dial In User Service) 7 Author(s): B. Aboba 8 Status: Standards Track 9 Date: July 2003 10 Mailbox: bernarda@microsoft.com 11 Pages: 8 12 Characters: 15539 13 Updates: 2865 15 I-D Tag: draft-aboba-radius-iana-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3575.txt 19 This document describes the IANA considerations for the Remote 20 Authentication Dial In User Service (RADIUS). 22 This is now a Proposed Standard Protocol. 24 This document specifies an Internet standards track protocol for 25 the Internet community, and requests discussion and suggestions 26 for improvements. Please refer to the current edition of the 27 "Internet Official Protocol Standards" (STD 1) for the 28 standardization state and status of this protocol. Distribution 29 of this memo is unlimited. 31 This announcement is sent to the IETF list and the RFC-DIST list. 32 Requests to be added to or deleted from the IETF distribution list 33 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 34 added to or deleted from the RFC-DIST distribution list should 35 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 37 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 38 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 39 help: ways_to_get_rfcs. For example: 41 To: rfc-info@RFC-EDITOR.ORG 42 Subject: getting rfcs 44 help: ways_to_get_rfcs 46 Requests for special distribution should be addressed to either the 47 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 48 specifically noted otherwise on the RFC itself, all RFCs are for 49 unlimited distribution.echo 50 Submissions for Requests for Comments should be sent to 51 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 52 Authors, for further information.