idnits 2.17.1 draft-li-vcarddav-vcard-id-property-extensions-02.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 (June 22, 2011) is 4682 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) == Outdated reference: A later version (-22) exists of draft-ietf-vcarddav-vcardrev-15 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 vcarddav K. Li 3 Internet-Draft B. Leiba 4 Intended status: Standards Track Huawei Technologies 5 Expires: December 24, 2011 June 22, 2011 7 vCard Format Extensions : place of birth, place and date of death 8 draft-li-vcarddav-vcard-id-property-extensions-02 10 Abstract 12 The base vCard 4.0 specification defines a large number of 13 properties, including date of birth. This specification adds three 14 new properties to vCard 4.0, for place of birth, place of death, and 15 date of death. 17 Note 19 Discussion and suggestions for improvement are requested, and should 20 be sent to vcarddav@ietf.org. 22 Status of this Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on December 24, 2011. 39 Copyright Notice 41 Copyright (c) 2011 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1.1. Terminology Used in This Document . . . . . . . . . . . . . 3 58 2. Identification Property Extensions . . . . . . . . . . . . . . 3 59 2.1. Property: BIRTH . . . . . . . . . . . . . . . . . . . . . . 3 60 2.2. Property: DEATH . . . . . . . . . . . . . . . . . . . . . . 4 61 2.3. Property: DDAY . . . . . . . . . . . . . . . . . . . . . . 4 62 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 63 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 64 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 65 6. Normative References . . . . . . . . . . . . . . . . . . . . . 6 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 68 1. Introduction 70 The base vCard 4.0 specification [I-D.ietf-vcarddav-vcardrev] defines 71 a large number of properties, including date of birth. This 72 specification adds three new properties to vCard 4.0, for place of 73 birth, place of death, and date of death. 75 1.1. Terminology Used in This Document 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in [RFC2119]. 81 Syntax specifications shown here use the augmented Backus-Naur Form 82 (ABNF) as described in [RFC5234], and are specified as in the base 83 vcard specification [I-D.ietf-vcarddav-vcardrev]. 85 2. Identification Property Extensions 87 2.1. Property: BIRTH 89 Namespace: 91 Property name: BIRTH 93 Purpose: To specify the place of birth of the object the vCard 94 represents. 96 Value type: A single text value (default) or a single URI value. 98 Cardinality: *1 100 Property parameters: VALUE, LANGUAGE 102 Description: 104 Format definition: 105 BIRTH-param = "VALUE=" / ("text" / "uri") 106 BIRTH-value = text / uri 107 ; Value and parameter MUST match. 109 BIRTH-param =/ altid-param / language-param / any-param 111 Examples: 112 BIRTH:Babies'R'Us Hospital 113 BIRTH;VALUE=uri:http://example.com/hospitals/babiesrus.vcf 114 BIRTH;VALUE=uri:geo:46.769307,-71.283079 116 2.2. Property: DEATH 118 Namespace: 120 Property name: DEATH 122 Purpose: To specify the place of death of the object the vCard 123 represents. 125 Value type: A single text value (default) or a single URI value. 127 Cardinality: *1 129 Property parameters: VALUE, LANGUAGE 131 Description: 133 Format definition: 134 DEATH-param = "VALUE=" / ("text" / "uri") 135 DEATH-value = text / uri 136 ; Value and parameter MUST match. 138 DEATH-param =/ altid-param / language-param / any-param 140 Examples: 141 DEATH:Aboard the Titanic\, near Newfoundland 142 DEATH;VALUE=uri:http://example.com/ships/titanic.vcf 143 DEATH;VALUE=uri:41.731944,-49.945833 145 2.3. Property: DDAY 147 Namespace: 149 Property name: DDAY 151 Purpose: To specify the date of death of the object the vCard 152 represents. 154 Value type: The default is a single date-and-or-time value. It can 155 also be reset to a single text value. 157 Cardinality: *1 159 Property parameters: VALUE, CALSCALE, LANGUAGE 160 CALSCALE can only be present when the value is a 161 date-and-or-time value and actually contains a date or date-time. 162 LANGUAGE can only be present when the value is text. 164 Description: 166 Format definition: 167 DDAY-param = DDAY-param-date / DDAY-param-text 168 DDAY-value = date-and-or-time / text 169 ; Value and parameter MUST match. 171 DDAY-param-date = "VALUE=date-and-or-time" 172 DDAY-param-text = "VALUE=text" / language-param 174 DDAY-param =/ altid-param / calscale-param / any-param 175 ; calscale-param can only be present when DDAY-value is 176 ; date-and-or-time and actually contains a date or date-time. 178 Examples: 179 DDAY:19960415 180 DDAY:--0415 181 DDAY;19531015T231000Z 182 DDAY;VALUE=text:circa 1800 184 3. Security Considerations 186 This presents no security considerations beyond those in section 9 of 187 the base vcard specification [I-D.ietf-vcarddav-vcardrev]. 189 4. IANA Considerations 191 The IANA is requested to add the following entries to the vCard 192 Properties registry, defined in [I-D.ietf-vcarddav-vcardrev] section 193 10.3.1. 195 +-----------+--------------+---------+------------------------+ 196 | Namespace | Property | Status | Reference | 197 +-----------+--------------+---------+------------------------+ 198 | | BIRTH | Current | RFCXXXX, section 2.1 | 199 | | DEATH | Current | RFCXXXX, section 2.2 | 200 | | DDAY | Current | RFCXXXX, section 2.3 | 201 +-----------+--------------+---------+------------------------+ 203 5. Acknowledgements 205 The author of this draft would like thank the authors of 206 draft-ietf-vcarddav-vcardrev-13, because much of the text is copied 207 from there. 209 6. Normative References 211 [I-D.ietf-vcarddav-vcardrev] 212 Perreault, S. and P. Resnick, "vCard Format 213 Specification", draft-ietf-vcarddav-vcardrev-15 (work in 214 progress), December 2010. 216 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 217 Requirement Levels", BCP 14, RFC 2119, March 1997. 219 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 220 Specifications: ABNF", STD 68, RFC 5234, January 2008. 222 Authors' Addresses 224 Kepeng Li 225 Huawei Technologies 226 Huawei Base, Bantian, Longgang District 227 Shenzhen, Guangdong 518129 228 P. R. China 230 Phone: +86-755-28974289 231 Email: likepeng@huawei.com 233 Barry Leiba 234 Huawei Technologies 236 Phone: +1 646 827 0648 237 Email: barryleiba@computer.org 238 URI: http://internetmessagingtechnology.org/