draft-ietf-asid-mime-vcard-07.txt   rfc2426.txt 
Network Working Group Frank Dawson Network Working Group F. Dawson
Request for Comments: DRAFT Lotus Development Corporation Request for Comments: 2426 Lotus Development Corporation
draft-ietf-asid-mime-vcard-07.txt Tim Howes Category: Standards Track T. Howes
Expires six months after July 21, 1998 Netscape Communications Netscape Communications
September 1998
vCard MIME Directory Profile vCard MIME Directory Profile
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its areas, Internet community, and requests discussion and suggestions for
and its working groups. Note that other groups may also distribute improvements. Please refer to the current edition of the "Internet
working documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast).
Distribution of this memo is unlimited. Copyright Notice
Copyright (C) The Internet Society 1997. All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This memo defines the profile of the MIME Content-Type [MIME-DIR] for This memo defines the profile of the MIME Content-Type [MIME-DIR] for
directory information for a white-pages person object, based on a directory information for a white-pages person object, based on a
vCard electronic business card. The profile definition is independent vCard electronic business card. The profile definition is independent
of any particular directory service or protocol. The profile is of any particular directory service or protocol. The profile is
defined for representing and exchanging a variety of information defined for representing and exchanging a variety of information
about an individual (e.g., formatted and structured name and delivery about an individual (e.g., formatted and structured name and delivery
addresses, email address, multiple telephone numbers, photograph, addresses, email address, multiple telephone numbers, photograph,
skipping to change at line 51 skipping to change at page 2, line 5
profile is based on the attributes for the person object defined in profile is based on the attributes for the person object defined in
the X.520 and X.521 directory services recommendations. The profile the X.520 and X.521 directory services recommendations. The profile
also provides the method for including a [VCARD] representation of a also provides the method for including a [VCARD] representation of a
white-pages directory entry within the MIME Content-Type defined by white-pages directory entry within the MIME Content-Type defined by
the [MIME-DIR] document. the [MIME-DIR] document.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in [RFC 2119]. document are to be interpreted as described in [RFC 2119].
vCard MIME Directory Profile
Table of Contents Table of Contents
1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION.......................4 Overview.........................................................3
1. THE VCARD MIME DIRECTORY PROFILE REGISTRATION.................4
2. MIME DIRECTORY FEATURES.............................................5 2. MIME DIRECTORY FEATURES.......................................5
2.1 PREDEFINED TYPE USAGE ......................................5
2.1 PREDEFINED TYPE USAGE ............................................5 2.1.1 BEGIN and END Type ......................................5
2.1.1 BEGIN and END Type ............................................5 2.1.2 NAME Type ...............................................5
2.1.2 NAME Type .....................................................6 2.1.3 PROFILE Type ............................................5
2.1.3 PROFILE Type ..................................................6 2.1.4 SOURCE Type .............................................5
2.1.4 SOURCE Type ...................................................6 2.2 PREDEFINED TYPE PARAMETER USAGE ............................6
2.2 PREDEFINED TYPE PARAMETER USAGE ..................................6 2.3 PREDEFINED VALUE TYPE USAGE ................................6
2.3 PREDEFINED VALUE TYPE USAGE ......................................6 2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES ...................6
2.4 EXTENSIONS TO THE PREDEFINED VALUE TYPES .........................6 2.4.1 BINARY ..................................................6
2.4.1 BINARY ........................................................6 2.4.2 VCARD ...................................................6
2.4.2 VCARD .........................................................7 2.4.3 PHONE-NUMBER ............................................7
2.4.3 PHONE-NUMBER ..................................................7 2.4.4 UTC-OFFSET ..............................................7
2.4.4 UTC-OFFSET ....................................................7 2.5 STRUCTURED TYPE VALUES .....................................7
2.5 STRUCTURED TYPE VALUES ...........................................8 2.6 LINE DELIMITING AND FOLDING ................................8
2.6 LINE DELIMITING AND FOLDING ......................................8 3. VCARD PROFILE FEATURES........................................8
3.1 IDENTIFICATION TYPES .......................................8
3. VCARD PROFILE FEATURES..............................................8 3.1.1 FN Type Definition ......................................8
3.1.2 N Type Definition .......................................9
3.1 IDENTIFICATION TYPES .............................................8 3.1.3 NICKNAME Type Definition ................................9
3.1.1 FN Type Definition ............................................8 3.1.4 PHOTO Type Definition ..................................10
3.1.2 N Type Definition .............................................9 3.1.5 BDAY Type Definition ...................................11
3.1.3 NICKNAME Type Definition ......................................9 3.2 DELIVERY ADDRESSING TYPES .................................11
3.1.4 PHOTO Type Definition ........................................10 3.2.1 ADR Type Definition ....................................11
3.1.5 BDAY Type Definition .........................................11 3.2.2 LABEL Type Definition ..................................13
3.2 DELIVERY ADDRESSING TYPES .......................................11 3.3 TELECOMMUNICATIONS ADDRESSING TYPES .......................13
3.2.1 ADR Type Definition ..........................................11 3.3.1 TEL Type Definition ....................................14
3.2.2 LABEL Type Definition ........................................12 3.3.2 EMAIL Type Definition ..................................15
3.3 TELECOMMUNICATIONS ADDRESSING TYPES .............................13 3.3.3 MAILER Type Definition .................................15
3.3.1 TEL Type Definition ..........................................13 3.4 GEOGRAPHICAL TYPES ........................................16
3.3.2 EMAIL Type Definition ........................................14 3.4.1 TZ Type Definition .....................................16
3.3.3 MAILER Type Definition .......................................14 3.4.2 GEO Type Definition ....................................16
3.4 GEOGRAPHICAL TYPES ..............................................15 3.5 ORGANIZATIONAL TYPES ......................................17
3.4.1 TZ Type Definition ...........................................15 3.5.1 TITLE Type Definition ..................................17
3.4.2 GEO Type Definition ..........................................15 3.5.2 ROLE Type Definition ...................................18
3.5 ORGANIZATIONAL TYPES ............................................16 3.5.3 LOGO Type Definition ...................................18
3.5.1 TITLE Type Definition ........................................16 3.5.4 AGENT Type Definition ..................................19
3.5.2 ROLE Type Definition .........................................17 3.5.5 ORG Type Definition ....................................20
3.5.3 LOGO Type Definition .........................................17 3.6 EXPLANATORY TYPES .........................................20
3.5.4 AGENT Type Definition ........................................18 3.6.1 CATEGORIES Type Definition .............................20
3.5.5 ORG Type Definition ..........................................18 3.6.2 NOTE Type Definition ...................................21
3.6 EXPLANATORY TYPES ...............................................19 3.6.3 PRODID Type Definition .................................21
3.6.1 CATEGORIES Type Definition ...................................19 3.6.4 REV Type Definition ....................................22
3.6.2 NOTE Type Definition .........................................19 3.6.5 SORT-STRING Type Definition ............................22
3.6.3 PRODID Type Definition .......................................20 3.6.6 SOUND Type Definition ..................................23
3.6.4 REV Type Definition ..........................................20 3.6.7 UID Type Definition ....................................24
3.6.5 SORT-STRING Type Definition ..................................21 3.6.8 URL Type Definition ....................................25
3.6.6 SOUND Type Definition ........................................21 3.6.9 VERSION Type Definition ................................25
vCard MIME Directory Profile 3.7 SECURITY TYPES ............................................25
3.7.1 CLASS Type Definition ..................................26
3.6.7 UID Type Definition ..........................................22 3.7.2 KEY Type Definition ....................................26
3.6.8 URL Type Definition ..........................................22 3.8 EXTENDED TYPES ............................................27
3.6.9 VERSION Type Definition ......................................23 4. FORMAL GRAMMAR...............................................27
3.7 SECURITY TYPES ..................................................23 5. DIFFERENCES FROM VCARD V2.1..................................37
3.7.1 CLASS Type Definition ........................................23 6. ACKNOWLEDGEMENTS.............................................39
3.7.2 KEY Type Definition ..........................................24 7. AUTHORS' ADDRESSES...........................................39
3.8 EXTENDED TYPES ..................................................24 8. SECURITY CONSIDERATIONS......................................39
9. REFERENCES...................................................40
4. FORMAL GRAMMAR.....................................................25 10. FULL COPYRIGHT STATEMENT....................................42
5. DIFFERENCES FROM VCARD V2.1........................................34
6. ACKNOWLEDGEMENTS...................................................35
7. AUTHORS' ADDRESSES.................................................35
8. SECURITY...........................................................35
9. AUTHENTICATION OR PRIVACY..........................................36
10. REFERENCES........................................................36
11. FULL COPYRIGHT STATEMENT..........................................37
vCard MIME Directory Profile
Overview Overview
The [MIME-DIR] document defines a MIME Content-Type for holding The [MIME-DIR] document defines a MIME Content-Type for holding
different kinds of directory information. The directory information different kinds of directory information. The directory information
can be based on any of a number of directory schemas. This document can be based on any of a number of directory schemas. This document
defines a [MIME-DIR] usage profile for conveying directory defines a [MIME-DIR] usage profile for conveying directory
information based on one such schema; that of the white-pages type of information based on one such schema; that of the white-pages type of
person object. person object.
The schema is based on the attributes for the person object defined The schema is based on the attributes for the person object defined
in the X.520 and X.521 directory services recommendations. The schema in the X.520 and X.521 directory services recommendations. The schema
skipping to change at line 174 skipping to change at page 4, line 14
digital sound; longitude and latitude geo-positioning information digital sound; longitude and latitude geo-positioning information
related to the person associated with the directory entry; date and related to the person associated with the directory entry; date and
time that the directory information was last updated; annotations time that the directory information was last updated; annotations
often written on a business card; Uniform Resource Locators (URL) for often written on a business card; Uniform Resource Locators (URL) for
a website; public key information. The profile also provides support a website; public key information. The profile also provides support
for non-standard extensions to the schema. This provides the for non-standard extensions to the schema. This provides the
flexibility for implementations to augment the current capabilities flexibility for implementations to augment the current capabilities
of the profile in a standardized way. More information about this of the profile in a standardized way. More information about this
electronic business card format can be found in [VCARD]. electronic business card format can be found in [VCARD].
1. The vCard Mime Directory Profile Registration 1. The vCard Mime Directory Profile Registration
This profile is identified by the following [MIME-DIR] registration This profile is identified by the following [MIME-DIR] registration
template information. Subsequent sections define the profile template information. Subsequent sections define the profile
definition. definition.
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME profile VCARD Subject: Registration of text/directory MIME profile VCARD
Profile name: VCARD Profile name: VCARD
vCard MIME Directory Profile
Profile purpose: To hold person object or white-pages type of Profile purpose: To hold person object or white-pages type of
directory information. The person schema captured in the directory directory information. The person schema captured in the directory
entries is that commonly found in an electronic business card. entries is that commonly found in an electronic business card.
Predefined MIME Directory value specifications used: uri, date, date- Predefined MIME Directory value specifications used: uri, date,
time, float date-time, float
New value specifications: This profile places further constraints on New value specifications: This profile places further constraints on
the [MIME-DIR] text value specification. In addition, it adds a the [MIME-DIR] text value specification. In addition, it adds a
binary, phone-number, utc-offset and vcard value specifications. binary, phone-number, utc-offset and vcard value specifications.
Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN, Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
END. END.
Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET, Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT. LANGUAGE, CONTEXT.
skipping to change at line 221 skipping to change at page 5, line 12
VERSION types. The type-grouping feature of [MIME-DIR] is supported VERSION types. The type-grouping feature of [MIME-DIR] is supported
by this profile to group related vCard properties about a directory by this profile to group related vCard properties about a directory
entry. For example, vCard properties describing WORK or HOME related entry. For example, vCard properties describing WORK or HOME related
characteristics can be grouped with a unique group label. characteristics can be grouped with a unique group label.
The profile permits the use of non-standard types (i.e., those The profile permits the use of non-standard types (i.e., those
identified with the prefix string "X-") as a flexible method for identified with the prefix string "X-") as a flexible method for
implementations to extend the functionality currently defined within implementations to extend the functionality currently defined within
this profile. this profile.
2. MIME Directory Features 2. MIME Directory Features
The vCard MIME Directory Profile makes use of many of the features The vCard MIME Directory Profile makes use of many of the features
defined by [MIME-DIR]. The following sections either clarify or defined by [MIME-DIR]. The following sections either clarify or
extend the content-type definition of [MIME-DIR]. extend the content-type definition of [MIME-DIR].
2.1 Predefined Type Usage 2.1 Predefined Type Usage
The vCard MIME Directory Profile uses the following predefined types The vCard MIME Directory Profile uses the following predefined types
from [MIME-DIR]. from [MIME-DIR].
2.1.1 BEGIN and END Type 2.1.1 BEGIN and END Type
The content entity MUST begin with the BEGIN type with a value of The content entity MUST begin with the BEGIN type with a value of
"VCARD". The content entity MUST end with the END type with a value "VCARD". The content entity MUST end with the END type with a value
of "VCARD". of "VCARD".
vCard MIME Directory Profile 2.1.2 NAME Type
2.1.2 NAME Type
If the NAME type appears within a MIME entity conforming to this If the NAME type is present, then its value is the displayable,
profile, its value is the displayable, presentation text associated presentation text associated with the source for the vCard, as
with the source for the vCard, as specified in the SOURCE type. specified in the SOURCE type.
2.1.3 PROFILE Type 2.1.3 PROFILE Type
If the PROFILE type appears within a MIME entity conforming to this If the PROFILE type is present, then its value MUST be "VCARD".
profile, its value MUST be "VCARD".
2.1.4 SOURCE Type 2.1.4 SOURCE Type
If the SOURCE type appears within a MIME entity conforming to this If the SOURCE type is present, then its value provides information
profile, its value provides information how to find the source for how to find the source for the vCard.
the vCard.
2.2 Predefined Type Parameter Usage 2.2 Predefined Type Parameter Usage
The vCard MIME Directory Profile uses the following predefined type The vCard MIME Directory Profile uses the following predefined type
parameters as defined by [MIME-DIR]. parameters as defined by [MIME-DIR].
- LANGUAGE - LANGUAGE
- ENCODING - ENCODING
- VALUE - VALUE
2.3 Predefined VALUE Type Usage 2.3 Predefined VALUE Type Usage
The predefined data type values specified in [MIME-DIR] MUST NOT be The predefined data type values specified in [MIME-DIR] MUST NOT be
repeated in COMMA separated value lists, unless specified by this repeated in COMMA separated value lists except within the N,
specification. NICKNAME, ADR and CATEGORIES value types.
The text value type defined in [MIME-DIR] is further restricted such The text value type defined in [MIME-DIR] is further restricted such
that any SEMI-COLON character (ASCII decimal 59) in the value MUST be that any SEMI-COLON character (ASCII decimal 59) in the value MUST be
escaped with the BACKSLASH character (ASCII decimal 92). escaped with the BACKSLASH character (ASCII decimal 92).
2.4 Extensions To The Predefined VALUE Types 2.4 Extensions To The Predefined VALUE Types
The predefined data type values specified in [MIME-DIR] have been The predefined data type values specified in [MIME-DIR] have been
extended by the vCard profile to include a number of value types that extended by the vCard profile to include a number of value types that
are specific to this profile. are specific to this profile.
2.4.1 BINARY 2.4.1 BINARY
The "binary" value type specifies that the type value is inline, The "binary" value type specifies that the type value is inline,
encoded binary data. This value type can be specified in the PHOTO, encoded binary data. This value type can be specified in the PHOTO,
LOGO, SOUND, and KEY types. 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
vCard MIME Directory Profile
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 [MIME-DIR]. folding method defined in [MIME-DIR].
The value type is defined by the following notation: The value type is defined by the following notation:
binary = <A "B" binary encoded string as defined by [RFC 2047].> binary = <A "B" binary encoded string as defined by [RFC 2047].>
2.4.2 VCARD 2.4.2 VCARD
The "vcard" value type specifies that the type value is another The "vcard" value type specifies that the type value is another
vCard. This value type can be specified in the AGENT type. The value vCard. This value type can be specified in the AGENT type. The value
type is defined by this specification. Since each of the type type is defined by this specification. Since each of the type
declarations with in the vcard value type are being specified within declarations with in the vcard value type are being specified within
a text value themselves, they MUST be terminated with the backslash a text value themselves, they MUST be terminated with the backslash
escape sequence "\n" or "\N", instead of the normal newline character escape sequence "\n" or "\N", instead of the normal newline character
sequence CRLF. In addition, any COMMA character (ASCII decimal 44), sequence CRLF. In addition, any COMMA character (ASCII decimal 44),
SEMI-COLON character (ASCII decimal 59) and COLON character (ASCII SEMI-COLON character (ASCII decimal 59) and COLON character (ASCII
decimal 58) MUST be escaped with the BACKSLASH character (ASCII decimal 58) MUST be escaped with the BACKSLASH character (ASCII
decimal 92). For example, with the AGENT type a value would be decimal 92). For example, with the AGENT type a value would be
specified as : specified as:
AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+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@host.com\nEND:VCARD\n
2.4.3 PHONE-NUMBER 2.4.3 PHONE-NUMBER
The "phone-number" value type specifies that the type value is a The "phone-number" value type specifies that the type value is a
telephone number. This value type can be specified in the TEL type. 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 The value type is a text value that has the special semantics of a
telephone number as defined in [CCITT E.163] and [CCITT X.121]. telephone number as defined in [CCITT E.163] and [CCITT X.121].
2.4.4 UTC-OFFSET 2.4.4 UTC-OFFSET
The "utc-offset" value type specifies that the type value is a signed The "utc-offset" value type specifies that the type value is a signed
offset from UTC. This value type can be specified in the TZ type. offset from UTC. This value type can be specified in the TZ type.
The value type is an offset from Coordinated Universal Time (UTC). It The value type is an offset from Coordinated Universal Time (UTC). It
is specified as a positive or negative difference in units of hours 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 clock. 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 to 59. 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 Hour and minutes are 2-digits with high order zeroes required to
maintain digit count. The extended format for ISO 8601 UTC offsets maintain digit count. The extended format for ISO 8601 UTC offsets
MUST be used. The extended format makes use of a colon character as a MUST be used. The extended format makes use of a colon character as a
separator of the hour and minute text fields. separator of the hour and minute text fields.
The value is defined by the following notation: The value is defined by the following notation:
time-hour = 2DIGIT ;00-23 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59 time-minute = 2DIGIT ;00-59
utc-offset = ("+" / "-") time-hour ":" time-minute utc-offset = ("+" / "-") time-hour ":" time-minute
vCard MIME Directory Profile
2.5 Structured Type Values 2.5 Structured Type Values
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).
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 MUST COMMA character (ASCII decimal 44). A COMMA character in a value MUST
be escaped with a BACKSLASH character (ASCII decimal 92). be escaped with a BACKSLASH character (ASCII decimal 92).
This profile supports the type grouping mechanism defined in [MIME- This profile supports the type grouping mechanism defined in [MIME-
DIR]. Grouping of related types is a useful technique to communicate DIR]. Grouping of related types is a useful technique to communicate
common semantics concerning the properties of a vCard. common semantics concerning the properties of a vCard.
2.6 Line Delimiting and Folding 2.6 Line Delimiting and Folding
This profile supports the same line delimiting and folding methods This profile supports the same line delimiting and folding methods
defined in [MIME-DIR]. Specifically, when parsing a content line, defined in [MIME-DIR]. Specifically, when parsing a content line,
folded lines must first be unfolded according to the unfolding folded lines must first be unfolded according to the unfolding
procedure described in [MIME-DIR]. After generating a content line, procedure described in [MIME-DIR]. After generating a content line,
lines longer than 75 characters SHOULD be folded according to the lines longer than 75 characters SHOULD be folded according to the
folding procedure described in [MIME DIR]. folding procedure described in [MIME DIR].
Folding is done after any content encoding of a type value. Unfolding Folding is done after any content encoding of a type value. Unfolding
is done before any decoding of a type value in a content line. is done before any decoding of a type value in a content line.
3. vCard Profile Features 3. vCard Profile Features
The vCard MIME Directory Profile Type contains directory information, The vCard MIME Directory Profile Type contains directory information,
typically pertaining to a single directory entry. The information is typically pertaining to a single directory entry. The information is
described using an attribute schema that is tailored for capturing described using an attribute schema that is tailored for capturing
personal contact information. The vCard can include attributes that personal contact information. The vCard can include attributes that
describe identification, delivery addressing, telecommunications describe identification, delivery addressing, telecommunications
addressing, geographical, organizational, general explanatory and addressing, geographical, organizational, general explanatory and
security and access information about the particular object security and access information about the particular object
associated with the vCard. associated with the vCard.
3.1 Identification Types 3.1 Identification Types
These types are used in the vCard profile to capture information These types are used in the vCard profile to capture information
associated with the identification and naming of the person or associated with the identification and naming of the person or
resource associated with the vCard. resource associated with the vCard.
3.1.1 FN Type Definition 3.1.1 FN Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type FN Subject: Registration of text/directory MIME type FN
Type name:FN Type name:FN
Type purpose: To specify the formatted text corresponding to the name Type purpose: To specify the formatted text corresponding to the name
of the object the vCard represents. of the object the vCard represents.
vCard MIME Directory Profile
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This type is based on the semantics of the X.520 Type special notes: This type is based on the semantics of the X.520
Common Name attribute. The property MUST be present if the vCard Common Name attribute. The property MUST be present in the vCard
conforms to this specification. object.
Type example: Type example:
FN:Mr. John Q. Public\, Esq. FN:Mr. John Q. Public\, Esq.
3.1.2 N Type Definition 3.1.2 N Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type N Subject: Registration of text/directory MIME type N
Type name: N Type name: N
Type purpose: To specify the components of the name of the object the Type purpose: To specify the components of the name of the object the
vCard represents. vCard represents.
skipping to change at line 448 skipping to change at page 9, line 48
Additional Names) separated by the COMMA character (ASCII decimal Additional Names) separated by the COMMA character (ASCII decimal
44). This type is based on the semantics of the X.520 individual name 44). This type is based on the semantics of the X.520 individual name
attributes. The property MUST be present in the vCard object. attributes. The property MUST be present in the vCard object.
Type example: Type example:
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.
3.1.3 NICKNAME Type Definition 3.1.3 NICKNAME Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type NICKNAME Subject: Registration of text/directory MIME type NICKNAME
Type name: NICKNAME Type name: NICKNAME
Type purpose: To specify the text corresponding to the nickname of Type purpose: To specify the text corresponding to the nickname of
the object the vCard represents. the object the vCard represents.
vCard MIME Directory Profile
Type encoding: 8bit Type encoding: 8bit
Type value: One or more text values separated by a COMMA character Type value: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Type special note: The nickname is the descriptive name given instead Type special note: The nickname is the descriptive name given instead
of or in addition to the one belonging to a person, place, or thing. of 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 types.
Type example: Type example:
NICKNAME:Robbie NICKNAME:Robbie
NICKNAME:Jim,Jimmie NICKNAME:Jim,Jimmie
3.1.4 PHOTO Type Definition 3.1.4 PHOTO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type PHOTO Subject: Registration of text/directory MIME type PHOTO
Type name: PHOTO Type name: PHOTO
Type purpose: To specify an image or photograph information that Type 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.
skipping to change at line 511 skipping to change at page 11, line 14
Type example: Type example:
PHOTO;VALUE=uri:http://www.abc.com/pub/photos PHOTO;VALUE=uri:http://www.abc.com/pub/photos
/jqpublic.gif /jqpublic.gif
PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of "B" encoded binary data...> <...remainder of "B" encoded binary data...>
vCard MIME Directory Profile
3.1.5 BDAY Type Definition 3.1.5 BDAY Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type BDAY Subject: Registration of text/directory MIME type BDAY
Type name: BDAY Type name: BDAY
Type purpose: To specify the birth date of the object the vCard Type purpose: To specify the birth date of the object the vCard
represents. represents.
skipping to change at line 537 skipping to change at page 11, line 39
to a single date-time value. to a single date-time value.
Type examples: Type examples:
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00Z BDAY:1953-10-15T23:10:00Z
BDAY:1987-09-27T08:30:00-06:00 BDAY:1987-09-27T08:30:00-06:00
3.2 Delivery Addressing Types 3.2 Delivery Addressing Types
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.
3.2.1 ADR Type Definition 3.2.1 ADR Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type ADR Subject: Registration of text/directory MIME type ADR
Type name: ADR Type name: ADR
Type purpose: To specify the components of the delivery address for Type purpose: To specify the components of the delivery address for
the vCard object. the vCard object.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured text value, separated by the SEMI- Type value: A single structured text value, separated by the
COLON character (ASCII decimal 59). SEMI-COLON character (ASCII decimal 59).
Type special notes: The structured type value consists of a sequence Type special notes: The structured type value consists of a sequence
of address components. The component values MUST be specified in of address components. The component values MUST be specified in
their corresponding position. The structured type value corresponds, their corresponding position. The structured type value corresponds,
in sequence, to the post office box; the extended address; the street in sequence, to the post office box; the extended address; the street
address; the locality (e.g., city); the region (e.g., state or address; the locality (e.g., city); the region (e.g., state or
province); the postal code; the country name. When a component value province); the postal code; the country name. When a component value
is missing, the associated component separator MUST still be is missing, the associated component separator MUST still be
specified. specified.
vCard MIME Directory Profile
The text components are separated by the SEMI-COLON character (ASCII The text components are separated by the SEMI-COLON character (ASCII
decimal 59). Where it makes semantic sense, individual text decimal 59). Where it makes semantic sense, individual text
components can include multiple text values (e.g., a "street" components can include multiple text values (e.g., a "street"
component with multiple lines) separated by the COMMA character component with multiple lines) separated by the COMMA character
(ASCII decimal 44). (ASCII decimal 44).
The type can include the type parameter "TYPE" to specify the The type can include the type parameter "TYPE" to specify the
delivery address type. The TYPE parameter values can include "dom" to delivery address type. The TYPE parameter values can include "dom" to
indicate a domestic delivery address; "intl" to indicate an indicate a domestic delivery address; "intl" to indicate an
international delivery address; "postal" to indicate a postal international delivery address; "postal" to indicate a postal
skipping to change at line 596 skipping to change at page 12, line 48
X.520 geographical and postal addressing attributes. The default is X.520 geographical and postal addressing attributes. The default is
"TYPE=intl,postal,parcel,work". The default can be overridden to some "TYPE=intl,postal,parcel,work". The default can be overridden to some
other set of values by specifying one or more alternate values. For other set of values by specifying one or more alternate values. For
example, the default can be reset to "TYPE=dom,postal,work,home" to example, the default can be reset to "TYPE=dom,postal,work,home" to
specify a domestic delivery address for postal delivery to a specify a domestic delivery address for postal delivery to a
residence that is also used for work. residence that is also used for work.
Type example: In this example the post office box and the extended Type example: In this example the post office box and the extended
address are absent. address are absent.
ADR;TYPE=dom,home,postal,parcel:;;123 Main ADR;TYPE=dom,home,postal,parcel:;;123 Main
Street;Any Town;CA;91921-1234 Street;Any Town;CA;91921-1234
3.2.2 LABEL Type Definition 3.2.2 LABEL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type LABEL Subject: Registration of text/directory MIME type LABEL
Type name: LABEL Type name: LABEL
Type purpose: To specify the formatted text corresponding to delivery Type purpose: To specify the formatted text corresponding to delivery
address of the object the vCard represents. address of the object the vCard represents.
skipping to change at line 623 skipping to change at page 13, line 29
Type special notes: The type value is formatted text that can be used Type special notes: The type value is formatted text that can be used
to present a delivery address label for the vCard object. The type to present a delivery address label for the vCard object. The type
can include the type parameter "TYPE" to specify delivery label type. can include the type parameter "TYPE" to specify delivery label type.
The TYPE parameter values can include "dom" to indicate a domestic The TYPE parameter values can include "dom" to indicate a domestic
delivery label; "intl" to indicate an international delivery label; delivery label; "intl" to indicate an international delivery label;
"postal" to indicate a postal delivery label; "parcel" to indicate a "postal" to indicate a postal delivery label; "parcel" to indicate a
parcel delivery label; "home" to indicate a delivery label for a parcel delivery label; "home" to indicate a delivery label for a
residence; "work" to indicate delivery label for a place of work; and residence; "work" to indicate delivery label for a place of work; and
"pref" to indicate the preferred delivery label when more than one "pref" to indicate the preferred delivery label when more than one
vCard MIME Directory Profile
label is specified. These type parameter values can be specified as a label is specified. These type parameter values can be specified as a
parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
(i.e., "TYPE=dom,postal"). This type is based on semantics of the (i.e., "TYPE=dom,postal"). This type is based on semantics of the
X.520 geographical and postal addressing attributes. The default is X.520 geographical and postal addressing attributes. The default is
"TYPE=intl,postal,parcel,work". The default can be overridden to some "TYPE=intl,postal,parcel,work". The default can be overridden to some
other set of values by specifying one or more alternate values. For other set of values by specifying one or more alternate values. For
example, the default can be reset to "TYPE=intl,post,parcel,home" to example, the default can be reset to "TYPE=intl,post,parcel,home" to
specify an international delivery label for both postal and parcel specify an international delivery label for both postal and parcel
delivery to a residential location. delivery to a residential location.
Type example: A multi-line address label. Type example: A multi-line address label.
LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public\, Esq.\n
Mail Drop: TNE QB\n Mail Drop: TNE QB\n123 Main Street\nAny Town\, CA 91921-1234
123 Main Street\n \nU.S.A.
Any Town\, CA 91921-1234\n
U.S.A.
3.3 Telecommunications Addressing Types 3.3 Telecommunications Addressing Types
These types are concerned with information associated with the These types are concerned with information associated with the
telecommunications addressing of the object the vCard represents. telecommunications addressing of the object the vCard represents.
3.3.1 TEL Type Definition 3.3.1 TEL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type TEL Subject: Registration of text/directory MIME type TEL
Type name: TEL Type name: TEL
Type purpose: To specify the telephone number for telephony Type purpose: To specify the telephone number for telephony
communication with the object the vCard represents. communication with the object the vCard represents.
skipping to change at line 679 skipping to change at page 14, line 36
use for the telephone number. The TYPE parameter values can include: use for the telephone number. The TYPE parameter values can include:
"home" to indicate a telephone number associated with a residence, "home" to indicate a telephone number associated with a residence,
"msg" to indicate the telephone number has voice messaging support, "msg" to indicate the telephone number has voice messaging support,
"work" to indicate a telephone number associated with a place of "work" to indicate a telephone number associated with a place of
work, "pref" to indicate a preferred-use telephone number, "voice" to work, "pref" to indicate a preferred-use telephone number, "voice" to
indicate a voice telephone number, "fax" to indicate a facsimile indicate a voice telephone number, "fax" to indicate a facsimile
telephone number, "cell" to indicate a cellular telephone number, telephone number, "cell" to indicate a cellular telephone number,
"video" to indicate a video conferencing telephone number, "pager" to "video" to indicate a video conferencing telephone number, "pager" to
indicate a paging device telephone number, "bbs" to indicate a indicate a paging device telephone number, "bbs" to indicate a
bulletin board system telephone number, "modem" to indicate a MODEM bulletin board system telephone number, "modem" to indicate a MODEM
vCard MIME Directory Profile
connected telephone number, "car" to indicate a car-phone telephone connected telephone number, "car" to indicate a car-phone telephone
number, "isdn" to indicate an ISDN service telephone number, "pcs" to number, "isdn" to indicate an ISDN service telephone number, "pcs" to
indicate a personal communication services telephone number. The indicate a personal communication services telephone number. The
default type is "voice". These type parameter values can be specified default 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 as 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 another (i.e., "TYPE=work,voice"). The default can be overridden to another
set of values by specifying one or more alternate values. For set of values by specifying one or more alternate values. For
example, the default TYPE of "voice" can be reset to a WORK and HOME, example, the default TYPE of "voice" can be reset to a WORK and HOME,
VOICE and FAX telephone number by the value list VOICE and FAX telephone number by the value list
"TYPE=work,home,voice,fax". "TYPE=work,home,voice,fax".
Type example: Type example:
TEL;TYPE=work,voice,pref,msg:+1-213-555-1234 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234
3.3.2 EMAIL Type Definition 3.3.2 EMAIL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type EMAIL Subject: Registration of text/directory MIME type EMAIL
Type name: EMAIL Type name: EMAIL
Type purpose: To specify the electronic mail address for Type purpose: To specify the electronic mail address for
communication with the object the vCard represents. communication with the object the vCard represents.
skipping to change at line 728 skipping to change at page 15, line 37
can also be specified. can also be specified.
Type example: Type example:
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
EMAIL;TYPE=internet:jdoe@isp.net EMAIL;TYPE=internet:jdoe@isp.net
EMAIL;TYPE=internet,pref:jane_doe@abc.com EMAIL;TYPE=internet,pref:jane_doe@abc.com
3.3.3 MAILER Type Definition 3.3.3 MAILER Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type MAILER Subject: Registration of text/directory MIME type MAILER
Type name: MAILER Type name: MAILER
vCard MIME Directory Profile
Type purpose: To specify the type of electronic mail software that is Type purpose: To specify the type of electronic mail software that is
used by the individual associated with the vCard. used by the individual associated with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This information can provide assistance to a Type special notes: This information can provide assistance to a
correspondent regarding the type of data representation which can be correspondent regarding the type of data representation which can be
used, and how they can be packaged. This property is based on the used, and how they can be packaged. This property is based on the
private MIME type X-Mailer that is generally implemented by MIME user private MIME type X-Mailer that is generally implemented by MIME user
agent products. agent products.
Type example: Type example:
MAILER:PigeonMail 2.1 MAILER:PigeonMail 2.1
3.4 Geographical Types 3.4 Geographical Types
These types are concerned with information associated with These types 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.
3.4.1 TZ Type Definition 3.4.1 TZ Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type TZ Subject: Registration of text/directory MIME type TZ
Type name: TZ Type name: TZ
Type purpose: To specify information related to the time zone of the Type purpose: To specify information related to the time zone of the
object the vCard represents. object the vCard represents.
skipping to change at line 785 skipping to change at page 16, line 46
Type special notes: The type value consists of a single value. Type 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.
3.4.2 GEO Type Definition 3.4.2 GEO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type GEO Subject: Registration of text/directory MIME type GEO
vCard MIME Directory Profile
Type name: GEO Type name: GEO
Type purpose: To specify information related to the global Type purpose: To specify information related to the global
positioning of the object the vCard represents. positioning of the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured value consisting of two float values Type value: 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).
Type special notes: This type specifies information related to the Type special notes: This type specifies information related to the
global position of the object associated with the vCard. The value global position of the object associated with the vCard. The value
skipping to change at line 822 skipping to change at page 17, line 32
separated by the SEMI-COLON character (ASCII decimal 59). The simple separated by the SEMI-COLON character (ASCII decimal 59). The simple
formula for converting degrees-minutes-seconds into decimal degrees formula for converting degrees-minutes-seconds into decimal degrees
is: is:
decimal = degrees + minutes/60 + seconds/3600. decimal = degrees + minutes/60 + seconds/3600.
Type example: Type example:
GEO:37.386013;-122.082932 GEO:37.386013;-122.082932
3.5 Organizational Types 3.5 Organizational Types
These types are concerned with information associated with These types 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.
3.5.1 TITLE Type Definition 3.5.1 TITLE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type TITLE Subject: Registration of text/directory MIME type TITLE
Type name: TITLE Type name: TITLE
Type purpose: To specify the job title, functional position or Type purpose: To specify the job title, functional position or
function of the object the vCard represents. function of the object the vCard represents.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: This type is based on the X.520 Title attribute. Type special notes: This type is based on the X.520 Title attribute.
Type example: Type example:
vCard MIME Directory Profile
TITLE:Director\, Research and Development TITLE:Director\, Research and Development
3.5.2 ROLE Type Definition 3.5.2 ROLE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type ROLE Subject: Registration of text/directory MIME type ROLE
Type name: ROLE Type name: ROLE
Type purpose: To specify information concerning the role, occupation, Type purpose: To specify information concerning the role, occupation,
or business category of the object the vCard represents. or business category of the object the vCard represents.
skipping to change at line 876 skipping to change at page 18, line 36
Type special notes: This type is based on the X.520 Business Category Type special notes: This type is based on the X.520 Business Category
explanatory attribute. This property is included as an organizational explanatory attribute. This property is included as an organizational
type to avoid confusion with the semantics of the TITLE type and type to avoid confusion with the semantics of the TITLE type and
incorrect usage of that type when the semantics of this type is incorrect usage of that type when the semantics of this type is
intended. intended.
Type example: Type example:
ROLE:Programmer ROLE:Programmer
3.5.3 LOGO Type Definition 3.5.3 LOGO Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type LOGO Subject: Registration of text/directory MIME type LOGO
Type name: LOGO Type name: LOGO
Type purpose: To specify a graphic image of a logo associated with Type purpose: To specify a graphic image of a logo associated with
the object the vCard represents. the object the vCard represents.
skipping to change at line 903 skipping to change at page 19, line 16
be reset to uri value. The uri value can be used to specify a value be reset to uri value. The uri value can be used to specify a value
outside of this MIME entity. outside of this MIME entity.
Type special notes: The type can include the type parameter "TYPE" to Type special notes: The type can include the type parameter "TYPE" to
specify the graphic image format type. The TYPE parameter values MUST specify the graphic image format type. The TYPE parameter values MUST
be one of the IANA registered image formats or a non-standard image be one of the IANA registered image formats or a non-standard image
format. format.
Type example: Type example:
vCard MIME Directory Profile
LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg
LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
3.5.4 AGENT Type Definition 3.5.4 AGENT Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type AGENT Subject: Registration of text/directory MIME type AGENT
Type name: AGENT Type name: AGENT
Type purpose: To specify information about another person who will Type purpose: To specify information about another person who will
act on behalf of the individual or resource associated with the act on behalf of the individual or resource associated with the
vCard. vCard.
skipping to change at line 944 skipping to change at page 20, line 8
represents somebody or something that is separately addressable. represents somebody or something that is separately addressable.
Type example: Type example:
AGENT;VALUE=uri: AGENT;VALUE=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555- AGENT:BEGIN:VCARD\nFN:Susan Thomas\nTEL:+1-919-555-
1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n 1234\nEMAIL\;INTERNET:sthomas@host.com\nEND:VCARD\n
3.5.5 ORG Type Definition 3.5.5 ORG Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type ORG Subject: Registration of text/directory MIME type ORG
Type name: ORG Type name: ORG
Type purpose: To specify the organizational name and units associated Type purpose: To specify the organizational name and units associated
with the vCard. with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single structured text value consisting of components Type value: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59). separated the SEMI-COLON character (ASCII decimal 59).
vCard MIME Directory Profile
Type special notes: The type is based on the X.520 Organization Name Type special notes: The type is based on the X.520 Organization Name
and Organization Unit attributes. The type value is a structured type and Organization Unit attributes. The type value is a structured type
consisting of the organization name, followed by one or more levels consisting of the organization name, followed by one or more levels
of organizational unit names. of organizational unit names.
Type example: A type value consisting of an organizational name, Type example: A type 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
3.6 Explanatory Types 3.6 Explanatory Types
These types are concerned with additional explanations, such as that These types are concerned with additional explanations, such as that
related to informational notes or revisions specific to the vCard. related to informational notes or revisions specific to the vCard.
3.6.1 CATEGORIES Type Definition 3.6.1 CATEGORIES Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type CATEGORIES Subject: Registration of text/directory MIME type CATEGORIES
Type name: CATEGORIES Type name: CATEGORIES
Type purpose: To specify application category information about the Type purpose: To specify application category information about the
vCard. vCard.
skipping to change at line 989 skipping to change at page 21, line 4
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type CATEGORIES Subject: Registration of text/directory MIME type CATEGORIES
Type name: CATEGORIES Type name: CATEGORIES
Type purpose: To specify application category information about the Type purpose: To specify application category information about the
vCard. vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: One or more text values separated by a COMMA character Type value: One or more text values separated by a COMMA character
(ASCII decimal 44). (ASCII decimal 44).
Type example: Type example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
3.6.2 NOTE Type Definition 3.6.2 NOTE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type NOTE Subject: Registration of text/directory MIME type NOTE
Type name: NOTE Type name: NOTE
Type purpose: To specify supplemental information or a comment that Type purpose: To specify supplemental information or a comment that
is associated with the vCard. is associated with the vCard.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: The type is based on the X.520 Description Type special notes: The type is based on the X.520 Description
attribute. attribute.
vCard MIME Directory Profile
Type example: Type 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.
3.6.3 PRODID Type Definition 3.6.3 PRODID Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type PRODID Subject: Registration of text/directory MIME type PRODID
Type name: PRODID Type name: PRODID
Type purpose: To specify the identifier for the product that created Type purpose: To specify the identifier for the product that created
the vCard object. the vCard object.
skipping to change at line 1047 skipping to change at page 22, line 13
Type value: A single text value. Type value: A single text value.
Type special notes: Implementations SHOULD use a method such as that Type special notes: Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in ISO 9070 to assure that specified for Formal Public Identifiers in ISO 9070 to assure that
the text value is unique. the text value is unique.
Type example: Type example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
3.6.4 REV Type Definition 3.6.4 REV Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type REV Subject: Registration of text/directory MIME type REV
Type name: REV Type name: REV
Type purpose: To specify revision information about the current Type purpose: To specify revision information about the current
vCard. vCard.
skipping to change at line 1072 skipping to change at page 22, line 38
Type special notes: The value distinguishes the current revision of Type special notes: The value distinguishes the current revision of
the information in this vCard for other renditions of the the information in this vCard for other renditions of the
information. information.
Type example: Type example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
REV:1997-11-15 REV:1997-11-15
vCard MIME Directory Profile
3.6.5 SORT-STRING Type Definition 3.6.5 SORT-STRING Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type SORT-STRING Subject: Registration of text/directory MIME type SORT-STRING
Type Name: SORT-STRING Type Name: SORT-STRING
Type purpose: To specify the text to be used in national language Type purpose: To specify the family name or given name text to be
specific sorting of the values specified by the FN or N types. used for national-language-specific sorting of the FN and N types.
Type encoding: 8bit Type encoding: 8bit
Type value: A single text value. Type value: A single text value.
Type special notes: The sort string is used to provide text that is Type special notes: The sort string is used to provide family name or
to be used in locale- or national language-specific sorting of the given name text that is to be used in locale- or national-language-
values for the formatted name or structured name types. Without this specific sorting of the formatted name and structured name types.
information, sorting algorithms could incorrectly sort this vCard Without this information, sorting algorithms could incorrectly sort
within a sequence of sorted vCards. If this type is present in a this vCard within a sequence of sorted vCards. When this type is
vCard, then this value should be used for sorting the vCard, instead present in a vCard, then this family name or given name value is used
of the values of the FN or N types. for sorting the vCard.
Type example: The following would define the sort string "Harten" for Type examples: For the case of family name sorting, the following
the "FN:Rene J. van der Harten" or "N:van der examples define common sort string usage with the FN and N types.
Harten;Rene;J.;Sir;R.D.O.N.".
FN:Rene van der Harten
N:van der Harten;Rene;J.;Sir;R.D.O.N.
SORT-STRING:Harten SORT-STRING:Harten
3.6.6 SOUND Type Definition FN:Robert Pau Shou Chang
N:Pau;Shou Chang;Robert
SORT-STRING:Pau
FN:Osamu Koura
N:Koura;Osamu
SORT-STRING:Koura
FN:Oscar del Pozo
N:del Pozo Triscon;Oscar
SORT-STRING:Pozo
FN:Chistine d'Aboville
N:d'Aboville;Christine
SORT-STRING:Aboville
3.6.6 SOUND Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type SOUND Subject: Registration of text/directory MIME type SOUND
Type name: SOUND Type name: SOUND
Type purpose: To specify a digital sound content information that Type purpose: To specify a digital sound content information that
annotates some aspect of the vCard. By default this type is used to annotates some aspect of the vCard. By default this type is used to
specify the proper pronunciation of the name type value of the vCard. specify the proper pronunciation of the name type value of the vCard.
skipping to change at line 1128 skipping to change at page 24, line 13
is used and no explicit ENCODING parameter is needed. is used and no explicit ENCODING parameter is needed.
Type value: A single value. The default is binary value. It can also Type value: A single value. The default is binary value. It can also
be reset to uri value. The uri value can be used to specify a value be reset to uri value. The uri value can be used to specify a value
outside of this MIME entity. outside of this MIME entity.
Type special notes: The type can include the type parameter "TYPE" to Type special notes: The type can include the type parameter "TYPE" to
specify the audio format type. The TYPE parameter values MUST be one specify the audio format type. The TYPE parameter values MUST be one
of the IANA registered audio formats or a non-standard audio format. of the IANA registered audio formats or a non-standard audio format.
vCard MIME Directory Profile
Type example: Type example:
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8. SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com 19960229T080000.xyzMail@host1.com
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...> <...the remainder of "B" encoded binary data...>
3.6.7 UID Type Definition 3.6.7 UID Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type UID Subject: Registration of text/directory MIME type UID
Type name: UID Type name: UID
Type purpose: To specify a value that represents a globally unique Type 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.
skipping to change at line 1168 skipping to change at page 25, line 5
The type can include the type parameter "TYPE" to specify the format The type can include the type parameter "TYPE" to specify the format
of the identifier. The TYPE parameter value should be an IANA of the identifier. The TYPE parameter value should be an IANA
registered identifier format. The value can also be a non-standard registered identifier format. The value can also be a non-standard
format. format.
Type example: Type example:
UID:19950401-080045-40000F192713-0052 UID:19950401-080045-40000F192713-0052
3.6.8 URL Type Definition 3.6.8 URL Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type URL Subject: Registration of text/directory MIME type URL
Type name: URL Type name: URL
Type purpose: To specify a uniform resource locator associated with Type purpose: To specify a uniform resource locator associated with
the object that the vCard refers to. the object that the vCard refers to.
Type encoding: 8bit Type encoding: 8bit
Type value: A single uri value. Type value: A single uri value.
Type example: Type example:
vCard MIME Directory Profile
URL:http://www.swbyps.restaurant.french/~chezchic.html URL:http://www.swbyps.restaurant.french/~chezchic.html
3.6.9 VERSION Type Definition 3.6.9 VERSION Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type VERSION Subject: Registration of text/directory MIME type VERSION
Type name: VERSION Type name: VERSION
Type purpose: To specify the version of the vCard specification used Type purpose: To specify the version of the vCard specification used
to format this vCard. to format this vCard.
skipping to change at line 1212 skipping to change at page 25, line 47
Type value: A single text value. Type value: A single text value.
Type special notes: The property MUST be present in the vCard object. Type special notes: The property MUST be present in the vCard object.
The value MUST be "3.0" if the vCard corresponds to this The value MUST be "3.0" if the vCard corresponds to this
specification. specification.
Type example: Type example:
VERSION:3.0 VERSION:3.0
3.7 Security Types 3.7 Security Types
These types are concerned with the security of communication pathways These types are concerned with the security of communication pathways
or access to the vCard. or access to the vCard.
3.7.1 CLASS Type Definition 3.7.1 CLASS Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type CLASS Subject: Registration of text/directory MIME type CLASS
Type name: CLASS Type name: CLASS
Type purpose: To specify the access classification for a vCard Type purpose: To specify the access classification for a vCard
object. object.
skipping to change at line 1240 skipping to change at page 26, line 28
Type value: A single text value. Type value: A single text value.
Type special notes: An access classification is only one component of Type special notes: An access classification is only one component of
the general security model for a directory service. The the general security model for a directory service. The
classification attribute provides a method of capturing the intent of classification attribute provides a method of capturing the intent of
the owner for general access to information described by the vCard the owner for general access to information described by the vCard
object. object.
Type examples: Type examples:
CLASS:PUBLIC CLASS:PUBLIC
vCard MIME Directory Profile
CLASS:PRIVATE CLASS:PRIVATE
CLASS:CONFIDENTIAL CLASS:CONFIDENTIAL
3.7.2 KEY Type Definition 3.7.2 KEY Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of text/directory MIME type KEY Subject: Registration of text/directory MIME type KEY
Type name: KEY Type name: KEY
Type purpose: To specify a public key or authentication certificate Type 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.
skipping to change at line 1291 skipping to change at page 27, line 29
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2 EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7 rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ== UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
3.8 Extended Types 3.8 Extended Types
The types defined by this document can be extended with private types The types defined by this document can be extended with private types
using the non-standard, private values mechanism defined in [RFC using the non-standard, private values mechanism defined in [RFC
2045]. Non-standard, private types with a name starting with "X-" may 2045]. Non-standard, private types with a name starting with "X-" may
vCard MIME Directory Profile
be defined bilaterally between two cooperating agents without outside be defined bilaterally between two cooperating agents without outside
registration or standardization. registration or standardization.
4. Formal Grammar 4. Formal Grammar
The following formal grammar is provided to assist developers in The following formal grammar is provided to assist developers in
building parsers for the vCard. building parsers for the vCard.
This syntax is written according to the form described in RFC 2234, This syntax is written according to the form described in RFC 2234,
but it references just this small subset of RFC 2234 literals: but it references just this small subset of RFC 2234 literals:
;******************************************* ;*******************************************
; Commonly Used Literal Definition ; Commonly Used Literal Definition
;******************************************* ;*******************************************
skipping to change at line 1350 skipping to change at page 28, line 38
; Horizontal Tabulation ; Horizontal Tabulation
SP = %x20 SP = %x20
; space ; space
VCHAR = %x21-7E VCHAR = %x21-7E
; Visible (printing) characters ; Visible (printing) characters
WSP = SP / HTAB WSP = SP / HTAB
; White Space ; White Space
vCard MIME Directory Profile
;******************************************* ;*******************************************
; Basic vCard Definition ; Basic vCard Definition
;******************************************* ;*******************************************
vcard_entity = 1*(vcard) vcard_entity = 1*(vcard)
vcard = [group "."] "BEGIN" ":" "VCARD" 1*CRLF vcard = [group "."] "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 line 1404 skipping to change at page 29, line 42
NON-ASCII = %x80-FF NON-ASCII = %x80-FF
; Use is restricted by CHARSET parameter ; Use is restricted by CHARSET parameter
; on outer MIME object (UTF-8 preferred) ; on outer MIME object (UTF-8 preferred)
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE ; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":", "," ; Any character except CTLs, DQUOTE, ";", ":", ","
vCard MIME Directory Profile
VALUE-CHAR = WSP / VCHAR / NON-ASCII VALUE-CHAR = WSP / VCHAR / NON-ASCII
; Any textual character ; Any textual character
;******************************************* ;*******************************************
; vCard Type Definition ; vCard Type Definition
; ;
; Provides type-specific definitions for how the ; Provides type-specific definitions for how the
; "value" and "param" are defined. ; "value" and "param" are defined.
;******************************************* ;*******************************************
skipping to change at line 1450 skipping to change at page 30, line 38
;For name="FN" ;For name="FN"
;This type MUST be included in a vCard object. ;This type MUST be included in a vCard object.
param = text-param param = text-param
; Text parameters allowed ; Text parameters allowed
value = text-value value = text-value
;For name="N" ;For name="N"
;This type MUST be included in a vCard object. ;This type MUST be included in a vCard object.
param = text-param param = text-param
; Text parameters allowed ; Text parameters allowed
value = n-value value = n-value
n-value = 0*4(text-value *("," text-value) ";") n-value = 0*4(text-value *("," text-value) ";")
text-value *("," text-value) text-value *("," text-value)
; Family; Given; Middle; Prefix; Suffix. ; Family; Given; Middle; Prefix; Suffix.
; Example: Public;John;Quincy,Adams;Reverend Dr. III ; Example: Public;John;Quincy,Adams;Reverend Dr. III
vCard MIME Directory Profile
;For name="NICKNAME" ;For name="NICKNAME"
param = text-param param = text-param
; Text parameters allowed ; Text parameters allowed
value = text-list value = text-list
;For name="PHOTO" ;For name="PHOTO"
param = img-inline-param param = img-inline-param
; Only image parameters allowed ; Only image parameters allowed
skipping to change at line 1512 skipping to change at page 32, line 4
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 = phone-number-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"
vCard MIME Directory Profile
/ "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
value = text-value value = text-value
email-param = "TYPE" "=" email-type ["," "PREF"] email-param = "TYPE" "=" email-type ["," "PREF"]
skipping to change at line 1571 skipping to change at page 33, line 12
;For name="LOGO" ;For name="LOGO"
param = img-inline-param / img-refer-param param = img-inline-param / img-refer-param
; Only image parameters allowed ; Only image parameters allowed
value = img-inline-value / img-refer-value value = img-inline-value / img-refer-value
; Value and parameter MUST match ; Value and parameter MUST match
;For name="AGENT" ;For name="AGENT"
param = agent-inline-param param = agent-inline-param
vCard MIME Directory Profile
param =/ agent-refer-param param =/ agent-refer-param
value = agent-inline-value value = agent-inline-value
; Value and parameter MUST match ; Value and parameter MUST match
value =/ agent-refer-value value =/ agent-refer-value
; Value and parameter MUST match ; Value and parameter MUST match
agent-inline-param = "" agent-inline-param = ""
skipping to change at line 1628 skipping to change at page 34, line 20
value = text-value value = text-value
;For name="REV" ;For name="REV"
param = ["VALUE" =" "date-time"] param = ["VALUE" =" "date-time"]
; Only value parameters allowed. Values are case insensitive. ; Only value parameters allowed. Values are case insensitive.
param =/ "VALUE" =" "date" param =/ "VALUE" =" "date"
; Only value parameters allowed. Values are case insensitive. ; Only value parameters allowed. Values are case insensitive.
vCard MIME Directory Profile
value = date-time-value value = date-time-value
value =/ date-value value =/ date-value
;For name="SORT-STRING" ;For name="SORT-STRING"
param = text-param param = text-param
; Only text parameters allowed ; Only text parameters allowed
value = text-value value = text-value
skipping to change at line 1684 skipping to change at page 35, line 25
;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
vCard MIME Directory Profile
value = text-value value = text-value
; Value MUST be "3.0" ; Value MUST be "3.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
skipping to change at line 1740 skipping to change at page 36, line 31
langval = <a language string as defined in RFC 1766> langval = <a language string as defined in RFC 1766>
img-inline-value = binary-value img-inline-value = binary-value
;Value MUST be "b" encoded image content ;Value MUST be "b" encoded image content
img-inline-param img-inline-param
img-inline-param = ("VALUE" "=" "binary") img-inline-param = ("VALUE" "=" "binary")
/ ("ENCODING" "=" "b") / ("ENCODING" "=" "b")
vCard MIME Directory Profile
/ ("TYPE" "=" param-value / ("TYPE" "=" param-value
;TYPE value MUST be an IANA registered image type ;TYPE value MUST be an IANA registered image type
img-refer-value = uri img-refer-value = uri
;URI MUST refer to image content of given type ;URI MUST refer to image content of given type
img-refer-param = ("VALUE" "=" "uri") img-refer-param = ("VALUE" "=" "uri")
/ ("TYPE" "=" param-value) / ("TYPE" "=" param-value)
;TYPE value MUST be an IANA registered image type ;TYPE value MUST be an IANA registered image type
skipping to change at line 1792 skipping to change at page 37, line 35
float-value = <A single float value as defined in [MIME-DIR]> float-value = <A single float value as defined in [MIME-DIR]>
phone-number-value = <A single text value as defined in [CCITT phone-number-value = <A single text value as defined in [CCITT
E.163] and [CCITT X.121]> E.163] and [CCITT X.121]>
uri-value = <A uri value as defined in [MIME-DIR]> uri-value = <A uri value as defined in [MIME-DIR]>
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
vCard MIME Directory Profile
5. Differences From vCard v2.1 5. Differences From vCard v2.1
This specification has been reviewed by the IETF community. The This specification has been reviewed by the IETF community. The
review process introduced a number of differences from the [VCARD] review process introduced a number of differences from the [VCARD]
version 2.1. These differences require that vCard objects conforming version 2.1. These differences require that vCard objects conforming
to this specification have a different version number than a vCard to this specification have a different version number than a vCard
conforming to [VCARD]. The differences include the following: conforming to [VCARD]. The differences include the following:
. The QUOTED-PRINTABLE inline encoding has been eliminated. . The QUOTED-PRINTABLE inline encoding has been eliminated.
Only the "B" encoding of [RFC 2047] is an allowed value for Only the "B" encoding of [RFC 2047] is an allowed value for
the ENCODING parameter. the ENCODING parameter.
skipping to change at line 1848 skipping to change at page 38, line 42
line after the encoded binary content is no longer required. line after the encoded binary content is no longer required.
. TEL values can be identified as personal communication . TEL values can be identified as personal communication
services telephone numbers with the PCS type parameter value. services telephone numbers with the PCS type parameter value.
. The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types . The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
have been added. have been added.
. The VERSION, N and FN types MUST be specified in a vCard. . The VERSION, N and FN types MUST be specified in a vCard.
This identifies the version of the specification that the This identifies the version of the specification that the
vCard MIME Directory Profile
object was formatted to. It also assures that every vCard object was formatted to. It also assures that every vCard
will include both a structured and formatted name that can be will include both a structured and formatted name that can be
used to identify the object. used to identify the object.
6. Acknowledgements 6. Acknowledgements
The many valuable comments contributed by members of the IETF ASID The many valuable comments contributed by members of the IETF ASID
working group are gratefully acknowledged, as are the contributions working group are gratefully acknowledged, as are the contributions
by Roland Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce by Roland Alden, Stephen Bartlett, Alec Dun, Patrik Faltstrom, Daniel
Johnston, Daniel Klaussen, Vinod Seraphin, Michelle Watkins. Chris Gurney, Bruce Johnston, Daniel Klaussen, Pete Miller, Keith Moore,
Newman was especially helpful in navigating the intricacies of ABNF Vinod Seraphin, Michelle Watkins. Chris Newman was especially helpful
lore. in navigating the intricacies of ABNF lore.
7. Authors' Addresses 7. Authors' Addresses
BEGIN:vCard BEGIN:vCard
VERSION:3.0 VERSION:3.0
FN:Frank Dawson FN:Frank Dawson
ORG:Lotus Development Corporation ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
;Raleigh;NC;27613-3502;U.S.A. ;Raleigh;NC;27613-3502;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515 TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
TEL;TYPE=FAX,WORK:+1-919-676-9564 TEL;TYPE=FAX,WORK:+1-919-676-9564
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
skipping to change at line 1889 skipping to change at page 39, line 40
VERSION:3.0 VERSION:3.0
FN:Tim Howes FN:Tim Howes
ORG:Netscape Communications Corp. ORG:Netscape Communications Corp.
ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View; ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A. CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164 TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard END:vCard
8. Security 8. Security Considerations
vCards can carry cryptographic keys or certificates, as described in vCards can carry cryptographic keys or certificates, as described in
Section 3.7.2. Section 3.7.2.
Section 3.7.1 specifies a desired security classification policy for Section 3.7.1 specifies a desired security classification policy for
a particular vCard. That policy is not enforced in any way. a particular vCard. That policy is not enforced in any way.
The vCard objects have no inherent authentication or privacy, but can The vCard objects have no inherent authentication or privacy, but can
easily be carried by any security mechanism that transfers MIME easily be carried by any security mechanism that transfers MIME
objects with authentication or privacy. In cases where threats of objects with authentication or privacy. In cases where threats of
"spoofed" vCard information is a concern, the vCard SHOULD BE "spoofed" vCard information is a concern, the vCard SHOULD BE
transported using one of these secure mechanisms. transported using one of these secure mechanisms.
vCard MIME Directory Profile
The information in a vCard may become out of date. In cases where the 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 "URL" vitality of data is important to an originator of a vCard, the "URL"
type described in section 3.6.8 SHOULD BE specified. In addition, the type described in section 3.6.8 SHOULD BE specified. In addition, the
"REV" type described in section 3.6.4 can be specified to indicate "REV" type described in section 3.6.4 can be specified to indicate
the last time that the vCard data was updated. the last time that the vCard data was updated.
9. authentication or privacy. 9. References
10. References
The following documents are referenced by this work.
[ISO 8601] ISO 8601:1988 - Data elements and interchange formats - [ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and times - The Information interchange - Representation of dates and
International Organization for Standardization, June, 1988. times - The International Organization for
Standardization, June, 1988.
[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange - Representation of interchange formats - Information interchange -
dates and times - The International Organization for Standardization, Representation of dates and times - The International
May, 1991. Organization for Standardization, May, 1991.
[ISO 9070] ISO 9070, Information Processing - SGML support facilities [ISO 9070] ISO 9070, Information Processing - SGML support
- Registration Procedures for Public Text Owner Identifiers, April, facilities - Registration Procedures for Public Text
1991. Owner Identifiers, April, 1991.
[CCITT E.163] Recommendation E.163 - Numbering Plan for The [CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. International Telephone Service, CCITT Blue Book,
128-134, November, 1988. Fascicle II.2, pp. 128-134, November, 1988.
[CCITT X.121] Recommendation X.121 - International Numbering Plan for [CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
November, 1988. pp. 317-332, November, 1988.
[CCITT X.520] Recommendation X.520 - The Directory - Selected [CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988. Attribute Types, November 1988.
[CCITT X.521] Recommendation X.521 - The Directory - Selected Object [CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988. Classes, November 1988.
[MIME-DIR] Howes, T., Smith, M., Dawson, F. "A MIME Content-Type for
Directory Information", RFC xxxx, April 1998.
[RFC 1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform [MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Resource Locators (URL)", RFC 1738, December 1994. Type for Directory Information", RFC 2425, September
1998.
[RFC 1766] Alvestrand, H., "Tags for the Identification of [RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
Languages", March 1995. "Uniform Resource Locators (URL)", RFC 1738, December
1994.
[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-type," [RFC 1766] Alvestrand, H., "Tags for the Identification of
RFC 1872, December 1995. Languages", RFC 1766, March 1995.
[RFC 2045] Freed, N., Borenstein, N., "Multipurpose Internet Mail [RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC type", RFC 1872, December 1995.
2045, November 1996.
vCard MIME Directory Profile [RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.
[RFC 2046] Freed, N., Borenstein, N., "Multipurpose Internet Mail [RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996. Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.
[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) - [RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, (MIME) - Part Three: Message Header Extensions for
November 1996. Non-ASCII Text", RFC 2047, November 1996.
[RFC 2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet [RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Mail Extensions (MIME) - Part Four: Registration Procedures", RFC Internet Mail Extensions (MIME) - Part Four:
2048, January 1997. Registration Procedures", RFC 2048, January 1997.
[RFC 2119] "Key words for use in RFCs to Indicate Requirement [RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Levels", RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC 2234] Crocker, D., Overell, P., "Augmented BNF for Syntax [RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[UNICODE] "The Unicode Standard - Version 2.0", The Unicode [UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996. Consortium, July 1996.
[VCARD] Internet Mail Consortium, "vCard - The Electronic Business [VCARD] Internet Mail Consortium, "vCard - The Electronic
Card Version 2.1", http://www.imc.org/pdi/vcard-21.txt, September 18, Business Card Version 2.1",
1996. http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
11. Full Copyright Statement 10. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it MAY be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation MAY be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself MAY not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process MUST be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
 End of changes. 148 change blocks. 
317 lines changed or deleted 248 lines changed or added

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