datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Verification Involving PSTN Reachability: Requirements and Architecture Overview
draft-jennings-vipr-overview-06

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-12-09
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

VIPR WG                                                   M. Barnes, Ed.
Internet-Draft                                                   Polycom
Intended status: Informational                               C. Jennings
Expires: June 12, 2014                                             Cisco
                                                            J. Rosenberg
                                                             jdrosen.net
                                                       M. Petit-Huguenin
                                                            Unaffiliated
                                                       December 09, 2013

Verification Involving PSTN Reachability: Requirements and Architecture
                                Overview
                    draft-jennings-vipr-overview-06

Abstract

   The Session Initiation Protocol (SIP) has seen widespread deployment
   within individual domains, typically supporting voice and video
   communications.  Though it was designed from the outset to support
   inter-domain federation over the public Internet, such federation has
   not materialized.  The primary reasons for this are the complexities
   of inter-domain phone number routing and concerns over security.
   This document reviews this problem space, outlines requirements, and
   then describes a model and technique for inter-domain federation with
   SIP involving the Public Switched Telephone Network (PSTN), called
   Verification Involving PSTN Reachability (VIPR).  VIPR addresses the
   problems that have prevented inter-domain federation over the
   Internet.  It provides fully distributed inter-domain routing for
   phone numbers, authorized mappings from phone numbers to domains, a
   new technique for automated SIP anti-spam, and privacy of number
   ownership, all while preserving the trapezoidal model of SIP.

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

Barnes, Ed., et al.       Expires June 12, 2014                 [Page 1]
Internet-Draft                VIPR Overview                December 2013

   This Internet-Draft will expire on June 12, 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  The Phone Number Routing Problem  . . . . . . . . . . . .   4
     3.2.  The Open Pinhole Problem  . . . . . . . . . . . . . . . .   6
     3.3.  Quality of Service Problem  . . . . . . . . . . . . . . .   6
     3.4.  Troubleshooting Problem . . . . . . . . . . . . . . . . .   7
   4.  Summary of Existing Solutions . . . . . . . . . . . . . . . .   7
     4.1.  Domain Routing  . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Public ENUM . . . . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Private Federations . . . . . . . . . . . . . . . . . . .   8
   5.  Key Requirements  . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Executive Overview  . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Key Properties  . . . . . . . . . . . . . . . . . . . . .  10
     6.2.  Challenging Past Assumptions  . . . . . . . . . . . . . .  12
     6.3.  Technical Overview  . . . . . . . . . . . . . . . . . . .  13
       6.3.1.  Storage of Phone Numbers  . . . . . . . . . . . . . .  14
       6.3.2.  PSTN First Call . . . . . . . . . . . . . . . . . . .  15
       6.3.3.  Validation and Caching  . . . . . . . . . . . . . . .  16

[include full document text]