Browse Prior Art Database

The History and Context of Telephone Number Mapping (ENUM) Operational Decisions: Informational Documents Contributed to ITU-T Study (RFC3245)

IP.com Disclosure Number: IPCOM000007533D
Original Publication Date: 2002-Mar-01
Included in the Prior Art Database: 2002-Apr-04
Document File: 11 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Ed.: AUTHOR [+2]

Abstract

RFC 2916 assigned responsibility for a number of administrative and operational details of Telephone Number Mapping (ENUM) to the IAB. It also anticipated that ITU would take responsibility for determining the legitimacy and appropriateness of applicants for delegation of "country code"-level subdomains of the top-level ENUM domain. Recently, three memos have been prepared for the ITU-T Study Group 2 (SG2) to explain the background of, and reasoning for, the relevant decisions. The IAB has also supplied a set of procedural instructions to the RIPE NCC for implementation of their part of the model. The content of the three memos is provided in this document for the information of the IETF community.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 14% of the total text.

Network Working Group                                    J. Klensin, Ed.

Request for Comments: 3245                                           IAB

Category: Informational                                       March 2002

       The History and Context of Telephone Number Mapping (ENUM)

       Operational Decisions: Informational Documents Contributed

                      to ITU-T Study Group 2 (SG2)

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   RFC 2916 assigned responsibility for a number of administrative and

   operational details of Telephone Number Mapping (ENUM) to the IAB.

   It also anticipated that ITU would take responsibility for

   determining the legitimacy and appropriateness of applicants for

   delegation of "country code"-level subdomains of the top-level ENUM

   domain.  Recently, three memos have been prepared for the ITU-T Study

   Group 2 (SG2) to explain the background of, and reasoning for, the

   relevant decisions.  The IAB has also supplied a set of procedural

   instructions to the RIPE NCC for implementation of their part of the

   model.  The content of the three memos is provided in this document

   for the information of the IETF community.

Table of Contents

   1. Introduction: ENUM Background Information .....................  2

   2. Why one and only one domain is used in ENUM ...................  2

   3. Why .ARPA was selected as the top level domain for ENUM .......  4

   4. The selection of an operator for E164.ARPA ....................  7

   5. Procedures to be followed by RIPE NCC .........................  8

   6. References ....................................................  8

   6.1. Normative references ........................................  8

   6.2. Informative and explanatory references ......................  8

   7. Security Considerations .......................................  9

   8. IANA Considerations ...........................................  9

   9. Authors' Addresses ............................................  9

   10. Full Copyright Statement ..................................... 10

Klensin                      Informational                      [Page 1]

RFC 3245   History and Context of ENUM Operational Decisions  March 2002

1. Introduction: ENUM Background Information

   In January 2002, in response to questions from the ITU-T Study Group

   2 (referred to just as "SG2", below), specifically its group working

   on "Questions 1 and 2", and members of the IETF and

   telecommunications communities, Scott Bradner, as Area Director

   responsible for the ENUM work and ISOC Vice President for Standards,

   initiated an effort to produce explanations of the decisions made by

   the IETF about ENUM administration.  The effort to produce and refine

   those documents eventually involved him, Patrik Faltstrom (author of

   RFC 2916), and several members of the IAB.

   The documents have now been contributed to ITU-T, and are being

   published as internal SG2 documents.  This document provides the IETF

   community a copy of the information provided to SG2.  Section 2 below

   contai...