CurrentPROPOSED STANDARDIETF stream

RFC 5729: Clarifications on the Routing of Diameter Requests Based on the Username and the Realm

In plain English — editorial summary, not part of the RFC

This specification defines the behavior required of Diameter agents to route requests when the User-Name Attribute Value Pair contains a Network Access Identifier formatted with multiple realms. These multi-realm, or "Decorated", Network Access Identifiers are used in order to force the routing of request messages through a predefined list of mediating realms. [STANDARDS-TRACK]

Document record

Document ID
RFC5729
Published
December 2009
Authors
J. Korhonen; M. Jones; L. Morand; T. Tsou
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
11
Also known as
Updates:
RFC 3588

Topics

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/5729-clarifications-on-the-routing-of-diameter-requests-based-on-the-username-and-the