database logo graphic

RFC 7075

"Realm-Based Redirection In Diameter", November 2013

Canonical URL:
http://www.rfc-editor.org/rfc/rfc7075.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Updates:
RFC 6733
Authors:
T. Tsou
R. Hao
T. Taylor, Ed.
Stream:
IETF
Source:
dime (ops)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

The Diameter protocol includes a capability for message redirection, controlled by an application-independent "redirect agent". In some circumstances, an operator may wish to redirect messages to an alternate domain without specifying individual hosts. This document specifies an application-specific mechanism by which a Diameter server or proxy (node) can perform such a redirection when the Straightforward-Naming Authority Pointer (S-NAPTR) is not used for dynamic peer discovery. A node performing this new function is referred to as a "Realm-based Redirect Server". This memo updates Sections 6.13 and 6.14 of RFC 6733 with respect to the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time Attribute-Value Pairs (AVPs).


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.