ENUM -- Telephone Number Mapping A. Mayrhofer Working Group enum.at Internet-Draft Jun 19, 2008 Expires: December 21, 2008 IANA Registration for Location ('loc') Enumservice draft-mayrhofer-enum-loc-enumservice-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on December 21, 2008. Abstract This document requests IANA registration of an Enumservice for reflecting location information. The Enumservice uses the 'loc' Type name, and makes use of the proposed 'held' and 'geo' URI schemes. Mayrhofer Expires December 21, 2008 [Page 1] Internet-Draft Location Enumservice Jun 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Enumservice Registration - 'loc' . . . . . . . . . . . . . . . 3 4.1. Registration for 'loc:helds' . . . . . . . . . . . . . . . 4 4.2. Registration for 'loc:geo' . . . . . . . . . . . . . . . . 4 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Security & Privacy Considerations . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 8. DNS Considerations . . . . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . . 7 10.2. Informative References . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Mayrhofer Expires December 21, 2008 [Page 2] Internet-Draft Location Enumservice Jun 2008 1. Introduction E.164 Number Mapping (ENUM) [RFC3761] uses the Domain Name System (DNS) [RFC1035] to refer from E.164 numbers [refs.E164] to Uniform Resource Identifiers (URIs) [RFC3986]. Specific services to be used with ENUM must be registered with IANA. HTTP Enabled Location Delivery (HELD) [I-D.ietf-geopriv-http-location-delivery] specifies a Layer 7 location configuration protocol for retrieving location information from a server. The URI scheme 'helds' is specified to identify resources on such a location server. [I-D.mayrhofer-geopriv-geo-uri] specifies the 'geo' URI scheme to identify a physical location by its latitude, longitude and optionally altitude in a compact, simple, human-readable, and protocol independent way. The 'loc' Enumservice proposed in this document refers from a E.164 number to an URI identifying the physical location of the respective number, identified by 'helds' or 'geo' URIs resulting from the processing of the respective ENUM record. 2. Change Log [Note to editors: This section is to be removed before publication - XML source available on request] draft-mayrhofer-enum-loc-enumservice-00 initial draft 3. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 4. Enumservice Registration - 'loc' The following template contains information required for the IANA registrations of the 'loc' Enumservice, according to [I-D.ietf-enum-enumservices-guide]. Mayrhofer Expires December 21, 2008 [Page 3] Internet-Draft Location Enumservice Jun 2008 4.1. Registration for 'loc:helds' Enumservice Class: Application-type, Common Enumservice Type: "loc" Enumservice Subtype: "helds" URI Scheme(s): "helds" Functional Specification: This Enumservice indicates that the resource identified is a HELD resource, which can be dereferenced to retrieve the location of the respective E.164 number. Clients should expect access to the HELD resource to be restricted, and should also be prepared for the server to return different granularity of information, based on for example the identity of the client. Security Considerations: see Section 6 Intended Usage: COMMON Registration Document(s): [RFC XXXX] (replace with RFC number of this document once assigned) Author(s): Alexander Mayrhofer Further Information: N/A 4.2. Registration for 'loc:geo' Enumservice Class: Application-type, Common Enumservice Type: "loc" Enumservice Subtype: "geo" URI Scheme(s): "geo" Functional Specification: This Enumservice indicates that the resource identified is an 'geo' URI, which in turn identifies the physical location of the respective E.164 number. Security Considerations: see Section 6 Intended Usage: COMMON Mayrhofer Expires December 21, 2008 [Page 4] Internet-Draft Location Enumservice Jun 2008 Registration Document(s): [RFC XXXX] (replace with RFC number of this document once assigned) Author(s): Alexander Mayrhofer Further Information: N/A 5. Examples An example ENUM entry identifying the location of a number using a HELD resource could look like this: $ORIGIN 6.9.4.0.6.9.4.5.1.1.4.4.e164.arpa. @ IN NAPTR ( 100 10 "u" "E2U+loc:helds" "!^.*$!helds://nottinghamshire.example.com/sherwood/robin72!" . ) A client who retrieves that ENUM record would then try to dereference the resulting HELD resource, with the location server returning the desired location information if the client is authorized to do so. The location server could, for example, return only rough location for anonymous clients, while trusted clients receive full location data. An example ENUM entry referring to a location of a number using a 'geo' URI could look like this: $ORIGIN 6.9.4.0.6.9.4.5.1.1.4.4.e164.arpa. @ IN NAPTR ( 100 10 "u" "E2U+loc:geo" "!^.*$!geo:53.204628,-1.072359!" . ) The client could use the geographical coordinates contained in the URI to display a map of the current user's location. Note that the location information is contained in the URI (and therefore in the ENUM record) itself, which makes it unnecessary to contact a location server. However, it is therefore not be possible to return different location information to different clients. 6. Security & Privacy Considerations General security considerations of the protocols on which this Mayrhofer Expires December 21, 2008 [Page 5] Internet-Draft Location Enumservice Jun 2008 Enumservice registration is based are addressed in Sections 3.1.3 and 6 of RFC 3761 (ENUM). Since ENUM uses DNS - a publicly available database - any information contained in records provisioned in ENUM domains must be considered public as well. Even after revoking the DNS entry and removing the refered resource, copies of the information could still be available. Information published in ENUM records could reveal associations between E.164 numbers and their owners - especially if IRIs/URIs contain personal identifiers or domain names for which ownership information can be obtained easily. However, it is important to note that the ENUM record itself does not need to contain any personal information. It just points to a location where access to personal information could be granted. ENUM records pointing to third party resources can easily be provisioned on purpose by the ENUM domain owner - so any assumption about the association between a number and an entity could therefore be completely bogus unless some kind of identity verification is in place. This verification is out of scope for this memo. 7. IANA Considerations This memo requests IANA to add a new "loc" Enumservice to the 'Enumservice Registrations' registry, according to the definitions in this document and RFC 3761 [RFC3761]. The required templates are contained in Section 4. 8. DNS Considerations The proposed Enumservice does not require any special DNS considerations. While 'geo' URIs can be dereferenced even without subsequent DNS lookups, a 'helds' URI may require additional DNS queries to resolve the server location. However, such queries can never end up in another ENUM query, hence the probability of endless loops is zero. 9. Acknowledgements Some text from HELD was used in the introduction Mayrhofer Expires December 21, 2008 [Page 6] Internet-Draft Location Enumservice Jun 2008 10. References 10.1. Normative References [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [I-D.ietf-geopriv-http-location-delivery] Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, "HTTP Enabled Location Delivery (HELD)", draft-ietf-geopriv-http-location-delivery-07 (work in progress), April 2008. [I-D.mayrhofer-geopriv-geo-uri] Mayrhofer, A. and C. Spanring, "A Uniform Resource Identifier for Geographic Locations ('geo' URI)", draft-mayrhofer-geopriv-geo-uri-00 (work in progress), May 2008. [I-D.ietf-enum-enumservices-guide] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA Registration of Enumservices: Guide, Template and IANA Considerations", draft-ietf-enum-enumservices-guide-10 (work in progress), May 2008. 10.2. Informative References [RFC1035] Mockapetris, P., "Domain names - Implementation and Specification", STD 13, RFC 1035, November 1987. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [refs.E164] ITU-T, "The international public telecommunication numbering plan", Recommendation E.164 (02/05), Feb 2005. [W3C.REC-xml-20040204] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)", W3C REC REC-xml-20040204, February 2004. Mayrhofer Expires December 21, 2008 [Page 7] Internet-Draft Location Enumservice Jun 2008 Author's Address Alexander Mayrhofer enum.at GmbH Karlsplatz 1/9 Wien A-1010 Austria Phone: +43 1 5056416 34 Email: alexander.mayrhofer@enum.at URI: http://www.enum.at/ Mayrhofer Expires December 21, 2008 [Page 8] Internet-Draft Location Enumservice Jun 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Mayrhofer Expires December 21, 2008 [Page 9]