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

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Last updated 2013-08-02 (latest revision 2013-07-29)
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
Document shepherd Lionel Morand
Shepherd write-up Show (last changed 2013-06-27)
IESG IESG state AD Evaluation::Revised I-D Needed
Telechat date
Responsible AD Benoit Claise
Send notices to dime-chairs@tools.ietf.org, draft-ietf-dime-realm-based-redirect@tools.ietf.org
Internet Engineering Task Force                                  T. Tsou
Internet-Draft                                 Huawei Technologies (USA)
Updates: 6733 (if approved)                                       R. Hao
Intended status: Standards Track                           Comcast Cable
Expires: January 29, 2014                                 T. Taylor, Ed.
                                                     Huawei Technologies
                                                           July 28, 2013

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

Abstract

   The Diameter protocol allows a Diameter redirect agent to return to
   the message sender one or more individual hosts as 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 a mechanism by
   which this can be achieved.  New applications may incorporate this
   capability by reference to the present document.

   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/.

   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 January 29, 2014.

Tsou, et al.            Expires January 29, 2014                [Page 1]
Internet-Draft     Realm-Based Redirection In Diameter         July 2013

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 Redirecting Server . . . . . . . . .   4
     3.2.  Behaviour of Diameter Nodes . . . . . . . . . . . . . . .   5
       3.2.1.  Behaviour at the Redirect Server  . . . . . . . . . .   5
       3.2.2.  Proxy Behaviour . . . . . . . . . . . . . . . . . . .   5
       3.2.3.  Client Behaviour  . . . . . . . . . . . . . . . . . .   6
     3.3.  The Redirect-Realm AVP  . . . . . . . . . . . . . . . . .   6
     3.4.  DIAMETER_REDIRECT_INDICATION Protocol Error Code  . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The usual redirect indication, as described in Section 6.1.8 and
   Sections 6.12-6.14 of [RFC6733], returns to the message sender one or
   more individual hosts as destination of the redirected message.
   However, consider the case where an operator has offered a specific
   service but no longer wishes to do so.  The operator has arranged for
   an alternative domain to provide the service.  To aid in the
   transition to the new arrangement, the original operator maintains a
   redirect server to indicate to the message sender the alternative
   domain to which redirect the request.  However, the original operator
   should be relieved from configuring in the redirect server a list of
   hosts to contact in the alternative operator's domain, and should
Show full document text