ENUM: Difference between revisions

Latest revision as of 22:12, 22 January 2014

ENUM (Electronic Numbering) is a protocol developed by the Internet Engineering Task Force's (IETF) Telephone Number Mapping Working Group,^[1] which used the Domain Name System (DNS) architecture and protocol to identify available services associated with E.164. ENUM involves the process of creating a domain name from a telephone number and resolving it to an Internet address or Uniform Resource Identifier (URI) using DNS technology and the hosting of ENUM domain names on the E.164 ARPA domain.^[2] ^[3] ENUM is defined in RFC 3761.

History[edit | edit source]

The International Engineering Task Force created the the Telephone Number Mapping Working Group in 1999. The working group was tasked with determining a DNS-based architecture and protocol for mapping a telephone number to a set of characteristics, such as a URL, that could be utilized to associate a resource to that particular number.^[4] In 2000, the working group published RFC 2916, which discussed ways of using the DNS to determine available services connected to a E.164 number.^[5] E.164 is an international telecommunications numbering plan. E.164 numbers are globally unique, language independent identifiers for resources on Public Telecommunication Networks capable of supporting numerous services and protocols.^[6]

In 2001, several International Telecommunications Standardization Sector (ITU-T) workshops were conducted in Asia, Europe and North America regarding the administrative issues in implementing ENUM.^[7]

By 2002, ITU-T and the Internet Architecture Board approved interim procedures for ENUM, subject to national authorities and end-users approval. ENUM protocols allowed consumers to use one number to access numerous terminals and services, which included phone, fax, e-mail, pager, mobile telephones, websites or any other services available through an Internet addressing scheme.^[8] Subsequently, the European Telecommunications Standards Institute (ETSI) published its technical specifications for ENUM Administration in Europe.^[9] The IAB also assigned the responsibility of delegating the E.164 ARPA domains to Reseaux IP Européens Network Coordination Centre (RIPE NCC). RIPE NCC assigned the ENUM TLD, 9.4.e164.arpa to the German Interne Community DENIC, which started the ENUM trial on May 21, 2002.^[10]

In 2003, ETSI published its technical specifications for Minimum Requirements for Interoperability of European ENUM Trials while the IETF issued final procedures for the ENUM domain and opened the registration of ENUM services through the Internet Assigned Numbers Authority (IANA). In 2004, IETF RFC 3761 was released, which specifies ENUM services registration, commercial private ENUM services and public ENUM (E.164.arpa).^[11]. The Asia Pacific ENUM Engineering Team (APEET) was established due to the growing interest of the use of ENUM in the region. Its members include JPRS, CNNIC, KRNIC, SGNIC and TWNIC.^[12] In 2005, APEET coordinated the ENUM/SIP live trial in Kyoto during the APRICOT Conference.^[13]

In 2006, the Public User ENUM trial was conducted in the United States for six months between n March 2006 and June 2007. It was sponsored by the Country Code 1 ENUM Limited Liability Company (LLC).^[14]

In 2008, the ITU-T approved the ENUM interim procedures for geographic country codes for the Telecommunications Standardization Bureau (TSB).^[15]

ENUM Working Group[edit | edit source]

The ENUM Working Group is responsible in monitoring and promoting discussions and initiatives to develop the advancement of ENUM, the internet resource mapping technology using the E.164 telephone numbers identifiers.

Types of ENUM[edit | edit source]

There are three types of ENUM:

Public User ENUM, which allows an end user to enter his or her own records in the ENUM registry under the public dumaine164.arpa;
Private Infrastructure ENUM, which is used by a closed group without using the e164.arpa public domain; instead they opt to use the process of creating a domain name from a telephone number and resolving it to a URI to exchange IP traffic;
Public Infrastructure ENUM is assigned by a National Number Administrator, which normally delegates a telephone number to a carrier, which in turn assigns the telephone number to an end-user. The carrier maps telephone numbers to internal network addresses to enable call routing features that are not publicly available, it is highly secure and access is restricted to other service providers.^[16]

Uses of ENUM[edit | edit source]

Based on a report prepared by the Center for Democracy and Technology, ENUM has several benefits and uses, such as:^[17]

It serves as single number point of contact wherein a single ENUM number facilitates the routing of telephone calls to the internet instead of the regular telephone sytem, meaning it allows numerous access points to different types of communication such as fax, cellular phones, and many others.
It facilitates the transition away from the Public Switch Telephone Network (PSTN) to the Internet as the main carrier of voice communication.
It can be used as an internal routing within a telephone company's network, for example major telecommunication companies in the United States convert voice calls using VoIP.
It serves as a dial access to new internet service providers that allows users to simply dial a telephone number which can be translated using ENUM to a desired internet address for them to be able to access Internet services via cellphone.

ENUM Administration[edit | edit source]

The International Telecommunication Union (ITU) is responsible for designating which organization will administer or control the implementation of ENUM based on the regulations of a certain country. Every country sets their own rules that govern the establishment and control of ENUM records, this means that "called party control" of ENUM is administered by each country.^[18]

ENUM Deployment Status[edit | edit source]

Since its establishment, ENUM has become commercially available worldwide. ENUM trials began in 2003 in different countries such as Australia, Austria, China, France, Germany, Korea, Netherlands, Sweden, Switzerland, and the United States. Prior to the implementation of ENUM in the United States, the Department of Commerce (DoC) issued an endorsement regarding the participation of the U.S. in the official ENUM trial and sought to create guidelines to protect users' privacy and security.^[19]

References[edit | edit source]

[1] www.itu.int

[2] RFC 3761

[3] www.enum.org

[4] ENUM Working Group

[5] RFC 2916

[6] E.164 Definition

[7] ITU-T Workshops

[8] ITU Press Release

[9] www.etsi.org

[10] www.denic.de

[11] RFC 3761

[12] rs.co.jp

[13] APRICOT 2005 Conference

[14] www.enumllc.com

[15] ENUM administration ad interim

[16] Types of ENUM

[17] ENUM:Mapping Telephone Numbers Onto The Internet

[18] ENUM Admiistration

[19] Deployment Status

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

@@ Line 3: / Line 3: @@
 ==History==
-The International Engineering Task Force created the the Telephone Number Mapping Working Group in 1999. The working group was tasked with determining a DNS based architecture and protocols for mapping a telephone number to a set of characteristics, such as [[URL]]s, that can be utilized to associate a resource to that particular number.<ref>[http://www.ietf.org/proceedings/46/46th-99nov-ietf-156.html#P24048_1450454 ENUM Working Group]</ref> In 2000, the working group published RFC 2916, which discussed ways of using the DNS to determine available services connected to a E.164 number.<ref>[http://www.ietf.org/rfc/rfc2916.txt RFC 2916]</ref> E.164  is an international telecommunications numbering plan. E.164 numbers are globally unique, language independent identifiers for resources on Public Telecommunication Networks capable of supporting numerous services and protocols.<ref>[http://www.itu.int/rec/T-REC-e E.164 Definition]</ref>
+The International Engineering Task Force created the the Telephone Number Mapping Working Group in 1999. The working group was tasked with determining a DNS-based architecture and protocol for mapping a telephone number to a set of characteristics, such as a [[URL]], that could be utilized to associate a resource to that particular number.<ref>[http://www.ietf.org/proceedings/46/46th-99nov-ietf-156.html#P24048_1450454 ENUM Working Group]</ref> In 2000, the working group published RFC 2916, which discussed ways of using the DNS to determine available services connected to a E.164 number.<ref>[http://www.ietf.org/rfc/rfc2916.txt RFC 2916]</ref> E.164  is an international telecommunications numbering plan. E.164 numbers are globally unique, language independent identifiers for resources on Public Telecommunication Networks capable of supporting numerous services and protocols.<ref>[http://www.itu.int/rec/T-REC-e E.164 Definition]</ref>
-In 2001, different International Telecommunications Standardization Sector ([[ITU-T]]) workshops were conducted in Asia, Europe and North America regarding the administrative issues in implementing the ENUM.<ref>[http://www.itu.int/osg/spu/enum/ ITU-T Workshops]</ref>
+In 2001, several International Telecommunications Standardization Sector ([[ITU-T]]) workshops were conducted in Asia, Europe and North America regarding the administrative issues in implementing ENUM.<ref>[http://www.itu.int/osg/spu/enum/ ITU-T Workshops]</ref>
-By 2002, ITU-T and the [[IAB|Internet Architecture Board]] approved interim procedures for ENUM subject to national authorities and end-users approval. ENUM protocols allow consumers to use one number to access numerous terminals and services, which include  phone, fax, e-mail, pager, mobile telephones, websites or any other services available through an Internet addressing scheme.<ref>[http://www.itu.int/newsroom/press_releases/2002/NP05.html ITU Press Release]</ref> Subsequently, the [[ETSI|European Telecommunications Standards Institute]] (ETSI) published its technical specifications for ENUM Administration in Europe.<ref>[http://www.etsi.org/deliver/etsi_ts/102000_102099/102051/01.01.01_60/ts_102051v010101p.pdf www.etsi.org]</ref>  The IAB also assigned the responsibility of delegating the E.164 arpa domains to [[RIPE NCC|Reseaux IP Européens Network Coordination Centre]] (RIPE NCC).  RIPE NCC assigned the ENUM TLD, 9.4.e164.arpa to the German Interne Community [[DENIC]], which started the ENUM trial on May 21, 2002.<ref>[http://www.denic.de/fileadmin/public/services/ENUM/ENUM_Abschlussbericht_EN.pdf www.denic.de]</ref>
+By 2002, ITU-T and the [[IAB|Internet Architecture Board]] approved interim procedures for ENUM, subject to national authorities and end-users approval. ENUM protocols allowed consumers to use one number to access numerous terminals and services, which included phone, fax, e-mail, pager, mobile telephones, websites or any other services available through an Internet addressing scheme.<ref>[http://www.itu.int/newsroom/press_releases/2002/NP05.html ITU Press Release]</ref> Subsequently, the [[ETSI|European Telecommunications Standards Institute]] (ETSI) published its technical specifications for ENUM Administration in Europe.<ref>[http://www.etsi.org/deliver/etsi_ts/102000_102099/102051/01.01.01_60/ts_102051v010101p.pdf www.etsi.org]</ref> The IAB also assigned the responsibility of delegating the E.164 ARPA domains to [[RIPE NCC|Reseaux IP Européens Network Coordination Centre]] (RIPE NCC). RIPE NCC assigned the ENUM TLD, 9.4.e164.arpa to the German Interne Community [[DENIC]], which started the ENUM trial on May 21, 2002.<ref>[http://www.denic.de/fileadmin/public/services/ENUM/ENUM_Abschlussbericht_EN.pdf www.denic.de]</ref>
 In 2003, ETSI published its technical specifications for Minimum Requirements for Interoperability of European ENUM Trials while the IETF issued final procedures for the ENUM domain and opened the registration of ENUM services through the [[IANA|Internet Assigned Numbers Authority]] (IANA). In 2004, IETF RFC 3761 was released, which specifies  ENUM services registration, commercial private ENUM services and public ENUM (E.164.arpa).<ref>[http://www.ietf.org/rfc/rfc3761.txt RFC 3761]</ref>. The [[APEET|Asia Pacific ENUM Engineering Team]] (APEET) was established due to the growing interest of the use of ENUM in the region. Its members include [[JPRS]], [[CNNIC]], [[KRNIC]], [[SGNIC]] and [[TWNIC]].<ref>[http://jprs.co.jp/en/topics/2004/040720.html jprs.co.jp]</ref> In 2005, APEET coordinated the ENUM/SIP live trial in Kyoto during the [[APRICOT]] Conference.<ref>[http://www.apricot.net/apricot2005/about.html APRICOT 2005 Conference]</ref>
@@ Line 20: / Line 20: @@
 ==Types of ENUM==
 There are three types of ENUM:
-* '''Public User ENUM'''- Allows an end user to enter his or her own records in the ENUM registry under the public dumaine164.arpa;
+* '''Public User ENUM''', which allows an end user to enter his or her own records in the ENUM registry under the public dumaine164.arpa;
-* '''Private Infrastructure ENUM'''- Is used  by a closed group without using the e164.arpa public domain, instead they opt to use the process of creating a domain name from a telephone number and resolving it to a URI to exchange IP traffic;
+* '''Private Infrastructure ENUM''', which is used by a closed group without using the e164.arpa public domain; instead they opt to use the process of creating a domain name from a telephone number and resolving it to a URI to exchange IP traffic;
-* '''Public Infrastructure ENUM'''- Is assigned by a National Number Administrator, which normally delegates a telephone number to a carrier, which in turn assigns the telephone number to an end-user. The Carrier maps telephone numbers to internal network addresses to enable call routing features that are not publicly available, it is highly secure and access is restricted to other service providers.<ref>[http://www.enum.org/what/types Types of ENUM]</ref>
+* '''Public Infrastructure ENUM''' is assigned by a National Number Administrator, which normally delegates a telephone number to a carrier, which in turn assigns the telephone number to an end-user. The carrier maps telephone numbers to internal network addresses to enable call routing features that are not publicly available, it is highly secure and access is restricted to other service providers.<ref>[http://www.enum.org/what/types Types of ENUM]</ref>
 ==Uses of ENUM==
-Based on a report prepared by the [[CDT|Center for Democracy and Technology]], ENUM has several benefits and uses, which include:<ref>[http://old.cdt.org/standards/enum/030428analysis.pdf ENUM:Mapping Telephone Numbers Onto The Internet]</ref>
+Based on a report prepared by the [[CDT|Center for Democracy and Technology]], ENUM has several benefits and uses, such as:<ref>[http://old.cdt.org/standards/enum/030428analysis.pdf ENUM:Mapping Telephone Numbers Onto The Internet]</ref>
-# It serves as single number point of contact wherein  a single ENUM number facilitates the routing of telephone calls to the internet instead of the regular telephone sytem, meaning it allows numerous access points to different types of communication such as fax, cellular phones and many others.
+# It serves as single number point of contact wherein a single ENUM number facilitates the routing of telephone calls to the internet instead of the regular telephone sytem, meaning it allows numerous access points to different types of communication such as fax, cellular phones, and many others.
-# It facilitates the transition away from the Public Switch Telephone Network (PSTN) to the internet as the main carrier of voice communication.
+# It facilitates the transition away from the Public Switch Telephone Network (PSTN) to the Internet as the main carrier of voice communication.
 # It can be used as an internal routing within a telephone company's network, for example major telecommunication companies in the United States convert voice calls using [[VoIP]].
 # It serves as a dial access to new internet service providers that allows users to simply dial a telephone number which can be translated using ENUM to a desired internet address for them to be able to access Internet services via cellphone.
@@ Line 35: / Line 35: @@
 ==ENUM Deployment Status==
-Since its establishment, ENUM has become commercially available worldwide. ENUM trials began in 2003 in different countries such as Australia, Austria, China, France, Germany, Korea, Netherlands, Sweden, Switzerland and the United States. Prior to the implementation of ENUM in the United States, the  [[DoC|Department of Commerce]] (DoC) issued an endorsement regarding the participation of the U.S. in the official ENUM trial and sought to create guidelines to protect users' privacy and security.<ref>[http://old.cdt.org/standards/enum/030428analysis.pdf Deployment Status]</ref>
+Since its establishment, ENUM has become commercially available worldwide. ENUM trials began in 2003 in different countries such as Australia, Austria, China, France, Germany, Korea, Netherlands, Sweden, Switzerland, and the United States. Prior to the implementation of ENUM in the United States, the [[DoC|Department of Commerce]] (DoC) issued an endorsement regarding the participation of the U.S. in the official ENUM trial and sought to create guidelines to protect users' privacy and security.<ref>[http://old.cdt.org/standards/enum/030428analysis.pdf Deployment Status]</ref>
 ==References==