ENUM -- Telephone Number Mapping A. Mayrhofer
Working Group enum.at
Internet-Draft D. Lindner
Expires: November 27, 2006 SIL
May 26, 2006
IANA Registration for vCard Enumservice
draft-ietf-enum-vcard-01
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 November 27, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This memo registers the Enumservice "vCard" with several subtypes
according to the IANA Enumservice registration process described in
RFC3671. 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
Mayrhofer & Lindner Expires November 27, 2006 [Page 1]
Internet-Draft vCard Enumservice May 2006
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
1. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. ENUM Service Registrations - vCard . . . . . . . . . . . . . . 4
3.1. "Plain" Subtype . . . . . . . . . . . . . . . . . . . . . . 4
3.2. "RDF" Subtype . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. "XML" Subtype . . . . . . . . . . . . . . . . . . . . . . . 5
4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security & Privacy Considerations . . . . . . . . . . . . . . . 5
5.1. The Record Itself . . . . . . . . . . . . . . . . . . . . . 5
5.2. The Resource Identified . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
Intellectual Property and Copyright Statements . . . . . . . . . . 9
Mayrhofer & Lindner Expires November 27, 2006 [Page 2]
Internet-Draft vCard Enumservice May 2006
1. Change Log
[This section is to be removed before publication]
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
2. Introduction
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].
E.164 number mapping (ENUM) [1] uses the Domain Name System (DNS) [3]
for mapping E.164 numbers [7] to Uniform Resource Identifiers (URIs)
[4]. The registration process for Enumservices is also described in
RFC 3761.
"vCard" [2] 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 entry using this Enumservice
identifies a resource from where a vCard corresponding to the E.164
number could be fetched.
Clients could use such resources to automatically update local
address books, eg. a Voice over IP phone could try to fetch vCards
for all outbound and inbound calls taking place on that phone and
display that information together with the call journal. In a more
integrated scenario, Information gathered from those vCards could
Mayrhofer & Lindner Expires November 27, 2006 [Page 3]
Internet-Draft vCard Enumservice May 2006
even be automatically incorporated into the personal information
manager application of the respective user.
3. ENUM Service Registrations - vCard
3.1. "Plain" Subtype
Enumservice Name: "vCard"
Enumservice Type: "vcard"
Enumservice Subtype: "plain"
URI Schemes: "http", "https"
Functional Specification:
This Enumservice indicates that the resource identified is a plain
vCard according to RFC 2426. Clients may attempt to fetch the
vCard from the resource indicated, but should expect access to be
restricted.
Security Considerations: see Section 5
Intended Usage: COMMON
Authors: David Lindner, Alexander Mayrhofer (see 'Authors' section
for contact details)
3.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 [6].
Clients may attempt to fetch the vCard from the resource
indicated, but should expect access to be restricted.
Security Considerations: see Section 5
Intended Usage: COMMON
Mayrhofer & Lindner Expires November 27, 2006 [Page 4]
Internet-Draft vCard Enumservice May 2006
Authors: David Lindner, Alexander Mayrhofer (see 'Authors' section
for contact details)
3.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 [6].
Clients may attempt to fetch the vCard from the resource
indicated, but should expect access to be restricted.
Security Considerations: see Section 5
Intended Usage: COMMON
Authors: David Lindner, Alexander Mayrhofer (see 'Authors' section
for contact details)
4. Example
An example ENUM entry referencing to a plain vCard could look like:
$ORIGIN 4.3.6.1.4.6.5.0.5.1.3.4.e164.arpa.
@ IN NAPTR 100 10 "u" "E2U+vcard:plain"
"!^.*$!http://www.enum.at/vcard-axelm.vcf!" .
5. Security & Privacy Considerations
5.1. The 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.
Information published in ENUM records could reveal associations
between E.164 numbers and their owners - especially if records
contain personal identifiers or domain names for which ownership
Mayrhofer & Lindner Expires November 27, 2006 [Page 5]
Internet-Draft vCard Enumservice May 2006
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. The Resource Identified
Users SHOULD carefully consider information they provide in the
resource identified by the ENUM record. 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 requesting entity.
On the other hand, most of the information which a vCard would
typically contain is already available via more "traditional" sources
like white pages and online directories. Therefore, publishing a
vCard on the internet and associating it to a phone number does not
increase the amount of available information at all if the
information was already public before.
If access restrictions are deployed, Standard HTTP mechanisms MUST be
used to enforce those restrictions. HTTPS SHOULD be preferred if the
deployed mechanisms are prone to eavesdropping and replay attacks.
6. IANA Considerations
This memo requests registration of the "vCard" Enumservice according
to the definitions in this document and RFC3761 [1].
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] Dawson, F. and T. Howes, "vCard MIME Directory Profile",
RFC 2426, September 1998.
Mayrhofer & Lindner Expires November 27, 2006 [Page 6]
Internet-Draft vCard Enumservice May 2006
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] Iannella, R., "Representing vCard Objects in RDF/XML", W3C
NOTE NOTE-vcard-rdf-20010222, February 2001.
[7] ITU-T, "The international public telecommunication numbering
plan", Recommendation E.164, May 1997.
Mayrhofer & Lindner Expires November 27, 2006 [Page 7]
Internet-Draft vCard Enumservice May 2006
Authors' Addresses
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/
David Lindner
Silver Voice over Internet Protocol GmbH
Lorenz-Mandl-Gasse 33/1
A-1160 Wien
Austria
Phone: +43 1 4933256
Email: d.lindner@sil.at
URI: http://www.sil.at/
Mayrhofer & Lindner Expires November 27, 2006 [Page 8]
Internet-Draft vCard Enumservice May 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.
Mayrhofer & Lindner Expires November 27, 2006 [Page 9]
