Diameter User-Name and Realm Based Request Routing Clarifications
draft-korhonen-dime-nai-routing-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jouni Korhonen , Mark Jones , Lionel Morand , Tina Tsou (Ting ZOU) | ||
| Last updated | 2010-04-12 (Latest revision 2008-10-27) | ||
| Replaced by | draft-ietf-dime-nai-routing | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dime-nai-routing | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Mark Jones
Lionel Morand
Tina Tsou (Ting ZOU)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)