Dismiss
There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

Liaison to IETF/ISOC on ENUM (RFC3026)

IP.com Disclosure Number: IPCOM000005218D
Original Publication Date: 2001-Jan-01
Included in the Prior Art Database: 2001-Aug-17
Document File: 7 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Blane: AUTHOR

Abstract

Working Party 1/2, of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) held a meeting of its collaborators in Berlin Germany 19-26 October 2000. The agenda of the meeting contained several contributions regarding RFC 2916: "E.164 Number and DNS" from the Internet Engineering Task Force's (IETF) ENUM Working Group - more specifically, the method for administering and maintaining the E.164-based resources in the Domain Name System (DNS) as related to the ENUM protocol. Consequently, in addition to the WP1/2 collaborators, there were several members of the IETF present to assist with the discussion of issues contained in the aforementioned contributions.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 30% of the total text.

Network Working Group R. Blane Request for Comments: 3026 ITU Category: Informational January 2001

Liaison to IETF/ISOC on ENUM

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 (2001). All Rights Reserved.

Abstract

Working Party 1/2, of the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) held a meeting of its collaborators in Berlin Germany 19-26 October 2000. The agenda of the meeting contained several contributions regarding RFC 2916: "E.164 Number and DNS" from the Internet Engineering Task Force's (IETF) ENUM Working Group more specifically, the method for administering and maintaining the E.164-based resources in the Domain Name System (DNS) as related to the ENUM protocol. Consequently, in addition to the WP1/2 collaborators, there were several members of the IETF present to assist with the discussion of issues contained in the aforementioned contributions.

This liaison from WP1/2 to the IETF/ISOC conveys the understandings of the WP1/2 collaborators resulting from the discussions.

1. Considerations under Question 1/2 (Numbering)

Throughout this document, the terms "administration" or "administrative functions" refer to the provision and update of the E.164 numerical values, to be contained in the zones of a domain name in the "e164.arpa" domain, in the DNS.

It is noted that most ENUM service and administrative decisions are national issues under the purview of ITU Member States, since most of the E.164 resources are utilized nationally.

These understandings are relative only to the provision of E.164 information for DNS administrative functions, not policy or operational functions.

Blane Informational [Page 1]

RFC 3026 Liaison to IETF/ISOC on ENUM January 2001

In order to advance a common terminology for the purpose of this liaison, we have defined the zones of a domain name as follows.

Using an example, domain name "1.5.1.5.0.2.0.4.1.3.3.e164.arpa" (as in RFC 2916) is segmented into zones as follow:

E164.arpa domain zone

3.3. country code zone (1, 2, or 3 digits dependent on CC)

1.5.1.5.0.2.0.4.1. national zone

The first understandings to be conveyed are those regarding the responsibilities for administration of the various zones within the "e164.arpa" domain:

o The domain zone administration was agreed to be outside the scope

of this meeting and WP1/2.

o For all E.164 Country Code Zone resources (Country Codes and Identification Codes), the ITU has the responsibility to provide assignment information to DNS administrators, for performing the administrative function. The ITU will ensure that each Member State has authorized the inclusion of their Country Code information for input to the DNS. For resources that are spare or designated as test codes there will normally be no entry in the DNS. However, the ITU will provide spare code lists to DNS admin...