draft-ietf-vcarddav-vcardrev-00.txt   draft-ietf-vcarddav-vcardrev-01.txt 
Network Working Group P. Resnick Network Working Group P. Resnick
Internet-Draft QUALCOMM Incorporated Internet-Draft QUALCOMM Incorporated
Obsoletes: 2425, 2426, 4770 S. Perreault Obsoletes: 2425, 2426, 4770 S. Perreault
(if approved) Viagenie (if approved) Viagenie
Intended status: Standards Track March 17, 2008 Updates: 2739 (if approved) April 9, 2008
Expires: September 18, 2008 Intended status: Standards Track
Expires: October 11, 2008
vCard Format Specification vCard Format Specification
draft-ietf-vcarddav-vcardrev-00 draft-ietf-vcarddav-vcardrev-01
Status of This Memo Status of This Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 37
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 18, 2008. This Internet-Draft will expire on October 11, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
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 an individual (e.g., exchanging a variety of information about an individual (e.g.,
formatted and structured name and delivery addresses, email address, formatted and structured name and delivery addresses, email address,
multiple telephone numbers, photograph, logo, audio clips, etc.). multiple telephone numbers, photograph, logo, audio clips, etc.).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 4 3. MIME Type Registration . . . . . . . . . . . . . . . . . . . . 5
4. vCard Format Specification . . . . . . . . . . . . . . . . . . 5 4. vCard Format Specification . . . . . . . . . . . . . . . . . . 6
4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 6 4.1. Line Delimiting and Folding . . . . . . . . . . . . . . . 7
4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 6 4.2. ABNF Format Definition . . . . . . . . . . . . . . . . . . 8
4.3. Value Types . . . . . . . . . . . . . . . . . . . . . . . 8 5. Property Value Data Types . . . . . . . . . . . . . . . . . . 10
4.4. Pre-defined Parameters . . . . . . . . . . . . . . . . . . 13 5.1. TEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 15 5.2. URI . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.1. General Properties . . . . . . . . . . . . . . . . . . . . 15 5.3. DATE, TIME, and DATE-TIME . . . . . . . . . . . . . . . . 13
5.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 15 5.4. BOOLEAN . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.5. INTEGER . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 16 5.6. FLOAT . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.7. BINARY . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.8. VCARD . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. Identification Properties . . . . . . . . . . . . . . . . 18 5.9. UTC-OFFSET . . . . . . . . . . . . . . . . . . . . . . . . 15
5.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6. Property Parameters . . . . . . . . . . . . . . . . . . . . . 15
5.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.1. LANGUAGE . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 19 6.2. ENCODING . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 19 6.3. VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.4. UID . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.5. TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 21 7. vCard Properties . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1. General Properties . . . . . . . . . . . . . . . . . . . . 18
5.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.1. BEGIN . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3. Delivery Addressing Properties . . . . . . . . . . . . . . 21 7.1.2. END . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.1.3. SOURCE . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 22 7.1.4. NAME . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4. Communications Properties . . . . . . . . . . . . . . . . 23 7.1.5. KIND . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.2. Identification Properties . . . . . . . . . . . . . . . . 21
5.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.1. FN . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.2.2. N . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.3. NICKNAME . . . . . . . . . . . . . . . . . . . . . . . 22
5.5. Geographical Properties . . . . . . . . . . . . . . . . . 25 7.2.4. PHOTO . . . . . . . . . . . . . . . . . . . . . . . . 22
5.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2.5. BDAY . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.2.6. DDAY . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.6. Organizational Properties . . . . . . . . . . . . . . . . 26 7.2.7. BIRTH . . . . . . . . . . . . . . . . . . . . . . . . 23
5.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 26 7.2.8. DEATH . . . . . . . . . . . . . . . . . . . . . . . . 23
5.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.2.9. GENDER . . . . . . . . . . . . . . . . . . . . . . . . 24
5.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.3. Delivery Addressing Properties . . . . . . . . . . . . . . 24
5.6.4. AGENT . . . . . . . . . . . . . . . . . . . . . . . . 28 7.3.1. ADR . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.6.5. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.3.2. LABEL . . . . . . . . . . . . . . . . . . . . . . . . 25
5.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 28 7.4. Communications Properties . . . . . . . . . . . . . . . . 25
5.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 29 7.4.1. TEL . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.4.2. EMAIL . . . . . . . . . . . . . . . . . . . . . . . . 26
5.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 29 7.4.3. IMPP . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.4.4. LANG . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 30 7.5. Geographical Properties . . . . . . . . . . . . . . . . . 28
5.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 31 7.5.1. TZ . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.5.2. GEO . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.6. Organizational Properties . . . . . . . . . . . . . . . . 29
5.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 32 7.6.1. TITLE . . . . . . . . . . . . . . . . . . . . . . . . 29
5.8. Security Properties . . . . . . . . . . . . . . . . . . . 33 7.6.2. ROLE . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 33 7.6.3. LOGO . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.6.4. AGENT . . . . . . . . . . . . . . . . . . . . . . . . 30
5.9. Extended Properties and Parameters . . . . . . . . . . . . 34 7.6.5. ORG . . . . . . . . . . . . . . . . . . . . . . . . . 31
6. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 34 7.7. Explanatory Properties . . . . . . . . . . . . . . . . . . 31
7. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 44 7.7.1. CATEGORIES . . . . . . . . . . . . . . . . . . . . . . 31
8. Security Considerations . . . . . . . . . . . . . . . . . . . 45 7.7.2. NOTE . . . . . . . . . . . . . . . . . . . . . . . . . 32
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45 7.7.3. PRODID . . . . . . . . . . . . . . . . . . . . . . . . 32
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45 7.7.4. REV . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.1. Normative References . . . . . . . . . . . . . . . . . . . 45 7.7.5. SORT-STRING . . . . . . . . . . . . . . . . . . . . . 33
10.2. Informative References . . . . . . . . . . . . . . . . . . 47 7.7.6. SOUND . . . . . . . . . . . . . . . . . . . . . . . . 33
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 48 7.7.7. UID . . . . . . . . . . . . . . . . . . . . . . . . . 34
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 48 7.7.8. URL . . . . . . . . . . . . . . . . . . . . . . . . . 35
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 48 7.7.9. VERSION . . . . . . . . . . . . . . . . . . . . . . . 35
A.3. New Properties and Parameters . . . . . . . . . . . . . . 48 7.8. Security Properties . . . . . . . . . . . . . . . . . . . 35
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 49 7.8.1. CLASS . . . . . . . . . . . . . . . . . . . . . . . . 35
7.8.2. KEY . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.9. Calendar Properties . . . . . . . . . . . . . . . . . . . 36
7.9.1. FBURL . . . . . . . . . . . . . . . . . . . . . . . . 36
7.9.2. CALADRURI . . . . . . . . . . . . . . . . . . . . . . 37
7.9.3. CAPURI . . . . . . . . . . . . . . . . . . . . . . . . 37
7.9.4. CALURI . . . . . . . . . . . . . . . . . . . . . . . . 37
7.10. Extended Properties and Parameters . . . . . . . . . . . . 38
8. Synchronization . . . . . . . . . . . . . . . . . . . . . . . 38
8.1. Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 38
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 39
9. Formal Grammar . . . . . . . . . . . . . . . . . . . . . . . . 40
10. Example: Authors' vCards . . . . . . . . . . . . . . . . . . . 49
11. Security Considerations . . . . . . . . . . . . . . . . . . . 49
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
12.1. Registering New vCard Elements . . . . . . . . . . . . . . 50
12.1.1. Registration Procedure . . . . . . . . . . . . . . . . 50
12.1.2. Vendor Namespace . . . . . . . . . . . . . . . . . . . 51
12.1.3. Registration Template for Properties . . . . . . . . . 51
12.1.4. Registration Template for Parameters . . . . . . . . . 52
12.1.5. Registration Template for Value Data Types . . . . . . 52
12.1.6. Registration Template for Values . . . . . . . . . . . 52
12.2. Initial vCard Elements Registries . . . . . . . . . . . . 53
12.2.1. Properties Registry . . . . . . . . . . . . . . . . . 53
12.2.2. Parameters Registry . . . . . . . . . . . . . . . . . 55
12.2.3. Value Data Types Registry . . . . . . . . . . . . . . 55
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 55
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 56
14.1. Normative References . . . . . . . . . . . . . . . . . . . 56
14.2. Informative References . . . . . . . . . . . . . . . . . . 58
Appendix A. Differences from RFCs 2425 and 2426 . . . . . . . . . 58
A.1. New Structure . . . . . . . . . . . . . . . . . . . . . . 58
A.2. Removed Features . . . . . . . . . . . . . . . . . . . . . 59
A.3. New Properties and Parameters . . . . . . . . . . . . . . 59
A.4. Other Changes . . . . . . . . . . . . . . . . . . . . . . 59
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) . . . . . . . . . . . . . . . . . . . . 49 publication) . . . . . . . . . . . . . . . . . . . . 59
B.1. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 49 B.1. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 59
B.2. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
Note: This draft contains much of the same text as 2425 and 2426 Note: This draft contains much of the same text as 2425 and 2426
which may not be correct. Those two RFCs have been merged and the which may not be correct. Those two RFCs have been merged and the
structure of this draft is what's new. Some vCard-specific structure of this draft is what's new. Some vCard-specific
suggestions have been added, but for the most part this is still very suggestions have been added, but for the most part this is still very
open. But we'd like to get feedback on the structure mostly so that open. But we'd like to get feedback on the structure mostly so that
it may be fixed. it may be fixed.
skipping to change at page 4, line 45 skipping to change at page 5, line 45
Subtype name: vcard Subtype name: vcard
Required parameters: none Required parameters: none
Optional parameters: charset Optional parameters: charset
Encoding considerations: The "charset" MIME parameter is interpreted Encoding considerations: The "charset" MIME parameter is interpreted
as defined in [RFC2046], section 4.1.2. If it is omitted, the as defined in [RFC2046], section 4.1.2. If it is omitted, the
default encoding is UTF-8 as defined in [RFC3629]. default encoding is UTF-8 as defined in [RFC3629].
Security considerations: See Section 8. Security considerations: See Section 11.
Interoperability considerations: The text/vcard media type is Interoperability considerations: The text/vcard media type is
intended to identify vCard data of any version. There are older intended to identify vCard data of any version. There are older
specifications of vCard [RFC2426][oldreference_VCARD] still in specifications of vCard [RFC2426][oldreference_VCARD] still in
common use. While these formats are similar, they are not common use. While these formats are similar, they are not
strictly compatible. In general, it is necessary to inspect the strictly compatible. In general, it is necessary to inspect the
value of the VERSION property (see Section 5.7.9) for identifying value of the VERSION property (see Section 7.7.9) for identifying
the standard to which a given vCard object conforms. the standard to which a given vCard object conforms.
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; type=vcard * text/directory; type=vcard
* text/x-vcard * text/x-vcard
Published specification: draft-ietf-vcarddav-vcardrev-00 Published specification: draft-ietf-vcarddav-vcardrev-01
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 6, line 11 skipping to change at page 7, line 11
contains contact information, typically pertaining to a single contains contact information, typically pertaining to a single
contact or group of contacts. The content consists of one or more contact or group of contacts. The content consists of one or more
lines in the format given below. lines in the format given below.
4.1. Line Delimiting and Folding 4.1. Line Delimiting and Folding
Individual lines within vCard are delimited by the [RFC2822] line Individual lines within vCard are delimited by the [RFC2822] line
break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII
decimal 10). Long logical lines of text can be split into a decimal 10). Long logical lines of text can be split into a
multiple-physical-line representation using the following folding multiple-physical-line representation using the following folding
technique. After generating a content line, lines longer than 75 technique. Content lines SHOULD be folded to a maximum width of 75
characters SHOULD be folded. octets. Multi-octet characters MUST remain contiguous. The
rationale for this folding process can be found in [RFC2822], Section
2.1.1.
A logical line MAY be continued on the next physical line anywhere A logical line MAY be continued on the next physical line anywhere
between two characters by inserting a CRLF immediately followed by a between two characters by inserting a CRLF immediately followed by a
single white space character (space, ASCII decimal 32, or horizontal single white space character (space, ASCII decimal 32, or horizontal
tab, ASCII decimal 9). At least one character must be present on the tab, ASCII decimal 9). At least one character must be present on the
folded line. Any sequence of CRLF followed immediately by a single folded line. Any sequence of CRLF followed immediately by a single
white space character is ignored (removed) when processing the white space character is ignored (removed) when processing the
content type. For example the line: content type. For example the line:
DESCRIPTION:This is a long description that exists on a long line. DESCRIPTION:This is a long description that exists on a long line.
skipping to change at page 6, line 42 skipping to change at page 7, line 44
tion that exists o tion that exists o
n a long line. n a long line.
The process of moving from this folded multiple-line representation The process of moving from this folded multiple-line representation
of a property definition to its single line representation is called of a property definition to its single line representation is called
unfolding. Unfolding is accomplished by regarding CRLF immediately unfolding. Unfolding is accomplished by regarding CRLF immediately
followed by a white space character (namely HTAB ASCII decimal 9 or followed by a white space character (namely HTAB ASCII decimal 9 or
SPACE ASCII decimal 32) as equivalent to no characters at all (i.e., SPACE ASCII decimal 32) as equivalent to no characters at all (i.e.,
the CRLF and single white space character are removed). the CRLF and single white space character are removed).
Note: It is possible for very simple implementations to generate
improperly folded lines in the middle of a UTF-8 multi-octet
sequence. For this reason, implementations SHOULD unfold lines in
such a way as to properly restore the original sequence.
Folding is done after any content encoding of a type value. Folding is done after any content encoding of a type value.
Unfolding is done before any decoding of a type value in a content Unfolding is done before any decoding of a type value in a content
line. line.
4.2. ABNF Format Definition 4.2. ABNF Format Definition
The following ABNF uses the notation of [RFC5234], which also defines The following ABNF uses the notation of [RFC5234], which also defines
CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. After the unfolding of CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. After the unfolding of
any folded lines as described above, the syntax for a line of this any folded lines as described above, the syntax for a line of this
content type is as follows: content type is as follows:
skipping to change at page 7, line 34 skipping to change at page 9, line 34
param-name = x-name / iana-token param-name = x-name / iana-token
param-value = ptext / quoted-string param-value = ptext / quoted-string
ptext = *SAFE-CHAR ptext = *SAFE-CHAR
value = *VALUE-CHAR value = *VALUE-CHAR
/ valuespec ; valuespec defined in section 5.8.4 / valuespec ; valuespec defined in section 5.8.4
contentline = name *(";" param) ":" value CRLF quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure
; described above.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described above.
name = x-name / iana-token
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
param = param-name "=" param-value *("," param-value) NON-ASCII = %x80-FF
param-name = x-name / iana-token ; use restricted by charset parameter
; on outer MIME object (UTF-8 preferred)
param-value = ptext / quoted-string QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
ptext = *SAFE-CHAR SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":", ","
value = *VALUE-CHAR VALUE-CHAR = WSP / VCHAR / NON-ASCII
/ valuespec ; valuespec defined in section 5.8.4 ; any textual character
A line that begins with a white space character is a continuation of A line that begins with a white space character is a continuation of
the previous line, as described above. The white space character and the previous line, as described above. The white space character and
immediately preceeding CRLF should be discarded when reconstructing immediately preceeding CRLF should be discarded when reconstructing
the original line. Note that this line-folding convention differs the original line. Note that this line-folding convention differs
from that found in [RFC2822], in that the sequence <CRLF><WSP> found from that found in [RFC2822], in that the sequence <CRLF><WSP> found
anywhere in the content indicates a continued line and should be anywhere in the content indicates a continued line and should be
removed. removed.
Property names and parameter names are case insensitive (e.g., the Property names and parameter names are case insensitive (e.g., the
skipping to change at page 8, line 35 skipping to change at page 10, line 22
Each property defined in a vCard instance MAY have multiple values. Each property defined in a vCard instance MAY have multiple values.
The general rule for encoding multi-valued properties is to simply The general rule for encoding multi-valued properties is to simply
create a new content line for each value (including the property create a new content line for each value (including the property
name). However, it should be noted that some value types support name). However, it should be noted that some value types support
encoding multiple values in a single content line by separating the encoding multiple values in a single content line by separating the
values with a comma ",". This approach has been taken for several of values with a comma ",". This approach has been taken for several of
the content types defined below (date, time, integer, float), for the content types defined below (date, time, integer, float), for
space-saving reasons. space-saving reasons.
4.3. Value Types 5. Property Value Data Types
Lists of values are delimited by a list delimiter, specified by the Lists of values are delimited by a list delimiter, specified by the
COMMA character (ASCII decimal 44). A COMMA character in a value COMMA character (ASCII decimal 44). A COMMA character in a value
MUST be escaped with a BACKSLASH character (ASCII decimal 92). MUST be escaped with a BACKSLASH character (ASCII decimal 92).
Compound type values are delimited by a field delimiter, specified by Compound type values are delimited by a field delimiter, specified by
the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a
component of a compound property value MUST be escaped with a component of a compound property value MUST be escaped with a
BACKSLASH character (ASCII decimal 92). BACKSLASH character (ASCII decimal 92).
skipping to change at page 9, line 10 skipping to change at page 10, line 45
valuespec = text-list valuespec = text-list
/ URI ; from Appendix A of [RFC3986] / URI ; from Appendix A of [RFC3986]
/ date-list / date-list
/ time-list / time-list
/ date-time-list / date-time-list
/ boolean / boolean
/ integer-list / integer-list
/ float-list / float-list
/ binary / binary
/ vcard / vcard
/ phone-number
/ utc-offset / utc-offset
/ iana-valuespec / iana-valuespec
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR) text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n" TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline> / <any VALUE-CHAR except , or \ or newline>
; Backslashes, newlines, and commas must be encoded. ; Backslashes, newlines, and commas must be encoded.
; \n or \N can be used to encode a newline. ; \n or \N can be used to encode a newline.
skipping to change at page 9, line 43 skipping to change at page 11, line 29
float-list = float *("," float) float-list = float *("," float)
float = [sign] 1*DIGIT ["." 1*DIGIT] float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-" sign = "+" / "-"
binary = <A "B" binary encoded string as defined by [RFC2047].> binary = <A "B" binary encoded string as defined by [RFC2047].>
vcard = <vCard data encoded as specified below.> vcard = <vCard data encoded as specified below.>
phone-number = <A telephone number as defined in
[CCITT.E163.1988] and [CCITT.X121.1988]>
date = date-fullyear ["-"] date-month ["-"] date-mday date = date-fullyear ["-"] date-month ["-"] date-mday
date-fullyear = 4 DIGIT date-fullyear = 4 DIGIT
date-month = 2 DIGIT ;01-12 date-month = 2 DIGIT ;01-12
date-mday = 2 DIGIT ;01-28, 01-29, 01-30, 01-31 date-mday = 2 DIGIT ;01-28, 01-29, 01-30, 01-31
;based on month/year ;based on month/year
time = time-hour [":"] time-minute [":"] time-second [time-secfrac] time = time-hour [":"] time-minute [":"] time-second [time-secfrac]
[time-zone] [time-zone]
time-hour = 2 DIGIT ;00-23 time-hour = 2 DIGIT ;00-23
time-minute = 2 DIGIT ;00-59 time-minute = 2 DIGIT ;00-59
skipping to change at page 10, line 21 skipping to change at page 12, line 4
time-minute = 2 DIGIT ;00-59 time-minute = 2 DIGIT ;00-59
time-second = 2 DIGIT ;00-60 (leap second) time-second = 2 DIGIT ;00-60 (leap second)
time-secfrac = "," 1*DIGIT time-secfrac = "," 1*DIGIT
time-zone = "Z" / time-numzone time-zone = "Z" / time-numzone
time-numzome = sign time-hour [":"] time-minute time-numzome = sign time-hour [":"] time-minute
utc-offset = ("+" / "-") time-hour ":" time-minute utc-offset = ("+" / "-") time-hour ":" time-minute
iana-valuespec = <a publicly-defined valuetype format, registered iana-valuespec = <a publicly-defined valuetype format, registered
with IANA, as defined in section 15 of this with IANA, as defined in section 15 of this
document> document>
Some specific notes on the value types and formats: 5.1. TEXT
"text": The "text" value type should be used to identify values that "text": The "text" value type should be used to identify values that
contain human-readable text. The character set in which the text is contain human-readable text. The character set in which the text is
represented is controlled by the "charset" MIME type parameter. Note represented is controlled by the "charset" MIME type parameter. Note
that there is no way to override this parameter on a per-property that there is no way to override this parameter on a per-property
basis. As for the language, it is controlled by the "language" basis. As for the language, it is controlled by the "language"
property parameter defined in Section 4.4. property parameter defined in Section 6.1.
Examples for "text": Examples for "text":
this is a text value this is a text value
this is one value,this is another this is one value,this is another
this is a single value\, with a comma encoded this is a single value\, with a comma encoded
A formatted text line break in a text value type MUST be represented A formatted text line break in a text value type MUST be represented
as the character sequence backslash (ASCII decimal 92) followed by a as the character sequence backslash (ASCII decimal 92) followed by a
Latin small letter n (ASCII decimal 110) or a Latin capital letter N Latin small letter n (ASCII decimal 110) or a Latin capital letter N
skipping to change at page 11, line 20 skipping to change at page 12, line 45
could be represented as: could be represented as:
DESCRIPTION:Mythical Manager\nHyjinx Software Division\n DESCRIPTION:Mythical Manager\nHyjinx Software Division\n
BabsCo\, Inc.\n BabsCo\, Inc.\n
demonstrating the \n literal formatted line break technique, the demonstrating the \n literal formatted line break technique, the
CRLF-followed-by-space line folding technique, and the backslash CRLF-followed-by-space line folding technique, and the backslash
escape technique. escape technique.
5.2. URI
"uri": The "uri" value type should be used to identify values that "uri": The "uri" value type should be used to identify values that
are referenced by a URI (including a Content-ID URI), instead of are referenced by a URI (including a Content-ID URI), instead of
encoded in-line. These value references might be used if the value encoded in-line. These value references might be used if the value
is too large, or otherwise undesirable to include directly. The is too large, or otherwise undesirable to include directly. The
format for the URI is as defined in [RFC3986]. Note that the value format for the URI is as defined in [RFC3986]. Note that the value
of a property of type "uri" is what the URI points to, not the URI of a property of type "uri" is what the URI points to, not the URI
itself. itself.
Examples for "uri": Examples for "uri":
http://www.foobar.com/my/picture.jpg http://www.example.com/my/picture.jpg
ldap://ldap.foobar.com/cn=babs%20jensen ldap://ldap.example.com/cn=babs%20jensen
5.3. DATE, TIME, and DATE-TIME
"date", "time", and "date-time": Each of these value types is based "date", "time", and "date-time": Each of these value types is based
on a subset of the definitions in [ISO.8601.1988] standard. Multiple on a subset of the definitions in [ISO.8601.1988] standard. Multiple
"date" and "time" values can be specified using the comma-separated "date" and "time" values can be specified using the comma-separated
notation. notation.
Examples for "date": Examples for "date":
1985-04-12 1985-04-12
1996-08-05,1996-11-11 1996-08-05,1996-11-11
skipping to change at page 12, line 4 skipping to change at page 13, line 33
19850412 19850412
Examples for "time": Examples for "time":
10:22:00 10:22:00
102200 102200
10:22:00.33 10:22:00.33
10:22:00.33Z 10:22:00.33Z
10:22:33,11:22:00 10:22:33,11:22:00
10:22:00-08:00 10:22:00-08:00
Examples for "date-time": Examples for "date-time":
1996-10-22T14:00:00Z 1996-10-22T14:00:00Z
1996-08-11T12:34:56Z 1996-08-11T12:34:56Z
19960811T123456Z 19960811T123456Z
1996-10-22T14:00:00Z,1996-08-11T12:34:56Z 1996-10-22T14:00:00Z,1996-08-11T12:34:56Z
5.4. BOOLEAN
"boolean": The "boolean" value type is used to express boolen values. "boolean": The "boolean" value type is used to express boolen values.
These values are case insensitive. These values are case insensitive.
Examples: Examples:
TRUE TRUE
false false
True True
5.5. INTEGER
"integer": The "integer" value type is used to express signed "integer": The "integer" value type is used to express signed
integers in decimal format. If sign is not specified, the value is integers in decimal format. If sign is not specified, the value is
assumed positive "+". Multiple "integer" values can be specified assumed positive "+". Multiple "integer" values can be specified
using the comma-separated notation. using the comma-separated notation.
Examples: Examples:
1234567890 1234567890
-1234556790 -1234556790
+1234556790,432109876 +1234556790,432109876
5.6. FLOAT
"float": The "float" value type is used to express real numbers. If "float": The "float" value type is used to express real numbers. If
sign is not specified, the value is assumed positive "+". Multiple sign is not specified, the value is assumed positive "+". Multiple
"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
5.7. BINARY
"binary": The "binary" value type specifies that the type value is "binary": The "binary" value type specifies that the type value is
inline, encoded binary data. This value type can be specified in the inline, encoded binary data. This value type can be specified in the
PHOTO, LOGO, SOUND, and KEY types. 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 4.1. folding method defined in Section 4.1.
5.8. VCARD
"vcard": The "vcard" value type specifies that the type value is "vcard": The "vcard" value type specifies that the type value is
another vCard. This value type can be specified in the AGENT another vCard. This value type can be specified in the AGENT
property. The value type is defined by this specification. Since property. The value type is defined by this specification. Since
each of the type declarations within the vcard value type are being each of the type declarations within the vcard value type are being
specified within a text value themselves, they MUST be terminated specified within a text value themselves, they MUST be terminated
with the backslash escape sequence "\n" or "\N", instead of the with the backslash escape sequence "\n" or "\N", instead of the
normal newline character sequence CRLF. In addition, any COMMA normal newline character sequence CRLF. In addition, any COMMA
character (ASCII decimal 44), SEMI-COLON character (ASCII decimal 59) character (ASCII decimal 44), SEMI-COLON character (ASCII decimal 59)
and COLON character (ASCII decimal 58) MUST be escaped with the and COLON character (ASCII decimal 58) MUST be escaped with the
BACKSLASH character (ASCII decimal 92). For example, with the AGENT BACKSLASH character (ASCII decimal 92). For example, with the AGENT
property a value would be specified as: property a value would be specified as:
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:tel:+1-919-555-7878\n
TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\n TITLE:Area Administrator\, Assistant\n EMAIL\;TYPE=INTERN\n
ET:jfriday@host.com\nEND:VCARD\n ET:jfriday@example.com\nEND:VCARD\n
"phone-number": The "phone-number" value type specifies that the type 5.9. UTC-OFFSET
value is a telephone number. This value type can be specified in the
TEL type. The value type is a text value that has the special
semantics of a telephone number as defined in [CCITT.E163.1988] and
[CCITT.X121.1988].
"utc-offset": The "utc-offset" value type specifies that the type "utc-offset": The "utc-offset" value type specifies that the type
value is a signed offset from UTC. This value type can be specified value is a signed offset from UTC. This value type can be specified
in the TZ type. in the TZ type.
The value type is an offset from Coordinated Universal Time (UTC). The value type is an offset from Coordinated Universal Time (UTC).
It is specified as a positive or negative difference in units of It is specified as a positive or negative difference in units of
hours and minutes (e.g., +hh:mm). The time is specified as a 24-hour hours and minutes (e.g., +hh:mm). The time is specified as a 24-hour
clock. Hour values are from 00 to 23, and minute values are from 00 clock. Hour values are from 00 to 23, and minute values are from 00
to 59. Hour and minutes are 2-digits with high order zeroes required to 59. Hour and minutes are 2-digits with high order zeroes required
to maintain digit count. The extended format for ISO 8601 UTC to maintain digit count. The extended format for ISO 8601 UTC
offsets MUST be used. The extended format makes use of a colon offsets MUST be used. The extended format makes use of a colon
character as a separator of the hour and minute text fields. character as a separator of the hour and minute text fields.
4.4. Pre-defined Parameters 6. Property Parameters
The following parameters are defined for general use. A property can have attributes associated with it. These "property
parameters" contain meta-information about the property or the
property value.
predefined-param = encodingparm Property parameter values that contain the COLON (US-ASCII decimal
/ valuetypeparm 58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
/ languageparm character separators MUST be specified as quoted-string text values.
Property parameter values MUST NOT contain the DQUOTE (US-ASCII
decimal 22) character. The DQUOTE (US-ASCII decimal 22) character is
used as a delimiter for parameter values that contain restricted
characters or URI text. For example:
encodingparm = "encoding" "=" encodingtype FN;UID="urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6":Jane Doe
encodingtype = "b" ; from [RFC2047] Property parameter values that are not in quoted strings are case
/ iana-token ; registered as described in insensitive.
; section 15 of this document
predefined-param = encodingparm The general property parameters defined by this memo are defined by
/ valuetypeparm the following notation:
/ languageparm
encodingparm = "encoding" "=" encodingtype vcardparameter = encodingparam
/ valuetypeparam
/ languageparam
/ uidparam
encodingparam = "encoding" "=" encodingtype
encodingtype = "b" ; from [RFC2047] encodingtype = "b" ; from [RFC2047]
/ iana-token ; registered as described in / iana-token ; registered as described in
; section 15 of this document ; section 15 of this document
predefined-param = encodingparm valuetypeparam = "value" "=" valuetype
/ valuetypeparm
/ languageparm
encodingparm = "encoding" "=" encodingtype
encodingtype = "b" ; from [RFC2047] valuetype = "uri" ; URI from Appendix A of [RFC3986]
/ "text"
/ "date"
/ "time"
/ "date-time" ; date time
/ "integer"
/ "boolean"
/ "float"
/ x-name
/ iana-token ; registered as described in / iana-token ; registered as described in
; section 15 of this document ; section 15 of this document
languageparam = "language" "=" Language-Tag
; Language-Tag is defined in section 2.1 of RFC 4646
uidparam = "uid" "=" URI ; from Appendix A of [RFC3986]
Applications MUST ignore x-param and iana-param value they don't
recognize.
6.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 [RFC4646]. language tag as defined in Section 2 of [RFC4646].
6.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
information in a more readable form. The encoded base 64 value can information in a more readable form. The encoded base 64 value can
be split across multiple physical lines by using the line folding be split across multiple physical lines by using the line folding
skipping to change at page 15, line 21 skipping to change at page 17, line 28
The Content-Transfer-Encoding and the encodings of individual The Content-Transfer-Encoding and the encodings of individual
properties given by the "encoding" property parameter are independent properties given by the "encoding" property parameter are independent
of one another. When encoding a text/vcard body part for of one another. When encoding a text/vcard body part for
transmission, individual property encodings are performed first, then transmission, individual property encodings are performed first, then
the entire body part is encoded according to the Content-Transfer- the entire body part is encoded according to the Content-Transfer-
Encoding. When decoding a text/vcard body part, the Content- Encoding. When decoding a text/vcard body part, the Content-
Transfer-Encoding is decoded first, and then any individual Transfer-Encoding is decoded first, and then any individual
properties with an "encoding" property parameter are decoded. properties with an "encoding" property parameter are decoded.
6.3. VALUE
The "value" parameter is optional, and is used to identify the value The "value" parameter is optional, and is used to identify the value
type (data type) and format of the value. The use of these type (data type) and format of the value. The use of these
predefined formats is encouraged even if the value parameter is not predefined formats is encouraged even if the value parameter is not
explicity used. By defining a standard set of value types and their explicity used. By defining a standard set of value types and their
formats, existing parsing and processing code can be leveraged. The formats, existing parsing and processing code can be leveraged. The
predefined data type values MUST NOT be repeated in COMMA separated predefined data type values MUST NOT be repeated in COMMA separated
value lists except within the N, NICKNAME, ADR and CATEGORIES value lists except within the N, NICKNAME, ADR and CATEGORIES
properties. properties.
Including the value type explicitly as part of each property provides Including the value type explicitly as part of each property provides
an extra hint to keep parsing simple and support more generalized an extra hint to keep parsing simple and support more generalized
applications. For example a search engine would not have to know the applications. For example a search engine would not have to know the
particular value types for all of the items for which it is particular value types for all of the items for which it is
searching. Because the value type is explicit in the definition, the searching. Because the value type is explicit in the definition, the
search engine could look for dates in any item type and provide search engine could look for dates in any item type and provide
results that can still be interpreted. results that can still be interpreted.
5. vCard Properties 6.4. UID
The "uid" parameter is used to uniquely identify the property. It
plays a role analogous to the UID property (Section 7.7.7) on a per-
property instead of per-vCard basis. It MUST NOT appear more than
once in a given property, and MUST be present if synchronization is
to be used. See Section 8.
6.5. TYPE
The "type" parameter has multiple, different uses. In general, it is
a way of specifying class characteristics of the associated property.
Most of the time, its value is a comma-separated subset of a pre-
defined enumeration. In this document, the following properties make
use of this parameter: PHOTO, ADR, LABEL, TEL, EMAIL, IMPP, LOGO,
SOUND, and KEY.
7. vCard Properties
What follows is an enumeration of the standard vCard properties. What follows is an enumeration of the standard vCard properties.
5.1. General Properties 7.1. General Properties
5.1.1. BEGIN 7.1.1. BEGIN
Purpose: To denote the beginning of a syntactic entity within a Purpose: To denote the beginning of a syntactic entity within a
text/vcard content-type. text/vcard content-type.
Value type: text Value type: text
Special notes: The content entity MUST begin with the BEGIN property Special notes: The content entity MUST begin with the BEGIN property
with a value of "VCARD". with a value of "VCARD".
The BEGIN type is used in conjunction with the END type to delimit The BEGIN property is used in conjunction with the END property to
an entity containing a related set of properties within an text/ delimit an entity containing a related set of properties within an
vcard content-type. This construct can be used instead of or in text/vcard content-type. This construct can be used instead of or
addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
Example: Example:
BEGIN:VCARD BEGIN:VCARD
5.1.2. END 7.1.2. END
Purpose: To denote the end of a syntactic entity within a text/vcard Purpose: To denote the end of a syntactic entity within a text/vcard
content-type. content-type.
Value type: text Value type: text
Special notes: The content entity MUST end with the END type with a Special notes: The content entity MUST end with the END type with a
value of "VCARD". value of "VCARD".
The END type is used in conjunction with the BEGIN type to delimit The END property is used in conjunction with the BEGIN property to
an entity containing a related set of properties within an text/ delimit an entity containing a related set of properties within an
vcard content-type. This construct can be used instead of or in text/vcard content-type. This construct can be used instead of or
addition to wrapping separate sets of information inside in addition to wrapping separate sets of information inside
additional MIME headers. It is provided for applications that additional MIME headers. It is provided for applications that
wish to define content that can contain multiple entities within wish to define content that can contain multiple entities within
the same text/vcard content-type or to define content that can be the same text/vcard content-type or to define content that can be
identifiable outside of a MIME environment. identifiable outside of a MIME environment.
Example: Example:
END:VCARD END:VCARD
5.1.3. SOURCE 7.1.3. SOURCE
Purpose: To identify the source of directory information contained Purpose: To identify the source of directory information contained
in the content type. in the content type.
Value type: uri Value type: uri
Special notes: The SOURCE property is used to provide the means by Special notes: The SOURCE property is used to provide the means by
which applications knowledgable in the given directory service which applications knowledgable in the given directory service
protocol can obtain additional or more up-to-date information from protocol can obtain additional or more up-to-date information from
the directory service. It contains a URI as defined in [RFC3986] the directory service. It contains a URI as defined in [RFC3986]
and/or other information referencing the vCard to which the and/or other information referencing the vCard to which the
information pertains. When directory information is available information pertains. When directory information is available
from more than one source, the sending entity can pick what it from more than one source, the sending entity can pick what it
considers to be the best source, or multiple SOURCE properties can considers to be the best source, or multiple SOURCE properties can
be included. be included.
skipping to change at page 17, line 16 skipping to change at page 19, line 42
protocol can obtain additional or more up-to-date information from protocol can obtain additional or more up-to-date information from
the directory service. It contains a URI as defined in [RFC3986] the directory service. It contains a URI as defined in [RFC3986]
and/or other information referencing the vCard to which the and/or other information referencing the vCard to which the
information pertains. When directory information is available information pertains. When directory information is available
from more than one source, the sending entity can pick what it from more than one source, the sending entity can pick what it
considers to be the best source, or multiple SOURCE properties can considers to be the best source, or multiple SOURCE properties can
be included. be included.
Examples: Examples:
SOURCE:ldap://ldap.host/cn=Babs%20Jensen,%20o=Babsco,%20c=US SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US
SOURCE:http://directory.example.com/addressbooks/jdoe/ SOURCE:http://directory.example.com/addressbooks/jdoe/
Jean%20Dupont.vcf Jean%20Dupont.vcf
5.1.4. NAME 7.1.4. NAME
Purpose: To identify the displayable name of the directory entity to Purpose: To identify the displayable name of the directory entity to
which information in the vCard pertains. which information in the vCard pertains.
Value type: text Value type: text
Special notes: The NAME property is used to convey the display name Special notes: The NAME property is used to convey the display name
of the entity to which the directory information pertains. Its of the entity to which the directory information pertains. Its
value is the displayable, presentation text associated with the value is the displayable, presentation text associated with the
source for the vCard, as specified in the SOURCE property. source for the vCard, as specified in the SOURCE property.
Example: Example:
NAME:Babs Jensen's Contact Information NAME:Babs Jensen's Contact Information
5.1.5. KIND 7.1.5. KIND
Purpose: To specify the kind of object the vCard represents. Purpose: To specify the kind of object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: The value may be one of: "individual" for a single Special notes: The value may be one of: "individual" for a single
person, "group" for a group of people, "org" for an organization, person, "group" for a group of people, "org" for an organization,
an x-name or an iana-token. If this property is absent, an x-name or an iana-token. If this property is absent,
"individual" MUST be assumed as default. "individual" MUST be assumed as default.
skipping to change at page 18, line 25 skipping to change at page 21, line 5
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
5.2. Identification Properties 7.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.
5.2.1. FN 7.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
the object the vCard represents. the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: This property is based on the semantics of the X.520 Special notes: This property is based on the semantics of the X.520
Common Name attribute. The property MUST be present in the vCard Common Name attribute. The property MUST be present in the vCard
object. object.
Example: Example:
FN:Mr. John Q. Public\, Esq. FN:Mr. John Q. Public\, Esq.
5.2.2. N 7.2.2. N
Purpose: To specify the components of the name of the object the Purpose: To specify the components of the name of the object the
vCard represents. vCard represents.
Value type: A single structured text value. Each component can have Value type: A single structured text value. Each component can have
multiple values. multiple values.
Special note: The structured type value corresponds, in sequence, to Special note: The structured property value corresponds, in
the Family Name, Given Name, Additional Names, Honorific Prefixes, sequence, to the Family Name, Given Name, Additional Names,
and Honorific Suffixes. The text components are separated by the Honorific Prefixes, and Honorific Suffixes. The text components
SEMI-COLON character (ASCII decimal 59). Individual text are separated by the SEMI-COLON character (ASCII decimal 59).
components can include multiple text values (e.g., multiple Individual text components can include multiple text values (e.g.,
Additional Names) separated by the COMMA character (ASCII decimal multiple Additional Names) separated by the COMMA character (ASCII
44). This type is based on the semantics of the X.520 individual decimal 44). This property is based on the semantics of the X.520
name attributes. The property SHOULD be present in the vCard individual name attributes. The property SHOULD be present in the
object when the name of the object the vCard represents follows vCard object when the name of the object the vCard represents
the X.520 model. follows the X.520 model.
Examples: Examples:
N:Public;John;Quinlan;Mr.;Esq. N:Public;John;Quinlan;Mr.;Esq.
N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P. N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
5.2.3. NICKNAME 7.2.3. NICKNAME
Purpose: To specify the text corresponding to the nickname of the Purpose: To specify the text corresponding to the nickname of the
object the vCard represents. object the vCard represents.
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Special note: The nickname is the descriptive name given instead of Special note: The nickname is the descriptive name given instead of
or in addition to the one belonging to a person, place, or thing. or in addition to the one belonging to a person, place, or thing.
It can also be used to specify a familiar form of a proper name It can also be used to specify a familiar form of a proper name
specified by the FN or N types. specified by the FN or N properties.
Examples: Examples:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
5.2.4. PHOTO 7.2.4. PHOTO
Purpose: To specify an image or photograph information that Purpose: To specify an image or photograph information that
annotates some aspect of the object the vCard represents. annotates some aspect of the object the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding is value is referenced by a URI value, then the default encoding is
used and no explicit ENCODING parameter is needed. used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
skipping to change at page 20, line 17 skipping to change at page 22, line 46
a value outside of this MIME entity. a value outside of this MIME entity.
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
Example: Example:
PHOTO;VALUE=uri:http://www.abc.com/pub/photos PHOTO;VALUE=uri:http://www.example.com/pub/photos
/jqpublic.gif /jqpublic.gif
PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo PHOTO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKo
ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv ZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENv
bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi bW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbi
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
5.2.5. BDAY 7.2.5. BDAY
Purpose: To specify the birth date of the object the vCard Purpose: To specify the birth date of the object the vCard
represents. represents.
Value type: The default is a single date value. It can also be Value type: The default is a single date value. It can also be
reset to a single date-time or text value. reset to a single date-time or text value.
Examples: Examples:
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00Z BDAY:1953-10-15T23:10:00Z
BDAY;VALUE=text:circa 1800 BDAY;VALUE=text:circa 1800
5.2.6. DDAY 7.2.6. DDAY
Purpose: To specify the date of death of the object the vCard Purpose: To specify the date of death of the object the vCard
represents. represents.
Value type: The default is a single date value. It can also be Value type: The default is a single date value. It can also be
reset to a single date-time or text value. reset to a single date-time or text value.
5.2.7. BIRTH 7.2.7. BIRTH
Purpose: To specify the place of birth of the object the vCard Purpose: To specify the place of birth of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Example: Example:
BIRTH:Babies'R'Us Hospital BIRTH:Babies'R'Us Hospital
5.2.8. DEATH 7.2.8. DEATH
Purpose: To specify the place of death of the object the vCard Purpose: To specify the place of death of the object the vCard
represents. represents.
Value type: A single text value. Value type: A single text value.
Example: Example:
DEATH:Aboard the Titanic\, near Newfoundland DEATH:Aboard the Titanic\, near Newfoundland
5.2.9. GENDER 7.2.9. GENDER
Purpose: To specify the gender of the object the vCard represents. Purpose: To specify the gender of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: The value "M" stands for male while "F" stands for Special notes: The value "M" stands for male while "F" stands for
female. female.
Example: Example:
GENDER:F GENDER:F
5.3. Delivery Addressing Properties 7.3. Delivery Addressing Properties
These types are concerned with information related to the delivery These types are concerned with information related to the delivery
addressing or label for the vCard object. addressing or label for the vCard object.
5.3.1. ADR 7.3.1. ADR
Purpose: To specify the components of the delivery address for the Purpose: To specify the components of the delivery address for the
vCard object. vCard object.
Value type: A single structured text value, separated by the SEMI- Value type: A single structured text value, separated by the SEMI-
COLON character (ASCII decimal 59). COLON character (ASCII decimal 59).
Special notes: The structured type value consists of a sequence of Special notes: The structured type value consists of a sequence of
address components. The component values MUST be specified in address components. The component values MUST be specified in
their corresponding position. The structured type value their corresponding position. The structured type value
skipping to change at page 22, line 39 skipping to change at page 25, line 13
parameter list (i.e., "TYPE=home;TYPE=pref") or as a value list parameter list (i.e., "TYPE=home;TYPE=pref") or as a value list
(i.e., "TYPE=home,pref"). This type is based on semantics of the (i.e., "TYPE=home,pref"). This type is based on semantics of the
X.520 geographical and postal addressing attributes. The default X.520 geographical and postal addressing attributes. The default
is "TYPE=work". is "TYPE=work".
Example: In this example the post office box and the extended address Example: In this example the post office box and the extended address
are absent. are absent.
ADR;TYPE=home:;;123 Main Street;Any Town;CA;91921-1234 ADR;TYPE=home:;;123 Main Street;Any Town;CA;91921-1234
5.3.2. LABEL 7.3.2. LABEL
Purpose: To specify the formatted text corresponding to delivery Purpose: To specify the formatted text corresponding to delivery
address of the object the vCard represents. address of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
type can include the type parameter "TYPE" to specify delivery type can include the type parameter "TYPE" to specify delivery
label type. The TYPE parameter values can include "home" to label type. The TYPE parameter values can include "home" to
skipping to change at page 23, line 4 skipping to change at page 25, line 27
Value type: A single text value. Value type: A single text value.
Special notes: The property value is formatted text that can be used Special notes: The property value is formatted text that can be used
to present a delivery address label for the vCard object. The to present a delivery address label for the vCard object. The
type can include the type parameter "TYPE" to specify delivery type can include the type parameter "TYPE" to specify delivery
label type. The TYPE parameter values can include "home" to label type. The TYPE parameter values can include "home" to
indicate a delivery label for a residence; "work" to indicate indicate a delivery label for a residence; "work" to indicate
delivery label for a place of work; and "pref" to indicate the delivery label for a place of work; and "pref" to indicate the
preferred delivery label when more than one label is specified. preferred delivery label when more than one label is specified.
These type parameter values can be specified as a parameter list These type parameter values can be specified as a parameter list
(i.e., "TYPE=home;TYPE=pref") or as a value list (i.e., (i.e., "TYPE=home;TYPE=pref") or as a value list (i.e.,
"TYPE=home,pref"). The default is "TYPE=work". "TYPE=home,pref"). The default is "TYPE=work".
Example: A multi-line address label. Example: A multi-line address label.
LABEL;TYPE=home:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n LABEL;TYPE=home:Mr.John Q. Public\, Esq.\nMail Drop: TNE QB\n
123 Main Street\nAny Town\, CA 91921-1234\nU.S.A. 123 Main Street\nAny Town\, CA 91921-1234\nU.S.A.
5.4. Communications Properties 7.4. Communications Properties
These properties are concerned with information associated with the These properties are concerned with information associated with the
way communications with the object the vCard represents are carried way communications with the object the vCard represents are carried
out. out.
5.4.1. TEL 7.4.1. TEL
Purpose: To specify the telephone number for telephony communication Purpose: To specify the telephone number for telephony communication
with the object the vCard represents. with the object the vCard represents.
Value type: A single phone-number value. Value type: A single URI value. It is expected that the URI scheme
will be "tel", as specified in [RFC3966], but other schemes MAY be
used.
Special notes: The value of this property is specified in a Special notes: This property is based on the X.520 Telephone Number
canonical form in order to specify an unambiguous representation attribute.
of the globally unique telephone endpoint. This property is based
on the X.500 Telephone Number attribute.
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: "home" to indicate a telephone number associated with a include: "home" to indicate a telephone number associated with a
residence, "msg" to indicate the telephone number has voice residence, "msg" to indicate the telephone number has voice
messaging support, "work" to indicate a telephone number messaging support, "work" to indicate a telephone number
associated with a place of work, "pref" to indicate a preferred- associated with a place of work, "pref" to indicate a preferred-
use telephone number, "voice" to indicate a voice telephone use telephone number, "voice" to indicate a voice telephone
number, "fax" to indicate a facsimile telephone number, "cell" to number, "fax" to indicate a facsimile telephone number, "cell" to
indicate a cellular telephone number, "video" to indicate a video indicate a cellular telephone number, "video" to indicate a video
skipping to change at page 24, line 8 skipping to change at page 26, line 33
type is "voice". These type parameter values can be specified as type is "voice". These type parameter values can be specified as
a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
(i.e., "TYPE=work,voice"). The default can be overridden to (i.e., "TYPE=work,voice"). The default can be overridden to
another set of values by specifying one or more alternate values. another set of values by specifying one or more alternate values.
For example, the default TYPE of "voice" can be reset to a WORK For example, the default TYPE of "voice" can be reset to a WORK
and HOME, VOICE and FAX telephone number by the value list and HOME, VOICE and FAX telephone number by the value list
"TYPE=work,home,voice,fax". "TYPE=work,home,voice,fax".
Example: Example:
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234 TEL;TYPE=work,voice,pref,msg:tel:+1-555-555-5555;ext=5555
TEL;TYPE=home:tel:+33-01-23-45-67
5.4.2. EMAIL 7.4.2. EMAIL
Purpose: To specify the electronic mail address for communication Purpose: To specify the electronic mail address for communication
with the object the vCard represents. with the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: The type can include the type parameter "TYPE" to Special notes: The type can include the type parameter "TYPE" to
specify the format or preference of the electronic mail address. specify the format or preference of the electronic mail address.
The TYPE parameter values can include: "internet" to indicate an The TYPE parameter values can include: "internet" to indicate an
Internet addressing type, "x400" to indicate a X.400 addressing Internet addressing type, "x400" to indicate a X.400 addressing
type, "uri" to indicate a URI useable for electronic type, "uri" to indicate a URI useable for electronic
communication, "home" to indicate an address associated with a communication, "home" to indicate an address associated with a
residence, "work" to indicate an address associated with a place residence, "work" to indicate an address associated with a place
of work, or "pref" to indicate a preferred-use email address when of work, or "pref" to indicate a preferred-use email address when
more than one is specified. Another IANA registered address type more than one is specified. Another IANA registered address type
can also be specified. The default email type is "internet". A can also be specified. The default email type is "internet". A
non-standard value can also be specified. non-standard value can also be specified.
Type example: Type example:
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com EMAIL;TYPE=internet:jqpublic@xyz.example.com
EMAIL;TYPE=internet,pref:jane_doe@abc.com EMAIL;TYPE=internet,pref:jane_doe@example.com
EMAIL;TYPE=uri,work:http://example.com/contact.php EMAIL;TYPE=uri,work:http://example.com/contact.php
5.4.3. IMPP 7.4.3. IMPP
Purpose: To specify the URI for instant messaging and presence Purpose: To specify the URI for instant messaging and presence
protocol communications with the object the vCard represents. protocol communications with the object the vCard represents.
Value type: A single URI. The type of the URI indicates the Value type: A single URI. The type of the URI indicates the
protocol that can be used for this contact. protocol that can be used for this contact.
Special notes: The property may include the type parameter "TYPE" to Special notes: The property may include the type parameter "TYPE" to
specify an intended use for the URI. The TYPE parameter values specify an intended use for the URI. The TYPE parameter values
include one or more of the following: include one or more of the following:
skipping to change at page 25, line 15 skipping to change at page 27, line 40
* An indication of the location of a device associated with this * An indication of the location of a device associated with this
URI. Values can be "home", "work", or "mobile". URI. Values can be "home", "work", or "mobile".
* The value "pref" indicates this is a preferred address and has * The value "pref" indicates this is a preferred address and has
the same semantics as the "pref" value in a TEL property. the same semantics as the "pref" value in a TEL property.
Example: Example:
IMPP;TYPE=personal,pref:xmpp:alice@example.com IMPP;TYPE=personal,pref:xmpp:alice@example.com
5.4.4. LANG 7.4.4. LANG
Purpose: To specify the language(s) that may be used for contacting Purpose: To specify the language(s) that may be used for contacting
the individual associated with the vCard. the individual associated with the vCard.
Value type: A list of text values. Value type: A list of text values.
Special notes: The list is to be interpreted as defined in Special notes: The list is to be interpreted as defined in
[RFC2616], Section 14.4, i.e. as the value of an Accept-Language [RFC2616], Section 14.4, i.e. as the value of an Accept-Language
HTTP header. This lets one specify preference among languages. HTTP header. This lets one specify preference among languages.
Note that any SEMI-COLON character (ASCII decimal 59) must be Note that any SEMI-COLON character (ASCII decimal 59) must be
escaped. escaped.
Example: Example:
LANG:fr,en\;q=0.9 LANG:fr,en\;q=0.9
5.5. Geographical Properties 7.5. Geographical Properties
These properties are concerned with information associated with These properties are concerned with information associated with
geographical positions or regions associated with the object the geographical positions or regions associated with the object the
vCard represents. vCard represents.
5.5.1. TZ 7.5.1. TZ
Purpose: To specify information related to the time zone of the Purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
Value type: The default is a single utc-offset value. It can also Value type: The default is a single utc-offset value. It can also
be reset to a single text value. be reset to a single text value.
Special notes: The type value consists of a single value. Special notes: The type value consists of a single value.
Type examples: Type examples:
TZ:-05:00 TZ:-05:00
TZ;VALUE=text:-05:00; EST; Raleigh/North America TZ;VALUE=text:-05:00; EST; Raleigh/North America
;This example has a single value, not a structure text value. ;This example has a single value, not a structure text value.
5.5.2. GEO 7.5.2. GEO
Purpose: To specify information related to the global positioning of Purpose: To specify information related to the global positioning of
the object the vCard represents. the object the vCard represents.
Value type: A single structured value consisting of two float values Value type: A single structured value consisting of two float values
separated by the SEMI-COLON character (ASCII decimal 59). separated by the SEMI-COLON character (ASCII decimal 59).
Special notes: This property specifies information related to the Special notes: This property specifies information related to the
global position of the object associated with the vCard. The global position of the object associated with the vCard. The
value specifies latitude and longitude, in that order (i.e., "LAT value specifies latitude and longitude, in that order (i.e., "LAT
LON" ordering). The longitude represents the location east and LON" ordering). The longitude represents the location east and
west of the prime meridian as a positive or negative real number, west of the prime meridian as a positive or negative real number,
respectively. The latitude represents the location north and respectively. The latitude represents the location north and
south of the equator as a positive or negative real number, south of the equator as a positive or negative real number,
respectively. The longitude and latitude values MUST be specified respectively. The longitude and latitude values MUST be expressed
as decimal degrees and should be specified to six decimal places. in the [WGS84] reference system. They MUST be specified as
decimal degrees and should be specified to six decimal places.
This will allow for granularity within a meter of the geographical This will allow for granularity within a meter of the geographical
position. The text components are separated by the SEMI-COLON position. The text components are separated by the SEMI-COLON
character (ASCII decimal 59). The simple formula for converting character (ASCII decimal 59). The simple formula for converting
degrees-minutes-seconds into decimal degrees is: degrees-minutes-seconds into decimal degrees is:
decimal = degrees + minutes/60 + seconds/3600. decimal = degrees + minutes/60 + seconds/3600.
Example: Example:
GEO:37.386013;-122.082932 GEO:37.386013;-122.082932
5.6. Organizational Properties 7.6. Organizational Properties
These properties are concerned with information associated with These properties are concerned with information associated with
characteristics of the organization or organizational units of the characteristics of the organization or organizational units of the
object the vCard represents. object the vCard represents.
5.6.1. TITLE 7.6.1. TITLE
Purpose: To specify the job title, functional position or function Purpose: To specify the job title, functional position or function
of the object the vCard represents. of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: This property is based on the X.520 Title attribute. Special notes: This property is based on the X.520 Title attribute.
Example: Example:
TITLE:Director\, Research and Development TITLE:Director\, Research and Development
5.6.2. ROLE 7.6.2. ROLE
Purpose: To specify information concerning the role, occupation, or Purpose: To specify information concerning the role, occupation, or
business category of the object the vCard represents. business category of the object the vCard represents.
Value type: A single text value. Value type: A single text value.
Special notes: This property is based on the X.520 Business Category Special notes: This property is based on the X.520 Business Category
explanatory attribute. This property is included as an explanatory attribute. This property is included as an
organizational type to avoid confusion with the semantics of the organizational type to avoid confusion with the semantics of the
TITLE property and incorrect usage of that property when the TITLE property and incorrect usage of that property when the
semantics of this property is intended. semantics of this property is intended.
Example: Example:
ROLE:Programmer ROLE:Programmer
5.6.3. LOGO 7.6.3. LOGO
Purpose: To specify a graphic image of a logo associated with the Purpose: To specify a graphic image of a logo associated with the
object the vCard represents. object the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of value is referenced by a URI value, then the default encoding of
8bit is used and no explicit ENCODING parameter is needed. 8bit is used and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary value. It can Value type: A single value. The default is binary value. It can
skipping to change at page 27, line 46 skipping to change at page 30, line 27
a value outside of this MIME entity. a value outside of this MIME entity.
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the graphic image format type. The TYPE parameter value specify the graphic image format type. The TYPE parameter value
MUST be an image media type as specified in [RFC4288]. The full MUST be an image media type as specified in [RFC4288]. The full
media type name, including the "image/" prefix, should be used. media type name, including the "image/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
Example: Example:
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.example.com/pub/logos/abccorp.jpg
LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ LOGO;ENCODING=b;TYPE=image/jpeg:MIICajCCAdOgAwIBAgICBEUwDQYJKoZ
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
5.6.4. AGENT 7.6.4. AGENT
Purpose: To specify information about another person who will act on Purpose: To specify information about another person who will act on
behalf of the individual or resource associated with the vCard. behalf of the individual or resource associated with the vCard.
Value type: The default is a single vcard value. It can also be Value type: The default is a single vcard value. It can also be
reset to either a single text or uri value. The text value can be reset to either a single text or uri value. The text value can be
used to specify textual information. The uri value can be used to used to specify textual information. The uri value can be used to
specify information outside of this MIME entity. specify information outside of this MIME entity.
Special notes: This property typically is used to specify an area Special notes: This property typically is used to specify an area
administrator, assistant, or secretary for the individual administrator, assistant, or secretary for the individual
associated with the vCard. A key characteristic of the AGENT associated with the vCard. A key characteristic of the AGENT
property is that it represents somebody or something that is property is that it represents somebody or something that is
separately addressable. separately addressable.
Example: Example:
AGENT;VALUE=uri: AGENT;VALUE=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555- CID:JQPUBLIC.part3.960129T083020.xyzMail@example.com
1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n
5.6.5. ORG AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:tel:+1-919-555-
1234\nEMAIL\;INTERNET:sthomas@example.com\nEND:VCARD\n
7.6.5. 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 the SEMI-COLON character (ASCII decimal 59).
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
one or more levels of organizational unit names. one or more levels of organizational unit names.
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
5.7. Explanatory Properties 7.7. Explanatory Properties
These properties are concerned with additional explanations, such as These properties are concerned with additional explanations, such as
that related to informational notes or revisions specific to the that related to informational notes or revisions specific to the
vCard. vCard.
5.7.1. CATEGORIES 7.7.1. CATEGORIES
Purpose: To specify application category information about the Purpose: To specify application category information about the
vCard. vCard.
Value type: One or more text values separated by a COMMA character Value type: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Example: Example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
5.7.2. NOTE 7.7.2. NOTE
Purpose: To specify supplemental information or a comment that is Purpose: To specify supplemental information or a comment that is
associated with the vCard. associated with the vCard.
Value type: A single text value. Value type: A single text value.
Special notes: The property is based on the X.520 Description Special notes: The property is based on the X.520 Description
attribute. attribute.
Example: Example:
NOTE:This fax number is operational 0800 to 1715 NOTE:This fax number is operational 0800 to 1715
EST\, Mon-Fri. EST\, Mon-Fri.
5.7.3. PRODID 7.7.3. PRODID
Purpose: To specify the identifier for the product that created the Purpose: To specify the identifier for the product that created the
vCard object. vCard object.
Type value: A single text value. Type value: A single text value.
Special notes: Implementations SHOULD use a method such as that Special notes: Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in [ISO9070] or for specified for Formal Public Identifiers in [ISO9070] or for
Universal Resource Names in [RFC3406] to assure that the text Universal Resource Names in [RFC3406] to assure that the text
value is unique. value is unique.
Example: Example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
5.7.4. REV 7.7.4. REV
Purpose: To specify revision information about the current vCard. Purpose: To specify revision information about the current vCard.
Value type: The default is a single date-time value. Can also be Value type: The default is a single date-time value. Can also be
reset to a single date value. reset to a single date value.
Special notes: The value distinguishes the current revision of the Special notes: The value distinguishes the current revision of the
information in this vCard for other renditions of the information. information in this vCard for other renditions of the information.
Example: Example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
REV:1997-11-15 REV:1997-11-15
5.7.5. SORT-STRING 7.7.5. SORT-STRING
Purpose: To specify the family name or given name text to be used Purpose: To specify the family name or given name text to be used
for national-language-specific sorting of the FN and N types. for national-language-specific sorting of the FN and N types.
Value type: A single text value. Value type: A single text value.
Special notes: The sort string is used to provide family name or Special notes: The sort string is used to provide family name or
given name text that is to be used in locale- or national- given name text that is to be used in locale- or national-
language- specific sorting of the formatted name and structured language- specific sorting of the formatted name and structured
name types. Without this information, sorting algorithms could name types. Without this information, sorting algorithms could
skipping to change at page 31, line 25 skipping to change at page 33, line 43
SORT-STRING:Koura SORT-STRING:Koura
FN:Oscar del Pozo FN:Oscar del Pozo
N:del Pozo Triscon;Oscar N:del Pozo Triscon;Oscar
SORT-STRING:Pozo SORT-STRING:Pozo
FN:Chistine d'Aboville FN:Chistine d'Aboville
N:d'Aboville;Christine N:d'Aboville;Christine
SORT-STRING:Aboville SORT-STRING:Aboville
5.7.6. SOUND 7.7.6. SOUND
Purpose: To specify a digital sound content information that Purpose: To specify a digital sound content information that
annotates some aspect of the vCard. By default this property is annotates some aspect of the vCard. By default this property is
used to specify the proper pronunciation of the name property used to specify the proper pronunciation of the name property
value of the vCard. value of the vCard.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of value is referenced by a URI value, then the default encoding of
8bit is used and no explicit ENCODING parameter is needed. 8bit is used and no explicit ENCODING parameter is needed.
skipping to change at page 32, line 6 skipping to change at page 34, line 23
Special notes: This property SHOULD include the parameter "TYPE" to Special notes: This property SHOULD include the parameter "TYPE" to
specify the audio format type. The TYPE parameter value MUST be specify the audio format type. The TYPE parameter value MUST be
an audio media type as specified in [RFC4288]. The full media an audio media type as specified in [RFC4288]. The full media
type name, including the "audio/" prefix, should be used. type name, including the "audio/" prefix, should be used.
However, implementations SHOULD be able to handle bare subtypes. However, implementations SHOULD be able to handle bare subtypes.
Example: Example:
SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;TYPE=audio/basic;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com 19960229T080000.xyzMail@example.com
SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK SOUND;TYPE=audio/basic;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJK
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
5.7.7. UID 7.7.7. UID
Purpose: To specify a value that represents a globally unique Purpose: To specify a value that represents a globally unique
identifier corresponding to the individual or resource associated identifier corresponding to the individual or resource associated
with the vCard. with the vCard.
Value type: A single text value. Value type: A single URI value.
Special notes: The type is used to uniquely identify the object that Special notes: The type is used to uniquely identify the object that
the vCard represents. the vCard represents. The "uuid" URN namespace defined in
[RFC4122] is particularly well-suited to this task, but other URI
schemes MAY be used.
The type can include the type parameter "TYPE" to specify the format This property MUST NOT appear more than once in a given vCard, and
of the identifier. The TYPE parameter value should be an IANA MUST be present if synchronization is to be used. See Section 8.
registered identifier format. The value can also be a non-standard
format. The UID parameter MUST NOT be applied to this property.
Example: Example:
UID:19950401-080045-40000F192713-0052 UID:urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
5.7.8. URL 7.7.8. URL
Purpose: To specify a uniform resource locator associated with the Purpose: To specify a uniform resource locator associated with the
object that the vCard refers to. object that the vCard refers to.
Value type: A single uri value. Value type: A single uri value.
Example: Example:
URL:http://www.swbyps.restaurant.french/~chezchic.html URL:http://www.swbyps.restaurant.french/~chezchic.html
5.7.9. VERSION 7.7.9. VERSION
Purpose: To specify the version of the vCard specification used to Purpose: To specify the version of the vCard specification used to
format this vCard. format this vCard.
Value type: A single text value. Value type: A single text value.
Special notes: The property MUST be present in the vCard object. Special notes: The property MUST be present in the vCard object.
The value MUST be "4.0" if the vCard corresponds to this The value MUST be "4.0" if the vCard corresponds to this
specification. specification.
Example: Example:
VERSION:4.0 VERSION:4.0
5.8. Security Properties 7.8. Security Properties
These properties are concerned with the security of communication These properties are concerned with the security of communication
pathways or access to the vCard. pathways or access to the vCard.
5.8.1. CLASS 7.8.1. CLASS
Purpose: To specify the access classification for a vCard object. Purpose: To specify the access classification for a vCard object.
Value type: A single text value. Value type: A single text value.
Special notes: An access classification is only one component of the Special notes: An access classification is only one component of the
general security model for a directory service. The general security model for a directory service. The
classification attribute provides a method of capturing the intent classification attribute provides a method of capturing the intent
of the owner for general access to information described by the of the owner for general access to information described by the
vCard object. vCard object.
Examples: Examples:
CLASS:PUBLIC CLASS:PUBLIC
CLASS:PRIVATE CLASS:PRIVATE
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
5.8.2. KEY 7.8.2. KEY
Purpose: To specify a public key or authentication certificate Purpose: To specify a public key or authentication certificate
associated with the object that the vCard represents. associated with the object that the vCard represents.
Encoding: The encoding MUST be reset to "b" using the ENCODING Encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the parameter in order to specify inline, encoded binary data. If the
value is a text value, then the default encoding of 8bit is used value is a text value, then the default encoding of 8bit is used
and no explicit ENCODING parameter is needed. and no explicit ENCODING parameter is needed.
Value type: A single value. The default is binary. It can also be Value type: A single value. The default is binary. It can also be
skipping to change at page 34, line 23 skipping to change at page 36, line 43
TYPE parameter value MUST be a media type as specified in TYPE parameter value MUST be a media type as specified in
[RFC4288]. [RFC4288].
Example: Example:
KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN KEY;TYPE=application/pgp-keys;ENCODING=b:mQGiBEbEPUsRBACBF0RSIN
mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g mGutdM+KSAl7HMzwXHaLbvEOyu8At80I8qGejhzWowKbfem3X0m68Y/vhb+J2g
7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8 7q11KHpnEdNb67uZaj9nTQ09Q+UFtH25qD/Afn3+9bOJQaPjAUYzXu3vD/xmN8
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
5.9. Extended Properties and Parameters 7.9. Calendar Properties
These properties are further specified in [RFC2739].
7.9.1. FBURL
Purpose: To specify the URI for a user's busy time in a vCard
object.
Value type: A single URI value.
Special notes: Where multiple FBURL properties are specified, the
default FBURL property is indicated with the PREF parameter. The
FTP or HTTP type of URI points to an iCalendar object associated
with a snapshot of the last six weeks of the user's busy time
data. If the iCalendar object is represented as a file or
document, it's file type should be "ifb".
Examples:
FBURL;PREF:http://www.example.com/busy/janedoe
FBURL:FTP://ftp.example.com/busy/project-a.ifb
7.9.2. CALADRURI
Purpose: To specify the location to which an event request should be
sent for the user.
Value type: A single URI value.
Special notes: Where multiple CALADRURI properties are specified,
the default CALADRURI property is indicated with the PREF
parameter.
Example:
CALADRURI;PREF:mailto:janedoe@example.com
7.9.3. CAPURI
Purpose: To specify a protocol independent location from which a
calendaring and scheduling client (i.e., CUA) can communicate with
a user's entire calendar.
Value type: A single URI value.
Special notes: Where multiple CAPURI properties are specified, the
default CAPURI property is indicated with the PREF parameter.
7.9.4. CALURI
Purpose: To specify the URI for a user's calendar in a vCard object.
Value type: A single URI value.
Special notes: Where multiple CALURI properties are specified, the
default CALURI property is indicated with the PREF parameter. The
property should contain a URI pointing to an iCalendar object
associated with a snapshot of the user's calendar store. If the
iCalendar object is represented as a file or document, it's file
type should be "ics".
Examples:
CALURI;PREF:http://cal.example.com/calA
CALURI:ftp://ftp.example.com/calA.ics
7.10. Extended Properties and Parameters
The properties and parameters defined by this document can be The properties and parameters defined by this document can be
extended. Non-standard, private properties and parameters with a extended. Non-standard, private properties and parameters with a
name starting with "X-" may be defined bilaterally between two name starting with "X-" may be defined bilaterally between two
cooperating agents without outside registration or standardization. cooperating agents without outside registration or standardization.
6. Formal Grammar 8. Synchronization
The following formal grammar is provided to assist developers in vCard data often needs to be synchronized between devices. In this
building parsers for the vCard. context, synchronization is defined as the intelligent merging of two
representations of the same object. vCard 4.0 includes mechanisms to
aid this process.
This syntax is written according to the form described in [RFC5234], 8.1. Mechanisms
but it references just this small subset of [RFC5234] literals:
;******************************************* Two vCards for which the UID properties (Section 7.7.7) are
; Commonly Used Literal Definition equivalent MUST be considered representations of the same object.
;******************************************* Equivalence is determined as specified in [RFC3986], Section 6. A
missing UID property MUST NOT be considered equivalent to any other.
Hence, the UID property MUST be present if synchronization is to be
used.
ALPHA = %x41-5A / %x61-7A Pairs of properties, one from each of a pair of vCards representing
; Latin Capital Letter A-Latin Capital Letter Z / the same object, having equivalent names and UID parameter values
; Latin Small Letter a-Latin Small Letter z MUST be considered representations of the same object. A missing UID
CHAR = %x01-7F parameter MUST NOT be considered equivalent to any other. Hence, the
; Any C0 Controls and Basic Latin, excluding NULL from UID parameter MUST be present if synchronization is to be used.
; Code Charts, pages 7-6 through 7-9 in [UNICODE]
CR = %x0D It is expected that a synchronization engine will exploit such
; Carriage Return property associations by e.g. overwriting the destination property
value and parameters with the source destination property value and
parameters. The particular merging strategy is out of scope for this
document.
LF = %0A 8.2. Example
; Line Feed
CRLF = CR LF Two vCards are to by synchronized:
; Internet standard newline
;CTL = %x00-1F / %x7F BEGIN:VCARD
; Controls. Not used, but referenced in comments. VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
jdoe1@example.com
EMAIL;UID="urn:uuid:48a28f93-d4a4-4430-a7c6-a784ecb3f865":
jdoe2@example.com
END:VCARD
DIGIT = %x30-39 BEGIN:VCARD
; Digit Zero-Digit Nine VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
jdoe3@example.com
EMAIL;UID="urn:uuid:a69f4bff-49c5-4829-8c95-63db67c85bd6":
jdoe4@example.com
END:VCARD
DQUOTE = %x22 Assuming the first one is the source and the other is the
; Quotation Mark destination, a synchronization engine may produce the following
merged vCard:
HTAB = %x09 BEGIN:VCARD
; Horizontal Tabulation VERSION:4.0
UID:urn:uuid:77a01597-0603-40f3-8138-36deca8618da
FN;UID="urn:uuid:dade7896-81bd-4a3c-950e-bdfc04f15b61":Jane Doe
EMAIL;UID="urn:uuid:69531f4a-c34d-4a1e-8922-bd38a9476a53":
jdoe1@example.com
EMAIL;UID="urn:uuid:48a28f93-d4a4-4430-a7c6-a784ecb3f865":
jdoe2@example.com
EMAIL;UID="urn:uuid:a69f4bff-49c5-4829-8c95-63db67c85bd6":
jdoe4@example.com
END:VCARD
SP = %x20 9. Formal Grammar
; space
VCHAR = %x21-7E The following formal grammar is provided to assist developers in
; Visible (printing) characters building parsers for the vCard.
WSP = SP / HTAB This syntax is written according to the form described in [RFC5234],
; White Space but it references just this small subset of [RFC5234] literals:
;******************************************* ;*******************************************
; Basic vCard Definition ; Basic vCard Definition
;******************************************* ;*******************************************
vcard_entity = 1*(vcard) vcard_entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" 1*CRLF vcard = "BEGIN" ":" "VCARD" 1*CRLF
1*(contentline) 1*(contentline)
;A vCard object MUST include the VERSION, FN and N types. ;A vCard object MUST include the VERSION, FN and N types.
skipping to change at page 38, line 41 skipping to change at page 43, line 23
;For name="LABEL" ;For name="LABEL"
param = adr-param / text-param param = adr-param / text-param
; Only adr and text parameters allowed ; Only adr and text parameters allowed
value = text-value value = text-value
;For name="TEL" ;For name="TEL"
param = tel-param param = tel-param
; Only tel parameters allowed ; Only tel parameters allowed
value = phone-number-value value = uri-value
tel-param = "TYPE" "=" tel-type *("," tel-type) tel-param = "TYPE" "=" tel-type *("," tel-type)
tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG" tel-type = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
/ "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN" / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
/ "VIDEO" / "PCS" / iana-token / x-name / "VIDEO" / "PCS" / iana-token / x-name
; Values are case insensitive ; Values are case insensitive
;For name="EMAIL" ;For name="EMAIL"
param = email-param param = email-param
; Only email parameters allowed ; Only email parameters allowed
skipping to change at page 41, line 46 skipping to change at page 46, line 28
/ ("TYPE" "=" *SAFE-CHAR) / ("TYPE" "=" *SAFE-CHAR)
; Value MUST be an IANA registered audio type ; Value MUST be an IANA registered audio type
snd-refer-value = uri snd-refer-value = uri
; URI MUST refer to audio content of given type ; URI MUST refer to audio content of given type
snd-refer-param = ("VALUE" "=" "uri") snd-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" word) / ("TYPE" "=" word)
; Value MUST be an IANA registered audio type ; Value MUST be an IANA registered audio type
;For name="UID" ;For name="UID"
param = "TYPE" "=" (iana-token / x-name) param = ""
;TYPE value should be an IANA registered identifier format ; No parameters allowed
value = text-value value = uri
;For name="URL" ;For name="URL"
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = uri value = uri
;For name="VERSION" ;For name="VERSION"
;This type MUST be included in a vCard object. ;This type MUST be included in a vCard object.
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = text-value value = text-value
; Value MUST be "3.0" ; Value MUST be "4.0"
;For name="CLASS" ;For name="CLASS"
param = "" param = ""
; No parameters allowed ; No parameters allowed
value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" value = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL"
/ iana-token / x-name / iana-token / x-name
; Value are case insensitive ; Value are case insensitive
;For name="KEY" ;For name="KEY"
skipping to change at page 44, line 4 skipping to change at page 48, line 36
ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N") ESCAPED-CHAR = "\\" / "\;" / "\," / "\n" / "\N")
; \\ encodes \, \n or \N encodes newline ; \\ encodes \, \n or \N encodes newline
; \; encodes ;, \, encodes , ; \; encodes ;, \, encodes ,
binary-value = <A "b" encoded text value as defined in [RFC2047]> binary-value = <A "b" encoded text value as defined in [RFC2047]>
date-value = <A single date value as defined in [RFC2425]> date-value = <A single date value as defined in [RFC2425]>
time-value = <A single time value as defined in [RFC2425]> time-value = <A single time value as defined in [RFC2425]>
date-time-value = <A single date-time value as defined in [RFC2425]> date-time-value = <A single date-time value as defined in [RFC2425]>
float-value = <A single float value as defined in [RFC2425]> float-value = <A single float value as defined in [RFC2425]>
phone-number-value = <A single text value as defined in [CCITT phone-number-value = phone-prefix 1*(SP 1*DIGIT) [phone-ext]
E.163] and [CCITT.X121.1988]>
phone-prefix = "+" 1*DIGIT / "(" 1*DIGIT ")"
phone-ext = "ext." 1*DIGIT
uri-value = <A uri value as defined in [RFC2425]> uri-value = <A uri value as defined in [RFC2425]>
utc-offset-value = ("+" / "-") time-hour ":" time-minute utc-offset-value = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
7. Example: Authors' vCards 10. Example: Authors' vCards
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Pete Resnick FN:Pete Resnick
N:Resnick;Pete;;; N:Resnick;Pete;;;
GENDER:M GENDER:M
ORG:QUALCOMM Incorporated ORG:QUALCOMM Incorporated
ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US ADR;TYPE=work:;;5775 Morehouse Drive;San Diego;CA;92121-1714;US
TEL;TYPE=voice:+1-858-651-4478 TEL;TYPE=voice:tel:+1-858-651-4478
EMAIL;TYPE=internet:presnick@qualcomm.com EMAIL;TYPE=internet:presnick@qualcomm.com
URL:http://www.qualcomm.com/~presnick/ URL:http://www.qualcomm.com/~presnick/
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:4.0 VERSION:4.0
FN:Simon Perreault FN:Simon Perreault
N:Perreault;Simon;;;ing. jr.,M.Sc. N:Perreault;Simon;;;ing. jr.,M.Sc.
BDAY:1983-02-03 BDAY:1983-02-03
GENDER:M GENDER:M
ORG:Viagenie ORG:Viagenie
ADR;TYPE=work:;;2600 boul. Laurier\, suite 625; ADR;TYPE=work:;;2600 boul. Laurier\, suite 625;
Quebec;QC;G1V 4W1;Canada Quebec;QC;G1V 4W1;Canada
TEL;TYPE=voice,work:+1-418-656-9254 TEL;TYPE=voice,work:tel:+1-418-656-9254;ext=102
TEL;TYPE=fax,work:+1-418-656-9257 TEL;TYPE=fax,work:tel:+1-418-656-9257
EMAIL;TYPE=internet,work:simon.perreault@viagenie.ca EMAIL;TYPE=internet,work:simon.perreault@viagenie.ca
GEO:46.772673,-71.282945 GEO:46.772673,-71.282945
CLASS:PUBLIC CLASS:PUBLIC
KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc KEY;VALUE=uri:http://www.viagenie.ca/simon.perreault/simon.asc
END:VCARD END:VCARD
8. Security Considerations 11. Security Considerations
o Internet mail is subject to many well known security attacks, o Internet mail is subject to many well known security attacks,
including monitoring, replay, and forgery. Care should be taken including monitoring, replay, and forgery. Care should be taken
by any directory service in allowing information to leave the by any directory service in allowing information to leave the
scope of the service itself, where any access controls can no scope of the service itself, where any access controls can no
longer be guaranteed. Applications should also take care to longer be guaranteed. Applications should also take care to
display directory data in a "safe" environment (e.g., PostScript- display directory data in a "safe" environment (e.g., PostScript-
valued types). valued types).
o vCards can carry cryptographic keys or certificates, as described o vCards can carry cryptographic keys or certificates, as described
in Section 5.8.2. in Section 7.8.2.
o Section 5.8.1 specifies a desired security classification policy o Section 7.8.1 specifies a desired security classification policy
for a particular vCard. That policy is not enforced in any way. for a particular vCard. That policy is not enforced in any way.
o The vCard objects have no inherent authentication or privacy, but o The vCard objects have no inherent authentication or privacy, but
can easily be carried by any security mechanism that transfers can easily be carried by any security mechanism that transfers
MIME objects with authentication or privacy. In cases where MIME objects with authentication or privacy. In cases where
threats of "spoofed" vCard information is a concern, the vCard threats of "spoofed" vCard information is a concern, the vCard
SHOULD BE transported using one of these secure mechanisms. SHOULD BE transported using one of these secure mechanisms.
o The information in a vCard may become out of date. In cases where o The information in a vCard may become out of date. In cases where
the vitality of data is important to an originator of a vCard, the the vitality of data is important to an originator of a vCard, the
"URL" type described in Section 5.7.8 SHOULD BE specified. In "URL" type described in Section 7.7.8 SHOULD BE specified. In
addition, the "REV" type described in section Section 5.7.4 can be addition, the "REV" type described in section Section 7.7.4 can be
specified to indicate the last time that the vCard data was specified to indicate the last time that the vCard data was
updated. updated.
9. Acknowledgements 12. IANA Considerations
12.1. Registering New vCard Elements
This section defines the process for registering new or modified
vCard elements (i.e. properties, parameters, value data types, and
values) with IANA.
12.1.1. Registration Procedure
The IETF will create a mailing list, vcard@ietf.org [1], which can be
used for public discussion of vCard element proposals prior to
registration. Use of the mailing list is strongly encouraged. The
IESG will appoint a designated expert who will monitor the
vcard@ietf.org [1] mailing list and review registrations.
Registration of new vCard elements MUST be reviewed by the designated
expert and published in an RFC. A Standard Tracks RFC is REQUIRED
for the regisration of new value data types that modify existing
properties. A Standard Tracks RFC is also REQUIRED for registration
of vCard elements that modify vCard elements previously documented in
a Standard Tracks RFC.
The registration procedure begins when a completed registration
template, defined in the sections below, is sent to
vcard@ietf.org [1] and iana@iana.org [2]. The designated expert is
expected to tell IANA and the submitter of the registration within
two weeks whether the registration is approved, approved with minor
changes, or rejected with cause. When a registration is rejected
with cause, it can be re-submitted if the concerns listed in the
cause are addressed. Decisions made by the designated expert can be
appealed to the IESG Applications Area Director, then to the IESG.
They follow the normal appeals procedure for IESG decisions.
12.1.2. Vendor Namespace
The vendor namespace is used for vCard elements associated with
commercially available products. "Vendor" or "producer" are
construed as equivalent and very broadly in this context.
A registration may be placed in the vendor namespace by anyone who
needs to interchange files associated with the particular product.
However, the registration formally belongs to the vendor or
organization handling the vCard elements in the namespace being
registered. Changes to the specification will be made at their
request, as discussed in subsequent sections.
vCard elements belonging to the vendor namespace will be
distinguished by the "VND-" prefix. That may be followed, at the
discretion of the registrant, by either a vCard element name from a
well-known producer (e.g., "VND-MUDPIE") or by an IANA-approved
designation of the producer's name that is followed by a vCard
element designation (e.g., "VND-BIGCOMPANY-MUDPIE").
While public exposure and review of vCard elements to be registered
in the vendor namespace is not required, using the vcard@ietf.org [1]
mailing list for review is strongly encouraged to improve the quality
of those specifications. Registrations in the vendor namespace may
be submitted directly to the IANA.
12.1.3. Registration Template for Properties
A property is defined by completing the following template.
Property name: The name of the property.
Purpose: The purpose of the property. Give a short but clear
description.
Value type: Any of the valid value types for the property value
needs to be specified. The default value type also needs to be
specified.
Property parameters: Any of the valid property parameters for the
property MUST be specified.
Description: Any special notes about the property, how it is to be
used, etc.
Format definition: The ABNF for the property definition needs to be
specified.
Example(s): One or more examples of instances of the property needs
to be specified.
12.1.4. Registration Template for Parameters
A parameter is defined by completing the following template.
Parameter name: The name of the parameter.
Purpose: The purpose of the parameter. Give a short but clear
description.
Description: Any special notes about the parameter, how it is to be
used, etc.
Format definition: The ABNF for the parameter definition needs to be
specified.
Example(s): One or more examples of instances of the parameter needs
to be specified.
12.1.5. Registration Template for Value Data Types
A value data type is defined by completing the following template.
Value name: The name of the value type.
Purpose: The purpose of the value type. Give a short but clear
description.
Description: Any special notes about the value type, how it is to be
used, etc.
Format definition: The ABNF for the value type definition needs to
be specified.
Example(s): One or more examples of instances of the value type
needs to be specified.
12.1.6. Registration Template for Values
A value is defined by completing the following template.
Value: The value literal.
Purpose: The purpose of the value. Give a short but clear
description.
Conformance: The vCard properties and/or parameters that can take
this value needs to be specified.
Example(s): One or more examples of instances of the value needs to
be specified.
The following is a fictitious example of a registration of a vCard
value:
Value: TOP-SECRET
Purpose: This value is used to specify the access classification of
top-secret vCards.
Conformance: This value can be used with the "CLASS" property.
Example(s): The following is an example of this value used with the
"CLASS" property:
CLASS:TOP-SECRET
12.2. Initial vCard Elements Registries
The IANA is requested to create and maintain the following registries
for vCard elements with pointers to appropriate reference documents.
12.2.1. Properties Registry
The following table is to be used to initialize the properties
registry.
+-------------+---------+------------------------+
| Property | Status | Reference |
+-------------+---------+------------------------+
| SOURCE | Current | RFCXXXX, Section 7.1.3 |
| NAME | Current | RFCXXXX, Section 7.1.4 |
| KIND | Current | RFCXXXX, Section 7.1.5 |
| FN | Current | RFCXXXX, Section 7.2.1 |
| N | Current | RFCXXXX, Section 7.2.2 |
| NICKNAME | Current | RFCXXXX, Section 7.2.3 |
| PHOTO | Current | RFCXXXX, Section 7.2.4 |
| BDAY | Current | RFCXXXX, Section 7.2.5 |
| DDAY | Current | RFCXXXX, Section 7.2.6 |
| BIRTH | Current | RFCXXXX, Section 7.2.7 |
| DEATH | Current | RFCXXXX, Section 7.2.8 |
| GENDER | Current | RFCXXXX, Section 7.2.9 |
| ADR | Current | RFCXXXX, Section 7.3.1 |
| LABEL | Current | RFCXXXX, Section 7.3.2 |
| TEL | Current | RFCXXXX, Section 7.4.1 |
| EMAIL | Current | RFCXXXX, Section 7.4.2 |
| IMPP | Current | RFCXXXX, Section 7.4.3 |
| LANG | Current | RFCXXXX, Section 7.4.4 |
| TZ | Current | RFCXXXX, Section 7.5.1 |
| GEO | Current | RFCXXXX, Section 7.5.2 |
| TITLE | Current | RFCXXXX, Section 7.6.1 |
| ROLE | Current | RFCXXXX, Section 7.6.2 |
| LOGO | Current | RFCXXXX, Section 7.6.3 |
| AGENT | Current | RFCXXXX, Section 7.6.4 |
| ORG | Current | RFCXXXX, Section 7.6.5 |
| CATEGORIES | Current | RFCXXXX, Section 7.7.1 |
| NOTE | Current | RFCXXXX, Section 7.7.2 |
| PRODID | Current | RFCXXXX, Section 7.7.3 |
| REV | Current | RFCXXXX, Section 7.7.4 |
| SORT-STRING | Current | RFCXXXX, Section 7.7.5 |
| SOUND | Current | RFCXXXX, Section 7.7.6 |
| UID | Current | RFCXXXX, Section 7.7.7 |
| URL | Current | RFCXXXX, Section 7.7.8 |
| VERSION | Current | RFCXXXX, Section 7.7.9 |
| CLASS | Current | RFCXXXX, Section 7.8.1 |
| KEY | Current | RFCXXXX, Section 7.8.2 |
| FBURL | Current | RFCXXXX, Section 7.9.1 |
| CALADRURI | Current | RFCXXXX, Section 7.9.2 |
| CAPURI | Current | RFCXXXX, Section 7.9.3 |
| CALURI | Current | RFCXXXX, Section 7.9.4 |
+-------------+---------+------------------------+
12.2.2. Parameters Registry
The following table is to be used to initialize the parameters
registry.
+-----------+---------+----------------------+
| Parameter | Status | Reference |
+-----------+---------+----------------------+
| LANGUAGE | Current | RFCXXXX, Section 6.1 |
| ENCODING | Current | RFCXXXX, Section 6.2 |
| VALUE | Current | RFCXXXX, Section 6.3 |
| UID | Current | RFCXXXX, Section 6.4 |
| TYPE | Current | RFCXXXX, Section 6.5 |
+-----------+---------+----------------------+
12.2.3. Value Data Types Registry
The following table is to be used to initialize the parameters
registry.
+-----------------+---------+----------------------+
| Value Data Type | Status | Reference |
+-----------------+---------+----------------------+
| BINARY | Current | RFCXXXX, Section 5.7 |
| BOOLEAN | Current | RFCXXXX, Section 5.4 |
| DATE | Current | RFCXXXX, Section 5.3 |
| TIME | Current | RFCXXXX, Section 5.3 |
| DATE-TIME | Current | RFCXXXX, Section 5.3 |
| FLOAT | Current | RFCXXXX, Section 5.6 |
| INTEGER | Current | RFCXXXX, Section 5.5 |
| TEXT | Current | RFCXXXX, Section 5.1 |
| URI | Current | RFCXXXX, Section 5.2 |
+-----------------+---------+----------------------+
13. Acknowledgements
The authors would like to thank Frank Dawson and Tim Howes, the The authors would like to thank Frank Dawson and Tim Howes, the
original authors of [RFC2425] and [RFC2426], as well as the following original authors of [RFC2425] and [RFC2426], as well as the following
individuals who have participated in the drafting, review and individuals who have participated in the drafting, review and
discussion of this memo: discussion of this memo:
Marc Blanchet, Darryl Champagne, Cyrus Daboo, Javier Godoy, Mark Marc Blanchet, Chris Bryant, Darryl Champagne, Cyrus Daboo, Lisa
Paterson, and Julien Reschke. Dusseault, Javier Godoy, Alexander Mayrhofer, Chris Newman, Mark
Paterson, Alexander Mayrhofer, Julian Reschke, Peter K. Sheerin, Anil
Srivastava, and Kurt Zeilenga.
10. References 14. References
10.1. Normative References 14.1. Normative References
[CCITT.E163.1988] International Telephone and Telegraph [CCITT.E163.1988] International Telephone and Telegraph
Consultative Committee, "Numbering Plan for Consultative Committee, "Numbering Plan for
the International Telephone Service", the International Telephone Service",
CCITT Recommendation E.163, 1988. CCITT Recommendation E.163, 1988.
[CCITT.X121.1988] International Telephone and Telegraph [CCITT.X121.1988] International Telephone and Telegraph
Consultative Committee, "International Consultative Committee, "International
Numbering Plan for the Public Data Networks", Numbering Plan for the Public Data Networks",
CCITT Recommendation X.121, 1988. CCITT Recommendation X.121, 1988.
skipping to change at page 47, line 6 skipping to change at page 57, line 13
RFC 2425, September 1998. RFC 2425, September 1998.
[RFC2426] Dawson, F. and T. Howes, "vCard MIME [RFC2426] Dawson, F. and T. Howes, "vCard MIME
Directory Profile", RFC 2426, September 1998. Directory Profile", RFC 2426, September 1998.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk,
H., Masinter, L., Leach, P., and T. Berners- H., Masinter, L., Leach, P., and T. Berners-
Lee, "Hypertext Transfer Protocol -- Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999. HTTP/1.1", RFC 2616, June 1999.
[RFC2739] Small, T., Hennessy, D., and F. Dawson,
"Calendar Attributes for vCard and LDAP",
RFC 2739, January 2000.
[RFC2822] Resnick, P., "Internet Message Format", [RFC2822] Resnick, P., "Internet Message Format",
RFC 2822, April 2001. RFC 2822, April 2001.
[RFC2978] Freed, N. and J. Postel, "IANA Charset [RFC2978] Freed, N. and J. Postel, "IANA Charset
Registration Procedures", BCP 19, RFC 2978, Registration Procedures", BCP 19, RFC 2978,
October 2000. October 2000.
[RFC3629] Yergeau, F., "UTF-8, a transformation format [RFC3629] Yergeau, F., "UTF-8, a transformation format
of ISO 10646", STD 63, RFC 3629, of ISO 10646", STD 63, RFC 3629,
November 2003. November 2003.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone
Numbers", RFC 3966, December 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. [RFC3986] Berners-Lee, T., Fielding, R., and L.
Masinter, "Uniform Resource Identifier (URI): Masinter, "Uniform Resource Identifier (URI):
Generic Syntax", STD 66, RFC 3986, Generic Syntax", STD 66, RFC 3986,
January 2005. January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A
Universally Unique IDentifier (UUID) URN
Namespace", RFC 4122, July 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type [RFC4288] Freed, N. and J. Klensin, "Media Type
Specifications and Registration Procedures", Specifications and Registration Procedures",
BCP 13, RFC 4288, December 2005. BCP 13, RFC 4288, December 2005.
[RFC4646] Phillips, A. and M. Davis, "Tags for [RFC4646] Phillips, A. and M. Davis, "Tags for
Identifying Languages", BCP 47, RFC 4646, Identifying Languages", BCP 47, RFC 4646,
September 2006. September 2006.
[RFC4770] Jennings, C. and J. Reschke, Ed., "vCard [RFC4770] Jennings, C. and J. Reschke, Ed., "vCard
Extensions for Instant Messaging (IM)", Extensions for Instant Messaging (IM)",
skipping to change at page 47, line 47 skipping to change at page 58, line 16
[oldreference_UNICODE] The International Organization for [oldreference_UNICODE] The International Organization for
Standardization, "The Unicode Standard - Standardization, "The Unicode Standard -
Version 2.0", The Unicode Consortium", Version 2.0", The Unicode Consortium",
July 1996. July 1996.
[oldreference_VCARD] Internet Mail Consortium, "vCard - The [oldreference_VCARD] Internet Mail Consortium, "vCard - The
Electronic Business Card Version 2.1", Electronic Business Card Version 2.1",
September September. September September.
10.2. Informative References 14.2. Informative References
[ISO9070] The International Organization for [ISO9070] The International Organization for
Standardization, "ISO 9070, Information Standardization, "ISO 9070, Information
Processing - SGML support facilities - Processing - SGML support facilities -
Registration Procedures for Public Text Owner Registration Procedures for Public Text Owner
Identifiers", April 1991. Identifiers", April 1991.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and
P. Faltstrom, "Uniform Resource Names (URN) P. Faltstrom, "Uniform Resource Names (URN)
Namespace Definition Mechanisms", BCP 66, Namespace Definition Mechanisms", BCP 66,
RFC 3406, October 2002. RFC 3406, October 2002.
[WGS84] National Imagery and Mapping Agency,
"Department of Defense World Geodetic System
1984, Third Edition", NIMA TR8350.2,
January 2000.
URIs
[1] <mailto:vcard@ietf.org>
[2] <mailto:iana@iana.org>
Appendix A. Differences from RFCs 2425 and 2426 Appendix A. Differences from RFCs 2425 and 2426
This appendix contains a list of changes that have been made in the This appendix contains a list of changes that have been made in the
vCard specification from RFCs 2425 and 2426. vCard specification from RFCs 2425 and 2426.
A.1. New Structure A.1. New Structure
o [RFC2425] and [RFC2426] have been merged. Initially [RFC2425] was o [RFC2425] and [RFC2426] have been merged. Initially [RFC2425] was
intended to be extensible but only 2426 ever extended it. intended to be extensible but only 2426 ever extended it.
o vCard is now not only a MIME type but a stand-alone format. o vCard is now not only a MIME type but a stand-alone format.
o A proper MIME type registration form has been included. o A proper MIME type registration form has been included.
o UTF-8 is now the default character set. o UTF-8 is now the default character set.
o New vCard elements can be registered from IANA.
A.2. Removed Features A.2. Removed Features
o The group construct (i.e. GROUP.PROPERTY:...) no longer exists. o The group construct (i.e. GROUP.PROPERTY:...) no longer exists.
o The CONTEXT and CHARSET parameters are no more. o The CONTEXT and CHARSET parameters are no more.
o The MAILER property is no more. o The MAILER property is no more.
o The "intl", "dom", "postal", and "parcel" TYPE parameter values o The "intl", "dom", "postal", and "parcel" TYPE parameter values
for the ADR and LABEL properties have been removed. for the ADR and LABEL properties have been removed.
A.3. New Properties and Parameters A.3. New Properties and Parameters
o The KIND, GENDER, LANG, DDAY, BIRTH, and DEATH properties have o The KIND, GENDER, LANG, DDAY, BIRTH, and DEATH properties have
been added. been added.
o [RFC2739], which defines the FBURL, CALADRURI, CAPURI, and CALURI
properties, has been merged in.
o [RFC4770], which defines the IMPP property, has been merged in. o [RFC4770], which defines the IMPP property, has been merged in.
o The "work", "home", and "uri" TYPE parameter values for the EMAIL o The "work", "home", and "uri" TYPE parameter values for the EMAIL
property have been added. property have been added.
A.4. Other Changes A.4. Other Changes
o Synchronization is addressed in Section 8.
o The N property is no longer mandatory. o The N property is no longer mandatory.
o The value of TEL is now a URI.
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 -01 B.1. Changes in -01
o Merged [RFC2739] in.
o Converted all foobar.com, abc.com, etc. to example.com.
o Fixed bugs in ABNF.
o Made explicit that coordinates in the GEO property are expressed
in the WGS 84 reference system.
o Clarified folding issues with multi-byte characters.
o Made the value of TEL a URI.
o Added the UID parameter.
o Made the UID property's value type a URI.
o Added Section 8.
o Created IANA process for registering new parameters, value types,
and properties.
o Created the initial IANA registries.
o Created vendor namespace based on text from RFC 4288.
B.2. Changes in -00
o Name change because draft has been accepted as WG item.
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.
o Renamed Section 5.4 from "Telecommunications Adressing Properties" o Renamed Section 7.4 from "Telecommunications Adressing Properties"
to "Communications Properties. to "Communications Properties.
o Added Appendix A and Appendix B. o Added Appendix A and Appendix B.
o Added reference to [RFC4770]. o Added reference to [RFC4770].
o Removed the group construct. o Removed the group construct.
o Made the N property no longer mandatory. o Made the N property no longer mandatory.
 End of changes. 159 change blocks. 
288 lines changed or deleted 774 lines changed or added

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