RFC 3588: Diameter Base Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6733.
Current document in this lineage: RFC 6733 — Diameter Base Protocol
In plain English — editorial summary, not part of the RFC
The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3588
- Published
- September 2003
- Authors
- P. Calhoun; J. Loughney; E. Guttman; G. Zorn; J. Arkko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 147
- Also known as
- —
- Obsoleted by:
- RFC 6733
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3588 (2003)
- RFC 5719 (2010)
- RFC 6733 (2012) ✓
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 5719Updated IANA Considerations for Diameter Command Code AllocationsObsoleted
January 2010
- RFC 5729Clarifications on the Routing of Diameter Requests Based on the Username and the RealmCurrent
December 2009
- RFC 6408Diameter Straightforward-Naming Authority Pointer (S-NAPTR) UsageCurrent
November 2011
- RFC 6733Diameter Base ProtocolUpdated
October 2012
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4004Diameter Mobile IPv4 ApplicationCurrent
August 2005
- RFC 4005Diameter Network Access Server ApplicationObsoleted
August 2005
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 3539Authentication, Authorization and Accounting (AAA) Transport ProfileCurrent
June 2003
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 3127Authentication, Authorization, and Accounting: Protocol EvaluationCurrent
June 2001
- RFC 5472IP Flow Information Export (IPFIX) ApplicabilityCurrent
March 2009
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?