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 in both local and roaming situations. This document specifies the message format, transport, error reporting, accounting, and security services used by all Diameter applications. The Diameter base protocol as defined in this document obsoletes RFC 3588 and RFC 5719, and it must be supported by all new Diameter implementations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6733
- Published
- October 2012
- Authors
- V. Fajardo; J. Arkko; J. Loughney; G. Zorn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 152
- Also known as
- —
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
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 7831Application Bridging for Federated Access Beyond Web (ABFAB) ArchitectureCurrent
May 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 6734Diameter Attribute-Value Pairs for Cryptographic Key TransportCurrent
October 2012
- RFC 7155Diameter Network Access Server ApplicationCurrent
April 2014
- RFC 7423Diameter Applications Design GuidelinesCurrent
November 2014
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- 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?