Realm-Based Redirection In Diameter
draft-ietf-dime-realm-based-redirect-12

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Last updated 2013-09-26 (latest revision 2013-09-04)
Replaces draft-tsou-dime-realm-based-redirect
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Lionel Morand
Shepherd write-up Show (last changed 2013-08-02)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 2 more YES or NO OBJECTION positions to pass.
Responsible AD Benoit Claise
Send notices to dime-chairs@tools.ietf.org, draft-ietf-dime-realm-based-redirect@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Internet Engineering Task Force                                  T. Tsou
Internet-Draft                                 Huawei Technologies (USA)
Updates: 6733 (if approved)                                       R. Hao
Intended status: Standards Track                           Comcast Cable
Expires: March 08, 2014                                   T. Taylor, Ed.
                                                     Huawei Technologies
                                                      September 04, 2013

                  Realm-Based Redirection In Diameter
                draft-ietf-dime-realm-based-redirect-12

Abstract

   Message redirection is a basic capability provided by the Diameter
   base protocol.  In its conventional form, message redirection is
   performed by an application-independent "redirect agent", which
   returns one or more individual hosts to the message sender as
   possible destinations of the redirected message.

   However, 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
   that can be achieved when S-NAPTR is not used for dynamic peer
   discovery.  New applications may incorporate this capability by
   reference to the present document.

   Because the redirection mechanism is application-specific, it must be
   performed by a Diameter server or proxy rather than a basic redirect
   agent as defined in the Diameter base protocol.  A new term, "Realm-
   based Redirect Server", is introduced in this document to
   differentiate the application-specific nature of realm-based
   redirection from the conventional Diameter redirection performed by a
   basic redirect agent.

   This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
   the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
   AVPs.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Tsou, et al.             Expires March 08, 2014                 [Page 1]
Internet-Draft     Realm-Based Redirection In Diameter    September 2013

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 08, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Support of Realm-Based Redirection                     Within
       Applications  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Realm-Based Redirection . . . . . . . . . . . . . . . . . . .   4
     3.1.  Configuration of the Realm-based Redirect Server  . . . .   5
     3.2.  Behaviour of Diameter Nodes . . . . . . . . . . . . . . .   5
       3.2.1.  Behaviour at the Realm-based Redirect Server  . . . .   5
       3.2.2.  Proxy Behaviour . . . . . . . . . . . . . . . . . . .   6
       3.2.3.  Client Behaviour  . . . . . . . . . . . . . . . . . .   7
     3.3.  The Redirect-Realm AVP  . . . . . . . . . . . . . . . . .   7
     3.4.  DIAMETER_REALM_REDIRECT_INDICATION Protocol Error Code  .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
Show full document text