draft-ietf-asid-mime-vcard-02.txt   draft-ietf-asid-mime-vcard-03.txt 
Network Working Group Frank Dawson Network Working Group Frank Dawson
INTERNET DRAFT Tim Howes INTERNET DRAFT Tim Howes
ietf-asid-mime-vcard-02.txt Lotus/Netscape Communications ietf-asid-mime-vcard-03.txt Lotus/Netscape Communications
March 26, 1997 July 30, 1997
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 is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
skipping to change at line 58 skipping to change at line 58
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
has augmented the basic attributes defined in the X.500 series has augmented the basic attributes defined in the X.500 series
recommendation in order to provide for an electronic representation recommendation in order to provide for an electronic representation
of the information commonly found on a paper business card. This of the information commonly found on a paper business card. This
Dawson & Howes [Page 1] Expires September 1997 Dawson & Howes [Page 1] ExpiresJanuary 1998
vCard MIME Directory Profile vCard MIME Directory Profile
schema was first defined in the [VCARD] document. Hence, this [MIME- schema was first defined in the [VCARD] document. Hence, this [MIME-
DIR] profile is referred to as the vCard MIME Directory Profile. DIR] profile is referred to as the vCard MIME Directory Profile.
A directory entry based on this usage profile can include traditional A directory entry based on this usage profile can include traditional
directory, white-pages information such as the distinguished name directory, white-pages information such as the distinguished name
used to uniquely identify the entry, a formatted representation of used to uniquely identify the entry, a formatted representation of
the name used for user-interface or presentation purposes, both the the name used for user-interface or presentation purposes, both the
skipping to change at line 96 skipping to change at line 96
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].
2. The vCard Mime Directory Profile Registration 2. 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@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME profile VCARD Subject: Registration of application/directory MIME profile VCARD
Profile name: VCARD Profile name: VCARD
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 types used: SOURCE, NAME, PROFILE, BEGIN, Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
END, PROFILE. END, PROFILE.
Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET, Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT. LANGUAGE, CONTEXT.
New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ, New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ,
GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV, SOUND, URL, UID, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORY, NOTE, PRODID, REV,
VERSION, KEY SOUND, URL, UID, VERSION, CLASS, KEY
Dawson & Howes [Page 2] Expires September 1997 Dawson & Howes [Page 2] Expires January 1998
vCard MIME Directory Profile vCard MIME Directory Profile
New parameters: TYPE New parameters: TYPE
Profile special notes: The type-grouping feature of [MIME-DIR] is Profile special notes: The type-grouping feature of [MIME-DIR] is
supported by this profile to group related vCard properties about a supported by this profile to group related vCard properties about a
directory entry. For example, vCard properties describing WORK or directory entry. For example, vCard properties describing WORK or
HOME related characteristics MAY be grouped with a unique group HOME related characteristics MAY be grouped with a unique group
label. 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.
3. MIME Directory Features 3. 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 sub-sections describe specific defined by [MIME-DIR]. The following sections either clarify or
usage constraints or extensions of these predefined features. extend the content-type definition of [MIME-DIR].
3.1 BEGIN and END Type 3.1 Predefined Type Usage
The vCard MIME Directory Profile uses the following predefined types
from [MIME-DIR].
3.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 of VCARD. The content entity MUST end with the END type with a value of
VCARD. VCARD.
3.2 NAME Type 3.1.2 NAME Type
If the NAME type appears within a MIME entity conforming to this If the NAME type appears within a MIME entity conforming to this
profile, it's value is the displayable, presentation text associated profile, it's value is the displayable, presentation text associated
with the source for the vCard, as specified in the SOURCE type. with the source for the vCard, as specified in the SOURCE type.
3.3 PROFILE Type 3.1.3 PROFILE Type
If the PROFILE type appears within a MIME entity conforming to this If the PROFILE type appears within a MIME entity conforming to this
profile, it's value must be "VCARD". profile, its value must be "VCARD".
3.4 SOURCE Type 3.1.4 SOURCE Type
If the SOURCE type appears within a MIME entity conforming to this If the SOURCE type appears within a MIME entity conforming to this
profile, it's value provides information how to find the source for profile, it's value provides information how to find the source for
the vCard. the vCard.
3.5 ENCODING Parameter 3.2 Predefined Type Parameter Usage
The default transfer encoding for the vCard profile is "8bit". The The vCard MIME Directory Profile uses the following predefined types
default transfer encoding MAY be overridden for an individual type parameters as defined by [MIME-DIR].
value by using the "ENCODING" type parameter. The parameter value can
be reset to either "7bit", "base64" or "quoted-printable". This type
parameter MAY be used on any type, unless specified otherwise by the
profile type registration.
Dawson & Howes [Page 3] Expires September 1997 Dawson & Howes [Page 3] Expires January 1998
vCard MIME Directory Profile vCard MIME Directory Profile
3.6 CHARSET Parameter · LANGUAGE
The default character set for the vCard profile is "UTF-8". The
default transfer encoding MAY be overridden for an individual type
value by using the "CHARSET" type parameter. The parameter value MAY
be reset to any IANA registered character set. This type parameter
MAY be used on any type, unless specified otherwise by the profile
type registration.
3.7 LANGUAGE
The default language for the vCard profile is "en-US" (US English).
The default language MAY be overridden for an individual type value
by using the "LANGUAGE" type parameter. The prameter value MAY be
reset to any IANA registered language. This type parameter MAY be
used on any type, unless specified otherwise by the profile type
registration.
3.8 Line Endings
The usual line-folding technique described in [MIME-DIR] can be used
to represent type values consisting of long lines of text.
A formatted text line break in a type value, MUST be specified by a
(RFC 822) line break, which is a CRLF sequence. However, since the
CRLF sequence is used to delimit a line, type values with formatted
line breaks (i.e., multiple lines) MUST be encoded using the Quoted-
Printable encoding.
For example, in the Quoted-Printable encoding the multiple lines of
formatted text are separated with a Quoted-Printable CRLF sequence of
"=0D" followed by "=0A" followed by a Quoted-Printable soft line
break sequence of "=". Quoted-Printable lines of text must also be
limited to less than 76 characters. The 76 characters does not
include the CRLF [RFC 822] line break sequence. For example a
multiple line LABEL value of:
Mr. John Q. Public
123 Main Street
Any Town, CA 12345
Would be represented in a Quoted-Printable encoding as:
LABEL;ENCODING=QUOTED-PRINTABLE:Mr. John Q. Public=0D=0A=
123 Mail Street=0D=0A=
Any Town, CA 12345
3.9 Structured Type Values
Compound property values are delimited by a field delimiter,
specified by the SEMI-COLON character (ASCII decimal 59). A SEMI-
COLON in a component of a compound property value must be escaped
with a Backslash character
Dawson & Howes [Page 4] Expires September 1997
vCard MIME Directory Profile
This profile supports the type grouping mechanism defined in [MIME- · ENCODING
DIR]. Grouping of related types is a useful technique to communicate
common semantics concerning the properties of a vCard.
4. vCard Features · VALUE
4.1 VALUE Type Parameter 3.3 VALUE Type Parameter Extensions
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.
4.1.1 BINARY 3.3.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 may be specified in the PHOTO, encoded binary data. This value type may 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. parameter must be used to specify the encoding format.
The value type is defined by the following notation: The value type is defined by the following notation:
binchar = <Any character valid in the base64 or quoted-printable binchar = <Any character valid in the base64 or quoted-printable
encoding> encoding>
binary = *binchar ;A base64 or quoted-printable binary = *binchar ;A base64 or quoted-printable
encoding of the binary information encoding of the binary information
4.1.2 VCARD 3.3.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 may be specified in the AGENT type. The value vCard. This value type may be specified in the AGENT type. The value
type is defined by this specification. type is defined by this specification.
4.1.3 PHONE-NUMBER 3.3.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 may be specified in the TEL type. telephone number. This value type may be specified in the TEL type.
The value type is a text value that has the semantics of a telephone The value type is a text value that has the semantics of a telephone
number. number.
4.1.4 UTC-OFFSET 3.3.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 may be specified in the TZ type. offset from UTC. This value type may be specified in the TZ type.
The format of the offset from UTC is defined by [DATETIME]. The value The format of the offset from UTC is defined by [DATETIME]. The value
type is an offset from Coordinated Universal Time (UTC). It is type is an offset from Coordinated Universal Time (UTC). It is
specified as a positive or negative difference in units of hours and 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. minutes (e.g., +hh:mm). The time is specified as a 24-hour clock.
Hour values are from 00 to 24, 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
Dawson & Howes [Page 5] Expires September 1997 Dawson & Howes [Page 4] Expires January 1998
vCard MIME Directory Profile vCard MIME Directory Profile
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-24 time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-60 time-minute = 2DIGIT ;00-59
time-numzone = ("+" / "-") time-hour ":" time-minute utc-offset = ("+" / "-") time-hour ":" time-minute
utc-offset = time-numzone
4.2 Identification Types 3.4 Structured Type Values
Compound type values are delimited by a field delimiter, specified by
the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a
component of a compound property value must be escaped with a
BACKSLASH character (ASCII decimal 92).
Lists of values are delimited by a list delimiter, specified by the
COMMA character (ASCII decimal 44). A COMMA character in a value must
be escaped with a BACKSLASH character (ASCII decimal 92).
This profile supports the type grouping mechanism defined in [MIME-
DIR]. Grouping of related types is a useful technique to communicate
common semantics concerning the properties of a vCard.
4. vCard Profile Features
The vCard MIME Directory Profile Type contains directory information,
typically pertaining to a single directory entry. The information is
described using an attribute schema that is tailored for capturing
personal contact information. The vCard can include attributes that
describe identification, delivery addressing, telecommunications
addressing, geographical, organizational, general explanatory and
security and access information about the particular object
associated with the vCard.
4.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.
4.2.1 FN Type Definition 4.1.1 FN Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type FN Subject: Registration of application/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.
Dawson & Howes [Page 5] Expires January 1998
vCard MIME Directory Profile
Type encoding: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
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. Common Name attribute.
Type example: Type example:
FN:Mr. John Q. Public, Esq. FN:Mr. John Q. Public, Esq.
4.2.2 N Type Definition 4.1.2 N Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type N Subject: Registration of application/directory MIME type N
Type name: N Type name: N
Type purpose: To specify the structured components of the name of the Type purpose: To specify the structured components of the name of the
object the vCard represents. object the vCard represents.
Type encoding: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
Dawson & Howes [Page 6] Expires September 1997
vCard MIME Directory Profile
Type special note: The type value is structured text corresponding, Type special note: The type value is structured text corresponding,
in sequence, to the Family Name, Given Name, Additional Names, in sequence, to the Family Name, Given Name, Additional Names,
Honorific Prefixes, and Honorific Suffixes. The text components are Honorific Prefixes, and Honorific Suffixes. The text components are
delimited by the SEMI-COLON character (ASCII decimal 59) and possibly delimited by the SEMI-COLON character (ASCII decimal 59) and possibly
one or more LWSP. This type is based on the semantics of the X.520 one or more LWSP. This type is based on the semantics of the X.520
individual name attributes. individual name attributes.
Type example: Type example:
N:Public;John;Quinlan;Mr.;Esq. N:Public;John;Quinlan;Mr.;Esq.
4.2.3 PHOTO Type Definition 4.1.3 PHOTO Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type PHOTO Subject: Registration of application/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.
Type encoding: The default is 8bit. May also be reset to base64 in Type encoding: The default is 8bit. May also be reset to base64 in
order to permit inline, encoded binary data. order to permit inline, encoded binary data.
Dawson & Howes [Page 6] Expires January 1998
vCard MIME Directory Profile
Type value: The default is binary. It may also be reset to url. The Type value: The default is binary. It may also be reset to url. The
url value may be used to specify a value outside of this MIME entity. url value may be used to specify a value outside of this MIME entity.
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY 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. In addition, a non- be one of the IANA registered image formats or a non-standard image
standard image format MAY be specified. format.
Type example: Type example:
PHOTO;VALUE=url:=http://www.abc.com/pub/photos PHOTO;VALUE=url:=http://www.abc.com/pub/photos
/jqpublic.gif /jqpublic.gif
4.2.4 BDAY Type Definition 4.1.4 BDAY Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type BDAY Subject: Registration of application/directory MIME type BDAY
Type name: BDAY Type name: BDAY
Type purpose: To specify the birthdate of the object the vCard Type purpose: To specify the birthdate of the object the vCard
represents. represents.
Type encoding: 8bit. Type encoding: 8bit.
Type value: The default is date. It may also be reset to date-time. Type value: The default is date. It may also be reset to date-time.
Type examples: Type examples:
Dawson & Howes [Page 7] Expires September 1997
vCard MIME Directory Profile
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00 BDAY:1953-10-15T23:10:00
BDAY:1987-09-27T08:30:00-06:00 BDAY:1987-09-27T08:30:00-06:00
4.3 Delivery Addressing Types 4.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 object the vCard represents. addressing or label for the object the vCard represents.
4.3.1 ADR Type Definition 4.2.1 ADR Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ADR Subject: Registration of application/directory MIME type ADR
Type name: ADR Type name: ADR
Type purpose: To specify the structured components of the delivery Type purpose: To specify the structured components of the delivery
address for the object the vCard represents. address for the object the vCard represents.
Dawson & Howes [Page 7] Expires January 1998
vCard MIME Directory Profile
Type encoding: The default is 8bit. It may also be reset to 7bit or Type encoding: The default is 8bit. It may also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
Type special notes: The type value is structured text consisting of a Type special notes: The type value is structured text consisting of a
sequence of address components (i.e., extended address, post office sequence of address components (i.e., post office box, extended
box, street address, locality, region, postal code, and country name) address, street address, locality, region, postal code, and country
separated by the SEMI-COLON character (ASCII decimal 59) and name) separated by the SEMI-COLON character (ASCII decimal 59) and
optionally one or more LWSP. optionally one or more LWSP.
The type may include the type parameter "TYPE" to specify the The type may include the type parameter "TYPE" to specify the
delivery address type. The TYPE parameter values may include "dom" to delivery address type. The TYPE parameter values may 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
delivery address; "parcel" to indicate a parcel delivery address; delivery address; "parcel" to indicate a parcel delivery address;
"home" to indicate a delivery address for a residence; "work" to "home" to indicate a delivery address for a residence; "work" to
indicate delivery address for a place of work; and "pref" to indicate indicate delivery address for a place of work; and "pref" to indicate
the preferred delivery address when more than one address might be the preferred delivery address when more than one address is
specified. These type parameter values may be specified as a specified. These type parameter values may 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=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: Type example:
Dawson & Howes [Page 8] Expires September 1997 ADR;TYPE=dom,home,postal,parcel:;;123 Main
vCard MIME Directory Profile
ADR;TYPE=dom,home,postal,parcel:123 Main
Street;Any Town;CA;91921-1234 Street;Any Town;CA;91921-1234
4.3.2 LABEL Type Definition 4.2.2 LABEL Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type LABEL Subject: Registration of application/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.
Type encoding: The default is 8bit. It may also be reset to 7bit or Type encoding: The default is 8bit. It may also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
Type special notes: The type value is formatted text that may be used Type special notes: The type value is formatted text that may be used
to present a delivery address label for the object the vCard to present a delivery address label for the object the vCard
represents. represents.
Dawson & Howes [Page 8] Expires January 1998
vCard MIME Directory Profile
The type may include the type parameter "TYPE" to specify delivery The type may include the type parameter "TYPE" to specify delivery
label type. The TYPE parameter values may include "dom" to indicate a label type. The TYPE parameter values may include "dom" to indicate a
domestic delivery label; "intl" to indicate an international delivery domestic delivery label; "intl" to indicate an international delivery
label; "postal" to indicate a postal delivery label; "parcel" to label; "postal" to indicate a postal delivery label; "parcel" to
indicate a parcel delivery label; "home" to indicate a delivery label indicate a parcel delivery label; "home" to indicate a delivery label
for a residence; "work" to indicate delivery label for a place of for a residence; "work" to indicate delivery label for a place of
work; and "pref" to indicate the preferred delivery label when more work; and "pref" to indicate the preferred delivery label when more
than one label might be specified. These type parameter values may than one label is specified. These type parameter values may
specified as a parameter list (i.e., "TYPE=dom;TYPE=postal") or as a specified as a parameter list (i.e., "TYPE=dom;TYPE=postal") or as a
value list (i.e., "TYPE=dom,postal"). This type is based on semantics value list (i.e., "TYPE=dom,postal"). This type is based on semantics
of the X.520 geographical and postal addressing attributes. The of the X.520 geographical and postal addressing attributes. The
default is "TYPE=intl,postal,parcel,work". The default can be default is "TYPE=intl,postal,parcel,work". The default can be
overridden to some other set of values by specifying one or more overridden to some other set of values by specifying one or more
alternate values. For example, the default can be reset to alternate values. For example, the default can be reset to
"TYPE=intl,post,parcel,home" to specify an international delivery "TYPE=intl,post,parcel,home" to specify an international delivery
label for both postal and parcel delivery to a residencial location. label for both postal and parcel delivery to a residencial location.
Type example: Type example:
LABEL;ENCODING=quoted-printable;TYPE=dom,home,= LABEL;ENCODING=quoted-printable;TYPE=dom,home,=
postal,parcel:Mr.John Q. Public, Esq.=0D=0A= postal,parcel:Mr.John Q. Public, Esq.=0D=0A=
Mail Drop: TNE QB=0D=0A= Mail Drop: TNE QB=0D=0A=
123 Main Street=0D=0A= 123 Main Street=0D=0A=
Any Town, CA 91921-1234=0D=0A= Any Town, CA 91921-1234=0D=0A=
U.S.A. U.S.A.
4.4 Telecommunications Addressing Types 4.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.
Dawson & Howes [Page 9] Expires September 1997 4.3.1 TEL Type Definition
vCard MIME Directory Profile
4.4.1 TEL Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TEL Subject: Registration of application/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.
Type encoding: 8bit. Type encoding: 8bit.
Type value: phone-number. Type value: phone-number.
Type special notes: .The value of this type is specified in a Type special notes: .The value of this type is specified in a
canonical form in order to specify an unambiguous representation of canonical form in order to specify an unambiguous representation of
the globally unique telephone endpoint. This type is based on the the globally unique telephone endpoint. This type is based on the
X.500 Telephone Number attribute. X.500 Telephone Number attribute.
The type may include the type parameter "TYPE" to specify intended The type may include the type parameter "TYPE" to specify intended
use for the telephone number. The TYPE parameter values may include: use for the telephone number. The TYPE parameter values may include:
Dawson & Howes [Page 9] Expires January 1998
vCard MIME Directory Profile
"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 line 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 line, "fax" to indicate a facsimile indicate a voice telephone number, "fax" to indicate a facsimile
telephone line, "cell" to indicate a cellular telephone line, "video" telephone number, "cell" to indicate a cellular telephone number,
to indicate a video conferencing telephone line, "pager" to indicate "video" to indicate a video conferencing telephone number, "pager" to
a paging device telephone line, "bbs" to indicate a bulletin board indicate a paging device telephone number, "bbs" to indicate a
system telephone line, "modem" to indicate a MODEM connected bulletin board system telephone number, "modem" to indicate a MODEM
telephone line, "car" to indicate a car-phone telephone line, "isdn" connected telephone number, "car" to indicate a car-phone telephone
to indicate an ISDN service telephone line. The default type is number, "isdn" to indicate an ISDN service telephone number, "pcs" to
"voice". These type parameter values may specified as a parameter indicate a personal communication services telephone number. The
list (i.e., "TYPE=work;TYPE=voice") or as a value list (i.e., default type is "voice". These type parameter values may specified as
"TYPE=work,voice"). The default may be overridden to another set of a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list
values by specifying one or more alternate values. For example, the (i.e., "TYPE=work,voice"). The default may be overridden to another
default TYPE of "voice" can be reset to a WORK and HOME, VOICE and set of values by specifying one or more alternate values. For
FAX telephone number by the value list "TYPE=work,home,voice,fax". example, the default TYPE of "voice" can be reset to a WORK and HOME,
VOICE and FAX telephone number by the value list
"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
4.4.2 EMAIL Type Definition 4.3.2 EMAIL Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type EMAIL Subject: Registration of application/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.
Dawson & Howes [Page 10] Expires September 1997
vCard MIME Directory Profile
Type encoding: 8bit. Type encoding: 8bit.
Type value: text. Type value: text.
Type special notes: . The type may include the type parameter "TYPE" Type special notes: . The type may include the type parameter "TYPE"
to specify the format of the electronic mail address. The TYPE to specify the format or preference of the electronic mail address.
parameter values may include: "internet" to indicate an Internet The TYPE parameter values may include: "internet" to indicate an
addressing type or "x400" to indicate a X.400 addressing type. Any Internet addressing type, "x400" to indicate a X.400 addressing type
other IANA registered address type may also be specified. The default or."pref" to indicate a preferred-use email address when more than
email type is "internet". Any non-standard value may also be one is specified. Another IANA registered address type may also be
specified. specified. The default email type is "internet". A non-standard value
may also be specified.
Type example: Type example:
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com EMAIL;TYPE=internet:jqpublic@xyz.dom1.com
4.4.3 MAILER Type Definition Dawson & Howes [Page 10] Expires January 1998
To: ietf-mime-directory@umich.edu vCard MIME Directory Profile
EMAIL;TYPE=internet:jdoe@isp.net
EMAIL;TYPE=internet,pref:jane_doe@abc.com
4.3.3 MAILER Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type MAILER Subject: Registration of application/directory MIME type MAILER
Type name: MAILER Type name: MAILER
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: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
skipping to change at line 625 skipping to change at line 604
Type special notes: This information may provide assistance to a Type special notes: This information may 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 may be packaged. This property is based on the used, and how they may 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
4.5 Geographical Types 4.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.
4.5.1 TZ Type Definition 4.4.1 TZ Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TZ Subject: Registration of application/directory MIME type TZ
Dawson & Howes [Page 11] Expires September 1997
vCard MIME Directory Profile
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.
Type encoding: 8bit. Type encoding: 8bit.
Type value: The default is utc-offset. It may also be reset to text. Type value: The default is utc-offset. It may also be reset to text.
Type examples: Type examples:
TZ:-05:00 TZ:-05:00
TZ;VALUE=text:-05:00, EST, Raleigh/North America Dawson & Howes [Page 11] Expires January 1998
4.5.2 GEO Type Definition vCard MIME Directory Profile
To: ietf-mime-directory@umich.edu TZ;VALUE=text:-05:00; EST; Raleigh/North America
4.4.2 GEO Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type GEO Subject: Registration of application/directory MIME type GEO
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: Two float values separated by the SEMI-COLON character Type value: Two float values separated by the SEMI-COLON character
(ASCII decimal 59). (ASCII decimal 59).
Type special notes: The value is the longitude and latitude of the Type special notes: This type specifies information related to the
object the vCard represents. The latitude represents the location global position of the object associated with the vCard. The value
north and south of the equator as a positive or negative number, specifies latitude and longitude, in that order (i.e., "LAT LON"
respectively. The longitude represents the location east and west of ordering). The longitude represents the location east and west of the
the prime meridian as a positive or negative number, respectively. prime meridian as a positive or negative real number, respectively.
The text components are separated by the SEMI-COLON character (ASCII The latitude represents the location north and south of the equator
decimal 59). as a positive or negative real number, respectively. The longitude
and latitude values must be specified as decimal degrees and should
be specified to six decimal places. This will allow for granularity
within a meter of the geographical position. The text components are
separated by the SEMI-COLON character (ASCII decimal 59). The simple
formula for converting degrees-minutes-seconds into decimal degrees
is:
decimal = degrees + minutes/60 + seconds/3600.
Type example: Type example:
GEO:+37.24;-17.87 GEO:37.386013;-122.082932
4.6 Organizational Types 4.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.
4.6.1 TITLE Type Definition 4.5.1 TITLE Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TITLE Subject: Registration of application/directory MIME type TITLE
Dawson & Howes [Page 12] Expires September 1997 Type name: TITLE
vCard MIME Directory Profile Dawson & Howes [Page 12] Expires January 1998
Type name: TITLE vCard MIME Directory Profile
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: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
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:
TITLE:Director, Research and Development TITLE:Director, Research and Development
4.6.2 ROLE Type Definition 4.5.2 ROLE Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ROLE Subject: Registration of application/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.
Type encoding: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
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.
The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].
Type example: Type example:
ROLE:Programmer ROLE:Programmer
4.6.3 LOGO Type Definition 4.5.3 LOGO Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type LOGO Subject: Registration of application/directory MIME type LOGO
Type name: LOGO Type name: LOGO
Dawson & Howes [Page 13] Expires September 1997
vCard MIME Directory Profile
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.
Type encoding: The default is 8bit. May also be reset to base64 in Type encoding: The default is 8bit. May also be reset to base64 in
order to permit inline encoded binary data. order to permit inline encoded binary data.
Dawson & Howes [Page 13] Expires January 1998
vCard MIME Directory Profile
Type value: The default is binary. It may also be reset to url. The Type value: The default is binary. It may also be reset to url. The
url value may be used to specify a value outside of this MIME entity. url value may be used to specify a value outside of this MIME entity.
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY 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. In addition, a non- be one of the IANA registered image formats or a non-standard image
standard image format MAY be specified. format.
Type example: Type example:
LOGO;VALUE=URL:http://www.abc.com/pub/logos/abccorp.jpg LOGO;VALUE=URL:http://www.abc.com/pub/logos/abccorp.jpg
4.6.4 AGENT Type Definition 4.5.4 AGENT Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type AGENT Subject: Registration of application/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.
Type encoding: 8-bit. Type encoding: 8-bit.
skipping to change at line 803 skipping to change at line 786
entity. entity.
Type special notes: This type typically is used to specify an area Type special notes: This type typically is used to specify an area
administrator, assistant, or secretary for the individual associated administrator, assistant, or secretary for the individual associated
with the vCard. A key characteristic of the Agent type is that it with the vCard. A key characteristic of the Agent type is that it
represents somebody or something that is separately addressable. represents somebody or something that is separately addressable.
Type example: Type example:
AGENT;VALUE=URL: AGENT;VALUE=URL:
CID:///<JQPUBLIC.part3.960129T083020.xyzMail@host3.com> CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
4.6.5 ORG Type Definition 4.5.5 ORG Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type ORG Subject: Registration of application/directory MIME type ORG
Type name: ORG Type name: ORG
Dawson & Howes [Page 14] Expires September 1997
vCard MIME Directory Profile
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.
Dawson & Howes [Page 14] Expires January 1998
vCard MIME Directory Profile
Type encoding: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
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 text and Organization Unit attributes. The type value is a structured text
consisting of the organization name, followed by any organizational consisting of the organization name, followed by any organizational
units. The text components are separated the SEMI-COLON character units. The text components are separated the SEMI-COLON character
(ASCII decimal 59). (ASCII decimal 59).
The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].
Type example: Type example:
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
4.7 Explanatory Types 4.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.
4.7.1 NOTE Type Definition 4.6.1 CATEGORIES Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type CATEGORIES
Type name: CATEGORIES
Type purpose: To specify application category information about the
vCard.
Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type value: text.
Type special notes: More than one category may be specified as a list
of categories separated by a COMMA (ASCII Decimal 44) character.
Type example:
CATEGORIES:TRAVEL AGENT
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
4.6.2 NOTE Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type NOTE Subject: Registration of application/directory MIME type NOTE
Type name: NOTE Type name: NOTE
Dawson & Howes [Page 15] Expires January 1998
vCard MIME Directory Profile
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: The default is 8bit. May also be reset to 7bit or Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable. quoted-printable.
Type value: text. Type value: text.
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.
The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR].
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.
Dawson & Howes [Page 15] Expires September 1997 4.6.3 PRODID Type Definition
vCard MIME Directory Profile To: ietf-mime-directory@imc.org
4.7.2 REV Type Definition Subject: Registration of application/directory MIME type PRODID
To: ietf-mime-directory@umich.edu Type name: PRODID
Type purpose: To specify the identifier for the product that created
the vCard object.
Type encoding: 8-bit.
Type value: Text.
Type example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
4.6.4 REV Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type REV Subject: Registration of application/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.
Type encoding: 8-bit. Type encoding: 8-bit.
Type value: The default is date-time. May also be reset to date. Type value: The default is date-time. May also be reset to date.
Type special notes: The type value is a calendar date and time of day Type special notes: The type value is a calendar date and time of day
in a form conforming to complete representation of ISO 8601 calendar in a form conforming to complete representation of ISO 8601 calendar
Dawson & Howes [Page 16] Expires January 1998
vCard MIME Directory Profile
date and time of day format. The value distinguishes the current date and time of day format. The value distinguishes the current
revision of the information defining this vCard. revision of the information defining this vCard.
Type example: Type example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
4.7.3 SOUND Type Definition 4.6.5 SOUND Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type SOUND Subject: Registration of application/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.
Type encoding: The default is 8bit. May also be reset to base64 in Type encoding: The default is 8bit. May also be reset to base64 in
order to permit inline encoded binary data. order to permit inline encoded binary data.
Type value: The default is binary. It may also be reset to url. The Type value: The default is binary. It may also be reset to url. The
url value may be used to specify a value outside of this MIME entity. url value may be used to specify a value outside of this MIME entity.
Type special notes: The type MAY include the type parameter "TYPE" to Type special notes: The type MAY 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. In addition, a non-standard of the IANA registered audio formats or a non-standard audio format.
audio format MAY be specified.
Type example: Type example:
SOUND;TYPE=BASIC;VALUE=URL:CID://<JOHNQPUBLIC.part8. SOUND;TYPE=BASIC;VALUE=URL:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com> 19960229T080000.xyzMail@host1.com
4.7.4 URL Type Definition
To: ietf-mime-directory@umich.edu
Dawson & Howes [Page 16] Expires September 1997 4.6.6 URL Type Definition
vCard MIME Directory Profile To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type URL Subject: Registration of application/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: url. Type value: url.
Type example: Type example:
URL:http://www.swbyps.restaurant.french/~chezchic.html URL:http://www.swbyps.restaurant.french/~chezchic.html
4.7.5 UID Type Definition Dawson & Howes [Page 17] Expires January 1998
To: ietf-mime-directory@umich.edu vCard MIME Directory Profile
4.6.7 UID Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type UID Subject: Registration of application/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.
Type encoding: 8bit. Type encoding: 8bit.
skipping to change at line 978 skipping to change at line 1001
The type may include the type parameter "TYPE" to specify the format The type may include the type parameter "TYPE" to specify the format
of the identifier. The TYPE parameter value may be any IANA of the identifier. The TYPE parameter value may be any IANA
registered identifier format. The value may also be a non-standard registered identifier format. The value may also be a non-standard
format. format.
Type example: Type example:
UID:19950401-080045-40000F192713-0052 UID:19950401-080045-40000F192713-0052
4.7.6 Version Type Definition 4.6.8 Version Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type VERSION Subject: Registration of application/directory MIME type VERSION
Type name: UID 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.
Dawson & Howes [Page 17] Expires September 1997
vCard MIME Directory Profile
Type encoding: 8bit. Type encoding: 8bit.
Type value: text. Type value: text.
Type special notes: The value must be "2.1" if the vCard version Type special notes: The value must be "2.2" if the vCard version
corresponds to the [VCARD] specification. corresponds to this specification.
Type example: Type example:
VERSION: 2.1 VERSION: 2.2
4.8 Security Types Dawson & Howes [Page 18] Expires January 1998
vCard MIME Directory Profile
4.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.
4.8.1 KEY Type Definition 4.7.1 CLASSIFICATION Type Definition
To: ietf-mime-directory@umich.edu To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type VERSION Subject: Registration of application/directory MIME type
CLASSIFICATION
Type name: KEY Type name: CLASS
Type purpose: To specify an identifier corresponding to the highest Type purpose: To specify the access classification for a vCard
version of the vCard profile used in creating the vCard. object.
To specify a public key or authentication certificate associated with Type encoding: The default is 8bit. May also be reset to 7bit or
the object that the vCard represents. quoted-printable.
Type value: text.
Type special notes: An access classification is only one component of
the general security model for a directory service. The
classification attribute provides a method of capturing the intent of
the owner for general access to information described by the vCard
object.
Type examples:
CLASS:PUBLIC
CLASS:PRIVATE
CLASS:CONFIDENTIAL
4.7.2 KEY Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type KEY
Type name: KEY
Type purpose: To specify a public key or authentication certificate
associated with the object that the vCard represents.
Type encoding: The default is 8bit. May also be reset to base64. Type encoding: The default is 8bit. May also be reset to base64.
Type value: The default is text. May also be reset to binary. Type value: The default is text. May also be reset to binary.
Type special notes: The type may also include the type parameter TYPE Type special notes: The type may also include the type parameter TYPE
to specify the public key or authentication certificate format. The to specify the public key or authentication certificate format. The
Dawson & Howes [Page 19] Expires January 1998
vCard MIME Directory Profile
parameter type may specify any IANA registered public key or parameter type may specify any IANA registered public key or
authentication certificate format. The parameter type may also authentication certificate format. The parameter type may also
specify a non-standard format. specify a non-standard format.
4.9 Extended Types 4.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 defined in [RFC-2045]. Non- using the non-standard, private values mechanism defined in [RFC-
standard, private types with a name starting with "X-" may be defined 2045]. Non-standard, private types with a name starting with "X-" may
bilaterally between two cooperating agents without outside be defined bilaterally between two cooperating agents without outside
registration or standardization. registration or standardization.
5. Formal Grammar 5. Differences With vCard v2.1
The following formal grammar is provided to assist developers in This specification has been reviewed by the IETF community. The
building parsers for the vCard. review process introduced a number of differences with the [VCARD]
version 2.1. These differences are minor, but require that vCard
objects conforming to this specification have a different version
number than a vCard conforming to [VCARD]. The differences include
the following:
Dawson & Howes [Page 18] Expires September 1997 · VERSION value corresponding to this specification must be
"2.2".
vCard MIME Directory Profile · The [MIME-DIR] predefined types of PROFILE, SOURCE, NAME are
allowed.
· The [MIME-DIR] VALUE type parameter for value data typing is
allowed.
· The [VCARD] CHARSET type parameter has been eliminated.
Character set may only be specified on the CHARSET parameter
on the Content-Type MIME header field.
· The [VCARD] support for non-signficant LWSP character been
eliminated. All LWSP is significant in this specification.
· LOGO, PHOTO and SOUND multimedia formats need to be either
IANA registered types or non-standard types.
· TEL values may be identified as personal communication
services telephone numbers with the PCS type parameter value.
· The PRODID, CATEGORIES and CLASS types have been added.
6. Formal Grammar
The following formal grammar is provided to assist developers in
building parsers for the vCard.
This syntax is written according to the form described in RFC 822, This syntax is written according to the form described in RFC 822,
but it references just this small subset of RFC 822 literals: but it references just this small subset of RFC 822 literals:
Dawson & Howes [Page 20] Expires January 1998
vCard MIME Directory Profile
CR = <ASCII CR, carriage return> ; (15, 13.) CR = <ASCII CR, carriage return> ; (15, 13.)
LF = <ASCII LF, linefeed> ; (12,10.) LF = <ASCII LF, linefeed> ; (12,10.)
CRLF = CR LF CRLF = CR LF
SPACE = <ASCII SP, space> ; (40,32.) SPACE = <ASCII SP, space> ; (40,32.)
HTAB = <ASCII HT, horizontal-tab> ; (11,9.) HTAB = <ASCII HT, horizontal-tab> ; (11,9.)
All literal property names are valid as upper, lower, or mixed case. All literal property names are valid as upper, lower, or mixed case.
ws = 1*(SPACE / HTAB)
; "whitespace," one or more spaces or tabs
wsls = 1*(SPACE / HTAB / CRLF)
; whitespace with line separators
word = <any printable 7bit us-ascii except []=:., > word = <any printable 7bit us-ascii except []=:., >
groups = groups "." word groups = groups "." word
/ word / word
vcard"entity = 1*([wsls] vcard [wsls]) vcard_entity = 1*(vcard)
vcard = "BEGIN" [ws] ":" [ws] "VCARD" [ws] 1*CRLF vcard = "BEGIN" ":" "VCARD" 1*CRLF
items *CRLF items *CRLF
"END" ws] [ ":" [ws] "VCARD" 1*CRLF "END" ":" "VCARD" 1*CRLF
items = items *CRLF item items = items *CRLF item
/ item / item
; these may be "folded" ; these may be "folded"
item = [groups "."] name item = [groups "."] name
[params] ":" value CRLF [params] ":" value CRLF
/ [groups "."] "ADR" / [groups "."] "ADR"
[params] ":" addressparts CRLF [params] ":" addressparts CRLF
/ [groups "."] "ORG" / [groups "."] "ORG"
[params] ":" orgparts CRLF [params] ":" orgparts CRLF
/ [groups "."] "N" / [groups "."] "N"
[params] ":" nameparts CRLF [params] ":" nameparts CRLF
/ [groups "."] "AGENT" / [groups "."] "AGENT"
[params] ":" vcard CRLF [params] ":" vcard CRLF
; these may be "folded" ; these may be "folded"
name = "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE" name = "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE"
/ "SOUND" / VERSION " " / "TEL" / "EMAIL" / "TZ" / "SOUND" / "VERSION" / "TEL" / "EMAIL" / "TZ"
/ "GEO" / "NOTE" / "SOURCE" / "NAME" / "PROFILE" / "GEO" / "NOTE" / "SOURCE" / "NAME" / "PROFILE"
/ "URL" / " " BDAY / "ROLE" / "REV" / "UID" / "KEY" / "URL" / "BDAY" / "ROLE" / "REV" / "UID" / "KEY"
/ "MAILER" / "X-" word / "MAILER" / "CATEGORIES" / "CLASS" / "PRODID"
/"X-" word
; these may be "folded" ; these may be "folded"
value = 7bit / quoted-printable / base64 value = 7bit / quoted-printable / base64
7bit = <7bit us-ascii printable chars, excluding CR LF> 7bit = <7bit us-ascii printable chars, excluding CR LF>
Dawson & Howes [Page 19] Expires September 1997
vCard MIME Directory Profile
8bit = <MIME RFC 2045 8-bit text> 8bit = <MIME RFC 2045 8-bit text>
quoted-printable = <MIME RFC 2045 quoted-printable text> quoted-printable = <MIME RFC 2045 quoted-printable text>
base64 = <MIME RFC 2045 base64 text> base64 = <MIME RFC 2045 base64 text>
; the end of the text is marked with two CRLF sequences ; the end of the text is marked with two CRLF sequences
Dawson & Howes [Page 21] Expires January 1998
vCard MIME Directory Profile
; this results in one blank line before the start of the next ; this results in one blank line before the start of the next
; property ; property
params = ";" [ws] paramlist params = ";" paramlist
paramlist = paramlist [ws] ";" [ws] param paramlist = paramlist ";" param
/ param / param
param = "TYPE" [ws] "=" [ws] ptypeval param = "TYPE" "=" ptypeval
/ "VALUE" [ws] "=" [ws] pvalueval / "VALUE" "=" pvalueval
/ "ENCODING" [ws] "=" [ws] pencodingval / "ENCODING" "=" pencodingval
/ "CHARSET" [ws] "=" [ws] charsetval / "LANGUAGE" "=" langval
/ "LANGUAGE" [ws] "=" [ws] langval / "X-" word "=" word
/ "X-" word [ws] "=" [ws] word / knowntype / ianatype
/ knowntype
ptypeval = knowntype / "X-" word ptypeval = knowntype / "X-" word
pvalueval = "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME" pvalueval = "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME"
/ "INTEGER" / "BOOLEAN" / "FLOAT" / "BINARY" / / "INTEGER" / "BOOLEAN" / "FLOAT" / "BINARY" /
/ "VCARD" / "PHONE-NUMBER" / "UTC-OFFSET" / "X-" word / "VCARD" / "PHONE-NUMBER" / "UTC-OFFSET" / "X-" word
pencodingval = "7BIT / " "8BIT" / "QUOTED-PRINTABLE" / "BASE64" pencodingval = "7BIT" / "8BIT" / "QUOTED-PRINTABLE" / "BASE64"
/ "X-" word / "X-" word
charsetval = <a character set text value as defined in Section 3
of RFC 2047>
langval = <a language string as defined in RFC 1766> langval = <a language string as defined in RFC 1766>
addressparts = 0*6(strnosemi ";") strnosemi addressparts = 0*6(strnosemi ";") strnosemi
; PO Box, Extended Addr, Street, Locality, Region, Postal Code, ; PO Box, Extended Addr, Street, Locality, Region, Postal Code,
; Country Name ; Country Name
orgparts = *(strnosemi ";") strnosemi orgparts = *(strnosemi ";") strnosemi
; First is Organization Name, remainder are Organization Units. ; First is Organization Name, remainder are Organization Units.
nameparts = 0*4(strnosemi ";") strnosemi nameparts = 0*4(strnosemi ";") strnosemi
; Family, Given, Middle, Prefix, Suffix. ; Family, Given, Middle, Prefix, Suffix.
; Example:Public;John;Q.;Reverend Dr.;III, Esq. ; Example:Public;John;Q.;Reverend Dr.;III, Esq.
strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi
; To include a semicolon in this string, it must be escaped ; To include a semicolon in this string, it must be escaped
; with a "\" character. ; with a "\" character.
nonsemi = <any non-control ASCII except ";"> nonsemi = <any non-control ASCII except ";">
Dawson & Howes [Page 20] Expires September 1997 knowntype = "DOM" / "INTL" / "POSTAL" / "PARCEL" / "HOME" / "WORK"
/ "PREF" / "VOICE" / "FAX" / "MSG" / "CELL" / "PAGER"
/ "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO" / "PCS"
/ "INTERNET" / "X400" / "X509" / "PGP"
vCard MIME Directory Profile ianatype = <Any IANA registered value>
knowntype = "DOM" / " " / "POSTAL" INTL / "PARCEL" / "HOME" / "WORK" Dawson & Howes [Page 22] Expires January 1998
/ "PREF" / " " VOICE / "FAX" / "MSG" / "CELL" / "PAGER"
/ "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO"
/ "INTERNET" / "GIF" / "JPEG" / "PCM" / "WAVE"
/ "X509" / "PGP"
5.1 Acknowledgements vCard MIME Directory Profile
6.1 Acknowledgements
The authors would like to thank the participants in the IETF ASID The authors would like to thank the participants in the IETF ASID
working group, in addition to the following individuals, Roland working group, in addition to the following individuals, Roland
Alden, Stephen Bartlett, Alec Dun, Daniel Klaussen, Chris Newman, Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce Johnston,
Michelle Watkins; who provided numerous suggestions and comments on Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who
this work. provided numerous suggestions and comments on this work.
5.2 Authors's Addresses 6.2 Authors’s Addresses
BEGIN:vCard BEGIN:vCard
FN:Frank Dawson FN:Frank Dawson
ORG:IBM Corporation;Network Software Division ORG:IBM Corporation;Network Software Division
ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002; ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002;
3039 Cornwallis Rd.;Research Triangle Park; 3039 Cornwallis Rd.;Research Triangle Park;
NC;27709;U.S.A. NC;27709;U.S.A.
TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861 TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861
TEL;TYPE=FAX,WORK: +1-919-543-6822 TEL;TYPE=FAX,WORK: +1-919-543-6822
EMAIL;TYPE=INTERNET,PREF:fdawson@raleigh.ibm.com EMAIL;TYPE=INTERNET,PREF:fdawson@raleigh.ibm.com
skipping to change at line 1205 skipping to change at line 1287
BEGIN:vCard BEGIN:vCard
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
5.3 References 6.3 References
The following documents are referenced by this work. The following documents are referenced by this work.
[ISO 639] ISO 639:1988 - Code for the representation of names of
languages - The International Organization for Standardization, April
1988.
[ISO 3166] ISO 3166:1993 - Codes for the representation of names of
countries - The International Organization for Standardization,
December 1993.
[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 times - The
International Organization for Standardization, June, 1988. International Organization for Standardization, June, 1988.
Dawson & Howes [Page 21] Expires September 1997
vCard MIME Directory Profile
[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 - Representation of
dates and times - The International Organization for Standardization, dates and times - The International Organization for Standardization,
May, 1991. May, 1991.
[ISO 9070] ISO 9070, Information Processing - SGML support facilities [ISO 9070] ISO 9070, Information Processing - SGML support facilities
- Registration Procedures for Public Text Owner Identifiers, April, - Registration Procedures for Public Text Owner Identifiers, April,
1991. 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, Fascicle II.2, pp.
128-134, November, 1988. 128-134, November, 1988.
Dawson & Howes [Page 23] Expires January 1998
vCard MIME Directory Profile
[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, pp. 317-332,
November, 1988. 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., "A MIME Content-Type for Directory [MIME-DIR] Howes, T., Smith, M., "A MIME Content-Type for Directory
Information", Internet-draft-ietf-asid-mime-direct-05.txt, March, Information", Internet-draft-ietf-asid-mime-direct-04.txt, July,
1997. 1997.
[RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text [RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text
Messages", STD 11, RFC 822, August 1982. Messages", STD 11, RFC 822, August 1982.
[RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail [RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
2045, November 1996. 2045, November 1996.
[RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail [RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail
skipping to change at line 1279 skipping to change at line 1353
[RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform [RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
Resource Locators (URL)", RFC 1738, December 1994. Resource Locators (URL)", RFC 1738, December 1994.
[RFC-1766] Alvestrand, H., "Tags for the Identification of [RFC-1766] Alvestrand, H., "Tags for the Identification of
Languages", March 1995. Languages", March 1995.
[RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type," [RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type,"
RFC 1872, December 1995. RFC 1872, December 1995.
Dawson & Howes [Page 22] Expires September 1997
vCard MIME Directory Profile
[VCARD] VERSIT Consortium, "vCard - The Electronic Business Card [VCARD] VERSIT Consortium, "vCard - The Electronic Business Card
Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18, Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18,
1996. 1996.
Dawson & Howes [Page 23] Expires September 1997 Dawson & Howes [Page 24] Expires January 1998
 End of changes. 160 change blocks. 
327 lines changed or deleted 397 lines changed or added

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