INTERNET-DRAFT M. Yevstifeyev Intended Status: Standards Track September 17, 2011 Expires: March 20, 2012 Registration of vCard VERSION Property Values draft-yevstifeyev-vcarddav-version-00 Abstract This document registers the existing vCard VERSION property values with IANA and contains some provisions on its generic syntax and use. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright and License Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Yevstifeyev Expires March 20, 2012 [Page 1] INTERNET DRAFT vCard VERSION Values September 17, 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 2 2. vCard VERSION Property . . . . . . . . . . . . . . . . . . . . 2 2.1. Generic Syntax . . . . . . . . . . . . . . . . . . . . . . 2 2.2. Use of VERSION Property . . . . . . . . . . . . . . . . . . 3 2.3. Registration of VERSION Property Values . . . . . . . . . . 3 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Normative References . . . . . . . . . . . . . . . . . . . 4 5.2. Informative References . . . . . . . . . . . . . . . . . . 4 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction vCard is used to represent and exchange a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). The most current vCard specification is RFC 6350 [RFC6350], that defines version 4.0 of vCard. However, a number of other vCard versions existed prior to publication of RFC 6350. vCard entity is capable of carrying information about its version in the VERSION property. The purpose of this document is to register all existing vCard versions as VERSION property values in the corresponding registry set up by RFC 6350. It also clarifies the generic syntax of VERSION property and contains guidelines on its use in vCard entities that conform to different vCard versions. 1.1. 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 [RFC2119]. 2. vCard VERSION Property 2.1. Generic Syntax The VERSION property was first introduced in vCard 2.1 [VCARD21], and continued to be used in vCard 3.0 [RFC2426] and vCard 4.0 [RFC6350]. Each of the aforementioned specifications defined a separate syntax for VERSION property which is appropriate for use in vCard entities conformant to such specification, such as (from RFC 6350; ABNF Yevstifeyev Expires March 20, 2012 [Page 2] INTERNET DRAFT vCard VERSION Values September 17, 2011 [RFC5234] is used): VERSION-value = "4.0" for VERSION property value of vCard 4.0. This document defines a simple generic syntax for VERSION property values, that is expressed using Augmented Backus-Naur Form (ABNF) [RFC5234] in the production: VERSION-value = 1*DIGIT "." DIGIT where is specified in RFC 5234 [RFC5234]. All subsequent versions of vCard MUST define VERSION property value syntax that is compatible with this document. 2.2. Use of VERSION Property As VERSION property was first introduced in vCard 2.1 [VCARD21], vCard 2.0 and vCard 1.0 did not contain such facility. However, this document set up the rule that any vCard entity, independent of the version, SHOULD contain VERSION property, with the value conformant to syntax described in Section 2.1, and such property, if present, SHOULD be put after the BEGIN property. 2.3. Registration of VERSION Property Values Section 4 of this document registers VERSION property values for all existing vCard versions, beginning with vCard 1.0 and ending in vCard 4.0. Specifications of further versions of vCard are supposed to register their own version. 3. Security Considerations This document is not believed to affect security of vCard in any way. Yevstifeyev Expires March 20, 2012 [Page 3] INTERNET DRAFT vCard VERSION Values September 17, 2011 4. IANA Considerations IANA is asked to add the following entries in the vCard Property Values registry created by RFC 6350: +----------+--------+-------------------------+ | Property | Value | Reference | +----------+--------+-------------------------+ | VERSION | 1.0 | [VCARD10], [RFCXXXX] | | VERSION | 2.0 | [VCARD20], [RFCXXXX] | | VERSION | 2.1 | [VCARD21], [RFCXXXX] | | VERSION | 3.0 | [RFC2426], [RFCXXXX] | | VERSION | 4.0 | [RFC6350], [RFCXXXX] | +----------+--------+-------------------------+ 5. References 5.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, August 2011. 5.2. Informative References [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998. [VCARD10] Reference unknown for the present. [VCARD20] Versit Consortium, "The Electronic Business Card Version 2.0", Versit Consortium Specification, April 1996, . Note: the link is temporary only and will be replaced soon by another one. [VCARD21] Versit Consortium, "The Electronic Business Card Version 2.1", Versit Consortium Specification, September 1996, . Yevstifeyev Expires March 20, 2012 [Page 4] INTERNET DRAFT vCard VERSION Values September 17, 2011 Appendix A. Acknowledgments Thanks to Roland Alden for providing vCard 2.0 specification. Authors' Addresses Mykyta Yevstifeyev 8 Kuzovkov St., Apt. 25 Kotovsk Ukraine EMail: evnikita2@gmail.com Yevstifeyev Expires March 20, 2012 [Page 5]