Network Working GroupC. Jennings
Internet-DraftCisco Systems
Intended status: Standards TrackJ. Reschke, Editor
Expires: December 2006greenbytes
June 2006

vCard Extensions for Instant Messaging (IM)

draft-jennings-impp-vcard-07

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 in December 2006.

Copyright Notice

Copyright © The Internet Society (2006). All Rights Reserved.

Abstract

This document describes an extension to vCard to support Instant Messaging (IM) and Presence Protocol (PP) applications. IM and PP are becoming increasingly common ways of communicating, and users want to save this contact information in their address books. This draft allows a URI that is associated with IM or PP to be specified inside of a vCard.

 I  

Editorial Note (To be removed by RFC Editor before publication)

This work is being discussed on the imc-vcard@imc.org mailing list.

 I  edit   (type: edit, status: open)
julian.reschke@greenbytes.de2006-06-25 Umbrella issue for editorial fixes/enhancements.
Associated changes in this document: <#rfc.change.edit.1>, <#rfc.change.edit.2>, 1, 2, 3, 7.1, 7.2, 7.2, <#rfc.change.edit.9>.
 I  irc-uri   (type: edit, status: open)
julian.reschke@greenbytes.de2006-06-25 Take out reference to IRC URI draft (which is dead)?
 I  

del-1. Conventions

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 [del].

1. Overview

As more and more people use various instant messaging (IM) and presence protocol (PP) applications, it becomes important for them to be able to share this contact address information along with the rest of their contact information. RFC 2425 [1] and RFC 2426 [2] define a standard format for this information, which is referred to as vCard. This document defines a new type in a vCard for representing instant IM and PP URIs. It is very similar to existing types for representing email address and telephone contact information.

The type entry to hold this new contact information is an IMPP type. The IMPP entry has a single URI that indicates the address of a service that provides IM, PP, or both. Also defined are some parameters that give hints as to when certain URIs would be appropriate. A given vCard can have multiple IMPP entries, but each entry can contain only one URI. Each IMPP entry can contain multiple parameters. Any combination of parameters is valid, although a parameter should occur at most once in a given IMPP entry.

The type of URI indicates what protocols might be usable for accessing it, but this document does not define any of the types. For example a URI type of

The normative definition of this new vCard type is given in Section 2, and an informational ABNF is provided in Section 3.

2. IANA Considerations

The required email to define this extension (as defined in RFC2425) was sent on October 29, 2004 to the ietf-mime-direct@imc.org mailing list with the subject "Registration of text/directory MIME type IMPP" I  (see <http://www.imc.org/ietf-mime-direct/mail-archive/msg00068.html>).

This specification updates the "text/directory MIME Types" subregistry in the "text/directory MIME Registrations" registry at http://www.iana.org/assignments/text-directory-registrations with the following information:

Type name: IMPP

Type purpose: To specify the URI for instant messaging and presence protocol communications with the object the vCard represents.

Type encoding: 8bit

Type value: A single URI. The type of the URI indicates the protocol that can be used for this contact.

Type special notes: The type can include the type parameter "TYPE" to specify an intended use for the URI. The TYPE parameter values can include:

Additional information can be found in RFCAAAA.

Intended usage: COMMON

[Note to IANA: Please replace AAAA with the RFC number for this specification.]

3. Formal Grammar

The following ABNF grammar  I [del][3] extends the grammar found in RFC 2425 [1] and RFC 2426 [2].

;For name="IMPP"
 param      = impp-param ; Only impp parameters are allowed

 value      = uri

 impp-param = "TYPE" "=" impp-type *("," impp-type)
 
 impp-type  = "PERSONAL" / "BUSINESS" / ; purpose of communications 
              "HOME" / "WORK" / "MOBILE" /
              "PREF" / 
              iana-token / x-name; 
              ; Values are case insensitive 

4. Example

BEGIN:vCard
VERSION:3.0
FN:Alice Doe
IMPP;TYPE=personal,pref:im:alice@example.com
END:vCard

5. Security Considerations

This does not introduce additional security issues beyond the current vCard specification. It is worth noting that many people consider their presence information more sensitive than other address information. Any system that stores or transfers vCards needs to carefully consider the privacy issues around this information.

6. Acknowledgments

Thanks to Paul Hoffman, Sam Roberts and Pekka Pessi for their comments.

7. References

7.1. Normative References

[1]
Howes, T., Smith, M., and F. Dawson, “A MIME-Content-Type for Directory Information”, RFC 2425, September 1998.
[2]
Dawson, F. and T. Howes, “vCard MIME Directory Profile”, RFC 2426, September 1998.
[del]
Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997.

7.2. Informational References

[del]
Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF”, RFC 2234, November 1997.
[3]
Crocker, D., Ed. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF”, RFC 4234, October 2005.
[4]
Butcher, S., “Uniform Resource Locator Schemes for Internet Relay Chat Entities”, Internet-Draft draft-butcher-irc-url-04 (work in progress), January 2004.
[5]
Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, “SIP: Session Initiation Protocol”, RFC 3261, June 2002.
[del]
Saint-Andre, P., “XMPP URI Format”, Internet-Draft draft-saintandre-xmpp-uri-08 (work in progress), December 2004.
[6]
Saint-Andre, P., “Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)”, Internet-Draft draft-saintandre-xmpp-iri-04 (work in progress), March 2006.
[7]
Peterson, J., “Common Profile for Presence (CPP)”, RFC 3859, August 2004.
[8]
Peterson, J., “Common Profile for Instant Messaging (CPIM)”, RFC 3860, August 2004.
 I  

A. Change Log (to be removed by RFC Editor before publication)

A.1. Since draft-jennings-impp-vcard-06.xml

Remove "Notational Conventions" (weren't actually used). Take out reference to RFC2119 accordingly.

Highlight editing instructions for the RFC Editor.

Add link to mention of registration request email.

Update reference to ABNF RFC and XMPP URI/IRI draft.

Add Julian Reschke as Editor.

Authors' Addresses

Cullen Jennings
Cisco Systems
170 West Tasman Drive
MS: SJC-21/2
San Jose, CA 95134
USA
Phone: +1 408 902-3341
EMail: fluffy@cisco.com
Julian F. Reschke (editor)
greenbytes GmbH
Hafenweg 16
Muenster, NW 48155
Germany
Phone: +49 251 2807760
EMail: julian.reschke@greenbytes.de

Full Copyright Statement

Copyright © 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.

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.

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.