draft-ietf-asid-mime-vcard-03.txt   draft-ietf-asid-mime-vcard-04.txt 
Network Working Group Frank Dawson Network Working Group Frank Dawson
INTERNET DRAFT Tim Howes INTERNET DRAFT Lotus Development Corporation
ietf-asid-mime-vcard-03.txt Lotus/Netscape Communications ietf-asid-mime-vcard-04.txt Tim Howes
July 30, 1997 Expires six months after November 21, 1997 Netscape Communications
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 27 skipping to change at line 27
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet- Drafts Shadow "1id-abstracts.txt" listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Distribution of this memo is unlimited.
Copyright (C) The Internet Society 1997. 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,
logo, audio clips, etc.). The directory information used by this logo, audio clips, etc.). The directory information used by this
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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interopreted as described in [RFC-2119].
1. Overview 1. 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
may be based on any of a number of directory schemas. This document may 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
Dawson & Howes [Page 1] May 1998
vCard MIME Directory Profile
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] ExpiresJanuary 1998
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
structured and presentation form of the delivery address, various structured and presentation form of the delivery address, various
telephone numbers and organizational information associated with the telephone numbers and organizational information associated with the
entry. In addition, traditional paper business card information such entry. In addition, traditional paper business card information such
skipping to change at line 109 skipping to change at line 117
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, Dawson & Howes [Page 2] May 1998
LANGUAGE, CONTEXT.
New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ, vCard MIME Directory Profile
GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORY, NOTE, PRODID, REV,
SOUND, URL, UID, VERSION, CLASS, KEY
Dawson & Howes [Page 2] Expires January 1998 Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT.
vCard MIME Directory Profile New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL,
MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE,
PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY
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
skipping to change at line 147 skipping to change at line 155
extend the content-type definition of [MIME-DIR]. extend the content-type definition of [MIME-DIR].
3.1 Predefined Type Usage 3.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].
3.1.1 BEGIN and END Type 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
VCARD. of "VCARD".
3.1.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.1.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, it's value must be "VCARD".
3.1.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.
Dawson & Howes [Page 3] May 1998
vCard MIME Directory Profile
3.2 Predefined Type Parameter Usage 3.2 Predefined Type Parameter Usage
The vCard MIME Directory Profile uses the following predefined types The vCard MIME Directory Profile uses the following predefined types
parameters as defined by [MIME-DIR]. parameters as defined by [MIME-DIR].
Dawson & Howes [Page 3] Expires January 1998 . LANGUAGE
vCard MIME Directory Profile . ENCODING
∑ LANGUAGE . VALUE
∑ ENCODING 3.3 Predefined VALUE Type Usage
∑ VALUE The predefined data type values specified in [MIME-DIR] MAY NOT be
repeated in COMMA separated value lists, unless specified by this
specification.
3.3 VALUE Type Parameter Extensions 3.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.
3.3.1 BINARY 3.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 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 binary
data MUST be encoded using the "B" encoding format. Long lines of
encoded binary data may be folded using the folding method defined in
[MIME-DIR].
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 binary = <A "B" binary encoded string as defined by [RFC 2047].>
encoding>
binary = *binchar ;A base64 or quoted-printable
encoding of the binary information
3.3.2 VCARD 3.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 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. Since each of the type
declarations with in the vcard value type are being specified within
a type value themselves, they MUST be terminated with the backslash
escapement sequence "\n" or "\N", instead of the character sequence
CRLF. For example, with the AGENT type a value would be specified as:
3.3.3 PHONE-NUMBER AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n
TITLE:Area Administrator\, Assistant\n
EMAIL;INTERNET:jfriday@host.com\n
END:VCARD
Dawson & Howes [Page 4] May 1998
vCard MIME Directory Profile
3.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 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 special semantics of a
number. telephone number as defined in [CCITT E.163] and [CCITT X.121].
3.3.4 UTC-OFFSET 3.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 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 value type is an offset from Coordinated Universal Time (UTC). It
type is an offset from Coordinated Universal Time (UTC). It is is specified as a positive or negative difference in units of hours
specified as a positive or negative difference in units of hours and 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 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
Dawson & Howes [Page 4] Expires January 1998
vCard MIME Directory Profile
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
3.4 Structured Type Values 3.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.
3.6 Line Delimiting and Folding
This profile supports the same line delimiting and folding methods
defined in [MIME-DIR].
4. vCard Profile Features 4. 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
Dawson & Howes [Page 5] May 1998
vCard MIME Directory Profile
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.
4.1 Identification Types 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.
skipping to change at line 286 skipping to change at line 317
To: ietf-mime-directory@imc.org 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 Type encoding: 8bit
vCard MIME Directory Profile
Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type value: text. 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. Common Name attribute.
Type example: Type example:
FN:Mr. John Q. Public, Esq. FN:Mr. John Q. Public, Esq.
4.1.2 N Type Definition 4.1.2 N Type Definition
To: ietf-mime-directory@imc.org 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: 8bit
quoted-printable.
Type value: text. Type value: A single structured text value. Each component may have
multiple values.
Type special note: The type value is structured text corresponding, Type special note: The structured text value corresponds, in
in sequence, to the Family Name, Given Name, Additional Names, sequence, to the Family Name, Given Name, Additional Names, Honorific
Honorific Prefixes, and Honorific Suffixes. The text components are Prefixes, and Honorific Suffixes. The text components are separated
delimited by the SEMI-COLON character (ASCII decimal 59) and possibly by the SEMI-COLON character (ASCII decimal 59) and possibly one or
one or more LWSP. This type is based on the semantics of the X.520 more LWSP. Individual text components MAY include multiple text
individual name attributes. values (e.g., multiple Additional Names), separated by the COMMA
Dawson & Howes [Page 6] May 1998
vCard MIME Directory Profile
character (ASCII decimal 44). This type is based on the semantics of
the X.520 individual name attributes.
Type example: Type example:
N:Public;John;Quinlan;Mr.;Esq. N:Public;John;Quinlan;Mr.;Esq.
4.1.3 PHOTO Type Definition N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P.
4.1.3 NICKNAME Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type NICKNAME
Type name: NICKNAME
Type purpose: To specify the text corresponding to the nickname of
the object the vCard represents.
Type encoding: 8bit
Type value: One or more text values separated by a COMMA character
(ASCII decimal 44).
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.
It may also be used to specify a familiar form of a proper name
specified by the FN or N types.
Type example:
NICKNAME:Robbie
NICKNAME:Jim,Jimmie
4.1.4 PHOTO Type Definition
To: ietf-mime-directory@imc.org 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 encoding MUST be reset to "b" using the ENCODING
order to permit inline, encoded binary data. parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of 8bit
is used and no explicit ENCODING parameter is needed.
Dawson & Howes [Page 6] Expires January 1998 Dawson & Howes [Page 7] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
Type value: The default is binary. It may also be reset to url. The Type value: A single value. The default is binary. It may also be
url value may be used to specify a value outside of this MIME entity. reset to uri. The uri 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 or a non-standard image be one of the IANA registered image formats or a non-standard image
format. format.
Type example: Type example:
PHOTO;VALUE=url:=http://www.abc.com/pub/photos PHOTO;VALUE=uri:=http://www.abc.com/pub/photos
/jqpublic.gif /jqpublic.gif
4.1.4 BDAY Type Definition PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...remainder of "B" encoded binary data...>
4.1.5 BDAY Type Definition
To: ietf-mime-directory@imc.org 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 a single date value. It may also be reset
to a single date-time value.
Type examples: Type examples:
BDAY:1996-04-15 BDAY:1996-04-15
BDAY:1953-10-15T23:10:00 BDAY:1953-10-15T23:10:00Z
BDAY:1987-09-27T08:30:00-06:00 BDAY:1987-09-27T08:30:00-06:00
4.2 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 vCard object.
4.2.1 ADR Type Definition 4.2.1 ADR Type Definition
To: ietf-mime-directory@imc.org 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 Dawson & Howes [Page 8] May 1998
Type purpose: To specify the structured components of the delivery vCard MIME Directory Profile
address for the object the vCard represents.
Dawson & Howes [Page 7] Expires January 1998 Type name: ADR
vCard MIME Directory Profile Type purpose: To specify the structured components of the delivery
address for the vCard object.
Type encoding: The default is 8bit. It may also be reset to 7bit or Type encoding: 8bit
quoted-printable.
Type value: text. Type value: A single structured text value, separated by the SEMI-
COLON character (ASCII decimal 59) and optionally one or more LWSP.
Type special notes: The type value is structured text consisting of a Type special notes: The structured text value consists of a sequence
sequence of address components (i.e., post office box, extended of address components. The component values MUST be specified in
address, street address, locality, region, postal code, and country their corresponding position. The structured text value corresponds,
name) separated by the SEMI-COLON character (ASCII decimal 59) and in sequence, to the post office box; the extended address; the street
optionally one or more LWSP. address; the locality (e.g., city); the region (e.g., state or
province); the postal code; the country name. When a component value
is missing, the associated component separator must still be
specified.
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 is 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: In this example the post office box and the extended
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
4.2.2 LABEL Type Definition 4.2.2 LABEL Type Definition
To: ietf-mime-directory@imc.org 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 Dawson & Howes [Page 9] May 1998
quoted-printable.
Type value: text.
Type special notes: The type value is formatted text that may be used vCard MIME Directory Profile
to present a delivery address label for the object the vCard
represents.
Dawson & Howes [Page 8] Expires January 1998 Type encoding: 8bit
vCard MIME Directory Profile Type value: A single text value.
The type may include the type parameter "TYPE" to specify delivery Type special notes: The type value is formatted text that may be used
label type. The TYPE parameter values may include "dom" to indicate a to present a delivery address label for the vCard object. The type
domestic delivery label; "intl" to indicate an international delivery may include the type parameter "TYPE" to specify delivery label type.
label; "postal" to indicate a postal delivery label; "parcel" to The TYPE parameter values may include "dom" to indicate a domestic
indicate a parcel delivery label; "home" to indicate a delivery label delivery label; "intl" to indicate an international delivery label;
for a residence; "work" to indicate delivery label for a place of "postal" to indicate a postal delivery label; "parcel" to indicate a
work; and "pref" to indicate the preferred delivery label when more parcel delivery label; "home" to indicate a delivery label for a
than one label is specified. These type parameter values may residence; "work" to indicate delivery label for a place of work; and
specified as a parameter list (i.e., "TYPE=dom;TYPE=postal") or as a "pref" to indicate the preferred delivery label when more than one
value list (i.e., "TYPE=dom,postal"). This type is based on semantics label is specified. These type parameter values may specified as a
of the X.520 geographical and postal addressing attributes. The parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list
default is "TYPE=intl,postal,parcel,work". The default can be (i.e., "TYPE=dom,postal"). This type is based on semantics of the
overridden to some other set of values by specifying one or more X.520 geographical and postal addressing attributes. The default is
alternate values. For example, the default can be reset to "TYPE=intl,postal,parcel,work". The default can be overridden to some
"TYPE=intl,post,parcel,home" to specify an international delivery other set of values by specifying one or more alternate values. For
label for both postal and parcel delivery to a residencial location. example, the default can be reset to "TYPE=intl,post,parcel,home" to
specify an international delivery label for both postal and parcel
delivery to a residencial location.
Type example: Type example: A multi-line address label.
LABEL;ENCODING=quoted-printable;TYPE=dom,home,= LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public, Esq.\n
postal,parcel:Mr.John Q. Public, Esq.=0D=0A= Mail Drop: TNE QB\n
Mail Drop: TNE QB=0D=0A= 123 Main Street\n
123 Main Street=0D=0A= Any Town, CA 91921-1234\n
Any Town, CA 91921-1234=0D=0A=
U.S.A. U.S.A.
4.3 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.
4.3.1 TEL Type Definition 4.3.1 TEL Type Definition
To: ietf-mime-directory@imc.org 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: A single 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
Dawson & Howes [Page 10] May 1998
vCard MIME Directory Profile
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 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
connected telephone number, "car" to indicate a car-phone telephone connected telephone number, "car" to indicate a car-phone telephone
skipping to change at line 554 skipping to change at line 625
To: ietf-mime-directory@imc.org 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.
Type encoding: 8bit. Type encoding: 8bit
Type value: text. Type value: A single text value.
Type special notes: . The type may include the type parameter "TYPE" Type special notes: The type may include the type parameter "TYPE" to
to specify the format or preference of the electronic mail address. specify the format or preference of the electronic mail address. The
The TYPE parameter values may include: "internet" to indicate an TYPE parameter values may include: "internet" to indicate an Internet
Internet addressing type, "x400" to indicate a X.400 addressing type addressing type, "x400" to indicate a X.400 addressing type or "pref"
or."pref" to indicate a preferred-use email address when more than to indicate a preferred-use email address when more than one is
one is specified. Another IANA registered address type may also be specified. Another IANA registered address type may also be
specified. The default email type is "internet". A non-standard value specified. The default email type is "internet". A non-standard value
may also be specified. may also be specified.
Type example: Type example:
EMAIL;TYPE=internet:jqpublic@xyz.dom1.com Dawson & Howes [Page 11] May 1998
Dawson & Howes [Page 10] Expires January 1998
vCard MIME Directory Profile vCard MIME Directory Profile
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
4.3.3 MAILER Type Definition 4.3.3 MAILER Type Definition
To: ietf-mime-directory@imc.org 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
skipping to change at line 589 skipping to change at line 661
To: ietf-mime-directory@imc.org 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: 8bit
quoted-printable.
Type value: text. Type value: A single text value.
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
skipping to change at line 623 skipping to change at line 694
Subject: Registration of application/directory MIME type TZ Subject: Registration of application/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.
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 a single utc-offset value. It may also be
reset to a single text value.
Type examples:
TZ:-05:00 Type special notes: The type value consists of a single value.
Dawson & Howes [Page 11] Expires January 1998 Dawson & Howes [Page 12] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
Type examples:
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.
4.4.2 GEO Type Definition 4.4.2 GEO Type Definition
To: ietf-mime-directory@imc.org 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
skipping to change at line 683 skipping to change at line 758
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.5.1 TITLE Type Definition 4.5.1 TITLE Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type TITLE Subject: Registration of application/directory MIME type TITLE
Type name: TITLE Dawson & Howes [Page 13] May 1998
Dawson & Howes [Page 12] Expires January 1998
vCard MIME Directory Profile vCard MIME Directory Profile
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: The default is 8bit. May also be reset to 7bit or Type encoding: 8bit
quoted-printable.
Type value: text. 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:
TITLE:Director, Research and Development TITLE:Director, Research and Development
4.5.2 ROLE Type Definition 4.5.2 ROLE Type Definition
To: ietf-mime-directory@imc.org 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: 8bit
quoted-printable.
Type value: text. Type value: A single text value.
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
skipping to change at line 740 skipping to change at line 813
To: ietf-mime-directory@imc.org 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
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 encoding MUST be reset to "b" using the ENCODING
order to permit inline encoded binary data. parameter in order to specify inline, encoded binary data. If the
Dawson & Howes [Page 13] Expires January 1998 Dawson & Howes [Page 14] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
Type value: The default is binary. It may also be reset to url. The value is referenced by a URI value, then the default encoding of 8bit
url value may be used to specify a value outside of this MIME entity. is used and no explicit ENCODING parameter is needed.
Type value: A single value. The default is binary. It may also be
reset to uri. The uri 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 or a non-standard image be one of the IANA registered image formats or a non-standard image
format. format.
Type example: Type example:
LOGO;VALUE=URL: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
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
4.5.4 AGENT Type Definition 4.5.4 AGENT Type Definition
To: ietf-mime-directory@imc.org 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.
Type value: The default is vcard. It may also be reset to text or Type value: The default is a single vcard value. It may also be reset
url. The text value may be used to specify textual information. The to either a single text or uri value. The text value may be used to
url value may be used to specify information outside of this MIME specify textual information. The uri value may be used to specify
entity. information outside of this MIME 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=uri:
CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com
AGENT:BEGIN:VCARD\n
FN:Susan Thomas\n
TEL:+1-919-555-1234\n
Dawson & Howes [Page 15] May 1998
vCard MIME Directory Profile
EMAIL;INTERNET:sthomas@host.com\n
END:VCARD\n
4.5.5 ORG Type Definition 4.5.5 ORG Type Definition
To: ietf-mime-directory@imc.org 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
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 Type encoding: 8bit
vCard MIME Directory Profile
Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type value: text. Type value: A single structured text value consisting of components
separated the SEMI-COLON character (ASCII decimal 59).
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 one or more levels
units. The text components are separated the SEMI-COLON character of organizational unit names.
(ASCII decimal 59).
Type example: Type example: A type value consisting of an organizational name,
organizational unit #1 name and organizational unit #2 name.
ORG:ABC, Inc.;North American Division;Marketing ORG:ABC, Inc.;North American Division;Marketing
4.6 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.6.1 CATEGORIES Type Definition 4.6.1 CATEGORIES Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type CATEGORIES Subject: Registration of application/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: The default is 8bit. May also be reset to 7bit or Type encoding: 8bit
quoted-printable.
Type value: text.
Type special notes: More than one category may be specified as a list Type value: One or more text values separated by a COMMA character
of categories separated by a COMMA (ASCII Decimal 44) character. (ASCII decimal 44).
Type example: Type example:
CATEGORIES:TRAVEL AGENT CATEGORIES:TRAVEL AGENT
Dawson & Howes [Page 16] May 1998
vCard MIME Directory Profile
CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY
4.6.2 NOTE Type Definition 4.6.2 NOTE Type Definition
To: ietf-mime-directory@imc.org 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: 8bit
quoted-printable.
Type value: text. 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.
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.
4.6.3 PRODID Type Definition 4.6.3 PRODID Type Definition
skipping to change at line 889 skipping to change at line 974
Subject: Registration of application/directory MIME type PRODID Subject: Registration of application/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.
Type encoding: 8-bit. Type encoding: 8-bit.
Type value: Text. Type value: A single text value.
Type special notes: Implementations SHOULD use a method such as that
specified for Formal Public Identifiers in ISO 9070 to assure that
the text value is unique.
Type example: Type example:
PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN
4.6.4 REV Type Definition 4.6.4 REV Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type REV Subject: Registration of application/directory MIME type REV
Dawson & Howes [Page 17] May 1998
vCard MIME Directory Profile
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 a single date-time value. May also be
reset to a single date value.
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
Dawson & Howes [Page 16] Expires January 1998
vCard MIME Directory Profile
date and time of day format. The value distinguishes the current Type special notes: The value distinguishes the current revision of
revision of the information defining this vCard. the information in this vCard for other renditions of the
information.
Type example: Type example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
4.6.5 SOUND Type Definition REV:1997-11-15
4.6.5 SORT-STRING Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type SOUND Subject: Registration of text/directory MIME type SORT-STRING
Type name: SOUND Type Name: SORT-STRING
Type purpose: To specify a digital sound content information that Type purpose: To specify the text to be used in national language
annotates some aspect of the vCard. By default this type is used to specific sorting of the values specified by the FN or N types.
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 7bit or
order to permit inline encoded binary data. quoted-printable.
Type value: The default is binary. It may also be reset to url. The Type value: text
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 sort string is used to provide text that is
specify the audio format type. The TYPE parameter values MUST be one to be used in locale- or national language-specific sorting of the
of the IANA registered audio formats or a non-standard audio format. values for the formatted name or structured name types. Without this
information, sorting algorithms may incorrectly sort this vCard
within a sequence of sorted vCards. If this type is present in a
vCard, then this value should be used for sorting the vCard, instead
of the values of the FN or N types.
Type example: Type example: The following would define the sort string "Harten" for
SOUND;TYPE=BASIC;VALUE=URL:CID:JOHNQPUBLIC.part8. the "FN:Rene J. van der Harten" or "N:van der
19960229T080000.xyzMail@host1.com Harten;Rene;J.;Sir;R.D.O.N.".
4.6.6 URL Type Definition SORT-STRING:Harten
4.6.6 SOUND Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type URL Dawson & Howes [Page 18] May 1998
Type name: URL vCard MIME Directory Profile
Type purpose: To specify a uniform resource locator associated with Subject: Registration of application/directory MIME type SOUND
the object that the vCard refers to.
Type encoding: 8bit. Type name: SOUND
Type value: url. Type purpose: To specify a digital sound content information that
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.
Type example: Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the
value is referenced by a URI value, then the default encoding of 8bit
is used and no explicit ENCODING parameter is needed.
URL:http://www.swbyps.restaurant.french/~chezchic.html Type value: A single value. The default is binary. It may also be
reset to uri. The uri value may be used to specify a value outside of
this MIME entity.
Dawson & Howes [Page 17] Expires January 1998 Type special notes: The type MAY include the type parameter "TYPE" to
specify the audio format type. The TYPE parameter values MUST be one
of the IANA registered audio formats or a non-standard audio format.
vCard MIME Directory Profile Type example:
SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com
SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN
AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm
ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
<...the remainder of "B" encoded binary data...>
4.6.7 UID Type Definition 4.6.7 UID Type Definition
To: ietf-mime-directory@imc.org 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.
Type value: text. Type value: A single text value.
Type special notes: The type is used to uniquely identify the object Type special notes: The type is used to uniquely identify the object
that the vCard represents. that the vCard represents.
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.
Dawson & Howes [Page 19] May 1998
vCard MIME Directory Profile
Type example: Type example:
UID:19950401-080045-40000F192713-0052 UID:19950401-080045-40000F192713-0052
4.6.8 Version Type Definition 4.6.8 URL Type Definition
To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type URL
Type name: URL
Type purpose: To specify a uniform resource locator associated with
the object that the vCard refers to.
Type encoding: 8bit
Type value: A single uri value.
Type example:
URL:http://www.swbyps.restaurant.french/~chezchic.html
4.6.9 VERSION Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type VERSION Subject: Registration of application/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.
Type encoding: 8bit. Type encoding: 8bit
Type value: text. Type value: A single text value.
Type special notes: The value must be "2.2" if the vCard version Type special notes: The value MUST be "3.0" if the vCard version
corresponds to this specification. corresponds to this specification.
Type example: Type example:
VERSION: 2.2 VERSION: 3.0
Dawson & Howes [Page 18] Expires January 1998
vCard MIME Directory Profile
4.7 Security Types 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.7.1 CLASSIFICATION Type Definition 4.7.1 CLASS Type Definition
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type Dawson & Howes [Page 20] May 1998
CLASSIFICATION
vCard MIME Directory Profile
Subject: Registration of application/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.
Type encoding: The default is 8bit. May also be reset to 7bit or Type encoding: 8bit
quoted-printable.
Type value: text. 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
skipping to change at line 1074 skipping to change at line 1205
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of application/directory MIME type KEY Subject: Registration of application/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.
Type encoding: The default is 8bit. May also be reset to base64. Type encoding: The encoding MUST be reset to "b" using the ENCODING
parameter in order to specify inline, encoded binary data. If the
value is a text value, then the default encoding of 8bit is used and
no explicit ENCODING parameter is needed.
Type value: The default is text. May also be reset to binary. Type value: A single value. The default is binary. It may also be
reset to text. The text value may be used to specify a text key.
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
parameter type may specify any IANA registered public key or
authentication certificate format. The parameter type may also
specify a non-standard format.
Dawson & Howes [Page 19] Expires January 1998 Type example:
KEY;ENCODING=b: MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA
wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX
Dawson & Howes [Page 21] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
parameter type may specify any IANA registered public key or Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0
authentication certificate format. The parameter type may also ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj
specify a non-standard format. E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD
VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx
MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz
Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ
EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2
dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB
EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau
+hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP
mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y
rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7
UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ==
4.8 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 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
be defined bilaterally between two cooperating agents without outside be defined bilaterally between two cooperating agents without outside
registration or standardization. registration or standardization.
5. Differences With vCard v2.1 5. Differences With 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 with the [VCARD] review process introduced a number of differences with the [VCARD]
version 2.1. These differences are minor, but require that vCard version 2.1. These differences are minor, but require that vCard
objects conforming to this specification have a different version objects conforming to this specification have a different version
number than a vCard conforming to [VCARD]. The differences include number than a vCard conforming to [VCARD]. The differences include
the following: the following:
∑ VERSION value corresponding to this specification must be . The QUOTED-PRINTABLE inline encoding has been eliminated.
"2.2". Only the "B" encoding of [RFC 2047] is an allowed value for
the ENCODING parameter.
The [MIME-DIR] predefined types of PROFILE, SOURCE, NAME are . The method for specifying CRLF character sequences in type
allowed. values has been changed. The CRLF character sequence in a
type value is specified with the backslash character sequence
"\n" or "\N".
∑ The [MIME-DIR] VALUE type parameter for value data typing is . Any COMMA or SEMICOLON in a type value must be backslash
allowed. escaped.
The [VCARD] CHARSET type parameter has been eliminated. . VERSION value corresponding to this specification must be
"3.0".
. The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE
are allowed.
. The [MIME-DIR] VALUE type parameter for value data typing is
allowed. In addition, there are extensions made to these type
values for additional value types used in this specification.
Dawson & Howes [Page 22] May 1998
vCard MIME Directory Profile
. The [VCARD] CHARSET type parameter has been eliminated.
Character set may only be specified on the CHARSET parameter Character set may only be specified on the CHARSET parameter
on the Content-Type MIME header field. on the Content-Type MIME header field.
The [VCARD] support for non-signficant LWSP character been . The [VCARD] support for non-signficant LWSP character, other
eliminated. All LWSP is significant in this specification. than after the COMMA character list separator, SEMICOLON
character value component separator and the COLON value
separator has been eliminated.
LOGO, PHOTO and SOUND multimedia formats need to be either . LOGO, PHOTO and SOUND multimedia formats need to be either
IANA registered types or non-standard types. IANA registered types or non-standard types.
TEL values may be identified as personal communication . Inline binary content must be "B" encoded and folded. A blank
line after the encoded binary content is nolonger required.
. TEL values may be identified as personal communication
services telephone numbers with the PCS type parameter value. services telephone numbers with the PCS type parameter value.
The PRODID, CATEGORIES and CLASS types have been added. . The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
have been added.
6. Formal Grammar 6. 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 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.)
WS = (SPACE / HTAB)
All literal property names are valid as upper, lower, or mixed case. All literal property names are valid as upper, lower, or mixed case.
word = <any printable 7bit us-ascii except []=:., > char = <any printable character from the current
character set >
groups = groups "." word word = 1*char
/ word
group = word "."
vcard_entity = 1*(vcard) vcard_entity = 1*(vcard)
vcard = "BEGIN" ":" "VCARD" 1*CRLF vcard = [group] "BEGIN" ":" [WS] "VCARD" 1*CRLF
items *CRLF 1*([group] item *CRLF
"END" ":" "VCARD" 1*CRLF [group] "END" ":" [WS] "VCARD" 1*CRLF
;All lines may be "folded".
items = items *CRLF item item = "NAME" *txtparam ":" [WS] text CRLF
/ item / "PROFILE" *txtparam ":" [WS] "VCARD" CRLF
; these may be "folded"
item = [groups "."] name Dawson & Howes [Page 23] May 1998
[params] ":" value CRLF
/ [groups "."] "ADR"
[params] ":" addressparts CRLF
/ [groups "."] "ORG"
[params] ":" orgparts CRLF
/ [groups "."] "N"
[params] ":" nameparts CRLF
/ [groups "."] "AGENT"
[params] ":" vcard CRLF
; these may be "folded"
name = "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE" vCard MIME Directory Profile
/ "SOUND" / "VERSION" / "TEL" / "EMAIL" / "TZ"
/ "GEO" / "NOTE" / "SOURCE" / "NAME" / "PROFILE"
/ "URL" / "BDAY" / "ROLE" / "REV" / "UID" / "KEY"
/ "MAILER" / "CATEGORIES" / "CLASS" / "PRODID"
/"X-" word
; these may be "folded"
value = 7bit / quoted-printable / base64 / "SOURCE" *srcparam ":" [WS] uri CRLF
/ "FN" *txtparam ":" [WS] text CRLF
/ "N" *(txtparam) ":" [WS] nameparts CRLF
/ "NICKNAME" *(txtparam) ":" [WS] text *("," [WS] text)
CRLF
/ "PHOTO" (imginline / imgrefer)
/ "BDAY" (dateval / datetimeval)
/ "ADR" adrparam ":" [WS] adrparts CRLF
/ "LABEL" *(adrparam) ":" [WS] text CRLF
/ "TEL" *(telparam) ":" [WS] phone-number CRLF
/ "EMAIL" *(emailparam) ":" [WS] text CRLF
/ "MAILER" *txtparam ":" [WS] text CRLF
/ "TZ" [";" [WS] "VALUE" "=" "utc-offset"] ":"
[WS] utc-offset
/ "GEO" [";" [WS] "VALUE" "=" "float"] ":"
float ";" float
/ "TITLE" *txtparam ":" [WS] text CRLF
/ "ROLE" *txtparam ":" [WS] text CRLF
/ "LOGO" (imginline / imgrefer)
/ "AGENT" ":" text CRLF
;The text value MUST be a string of vCard types, each
;type terminated with a "\n" or "\N" escapement.
/ "ORG" *txtparam ":" [WS] orgparts CRLF
/ "CATEGORIES" *txtparam ":" [WS] text *("," [WS] text)
CRLF
/ "NOTE" *txtparam ":" [WS] text CRLF
/ "PRODID *txtparam ":" [WS] text CRLF
/ "REV" (dateval / datetimeval)
/ "SOUND" (sndinline / sndrefer)
/ "URL" [";" [WS] "VALUE" "=" "uri"] ":" [WS] uri CRLF
/ "UID" [";" [WS] "VALUE" "=" "text"] ":" [WS] text CRLF
/ "VERSION" ":" "3.0"
/ "CLASS" *txtparam ":" [WS] text CRLF
/ "KEY" (keytext) / (keybinary)
/ "X-" word *txtparam ":" [WS] value
7bit = <7bit us-ascii printable chars, excluding CR LF> txtparam = (";" [WS] "VALUE" "=" "text")
/ (";" [WS] "LANGUAGE" "=" langval)
/ (";" [WS] "X-" word "=" word)
8bit = <MIME RFC 2045 8-bit text> langval = <a language string as defined in RFC 1766>
quoted-printable = <MIME RFC 2045 quoted-printable text> srcparam = (";" [WS] "VALUE" "=" "uri")
/ (";" [WS] "CONTEXT" "=" word)
;Parameter values specifies the protocol
; context for the URI value.
/ (";" [WS] "X-" word "=" word)
base64 = <MIME RFC 2045 base64 text> adrparam = ";" [WS] ["TYPE" "="] adrtype *("," [WS] adrtype)
; the end of the text is marked with two CRLF sequences *(txtparam)
Dawson & Howes [Page 21] Expires January 1998 adrtype = "dom" / "intl" / "postal" / "parcel" / "home"
/ "work" / "pref" / ianatype / "X-" word
Dawson & Howes [Page 24] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
; this results in one blank line before the start of the next adrparts = 0*6(text ";") text
; property ; PO Box, Extended Address, Street, Locality, Region, Postal
; Code, Country Name
params = ";" paramlist orgparts = *(text ";") text
; First is Organization Name, remainder are Organization Units.
paramlist = paramlist ";" param nameparts = 0*4(text *("," text) ";") text *("," text)
/ param ; Family, Given, Middle, Prefix, Suffix.
; Example:Public;John;Q.;Reverend Dr.;III, Esq.
param = "TYPE" "=" ptypeval telparam = ";" [WS] ["TYPE" "="] teltype *("," [WS] teltype)
/ "VALUE" "=" pvalueval
/ "ENCODING" "=" pencodingval
/ "LANGUAGE" "=" langval
/ "X-" word "=" word
/ knowntype / ianatype
ptypeval = knowntype / "X-" word teltype = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG"
/ "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN"
/ "VIDEO" / "PCS" / ianatype / "X-" word
pvalueval = "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME" emailparam = ";" [WS] ["TYPE" "="] emailtype ["," [WS] "PREF"]
/ "INTEGER" / "BOOLEAN" / "FLOAT" / "BINARY" /
/ "VCARD" / "PHONE-NUMBER" / "UTC-OFFSET" / "X-" word
pencodingval = "7BIT" / "8BIT" / "QUOTED-PRINTABLE" / "BASE64" emailtype = "INTERNET" / "X400" / ianatype / "X-" word
/ "X-" word
langval = <a language string as defined in RFC 1766> imginline = imginlparm ":" [WS] binary CRLF
;Value MUST be "b" encoded image content
addressparts = 0*6(strnosemi ";") strnosemi imginlparm = [";" [WS] "VALUE" "=" "binary"]
; PO Box, Extended Addr, Street, Locality, Region, Postal Code, ";" [WS] "ENCODING" "=" "b"
; Country Name ";" [WS] "TYPE" "=" word
;Value MUST be an IANA registered image type
orgparts = *(strnosemi ";") strnosemi imgrefer = imgrefparm ":" [WS] uri
; First is Organization Name, remainder are Organization Units. ;URI MUST refer to image content of given type
nameparts = 0*4(strnosemi ";") strnosemi imgrefparm = ";" [WS] "VALUE" "=" "uri"
; Family, Given, Middle, Prefix, Suffix. ";" [WS] "TYPE" "=" word
; Example:Public;John;Q.;Reverend Dr.;III, Esq. ;Value MUST be an IANA registered image type
strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi sndinline = sndinlparm ":" [WS] binary CRLF
; To include a semicolon in this string, it must be escaped ;Value MUST be "b" encoded audio content
; with a "\" character.
nonsemi = <any non-control ASCII except ";"> sndinlparm = [";" [WS] "VALUE" "=" "binary"]
";" [WS] "ENCODING" "=" "b"
";" [WS] "TYPE" "=" word
;Value MUST be an IANA registered audio type
knowntype = "DOM" / "INTL" / "POSTAL" / "PARCEL" / "HOME" / "WORK" sndrefer = sndrefparm ":" [WS] uri
/ "PREF" / "VOICE" / "FAX" / "MSG" / "CELL" / "PAGER" ;URI MUST refer to audio content of given type
/ "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO" / "PCS"
/ "INTERNET" / "X400" / "X509" / "PGP"
ianatype = <Any IANA registered value> sndrefparm = ";" [WS] "VALUE" "=" "uri"
";" [WS] "TYPE" "=" word
;Value MUST be an IANA registered audio type
Dawson & Howes [Page 22] Expires January 1998 dateval = [";" [WS] "VALUE" "=" "date"] ":" [WS] date
datetimeval = ";" [WS] "VALUE" "=" "date-time" ";" [ws] date-time
Dawson & Howes [Page 25] May 1998
vCard MIME Directory Profile vCard MIME Directory Profile
/ "KEY" (keytext) / (keybinary)
keytext = [";" [WS] "TYPE" "=" keytype] [";" [WS] "TYPE" "="
"text"] ":" text
keybinary = [";" [WS] "TYPE" "=" keytype] (";" [WS] "TYPE" "="
"binary") (";" [WS] "ENCODING" "=" "b") ":" [WS]
binary
;Value MUST be a "b" encoded key or certificate
keytype = "X509" / "PGP" / ianatype / "X-" word
value = binary / boolean / date / date-time / float / integer
/ phone-number / text / time / utc-offset / vcard /
/ ianavalue
text = *(word WS)
; To include a SEMICOLON in this string it must be escaped
; with a "\" character. To include a COMMA in this string it
; MUST be escaped with a "\" characer.
binary = <A text string as defined in [RFC 2047]>
date = <A single value as defined in [MIME-DIR]>
time = <A single value as defined in [MIME-DIR]>
date-time = <A single value as defined in [MIME-DIR]
float = <A single value as defined in [MIME-DIR]>
phone-number = <A text value as defined in [CCITT E.163] and
[CCITT X.121]>
uri = <A single value as defined in RFC 1738>
utc-offset = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
ianatype = <Any IANA registered value>
ianavalue = <ANY IANA registered value type format>
6.1 Acknowledgements 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 Gurney, Bruce Johnston, Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce Johnston,
Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who
provided numerous suggestions and comments on this work. provided numerous suggestions and comments on this work.
6.2 Authorsís Addresses Dawson & Howes [Page 26] May 1998
vCard MIME Directory Profile
6.2 Authors's Addresses
BEGIN:vCard BEGIN:vCard
FN:Frank Dawson FN:Frank Dawson
ORG:IBM Corporation;Network Software Division ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002; ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
3039 Cornwallis Rd.;Research Triangle Park; ;Raleigh;NC;27613-3502;U.S.A.
NC;27709;U.S.A. TEL;TYPE=VOICE,MSG,WORK: +1-919-676-9515
TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861 TEL;TYPE=FAX,WORK: +1-919-676-9564
TEL;TYPE=FAX,WORK: +1-919-543-6822 EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET,PREF:fdawson@raleigh.ibm.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson URL:http://home.earthlink.net/~fdawson
END:vCard END:vCard
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
6.3 References 6.3 References
The following documents are referenced by this work. The following documents are referenced by this work.
skipping to change at line 1308 skipping to change at line 1562
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.
Dawson & Howes [Page 27] May 1998
vCard MIME Directory Profile
[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-04.txt, July, Information", Internet-draft-ietf-asid-mime-direct-05.txt, November,
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-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
Resource Locators (URL)", RFC 1738, December 1994.
[RFC-1766] Alvestrand, H., "Tags for the Identification of
Languages", March 1995.
[RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type,"
RFC 1872, December 1995.
[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
Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996. 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 (MIME) -
Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
November 1996. November 1996.
[RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet [RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
Mail Extensions (MIME) - Part Four: Registration Procedures", RFC Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
2048, January 1997. 2048, January 1997.
[RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform [RFC2119] "Key words for use in RFCs to Indicate Requirement Levels",
Resource Locators (URL)", RFC 1738, December 1994. RFC 2119, March 1997.
[RFC-1766] Alvestrand, H., "Tags for the Identification of
Languages", March 1995.
[RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type,"
RFC 1872, December 1995.
[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 24] Expires January 1998 7. Full Copyright Statement
"Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it MAY be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation MAY be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself MAY not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process MUST be
Dawson & Howes [Page 28] May 1998
vCard MIME Directory Profile
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
__
Dawson & Howes [Page 29] May 1998
 End of changes. 188 change blocks. 
359 lines changed or deleted 616 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/