Difference between revisions of "ENUM"
| Line 10: | Line 10: | ||
In 2001, different International Telecommunications Standardization Sector ([[ITU-T]]) workshops as 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, different International Telecommunications Standardization Sector ([[ITU-T]]) workshops as 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> | ||
| − | By 2002, ITU-T and the Internet Architecture Board ([[IAB]]) approved the interim procedures for ENUM subject to national authorities and end-users approval. ENUM protocol allows 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 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]</ | + | By 2002, ITU-T and the Internet Architecture Board ([[IAB]]) approved the interim procedures for ENUM subject to national authorities and end-users approval. ENUM protocol allows 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 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.164arpa 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.<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 Internet Assigned Numbers Authority [[IANA]. In 2004, IETF RFC 3761, which specifies Enumservices registration, commercial private ENUM services and public ENUM (E.164.arpa).<ref>[http://www.ietf.org/rfc/rfc3761.txt RFC 3761]</ref. 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]].<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 theAsia Pacific Regional Internet Conference on Operational Technologies ([[APRICOT]]) Conference.<ref>[http://www.apricot.net/apricot2005/about.html APRICOT 2005 Conference]</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 Internet Assigned Numbers Authority [[IANA]. In 2004, IETF RFC 3761, which specifies Enumservices registration, commercial private ENUM services and public ENUM (E.164.arpa).<ref>[http://www.ietf.org/rfc/rfc3761.txt RFC 3761]</ref>. 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]].<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 theAsia Pacific Regional Internet Conference on Operational Technologies ([[APRICOT]]) Conference.<ref>[http://www.apricot.net/apricot2005/about.html APRICOT 2005 Conference]</ref> |
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).<ref>[http://www.enumllc.com/USEUTrialRpt.pdf www.enumllc.com]</ref> | 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).<ref>[http://www.enumllc.com/USEUTrialRpt.pdf www.enumllc.com]</ref> | ||
In 2008, the ITU-T approved the ENUM interim procedures for geographic country codes for the Telecommunications Standardization Bureau ([[TSB]]).<ref>[http://www.itu.int/en/ITU-T/inr/enum/Pages/procedures.aspx ENUM administration ad interim]</ref> | In 2008, the ITU-T approved the ENUM interim procedures for geographic country codes for the Telecommunications Standardization Bureau ([[TSB]]).<ref>[http://www.itu.int/en/ITU-T/inr/enum/Pages/procedures.aspx ENUM administration ad interim]</ref> | ||
| − | |||
==References== | ==References== | ||
Revision as of 21:12, 24 June 2011
ENUM (Electronic Numbering) is a protocol developed by the Internet Engineering Task Force's (IETF's) Telephone Number Mapping Working Group<re>www.itu.int</ref> 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 the DNS technology and the hosting of ENUM domain names on the E.164 arpa domain.[1] [2] ENUM is defined in RFC 3761.
History
The International Engineering Task Force created the the Telephone Number Mapping Working Group in 1999. The working group was tasked to determine a DNS based architecture and protocols for mapping a telephone number to a set of characteristics such as URLs, which can be utilize to contact a resource to that particular number.[3] In 2000, the working group published RFC 2916, which discussed ways on using the DNS to determine available services connected to a E.164 number.[4] 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.[5]
In 2001, different International Telecommunications Standardization Sector (ITU-T) workshops as conducted in Asia, Europe and North America regarding the administrative issues in implementing the ENUM.[6]
By 2002, ITU-T and the Internet Architecture Board (IAB) approved the interim procedures for ENUM subject to national authorities and end-users approval. ENUM protocol allows 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.[7] Subsequently the European Telecommunications Standards Institute (ETSI) published its technical specifications for ENUM Administration in Europe.[8] The IAB also assigned the responsibility of delegating the E.164arpa 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.[9]
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, which specifies Enumservices registration, commercial private ENUM services and public ENUM (E.164.arpa).[10]. 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.[11] In 2005, APEET coordinated the ENUM/SIP live trial in Kyoto during theAsia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Conference.[12]
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).[13]
In 2008, the ITU-T approved the ENUM interim procedures for geographic country codes for the Telecommunications Standardization Bureau (TSB).[14]