ENUM -- Telephone Number Mapping K. Reichinger Working Group TU Wien Internet-Draft February 14, 2006 Expires: August 18, 2006 IANA Registration for Enumservice foaf draft-reichinger-enum-foaf-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 August 18, 2006. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend Reichinger Expires August 18, 2006 [Page 1] Internet-Draft Enumservice foaf February 2006 (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). Table of Contents 1. Conventions used in this document . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Enumservice Registrations - foaf . . . . . . . . . . . . . . . 3 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Security & Privacy Considerations . . . . . . . . . . . . . . . 4 5.1. ENUM Record . . . . . . . . . . . . . . . . . . . . . . . . 4 5.2. FOAF File . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Reichinger Expires August 18, 2006 [Page 2] Internet-Draft Enumservice foaf February 2006 1. Conventions used in this document 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 [5]. 2. Introduction ENUM [1] uses the Domain Name System (DNS) [3] for mapping E.164 telephone numbers [13] to Uniform Resource Identifiers (URIs) [4]. Therefore E.164 numbers are converted to ENUM domain names through means described further in RFC3761. 'Friend-Of-A-Friend' (FOAF) [2] describes a Semantic Web [15] project for machine-readable modelling of homepage-like content and social networks. The FOAF specification defines terms to be used in statements someone can make about someone else, such as name, gender and various online attributes, e.g. e-mail address, instant messaging identifier, VoIP address or web URL. FOAF is based on the Resource Description Framework (RDF) [11] defined using the Web Ontology Language (OWL) [12]. Typically, the FOAF RDF file is named foaf.rdf and made publicly available on the Web. Integrating FOAF and ENUM [14] potentially offers a variety of Semantic Web applications to be accessed by means of a telephone number. The introduction of a specific Enumservice dedicated to FOAF significantly eases that integration. This memo registers an Enumservice according to the guidelines given in RFC3761 to be used for provisioning in the services field of a NAPTR [13] resource record to indicate what class of functionality a given end point offers. The registration is defined within the Dynamic Delegation Discovery System (DDDS) [6][7][8][9][10] hierarchy, for use with the "E2U" DDDS application defined in RFC3761. This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. 3. Enumservice Registrations - foaf The Enumservice registered in this section indicates that the resource identified by the associated URI is a source of FOAF data. Reichinger Expires August 18, 2006 [Page 3] Internet-Draft Enumservice foaf February 2006 Enumservice Name: "foaf" Enumservice Type: "foaf" Enumservice Subtype: N/A URI Schemes: "http", "https" Functional Specification: This Enumservice indicates that the resource identified by the associated URI is a source of FOAF data. If the URI scheme "https" is used, the resource can be fetched by using TLS or the Secure Socket Layer protocol. Security Considerations: see Section 5 Intended Usage: COMMON Authors: Kurt Reichinger (see 'Authors' section for contact details) 4. Example An example ENUM entry referring to a FOAF RDF file could look like following: $ORIGIN 1.0.1.1.1.1.5.5.5.0.8.7.3.4.e164.arpa. @ IN NAPTR 100 10 "u" "E2U+foaf" !^.*$!http://www.dbai.tuwien.ac.at/proj/semnum/user1/foaf.rdf!" . Performing an ENUM query for the Austrian E.164 telephone number +43780555111101 will result in a referral to the web URL http://www.dbai.tuwien.ac.at/proj/semnum/user1/foaf.rdf indicating that a FOAF RDF file associated with that telephone number can be accessed there. 5. Security & Privacy Considerations 5.1. ENUM Record With ENUM utilising the DNS - a globally distributed and publicly accessible database - all information contained in DNS records must be considered publicly available. Thus, data can be harvested, stored and re-used by third parties, e.g. for generating lists of targets for sending of unrequested information. This could result in being targeted with SPAM (e-mail), SPIT (VoIP calls), junk fax, junk SMS or other unwanted information. Even after removing the DNS entry Reichinger Expires August 18, 2006 [Page 4] Internet-Draft Enumservice foaf February 2006 and the referred 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 DNS records contain personal identifiers or domain names for which ownership information can easily be obtained. 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. 5.2. FOAF File FOAF files describe persons and online communities explicitly focusing on making the content easily machine-readable. Furthermore, FOAF implicitly relies on information being publicly available on the Web. FOAF files potentially contain a rich variety of personal data making it of interest to data harvesters, e.g. for generating lists of targets for unrequested information. This could result in being targeted with SPAM (e-mail), SPIT (VoIP calls), "junk" fax, "junk" SMS or other unwanted information. Even after removing the FOAF RDF file and referred resources, copies of the information could still be available. Content, administration and publication of FOAF RDF files is under the responsibility of the individual FOAF RDF file owner. FOAF files easily can be created and published on the Web by anyone - so any assumption about data from a FOAF RDF file 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. 6. IANA Considerations This memo requests registration of the "foaf" Enumservice according to the definitions in this document and RFC3761. Reichinger Expires August 18, 2006 [Page 5] Internet-Draft Enumservice foaf February 2006 7. References 7.1. Normative References [1] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004. [2] Brickley, D. and L. Miller, "FOAF Vocabulary Specification", http://xmlns.com/foaf/0.1 , July 2005. 7.2. Informative References [3] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987. [4] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [6] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002. [7] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402, October 2002. [8] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002. [9] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404, October 2002. [10] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", BCP 65, RFC 3405, October 2002. [11] World Wide Web Consortium, "Resource Description Framework", W3C Recommendation , February 2004. [12] World Wide Web Consortium, "Web Ontology Language", W3C Recommendation , February 2004. [13] ITU Telecommunication Standardization Sector, "The Reichinger Expires August 18, 2006 [Page 6] Internet-Draft Enumservice foaf February 2006 International Public Telecommunication Numbering Plan", ITU-T Recommendation E.164, May 1997. [14] Reichinger, K. and R. Baumgartner, "Introducing ENUM to the Semantic Web", Proceedings of the IASTED International Conference on Web Technologies, Applications and Services WTAS2005, July 2005. [15] Berners-Lee, T., Hendler, J., and O. Lassila, "The Semantic Web", Scientific American , May 2001. Reichinger Expires August 18, 2006 [Page 7] Internet-Draft Enumservice foaf February 2006 Author's Address Kurt Reichinger Vienna University of Technology - DBAI Group Favoritenstrasse 9 A-1040 Vienna Austria Phone: +43 1 58058 306 Email: reiching@dbai.tuwien.ac.at URI: http://www.dbai.tuwien.ac.at/ Reichinger Expires August 18, 2006 [Page 8] Internet-Draft Enumservice foaf February 2006 Intellectual Property Statement 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. Disclaimer of Validity 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 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. Copyright Statement Copyright (C) The Internet Society (2006). 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Reichinger Expires August 18, 2006 [Page 9]