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

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Last updated 2012-07-15
Replaces draft-tsou-dime-realm-based-redirect
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                  T. Tsou
Internet-Draft                                 Huawei Technologies (USA)
Intended status: Standards Track                                  R. Hao
Expires: January 17, 2013                                  Comcast Cable
                                                          T. Taylor, Ed.
                                                     Huawei Technologies
                                                           July 16, 2012

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

Abstract

   The Diameter protocol 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 a mechanism by which this can be achieved.  New
   applications may incorporate this capability by reference to the
   present document.

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 17, 2013.

Copyright Notice

   Copyright (c) 2012 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

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

   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  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . 4
       3.2.1.  Behaviour at the Redirecting Server . . . . . . . . . . 4
       3.2.2.  Proxy Behaviour . . . . . . . . . . . . . . . . . . . . 5
       3.2.3.  Client Behaviour  . . . . . . . . . . . . . . . . . . . 6
     3.3.  The Redirect-Realm AVP  . . . . . . . . . . . . . . . . . . 6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   7.  Normative References  . . . . . . . . . . . . . . . . . . . . . 7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7

Tsou, et al.            Expires January 17, 2013                [Page 2]
Internet-Draft     Realm-Based Redirection In Diameter         July 2012

1.  Introduction

   The usual redirect indication, as described in Section 6.1.8 and
   Sections 6.12-6.14 of [RFC3588bis], returns one or more individual
   host names to the upstream Diameter node.  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 the alternative destination to upstream nodes.  However, the
   original operator has no interest in configuring a list of hosts in
   the alternative operator's domain, and would prefer simply to provide
   redirect indications to the domain as a whole.

   As an example of another use case, consider a 3GPP IMS deployment
Show full document text