datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Data for Reachability of Inter-/Intra-NetworK SIP (DRINKS) Use Cases and Protocol Requirements
RFC 6461

Internet Engineering Task Force (IETF)             S. Channabasappa, Ed.
Request for Comments: 6461                                     CableLabs
Category: Informational                                     January 2012
ISSN: 2070-1721

       Data for Reachability of Inter-/Intra-NetworK SIP (DRINKS)
                  Use Cases and Protocol Requirements

Abstract

   This document captures the use cases and associated requirements for
   interfaces that provision session establishment data into Session
   Initiation Protocol (SIP) Service Provider components to assist with
   session routing.  Specifically, this document focuses on the
   provisioning of one such element termed the "registry".

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6461.

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

Channabasappa                 Informational                     [Page 1]
RFC 6461            DRINKS Use Cases and Requirements       January 2012

Table of Contents

   1. Overview ........................................................2
   2. Terminology .....................................................5
   3. Registry Use Cases ..............................................6
      3.1. Category: Provisioning Mechanisms ..........................6
      3.2. Category: Interconnect Schemes .............................7
      3.3. Category: SED Exchange and Discovery Models ................8
      3.4. Category: SED Record Content ...............................9
      3.5. Category: Separation and Facilitation of Data Management ...9
      3.6. Category: Public Identifiers, TN Ranges, and RNs ..........10
      3.7. Category: Misc ............................................11
   4. Requirements ...................................................11
      4.1. Provisioning Mechanisms ...................................12
      4.2. Interconnect Schemes ......................................12
      4.3. SED Exchange and Discovery Requirements ...................12
      4.4. SED Record Content Requirements ...........................12
      4.5. Data Management Requirements ..............................13
      4.6. Public Identifier, TN Range, and RN Requirements ..........13
      4.7. Misc. Requirements ........................................13
   5. Security Considerations ........................................14
   6. Acknowledgments ................................................14
   7. References .....................................................15
      7.1. Normative References ......................................15
      7.2. Informative References ....................................15

1.  Overview

   [RFC5486] (Section 3.3) defines Session Establishment Data, or SED,
   as the data used to route a call to the next hop associated with the
   called domain's ingress point.  More specifically, the SED is the set
   of parameters that the outgoing signaling path border elements (SBEs)
   need to establish a session.  However, [RFC5486] does not specify the
   protocol(s) or format(s) to provision SED.  To pave the way to
   specify such a protocol, this document presents the use cases and
   associated requirements that have been proposed to provision SED.

   SED is typically created by the terminating or next-hop SIP service
   provider (SSP) and consumed by the originating SSP.  To avoid a
   multitude of bilateral exchanges, SED is often shared via
   intermediary systems -- termed "registries" within this document.
   Such registries receive data via provisioning transactions from SSPs,

[include full document text]