Changes

==History==

==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.<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 on 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 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>

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 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>  

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>

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>

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 [[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>

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>