IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information
RFC 4769

 
Document Type RFC - Proposed Standard (November 2006; No errata)
Updated by RFC 6118
Last updated 2013-03-02
Replaces draft-livingood-shockey-enum-npd
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4769 (Proposed Standard)
Telechat date
Responsible AD Jon Peterson
Send notices to paf@cisco.com, panic@paf.se, rich.shockey@neustar.biz
Network Working Group                                       J. Livingood
Request for Comments: 4769                  Comcast Cable Communications
Category: Standards Track                                     R. Shockey
                                                                 NeuStar
                                                           November 2006

            IANA Registration for an Enumservice Containing
    Public Switched Telephone Network (PSTN) Signaling Information

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2006).

Abstract

   This document registers the Enumservice type "pstn" and subtype "tel"
   using the URI scheme 'tel', as well as the subtype "sip" using the
   URI scheme 'sip' as per the IANA registration process defined in the
   ENUM specification, RFC 3761.  This Enumservice is used to facilitate
   the routing of telephone calls in those countries where number
   portability exists.

Livingood & Shockey        Standards Track                      [Page 1]
RFC 4769                    PSTN Enumservice               November 2006

Table of Contents

   1. Introduction ....................................................3
   2. Distribution of Data ............................................4
   3. ENUM Service Registration for PSTN ..............................5
      3.1. ENUM Service Registration for PSTN with Subtype "tel" ......5
      3.2. ENUM Service Registration for PSTN with Subtype "sip" ......5
   4. Examples ........................................................6
      4.1. Example of a Ported Number, Using a 'tel' URI Scheme .......6
      4.2. Example of a Ported Number, Using a 'sip' URI Scheme .......6
      4.3. Example of a Non-Ported Number, Using a 'tel' URI Scheme ...7
      4.4. Example of a Non-Ported Number, Using a 'sip' URI Scheme ...7
      4.5. Example Using a Regular Expression .........................7
   5. Implementation Recommendations ..................................7
      5.1. Call Processing When Multiple Records Are Returned .........7
      5.2. NAPTR Configuration issues .................................8
   6. Examples of E2U+pstn in Call Processing .........................8
      6.1. Dialed Number Not Available On-Net .........................8
      6.2. Dialed Number Available On-Net and on the PSTN .............9
   7. Security Considerations .........................................9
   8. IANA Considerations ............................................10
   9. Acknowledgements ...............................................10
   10. References ....................................................10
      10.1. Normative References .....................................10
      10.2. Informative References ...................................11

Livingood & Shockey        Standards Track                      [Page 2]
RFC 4769                    PSTN Enumservice               November 2006

1.  Introduction

   ENUM (E.164 Number Mapping, RFC 3761 [1]) is a technology that
   transforms E.164 numbers (The International Public Telecommunication
   Numbering Plan, ITU-T Recommendation E.164 [2]) into domain names and
   then uses DNS (Domain Name System, RFC 1034 [3]) delegation through
   NS records and NAPTR records (Dynamic Delegation Discovery System
   (DDDS) Part Three: The Domain Name System (DNS) Database, RFC 3403
   [4]) to look up what services are available for a specific domain
   name.

   This document registers Enumservices according to the guidelines
   given in RFC 3761 [1] to be used for provisioning in the services
   field of a NAPTR [4] resource record to indicate the types of
   functionality associated with an end point and/or telephone number.
   The registration is defined within the DDDS (Dynamic Delegation
   Discovery System [4][5][6][7][8]) hierarchy, for use with the "E2U"
   DDDS Application defined in RFC 3761.

   Number Portability allows telephone subscribers to keep their
   telephone numbers when they change service providers, move to a new
   location, or change the subscribed services [14].  In many countries,
   such as the United States and Canada, the functions of naming and
   addressing on the Public Switched Telephone Network (PSTN) have been
   abstracted.  In the case of a ported number, the dialed number is not
Show full document text