Modern Problem Statement, Use Cases, and Framework
draft-ietf-modern-problem-framework-02

Document Type Active Internet-Draft (modern WG)
Last updated 2017-03-13
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Peterson
Internet-Draft                                                T. McGarry
Intended status: Informational                             NeuStar, Inc.
Expires: September 14, 2017                               March 13, 2017

           Modern Problem Statement, Use Cases, and Framework
               draft-ietf-modern-problem-framework-02.txt

Abstract

   The functions of the public switched telephone network (PSTN) are
   rapidly migrating to the Internet.  This is generating new
   requirements for many traditional elements of the PSTN, including
   telephone numbers (TNs).  TNs no longer serve simply as telephone
   routing addresses: they are now identifiers which may be used by
   Internet-based services for a variety of purposes including session
   establishment, identity verification, and service enablement.  This
   problem statement examines how the existing tools for allocating and
   managing telephone numbers do not align with the use cases of the
   Internet environment, and proposes a framework for Internet-based
   services relying on TNs.

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 September 14, 2017.

Copyright Notice

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

Peterson & McGarry     Expires September 14, 2017               [Page 1]
Internet-Draft               Modern Problems                  March 2017

   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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Actors  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Data Types  . . . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  Data Management Architectures . . . . . . . . . . . . . .   8
   3.  Framework . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Acquisition . . . . . . . . . . . . . . . . . . . . . . .  11
       4.1.1.  CSP Acquires TNs from Registrar . . . . . . . . . . .  12
       4.1.2.  User Acquires TNs from CSP  . . . . . . . . . . . . .  12
       4.1.3.  CSP Delegates TNs to Another CSP  . . . . . . . . . .  13
       4.1.4.  User Acquires TNs from a Delegate . . . . . . . . . .  13
       4.1.5.  User Acquires TNs from Registrar  . . . . . . . . . .  14
     4.2.  Management  . . . . . . . . . . . . . . . . . . . . . . .  14
       4.2.1.  Management of Administrative Data . . . . . . . . . .  14
         4.2.1.1.  CSP to Registrar  . . . . . . . . . . . . . . . .  15
         4.2.1.2.  User to CSP . . . . . . . . . . . . . . . . . . .  15
         4.2.1.3.  User to Registrar . . . . . . . . . . . . . . . .  15
       4.2.2.  Management of Service Data  . . . . . . . . . . . . .  16
         4.2.2.1.  CSP to other CSPs . . . . . . . . . . . . . . . .  16
         4.2.2.2.  User to CSP . . . . . . . . . . . . . . . . . . .  16
       4.2.3.  Managing Change . . . . . . . . . . . . . . . . . . .  17
         4.2.3.1.  Changing the CSP for an Existing Communications
                   Service . . . . . . . . . . . . . . . . . . . . .  17
         4.2.3.2.  Terminating a Service . . . . . . . . . . . . . .  17
     4.3.  Retrieval . . . . . . . . . . . . . . . . . . . . . . . .  18
       4.3.1.  Retrieval of Public Data  . . . . . . . . . . . . . .  18
       4.3.2.  Retrieval of Semi-restricted Administrative Data  . .  18
       4.3.3.  Retrieval of Semi-restricted Service Data . . . . . .  19
Show full document text