draft-ietf-vcarddav-vcardrev-10.txt   draft-ietf-vcarddav-vcardrev-11.txt 
Network Working Group S. Perreault Network Working Group S. Perreault
Internet-Draft Viagenie Internet-Draft Viagenie
Obsoletes: 2425, 2426, 4770 P. Resnick Obsoletes: 2425, 2426, 4770 P. Resnick
(if approved) QUALCOMM Incorporated (if approved) QUALCOMM Incorporated
Updates: 2739 (if approved) March 8, 2010 Updates: 2739 (if approved) May 9, 2010
Intended status: Standards Track Intended status: Standards Track
Expires: September 9, 2010 Expires: November 10, 2010
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-10 draft-ietf-vcarddav-vcardrev-11
Abstract Abstract
This document defines the vCard data format for representing and This document defines the vCard data format for representing and
exchanging a variety of information about individuals and other exchanging a variety of information about individuals and other
entities (e.g., formatted and structured name and delivery addresses, entities (e.g., formatted and structured name and delivery addresses,
email address, multiple telephone numbers, photograph, logo, audio email address, multiple telephone numbers, photograph, logo, audio
clips, etc.). clips, etc.).
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 9, 2010. This Internet-Draft will expire on November 10, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 52 skipping to change at page 2, line 52
4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13 4.3.3. DATE-TIME . . . . . . . . . . . . . . . . . . . . . . 13
4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14 4.3.4. DATE-AND-OR-TIME . . . . . . . . . . . . . . . . . . . 14
4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 14 4.3.5. TIMESTAMP . . . . . . . . . . . . . . . . . . . . . . 14
4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16 4.8. LANGUAGE-TAG . . . . . . . . . . . . . . . . . . . . . . . 16
5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16 5. Property Parameters . . . . . . . . . . . . . . . . . . . . . 16
5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.4. PREF . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.5. PID . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.6. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.7. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.7. CALSCALE . . . . . . . . . . . . . . . . . . . . . . . . . 20
6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 20 6. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. General Properties . . . . . . . . . . . . . . . . . . . . 20 6.1. General Properties . . . . . . . . . . . . . . . . . . . . 21
6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 20 6.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 21 6.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 21 6.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 22 6.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.1.6. XML . . . . . . . . . . . . . . . . . . . . . . . . . 23 6.1.6. XML . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2. Identification Properties . . . . . . . . . . . . . . . . 24 6.2. Identification Properties . . . . . . . . . . . . . . . . 25
6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26 6.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 26
6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 26 6.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 29 6.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 29 6.2.9. ANNIVERSARY . . . . . . . . . . . . . . . . . . . . . 30
6.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.2.10. SEX . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 30 6.3. Delivery Addressing Properties . . . . . . . . . . . . . . 31
6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 30 6.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 32
6.4. Communications Properties . . . . . . . . . . . . . . . . 32 6.4. Communications Properties . . . . . . . . . . . . . . . . 32
6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 33 6.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 34 6.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.5. Geographical Properties . . . . . . . . . . . . . . . . . 35 6.5. Geographical Properties . . . . . . . . . . . . . . . . . 35
6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 35 6.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 36 6.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.6. Organizational Properties . . . . . . . . . . . . . . . . 36 6.6. Organizational Properties . . . . . . . . . . . . . . . . 37
6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 36 6.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 37
6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 37 6.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 38 6.6.4. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 39 6.6.5. MEMBER . . . . . . . . . . . . . . . . . . . . . . . . 39
6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 40 6.6.6. RELATED . . . . . . . . . . . . . . . . . . . . . . . 40
6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 42 6.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 42
6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 42 6.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 42
6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 43
6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 43 6.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 44 6.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 44
6.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 45 6.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 45
6.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 46
skipping to change at page 5, line 7 skipping to change at page 5, line 7
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.1. Normative References . . . . . . . . . . . . . . . . . . . 69 12.1. Normative References . . . . . . . . . . . . . . . . . . . 69
12.2. Informative References . . . . . . . . . . . . . . . . . . 72 12.2. Informative References . . . . . . . . . . . . . . . . . . 72
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 72 Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 72
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 72 A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 72
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 73 A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 73
A.3. New Properties and Parameters . . . . . . . . . . . . . . 73 A.3. New Properties and Parameters . . . . . . . . . . . . . . 73
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 74 A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 74
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . 74 publication) . . . . . . . . . . . . . . . . . . . . 74
B.1. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 74 B.1. Changes in -11 . . . . . . . . . . . . . . . . . . . . . . 74
B.2. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 74 B.2. Changes in -10 . . . . . . . . . . . . . . . . . . . . . . 74
B.3. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 75 B.3. Changes in -09 . . . . . . . . . . . . . . . . . . . . . . 75
B.4. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 75 B.4. Changes in -08 . . . . . . . . . . . . . . . . . . . . . . 75
B.5. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 76 B.5. Changes in -07 . . . . . . . . . . . . . . . . . . . . . . 76
B.6. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 76 B.6. Changes in -06 . . . . . . . . . . . . . . . . . . . . . . 76
B.7. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 76 B.7. Changes in -05 . . . . . . . . . . . . . . . . . . . . . . 77
B.8. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 77 B.8. Changes in -04 . . . . . . . . . . . . . . . . . . . . . . 77
B.9. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 77 B.9. Changes in -03 . . . . . . . . . . . . . . . . . . . . . . 78
B.10. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 78 B.10. Changes in -02 . . . . . . . . . . . . . . . . . . . . . . 78
B.11. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 79 B.11. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 78
B.12. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 79
1. Introduction 1. Introduction
Electronic address books have become ubiquitous. Their increased Electronic address books have become ubiquitous. Their increased
presence on portable, connected devices as well as the diversity of presence on portable, connected devices as well as the diversity of
platforms exchanging contact data call for a standard. This memo platforms exchanging contact data call for a standard. This memo
defines the vCard format, which allows the capture and exchange of defines the vCard format, which allows the capture and exchange of
information normally stored within an address book or directory information normally stored within an address book or directory
application. application.
skipping to change at page 8, line 9 skipping to change at page 8, line 9
; procedure described above. ; procedure described above.
group = 1*(ALPHA / DIGIT / "-") group = 1*(ALPHA / DIGIT / "-")
name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME" name = "SOURCE" / "NAME" / "KIND" / "FN" / "N" / "NICKNAME"
/ "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "SEX" / "PHOTO" / "BDAY" / "DDAY" / "BIRTH" / "DEATH" / "SEX"
/ "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG" / "ADR" / "LABEL" / "TEL" / "EMAIL" / "IMPP" / "LANG"
/ "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER" / "TZ" / "GEO" / "TITLE" / "ROLE" / "LOGO" / "ORG" / "MEMBER"
/ "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV" / "RELATED" / "CATEGORIES" / "NOTE" / "PRODID" / "REV"
/ "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL" / "SORT-STRING" / "SOUND" / "UID" / "CLIENTPIDMAP" / "URL"
/ "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI" / "VERSION" / "CLASS" / "KEY" / "FBURL" / "CALADRURI"
/ "CALURI" / iana-token / x-name / "CALURI" / "XML" / iana-token / x-name
; Parsing of the param and value is based on the "name" as ; Parsing of the param and value is based on the "name" as
; defined in ABNF sections below. ; defined in ABNF sections below.
; Group and name are case-insensitive. ; Group and name are case-insensitive.
iana-token = 1*(ALPHA / DIGIT / "-") iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA ; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-") x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are ; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released ; reserved for experimental use, not intended for released
skipping to change at page 9, line 26 skipping to change at page 9, line 26
depending on the property cardinality. The general rule for encoding depending on the property cardinality. The general rule for encoding
multi-valued properties is to simply create a new content line for multi-valued properties is to simply create a new content line for
each value (including the property name). However, it should be each value (including the property name). However, it should be
noted that some value types support encoding multiple values in a noted that some value types support encoding multiple values in a
single content line by separating the values with a comma ",". This single content line by separating the values with a comma ",". This
approach has been taken for several of the content types defined approach has been taken for several of the content types defined
below (date, time, integer, float), for space-saving reasons. below (date, time, integer, float), for space-saving reasons.
3.3. Property Value Escaping 3.3. Property Value Escaping
A property instance may contain one or more values delimited by a Some properties may contain one or more values delimited by a COMMA
COMMA character (ASCII decimal 44). Therefore, a COMMA character in character (ASCII decimal 44). Therefore, a COMMA character in a
a value MUST be escaped with a BACKSLASH character (ASCII decimal value MUST be escaped with a BACKSLASH character (ASCII decimal 92),
92), even for properties that don't allow multiple instances (for even for properties that don't allow multiple instances (for
consistency). consistency).
Some properties (e.g. N and ADR) comprise multiple fields delimited Some properties (e.g. N and ADR) comprise multiple fields delimited
by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI- by a SEMI-COLON character (ASCII decimal 59). Therefore, a SEMI-
COLON in a field of such a "compound" property MUST be escaped with a COLON in a field of such a "compound" property MUST be escaped with a
BACKSLASH character. SEMI-COLON characters in non-compound BACKSLASH character. SEMI-COLON characters in non-compound
properties MUST NOT be escaped. properties MUST NOT be escaped.
Furthermore, some fields of compound properties may contain a list of Furthermore, some fields of compound properties may contain a list of
values delimited by a COMMA character. Therefore, a COMMA character values delimited by a COMMA character. Therefore, a COMMA character
in one of a field's values MUST be escaped with a BACKSLASH in one of a field's values MUST be escaped with a BACKSLASH
character, even for fields that don't allow multiple values (for character, even for fields that don't allow multiple values (for
consistency). Compound properties allowing multiple instances MUST consistency). Compound properties allowing multiple instances MUST
NOT be encoded in a single content line. NOT be encoded in a single content line.
Finally, newline (ASCII decimal 10) and backslash (ASCII decimal 92) Finally, BACKSLASH characters in values MUST be escaped with a
characters in values MUST be escaped by prefixing them with a BACKSLASH character. NEWLINE (ASCII decimal 10) characters in values
backslash character. MUST be encoded by two characters: a BACKSLASH followed by an 'n'
(ASCII decimal 110).
In all other cases, escaping MUST NOT be used. In all other cases, escaping MUST NOT be used.
3.4. Character Set 3.4. Character Set
The character set for vCard is UTF-8 as defined in [RFC3629]. There The character set for vCard is UTF-8 as defined in [RFC3629]. There
is no way to override this. is no way to override this.
4. Property Value Data Types 4. Property Value Data Types
skipping to change at page 15, line 43 skipping to change at page 15, line 43
"float" values can be specified using the comma-separated notation. "float" values can be specified using the comma-separated notation.
Examples: Examples:
20.30 20.30
1000000.0000001 1000000.0000001
1.333,3.14 1.333,3.14
4.7. BINARY 4.7. BINARY
"binary": The "binary" value type specifies that the type value is "binary": The "binary" value type specifies that the property value
inline, encoded binary data. This value type can be specified in the is inline, encoded binary data. This value type can be specified in
PHOTO, LOGO, SOUND, and KEY types. the PHOTO, LOGO, SOUND, and KEY types.
If inline encoded binary data is specified, the ENCODING type If inline encoded binary data is specified, the ENCODING type
parameter MUST be used to specify the encoding format. The binary parameter MUST be used to specify the encoding format. The binary
data MUST be encoded using the "B" encoding format. Long lines of data MUST be encoded using the "B" encoding format. Long lines of
encoded binary data SHOULD BE folded to 75 characters using the encoded binary data SHOULD BE folded to 75 characters using the
folding method defined in Section 3.1. folding method defined in Section 3.1.
4.8. LANGUAGE-TAG 4.8. LANGUAGE-TAG
"language-tag": A single language tag, as defined in [RFC5646]. "language-tag": A single language tag, as defined in [RFC5646].
skipping to change at page 16, line 23 skipping to change at page 16, line 23
property value. property value.
Property parameter values that contain the COLON (US-ASCII decimal Property parameter values that contain the COLON (US-ASCII decimal
58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44) 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
character separators MUST be specified as quoted-string text values. character separators MUST be specified as quoted-string text values.
Property parameter values MUST NOT contain the DQUOTE (US-ASCII Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted used as a delimiter for parameter values that contain restricted
characters or URI text. characters or URI text.
Property parameter values that are not in quoted strings are case
insensitive.
Applications MUST ignore x-param and iana-param values they don't Applications MUST ignore x-param and iana-param values they don't
recognize. recognize.
5.1. LANGUAGE 5.1. LANGUAGE
The "language" property parameter is used to identify data in The "language" property parameter is used to identify data in
multiple languages. There is no concept of "default" language, multiple languages. There is no concept of "default" language,
except as specified by any "Content-Language" MIME header parameter except as specified by any "Content-Language" MIME header parameter
that is present. The value of the "language" property parameter is a that is present. The value of the "language" property parameter is a
language tag as defined in Section 2 of [RFC5646]. language tag as defined in Section 2 of [RFC5646].
ABNF: ABNF:
language-param = "LANGUAGE=" Language-Tag language-param = "LANGUAGE=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 5646 ; Language-Tag is defined in section 2.1 of RFC 5646
Properties with different LANGUAGE parameters that represent the same
data count as 1 toward cardinality and MUST have the same PID value
if the PID parameter is used. This is because there is logically a
single property which is expressed in multiple languages.
Therefore, since BIRTH (Section 6.2.7) has cardinality (0,1), this
example would be legal:
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH;LANGUAGE=en:Quebec City
while these four would not:
BIRTH;PID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;PID=1;LANGUAGE=en:Quebec City
BIRTH;PID=1;LANGUAGE=fr:Ville de Quebec
BIRTH;PID=2;LANGUAGE=en:Quebec City
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH:Quebec City
BIRTH;LANGUAGE=fr:Ville de Quebec
BIRTH;LANGUAGE=en:Quebec City
BIRTH;LANGUAGE=en:Montreal
5.2. ENCODING 5.2. ENCODING
The "encoding" property parameter is used to specify an alternate The "encoding" property parameter is used to specify an alternate
encoding for a value. If the value contains a CRLF, it must be encoding for a value. If the value contains a CRLF, it must be
encoded, since CRLF is used to separate lines in the content-type encoded, since CRLF is used to separate lines in the content-type
itself. Currently, only the "b" encoding is supported. itself. Currently, only the "b" encoding is supported.
The "b" encoding can also be useful for binary values that are mixed The "b" encoding can also be useful for binary values that are mixed
with other text information in the body part (e.g., a certificate). with other text information in the body part (e.g., a certificate).
Using a per-value "b" encoding in this case leaves the other Using a per-value "b" encoding in this case leaves the other
skipping to change at page 23, line 29 skipping to change at page 24, line 14
Example: Example:
This represents someone named Jane Doe working in the marketing This represents someone named Jane Doe working in the marketing
department of the North American division of ABC Inc. department of the North American division of ABC Inc.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:individual KIND:individual
FN:Jane Doe FN:Jane Doe
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
END:VCARD END:VCARD
This represents the department itself, commonly known as ABC This represents the department itself, commonly known as ABC
Marketing. Marketing.
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
KIND:org KIND:org
FN:ABC Marketing FN:ABC Marketing
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
END:VCARD END:VCARD
6.1.6. XML 6.1.6. XML
Purpose: To include XML-encoded vCard data in a plain vCard. Purpose: To include extended XML-encoded vCard data in a plain
vCard.
Value type: A single text value. Value type: A single text value.
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The content of this property is an XML chunk. Its
default XML namespace is "urn:ietf:params:xml:ns:vcard-4.0". The
elements allowed at the root level of this chunk are those that
are allowed to be immediate children of the <vcard> element
defined in this document. The normal rules for extensibility
apply (i.e. things in unknown namespaces are ignored). The chunk
is subject to normal line folding and escaping, i.e. replace all
backslashes with "\\", then replace all newlines with "\n", then
fold long lines.
Support for this property is OPTIONAL. The XML syntax is
described in [I-D.ietf-vcarddav-vcardxml].
ABNF: Special notes: The content of this property is a single XML element
whose namespace MUST be explicitly specified using the xmlns
attribute and MUST NOT be the vCard 4 namespace
("urn:ietf:params:xml:ns:vcard-4.0"). The element is to be
interpreted as if it was contained in a <vcard> element, as
defined in [I-D.ietf-vcarddav-vcardxml].
XML-param = "" The fragment is subject to normal line folding and escaping, i.e.
XML-value = text replace all backslashes with "\\", then replace all newlines with
"\n", then fold long lines.
Example: The three following vCards are equivalent. Support for this property is OPTIONAL, but implementations of this
specification MUST preserve instances of this property when
propagating vCards.
<?xml version="1.0"?> See [I-D.ietf-vcarddav-vcardxml] for more information on the
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0"> intended use of this property.
<vcard>
<fn><text>John Doe</text></fn>
<email><text>jdoe@example.com</text></email>
</vcard>
</vcards>
BEGIN:VCARD ABNF:
VERSION:4.0
XML:<fn><text>John Doe>/text></fn>\n
<email><text>jdoe@example.com</text></email>
END:VCARD
BEGIN:VCARD XML-param = ""
VERSION:4.0 XML-value = text
FN:John Doe
EMAIL:jdoe@example.com
END:VCARD
6.2. Identification Properties 6.2. Identification Properties
These types are used to capture information associated with the These types are used to capture information associated with the
identification and naming of the person or resource associated with identification and naming of the person or resource associated with
the vCard. the vCard.
6.2.1. FN 6.2.1. FN
Purpose: To specify the formatted text corresponding to the name of Purpose: To specify the formatted text corresponding to the name of
skipping to change at page 33, line 11 skipping to change at page 33, line 25
Special notes: This property is based on the X.520 Telephone Number Special notes: This property is based on the X.520 Telephone Number
attribute. attribute.
The property can include the "PREF" parameter to indicate a The property can include the "PREF" parameter to indicate a
preferred-use telephone number. preferred-use telephone number.
The property can include the parameter "TYPE" to specify intended The property can include the parameter "TYPE" to specify intended
use for the telephone number. The TYPE parameter values can use for the telephone number. The TYPE parameter values can
include: "text" to indicate the telephone number supports text include: "text" to indicate the telephone number supports text
messages, "voice" to indicate a voice telephone number, "fax" to messages (SMS), "voice" to indicate a voice telephone number,
indicate a facsimile telephone number, "cell" to indicate a "fax" to indicate a facsimile telephone number, "cell" to indicate
cellular or mobile telephone number, "video" to indicate a video a cellular or mobile telephone number, "video" to indicate a video
conferencing telephone number, "pager" to indicate a paging device conferencing telephone number, "pager" to indicate a paging device
telephone number. The default type is "voice". These type telephone number, and "textphone" to indicate a telecommunication
device for the deaf. The default type is "voice". These type
parameter values can be specified as a parameter list (e.g., parameter values can be specified as a parameter list (e.g.,
"TYPE=text;TYPE=voice") or as a value list (e.g., "TYPE=text;TYPE=voice") or as a value list (e.g.,
"TYPE=text,voice"). The default can be overridden to another set "TYPE=text,voice"). The default can be overridden to another set
of values by specifying one or more alternate values. For of values by specifying one or more alternate values. For
example, the default TYPE of "voice" can be reset to a VOICE and example, the default TYPE of "voice" can be reset to a VOICE and
FAX telephone number by the value list "TYPE=voice,fax". FAX telephone number by the value list "TYPE=voice,fax".
ABNF: ABNF:
TEL-param = "VALUE=uri" / type-param / pid-param / pref-param TEL-param = "VALUE=uri" / type-param / pid-param / pref-param
skipping to change at page 36, line 9 skipping to change at page 36, line 20
Note that utc-offset values SHOULD NOT be used because the UTC Note that utc-offset values SHOULD NOT be used because the UTC
offset varies with time - not just because of the usual DST shifts offset varies with time - not just because of the usual DST shifts
that occur in may regions, but often entire regions will "re-base" that occur in may regions, but often entire regions will "re-base"
their offset entirely. The actual offset may be +/- 1 hour (or their offset entirely. The actual offset may be +/- 1 hour (or
perhaps a little more) than the one given. perhaps a little more) than the one given.
ABNF: ABNF:
TZ-param = "VALUE=" ("text" / "uri" / "utc-offset") TZ-param = "VALUE=" ("text" / "uri" / "utc-offset")
TZ-value = text / uri / utc-offset TZ-value = text / uri / utc-offset
; Value and parameter must match ; Value and parameter MUST match
TZ-param =/ pid-param / pref-param / type-param / any-param TZ-param =/ pid-param / pref-param / type-param / any-param
Examples: Examples:
TZ:Raleigh/North America TZ:Raleigh/North America
TZ;VALUE=utc-offset:-0500 TZ;VALUE=utc-offset:-0500
; Note: utc-offset format is NOT RECOMMENDED. ; Note: utc-offset format is NOT RECOMMENDED.
skipping to change at page 39, line 6 skipping to change at page 39, line 11
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
6.6.4. ORG 6.6.4. ORG
Purpose: To specify the organizational name and units associated Purpose: To specify the organizational name and units associated
with the vCard. with the vCard.
Value type: A single structured text value consisting of components Value type: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59). separated by the SEMI-COLON character (ASCII decimal 59).
Cardinality: (0,n) Cardinality: (0,n)
Special notes: The property is based on the X.520 Organization Name Special notes: The property is based on the X.520 Organization Name
and Organization Unit attributes. The property value is a and Organization Unit attributes. The property value is a
structured type consisting of the organization name, followed by structured type consisting of the organization name, followed by
zero or more levels of organizational unit names. zero or more levels of organizational unit names.
ABNF: ABNF:
ORG-param = "VALUE=text" / language-param / pid-param / pref-param ORG-param = "VALUE=text" / language-param / pid-param / pref-param
/ type-param / any-param / type-param / any-param
ORG-value = component *(";" component) ORG-value = component *(";" component)
component = "\\" / "\;" / "\n" / WSP / NON-ASCII component = "\\" / "\;" / "\n" / WSP / NON-ASCII
/ %x21-3A / %x3C-5B / %x5D-7E / %x21-3A / %x3C-5B / %x5D-7E
Example: A property value consisting of an organizational name, Example: A property value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name. organizational unit #1 name and organizational unit #2 name.
ORG:ABC\, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
6.6.5. MEMBER 6.6.5. MEMBER
Purpose: To include a member in the group this vCard represents. Purpose: To include a member in the group this vCard represents.
Value type: A single URI. It MAY refer to something other than a Value type: A single URI. It MAY refer to something other than a
vCard object. For example, an e-mail distribution list could vCard object. For example, an e-mail distribution list could
employ the "mailto" URI scheme for efficiency. employ the "mailto" URI scheme for efficiency.
Cardinality: (0,n) Cardinality: (0,n)
skipping to change at page 60, line 15 skipping to change at page 60, line 15
In addition, the following media types are known to have been used In addition, the following media types are known to have been used
to refer to vCard data. They should be considered deprecated in to refer to vCard data. They should be considered deprecated in
favor of text/vcard. favor of text/vcard.
* text/directory * text/directory
* text/directory; profile=vcard * text/directory; profile=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-10 Published specification: draft-ietf-vcarddav-vcardrev-11
Applications that use this media type: They are numerous, diverse, Applications that use this media type: They are numerous, diverse,
and include mail user agents, instant messaging clients, address and include mail user agents, instant messaging clients, address
book applications, directory servers, customer relationship book applications, directory servers, customer relationship
management software, etc. management software, etc.
Additional information: Additional information:
Magic number(s): Magic number(s):
skipping to change at page 69, line 25 skipping to change at page 69, line 25
The authors would like to thank Tim Howes, Mark Smith, and Frank The authors would like to thank Tim Howes, Mark Smith, and Frank
Dawson, the original authors of [RFC2425] and [RFC2426], as well as Dawson, the original authors of [RFC2425] and [RFC2426], as well as
the following individuals who have participated in the drafting, the following individuals who have participated in the drafting,
review and discussion of this memo: review and discussion of this memo:
Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil Aki Niemi, Andy Mabbett, Alexander Mayrhofer, Alexey Melnikov, Anil
Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie Srivastava, Barry Leiba, Ben Fortuna, Bernard Desruisseaux, Bernie
Hoeneisen, Caleb Richarson, Chris Bryant, Chris Newman, Cyrus Daboo, Hoeneisen, Caleb Richarson, Chris Bryant, Chris Newman, Cyrus Daboo,
Dan Brickley, Dan Mosedale, Dany Cauchie, Darryl Champagne, Dave Dan Brickley, Dan Mosedale, Dany Cauchie, Darryl Champagne, Dave
Thewlis, Filip Navara, Helge Hess, Jari Urpalainen, Javier Godoy, Thewlis, Filip Navara, Florian Zeitz, Helge Hess, Jari Urpalainen,
Jean-Luc Schellens, Joe Hildebrand, Jose Luis Gayosso, Joseph Smarr, Javier Godoy, Jean-Luc Schellens, Joe Hildebrand, Jose Luis Gayosso,
Julian Reschke, Kepeng Li, Kurt Zeilenga. Lisa Dusseault, Marc Joseph Smarr, Julian Reschke, Kepeng Li, Kurt Zeilenga. Lisa
Blanchet, Mark Paterson, Markus Lorenz, Mike Douglass, Nick Levinson, Dusseault, Marc Blanchet, Mark Paterson, Markus Lorenz, Mike
Peter K. Sheerin, Peter Mogensen, Peter Saint-Andre, Renato Iannella, Douglass, Nick Levinson, Peter K. Sheerin, Peter Mogensen, Peter
Sly Gryphon, Stephane Bortzmeyer, Tantek Celik, and Zoltan Ordogh. Saint-Andre, Renato Iannella, Sly Gryphon, Stephane Bortzmeyer,
Tantek Celik, and Zoltan Ordogh.
12. References 12. References
12.1. Normative References 12.1. Normative References
[CCITT.E163.1988] International Telephone and Telegraph [CCITT.E163.1988] International Telephone and Telegraph
Consultative Committee, "Numbering Plan Consultative Committee, "Numbering Plan
for the International Telephone for the International Telephone
Service", CCITT Recommendation E.163, Service", CCITT Recommendation E.163,
1988. 1988.
skipping to change at page 74, line 21 skipping to change at page 74, line 21
o The value of TEL is now a URI. o The value of TEL is now a URI.
o The AGENT property was replaced with a type of RELATED. o The AGENT property was replaced with a type of RELATED.
o Date and time values now only support the basic format. o Date and time values now only support the basic format.
Truncation is now supported. Truncation is now supported.
Appendix B. Change Log (to be removed by RFC Editor prior to Appendix B. Change Log (to be removed by RFC Editor prior to
publication) publication)
B.1. Changes in -10 B.1. Changes in -11
o Change "XML chunk" to "XML fragment".
o Cite W3C document containing definition of "fragment".
o Added "XML" to property name ABNF.
o Clarified newline escaping rule.
o Replaced one remaining "type" with "property".
o Removed case insensitivity of parameter values.
o XML property can now only contain one element that is not in the
vCard 4 namespace.
o Clarified interrelationship between LANGUAGE, cardinality, and
PID.
o Added "textphone" TEL type.
o Fixed quoting of comma in ORG examples.
B.2. Changes in -10
o Added component in SORT-STRING for sorting by given name. Fixed o Added component in SORT-STRING for sorting by given name. Fixed
and expanded the examples. and expanded the examples.
o Fixed KIND-value ABNF. o Fixed KIND-value ABNF.
o Fixed deprecated media type. o Fixed deprecated media type.
o Created the CALSCALE parameter. o Created the CALSCALE parameter.
o Strenghtened the stance on character set. o Strenghtened the stance on character set.
o Defined the Language-Tag ABNF. o Defined the Language-Tag ABNF.
o Made explicit the fact that IANA does not register templates. o Made explicit the fact that IANA does not register templates.
o Created the XML property. o Created the XML property.
o Added social networking examples to URL property. o Added social networking examples to URL property.
B.2. Changes in -09 B.3. Changes in -09
o Removed special meaning for groups. Removed the "work" and "home" o Removed special meaning for groups. Removed the "work" and "home"
groups. Removed the group registry. Re-introduced the "work" and groups. Removed the group registry. Re-introduced the "work" and
"home" TYPE parameter values. Applied the TYPE parameter to "home" TYPE parameter values. Applied the TYPE parameter to
properties which supported the "work" and "home" groups. properties which supported the "work" and "home" groups.
o Vendor namespace now uses private enterprise number in prefix. o Vendor namespace now uses private enterprise number in prefix.
o Added "thing" value for KIND property. o Added "thing" value for KIND property.
B.3. Changes in -08 B.4. Changes in -08
o Allow 1985 (year only) in date ABNF. o Allow 1985 (year only) in date ABNF.
o Fixed missing country in ADR example. o Fixed missing country in ADR example.
o Added the DATE-AND-OR-TIME value. o Added the DATE-AND-OR-TIME value.
o Made BDAY and DDAY use DATE-AND-OR-TIME. o Made BDAY and DDAY use DATE-AND-OR-TIME.
o Prefixed "param" and "value" production rules specific to o Prefixed "param" and "value" production rules specific to
skipping to change at page 75, line 28 skipping to change at page 76, line 5
o Replaced the GENDER property with the SEX property. o Replaced the GENDER property with the SEX property.
o Added the ANNIVERSARY property. o Added the ANNIVERSARY property.
o Added the "friend" and "spouse" types of RELATED. o Added the "friend" and "spouse" types of RELATED.
o TZ property now has text / uri value. o TZ property now has text / uri value.
o Refined the definitions of TITLE and ROLE. o Refined the definitions of TITLE and ROLE.
B.4. Changes in -07 B.5. Changes in -07
o PREF is now bounded. 100 is the maximum value. o PREF is now bounded. 100 is the maximum value.
o Added the "emergency" RELATED type. o Added the "emergency" RELATED type.
o Made GEO a URI. o Made GEO a URI.
o Added GEO and TZ parameters to ADR. o Added GEO and TZ parameters to ADR.
o Changed wording of "default" use of SOUND property. o Changed wording of "default" use of SOUND property.
skipping to change at page 76, line 5 skipping to change at page 76, line 27
o Completely reworked the date, time, and date-time grammars. o Completely reworked the date, time, and date-time grammars.
o Added the timestamp value type. o Added the timestamp value type.
o REV now has the timestamp value type. o REV now has the timestamp value type.
o Rewrote ABNF. o Rewrote ABNF.
o ORG can now have a single level. o ORG can now have a single level.
B.5. Changes in -06 B.6. Changes in -06
o Corrected omission of resetability to text value for RELATED. o Corrected omission of resetability to text value for RELATED.
o Let KEY value type be reset to a URI value. o Let KEY value type be reset to a URI value.
o ABNF fixes. o ABNF fixes.
o Made gender values extensible. o Made gender values extensible.
o Gave the PREF parameter a positive integer value. o Gave the PREF parameter a positive integer value.
skipping to change at page 76, line 44 skipping to change at page 77, line 19
o Removed TYPE parameter from EMAIL properties in examples. o Removed TYPE parameter from EMAIL properties in examples.
o Created the CLIENTPIDMAP property. o Created the CLIENTPIDMAP property.
o Changed PID value to a pair of small integers. o Changed PID value to a pair of small integers.
o Completely reworked synchronization mechanisms. o Completely reworked synchronization mechanisms.
o Created brand new synchronization example. o Created brand new synchronization example.
B.6. Changes in -05 B.7. Changes in -05
o Added multi PID value proposal. o Added multi PID value proposal.
B.7. Changes in -04 B.8. Changes in -04
o Added "location" value for KIND property. o Added "location" value for KIND property.
o Some fixes to ABNF. o Some fixes to ABNF.
o Moved "pref" from being a TYPE value to a parameter in its own o Moved "pref" from being a TYPE value to a parameter in its own
right. right.
o Removed the "work" and "home" TYPE values. o Removed the "work" and "home" TYPE values.
skipping to change at page 77, line 31 skipping to change at page 78, line 5
o Removed TYPE parameter from EMAIL and IMPP properties. o Removed TYPE parameter from EMAIL and IMPP properties.
o Replaced AGENT with a type of RELATED. o Replaced AGENT with a type of RELATED.
o Use example.org domain in URL example. o Use example.org domain in URL example.
o Created initial IANA table of values. o Created initial IANA table of values.
o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL. o Defined meaning of PUBLIC, PRIVATE, CONFIDENTIAL.
B.8. Changes in -03 B.9. Changes in -03
o Various changes to the synchronization mechanisms. o Various changes to the synchronization mechanisms.
o Allowed truncated format for dated. See issue #236. o Allowed truncated format for dated. See issue #236.
B.9. Changes in -02 B.10. Changes in -02
o Removed useless text in IMPP description. o Removed useless text in IMPP description.
o Added CalDAV-SCHED example to CALADRURI. o Added CalDAV-SCHED example to CALADRURI.
o Removed CAPURI property. o Removed CAPURI property.
o Dashes in dates and colons in times are now mandatory. o Dashes in dates and colons in times are now mandatory.
o Allow for dates such as 2008 and 2008-05 and times such as 07 and o Allow for dates such as 2008 and 2008-05 and times such as 07 and
skipping to change at page 78, line 23 skipping to change at page 78, line 44
o Changed the presence of UID and PID when synchronization is to be o Changed the presence of UID and PID when synchronization is to be
used from MUST to SHOULD. used from MUST to SHOULD.
o Added the RELATED (Section 6.6.6) property. o Added the RELATED (Section 6.6.6) property.
o Fixed many ABNF typos (issue #252). o Fixed many ABNF typos (issue #252).
o Changed formatting of ABNF comments to make them easier to read o Changed formatting of ABNF comments to make them easier to read
(issue #226). (issue #226).
B.10. Changes in -01 B.11. Changes in -01
o Merged [RFC2739] in. o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com. o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF. o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system. in the WGS 84 reference system.
skipping to change at page 79, line 5 skipping to change at page 79, line 25
o Added Section 7. o Added Section 7.
o Created IANA process for registering new parameters, value types, o Created IANA process for registering new parameters, value types,
and properties. and properties.
o Created the initial IANA registries. o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288. o Created vendor namespace based on text from RFC 4288.
B.11. Changes in -00 B.12. Changes in -00
o Name change because draft has been accepted as WG item. o Name change because draft has been accepted as WG item.
Otherwise, same as draft-resnick-vcarddav-vcardrev-01. Otherwise, same as draft-resnick-vcarddav-vcardrev-01.
o Removed reference to RFC 2234. o Removed reference to RFC 2234.
o Fixed errata from o Fixed errata from
http://www.rfc-editor.org/errata_search.php?rfc=2426. http://www.rfc-editor.org/errata_search.php?rfc=2426.
o Removed passage referring to RFC 2425 profiles. o Removed passage referring to RFC 2425 profiles.
 End of changes. 50 change blocks. 
112 lines changed or deleted 148 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/