Clarifications on the Routing of Diameter Requests Based on the Username and the Realm

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 11
Abstract: 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]
Publication Date: 2009-12-01
Status Note: Proposed Standard
DOI: 10.17487/RFC5729
Link: https://doi.org/10.17487/RFC5729
Author(s): Jouni Korhonen
Mark Jones
Lionel Morand
Tina Tsou (Ting ZOU)
Keyword(s): NAI

Latest version of IETF RFC 5729

Document Versions — IETF RFC 5729

▶ IETF RFC 5729 (2009-12-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

IETF RFC 2119 [Active*]
IETF RFC 3588 [Superseded*]
IETF RFC 4282 [Superseded*]

Bibliographic Reference(s)

3GPP.TS-23.003.200906 — 3GPP.23.003 EXTERNAL
3GPP.TS-23.234.200610 — 3GPP.23.234 EXTERNAL
3GPP.TS-24.234.200610 — 3GPP.24.234 EXTERNAL
3GPP.TS-29.273.200909 — 3GPP.29.273 EXTERNAL
WiMAX Forum, "WiMAX Forum Network Architecture (Stage 2: Architecture Tenets, Reference Model and Reference Points)", Release 1 Version 1.2, January 2008. EXTERNAL
DeKok, A., "The Network Access Identifier" , Work in Progress, September 2009. EXTERNAL
Klensin, J., "Internationalized Domain Names in Applications (IDNA): Protocol", Work in Progress, October 2009. EXTERNAL
IETF RFC 1034 [Active*]
IETF RFC 1035 [Active, Amended*]
IETF RFC 2486 [Superseded*]
IETF RFC 2865 [Active*]
IETF RFC 3490 [Superseded*]
IETF RFC 3748 [Active*]
IETF RFC 4005 [Superseded*]
IETF RFC 4072 [Active*]
IETF RFC 4284 [Active*]
IETF RFC 5113 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5729.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm. Available at https://doi.org/10.17487/RFC5729

Snippet:

IETF RFC 5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm. Available at https://doi.org/10.17487/RFC5729

HTML (ISO 690 compliant)

Preview:

IETF RFC 5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm. Available at https://doi.org/10.17487/RFC5729

Snippet:

<span class="citation"><cite>IETF RFC 5729</cite>, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm. Available at <a href="https://doi.org/10.17487/RFC5729" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5729</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 5729, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm
doi: 10.17487/RFC5729
url: https://doi.org/10.17487/RFC5729

Snippet:

<li>
<cite id="bib-rfc5729">IETF RFC 5729</cite>, Clarifications on the Routing of Diameter Requests Based on the Username and the Realm
<span class="doi">10.17487/RFC5729</span>
</li>

Referenced By

IETF RFC 6733 [Active*]
IETF RFC 7542 [Active*]