Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoleted by:

RFC 6733

Updates:

RFC 3588

Authors:

D. Romascanu
H. Tschofenig

Stream:

IETF

Source:

dime (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5719

Discuss this RFC: Send questions or comments to the mailing listdime@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5719

Abstract

The Diameter base specification, described in RFC 3588, provides anumber of ways to extend Diameter, with new Diameter commands (i.e.,messages used by Diameter applications) and applications as the mostextensive enhancements. RFC 3588 illustrates the conditions thatlead to the need to define a new Diameter application or a newcommand code. Depending on the scope of the Diameter extension, IETFactions are necessary. Although defining new Diameter applicationsdoes not require IETF consensus, defining new Diameter commandsrequires IETF consensus per RFC 3588. This has led to questionabledesign decisions by other Standards Development Organizations, whichchose to define new applications on existing commands -- rather thanasking for assignment of new command codes -- for the pure purpose ofavoiding bringing their specifications to the IETF. In some cases,interoperability problems were an effect of the poor design caused byoverloading existing commands.

This document aligns the extensibility rules of the Diameterapplication with the Diameter commands, offering ways to delegatework on Diameter to other SDOs to extend Diameter in a way that doesnot lead to poor design choices. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.