draft-ietf-asid-mime-vcard-01.txt   draft-ietf-asid-mime-vcard-02.txt 
Network Working Group Frank Dawson Network Working Group Frank Dawson
INTERNET DRAFT Tim Howes INTERNET DRAFT Tim Howes
draft-ietf-asid-mime-vcard-01.txt IBM/Netscape Communications ietf-asid-mime-vcard-02.txt Lotus/Netscape Communications
November 26, 1996 March 26, 1997
An Application/Directory MIME Content-Type vCard MIME Directory Profile
Electronic Business Card 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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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).
Abstract Abstract
This memo defines a directory information profile for a white pages This memo defines the profile of the MIME Content-Type [MIME-DIR] for
person, to be carried in an application/directory MIME Content-Type. directory information for a white-pages person object, based on a
The profile consists of type definitions (e.g., for name and email vCard electronic business card. The profile definition is independent
address) and the corresponding format of values that each type is of any particular directory service or protocol. The profile is
allowed to contain. defined for representing and exchanging a variety of information
about an individual (e.g., formatted and structured name and delivery
addresses, email address, multiple telephone numbers, photograph,
logo, audio clips, etc.). The directory information used by this
profile is based on the attributes for the person object defined in
the X.520 and X.521 directory services recommendations. The profile
also provides the method for including a [VCARD] representation of a
white-pages directory entry within the MIME Content-Type defined by
the [MIME-DIR] document.
1. Overview 1. Overview
The application/directory MIME Content-Type defined in [MIME-DIR] is The [MIME-DIR] document defines a MIME Content-Type for holding
used for representing directory information in MIME format. It different kinds of directory information. The directory information
defines a general framework for carrying _type: value_ style may be based on any of a number of directory schemas. This document
information in the body of a MIME message, but does not define defines a [MIME-DIR] usage profile for conveying directory
specific types or values. This document defines a profile containing information based on one such schema; that of the white-pages type of
the types and corresponding value formats for representing person object.
information about an electronic business card. The profile reflects
the vCard (The Electronic Business Card) schema defined in [VCARD].
1.1 The vCard Profile The schema is based on the attributes for the person object defined
in the X.520 and X.521 directory services recommendations. The schema
has augmented the basic attributes defined in the X.500 series
recommendation in order to provide for an electronic representation
of the information commonly found on a paper business card. This
The profile is defined as follows, using the profile registration Dawson & Howes [Page 1] Expires September 1997
template from Section 8 of [MIME-DIR].
1.2 vCard Profile Definition vCard MIME Directory Profile
To: ietf-mime-direct@umich.edu schema was first defined in the [VCARD] document. Hence, this [MIME-
DIR] profile is referred to as the vCard MIME Directory Profile.
Subject: Registration of application/directory MIME profile vcard A directory entry based on this usage profile can include traditional
directory, white-pages information such as the distinguished name
used to uniquely identify the entry, a formatted representation of
the name used for user-interface or presentation purposes, both the
structured and presentation form of the delivery address, various
telephone numbers and organizational information associated with the
entry. In addition, traditional paper business card information such
as an image of an organizational logo or identify photograph can be
included in this person object.
Dawson & Howes [Page 1] Expires June 1997 The vCard MIME Directory Profile also provides support for
representing other important information about the person associated
with the directory entry. For instance, the date of birth of the
person; an audio clip describing the pronunciation of the name
associated with the directory entry, or some other application of the
digital sound; longitude and latitude geo-positioning information
related to the person associated with the directory entry; date and
time that the directory information was last updated; annotations
often written on a business card; Uniform Resource Locators (URL) for
a website; public key information. The profile also provides support
for non-standard extensions to the schema. This provides the
flexibility for implementations to augment the current capabilities
of the profile in a standardized way. More information about this
electronic business card format can be found in [VCARD].
vCard Application/Directory Content Type 2. The vCard Mime Directory Profile Registration
Profile name: vcard This profile is identified by the following [MIME-DIR] registration
template information. Subsequent sections define the profile
definition.
Profile purpose: To hold vcard information about an electronic To: ietf-mime-directory@umich.edu
business card.
Profile types: BEGIN, END, FN, N, PHOTO, BDAY, ADR, LABEL, TEL, Subject: Registration of application/directory MIME profile VCARD
EMAIL, MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV,
SOUND, URL, UID, VERSION, KEY
Profile special notes: The content entity must begin with the type Profile name: VCARD
BEGIN and end with the type END. There is no other ordering
limitations on types within the content entity.
The default transfer encoding for the vCard profile is _8BIT_. The Profile purpose: To hold person object or white-pages type of
default transfer encoding can be overridden for an individual type directory information. The person schema captured in the directory
value by using the _ENCODING_ type parameter. The parameter value can entries is that commonly found in an electronic business card.
be reset to either _7BIT_, _BASE64_ or _QUOTED-PRINTABLE_. This type
parameter may be used on any profile type.
The usual line-folding technique described in [MIME-DIR] can be used Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN,
to represent type values consisting of long lines of text. For END, PROFILE.
example, individual lines in the content entity are delimited by the
[RFC 822] line break, which is a CRLF sequence (ASCII decimal 13,
followed by ASCII decimal 10). Long lines of text can be split into a
multiple-line representation using the RFC 822 _folding_ technique.
That is, wherever there may be linear white space (NOT simply LWSP-
chars), a CRLF immediately followed by at least one LWSP-char may
instead be inserted. For example the line:
NOTE:This is a long note that exists on a long line. Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET,
LANGUAGE, CONTEXT.
Can be represented as: New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ,
GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV, SOUND, URL, UID,
VERSION, KEY
NOTE:This is a long note Dawson & Howes [Page 2] Expires September 1997
that exists on a long line.
The process of moving from this folded multiple-line representation vCard MIME Directory Profile
of a type value to its single line representation is called
_unfolding_. Unfolding is accomplished by regarding CRLF immediately
followed by a LWSP-char as equivalent to the LWSP-char.
It is recommended that folding be limited to higher-level syntactic New parameters: TYPE
breaks in structured components of the property definition.
A formatted text line break in a type value, MUST also be specified Profile special notes: The type-grouping feature of [MIME-DIR] is
by a (RFC 822) line break, which is a CRLF sequence. However, since supported by this profile to group related vCard properties about a
the CRLF sequence is used to delimit a line, type values with directory entry. For example, vCard properties describing WORK or
formatted line breaks (i.e., multiple lines) MUST be encoded using an HOME related characteristics MAY be grouped with a unique group
alternate encoding of either Quoted-Printable or Base64, as defined label.
in [RFC 1521].
For example, in the Quoted-Printable encoding the multiple lines of The profile permits the use of non-standard types (i.e., those
formatted text are separated with a Quoted-Printable CRLF sequence of identified with the prefix string "X-") as a flexible method for
_=0D_ followed by _=0A_ followed by a Quoted-Printable soft line implementations to extend the functionality currently defined within
this profile.
Dawson & Howes [Page 2] Expires June 1997 3. MIME Directory Features
vCard Application/Directory Content Type The vCard MIME Directory Profile makes use of many of the features
defined by [MIME-DIR]. The following sub-sections describe specific
usage constraints or extensions of these predefined features.
break sequence of _=_. Quoted-Printable lines of text must also be 3.1 BEGIN and END Type
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.
3.2 NAME Type
If the NAME type appears within a MIME entity conforming to this
profile, it's value is the displayable, presentation text associated
with the source for the vCard, as specified in the SOURCE type.
3.3 PROFILE Type
If the PROFILE type appears within a MIME entity conforming to this
profile, it's value must be "VCARD".
3.4 SOURCE Type
If the SOURCE type appears within a MIME entity conforming to this
profile, it's value provides information how to find the source for
the vCard.
3.5 ENCODING Parameter
The default transfer encoding for the vCard profile is "8bit". The
default transfer encoding MAY be overridden for an individual type
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
vCard MIME Directory Profile
3.6 CHARSET Parameter
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 limited to less than 76 characters. The 76 characters does not
include the CRLF [RFC 822] line break sequence. For example a include the CRLF [RFC 822] line break sequence. For example a
multiple line LABEL value of: multiple line LABEL value of:
Mr. John Q. Public Mr. John Q. Public
123 Main Street 123 Main Street
Any Town, CA 12345 Any Town, CA 12345
Would be represented in a Quoted-Printable encoding as: Would be represented in a Quoted-Printable encoding as:
LABEL;ENCODING=QUOTED-PRINTABLE:Mr. John Q. Public=0D=0A= LABEL;ENCODING=QUOTED-PRINTABLE:Mr. John Q. Public=0D=0A=
123 Mail Street=0D=0A= 123 Mail Street=0D=0A=
Any Town, CA 12345 Any Town, CA 12345
3.9 Structured Type Values
Compound property values are delimited by a field delimiter, Compound property values are delimited by a field delimiter,
specified by the SEMI-COLON character (ASCII decimal 59). A SEMI- specified by the SEMI-COLON character (ASCII decimal 59). A SEMI-
COLON in a component of a compound property value must be escaped COLON in a component of a compound property value must be escaped
with a Backslash character with a Backslash character
The default character set is _UTF-8_. The default character set can Dawson & Howes [Page 4] Expires September 1997
be overridden for an individual type value by using the _CHARSET_
type parameter. This type parameter may be used on any profile type.
However, the use of this parameter on some profile types may not make
sense.
The default language is _en-US_ (US English). The default language
can be overridden for an individual type value by using the
_LANGUAGE_ type parameter. This type parameter may be used on any
profile type. However, the use of this parameter on some profile
types may not make sense.
The default location of the type values is inline with the profile vCard MIME Directory Profile
type. However, for some profile types, such as those that specify
multimedia values, it is efficient to organize the type value as a
separate MIME entity. The type parameter _VALUE_ can be specified to
override the _INLINE_ location of the type value. The type value can
be specified as being located in a separate MIME entity with the
_CID_ value. In this case, the type value is the Content-ID for the
MIME entity containing the type value. In addition, the type value
can be specified as being located out on the network within some
Internet resource with the _URL_ value. In this case, the type value
is the Uniform Resource Locator for the Internet resource containing
the type value. This type parameter may be used on any profile type.
However, the use of this parameter on some profile types may not make
sense.
This profile supports the type grouping mechanism defined in [MIME- This profile supports the type grouping mechanism defined in [MIME-
DIR]. Grouping of related profile types is a useful technique to DIR]. Grouping of related types is a useful technique to communicate
communicate common semantics concerning the properties of a vCard common semantics concerning the properties of a vCard.
object.
Intended usage: COMMON
Dawson & Howes [Page 3] Expires June 1997
vCard Application/Directory Content Type
The associated type definitions follow, using the type registration
template from Section 9 of [MIME-DIR].
1.3 Delimiter Profile Types
The following profile types are used to delimit the vCard data within
the content type. These types are necessary to completely define the
content type so that it might be identified as a vCard object when
the content type is in a persistent form outside of a MIME message.
1.3.1 BEGIN Type Definition 4. vCard Features
To: ietf-mime-direct@umich.edu 4.1 VALUE Type Parameter
Subject: Registration of application/directory MIME type BEGIN The predefined data type values specified in [MIME-DIR] have been
extended by the vCard profile to include a number of value types that
are specific to this profile.
Type name: BEGIN 4.1.1 BINARY
Type purpose: To delimit the beginning of the vCard content data. The "binary" value type specifies that the type value is inline,
encoded binary data. This value type may be specified in the PHOTO,
LOGO, SOUND, and KEY types.
Type encoding: text. If inline, encoded binary data is specified, the ENCODING type
parameter must be used to specify the encoding format.
Type special notes: The only valid value is _vCard_. The value type is defined by the following notation:
Type example: binchar = <Any character valid in the base64 or quoted-printable
encoding>
binary = *binchar ;A base64 or quoted-printable
encoding of the binary information
BEGIN:vCard 4.1.2 VCARD
1.3.2 END Type Definition The "vcard" value type specifies that the type value is another
vCard. This value type may be specified in the AGENT type. The value
type is defined by this specification.
To: ietf-mime-direct@umich.edu 4.1.3 PHONE-NUMBER
Subject: Registration of application/directory MIME type END The "phone-number" value type specifies that the type value is a
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
number.
Type name: END 4.1.4 UTC-OFFSET
Type purpose: To delimit the end of the vCard content data. 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.
Type encoding: text. The format of the offset from UTC is defined by [DATETIME]. The value
type is an offset from Coordinated Universal Time (UTC). It is
specified as a positive or negative difference in units of hours and
minutes (e.g., +hh:mm). The time is specified as a 24-hour clock.
Hour values are from 00 to 24, and minute values are from 00 to 59.
Hour and minutes are 2-digits with high order zeroes required to
maintain digit count. The extended format for ISO 8601 UTC offsets
Type special notes: The type either has no value or has the value Dawson & Howes [Page 5] Expires September 1997
_vCard_.
Type example: vCard MIME Directory Profile
END: vCard MUST be used. The extended format makes use of a colon character as a
separator of the hour and minute text fields.
1.4 Identification Profile Types The value is defined by the following notation:
These profile types are concerned with information associated with time-hour = 2DIGIT ;00-24
the identification and naming of the individual or resource time-minute = 2DIGIT ;00-60
associated with the vCard object. time-numzone = ("+" / "-") time-hour ":" time-minute
utc-offset = time-numzone
Dawson & Howes [Page 4] Expires June 1997 4.2 Identification Types
vCard Application/Directory Content Type These types are used in the vCard profile to capture information
associated with the identification and naming of the person or
resource associated with the vCard.
1.4.1 FN Type Definition 4.2.1 FN Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 name string associated with Type purpose: To specify the formatted text corresponding to the name
the vCard object. of the object the vCard represents.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type special notes: The value is intended to be used as a formatted Type value: text.
string corresponding to how the name of the individual or resource
associated with the vCard is to be displayed. This type is based on
the semantics of the X.520 Common Name attribute.
The type may specify the type parameters CHARSET, to specify a Type special notes: This type is based on the semantics of the X.520
character set for the type value, and LANGUAGE, to specify a language Common Name attribute.
for the type value. These are further defined in [MIME-DIR].
Type example: Type example:
FN:Mr. John Q. Public, Esq. FN:Mr. John Q. Public, Esq.
1.4.2 N Type Definition 4.2.2 N Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 name strings associated with Type purpose: To specify the structured components of the name of the
the vCard object. object the vCard represents.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type special note: The type value is a structured string Type value: text.
corresponding, in sequence, to the Family Name, Given Name,
Additional Names, Honorific Prefixes, and Suffixes corresponding to
the individual or resource associated with the vCard. The component
strings are delimited by SEMI-COLON character (ASCII decimal 59) and
possibly one or more LWSP. This type is based on the semantics of the
X.520 individual name attributes.
The type may specify the type parameters CHARSET, to specify a Dawson & Howes [Page 6] Expires September 1997
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: vCard MIME Directory Profile
N:Public;John;Quinlan;Mr.;Esq. Type special note: The type value is structured text corresponding,
in sequence, to the Family Name, Given Name, Additional Names,
Honorific Prefixes, and Honorific Suffixes. The text components are
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
individual name attributes.
Dawson & Howes [Page 5] Expires June 1997 Type example:
vCard Application/Directory Content Type N:Public;John;Quinlan;Mr.;Esq.
1.4.3 PHOTO Type Definition 4.2.3 PHOTO Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 vCard object. By default this type is annotates some aspect of the object the vCard represents.
used to specify a photograph or image of the individual or resource
associated with the vCard.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to base64 in
order to permit inline, encoded binary data.
Type special notes: The type may include the type parameter _TYPE_ to Type value: The default is binary. It may also be reset to url. The
specify the format of the graphic image. The TYPE parameter values url value may be used to specify a value outside of this MIME entity.
may include _GIF_ to indicate the GIF format and _JPEG_ to indicate
the JPEG format. The type may also include the type parameter Type special notes: The type MAY include the type parameter "TYPE" to
_ENCODING_ to specify the content encoding applied to the graphic specify the graphic image format type. The TYPE parameter values MUST
image. The ENCODING parameter value may include _7BIT_ to indicate be one of the IANA registered image formats. In addition, a non-
the 7-bit encoding, _8BIT_ to indicate the 8-bit encoding, _BASE64_ standard image format MAY be specified.
to indicate the Base64 encoding or _QUOTED-PRINTABLE_ to indicate the
quoted printable encoding. The type may also include the type
parameter _VALUE_ to specify the location of the type value. The
VALUE parameter values may include _INLINE_ to indicate that the
graphic image value is included within the content type value, _URL_
to indicate the uniform resource locator for where the content for
the graphic image can be found in the network, and _CID_ to indicate
the content-id for the MIME entity that encapsulates the content for
the graphic image.
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
1.4.4 BDAY Type Definition 4.2.4 BDAY Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 individual associated Type purpose: To specify the birthdate of the object the vCard
with the vCard. represents.
Type encoding: text. Type encoding: 8bit.
Type special notes: The text value is a string conforming to the ISO Type value: The default is date. It may also be reset to date-time.
8601 calendar date, complete representation.
Type example: Type examples:
Dawson & Howes [Page 6] Expires June 1997 Dawson & Howes [Page 7] Expires September 1997
vCard Application/Directory Content Type vCard MIME Directory Profile
BDAY:1996-04-15 BDAY:1996-04-15
1.5 Delivery Addressing Profile Types BDAY:1953-10-15T23:10:00
These profile types are concerned with information associated with BDAY:1987-09-27T08:30:00-06:00
the delivery addressing or label for the vCard object.
1.5.1 ADR Type Definition 4.3 Delivery Addressing Types
To: ietf-mime-direct@umich.edu These types are concerned with information related to the delivery
addressing or label for the object the vCard represents.
4.3.1 ADR Type Definition
To: ietf-mime-directory@umich.edu
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 delivery address strings of Type purpose: To specify the structured components of the delivery
the individual or resource associated with the vCard. address for the object the vCard represents.
Type encoding: text Type encoding: The default is 8bit. It may also be reset to 7bit or
quoted-printable.
Type special notes: The type value is a string consisting of a Type value: text.
sequence of address components (i.e., extended address, street
address, locality, region, postal code, and country name) separated
by SEMI-COLON character (ASCII decimal 59) and optionally one or more
LWSP.
The usual line-folding technique described in [MIME-DIR] can be used Type special notes: The type value is structured text consisting of a
to represent type values consisting of long lines of text. However, a sequence of address components (i.e., extended address, post office
line break character in a value MUST be encoded using either Base64 box, street address, locality, region, postal code, and country name)
or Quoted-Printable methods. separated by the SEMI-COLON character (ASCII decimal 59) and
optionally one or more LWSP.
The type may include the type parameter _TYPE_ to further qualify the The type may include the type parameter "TYPE" to specify the
usage of the delivery address. The TYPE parameter values may include: delivery address type. The TYPE parameter values may include "dom" to
_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_ for the indicate delivery address for a place of work; and "pref" to indicate
preferred delivery address when more than one address might be the preferred delivery address when more than one address might be
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.
The type may also 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:
Dawson & Howes [Page 7] Expires June 1997 Dawson & Howes [Page 8] Expires September 1997
vCard Application/Directory Content Type vCard MIME Directory Profile
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
1.5.2 LABEL Type Definition 4.3.2 LABEL Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 delivery address string of the Type purpose: To specify the formatted text corresponding to delivery
individual or resource associated with the vCard. address of the object the vCard represents.
Type encoding: text Type encoding: The default is 8bit. It may also be reset to 7bit or
quoted-printable.
Type special notes: The type value is a string consisting of a Type value: text.
sequence of lines of formatted text corresponding to the delivery
address.
The usual line-folding technique described in [MIME-DIR] can be used Type special notes: The type value is formatted text that may be used
to represent type values consisting of long lines of text. However, a to present a delivery address label for the object the vCard
formatted line break character in a value MUST be encoded using represents.
either Base64 or Quoted-Printable methods.
The type may include the type parameter _TYPE_ to further qualify the The type may include the type parameter "TYPE" to specify delivery
usage of the delivery label. The TYPE parameter values may include: label type. The TYPE parameter values may include "dom" to indicate a
_DOM_ to indicate a domestic delivery label, _INTL_ to indicate an domestic delivery label; "intl" to indicate an international delivery
international delivery label, _POSTAL_ to indicate a postal delivery label; "postal" to indicate a postal delivery label; "parcel" to
label, _PARCEL_ to indicate a parcel delivery label, _HOME_ to indicate a parcel delivery label; "home" to indicate a delivery label
indicate a delivery label for a residence, _WORK_ to indicate for a residence; "work" to indicate delivery label for a place of
delivery label for a place of work, and _PREF_ for the preferred work; and "pref" to indicate the preferred delivery label when more
delivery label when more than one label might be specified. These than one label might be specified. These type parameter values may
type parameter values may specified as a parameter list (i.e., specified as a parameter list (i.e., "TYPE=dom;TYPE=postal") or as a
_TYPE=DOM;TYPE=POSTAL_) or as a value list (i.e., _TYPE=DOM;POSTAL_). value list (i.e., "TYPE=dom,postal"). This type is based on semantics
This type is based on semantics of the X.520 geographical and postal of the X.520 geographical and postal addressing attributes. The
addressing attributes. The default is _TYPE=INTL;POSTAL;PARCEL;WORK_. default is "TYPE=intl,postal,parcel,work". The default can be
The default can be overridden to some other set of values by overridden to some other set of values by specifying one or more
specifying one or more alternate values. For example, the default can alternate values. For example, the default can be reset to
be reset to _TYPE=INTL;POST;PARCEL;HOME_ to specify an international "TYPE=intl,post,parcel,home" to specify an international delivery
delivery label for both postal and parcel delivery to a residencial label for both postal and parcel delivery to a residencial location.
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.
Dawson & Howes [Page 8] Expires June 1997 4.4 Telecommunications Addressing Types
vCard Application/Directory Content Type These types are concerned with information associated with the
telecommunications addressing of the object the vCard represents.
1.6 Telecommunications Addressing Profile Types Dawson & Howes [Page 9] Expires September 1997
These profile types are concerned with information associated with vCard MIME Directory Profile
the telecommunications addressing of the vCard object.
1.6.1 TEL Type Definition 4.4.1 TEL Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 individual or resource associated with the communication with the object the vCard represents.
vCard.
Type encoding: text. Type encoding: 8bit.
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 further qualify the The type may include the type parameter "TYPE" to specify intended
usage of the telephone number. The TYPE parameter values may include: use for the telephone number. The TYPE parameter values may include:
_HOME_ to indicate a telephone number associated with a residence, "home" to indicate a telephone number associated with a residence,
_MSG_ to indicate the telephone line has voice messaging support, "msg" to indicate the telephone line 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 line, "fax" to indicate a facsimile
telephone line, _CELL_ to indicate a cellular telephone line, _VIDEO_ telephone line, "cell" to indicate a cellular telephone line, "video"
to indicate a video conferencing telephone line, _PAGER_ to indicate to indicate a video conferencing telephone line, "pager" to indicate
a paging device telephone line, _BBS_ to indicate a bulletin board a paging device telephone line, "bbs" to indicate a bulletin board
system telephone line, _MODEM_ to indicate a MODEM connected system telephone line, "modem" to indicate a MODEM connected
telephone line, _CAR_ to indicate a car-phone telephone line, _ISDN_ telephone line, "car" to indicate a car-phone telephone line, "isdn"
to indicate an ISDN service telephone line. The default type is to indicate an ISDN service telephone line. The default type is
_VOICE_. These type parameter values may specified as a parameter "voice". These type parameter values may specified as a parameter
list (i.e., _TYPE=WORK;TYPE=VOICE_) or as a value list (i.e., list (i.e., "TYPE=work;TYPE=voice") or as a value list (i.e.,
_TYPE=WORK;VOICE_). The default may be overridden to another set of "TYPE=work,voice"). The default may be overridden to another set of
values by specifying one or more alternate values. For example, the values by specifying one or more alternate values. For example, the
default TYPE of _VOICE_ can be reset to a WORK and HOME, VOICE and 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_. 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
1.6.2 EMAIL Type Definition 4.4.2 EMAIL Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type EMAIL Subject: Registration of application/directory MIME type EMAIL
Dawson & Howes [Page 9] Expires June 1997 Type name: EMAIL
vCard Application/Directory Content Type Type purpose: To specify the electronic mail address for
communication with the object the vCard represents.
Type name: EMAIL Dawson & Howes [Page 10] Expires September 1997
Type purpose: To specify the address for electronic mail vCard MIME Directory Profile
communication with the vCard object. The address is in the form of a
specific addressing type. The default is an Internet addressing type.
Type encoding: text. Type encoding: 8bit.
Type special notes: . The type may include the type parameter _TYPE_ Type value: text.
to specify the addressing type of the electronic mail address. The
TYPE parameter values may include: _INTERNET_ to indicate an Internet Type special notes: . The type may include the type parameter "TYPE"
addressing type or _X400_ to indicate a X.400 addressing type. Other to specify the format of the electronic mail address. The TYPE
type values are allowed, but are to be specified by individual parameter values may include: "internet" to indicate an Internet
electronic mail service providers. The default email type is addressing type or "x400" to indicate a X.400 addressing type. Any
_INTERNET_. other IANA registered address type may also be specified. The default
email type is "internet". Any 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
1.6.3 MAILER Type Definition 4.4.3 MAILER Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 object. used by the individual associated with the vCard.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
Type value: text.
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 accepted within the MIME private MIME type X-Mailer that is generally implemented by MIME user
user agent product offerings. agent products.
Type example: Type example:
MAILER:GypsyMail 2.1 MAILER:PigeonMail 2.1
1.7 Geographical Profile Types 4.5 Geographical Types
These profile types are concerned with information associated with These types are concerned with information associated with
geographical positions or regions associated with the vCard object. geographical positions or regions associated with the object the
vCard represents.
1.7.1 TZ Type Definition 4.5.1 TZ Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type TZ Subject: Registration of application/directory MIME type TZ
Dawson & Howes [Page 10] Expires June 1997 Dawson & Howes [Page 11] Expires September 1997
vCard Application/Directory Content Type 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
vCard object. object the vCard represents.
Type encoding: text. Type encoding: 8bit.
Type special notes: the type value is specified as a string as Type value: The default is utc-offset. It may also be reset to text.
specified in a manner consistent with [ISO 8601]. It is an offset
from Coordinated Universal Time (UTC). An ISO 8601 UTC offset, in
basic format, is specified as a positive or negative difference in
units of hours and minutes (e.g., +hhmm). If minutes are zero, then
they may be omitted and the format would be specified in units of
hours (e.g., +hh). 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
and minutes are 2-digits with high order zeroes required to maintain
digit count. The extended format for ISO 8601 makes use of a colon
character as a separator of the hour and minute substrings.
Type example: Type examples:
TZ:-0500 TZ:-05:00
1.7.2 GEO Type Definition TZ;VALUE=text:-05:00, EST, Raleigh/North America
To: ietf-mime-direct@umich.edu 4.5.2 GEO Type Definition
To: ietf-mime-directory@umich.edu
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 vCard object. positioning of the object the vCard represents.
Type encoding: text. Type encoding: 8bit.
Type special notes: the type value is a structured string that Type value: Two float values separated by the SEMI-COLON character
specifies a longitude and latitude. The latitude represents the (ASCII decimal 59).
location north and south of the equator as a positive or negative
number, respectively. The longitude represents the location east and Type special notes: The value is the longitude and latitude of the
west of the prime meridian as a positive or negative number, object the vCard represents. The latitude represents the location
respectively. The string components are separated by the SEMI-COLON north and south of the equator as a positive or negative number,
character (ASCII decimal 59). respectively. The longitude represents the location east and west of
the prime meridian as a positive or negative number, respectively.
The text components are separated by the SEMI-COLON character (ASCII
decimal 59).
Type example: Type example:
GEO:37.24;-17.87 GEO:+37.24;-17.87
1.8 Organizational Profile Types 4.6 Organizational Types
These profile types are concerned with information associated with These types are concerned with information associated with
characteristics of the organization or organizational units characteristics of the organization or organizational units of the
associated with the vCard object. object the vCard represents.
Dawson & Howes [Page 11] Expires June 1997 4.6.1 TITLE Type Definition
vCard Application/Directory Content Type To: ietf-mime-directory@umich.edu
1.8.1 TITLE Type Definition Subject: Registration of application/directory MIME type TITLE
To: ietf-mime-direct@umich.edu Dawson & Howes [Page 12] Expires September 1997
Subject: Registration of application/directory MIME type TITLE vCard MIME Directory Profile
Type name: TITLE Type name: TITLE
Type purpose: To specify the job title, functional position or Type purpose: To specify the job title, functional position or
function of the individual or resource associated with the vCard function of the object the vCard represents.
object within an organization
Type encoding: text.
Type special notes: This type is based on the X.520 Title attribute. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
The usual line-folding technique described in [MIME-DIR] can be used Type value: text.
to represent type values consisting of long lines of text.
The type may specify the type parameters CHARSET, to specify a Type special notes: This type is based on the X.520 Title attribute.
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:
TITLE:Director, Research and Development TITLE:Director, Research and Development
1.8.2 ROLE Type Definition 4.6.2 ROLE Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 vCard object within an organization. or business category of the object the vCard represents.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
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 The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR]. for the type value. These are further defined in [MIME-DIR].
Type example: Type example:
ROLE:Programmer ROLE:Programmer
Dawson & Howes [Page 12] Expires June 1997 4.6.3 LOGO Type Definition
vCard Application/Directory Content Type
1.8.3 LOGO Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 the logo of the Dawson & Howes [Page 13] Expires September 1997
organization that is associated with the individual or resource the
vCard belongs to.
Type encoding: text. vCard MIME Directory Profile
Type special notes: The type may include the type parameter _TYPE_ to Type purpose: To specify a graphic image of a logo associated with
specify the format of the graphic image. The TYPE parameter values the object the vCard represents.
may include _GIF_ to indicate the GIF format and _JPEG_ to indicate
the JPEG format. The type may also include the type parameter Type encoding: The default is 8bit. May also be reset to base64 in
_ENCODING_ to specify the content encoding applied to the graphic order to permit inline encoded binary data.
image. The ENCODING parameter value may include _BASE64_ to indicate
the Base64 encoding or _QUOTED-PRINTABLE_ to indicate the quoted- Type value: The default is binary. It may also be reset to url. The
printable encoding. The type may also include the type parameter url value may be used to specify a value outside of this MIME entity.
_VALUE_ to specify the location of the type value. The VALUE
parameter values may include _INLINE_ to indicate that the graphic Type special notes: The type MAY include the type parameter "TYPE" to
image value is included within the content type value, _URL_ to specify the graphic image format type. The TYPE parameter values MUST
indicate the uniform resource locator for where the content for the be one of the IANA registered image formats. In addition, a non-
graphic image can be found in the network, and _CID_ to indicate the standard image format MAY be specified.
content-id for the MIME entity that encapsulates the content for the
graphic image.
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
1.8.4 AGENT Type Definition 4.6.4 AGENT Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 associate with the vCard act on behalf of the individual or resource associated with the
object. vCard.
Type encoding: text. Type encoding: 8-bit.
Type value: The default is vcard. It may also be reset to text or
url. The text value may be used to specify textual information. The
url value may be used to specify 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 object. A key characteristic of the Agent type is that with the vCard. A key characteristic of the Agent type is that it
it represents somebody or something that is separately addressable. represents somebody or something that is separately addressable.
The value for this type is the content message identifier or Uniform
Dawson & Howes [Page 13] Expires June 1997
vCard Application/Directory Content Type
Resource Locator associated with the vCard defining the Agent
individual or resource.
The type may include the type parameter _VALUE_ to specify the
location of the type value. The VALUE parameter values may include
_CID_ to indicate the value specifies the content identifier for the
MIME entity containing the value or _URL_ to indicate the value
specifies the uniform resource locator for the value. The type
parameter may also include _INLINE_; however, this is not a
recommended practice as MIME user agents will not be expected to be
able to process vCard objects nested in this manner. Nested vCard
object will be expected to be mailed within a single message as
multiple MIME entities. The INLINE nesting of vCard object may have
some limited utility in where a monolithic data stream is required.
Type example: Type example:
AGENT;VALUE=CID: AGENT;VALUE=URL:
<JQPUBLIC.part3.960129T083020.xyzMail@host3.com> CID:///<JQPUBLIC.part3.960129T083020.xyzMail@host3.com>
1.8.5 ORG Type Definition 4.6.5 ORG Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
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 object. with the vCard.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
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 and Organization Unit attributes. The type value is a structured text
string consisting of the organization name, followed by any consisting of the organization name, followed by any organizational
organizational units. The string components are separated the SEMI- units. The text components are separated the SEMI-COLON character
COLON character (ASCII decimal 59). (ASCII decimal 59).
The type may specify the type parameters CHARSET, to specify a The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR]. 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
1.9 Explanatory Profile Types 4.7 Explanatory Types
These profile types are concerned with additional explanations, such
as that related to informational notes or revisions specific to the
vCard object.
Dawson & Howes [Page 14] Expires June 1997
vCard Application/Directory Content Type These types are concerned with additional explanations, such as that
related to informational notes or revisions specific to the vCard.
1.9.1 NOTE Type Definition 4.7.1 NOTE Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type NOTE Subject: Registration of application/directory MIME type NOTE
Type name: NOTE Type name: NOTE
Type purpose: To specify supplemental information or a comment that Type purpose: To specify supplemental information or a comment that
is associated with the vCard object. is associated with the vCard.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to 7bit or
quoted-printable.
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 The type may specify the type parameters CHARSET, to specify a
character set for the type value, and LANGUAGE, to specify a language character set for the type value, and LANGUAGE, to specify a language
for the type value. These are further defined in [MIME-DIR]. 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.
1.9.2 REV Type Definition Dawson & Howes [Page 15] Expires September 1997
To: ietf-mime-direct@umich.edu vCard MIME Directory Profile
4.7.2 REV Type Definition
To: ietf-mime-directory@umich.edu
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 vCard Type purpose: To specify revision information about the current
object. vCard.
Type encoding: text. Type encoding: 8-bit.
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 ISO 8601 complete representation. The value in a form conforming to complete representation of ISO 8601 calendar
distinguishes the current revision of the information defining this date and time of day format. The value distinguishes the current
vCard object. revision of the information defining this vCard.
Type example: Type example:
REV:1995-10-31T22:27:10Z REV:1995-10-31T22:27:10Z
1.9.3 SOUND Type Definition 4.7.3 SOUND Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type SOUND Subject: Registration of application/directory MIME type SOUND
Type name: SOUND Type name: SOUND
Dawson & Howes [Page 15] Expires June 1997
vCard Application/Directory Content Type
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 object. By default this type is annotates some aspect of the vCard. By default this type is used to
used to specify the proper pronunciation of the name type value of specify the proper pronunciation of the name type value of the vCard.
the vCard object.
Type encoding: text. Type encoding: The default is 8bit. May also be reset to base64 in
order to permit inline encoded binary data.
Type special notes: The type may include the type parameter _TYPE_ to Type value: The default is binary. It may also be reset to url. The
specify the format of the digital sound. The TYPE parameter values url value may be used to specify a value outside of this MIME entity.
may include _PCM_ to indicate the MIME basic audio content type and
_WAVE_ to indicate the Wave format. The type may also include the Type special notes: The type MAY include the type parameter "TYPE" to
type parameter _ENCODING_ to specify the content encoding applied to specify the audio format type. The TYPE parameter values MUST be one
the digital sound. The ENCODING parameter value may include _BASE64_ of the IANA registered audio formats. In addition, a non-standard
to indicate the Base64 encoding. The type may also include the type audio format MAY be specified.
parameter _VALUE_ to specify the location of the type value. The
VALUE parameter values may include _INLINE_ to indicate that the
digital sound is included within the content type value, _URL_ to
indicate the uniform resource locator for where the content for the
digital sound can be found in the network, and _CID_ to indicate the
content-id for the MIME entity that encapsulates the content for the
digital sound.
Type example: Type example:
SOUND;TYPE=PCM;VALUE=CID:<JOHNQPUBLIC.part8. SOUND;TYPE=BASIC;VALUE=URL:CID://<JOHNQPUBLIC.part8.
19960229T080000.xyzMail@host1.com> 19960229T080000.xyzMail@host1.com>
1.9.4 URL Type Definition 4.7.4 URL Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Dawson & Howes [Page 16] Expires September 1997
vCard MIME Directory Profile
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 an Internet location that can be used to Type purpose: To specify a uniform resource locator associated with
obtain real-time or more complete information about the individual or the object that the vCard refers to.
resource associate with the vCard object.
Type encoding: text. Type encoding: 8bit.
Type special notes: An application of this type might be to specify Type value: url.
the location of a publicly accessible directory, such as an Internet
whitepages, where up-to-date information can be found about the
individual specified by a vCard.
Type example: Type example:
URL:http://www.swbyps.restaurant.french/~chezchic.html URL:http://www.swbyps.restaurant.french/~chezchic.html
1.9.5 UID Type Definition 4.7.5 UID Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type UID Subject: Registration of application/directory MIME type UID
Dawson & Howes [Page 16] Expires June 1997
vCard Application/Directory Content Type
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 object. with the vCard.
Type encoding: text. Type encoding: 8bit.
Type special notes: The type value can be used as a mechanism to Type value: text.
relate different vCard objects. Some examples of valid forms of
unique identifiers would include ISO 9070 formal public identifiers
(FPI) as defined in [ISO 9070], X.500 distinguished names, machine-
generated random numbers with a statistically high likelihood of
being globally unique, and Uniform Resource Locators (URL). If an URL
is specified, it is suggested that the URL reference a service which
will produce an updated version of the vCard associated with the
individual or resource.
The type may include the type parameter _TYPE_ to specify the format Type special notes: The type is used to uniquely identify the object
of the unique identifier. The TYPE parameter values may include that the vCard represents.
_ISO9070_ to indicate the ISO 9070 FPI type of unique identifier,
_X500_ to indicate the X.500 DSN type of unique identifier, _MACH_ to The type may include the type parameter "TYPE" to specify the format
indicate a machine generated random number type of unique identifier, of the identifier. The TYPE parameter value may be any IANA
and _URL_ to indicate a Uniform Resource Locator type of unique registered identifier format. The value may also be a non-standard
identifier. format.
Type example: Type example:
UID;TYPE=MACH:19950401-080045-40000F192713-0052 UID:19950401-080045-40000F192713-0052
1.9.6 Version Type Definition 4.7.6 Version Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type UID Subject: Registration of application/directory MIME type VERSION
Type name: UID Type name: UID
Type purpose: To specify a value that represents a globally unique Type purpose: To specify the version of the vCard specification used
identifier corresponding to the individual or resource associated to format this vCard.
with the vCard object.
Type encoding: text. Dawson & Howes [Page 17] Expires September 1997
Type special notes: The type value can be used as a mechanism to vCard MIME Directory Profile
relate different vCard objects. Some examples of valid forms of
unique identifiers would include ISO 9070 formal public identifiers
(FPI) as defined in [ISO 9070], X.500 distinguished names, machine-
generated random numbers with a statistically high likelihood of
being globally unique, and Uniform Resource Locators (URL). If an URL
is specified, it is suggested that the URL reference a service which
will produce an updated version of the vCard associated with the
individual or resource.
Dawson & Howes [Page 17] Expires June 1997 Type encoding: 8bit.
vCard Application/Directory Content Type Type value: text.
The type may include the type parameter _TYPE_ to specify the format Type special notes: The value must be "2.1" if the vCard version
of the unique identifier. The TYPE parameter values may include corresponds to the [VCARD] specification.
_ISO9070_ to indicate the ISO 9070 FPI type of unique identifier,
_X500_ to indicate the X.500 DSN type of unique identifier, _MACH_ to
indicate a machine generated random number type of unique identifier,
and _URL_ to indicate a Uniform Resource Locator type of unique
identifier.
Type example: Type example:
UID;TYPE=MACH:19950401-080045-40000F192713-0052 VERSION: 2.1
1.10 Security Profile Types 4.8 Security Types
These profile types are concerned with the security of communication These types are concerned with the security of communication pathways
pathways or access to the vCard object. or access to the vCard.
1.10.1 KEY Type Definition 4.8.1 KEY Type Definition
To: ietf-mime-direct@umich.edu To: ietf-mime-directory@umich.edu
Subject: Registration of application/directory MIME type VERSION Subject: Registration of application/directory MIME type VERSION
Type name: VERSION Type name: KEY
Type purpose: To specify an identifier corresponding to the highest Type purpose: To specify an identifier corresponding to the highest
version of the vCard profile used in creating the vCard object. version of the vCard profile used in creating the vCard.
Type encoding: text. To specify a public key or authentication certificate associated with
the object that the vCard represents.
Type special notes: The type value corresponding to this version of Type encoding: The default is 8bit. May also be reset to base64.
the vCard profile MUST be _2.1_.
1.11 Extended Profile Types Type value: The default is text. May also be reset to binary.
The profile types defined by this document can be extended with Type special notes: The type may also include the type parameter TYPE
private types using the private type mechanism defined in [MIME]. to specify the public key or authentication certificate format. The
Private types with a name starting with _X-_ may be defined parameter type may specify any IANA registered public key or
authentication certificate format. The parameter type may also
specify a non-standard format.
4.9 Extended Types
The types defined by this document can be extended with private types
using the non-standard, private values defined in [RFC-2045]. Non-
standard, private types with a name starting with "X-" may be defined
bilaterally between two cooperating agents without outside bilaterally between two cooperating agents without outside
registration or standardization. registration or standardization.
2. Formal Grammar 5. Formal Grammar
The following modified Backus-Naur Notation (BNF) is provided to The following formal grammar is provided to assist developers in
assist developers in building parsers for the vCard. building parsers for the vCard.
Dawson & Howes [Page 18] Expires September 1997
vCard MIME Directory Profile
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:
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.)
Dawson & Howes [Page 18] Expires June 1997
vCard Application/Directory Content Type
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) ws = 1*(SPACE / HTAB)
; _whitespace,_ one or more spaces or tabs ; "whitespace," one or more spaces or tabs
wsls = 1*(SPACE / HTAB / CRLF) wsls = 1*(SPACE / HTAB / CRLF)
; whitespace with line separators ; 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*([wsls] vcard [wsls])
vcard = _BEGIN_ [ws] _:_ [ws] _VCARD_ [ws] 1*CRLF vcard = "BEGIN" [ws] ":" [ws] "VCARD" [ws] 1*CRLF
items *CRLF items *CRLF
_END_ [ws] _:_ [ws] _VCARD_ 1*CRLF "END" ws] [ ":" [ws] "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_ / "GEO" / "NOTE" / "SOURCE" / "NAME" / "PROFILE"
/ _URL_ / _BDAY_ / _ROLE_ / _REV_ / _UID_ / _KEY_ / "URL" / " " BDAY / "ROLE" / "REV" / "UID" / "KEY"
/ _MAILER_ / _X-_ word / "MAILER" / "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>
8bit = <MIME RFC 1521 8-bit text> Dawson & Howes [Page 19] Expires September 1997
quoted-printable = <MIME RFC 1521 quoted-printable text> vCard MIME Directory Profile
base64 = <MIME RFC 1521 base64 text> 8bit = <MIME RFC 2045 8-bit text>
quoted-printable = <MIME RFC 2045 quoted-printable 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
; 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
Dawson & Howes [Page 19] Expires June 1997 params = ";" [ws] paramlist
vCard Application/Directory Content Type
params = _;_ [ws] paramlist
paramlist = paramlist [ws] _;_ [ws] param paramlist = paramlist [ws] ";" [ws] param
/ param / param
param = _TYPE_ [ws] _=_ [ws] ptypeval param = "TYPE" [ws] "=" [ws] ptypeval
/ _VALUE_ [ws] _=_ [ws] pvalueval / "VALUE" [ws] "=" [ws] pvalueval
/ _ENCODING_ [ws] _=_ [ws] pencodingval / "ENCODING" [ws] "=" [ws] pencodingval
/ _CHARSET_ [ws] _=_ [ws] charsetval / "CHARSET" [ws] "=" [ws] charsetval
/ _LANGUAGE_ [ws] _=_ [ws] langval / "LANGUAGE" [ws] "=" [ws] langval
/ _X-_ word [ws] _=_ [ws] word / "X-" word [ws] "=" [ws] word
/ knowntype / knowntype
ptypeval = knowntype / _X-_ word ptypeval = knowntype / "X-" word
pvalueval = _INLINE_ / _URL_ / _CONTENT-ID_ / _CID_ / _X-_ word pvalueval = "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME"
/ "INTEGER" / "BOOLEAN" / "FLOAT" / "BINARY" /
/ "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 string as defined in Section 7.1 of charsetval = <a character set text value as defined in Section 3
RFC 1521> 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 ";">
knowntype = _DOM_ / _INTL_ / _POSTAL_ / _PARCEL_ / _HOME_ / _WORK_ Dawson & Howes [Page 20] Expires September 1997
/ _PREF_ / _VOICE_ / _FAX_ / _MSG_ / _CELL_ / _PAGER_
/ _BBS_ / _MODEM_ / _CAR_ / _ISDN_ / _VIDEO_
/ _INTERNET_ / _GIF_ / _JPEG_ / _PCM_ / _WAVE_
/ _X509_ / _PGP_
2.1 Acknowledgements vCard MIME Directory Profile
The authors would like to thank the participants in the IETF ASID knowntype = "DOM" / " " / "POSTAL" INTL / "PARCEL" / "HOME" / "WORK"
working group, in addition to the following individuals, Roland / "PREF" / " " VOICE / "FAX" / "MSG" / "CELL" / "PAGER"
Alden, Stephen Bartlett, Daniel Klaussen, Michelle Watkins; who / "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO"
provided numerous suggestions and comments on this work. / "INTERNET" / "GIF" / "JPEG" / "PCM" / "WAVE"
/ "X509" / "PGP"
Dawson & Howes [Page 20] Expires June 1997 5.1 Acknowledgements
vCard Application/Directory Content Type The authors would like to thank the participants in the IETF ASID
working group, in addition to the following individuals, Roland
Alden, Stephen Bartlett, Alec Dun, Daniel Klaussen, Chris Newman,
Michelle Watkins; who provided numerous suggestions and comments on
this work.
2.2 Authors's Addresses 5.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
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
EMAIL;TYPE=INTERNET:howes@netscape.com EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard END:vCard
2.3 References 5.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 [ISO 639] ISO 639:1988 - Code for the representation of names of
languages - The International Organization for Standardization, April languages - The International Organization for Standardization, April
1988. 1988.
[ISO 3166] ISO 3166:1993 - Codes for the representation of names of [ISO 3166] ISO 3166:1993 - Codes for the representation of names of
countries - The International Organization for Standardization, countries - The International Organization for Standardization,
December 1993. 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 21] Expires June 1997
vCard Application/Directory Content Type
[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-03.txt, November, Information", Internet-draft-ietf-asid-mime-direct-05.txt, March,
1996. 1997.
[MIME-REG] Freed, N., Postel, J., _Multipurpose Internet Mail [RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text
Extensions (MIME) Part Four: Registration Procedures,_ Internet- Messages", STD 11, RFC 822, August 1982.
Draft draft-ietf-822ext-mime-reg-02.txt, December 1995.
[RFC-822] Crocker, D., _Standard for the Format of ARPA Internet Text [RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Messages_, STD 11, RFC 822, August 1982. Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC
2045, November 1996.
[RFC-1521] Borenstein, N., Freed, N., _MIME (Multipurpose Internet [RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail
Mail Extensions) Part One: Mechanisms for Specifying and Describing Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996.
the Format of Internet Message Bodies_, RFC 1521, September 1993.
[RFC-1522] Moore, K., _MIME (Multipurpose Internet Mail Extensions) [RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) -
Part Two: Message Header Extensions for Non-ASCII Text_, RFC 1522, Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
September 1993. November 1996.
[RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., _Uniform [RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet
Resource Locators (URL)_, RFC 1738, December 1994. Mail Extensions (MIME) - Part Four: Registration Procedures", RFC
2048, January 1997.
[RFC-1766] Alvestrand, H., _Tags for the Identification of [RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform
Languages_, March 1995. Resource Locators (URL)", RFC 1738, December 1994.
[RFC-1872] Levinson, E., _The MIME Multipart/Related Content-type,_ [RFC-1766] Alvestrand, H., "Tags for the Identification of
Languages", March 1995.
[RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type,"
RFC 1872, December 1995. RFC 1872, December 1995.
[VCARD] VERSIT Consortium, _vCard - The Electronic Business Card Dawson & Howes [Page 22] Expires September 1997
Version 2.1_, http://www.versit.com/pdi, September 18, 1996.
Dawson & Howes [Page 22] Expires June 1997 vCard MIME Directory Profile
[VCARD] VERSIT Consortium, "vCard - The Electronic Business Card
Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18,
1996.
Dawson & Howes [Page 23] Expires September 1997
 End of changes. 284 change blocks. 
660 lines changed or deleted 674 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/