Realm-Based Redirection In Diameter
draft-tsou-dime-realm-based-redirect-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tina Tsou (Ting ZOU) , Tom Taylor | ||
| Last updated | 2009-07-13 | ||
| Replaced by | draft-ietf-dime-realm-based-redirect | ||
| 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-realm-based-redirect | |
| 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
RFC 3588 allows a Diameter redirect agent to specify one or more individual hosts to which a Diameter message may be redirected by an upstream Diameter node. However, in some circumstances an operator may wish to redirect messages to an alternate domain without specifying individual hosts. This document specifies the means by which this can be achieved.
Authors
Tina Tsou (Ting ZOU)
Tom Taylor
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)