utc-offset-value = ("+" / "-") time-hour ":" time-minute
time-hour = 2DIGIT ;00-23
time-minute = 2DIGIT ;00-59
5. Differences From vCard v2.1
This specification has been reviewed by the IETF community. The
review process introduced a number of differences from the [VCARD]
version 2.1. These differences require that vCard objects conforming
to this specification have a different version number than a vCard
conforming to [VCARD]. The differences include the following:
. The QUOTED-PRINTABLE inline encoding has been eliminated.
Only the "B" encoding of [RFC 2047] is an allowed value for
the ENCODING parameter.
. The method for specifying CRLF character sequences in text
type values has been changed. The CRLF character sequence in
a text type value is specified with the backslash character
sequence "\n" or "\N".
Dawson & Howes Standards Track [Page 37]
RFC 2426 vCard MIME Directory Profile September 1998
. Any COMMA or SEMICOLON in a text type value must be backslash
escaped.
. 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.
. The [VCARD] CHARSET type parameter has been eliminated.
Character set can only be specified on the CHARSET parameter
on the Content-Type MIME header field.
. The [VCARD] support for non-significant WSP character has
been eliminated.
. The "TYPE=" prefix to parameter values is required. In
[VCARD] this was optional.
. LOGO, PHOTO and SOUND multimedia formats MUST be either IANA
registered types or non-standard types.
. Inline binary content must be "B" encoded and folded. A blank
line after the encoded binary content is no longer required.
. TEL values can be identified as personal communication
services telephone numbers with the PCS type parameter value.
. The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types
have been added.
. The VERSION, N and FN types MUST be specified in a vCard.
This identifies the version of the specification that the
object was formatted to. It also assures that every vCard
will include both a structured and formatted name that can be
used to identify the object.
Dawson & Howes Standards Track [Page 38]
RFC 2426 vCard MIME Directory Profile September 1998
6. Acknowledgements
The many valuable comments contributed by members of the IETF ASID
working group are gratefully acknowledged, as are the contributions
by Roland Alden, Stephen Bartlett, Alec Dun, Patrik Faltstrom, Daniel
Gurney, Bruce Johnston, Daniel Klaussen, Pete Miller, Keith Moore,
Vinod Seraphin, Michelle Watkins. Chris Newman was especially helpful
in navigating the intricacies of ABNF lore.
7. Authors' Addresses
BEGIN:vCard
VERSION:3.0
FN:Frank Dawson
ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive
;Raleigh;NC;27613-3502;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-919-676-9515
TEL;TYPE=FAX,WORK:+1-919-676-9564
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:vCard
BEGIN:vCard
VERSION:3.0
FN:Tim Howes
ORG:Netscape Communications Corp.
ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View;
CA; 94043;U.S.A.
TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419
TEL;TYPE=FAX,WORK:+1-415-528-4164
EMAIL;TYPE=INTERNET:howes@netscape.com
END:vCard
8. Security Considerations
vCards can carry cryptographic keys or certificates, as described in
Section 3.7.2.
Section 3.7.1 specifies a desired security classification policy for
a particular vCard. That policy is not enforced in any way.
The vCard objects have no inherent authentication or privacy, but can
easily be carried by any security mechanism that transfers MIME
objects with authentication or privacy. In cases where threats of
"spoofed" vCard information is a concern, the vCard SHOULD BE
Dawson & Howes Standards Track [Page 39]
RFC 2426 vCard MIME Directory Profile September 1998
transported using one of these secure mechanisms.
The information in a vCard may become out of date. In cases where the
vitality of data is important to an originator of a vCard, the "URL"
type described in section 3.6.8 SHOULD BE specified. In addition, the
"REV" type described in section 3.6.4 can be specified to indicate
the last time that the vCard data was updated.
9. References
[ISO 8601] ISO 8601:1988 - Data elements and interchange formats -
Information interchange - Representation of dates and
times - The International Organization for
Standardization, June, 1988.
[ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and
interchange formats - Information interchange -
Representation of dates and times - The International
Organization for Standardization, May, 1991.
[ISO 9070] ISO 9070, Information Processing - SGML support
facilities - Registration Procedures for Public Text
Owner Identifiers, April, 1991.
[CCITT E.163] Recommendation E.163 - Numbering Plan for The
International Telephone Service, CCITT Blue Book,
Fascicle II.2, pp. 128-134, November, 1988.
[CCITT X.121] Recommendation X.121 - International Numbering Plan for
Public Data Networks, CCITT Blue Book, Fascicle VIII.3,
pp. 317-332, November, 1988.
[CCITT X.520] Recommendation X.520 - The Directory - Selected
Attribute Types, November 1988.
[CCITT X.521] Recommendation X.521 - The Directory - Selected Object
Classes, November 1988.
[MIME-DIR] Howes, T., Smith, M., and F. Dawson, "A MIME Content-
Type for Directory Information", RFC 2425, September
1998.
[RFC 1738] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", RFC 1738, December
1994.
[RFC 1766] Alvestrand, H., "Tags for the Identification of
Languages", RFC 1766, March 1995.
Dawson & Howes Standards Track [Page 40]
RFC 2426 vCard MIME Directory Profile September 1998
[RFC 1872] Levinson, E., "The MIME Multipart/Related Content-
type", RFC 1872, December 1995.
[RFC 2045] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part One: Format of Internet
Message Bodies", RFC 2045, November 1996.
[RFC 2046] Freed, N., and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) - Part Two: Media Types", RFC
2046, November 1996.
[RFC 2047] Moore, K., "Multipurpose Internet Mail Extensions
(MIME) - Part Three: Message Header Extensions for
Non-ASCII Text", RFC 2047, November 1996.
[RFC 2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose
Internet Mail Extensions (MIME) - Part Four:
Registration Procedures", RFC 2048, January 1997.
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC 2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[UNICODE] "The Unicode Standard - Version 2.0", The Unicode
Consortium, July 1996.
[VCARD] Internet Mail Consortium, "vCard - The Electronic
Business Card Version 2.1",
http://www.imc.org/pdi/vcard-21.txt, September 18,
1996.
Dawson & Howes Standards Track [Page 41]
RFC 2426 vCard MIME Directory Profile September 1998
10. Full Copyright Statement
Copyright (C) The Internet Society (1998). 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 implementation 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
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 Standards Track [Page 42]
gemini://gemini.bortzmeyer.org/rfc-mirror/rfc2426.txt-- Leo's gemini proxy
-- Connecting to gemini.bortzmeyer.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/plain
-- Response ended
-- Page fetched on Mon May 6 12:58:43 2024