Diameter User-Name and Realm Based Request Routing Clarifications
draft-korhonen-dime-nai-routing-02

Document Type Replaced Internet-Draft (individual)
Last updated 2010-04-12 (latest revision 2008-10-27)
Replaced by draft-ietf-dime-nai-routing
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-dime-nai-routing
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-korhonen-dime-nai-routing-02.txt

Abstract

This specification clarifies the Diameter realm based request routing. We focus on the case where a Network Access Identifier in the User-Name AVP is used to populate the Destination-Realm AVP and the Network Access Identifier contains more than one realm. This particular case is possible when the Network Access Identifier decoration is used to force a routing of request messages through a predefined list of realms. However, this functionality is not unambiguously specified in the Diameter Base Protocol specification.

Authors

Jouni Korhonen (jouni.nospam@gmail.com)
Mark Jones (mark.jones@bridgewatersystems.com)
Lionel Morand (lionel.morand@orange.com)
Tina Tsou (tena@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)