Cisco Systems

170 West Tasman Drive MS: SJC-21/2 San Jose CA 95134 USA +1 408 902-3341 fluffy@cisco.com

greenbytes GmbH

Hafenweg 16 MuensterNW48155 Germany +49 251 2807760 julian.reschke@greenbytes.de

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 draftIt allows a URI that is associated with IM or PP to be specified inside of a vCard. This work is being discussed on the imc-vcard@imc.org mailing list. Umbrella issue for editorial fixes/enhancements. Take out reference to IRC URI draft (which is dead)? Update ref to XMPP URI/IRI spec. Done. Ted Hardie: I believe citing the ABNF RFC as normative is also required. Done. Ted Hardie: This document apparently imports the definition of uri from 2425, which in turn says that URI is "as defined in 1738". 1738's description of URIs has long been superseded, and its formal description of genericurl (the closest thing to this) is in RFC822's BNF-like grammar, not ABNF. May I suggest this document cite RFC 3986 directly? It's a full standard. Done. Clarify that type parameter contains one or more values. Done. Lars Eggert (IESG discussion): Might want to mention that some vendors have already extended the vcard format to include IM addresses. I think there are two sides to this: (1) is there a deployed format that we could use instead of inventing a new one, and (2) if we decide to invent a new one, should we discuss other approaches we rejected?
My take: (1) the format used by Apple (mentioned by Lars) assigns a new type for each IMPP URI scheme - that seems to be a bad idea as it doesn't allow clients to uniformly treat different IMPP systems without prior knowledge of what the URI scheme is. So no, the format used by Apple doesn't seem to be a good idea. As for (2), I'd like to avoid that additional work. However I'm open to add minimal text mentioning other approaches if people make a concrete proposal for spec text.

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 and RFC 2426 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 (see RFC 3986) 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 "sip" indicates to use SIP/SIMPLE, "xmpp" indicates to use XMPP, "irc" indicates to use IRC, "ymsgr" indicates to use yahoo, "msn" might indicate to use Microsoft messenger, "aim" indicates to use AOL, and "im" or "pres" indicates to use a CPIM or CPP gateway. The normative definition of this new vCard type is given in , and an informational ABNF is provided in .

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" (see ). 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 canmay include the type parameter "TYPE" to specify an intended use for the URI. The TYPE parameter values can includeinclude one or more of the following: An indication of the type of communication for which this URI is appropriate. This can be a value of PERSONAL or BUSINESS. An indication of the location of a device associated with this URI. Values can be HOME, WORK, or MOBILE. The value PREF indicates this is a preferred address and has the same semantics as the PREF value in a TEL type. Additional information can be found in RFCAAAA. Intended usage: COMMON [Note to IANA: Please replace AAAA with the RFC number for this specification.]

The following ABNF grammar extends the grammar found in RFC 2425 () and RFC 2426 ().

;For name="IMPP" param = impp-param ; Only impp parameters are allowed value = uriURI ; URI defined in 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

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

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.

Thanks to Brian Carpenter, Lars Eggert, Ted Hardie, Paul Hoffman, Sam Roberts and Pekka Pessi for their comments.

Netscape Communications Corp.

501 East Middlefield Rd. Mountain View CA 94041 USA +1.415.937.3419 howes@netscape.com

Netscape Communications Corp.

501 East Middlefield Rd. Mountain View CA 94041 USA +1.415.937.3477 mcs@netscape.com

Lotus Development Corporation

6544 Battleford Drive Raleigh NC 27613 USA +1-919-676-9515 frank_dawson@lotus.com

Applications MIME content-type directory multipurpose internet mail extensions Lotus Development Corporation

6544 Battleford Drive Raleigh NC 27613 USA +1-919-676-9515 frank_dawson@lotus.com

Netscape Communications Corp.

501 East Middlefield Rd. Mountain View CA 94041 USA +1.415.937.3419 howes@netscape.com

Applications MIME audio content-type directory multipurpose internet mail extensions World Wide Web Consortium

timbl@w3.org

Day Software

fielding@gbiv.com

Adobe Systems Incorporated

LMM@acm.org

Brandenburg InternetWorking

675 Spruce Dr. Sunnyvale CA 94086 US +1.408.246.8253 dcrocker@bbiw.net

THUS plc.

1/2 Berkeley Square 99 Berkely Street Glasgow G3 7HR UK paul.overell@thus.net

Brandenburg InternetWorking

675 Spruce Dr. Sunnyvale CA 94086 US +1.408.246.8253 dcrocker@bbiw.net

THUS plc.

1/2 Berkeley Square 99 Berkely Street Glasgow G3 7HR UK paul.overell@thus.net

This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP).

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.

Update XMPP URI/IRI reference. Add and resolve issues "abnf-ref-normative", "clarify-type-recurrence" and "cite-rfc3986-for-URI". Add open issue "mention-other-approaches".