metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5719: Updated IANA Considerations for Diameter Command Code Allocations

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 specification, described in RFC 3588, provides a number of ways to extend Diameter, with new Diameter commands (i.e., messages used by Diameter applications) and applications as the most extensive enhancements. RFC 3588 illustrates the conditions that lead to the need to define a new Diameter application or a new command code. Depending on the scope of the Diameter extension, IETF actions are necessary. Although defining new Diameter applications does not require IETF consensus, defining new Diameter commands requires IETF consensus per RFC 3588. This has led to questionable design decisions by other Standards Development Organizations, which chose to define new applications on existing commands -- rather than asking for assignment of new command codes -- for the pure purpose of avoiding bringing their specifications to the IETF. In some cases, interoperability problems were an effect of the poor design caused by overloading existing commands. This document aligns the extensibility rules of the Diameter application with the Diameter commands, offering ways to delegate work on Diameter to other SDOs to extend Diameter in a way that does not lead to poor design choices. [STANDARDS-TRACK]

Document record

Document ID
RFC5719
Published
January 2010
Authors
D. Romascanu; H. Tschofenig
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
5
Also known as
—
Obsoleted by:
RFC 6733
Updates:
RFC 3588

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

One later RFC formally updates or obsoletes 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/5719-updated-iana-considerations-for-diameter-command-code-allocations