Application Working Group Doug Royer/INET-Consulting LLC Internet Draft October 3, 2003 Expires: March 2004 Using VCARDs with iCalendar draft-royer-ical-vcard-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 March 1, 2004. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. ABSTRACT This memo is a registration of a [iCAL] component called "VCARD". And defines that the "VCARD" component as the 'vcard entity' object as defined in [vCARD] and [LDAPVCARD]. This memo describes a way to include contact information in [iCAL] objects. The contact information is included by the insertion of [vCARD] objects into [iCAL] objects. Also included is an extension to [LDAPVCARD] to allow [CAP] URLs. This memo does not define [iCAL] or [vCARD] objects. 1. Registration of VCARDURL parameter for iCalendar Parameter Name: VCARDURI Purpose: To specify the URL of a [vCARD] that matches the property value associated with the "VCARDURL" parameter. Value Type: URI Format Definition: The property parameter is defined by the following notation: Royer Expires: March 2004 [Page 1] Internet Draft Using VCARDs with iCalendar October 3, 2003 vcardparam = "VCARDURL" "=" uri Description: This parameter can be specified on properties with a CAL- ADDRESS value type. The parameter identifies the location of a [vCARD] that describes in [vCARD] format information about the associated property value. Examples: ATTENDEE;VCARDURL="CID:": MAILTO:jsmith@host.com ATTENDEE;VCARDURL="CAP:cal.example.com/user?search=vcard:123.vcf": CAP:Doug@Royer.com ATTENDEE;VCARDURL="https:cal.example.com/user?uid=vcard=123.vcf": CAP:Doug@Royer.com The only restriction of the "VCARD" parameter value is that it point to a machine readable [vCARD] and that it is not to point to a textual description of the property value indented for a human to read. So it could be a [vCARD] object as part of a MIME multipart object, an FTP:, HTTP:, HTTPS:, CAP:, FILE:, or other URI. Any implementation conforming to this specification must be able to parse the URI contents. 2. Extension of [iTIP] Restriction Tables The following is an extension of the [iTIP] restriction tables to allow a [vCARD] object to be sent in [iCAL] objects. The "Organizer" may include a "VCARD" component in objects sent to "Attendees". They may be included in components that have a "METHOD" property with a "PUBLISH" or "REQUEST" values. For implementations that conform to this specification the following is added to the restriction tables in [iTIP]: VEVENT: In: [iTIP] Section 3.2.1, Page 16, After the line: METHOD 1 MUST BE "PUBLISH" VCARD 0 or 1 The "Organizers" VCARD may be included In: [iTIP] Section 3.2.2, Page 18, After the line: METHOD 1 MUST BE "REQUEST" VCARD 0 or 1 The "Organizers" VCARD may be included In: [iTIP] Section 3.2.3, Page 16, After the line: METHOD 1 MUST BE "REPLY" Royer Expires: March 2004 [Page 2] Internet Draft Using VCARDs with iCalendar October 3, 2003 VCARD 0 or 1 The "Attendees" VCARD may be included. In: [iTIP] Section 3.2.4, Page 24, After the line: METHOD 1 MUST BE "ADD" VCARD 0 or 1 The "Organizers" VCARD may be included. In: [iTIP] Section 3.2.5, Page 25, After the line: METHOD 1 MUST BE "CANCEL" VCARD 0 or 1 The "Organizers" VCARD may be included. VFREEBUSY: In: [iTIP] Section 3.3.1, Page 32, After the line: METHOD 1 MUST BE "PUBLISH" VCARD 0 or 1 The Calendar Owners VCARD may be included In: [iTIP] Section 3.3.2, Page 33, After the line: METHOD 1 MUST BE "REQUEST" VCARD 0 or 1 The Requesters VCARD may be included In: [iTIP] Section 3.3.3, Page 34, After the line: METHOD 1 MUST BE "REPLY" VCARD 0 or 1 The Repliers VCARD may be included. VTODO: In: [iTIP] Section 3.4.1, Page 36, After the line: METHOD 1 MUST BE "PUBLISH" VCARD 0 or 1 The "Organizers" VCARD may be included In: [iTIP] Section 3.4.2, Page 38, After the line: METHOD 1 MUST BE "REQUEST" VCARD 0 or 1 The "Organizers" VCARD may be included In: [iTIP] Section 3.4.3, Page 42, After the line: METHOD 1 MUST BE "REPLY" VCARD 0 or 1 The "Attendees" VCARD may be included. In: [iTIP] Section 3.4.4, Page 43, After the line: METHOD 1 MUST BE "ADD" VCARD 0 or 1 The "Organizers" VCARD may be included. Royer Expires: March 2004 [Page 3] Internet Draft Using VCARDs with iCalendar October 3, 2003 In: [iTIP] Section 3.4.5, Page 45, After the line: METHOD 1 MUST BE "CANCEL" VCARD 0 or 1 The "Organizers" VCARD may be included. VJOURNAL: In: [iTIP] Section 3.5.1, Page 51, After the line: METHOD 1 MUST BE "PUBLISH" VCARD 0 or 1 The Calendar Owners VCARD may be included In: [iTIP] Section 3.5.2, Page 52, After the line: METHOD 1 MUST BE "ADD" VCARD 0 or 1 The Calendar Owners VCARD may be included. 3. When to include VCARDs There is no requirement that the "Organizer" or "Attendee" include a "VCARD" component. They should be included whenever the a change to the [vCARD] is deemed to be significant and in the original object sent to a new recipient or when sending an [INVITATION]. 3.1 VCARD and CAP With the addition of the "VCARD" component there is no major impact on [CAP] or [iCAL] as this memo defines the "VCARD" component as a new 'iana-comp' and therefore can be used and searched for like any other component. 3.2 Adding CAP URLs to [LDAPVCARD] This memo also extends [LDAPVCARD] to allow the [CAP] URL 'cap:' in the 'FBURL' and 'CALURL' [vCARD] properties. 3.3 CAP URI as FBURL property value The following is to be considered added to section "1.3" of [LDAPVCARD]: CAP URI -- If the URI is a CAP URI, then it is the address of a [CAP] server where a snapshot of the users calendar can be retrieived as the [CAP] anonymous UPN '@'. Only BOOKED and PUBLIC components will be returned. Use the "CAPURI" property for non anonymous access to the [CAP] server. 3.4 CAP URI as CAPURI property value The following is to be considered added to section "1.3" of [LDAPVCARD]: Royer Expires: March 2004 [Page 4] Internet Draft Using VCARDs with iCalendar October 3, 2003 CAP URI -- If the URI is a CAP URI, then it is the address of a [CAP] server where a snapshot of the users calendar can be retrieived as the [CAP] anonymous UPN '@'. Only BOOKED and PUBLIC components will be returned. Use the "CAPURI" property for non anonymous access to the [CAP] server. 3.5 Bibliography [iCAL] Dawson, F. and Stenerson, D., "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1998, ftp://ftp.isi.edu/in-notes/rfc2445.txt [iTIP] Silverberg, S., Mansour, S., Dawson, F. and Hopson, R., "iCalendar Transport-Independent Interoperability Protocol (iTIP) Events, BusyTime, To-dos and Journal Entries", RFC 2446, November 1998 ftp://ftp.isi.edu/in-notes/rfc2446.txt [iMIP] Dawson, F., Mansour, S. and Silverberg, "iCalendar Message-Based Interoperability Protocol (iMIP)", RFC 2447, November 1998, ftp://ftp.isi.edu/in-notes/rfc2447.txt [CAP] Royer, D., Babics, G., Hill, P. Mansour, S. "Calendar Access Protocol (CAP)", work in progress, September 2003, draft-ietf-calsch-cap-12.txt [INVITATION] Royer, D. "How to create dynamic UPNs for invited ATTENDEEs", work in progress, October 2003, draft-royer-calsch-dynamic-upn-02.txt [vCARD] Dawson F., Howes T., "vCard MIME Directory Profile", RFC2426, September 1998, ftp://ftp.isi.edu/in-notes/rfc2426.txt [LDAPCARD] Small T., Hennesy D., Dawson F. "Calendar Attributes for vCARD and LDAP", RFC 2739, January 2000, ftp://ftp.isi.edu/in-notes/rfc2736.txt 4. Author's Address Doug Royer http://INET-Consulting.com 1795 W. Broadway #266 Idaho Falls, Idaho 83402 US Phone: 208-520-4044 Fax: 866-594-8574 EMail: Doug@Royer.com URI: http://Royer.com/People/Doug Royer Expires: March 2004 [Page 5] Internet Draft Using VCARDs with iCalendar October 3, 2003 CALADRUI: mailto:Doug@Cal.Royer.com Royer Expires: March 2004 [Page 6] Internet Draft Using VCARDs with iCalendar October 3, 2003 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than nglish. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Royer Expires: March 2004 [Page 7]