idnits 2.17.1 draft-ietf-aaa-diameter-17.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 3588 5 Title: Diameter Base Protocol 6 Author(s): P. Calhoun, J. Loughney, E. Guttman, G. Zorn, 7 J. Arkko 8 Status: Standards Track 9 Date: September 2003 10 Mailbox: pcalhoun@airespace.com, john.Loughney@nokia.com, 11 Jari.Arkko@ericsson.com, erik.guttman@sun.com 12 Pages: 147 13 Characters: 341261 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-aaa-diameter-17.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3588.txt 20 The Diameter base protocol is intended to provide an Authentication, 21 Authorization and Accounting (AAA) framework for applications such as 22 network access or IP mobility. Diameter is also intended to work in 23 both local Authentication, Authorization & Accounting and roaming 24 situations. This document specifies the message format, transport, 25 error reporting, accounting and security services to be used by all 26 Diameter applications. The Diameter base application needs to be 27 supported by all Diameter implementations. 29 This document is a product of the Authentication, Authorization and 30 Accounting Working Group of the IETF. 32 This is now a Proposed Standard Working Group. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.