RFC 7075: Realm-Based Redirection In Diameter
In plain English — editorial summary, not part of the RFC
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).
Document record
- Document ID
- RFC7075
- Published
- November 2013
- Authors
- T. Tsou; R. Hao; T. Taylor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 6733
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 7966Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and RequirementsCurrent
September 2016
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 5777Traffic Classification and Quality of Service (QoS) Attributes for DiameterCurrent
February 2010
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?