idnits 2.17.1 draft-ietf-asid-mime-vcard-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 29 longer pages, the longest (page 2) being 63 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The abstract seems to contain references ([VCARD], [MIME-DIR], [RFC-2119]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 131: '... characteristics MAY be grouped with a...' RFC 2119 keyword, line 152: '...e content entity MUST begin with the B...' RFC 2119 keyword, line 153: '...e content entity MUST end with the END...' RFC 2119 keyword, line 189: '... The predefined data type values specified in [MIME-DIR] MAY NOT be...' RFC 2119 keyword, line 207: '... data MUST be encoded using the "B" ...' (31 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1013 has weird spacing: '...de text that ...' -- The exact meaning of the all-uppercase expression 'MAY NOT' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. == The expression 'MAY NOT', while looking like RFC 2119 requirements text, is not defined in RFC 2119, and should not be used. Consider using 'MUST NOT' instead (if that is what you mean). Found 'MAY NOT' in this paragraph: The predefined data type values specified in [MIME-DIR] MAY NOT be repeated in COMMA separated value lists, unless specified by this specification. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'MIME-DIR' on line 1549 looks like a reference -- Missing reference section? 'VCARD' on line 1583 looks like a reference -- Missing reference section? 'RFC-2119' on line 50 looks like a reference -- Missing reference section? 'RFC 2047' on line 1239 looks like a reference -- Missing reference section? 'RFC-2045' on line 1565 looks like a reference -- Missing reference section? 'WS' on line 1442 looks like a reference -- Missing reference section? 'ISO 8601' on line 1519 looks like a reference -- Missing reference section? 'ISO 9070' on line 1528 looks like a reference -- Missing reference section? 'RFC-822' on line 1553 looks like a reference -- Missing reference section? 'RFC-1738' on line 1556 looks like a reference -- Missing reference section? 'RFC-1766' on line 1559 looks like a reference -- Missing reference section? 'RFC-1872' on line 1562 looks like a reference -- Missing reference section? 'RFC-2046' on line 1569 looks like a reference -- Missing reference section? 'RFC-2047' on line 1572 looks like a reference -- Missing reference section? 'RFC-2048' on line 1576 looks like a reference -- Missing reference section? 'RFC2119' on line 1580 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 6 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Frank Dawson 3 INTERNET DRAFT Lotus Development Corporation 4 ietf-asid-mime-vcard-04.txt Tim Howes 5 Expires six months after November 21, 1997 Netscape Communications 7 vCard MIME Directory Profile 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet- Drafts as reference 19 material or to cite them other than as "work in progress." 21 To learn the current status of any Internet-Draft, please check the 22 "1id-abstracts.txt" listing contained in the Internet- Drafts Shadow 23 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 24 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 25 ftp.isi.edu (US West Coast). 27 Distribution of this memo is unlimited. 29 Copyright (C) The Internet Society 1997. All Rights Reserved. 31 Abstract 33 This memo defines the profile of the MIME Content-Type [MIME-DIR] for 34 directory information for a white-pages person object, based on a 35 vCard electronic business card. The profile definition is independent 36 of any particular directory service or protocol. The profile is 37 defined for representing and exchanging a variety of information 38 about an individual (e.g., formatted and structured name and delivery 39 addresses, email address, multiple telephone numbers, photograph, 40 logo, audio clips, etc.). The directory information used by this 41 profile is based on the attributes for the person object defined in 42 the X.520 and X.521 directory services recommendations. The profile 43 also provides the method for including a [VCARD] representation of a 44 white-pages directory entry within the MIME Content-Type defined by 45 the [MIME-DIR] document. 47 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 48 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this 49 document are to be interopreted as described in [RFC-2119]. 51 1. Overview 53 The [MIME-DIR] document defines a MIME Content-Type for holding 54 different kinds of directory information. The directory information 55 may be based on any of a number of directory schemas. This document 56 defines a [MIME-DIR] usage profile for conveying directory 58 Dawson & Howes [Page 1] May 1998 59 vCard MIME Directory Profile 61 information based on one such schema; that of the white-pages type of 62 person object. 64 The schema is based on the attributes for the person object defined 65 in the X.520 and X.521 directory services recommendations. The schema 66 has augmented the basic attributes defined in the X.500 series 67 recommendation in order to provide for an electronic representation 68 of the information commonly found on a paper business card. This 69 schema was first defined in the [VCARD] document. Hence, this [MIME- 70 DIR] profile is referred to as the vCard MIME Directory Profile. 72 A directory entry based on this usage profile can include traditional 73 directory, white-pages information such as the distinguished name 74 used to uniquely identify the entry, a formatted representation of 75 the name used for user-interface or presentation purposes, both the 76 structured and presentation form of the delivery address, various 77 telephone numbers and organizational information associated with the 78 entry. In addition, traditional paper business card information such 79 as an image of an organizational logo or identify photograph can be 80 included in this person object. 82 The vCard MIME Directory Profile also provides support for 83 representing other important information about the person associated 84 with the directory entry. For instance, the date of birth of the 85 person; an audio clip describing the pronunciation of the name 86 associated with the directory entry, or some other application of the 87 digital sound; longitude and latitude geo-positioning information 88 related to the person associated with the directory entry; date and 89 time that the directory information was last updated; annotations 90 often written on a business card; Uniform Resource Locators (URL) for 91 a website; public key information. The profile also provides support 92 for non-standard extensions to the schema. This provides the 93 flexibility for implementations to augment the current capabilities 94 of the profile in a standardized way. More information about this 95 electronic business card format can be found in [VCARD]. 97 2. The vCard Mime Directory Profile Registration 99 This profile is identified by the following [MIME-DIR] registration 100 template information. Subsequent sections define the profile 101 definition. 103 To: ietf-mime-directory@imc.org 105 Subject: Registration of application/directory MIME profile VCARD 107 Profile name: VCARD 109 Profile purpose: To hold person object or white-pages type of 110 directory information. The person schema captured in the directory 111 entries is that commonly found in an electronic business card. 113 Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN, 114 END, PROFILE. 116 Dawson & Howes [Page 2] May 1998 117 vCard MIME Directory Profile 119 Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET, 120 LANGUAGE, CONTEXT. 122 New types: FN, N, NICKNAME, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, 123 MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORIES, NOTE, 124 PRODID, REV, SORT-STRING, SOUND, URL, UID, VERSION, CLASS, KEY 126 New parameters: TYPE 128 Profile special notes: The type-grouping feature of [MIME-DIR] is 129 supported by this profile to group related vCard properties about a 130 directory entry. For example, vCard properties describing WORK or 131 HOME related characteristics MAY be grouped with a unique group 132 label. 134 The profile permits the use of non-standard types (i.e., those 135 identified with the prefix string "X-") as a flexible method for 136 implementations to extend the functionality currently defined within 137 this profile. 139 3. MIME Directory Features 141 The vCard MIME Directory Profile makes use of many of the features 142 defined by [MIME-DIR]. The following sections either clarify or 143 extend the content-type definition of [MIME-DIR]. 145 3.1 Predefined Type Usage 147 The vCard MIME Directory Profile uses the following predefined types 148 from [MIME-DIR]. 150 3.1.1 BEGIN and END Type 152 The content entity MUST begin with the BEGIN type with a value of 153 "VCARD". The content entity MUST end with the END type with a value 154 of "VCARD". 156 3.1.2 NAME Type 158 If the NAME type appears within a MIME entity conforming to this 159 profile, it's value is the displayable, presentation text associated 160 with the source for the vCard, as specified in the SOURCE type. 162 3.1.3 PROFILE Type 164 If the PROFILE type appears within a MIME entity conforming to this 165 profile, it's value must be "VCARD". 167 3.1.4 SOURCE Type 169 If the SOURCE type appears within a MIME entity conforming to this 170 profile, it's value provides information how to find the source for 171 the vCard. 173 Dawson & Howes [Page 3] May 1998 174 vCard MIME Directory Profile 176 3.2 Predefined Type Parameter Usage 178 The vCard MIME Directory Profile uses the following predefined types 179 parameters as defined by [MIME-DIR]. 181 . LANGUAGE 183 . ENCODING 185 . VALUE 187 3.3 Predefined VALUE Type Usage 189 The predefined data type values specified in [MIME-DIR] MAY NOT be 190 repeated in COMMA separated value lists, unless specified by this 191 specification. 193 3.4 Extensions To The Predefined VALUE Types 195 The predefined data type values specified in [MIME-DIR] have been 196 extended by the vCard profile to include a number of value types that 197 are specific to this profile. 199 3.4.1 BINARY 201 The "binary" value type specifies that the type value is inline, 202 encoded binary data. This value type may be specified in the PHOTO, 203 LOGO, SOUND, and KEY types. 205 If inline encoded binary data is specified, the ENCODING type 206 parameter must be used to specify the encoding format. The binary 207 data MUST be encoded using the "B" encoding format. Long lines of 208 encoded binary data may be folded using the folding method defined in 209 [MIME-DIR]. 211 The value type is defined by the following notation: 213 binary = 215 3.4.2 VCARD 217 The "vcard" value type specifies that the type value is another 218 vCard. This value type may be specified in the AGENT type. The value 219 type is defined by this specification. Since each of the type 220 declarations with in the vcard value type are being specified within 221 a type value themselves, they MUST be terminated with the backslash 222 escapement sequence "\n" or "\N", instead of the character sequence 223 CRLF. For example, with the AGENT type a value would be specified as: 225 AGENT:BEGIN:VCARD\nFN:Joe Friday\nTEL:+1-919-555-7878\n 226 TITLE:Area Administrator\, Assistant\n 227 EMAIL;INTERNET:jfriday@host.com\n 228 END:VCARD 230 Dawson & Howes [Page 4] May 1998 231 vCard MIME Directory Profile 233 3.4.3 PHONE-NUMBER 235 The "phone-number" value type specifies that the type value is a 236 telephone number. This value type may be specified in the TEL type. 237 The value type is a text value that has the special semantics of a 238 telephone number as defined in [CCITT E.163] and [CCITT X.121]. 240 3.4.4 UTC-OFFSET 242 The "utc-offset" value type specifies that the type value is a signed 243 offset from UTC. This value type may be specified in the TZ type. 245 The value type is an offset from Coordinated Universal Time (UTC). It 246 is specified as a positive or negative difference in units of hours 247 and minutes (e.g., +hh:mm). The time is specified as a 24-hour clock. 248 Hour values are from 00 to 23, and minute values are from 00 to 59. 249 Hour and minutes are 2-digits with high order zeroes required to 250 maintain digit count. The extended format for ISO 8601 UTC offsets 251 MUST be used. The extended format makes use of a colon character as a 252 separator of the hour and minute text fields. 254 The value is defined by the following notation: 256 time-hour = 2DIGIT ;00-23 257 time-minute = 2DIGIT ;00-59 258 utc-offset = ("+" / "-") time-hour ":" time-minute 260 3.5 Structured Type Values 262 Compound type values are delimited by a field delimiter, specified by 263 the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a 264 component of a compound property value must be escaped with a 265 BACKSLASH character (ASCII decimal 92). 267 Lists of values are delimited by a list delimiter, specified by the 268 COMMA character (ASCII decimal 44). A COMMA character in a value must 269 be escaped with a BACKSLASH character (ASCII decimal 92). 271 This profile supports the type grouping mechanism defined in [MIME- 272 DIR]. Grouping of related types is a useful technique to communicate 273 common semantics concerning the properties of a vCard. 275 3.6 Line Delimiting and Folding 277 This profile supports the same line delimiting and folding methods 278 defined in [MIME-DIR]. 280 4. vCard Profile Features 282 The vCard MIME Directory Profile Type contains directory information, 283 typically pertaining to a single directory entry. The information is 284 described using an attribute schema that is tailored for capturing 285 personal contact information. The vCard can include attributes that 286 describe identification, delivery addressing, telecommunications 288 Dawson & Howes [Page 5] May 1998 289 vCard MIME Directory Profile 291 addressing, geographical, organizational, general explanatory and 292 security and access information about the particular object 293 associated with the vCard. 295 4.1 Identification Types 297 These types are used in the vCard profile to capture information 298 associated with the identification and naming of the person or 299 resource associated with the vCard. 301 4.1.1 FN Type Definition 303 To: ietf-mime-directory@imc.org 305 Subject: Registration of application/directory MIME type FN 307 Type name:FN 309 Type purpose: To specify the formatted text corresponding to the name 310 of the object the vCard represents. 312 Type encoding: 8bit 314 Type value: A single text value. 316 Type special notes: This type is based on the semantics of the X.520 317 Common Name attribute. 319 Type example: 321 FN:Mr. John Q. Public, Esq. 323 4.1.2 N Type Definition 325 To: ietf-mime-directory@imc.org 327 Subject: Registration of application/directory MIME type N 329 Type name: N 331 Type purpose: To specify the structured components of the name of the 332 object the vCard represents. 334 Type encoding: 8bit 336 Type value: A single structured text value. Each component may have 337 multiple values. 339 Type special note: The structured text value corresponds, in 340 sequence, to the Family Name, Given Name, Additional Names, Honorific 341 Prefixes, and Honorific Suffixes. The text components are separated 342 by the SEMI-COLON character (ASCII decimal 59) and possibly one or 343 more LWSP. Individual text components MAY include multiple text 344 values (e.g., multiple Additional Names), separated by the COMMA 346 Dawson & Howes [Page 6] May 1998 347 vCard MIME Directory Profile 349 character (ASCII decimal 44). This type is based on the semantics of 350 the X.520 individual name attributes. 352 Type example: 354 N:Public;John;Quinlan;Mr.;Esq. 356 N:Stevenson;John;Philip,Paul;Dr.;Jr.,M.D.,A.C.P. 358 4.1.3 NICKNAME Type Definition 360 To: ietf-mime-directory@imc.org 362 Subject: Registration of application/directory MIME type NICKNAME 364 Type name: NICKNAME 366 Type purpose: To specify the text corresponding to the nickname of 367 the object the vCard represents. 369 Type encoding: 8bit 371 Type value: One or more text values separated by a COMMA character 372 (ASCII decimal 44). 374 Type special note: The nickname is the descriptive name given instead 375 of or in addition to the one belonging to a person, place, or thing. 376 It may also be used to specify a familiar form of a proper name 377 specified by the FN or N types. 379 Type example: 381 NICKNAME:Robbie 383 NICKNAME:Jim,Jimmie 385 4.1.4 PHOTO Type Definition 387 To: ietf-mime-directory@imc.org 389 Subject: Registration of application/directory MIME type PHOTO 391 Type name: PHOTO 393 Type purpose: To specify an image or photograph information that 394 annotates some aspect of the object the vCard represents. 396 Type encoding: The encoding MUST be reset to "b" using the ENCODING 397 parameter in order to specify inline, encoded binary data. If the 398 value is referenced by a URI value, then the default encoding of 8bit 399 is used and no explicit ENCODING parameter is needed. 401 Dawson & Howes [Page 7] May 1998 402 vCard MIME Directory Profile 404 Type value: A single value. The default is binary. It may also be 405 reset to uri. The uri value may be used to specify a value outside of 406 this MIME entity. 408 Type special notes: The type MAY include the type parameter "TYPE" to 409 specify the graphic image format type. The TYPE parameter values MUST 410 be one of the IANA registered image formats or a non-standard image 411 format. 413 Type example: 415 PHOTO;VALUE=uri:=http://www.abc.com/pub/photos 416 /jqpublic.gif 418 PHOTO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN 419 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm 420 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 421 <...remainder of "B" encoded binary data...> 423 4.1.5 BDAY Type Definition 425 To: ietf-mime-directory@imc.org 427 Subject: Registration of application/directory MIME type BDAY 429 Type name: BDAY 431 Type purpose: To specify the birthdate of the object the vCard 432 represents. 434 Type encoding: 8bit 436 Type value: The default is a single date value. It may also be reset 437 to a single date-time value. 439 Type examples: 441 BDAY:1996-04-15 443 BDAY:1953-10-15T23:10:00Z 445 BDAY:1987-09-27T08:30:00-06:00 447 4.2 Delivery Addressing Types 449 These types are concerned with information related to the delivery 450 addressing or label for the vCard object. 452 4.2.1 ADR Type Definition 454 To: ietf-mime-directory@imc.org 456 Subject: Registration of application/directory MIME type ADR 458 Dawson & Howes [Page 8] May 1998 459 vCard MIME Directory Profile 461 Type name: ADR 463 Type purpose: To specify the structured components of the delivery 464 address for the vCard object. 466 Type encoding: 8bit 468 Type value: A single structured text value, separated by the SEMI- 469 COLON character (ASCII decimal 59) and optionally one or more LWSP. 471 Type special notes: The structured text value consists of a sequence 472 of address components. The component values MUST be specified in 473 their corresponding position. The structured text value corresponds, 474 in sequence, to the post office box; the extended address; the street 475 address; the locality (e.g., city); the region (e.g., state or 476 province); the postal code; the country name. When a component value 477 is missing, the associated component separator must still be 478 specified. 480 The type may include the type parameter "TYPE" to specify the 481 delivery address type. The TYPE parameter values may include "dom" to 482 indicate a domestic delivery address; "intl" to indicate an 483 international delivery address; "postal" to indicate a postal 484 delivery address; "parcel" to indicate a parcel delivery address; 485 "home" to indicate a delivery address for a residence; "work" to 486 indicate delivery address for a place of work; and "pref" to indicate 487 the preferred delivery address when more than one address is 488 specified. These type parameter values may be specified as a 489 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list 490 (i.e., "TYPE=dom,postal"). This type is based on semantics of the 491 X.520 geographical and postal addressing attributes. The default is 492 "TYPE=intl,postal,parcel,work". The default can be overridden to some 493 other set of values by specifying one or more alternate values. For 494 example, the default can be reset to "TYPE=dom,postal,work,home" to 495 specify a domestic delivery address for postal delivery to a 496 residence that is also used for work. 498 Type example: In this example the post office box and the extended 499 address are absent. 501 ADR;TYPE=dom,home,postal,parcel:;;123 Main 502 Street;Any Town;CA;91921-1234 504 4.2.2 LABEL Type Definition 506 To: ietf-mime-directory@imc.org 508 Subject: Registration of application/directory MIME type LABEL 510 Type name: LABEL 512 Type purpose: To specify the formatted text corresponding to delivery 513 address of the object the vCard represents. 515 Dawson & Howes [Page 9] May 1998 516 vCard MIME Directory Profile 518 Type encoding: 8bit 520 Type value: A single text value. 522 Type special notes: The type value is formatted text that may be used 523 to present a delivery address label for the vCard object. The type 524 may include the type parameter "TYPE" to specify delivery label type. 525 The TYPE parameter values may include "dom" to indicate a domestic 526 delivery label; "intl" to indicate an international delivery label; 527 "postal" to indicate a postal delivery label; "parcel" to indicate a 528 parcel delivery label; "home" to indicate a delivery label for a 529 residence; "work" to indicate delivery label for a place of work; and 530 "pref" to indicate the preferred delivery label when more than one 531 label is specified. These type parameter values may specified as a 532 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list 533 (i.e., "TYPE=dom,postal"). This type is based on semantics of the 534 X.520 geographical and postal addressing attributes. The default is 535 "TYPE=intl,postal,parcel,work". The default can be overridden to some 536 other set of values by specifying one or more alternate values. For 537 example, the default can be reset to "TYPE=intl,post,parcel,home" to 538 specify an international delivery label for both postal and parcel 539 delivery to a residencial location. 541 Type example: A multi-line address label. 543 LABEL;TYPE=dom,home,postal,parcel:Mr.John Q. Public, Esq.\n 544 Mail Drop: TNE QB\n 545 123 Main Street\n 546 Any Town, CA 91921-1234\n 547 U.S.A. 549 4.3 Telecommunications Addressing Types 551 These types are concerned with information associated with the 552 telecommunications addressing of the object the vCard represents. 554 4.3.1 TEL Type Definition 556 To: ietf-mime-directory@imc.org 558 Subject: Registration of application/directory MIME type TEL 560 Type name: TEL 562 Type purpose: To specify the telephone number for telephony 563 communication with the object the vCard represents. 565 Type encoding: 8bit 567 Type value: A single phone-number. 569 Type special notes: The value of this type is specified in a 570 canonical form in order to specify an unambiguous representation of 572 Dawson & Howes [Page 10] May 1998 573 vCard MIME Directory Profile 575 the globally unique telephone endpoint. This type is based on the 576 X.500 Telephone Number attribute. 578 The type may include the type parameter "TYPE" to specify intended 579 use for the telephone number. The TYPE parameter values may include: 580 "home" to indicate a telephone number associated with a residence, 581 "msg" to indicate the telephone number has voice messaging support, 582 "work" to indicate a telephone number associated with a place of 583 work, "pref" to indicate a preferred-use telephone number, "voice" to 584 indicate a voice telephone number, "fax" to indicate a facsimile 585 telephone number, "cell" to indicate a cellular telephone number, 586 "video" to indicate a video conferencing telephone number, "pager" to 587 indicate a paging device telephone number, "bbs" to indicate a 588 bulletin board system telephone number, "modem" to indicate a MODEM 589 connected telephone number, "car" to indicate a car-phone telephone 590 number, "isdn" to indicate an ISDN service telephone number, "pcs" to 591 indicate a personal communication services telephone number. The 592 default type is "voice". These type parameter values may specified as 593 a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list 594 (i.e., "TYPE=work,voice"). The default may be overridden to another 595 set of values by specifying one or more alternate values. For 596 example, the default TYPE of "voice" can be reset to a WORK and HOME, 597 VOICE and FAX telephone number by the value list 598 "TYPE=work,home,voice,fax". 600 Type example: 602 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234 604 4.3.2 EMAIL Type Definition 606 To: ietf-mime-directory@imc.org 608 Subject: Registration of application/directory MIME type EMAIL 610 Type name: EMAIL 612 Type purpose: To specify the electronic mail address for 613 communication with the object the vCard represents. 615 Type encoding: 8bit 617 Type value: A single text value. 619 Type special notes: The type may include the type parameter "TYPE" to 620 specify the format or preference of the electronic mail address. The 621 TYPE parameter values may include: "internet" to indicate an Internet 622 addressing type, "x400" to indicate a X.400 addressing type or "pref" 623 to indicate a preferred-use email address when more than one is 624 specified. Another IANA registered address type may also be 625 specified. The default email type is "internet". A non-standard value 626 may also be specified. 628 Type example: 630 Dawson & Howes [Page 11] May 1998 631 vCard MIME Directory Profile 633 EMAIL;TYPE=internet:jqpublic@xyz.dom1.com 635 EMAIL;TYPE=internet:jdoe@isp.net 637 EMAIL;TYPE=internet,pref:jane_doe@abc.com 639 4.3.3 MAILER Type Definition 641 To: ietf-mime-directory@imc.org 643 Subject: Registration of application/directory MIME type MAILER 645 Type name: MAILER 647 Type purpose: To specify the type of electronic mail software that is 648 used by the individual associated with the vCard. 650 Type encoding: 8bit 652 Type value: A single text value. 654 Type special notes: This information may provide assistance to a 655 correspondent regarding the type of data representation which can be 656 used, and how they may be packaged. This property is based on the 657 private MIME type X-Mailer that is generally implemented by MIME user 658 agent products. 660 Type example: 662 MAILER:PigeonMail 2.1 664 4.4 Geographical Types 666 These types are concerned with information associated with 667 geographical positions or regions associated with the object the 668 vCard represents. 670 4.4.1 TZ Type Definition 672 To: ietf-mime-directory@imc.org 674 Subject: Registration of application/directory MIME type TZ 676 Type name: TZ 678 Type purpose: To specify information related to the time zone of the 679 object the vCard represents. 681 Type encoding: 8bit. 683 Type value: The default is a single utc-offset value. It may also be 684 reset to a single text value. 686 Type special notes: The type value consists of a single value. 688 Dawson & Howes [Page 12] May 1998 689 vCard MIME Directory Profile 691 Type examples: 693 TZ:-05:00 695 TZ;VALUE=text:-05:00; EST; Raleigh/North America 696 ;This example has a single value, not a structure text value. 698 4.4.2 GEO Type Definition 700 To: ietf-mime-directory@imc.org 702 Subject: Registration of application/directory MIME type GEO 704 Type name: GEO 706 Type purpose: To specify information related to the global 707 positioning of the object the vCard represents. 709 Type encoding: 8bit. 711 Type value: Two float values separated by the SEMI-COLON character 712 (ASCII decimal 59). 714 Type special notes: This type specifies information related to the 715 global position of the object associated with the vCard. The value 716 specifies latitude and longitude, in that order (i.e., "LAT LON" 717 ordering). The longitude represents the location east and west of the 718 prime meridian as a positive or negative real number, respectively. 719 The latitude represents the location north and south of the equator 720 as a positive or negative real number, respectively. The longitude 721 and latitude values must be specified as decimal degrees and should 722 be specified to six decimal places. This will allow for granularity 723 within a meter of the geographical position. The text components are 724 separated by the SEMI-COLON character (ASCII decimal 59). The simple 725 formula for converting degrees-minutes-seconds into decimal degrees 726 is: 728 decimal = degrees + minutes/60 + seconds/3600. 730 Type example: 732 GEO:37.386013;-122.082932 734 4.5 Organizational Types 736 These types are concerned with information associated with 737 characteristics of the organization or organizational units of the 738 object the vCard represents. 740 4.5.1 TITLE Type Definition 742 To: ietf-mime-directory@imc.org 744 Subject: Registration of application/directory MIME type TITLE 746 Dawson & Howes [Page 13] May 1998 747 vCard MIME Directory Profile 749 Type name: TITLE 751 Type purpose: To specify the job title, functional position or 752 function of the object the vCard represents. 754 Type encoding: 8bit 756 Type value: A single text value. 758 Type special notes: This type is based on the X.520 Title attribute. 760 Type example: 762 TITLE:Director, Research and Development 764 4.5.2 ROLE Type Definition 766 To: ietf-mime-directory@imc.org 768 Subject: Registration of application/directory MIME type ROLE 770 Type name: ROLE 772 Type purpose: To specify information concerning the role, occupation, 773 or business category of the object the vCard represents. 775 Type encoding: 8bit 777 Type value: A single text value. 779 Type special notes: This type is based on the X.520 Business Category 780 explanatory attribute. This property is included as an organizational 781 type to avoid confusion with the semantics of the TITLE type and 782 incorrect usage of that type when the semantics of this type is 783 intended. 785 Type example: 787 ROLE:Programmer 789 4.5.3 LOGO Type Definition 791 To: ietf-mime-directory@imc.org 793 Subject: Registration of application/directory MIME type LOGO 795 Type name: LOGO 797 Type purpose: To specify a graphic image of a logo associated with 798 the object the vCard represents. 800 Type encoding: The encoding MUST be reset to "b" using the ENCODING 801 parameter in order to specify inline, encoded binary data. If the 803 Dawson & Howes [Page 14] May 1998 804 vCard MIME Directory Profile 806 value is referenced by a URI value, then the default encoding of 8bit 807 is used and no explicit ENCODING parameter is needed. 809 Type value: A single value. The default is binary. It may also be 810 reset to uri. The uri value may be used to specify a value outside of 811 this MIME entity. 813 Type special notes: The type MAY include the type parameter "TYPE" to 814 specify the graphic image format type. The TYPE parameter values MUST 815 be one of the IANA registered image formats or a non-standard image 816 format. 818 Type example: 820 LOGO;VALUE=uri:http://www.abc.com/pub/logos/abccorp.jpg 822 LOGO;ENCODING=b;TYPE=JPEG:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN 823 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm 824 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 825 <...the remainder of "B" encoded binary data...> 827 4.5.4 AGENT Type Definition 829 To: ietf-mime-directory@imc.org 831 Subject: Registration of application/directory MIME type AGENT 833 Type name: AGENT 835 Type purpose: To specify information about another person who will 836 act on behalf of the individual or resource associated with the 837 vCard. 839 Type encoding: 8-bit. 841 Type value: The default is a single vcard value. It may also be reset 842 to either a single text or uri value. The text value may be used to 843 specify textual information. The uri value may be used to specify 844 information outside of this MIME entity. 846 Type special notes: This type typically is used to specify an area 847 administrator, assistant, or secretary for the individual associated 848 with the vCard. A key characteristic of the Agent type is that it 849 represents somebody or something that is separately addressable. 851 Type example: 853 AGENT;VALUE=uri: 854 CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com 856 AGENT:BEGIN:VCARD\n 857 FN:Susan Thomas\n 858 TEL:+1-919-555-1234\n 860 Dawson & Howes [Page 15] May 1998 861 vCard MIME Directory Profile 863 EMAIL;INTERNET:sthomas@host.com\n 864 END:VCARD\n 866 4.5.5 ORG Type Definition 868 To: ietf-mime-directory@imc.org 870 Subject: Registration of application/directory MIME type ORG 872 Type name: ORG 874 Type purpose: To specify the organizational name and units associated 875 with the vCard. 877 Type encoding: 8bit 879 Type value: A single structured text value consisting of components 880 separated the SEMI-COLON character (ASCII decimal 59). 882 Type special notes: The type is based on the X.520 Organization Name 883 and Organization Unit attributes. The type value is a structured text 884 consisting of the organization name, followed by one or more levels 885 of organizational unit names. 887 Type example: A type value consisting of an organizational name, 888 organizational unit #1 name and organizational unit #2 name. 890 ORG:ABC, Inc.;North American Division;Marketing 892 4.6 Explanatory Types 894 These types are concerned with additional explanations, such as that 895 related to informational notes or revisions specific to the vCard. 897 4.6.1 CATEGORIES Type Definition 899 To: ietf-mime-directory@imc.org 901 Subject: Registration of application/directory MIME type CATEGORIES 903 Type name: CATEGORIES 905 Type purpose: To specify application category information about the 906 vCard. 908 Type encoding: 8bit 910 Type value: One or more text values separated by a COMMA character 911 (ASCII decimal 44). 913 Type example: 915 CATEGORIES:TRAVEL AGENT 917 Dawson & Howes [Page 16] May 1998 918 vCard MIME Directory Profile 920 CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY 922 4.6.2 NOTE Type Definition 924 To: ietf-mime-directory@imc.org 926 Subject: Registration of application/directory MIME type NOTE 928 Type name: NOTE 930 Type purpose: To specify supplemental information or a comment that 931 is associated with the vCard. 933 Type encoding: 8bit 935 Type value: A single text value. 937 Type special notes: The type is based on the X.520 Description 938 attribute. 940 Type example: 942 NOTE:This fax number is operational 0800 to 1715 943 EST, Mon-Fri. 945 4.6.3 PRODID Type Definition 947 To: ietf-mime-directory@imc.org 949 Subject: Registration of application/directory MIME type PRODID 951 Type name: PRODID 953 Type purpose: To specify the identifier for the product that created 954 the vCard object. 956 Type encoding: 8-bit. 958 Type value: A single text value. 960 Type special notes: Implementations SHOULD use a method such as that 961 specified for Formal Public Identifiers in ISO 9070 to assure that 962 the text value is unique. 964 Type example: 966 PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN 968 4.6.4 REV Type Definition 970 To: ietf-mime-directory@imc.org 972 Subject: Registration of application/directory MIME type REV 974 Dawson & Howes [Page 17] May 1998 975 vCard MIME Directory Profile 977 Type name: REV 979 Type purpose: To specify revision information about the current 980 vCard. 982 Type encoding: 8-bit. 984 Type value: The default is a single date-time value. May also be 985 reset to a single date value. 987 Type special notes: The value distinguishes the current revision of 988 the information in this vCard for other renditions of the 989 information. 991 Type example: 993 REV:1995-10-31T22:27:10Z 995 REV:1997-11-15 997 4.6.5 SORT-STRING Type Definition 999 To: ietf-mime-directory@imc.org 1001 Subject: Registration of text/directory MIME type SORT-STRING 1003 Type Name: SORT-STRING 1005 Type purpose: To specify the text to be used in national language 1006 specific sorting of the values specified by the FN or N types. 1008 Type encoding: The default is 8bit. May also be reset to 7bit or 1009 quoted-printable. 1011 Type value: text 1013 Type special notes: The sort string is used to provide text that is 1014 to be used in locale- or national language-specific sorting of the 1015 values for the formatted name or structured name types. Without this 1016 information, sorting algorithms may incorrectly sort this vCard 1017 within a sequence of sorted vCards. If this type is present in a 1018 vCard, then this value should be used for sorting the vCard, instead 1019 of the values of the FN or N types. 1021 Type example: The following would define the sort string "Harten" for 1022 the "FN:Rene J. van der Harten" or "N:van der 1023 Harten;Rene;J.;Sir;R.D.O.N.". 1025 SORT-STRING:Harten 1027 4.6.6 SOUND Type Definition 1029 To: ietf-mime-directory@imc.org 1031 Dawson & Howes [Page 18] May 1998 1032 vCard MIME Directory Profile 1034 Subject: Registration of application/directory MIME type SOUND 1036 Type name: SOUND 1038 Type purpose: To specify a digital sound content information that 1039 annotates some aspect of the vCard. By default this type is used to 1040 specify the proper pronunciation of the name type value of the vCard. 1042 Type encoding: The encoding MUST be reset to "b" using the ENCODING 1043 parameter in order to specify inline, encoded binary data. If the 1044 value is referenced by a URI value, then the default encoding of 8bit 1045 is used and no explicit ENCODING parameter is needed. 1047 Type value: A single value. The default is binary. It may also be 1048 reset to uri. The uri value may be used to specify a value outside of 1049 this MIME entity. 1051 Type special notes: The type MAY include the type parameter "TYPE" to 1052 specify the audio format type. The TYPE parameter values MUST be one 1053 of the IANA registered audio formats or a non-standard audio format. 1055 Type example: 1057 SOUND;TYPE=BASIC;VALUE=uri:CID:JOHNQPUBLIC.part8. 1058 19960229T080000.xyzMail@host1.com 1060 SOUND;TYPE=BASIC;ENCODING=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcN 1061 AQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bm 1062 ljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 1063 <...the remainder of "B" encoded binary data...> 1065 4.6.7 UID Type Definition 1067 To: ietf-mime-directory@imc.org 1069 Subject: Registration of application/directory MIME type UID 1071 Type name: UID 1073 Type purpose: To specify a value that represents a globally unique 1074 identifier corresponding to the individual or resource associated 1075 with the vCard. 1077 Type encoding: 8bit. 1079 Type value: A single text value. 1081 Type special notes: The type is used to uniquely identify the object 1082 that the vCard represents. 1084 The type may include the type parameter "TYPE" to specify the format 1085 of the identifier. The TYPE parameter value may be any IANA 1086 registered identifier format. The value may also be a non-standard 1087 format. 1089 Dawson & Howes [Page 19] May 1998 1090 vCard MIME Directory Profile 1092 Type example: 1094 UID:19950401-080045-40000F192713-0052 1096 4.6.8 URL Type Definition 1098 To: ietf-mime-directory@imc.org 1100 Subject: Registration of application/directory MIME type URL 1102 Type name: URL 1104 Type purpose: To specify a uniform resource locator associated with 1105 the object that the vCard refers to. 1107 Type encoding: 8bit 1109 Type value: A single uri value. 1111 Type example: 1113 URL:http://www.swbyps.restaurant.french/~chezchic.html 1115 4.6.9 VERSION Type Definition 1117 To: ietf-mime-directory@imc.org 1119 Subject: Registration of application/directory MIME type VERSION 1121 Type name: VERSION 1123 Type purpose: To specify the version of the vCard specification used 1124 to format this vCard. 1126 Type encoding: 8bit 1128 Type value: A single text value. 1130 Type special notes: The value MUST be "3.0" if the vCard version 1131 corresponds to this specification. 1133 Type example: 1135 VERSION: 3.0 1137 4.7 Security Types 1139 These types are concerned with the security of communication pathways 1140 or access to the vCard. 1142 4.7.1 CLASS Type Definition 1144 To: ietf-mime-directory@imc.org 1146 Dawson & Howes [Page 20] May 1998 1147 vCard MIME Directory Profile 1149 Subject: Registration of application/directory MIME type CLASS 1151 Type name: CLASS 1153 Type purpose: To specify the access classification for a vCard 1154 object. 1156 Type encoding: 8bit 1158 Type value: A single text value. 1160 Type special notes: An access classification is only one component of 1161 the general security model for a directory service. The 1162 classification attribute provides a method of capturing the intent of 1163 the owner for general access to information described by the vCard 1164 object. 1166 Type examples: 1168 CLASS:PUBLIC 1170 CLASS:PRIVATE 1172 CLASS:CONFIDENTIAL 1174 4.7.2 KEY Type Definition 1176 To: ietf-mime-directory@imc.org 1178 Subject: Registration of application/directory MIME type KEY 1180 Type name: KEY 1182 Type purpose: To specify a public key or authentication certificate 1183 associated with the object that the vCard represents. 1185 Type encoding: The encoding MUST be reset to "b" using the ENCODING 1186 parameter in order to specify inline, encoded binary data. If the 1187 value is a text value, then the default encoding of 8bit is used and 1188 no explicit ENCODING parameter is needed. 1190 Type value: A single value. The default is binary. It may also be 1191 reset to text. The text value may be used to specify a text key. 1193 Type special notes: The type may also include the type parameter TYPE 1194 to specify the public key or authentication certificate format. The 1195 parameter type may specify any IANA registered public key or 1196 authentication certificate format. The parameter type may also 1197 specify a non-standard format. 1199 Type example: 1201 KEY;ENCODING=b: MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQA 1202 wdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENbW11bmljYX 1204 Dawson & Howes [Page 21] May 1998 1205 vCard MIME Directory Profile 1207 Rpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0 1208 ZW1zMRwwGgYDVQQDExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNj 1209 E5NDc1OVoXDTk3MTIwMzE5NDc1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYD 1210 VQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW9ucyBDb3JwLjEYMBYGA1UEAx 1211 MPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBFhJob3dlc0BuZXRz 1212 Y2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqGSIb3DQ 1213 EBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2 1214 dXcoX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MB 1215 EGCWCGSAGG+EIBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau 1216 +hUMbsQukjANBgkqhkiG9w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIP 1217 mx93HGp0Kgyx1jIVMyNgsemeAwBM+MSlhMfcpbTrONwNjZYW8vJDSoi//y 1218 rZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8VUMk1U7jt8LYpo4YULU7 1219 UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ== 1221 4.8 Extended Types 1223 The types defined by this document can be extended with private types 1224 using the non-standard, private values mechanism defined in [RFC- 1225 2045]. Non-standard, private types with a name starting with "X-" may 1226 be defined bilaterally between two cooperating agents without outside 1227 registration or standardization. 1229 5. Differences With vCard v2.1 1231 This specification has been reviewed by the IETF community. The 1232 review process introduced a number of differences with the [VCARD] 1233 version 2.1. These differences are minor, but require that vCard 1234 objects conforming to this specification have a different version 1235 number than a vCard conforming to [VCARD]. The differences include 1236 the following: 1238 . The QUOTED-PRINTABLE inline encoding has been eliminated. 1239 Only the "B" encoding of [RFC 2047] is an allowed value for 1240 the ENCODING parameter. 1242 . The method for specifying CRLF character sequences in type 1243 values has been changed. The CRLF character sequence in a 1244 type value is specified with the backslash character sequence 1245 "\n" or "\N". 1247 . Any COMMA or SEMICOLON in a type value must be backslash 1248 escaped. 1250 . VERSION value corresponding to this specification must be 1251 "3.0". 1253 . The [MIME-DIR] predefined types of SOURCE, NAME and PROFILE 1254 are allowed. 1256 . The [MIME-DIR] VALUE type parameter for value data typing is 1257 allowed. In addition, there are extensions made to these type 1258 values for additional value types used in this specification. 1260 Dawson & Howes [Page 22] May 1998 1261 vCard MIME Directory Profile 1263 . The [VCARD] CHARSET type parameter has been eliminated. 1264 Character set may only be specified on the CHARSET parameter 1265 on the Content-Type MIME header field. 1267 . The [VCARD] support for non-signficant LWSP character, other 1268 than after the COMMA character list separator, SEMICOLON 1269 character value component separator and the COLON value 1270 separator has been eliminated. 1272 . LOGO, PHOTO and SOUND multimedia formats need to be either 1273 IANA registered types or non-standard types. 1275 . Inline binary content must be "B" encoded and folded. A blank 1276 line after the encoded binary content is nolonger required. 1278 . TEL values may be identified as personal communication 1279 services telephone numbers with the PCS type parameter value. 1281 . The CATEGORIES, CLASS, NICKNAME, PRODID and SORT-STRING types 1282 have been added. 1284 6. Formal Grammar 1286 The following formal grammar is provided to assist developers in 1287 building parsers for the vCard. 1289 This syntax is written according to the form described in RFC 822, 1290 but it references just this small subset of RFC 822 literals: 1292 CR = ; (15, 13.) 1293 LF = ; (12,10.) 1294 CRLF = CR LF 1295 SPACE = ; (40,32.) 1296 HTAB = ; (11,9.) 1297 WS = (SPACE / HTAB) 1299 All literal property names are valid as upper, lower, or mixed case. 1301 char = 1304 word = 1*char 1306 group = word "." 1308 vcard_entity = 1*(vcard) 1310 vcard = [group] "BEGIN" ":" [WS] "VCARD" 1*CRLF 1311 1*([group] item *CRLF 1312 [group] "END" ":" [WS] "VCARD" 1*CRLF 1313 ;All lines may be "folded". 1315 item = "NAME" *txtparam ":" [WS] text CRLF 1316 / "PROFILE" *txtparam ":" [WS] "VCARD" CRLF 1318 Dawson & Howes [Page 23] May 1998 1319 vCard MIME Directory Profile 1321 / "SOURCE" *srcparam ":" [WS] uri CRLF 1322 / "FN" *txtparam ":" [WS] text CRLF 1323 / "N" *(txtparam) ":" [WS] nameparts CRLF 1324 / "NICKNAME" *(txtparam) ":" [WS] text *("," [WS] text) 1325 CRLF 1326 / "PHOTO" (imginline / imgrefer) 1327 / "BDAY" (dateval / datetimeval) 1328 / "ADR" adrparam ":" [WS] adrparts CRLF 1329 / "LABEL" *(adrparam) ":" [WS] text CRLF 1330 / "TEL" *(telparam) ":" [WS] phone-number CRLF 1331 / "EMAIL" *(emailparam) ":" [WS] text CRLF 1332 / "MAILER" *txtparam ":" [WS] text CRLF 1333 / "TZ" [";" [WS] "VALUE" "=" "utc-offset"] ":" 1334 [WS] utc-offset 1335 / "GEO" [";" [WS] "VALUE" "=" "float"] ":" 1336 float ";" float 1337 / "TITLE" *txtparam ":" [WS] text CRLF 1338 / "ROLE" *txtparam ":" [WS] text CRLF 1339 / "LOGO" (imginline / imgrefer) 1340 / "AGENT" ":" text CRLF 1341 ;The text value MUST be a string of vCard types, each 1342 ;type terminated with a "\n" or "\N" escapement. 1343 / "ORG" *txtparam ":" [WS] orgparts CRLF 1344 / "CATEGORIES" *txtparam ":" [WS] text *("," [WS] text) 1345 CRLF 1346 / "NOTE" *txtparam ":" [WS] text CRLF 1347 / "PRODID *txtparam ":" [WS] text CRLF 1348 / "REV" (dateval / datetimeval) 1349 / "SOUND" (sndinline / sndrefer) 1350 / "URL" [";" [WS] "VALUE" "=" "uri"] ":" [WS] uri CRLF 1351 / "UID" [";" [WS] "VALUE" "=" "text"] ":" [WS] text CRLF 1352 / "VERSION" ":" "3.0" 1353 / "CLASS" *txtparam ":" [WS] text CRLF 1354 / "KEY" (keytext) / (keybinary) 1355 / "X-" word *txtparam ":" [WS] value 1357 txtparam = (";" [WS] "VALUE" "=" "text") 1358 / (";" [WS] "LANGUAGE" "=" langval) 1359 / (";" [WS] "X-" word "=" word) 1361 langval = 1363 srcparam = (";" [WS] "VALUE" "=" "uri") 1364 / (";" [WS] "CONTEXT" "=" word) 1365 ;Parameter values specifies the protocol 1366 ; context for the URI value. 1367 / (";" [WS] "X-" word "=" word) 1369 adrparam = ";" [WS] ["TYPE" "="] adrtype *("," [WS] adrtype) 1370 *(txtparam) 1372 adrtype = "dom" / "intl" / "postal" / "parcel" / "home" 1373 / "work" / "pref" / ianatype / "X-" word 1375 Dawson & Howes [Page 24] May 1998 1376 vCard MIME Directory Profile 1378 adrparts = 0*6(text ";") text 1379 ; PO Box, Extended Address, Street, Locality, Region, Postal 1380 ; Code, Country Name 1382 orgparts = *(text ";") text 1383 ; First is Organization Name, remainder are Organization Units. 1385 nameparts = 0*4(text *("," text) ";") text *("," text) 1386 ; Family, Given, Middle, Prefix, Suffix. 1387 ; Example:Public;John;Q.;Reverend Dr.;III, Esq. 1389 telparam = ";" [WS] ["TYPE" "="] teltype *("," [WS] teltype) 1391 teltype = "HOME" / "WORK" / "PREF" / "VOICE" / "FAX" / "MSG" 1392 / "CELL" / "PAGER" / "BBS" / "MODEM" / "CAR" / "ISDN" 1393 / "VIDEO" / "PCS" / ianatype / "X-" word 1395 emailparam = ";" [WS] ["TYPE" "="] emailtype ["," [WS] "PREF"] 1397 emailtype = "INTERNET" / "X400" / ianatype / "X-" word 1399 imginline = imginlparm ":" [WS] binary CRLF 1400 ;Value MUST be "b" encoded image content 1402 imginlparm = [";" [WS] "VALUE" "=" "binary"] 1403 ";" [WS] "ENCODING" "=" "b" 1404 ";" [WS] "TYPE" "=" word 1405 ;Value MUST be an IANA registered image type 1407 imgrefer = imgrefparm ":" [WS] uri 1408 ;URI MUST refer to image content of given type 1410 imgrefparm = ";" [WS] "VALUE" "=" "uri" 1411 ";" [WS] "TYPE" "=" word 1412 ;Value MUST be an IANA registered image type 1414 sndinline = sndinlparm ":" [WS] binary CRLF 1415 ;Value MUST be "b" encoded audio content 1417 sndinlparm = [";" [WS] "VALUE" "=" "binary"] 1418 ";" [WS] "ENCODING" "=" "b" 1419 ";" [WS] "TYPE" "=" word 1420 ;Value MUST be an IANA registered audio type 1422 sndrefer = sndrefparm ":" [WS] uri 1423 ;URI MUST refer to audio content of given type 1425 sndrefparm = ";" [WS] "VALUE" "=" "uri" 1426 ";" [WS] "TYPE" "=" word 1427 ;Value MUST be an IANA registered audio type 1429 dateval = [";" [WS] "VALUE" "=" "date"] ":" [WS] date 1431 datetimeval = ";" [WS] "VALUE" "=" "date-time" ";" [ws] date-time 1433 Dawson & Howes [Page 25] May 1998 1434 vCard MIME Directory Profile 1436 / "KEY" (keytext) / (keybinary) 1438 keytext = [";" [WS] "TYPE" "=" keytype] [";" [WS] "TYPE" "=" 1439 "text"] ":" text 1441 keybinary = [";" [WS] "TYPE" "=" keytype] (";" [WS] "TYPE" "=" 1442 "binary") (";" [WS] "ENCODING" "=" "b") ":" [WS] 1443 binary 1444 ;Value MUST be a "b" encoded key or certificate 1446 keytype = "X509" / "PGP" / ianatype / "X-" word 1448 value = binary / boolean / date / date-time / float / integer 1449 / phone-number / text / time / utc-offset / vcard / 1450 / ianavalue 1452 text = *(word WS) 1453 ; To include a SEMICOLON in this string it must be escaped 1454 ; with a "\" character. To include a COMMA in this string it 1455 ; MUST be escaped with a "\" characer. 1457 binary = 1459 date = 1461 time = 1463 date-time = 1467 phone-number = 1470 uri = 1472 utc-offset = ("+" / "-") time-hour ":" time-minute 1473 time-hour = 2DIGIT ;00-23 1474 time-minute = 2DIGIT ;00-59 1476 ianatype = 1478 ianavalue = 1480 6.1 Acknowledgements 1482 The authors would like to thank the participants in the IETF ASID 1483 working group, in addition to the following individuals, Roland 1484 Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce Johnston, 1485 Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who 1486 provided numerous suggestions and comments on this work. 1488 Dawson & Howes [Page 26] May 1998 1489 vCard MIME Directory Profile 1491 6.2 Authors's Addresses 1493 BEGIN:vCard 1494 FN:Frank Dawson 1495 ORG:Lotus Development Corporation 1496 ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive 1497 ;Raleigh;NC;27613-3502;U.S.A. 1498 TEL;TYPE=VOICE,MSG,WORK: +1-919-676-9515 1499 TEL;TYPE=FAX,WORK: +1-919-676-9564 1500 EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com 1501 EMAIL;TYPE=INTERNET:fdawson@earthlink.net 1502 URL:http://home.earthlink.net/~fdawson 1503 END:vCard 1505 BEGIN:vCard 1506 FN:Tim Howes 1507 ORG:Netscape Communications Corp. 1508 ADR;TYPE=WORK:;;501 E. Middlefield Rd.;Mountain View; 1509 CA; 94043;U.S.A. 1510 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419 1511 TEL;TYPE=FAX,WORK:+1-415-528-4164 1512 EMAIL;TYPE=INTERNET:howes@netscape.com 1513 END:vCard 1515 6.3 References 1517 The following documents are referenced by this work. 1519 [ISO 8601] ISO 8601:1988 - Data elements and interchange formats - 1520 Information interchange - Representation of dates and times - The 1521 International Organization for Standardization, June, 1988. 1523 [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and 1524 interchange formats - Information interchange - Representation of 1525 dates and times - The International Organization for Standardization, 1526 May, 1991. 1528 [ISO 9070] ISO 9070, Information Processing - SGML support facilities 1529 - Registration Procedures for Public Text Owner Identifiers, April, 1530 1991. 1532 [CCITT E.163] Recommendation E.163 - Numbering Plan for The 1533 International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. 1534 128-134, November, 1988. 1536 [CCITT X.121] Recommendation X.121 - International Numbering Plan for 1537 Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, 1538 November, 1988. 1540 [CCITT X.520] Recommendation X.520 - The Directory - Selected 1541 Attribute Types, November 1988. 1543 [CCITT X.521] Recommendation X.521 - The Directory - Selected Object 1544 Classes, November 1988. 1546 Dawson & Howes [Page 27] May 1998 1547 vCard MIME Directory Profile 1549 [MIME-DIR] Howes, T., Smith, M., "A MIME Content-Type for Directory 1550 Information", Internet-draft-ietf-asid-mime-direct-05.txt, November, 1551 1997. 1553 [RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text 1554 Messages", STD 11, RFC 822, August 1982. 1556 [RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform 1557 Resource Locators (URL)", RFC 1738, December 1994. 1559 [RFC-1766] Alvestrand, H., "Tags for the Identification of 1560 Languages", March 1995. 1562 [RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type," 1563 RFC 1872, December 1995. 1565 [RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail 1566 Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC 1567 2045, November 1996. 1569 [RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail 1570 Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996. 1572 [RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) - 1573 Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, 1574 November 1996. 1576 [RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet 1577 Mail Extensions (MIME) - Part Four: Registration Procedures", RFC 1578 2048, January 1997. 1580 [RFC2119] "Key words for use in RFCs to Indicate Requirement Levels", 1581 RFC 2119, March 1997. 1583 [VCARD] VERSIT Consortium, "vCard - The Electronic Business Card 1584 Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18, 1585 1996. 1587 7. Full Copyright Statement 1589 "Copyright (C) The Internet Society (date). All Rights Reserved. 1591 This document and translations of it MAY be copied and furnished to 1592 others, and derivative works that comment on or otherwise explain it 1593 or assist in its implmentation MAY be prepared, copied, published and 1594 distributed, in whole or in part, without restriction of any kind, 1595 provided that the above copyright notice and this paragraph are 1596 included on all such copies and derivative works. However, this 1597 document itself MAY not be modified in any way, such as by removing 1598 the copyright notice or references to the Internet Society or other 1599 Internet organizations, except as needed for the purpose of 1600 developing Internet standards in which case the procedures for 1601 copyrights defined in the Internet Standards process MUST be 1603 Dawson & Howes [Page 28] May 1998 1604 vCard MIME Directory Profile 1606 followed, or as required to translate it into languages other than 1607 English. 1609 The limited permissions granted above are perpetual and will not be 1610 revoked by the Internet Society or its successors or assigns. 1612 This document and the information contained herein is provided on an 1613 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1614 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1615 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1616 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1617 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1618 __ 1620 Dawson & Howes [Page 29] May 1998