IANA Registration for vCard Enumservice

Network Working Group                                       A. Mayrhofer
Request for Comments: 4969                                       enum.at
Category: Standards Track                                    August 2007


                <span class="h1">IANA Registration for vCard Enumservice</span>

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   This memo registers the Enumservice "vCard" using the URI schemes
   "http" and "https".  This Enumservice is to be used to refer from an
   ENUM domain name to a vCard instance describing the user of the
   respective E.164 number.

   Information gathered from those vCards could be used before, during,
   or after inbound or outbound communication takes place.  For example,
   a callee might be presented with the name and association of the
   caller before picking up the call.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-3">3</a>.  Enumservice Registration - vCard  . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-4">4</a>.  Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
   <a href="#section-5">5</a>.  Security and Privacy Considerations . . . . . . . . . . . . . . <a href="#page-3">3</a>
     <a href="#section-5.1">5.1</a>.  The ENUM Record Itself  . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
     <a href="#section-5.2">5.2</a>.  The Resource Identified . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
   <a href="#section-6">6</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
   <a href="#section-7">7</a>.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
   <a href="#section-8">8</a>.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
     <a href="#section-8.1">8.1</a>.  Normative References  . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
     <a href="#section-8.2">8.2</a>.  Informative References  . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>






<span class="grey">Mayrhofer                   Standards Track                     [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   E.164 Number Mapping (ENUM) [<a href="#ref-1" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">1</a>] uses the Domain Name System (DNS) [<a href="#ref-2" title=""Domain names - implementation and specification"">2</a>]
   to refer from E.164 numbers [<a href="#ref-3" title=""The international public telecommunication numbering plan"">3</a>] to Uniform Resource Identifiers
   (URIs) [<a href="#ref-6" title=""Uniform Resource Identifier (URI): Generic Syntax"">6</a>].  The registration process for Enumservices is described
   in <a href="./rfc3761#section-3">Section 3 of RFC 3761</a>.

   "vCard" [<a href="#ref-4" title=""vCard MIME Directory Profile"">4</a>] is a transport-independent data format for the exchange
   of information about an individual.  For the purpose of this
   document, the term "vCard" refers to a specific instance of this data
   format -- an "electronic business card". vCards are exchanged via
   several protocols; most commonly, they are distributed as electronic
   mail attachments or published on web servers.  Most popular personal
   information manager applications are capable of reading and writing
   vCards.

   The Enumservice specified in this document deals with the relation
   between an E.164 number and vCards.  An ENUM record using this
   Enumservice identifies a resource from where a vCard corresponding to
   the respective E.164 number could be fetched.

   Clients could use those resources to, e.g., automatically update
   local address books (a Voice over IP phone could try to fetch vCards
   for all outbound and inbound calls taking place on that phone and
   display them together with the call journal).  In a more integrated
   scenario, information gathered from those vCards could even be
   automatically incorporated into the personal information manager
   application of the respective user.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Terminology</span>

   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 <a href="./rfc2119">RFC 2119</a> [<a href="#ref-5" title=""Key words for use in RFCs to Indicate Requirement Levels"">5</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Enumservice Registration - vCard</span>

   Enumservice Name: "vCard"

   Enumservice Type: "vcard"

   Enumservice Subtype: n/a

   URI Schemes: "http", "https"







<span class="grey">Mayrhofer                   Standards Track                     [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


   Functional Specification:

      This Enumservice indicates that the resource identified is a plain
      vCard, according to <a href="./rfc2426">RFC 2426</a>, which may be accessed using HTTP/
      HTTPS [<a href="#ref-7" title=""Hypertext Transfer Protocol -- HTTP/1.1"">7</a>].

      Clients fetching the vCard from the resource indicated should
      expect access to be restricted.  Additionally, the comprehension
      of the data provided may vary depending on the client's identity.

   Security Considerations: see <a href="#section-5">Section 5</a>

   Intended Usage: COMMON

   Author: Alexander Mayrhofer <alexander.mayrhofer@enum.at>

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Example</span>

   An example ENUM entry referencing to a vCard could look like:

      $ORIGIN 6.4.9.0.6.4.9.7.0.2.4.4.e164.arpa.
      @  IN NAPTR 100 10 "u" "E2U+vcard" \
      "!^.*$!http://example.net/vcard.vcf!" .

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security and Privacy Considerations</span>

   As with any Enumservice, the security considerations of ENUM itself
   (<a href="./rfc3761#section-6">Section 6 of RFC 3761</a>) apply.

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  The ENUM Record Itself</span>

   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 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 URIs contain
   personal identifiers or domain names for which ownership information
   can be obtained easily.  For example, the following URI makes it easy
   to guess the owner of an E.164 number, as well as his location and
   association, by just examining the result from the ENUM lookup:

      <a href="http://sandiego.company.example.com/joe-william-user.vcf">http://sandiego.company.example.com/joe-william-user.vcf</a>






<span class="grey">Mayrhofer                   Standards Track                     [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


   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.  For
   example, the following URI only reveals the service provider hosting
   the vCard (who probably even provides anonymous hosting):

      http://anonhoster.example.org/file_adfa001.vcf

   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.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  The Resource Identified</span>

   In most cases, vCards provide information about individuals.  Linking
   telephone numbers to such Personally Identifiable Information (PII)
   is a very sensitive topic, because it provides a "reverse lookup"
   from the number to its owner.  Publication of such PII is covered by
   data-protection law in many legislations.  In most cases, the
   explicit consent of the affected individual is required.

   Users MUST therefore carefully consider information they provide in
   the resource identified by the ENUM record as well as in the record
   itself.  Considerations SHOULD include serving information only to
   entities of the user's choice and/or limiting the comprehension of
   the information provided based on the identity of the requestor.

   The use of HTTP in this Enumservice allows using built-in
   authentication, authorization, and session control mechanisms to be
   used to maintain access controls on vCards.  Most notable, Digest
   Authentication [<a href="#ref-8" title=""HTTP Authentication: Basic and Digest Access Authentication"">8</a>] could be used to challenge requestors, and even
   synthesize vCards based on the client's identity (or refuse access
   entirely).  This could especially be useful in private ENUM
   deployments (like within enterprises), where clients would more
   likely have a valid credential to access the indicated resource.

   Even public deployments could synthesize vCards based on the identity
   of the client.  Social network sites, for example, could (based on
   HTTP session data like cookies [<a href="#ref-9" title=""HTTP State Management Mechanism"">9</a>]) provide more comprehensive vCards
   to their members than to anonymous clients.

   If access restrictions on the vCard resource are deployed, standard
   HTTP authentication, authorization, and state management mechanisms
   (as described in RFCs 2617 and 2695) MUST be used to enforce those
   restrictions.  HTTPS SHOULD be preferred if the deployed mechanisms
   are prone to eavesdropping and replay attacks.



<span class="grey">Mayrhofer                   Standards Track                     [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


   ENUM deployments using this Enumservice together with DNS Security
   Extensions (DNSSEC) [<a href="#ref-10" title=""DNS Security Introduction and Requirements"">10</a>] should consider using Minimally Covering
   NSEC Records [<a href="#ref-11" title=""Minimally Covering NSEC Records and DNSSEC On-line Signing"">11</a>] to prevent zone walking, as the PII data contained
   in vCards constitutes a rich target for such attempts.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  IANA Considerations</span>

   This memo requests registration of the "vCard" Enumservice according
   to the template in <a href="#section-3">Section 3</a> of this document and the definitions in
   <a href="./rfc3761">RFC 3761</a> [<a href="#ref-1" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">1</a>].

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgements</span>

   The author wishes to thank David Lindner for his contributions during
   the early stages of this document.  In addition, Klaus Nieminen, Jon
   Peterson, Ondrej Sury, and Ted Hardie provided very helpful
   suggestions.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  References</span>

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Normative References</span>

   [<a id="ref-1">1</a>]   Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
         Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
         Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.

   [<a id="ref-2">2</a>]   Mockapetris, P., "Domain names - implementation and
         specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.

   [<a id="ref-3">3</a>]   ITU-T, "The international public telecommunication numbering
         plan", Recommendation E.164 (02/05), Feb 2005.

   [<a id="ref-4">4</a>]   Dawson, F. and T. Howes, "vCard MIME Directory Profile",
         <a href="./rfc2426">RFC 2426</a>, September 1998.

   [<a id="ref-5">5</a>]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Informative References</span>

   [<a id="ref-6">6</a>]   Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
         Resource Identifier (URI): Generic Syntax", STD 66, <a href="./rfc3986">RFC 3986</a>,
         January 2005.

   [<a id="ref-7">7</a>]   Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
         Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol --
         HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.




<span class="grey">Mayrhofer                   Standards Track                     [Page 5]</span>

<span id="page-6" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


   [<a id="ref-8">8</a>]   Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
         Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication:
         Basic and Digest Access Authentication", <a href="./rfc2617">RFC 2617</a>, June 1999.

   [<a id="ref-9">9</a>]   Kristol, D. and L. Montulli, "HTTP State Management Mechanism",
         <a href="./rfc2965">RFC 2965</a>, October 2000.

   [<a id="ref-10">10</a>]  Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose,
         "DNS Security Introduction and Requirements", <a href="./rfc4033">RFC 4033</a>,
         March 2005.

   [<a id="ref-11">11</a>]  Weiler, S. and J. Ihren, "Minimally Covering NSEC Records and
         DNSSEC On-line Signing", <a href="./rfc4470">RFC 4470</a>, April 2006.

Author's Address

   Alexander Mayrhofer
   enum.at GmbH
   Karlsplatz 1/2/9
   Wien  A-1010
   Austria

   Phone: +43 1 5056416 34
   EMail: [email protected]
   URI:   <a href="http://www.enum.at/">http://www.enum.at/</a>


























<span class="grey">Mayrhofer                   Standards Track                     [Page 6]</span>

<span id="page-7" ></span>
<span class="grey"><a href="./rfc4969">RFC 4969</a>                   vCard Enumservice                 August 2007</span>


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   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
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   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
   [email protected].

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.







Mayrhofer                   Standards Track                     [Page 7]