idnits 2.17.1 draft-yevstifeyev-vcarddav-version-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 17, 2011) is 4577 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFCXXXX' is mentioned on line 147, but not defined -- Obsolete informational reference (is this intentional?): RFC 2426 (Obsoleted by RFC 6350) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Yevstifeyev 3 Intended Status: Standards Track September 17, 2011 4 Expires: March 20, 2012 6 Registration of vCard VERSION Property Values 7 draft-yevstifeyev-vcarddav-version-00 9 Abstract 11 This document registers the existing vCard VERSION property values 12 with IANA and contains some provisions on its generic syntax and use. 14 Status of this Memo 16 This Internet-Draft is submitted to IETF in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as 22 Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Copyright and License Notice 37 Copyright (c) 2011 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 53 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. vCard VERSION Property . . . . . . . . . . . . . . . . . . . . 2 55 2.1. Generic Syntax . . . . . . . . . . . . . . . . . . . . . . 2 56 2.2. Use of VERSION Property . . . . . . . . . . . . . . . . . . 3 57 2.3. Registration of VERSION Property Values . . . . . . . . . . 3 58 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 60 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 5.1. Normative References . . . . . . . . . . . . . . . . . . . 4 62 5.2. Informative References . . . . . . . . . . . . . . . . . . 4 63 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 5 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 vCard is used to represent and exchange a variety of information 69 about individuals and other entities (e.g., formatted and structured 70 name and delivery addresses, email address, multiple telephone 71 numbers, photograph, logo, audio clips, etc.). The most current 72 vCard specification is RFC 6350 [RFC6350], that defines version 4.0 73 of vCard. However, a number of other vCard versions existed prior to 74 publication of RFC 6350. 76 vCard entity is capable of carrying information about its version in 77 the VERSION property. The purpose of this document is to register 78 all existing vCard versions as VERSION property values in the 79 corresponding registry set up by RFC 6350. It also clarifies the 80 generic syntax of VERSION property and contains guidelines on its use 81 in vCard entities that conform to different vCard versions. 83 1.1. Terminology 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in RFC 2119 [RFC2119]. 89 2. vCard VERSION Property 91 2.1. Generic Syntax 93 The VERSION property was first introduced in vCard 2.1 [VCARD21], and 94 continued to be used in vCard 3.0 [RFC2426] and vCard 4.0 [RFC6350]. 95 Each of the aforementioned specifications defined a separate syntax 96 for VERSION property which is appropriate for use in vCard entities 97 conformant to such specification, such as (from RFC 6350; ABNF 99 [RFC5234] is used): 101 VERSION-value = "4.0" 103 for VERSION property value of vCard 4.0. 105 This document defines a simple generic syntax for VERSION property 106 values, that is expressed using Augmented Backus-Naur Form (ABNF) 107 [RFC5234] in the production: 109 VERSION-value = 1*DIGIT "." DIGIT 111 where is specified in RFC 5234 [RFC5234]. All subsequent 112 versions of vCard MUST define VERSION property value syntax that is 113 compatible with this document. 115 2.2. Use of VERSION Property 117 As VERSION property was first introduced in vCard 2.1 [VCARD21], 118 vCard 2.0 and vCard 1.0 did not contain such facility. However, this 119 document set up the rule that any vCard entity, independent of the 120 version, SHOULD contain VERSION property, with the value conformant 121 to syntax described in Section 2.1, and such property, if present, 122 SHOULD be put after the BEGIN property. 124 2.3. Registration of VERSION Property Values 126 Section 4 of this document registers VERSION property values for all 127 existing vCard versions, beginning with vCard 1.0 and ending in vCard 128 4.0. Specifications of further versions of vCard are supposed to 129 register their own version. 131 3. Security Considerations 133 This document is not believed to affect security of vCard in any way. 135 4. IANA Considerations 137 IANA is asked to add the following entries in the vCard Property 138 Values registry created by RFC 6350: 140 +----------+--------+-------------------------+ 141 | Property | Value | Reference | 142 +----------+--------+-------------------------+ 143 | VERSION | 1.0 | [VCARD10], [RFCXXXX] | 144 | VERSION | 2.0 | [VCARD20], [RFCXXXX] | 145 | VERSION | 2.1 | [VCARD21], [RFCXXXX] | 146 | VERSION | 3.0 | [RFC2426], [RFCXXXX] | 147 | VERSION | 4.0 | [RFC6350], [RFCXXXX] | 148 +----------+--------+-------------------------+ 150 5. References 152 5.1. Normative References 154 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 155 Requirement Levels", BCP 14, RFC 2119, March 1997. 157 [RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for 158 Syntax Specifications: ABNF", STD 68, RFC 5234, January 159 2008. 161 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 162 August 2011. 164 5.2. Informative References 166 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 167 RFC 2426, September 1998. 169 [VCARD10] Reference unknown for the present. 171 [VCARD20] Versit Consortium, "The Electronic Business Card Version 172 2.0", Versit Consortium Specification, April 1996, 173 . 175 Note: the link is temporary only and will be replaced soon 176 by another one. 178 [VCARD21] Versit Consortium, "The Electronic Business Card Version 179 2.1", Versit Consortium Specification, September 1996, 180 . 182 Appendix A. Acknowledgments 184 Thanks to Roland Alden for providing vCard 2.0 specification. 186 Authors' Addresses 188 Mykyta Yevstifeyev 189 8 Kuzovkov St., Apt. 25 190 Kotovsk 191 Ukraine 193 EMail: evnikita2@gmail.com