UpdatedPROPOSED STANDARDIETF stream

RFC 6733: Diameter Base Protocol

Still current, but amended. Parts of this document are changed or extended by RFC 7075, RFC 8553. Read both.

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
Obsoletes:
RFC 3588, RFC 5719
Updated by:
RFC 7075, RFC 8553

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 3588 (2003)
  2. RFC 5719 (2010)
  3. RFC 6733 (2012)

Read the full history of Diameter Base Protocol

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.

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?

canonical URL: /rfc/6733-diameter-base-protocol