ENUM -- Telephone Number Mapping A. Mayrhofer
Working Group enum.at
Internet-Draft November 14, 2006
Expires: May 18, 2007
IANA Registration for vCard Enumservice
draft-ietf-enum-vcard-05
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 May 18, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2006).
Abstract
This memo registers the Enumservice "vCard" with three subtypes
(empty subtype, "xml", "rdf") 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,
Mayrhofer Expires May 18, 2007 [Page 1]
Internet-Draft vCard Enumservice November 2006
a callee might be presented with the name and association of the
caller before picking up the call.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. ENUM Service Registrations - vCard . . . . . . . . . . . . . . 4
4.1. Empty Subtype . . . . . . . . . . . . . . . . . . . . . . 5
4.2. "RDF" Subtype . . . . . . . . . . . . . . . . . . . . . . 5
4.3. "XML" Subtype . . . . . . . . . . . . . . . . . . . . . . 6
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security & Privacy Considerations . . . . . . . . . . . . . . 6
6.1. The ENUM Record Itself . . . . . . . . . . . . . . . . . . 6
6.2. The Resource Identified . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . . . 10
Mayrhofer Expires May 18, 2007 [Page 2]
Internet-Draft vCard Enumservice November 2006
1. Introduction
E.164 Number Mapping (ENUM) [1] uses the Domain Name System (DNS) [2]
to refer from E.164 numbers [3] to Uniform Resource Identifiers
(URIs) [7]. The registration process for Enumservices is described
in section 3 of RFC 3761.
"vCard" [5] 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.
In addition to the format specified in RFC 2426, 'Representing vCard
Objects in RDF/XML' [4] specifies two alternative formats for
representing vCard data, namely as RDF (Resource Description
Framework) or "plain" XML documents.
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. Each subtype of the
Enumservice corresponds to one of the vCard data formats mentioned
above.
Clients could use those resources to eg. 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.
2. Change Log
[Note to editors: This section is to be removed before publication -
XML source available on request]
draft-ietf-enum-vcard-05
removed reference to RFC 3761 from Abstract
moved Changelog section
moved RFC 2119 stuff to seperate section
Mayrhofer Expires May 18, 2007 [Page 3]
Internet-Draft vCard Enumservice November 2006
changed "plain" subtype to n/a
added examples to security consideration, changed text
added HTTP authentication reference
removed text about phone reverse lookups
clarified IANA registration section
draft-ietf-enum-vcard-04
added email address to IANA template (selfcontained)
changed number in example to UK drama number
added note about line break in example
draft-ietf-enum-vcard-03
Fixed typo in abstract
Added acks
Added text about PII data
draft-ietf-enum-vcard-02
added Acknowledgement section
clarified security considerations
extended introduction
sanitized references
added subtypes and URI schemes to Abstract
draft-ietf-enum-vcard-01
minor title change
removed sink type
draft-ietf-enum-vcard-00
changed name to reflect WG adoption
subtyped Enumservice
added "sink" type idea
worked on the text
draft-mayrhofer-enum-vcard-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 [6].
4. ENUM Service Registrations - vCard
Mayrhofer Expires May 18, 2007 [Page 4]
Internet-Draft vCard Enumservice November 2006
4.1. Empty Subtype
Enumservice Name: "vCard"
Enumservice Type: "vcard"
Enumservice Subtype: n/a
URI Schemes: "http", "https"
Functional Specification:
This Enumservice indicates that the resource identified is a plain
vCard according to RFC 2426 which may be accessed using HTTP/HTTPS
[8].
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 Section 6
Intended Usage: COMMON
Author: Alexander Mayrhofer <mailto:alexander.mayrhofer@enum.at>
4.2. "RDF" Subtype
Enumservice Name: "vCard"
Enumservice Type: "vcard"
Enumservice Subtype: "rdf"
URI Schemes: "http", "https"
Functional Specification:
This Enumservice indicates that the resource identified is a RDF-
formatted vCard according to section 3 - 5 of W3C vcard-rdf [4]
which may be accessed using HTTP/HTTPS.
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 Section 6
Intended Usage: COMMON
Author: Alexander Mayrhofer <mailto:alexander.mayrhofer@enum.at>
Mayrhofer Expires May 18, 2007 [Page 5]
Internet-Draft vCard Enumservice November 2006
4.3. "XML" Subtype
Enumservice Name: "vCard"
Enumservice Type: "vcard"
Enumservice Subtype: "xml"
URI Schemes: "http", "https"
Functional Specification:
This Enumservice indicates that the resource identified is a XML-
formatted vCard according to section 6 of W3C vcard-rdf [4] which
may be accessed using HTTP/HTTPS.
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 Section 6
Intended Usage: COMMON
Author: Alexander Mayrhofer <mailto:alexander.mayrhofer@enum.at>
5. Example
An example ENUM entry referencing to a plain 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!" .
(Note: Due to line length constraints, the example record above is
split in two lines)
6. Security & Privacy Considerations
As with any Enumservice, the security considerations of ENUM itself
(Section 6 of RFC 3761) apply.
6.1. The ENUM Record Itself
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.
Mayrhofer Expires May 18, 2007 [Page 6]
Internet-Draft vCard Enumservice November 2006
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:
http://sandiego.company.example.com/joe-william-user.vcf
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.
6.2. The Resource Identified
In most cases, vCards provide information about individuals. Linking
telephone numbers to such Personally Identifyable 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 builtin
authentication and authorization mechanisms to be used to maintain
access controls on vCards. Most notable, Digest Authentication [9]
could be used to challenge requestors, and even synthesize vCards
based on the client's identity (or refuse access entirely).
If access restrictions on the vCard resource are deployed, Standard
HTTP authentication and authorization mechanisms as described in
RFC2617 MUST be used to enforce those restrictions. HTTPS SHOULD be
preferred if the deployed mechanisms are prone to eavesdropping and
Mayrhofer Expires May 18, 2007 [Page 7]
Internet-Draft vCard Enumservice November 2006
replay attacks.
7. IANA Considerations
This memo requests registration of multiple "vCard" Enumservices
according to the templates in Section 4 of this document and the
definitions in RFC 3761 [1].
8. Acknowledgements
The author wishes to thank David Lindner for his contributions during
the early stages of this document. In addition, Klaus Nieminen, Jon
Peterson and Ondrej Sury provided very helpful suggestions.
9. References
9.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] Mockapetris, P., "Domain names - Implementation and
Specification", STD 13, RFC 1035, November 1987.
[3] ITU-T, "The international public telecommunication numbering
plan", Recommendation E.164 (02/05), Feb 2005.
[4] Iannella, R., "Representing vCard Objects in RDF/XML", W3C
NOTE NOTE-vcard-rdf-20010222, February 2001.
[5] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
RFC 2426, September 1998.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
9.2. Informative References
[7] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986,
January 2005.
[8] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol --
Mayrhofer Expires May 18, 2007 [Page 8]
Internet-Draft vCard Enumservice November 2006
HTTP/1.1", RFC 2616, June 1999.
[9] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication:
Basic and Digest Access Authentication", RFC 2617, June 1999.
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 May 18, 2007 [Page 9]
Internet-Draft vCard Enumservice November 2006
Full Copyright Statement
Copyright (C) The IETF Trust (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.
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Mayrhofer Expires May 18, 2007 [Page 10]
