Abstract
The problem of a single identifier for multiple communication services can be solved with different approaches. One simple approach is the ENUM system developed by the IETF (Internet Engineering Task Force), using existing E. 164 telephone numbers, protocols and infrastructure to point to different services available under this identifier. The technical aspects of the underlying protocols and the administrative aspects of the distributed database used — the domain name system — are presented. This includes the related activities in ITU and ETSI and possible national implementations.
Zusammenfassung
Das Problem der Verwendung einer einzigen Kennung für eine Vielfalt von Kommunikationsdiensten kann auf verschiedene Arten gelöst werden. Eine einfache Lösung wurde durch die IETF (Internet Engineering Task Force) entwickelt: Es wird vorgeschlagen, vorhandene E.164-Telefonnummern, Protikolle und Infrastruktureinrichtungen zu verwenden, um zu verschiedenen Diensten zu verweisen, die unter dieser Kennung erreichbar sind. Die technischen Aspekte der verwendeten Protokolle und die administrativen Aspekte der dafür verwendeten Datenbank — des Domain Name Systems — werden präsentiert. Dies inkludiert auch die damit verbundenen Aktivitäten in ITU und ETSI und mögliche nationale Implementierungen.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Berners-Lee, T. (1998): Uniform resource identifiers (URI): generic syntax. RFC2396.
Blane, P. (2001): Liaison to IETF/ISOC on ENUM. RFC 3026.
Bradner, S. (1996): The Internet standards process — revision 3. BCP, RFC2026.
Bundesgesetzblatt für die Republik Österreich, BGBI. I Nr. 100/1997, Telekommunikationsgesetz — TKG,
Bundesgesetzblatt für die Republik Österreich, BGBI. II Nr. 416/1997, Nummerierungsverordnung — NVO,
Daniel, R., Mealling, M. (1997): Resolution of uniform resource identifiers using the domain name system. RFC 2168.
ETSI EG 201 940 (04/01): Human Factors (HF); User identification solutions in converging networks.
ETSI TS 102 051 “ENUM Administration in Europe”; DTS/SPAN-110106, stable draft February 2002.
Faltstrom, P. (2000): E. 164 number and DNS. RFC 2916.
Faltstrom, P. (2002): The E. 164 to URI DDDS application. Draft-leftenum-rfc2916bis-00.txt.
Harenstien, K. (1985): NICNAME/WHOIS. RFC954.
IAB Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain (“arpa”), BCP52, RFC3172, September 2001.
IAB (09/2001): Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain (“arpa”). BCP52, RFC3172.
IEEE, The Institute of Electrical and Electronics Engineers, “IEEE Standard for Information Technology-Portable Operating System Interface (POSIX) — Part 2: Shell and Utilities (Vol. 1)”, IEEE Std 1003.2-1992, ISBN 1-55937-255-9, January 1993.
ITU-T Recommendation E. 164 (05/97): The International Public Telecommunications Numbering Plan.
ITU-T Recommendation E. 164.2: E. 164 numbering resources for trials (to be published).
ITU-T Recommendation E. 164.3: Principles, criteria and procedures for the assignment and reclamation of E.164 country codes and associated identification codes for groups of countries (determined at January 2001 meeting of Study Group 2).
ITU-T Recommendation E. 168 (05/99): Application of E.164 numbering plan for UPT.
ITU-T Recommendation E.169 (11/98): Application of Recommendation E. 164 numbering plan for universal international freephone numbers for international freephone service.
ITU-T Recommendation F.850 (03/93): Principles of Universal Personal Telecommunication (UPT).
ITU-T Recommendation F.851 (02/95): Universal Personal Telecommunication (UPT) — Service description (service set 1).
ITU-T Recommendation F.852 (03/00): Universal Personal Telecommunication (UPT) — Service description (service set 2).
ITU-T Recommendation H.323 (11/00): Packet-Based Multimedia Communications Systems.
ITU-TWTSA (2000) Resolution 20: Procedures for allocation and management of international numbering resources.
Mealling, M. (1998): The naming authority pointer (NAPTR) DNS resource record, RFC 2915.
Mealling, M. (2002a): Dynamic delegation discovery system (DDDS), part one: the comprehensive DDDS standard. Draft-ieff-urn-ddds-toc-02.txt (work in progress).
Mealling, M. (2002b): Dynamic delegation discovery system (DDDS), part two: the algorithm. Draft-ieff-urn-ddds-06.txt (work in progress).
Mealling, M. (2002c): Dynamic delegation discovery system (DDDS), part three: the DNS database”. Draft-ieft-urn-dns-ddds-database-08.txt (work in progress).
Mealling, M. (2002d): Dynamic delegation discovery system (DDDS), part four: the URI resolution application. Draft-ietf-um-uri-res-ddds-06.txt (work in progress).
Mealling, M. (2002e): Dynamic delegation discovery system (DDDS), part five: URI.ARPA assignment procedures. Draft-ietf-uri-net-procedures-10.txt (work in progress).
Moats, R. (1997): URN syntax. RFC2141.
Mockapetris, P. (1987a): Domain names — concepts and facilities. STD 13, RFC 1034.
Mockapetris, P. (1987b): Domain names — implementation and specification. STD 13, RFC 1035.
Postel, J.: Domain Name System Structure and Delegation. RFC1591, March 1994.
Rosenberg, J. (2000): SIP: Session initation protocol. Draft-ietf-sip-frc2543bis-09.txt (work in progress).
Sollins, K. (1998): Architectural principles of uniform resource name resolution. RFC 2276.
US DoC (1998): Management of Internet Names and Addresses. Docket Number: 980212036-8146-02. (http://www.ntia.doc.gov/ntiahome/domainaname/6_5_98dns.htm/.)
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Stastny, R. ENUM — Phone numbers on the Internet. Elektrotech. Inftech. 119, 126–135 (2002). https://doi.org/10.1007/BF03161620
Issue Date:
DOI: https://doi.org/10.1007/BF03161620