idnits 2.17.1 draft-ietf-asid-mime-vcard-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 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. == There are 13 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 24 longer pages, the longest (page 3) being 69 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]), 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 123: '... characteristics MAY be grouped with a...' RFC 2119 keyword, line 144: '...e content entity MUST begin with the B...' RFC 2119 keyword, line 145: '...e content entity MUST end with the END...' RFC 2119 keyword, line 230: '... MUST be used. The extended format m...' RFC 2119 keyword, line 344: '... notes: The type MAY include the type ...' (5 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == 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. -- The document date (July 30, 1997) is 9766 days in the past. Is this intentional? 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 1299 looks like a reference -- Missing reference section? 'VCARD' on line 1330 looks like a reference -- Missing reference section? 'DATETIME' on line 219 looks like a reference -- Missing reference section? 'RFC-2045' on line 1306 looks like a reference -- Missing reference section? 'ISO 8601' on line 1269 looks like a reference -- Missing reference section? 'ISO 9070' on line 1278 looks like a reference -- Missing reference section? 'RFC-822' on line 1303 looks like a reference -- Missing reference section? 'RFC-2046' on line 1310 looks like a reference -- Missing reference section? 'RFC-2047' on line 1313 looks like a reference -- Missing reference section? 'RFC-2048' on line 1317 looks like a reference -- Missing reference section? 'RFC-1738' on line 1321 looks like a reference -- Missing reference section? 'RFC-1766' on line 1324 looks like a reference -- Missing reference section? 'RFC-1872' on line 1327 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 4 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Frank Dawson 3 INTERNET DRAFT Tim Howes 4 ietf-asid-mime-vcard-03.txt Lotus/Netscape Communications 5 July 30, 1997 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 Abstract 29 This memo defines the profile of the MIME Content-Type [MIME-DIR] for 30 directory information for a white-pages person object, based on a 31 vCard electronic business card. The profile definition is independent 32 of any particular directory service or protocol. The profile is 33 defined for representing and exchanging a variety of information 34 about an individual (e.g., formatted and structured name and delivery 35 addresses, email address, multiple telephone numbers, photograph, 36 logo, audio clips, etc.). The directory information used by this 37 profile is based on the attributes for the person object defined in 38 the X.520 and X.521 directory services recommendations. The profile 39 also provides the method for including a [VCARD] representation of a 40 white-pages directory entry within the MIME Content-Type defined by 41 the [MIME-DIR] document. 43 1. Overview 45 The [MIME-DIR] document defines a MIME Content-Type for holding 46 different kinds of directory information. The directory information 47 may be based on any of a number of directory schemas. This document 48 defines a [MIME-DIR] usage profile for conveying directory 49 information based on one such schema; that of the white-pages type of 50 person object. 52 The schema is based on the attributes for the person object defined 53 in the X.520 and X.521 directory services recommendations. The schema 54 has augmented the basic attributes defined in the X.500 series 55 recommendation in order to provide for an electronic representation 56 of the information commonly found on a paper business card. This 58 Dawson & Howes [Page 1] ExpiresJanuary 1998 59 vCard MIME Directory Profile 61 schema was first defined in the [VCARD] document. Hence, this [MIME- 62 DIR] profile is referred to as the vCard MIME Directory Profile. 64 A directory entry based on this usage profile can include traditional 65 directory, white-pages information such as the distinguished name 66 used to uniquely identify the entry, a formatted representation of 67 the name used for user-interface or presentation purposes, both the 68 structured and presentation form of the delivery address, various 69 telephone numbers and organizational information associated with the 70 entry. In addition, traditional paper business card information such 71 as an image of an organizational logo or identify photograph can be 72 included in this person object. 74 The vCard MIME Directory Profile also provides support for 75 representing other important information about the person associated 76 with the directory entry. For instance, the date of birth of the 77 person; an audio clip describing the pronunciation of the name 78 associated with the directory entry, or some other application of the 79 digital sound; longitude and latitude geo-positioning information 80 related to the person associated with the directory entry; date and 81 time that the directory information was last updated; annotations 82 often written on a business card; Uniform Resource Locators (URL) for 83 a website; public key information. The profile also provides support 84 for non-standard extensions to the schema. This provides the 85 flexibility for implementations to augment the current capabilities 86 of the profile in a standardized way. More information about this 87 electronic business card format can be found in [VCARD]. 89 2. The vCard Mime Directory Profile Registration 91 This profile is identified by the following [MIME-DIR] registration 92 template information. Subsequent sections define the profile 93 definition. 95 To: ietf-mime-directory@imc.org 97 Subject: Registration of application/directory MIME profile VCARD 99 Profile name: VCARD 101 Profile purpose: To hold person object or white-pages type of 102 directory information. The person schema captured in the directory 103 entries is that commonly found in an electronic business card. 105 Predefined MIME Directory types used: SOURCE, NAME, PROFILE, BEGIN, 106 END, PROFILE. 108 Predefined MIME Directory parameters used: ENCODING, VALUE, CHARSET, 109 LANGUAGE, CONTEXT. 111 New types: FN, N, PHOTO, BDAY, ADR, LABEL, TEL, EMAIL, MAILER, TZ, 112 GEO, TITLE, ROLE, LOGO, AGENT, ORG, CATEGORY, NOTE, PRODID, REV, 113 SOUND, URL, UID, VERSION, CLASS, KEY 115 Dawson & Howes [Page 2] Expires January 1998 116 vCard MIME Directory Profile 118 New parameters: TYPE 120 Profile special notes: The type-grouping feature of [MIME-DIR] is 121 supported by this profile to group related vCard properties about a 122 directory entry. For example, vCard properties describing WORK or 123 HOME related characteristics MAY be grouped with a unique group 124 label. 126 The profile permits the use of non-standard types (i.e., those 127 identified with the prefix string "X-") as a flexible method for 128 implementations to extend the functionality currently defined within 129 this profile. 131 3. MIME Directory Features 133 The vCard MIME Directory Profile makes use of many of the features 134 defined by [MIME-DIR]. The following sections either clarify or 135 extend the content-type definition of [MIME-DIR]. 137 3.1 Predefined Type Usage 139 The vCard MIME Directory Profile uses the following predefined types 140 from [MIME-DIR]. 142 3.1.1 BEGIN and END Type 144 The content entity MUST begin with the BEGIN type with a value of 145 VCARD. The content entity MUST end with the END type with a value of 146 VCARD. 148 3.1.2 NAME Type 150 If the NAME type appears within a MIME entity conforming to this 151 profile, it's value is the displayable, presentation text associated 152 with the source for the vCard, as specified in the SOURCE type. 154 3.1.3 PROFILE Type 156 If the PROFILE type appears within a MIME entity conforming to this 157 profile, it�s value must be "VCARD". 159 3.1.4 SOURCE Type 161 If the SOURCE type appears within a MIME entity conforming to this 162 profile, it's value provides information how to find the source for 163 the vCard. 165 3.2 Predefined Type Parameter Usage 167 The vCard MIME Directory Profile uses the following predefined types 168 parameters as defined by [MIME-DIR]. 170 Dawson & Howes [Page 3] Expires January 1998 171 vCard MIME Directory Profile 173 � LANGUAGE 175 � ENCODING 177 � VALUE 179 3.3 VALUE Type Parameter Extensions 181 The predefined data type values specified in [MIME-DIR] have been 182 extended by the vCard profile to include a number of value types that 183 are specific to this profile. 185 3.3.1 BINARY 187 The "binary" value type specifies that the type value is inline, 188 encoded binary data. This value type may be specified in the PHOTO, 189 LOGO, SOUND, and KEY types. 191 If inline, encoded binary data is specified, the ENCODING type 192 parameter must be used to specify the encoding format. 194 The value type is defined by the following notation: 196 binchar = 198 binary = *binchar ;A base64 or quoted-printable 199 encoding of the binary information 201 3.3.2 VCARD 203 The "vcard" value type specifies that the type value is another 204 vCard. This value type may be specified in the AGENT type. The value 205 type is defined by this specification. 207 3.3.3 PHONE-NUMBER 209 The "phone-number" value type specifies that the type value is a 210 telephone number. This value type may be specified in the TEL type. 211 The value type is a text value that has the semantics of a telephone 212 number. 214 3.3.4 UTC-OFFSET 216 The "utc-offset" value type specifies that the type value is a signed 217 offset from UTC. This value type may be specified in the TZ type. 219 The format of the offset from UTC is defined by [DATETIME]. The value 220 type is an offset from Coordinated Universal Time (UTC). It is 221 specified as a positive or negative difference in units of hours and 222 minutes (e.g., +hh:mm). The time is specified as a 24-hour clock. 223 Hour values are from 00 to 23, and minute values are from 00 to 59. 224 Hour and minutes are 2-digits with high order zeroes required to 226 Dawson & Howes [Page 4] Expires January 1998 227 vCard MIME Directory Profile 229 maintain digit count. The extended format for ISO 8601 UTC offsets 230 MUST be used. The extended format makes use of a colon character as a 231 separator of the hour and minute text fields. 233 The value is defined by the following notation: 235 time-hour = 2DIGIT ;00-23 236 time-minute = 2DIGIT ;00-59 237 utc-offset = ("+" / "-") time-hour ":" time-minute 239 3.4 Structured Type Values 241 Compound type values are delimited by a field delimiter, specified by 242 the SEMI-COLON character (ASCII decimal 59). A SEMI-COLON in a 243 component of a compound property value must be escaped with a 244 BACKSLASH character (ASCII decimal 92). 246 Lists of values are delimited by a list delimiter, specified by the 247 COMMA character (ASCII decimal 44). A COMMA character in a value must 248 be escaped with a BACKSLASH character (ASCII decimal 92). 250 This profile supports the type grouping mechanism defined in [MIME- 251 DIR]. Grouping of related types is a useful technique to communicate 252 common semantics concerning the properties of a vCard. 254 4. vCard Profile Features 256 The vCard MIME Directory Profile Type contains directory information, 257 typically pertaining to a single directory entry. The information is 258 described using an attribute schema that is tailored for capturing 259 personal contact information. The vCard can include attributes that 260 describe identification, delivery addressing, telecommunications 261 addressing, geographical, organizational, general explanatory and 262 security and access information about the particular object 263 associated with the vCard. 265 4.1 Identification Types 267 These types are used in the vCard profile to capture information 268 associated with the identification and naming of the person or 269 resource associated with the vCard. 271 4.1.1 FN Type Definition 273 To: ietf-mime-directory@imc.org 275 Subject: Registration of application/directory MIME type FN 277 Type name:FN 279 Type purpose: To specify the formatted text corresponding to the name 280 of the object the vCard represents. 282 Dawson & Howes [Page 5] Expires January 1998 283 vCard MIME Directory Profile 285 Type encoding: The default is 8bit. May also be reset to 7bit or 286 quoted-printable. 288 Type value: text. 290 Type special notes: This type is based on the semantics of the X.520 291 Common Name attribute. 293 Type example: 295 FN:Mr. John Q. Public, Esq. 297 4.1.2 N Type Definition 299 To: ietf-mime-directory@imc.org 301 Subject: Registration of application/directory MIME type N 303 Type name: N 305 Type purpose: To specify the structured components of the name of the 306 object the vCard represents. 308 Type encoding: The default is 8bit. May also be reset to 7bit or 309 quoted-printable. 311 Type value: text. 313 Type special note: The type value is structured text corresponding, 314 in sequence, to the Family Name, Given Name, Additional Names, 315 Honorific Prefixes, and Honorific Suffixes. The text components are 316 delimited by the SEMI-COLON character (ASCII decimal 59) and possibly 317 one or more LWSP. This type is based on the semantics of the X.520 318 individual name attributes. 320 Type example: 322 N:Public;John;Quinlan;Mr.;Esq. 324 4.1.3 PHOTO Type Definition 326 To: ietf-mime-directory@imc.org 328 Subject: Registration of application/directory MIME type PHOTO 330 Type name: PHOTO 332 Type purpose: To specify an image or photograph information that 333 annotates some aspect of the object the vCard represents. 335 Type encoding: The default is 8bit. May also be reset to base64 in 336 order to permit inline, encoded binary data. 338 Dawson & Howes [Page 6] Expires January 1998 339 vCard MIME Directory Profile 341 Type value: The default is binary. It may also be reset to url. The 342 url value may be used to specify a value outside of this MIME entity. 344 Type special notes: The type MAY include the type parameter "TYPE" to 345 specify the graphic image format type. The TYPE parameter values MUST 346 be one of the IANA registered image formats or a non-standard image 347 format. 349 Type example: 351 PHOTO;VALUE=url:=http://www.abc.com/pub/photos 352 /jqpublic.gif 354 4.1.4 BDAY Type Definition 356 To: ietf-mime-directory@imc.org 358 Subject: Registration of application/directory MIME type BDAY 360 Type name: BDAY 362 Type purpose: To specify the birthdate of the object the vCard 363 represents. 365 Type encoding: 8bit. 367 Type value: The default is date. It may also be reset to date-time. 369 Type examples: 371 BDAY:1996-04-15 373 BDAY:1953-10-15T23:10:00 375 BDAY:1987-09-27T08:30:00-06:00 377 4.2 Delivery Addressing Types 379 These types are concerned with information related to the delivery 380 addressing or label for the object the vCard represents. 382 4.2.1 ADR Type Definition 384 To: ietf-mime-directory@imc.org 386 Subject: Registration of application/directory MIME type ADR 388 Type name: ADR 390 Type purpose: To specify the structured components of the delivery 391 address for the object the vCard represents. 393 Dawson & Howes [Page 7] Expires January 1998 394 vCard MIME Directory Profile 396 Type encoding: The default is 8bit. It may also be reset to 7bit or 397 quoted-printable. 399 Type value: text. 401 Type special notes: The type value is structured text consisting of a 402 sequence of address components (i.e., post office box, extended 403 address, street address, locality, region, postal code, and country 404 name) separated by the SEMI-COLON character (ASCII decimal 59) and 405 optionally one or more LWSP. 407 The type may include the type parameter "TYPE" to specify the 408 delivery address type. The TYPE parameter values may include "dom" to 409 indicate a domestic delivery address; "intl" to indicate an 410 international delivery address; "postal" to indicate a postal 411 delivery address; "parcel" to indicate a parcel delivery address; 412 "home" to indicate a delivery address for a residence; "work" to 413 indicate delivery address for a place of work; and "pref" to indicate 414 the preferred delivery address when more than one address is 415 specified. These type parameter values may be specified as a 416 parameter list (i.e., "TYPE=dom;TYPE=postal") or as a value list 417 (i.e., "TYPE=dom,postal"). This type is based on semantics of the 418 X.520 geographical and postal addressing attributes. The default is 419 "TYPE=intl,postal,parcel,work". The default can be overridden to some 420 other set of values by specifying one or more alternate values. For 421 example, the default can be reset to "TYPE=dom,postal,work,home" to 422 specify a domestic delivery address for postal delivery to a 423 residence that is also used for work. 425 Type example: 427 ADR;TYPE=dom,home,postal,parcel:;;123 Main 428 Street;Any Town;CA;91921-1234 430 4.2.2 LABEL Type Definition 432 To: ietf-mime-directory@imc.org 434 Subject: Registration of application/directory MIME type LABEL 436 Type name: LABEL 438 Type purpose: To specify the formatted text corresponding to delivery 439 address of the object the vCard represents. 441 Type encoding: The default is 8bit. It may also be reset to 7bit or 442 quoted-printable. 444 Type value: text. 446 Type special notes: The type value is formatted text that may be used 447 to present a delivery address label for the object the vCard 448 represents. 450 Dawson & Howes [Page 8] Expires January 1998 451 vCard MIME Directory Profile 453 The type may include the type parameter "TYPE" to specify delivery 454 label type. The TYPE parameter values may include "dom" to indicate a 455 domestic delivery label; "intl" to indicate an international delivery 456 label; "postal" to indicate a postal delivery label; "parcel" to 457 indicate a parcel delivery label; "home" to indicate a delivery label 458 for a residence; "work" to indicate delivery label for a place of 459 work; and "pref" to indicate the preferred delivery label when more 460 than one label is specified. These type parameter values may 461 specified as a parameter list (i.e., "TYPE=dom;TYPE=postal") or as a 462 value list (i.e., "TYPE=dom,postal"). This type is based on semantics 463 of the X.520 geographical and postal addressing attributes. The 464 default is "TYPE=intl,postal,parcel,work". The default can be 465 overridden to some other set of values by specifying one or more 466 alternate values. For example, the default can be reset to 467 "TYPE=intl,post,parcel,home" to specify an international delivery 468 label for both postal and parcel delivery to a residencial location. 470 Type example: 472 LABEL;ENCODING=quoted-printable;TYPE=dom,home,= 473 postal,parcel:Mr.John Q. Public, Esq.=0D=0A= 474 Mail Drop: TNE QB=0D=0A= 475 123 Main Street=0D=0A= 476 Any Town, CA 91921-1234=0D=0A= 477 U.S.A. 479 4.3 Telecommunications Addressing Types 481 These types are concerned with information associated with the 482 telecommunications addressing of the object the vCard represents. 484 4.3.1 TEL Type Definition 486 To: ietf-mime-directory@imc.org 488 Subject: Registration of application/directory MIME type TEL 490 Type name: TEL 492 Type purpose: To specify the telephone number for telephony 493 communication with the object the vCard represents. 495 Type encoding: 8bit. 497 Type value: phone-number. 499 Type special notes: .The value of this type is specified in a 500 canonical form in order to specify an unambiguous representation of 501 the globally unique telephone endpoint. This type is based on the 502 X.500 Telephone Number attribute. 504 The type may include the type parameter "TYPE" to specify intended 505 use for the telephone number. The TYPE parameter values may include: 507 Dawson & Howes [Page 9] Expires January 1998 508 vCard MIME Directory Profile 510 "home" to indicate a telephone number associated with a residence, 511 "msg" to indicate the telephone number has voice messaging support, 512 "work" to indicate a telephone number associated with a place of 513 work, "pref" to indicate a preferred-use telephone number, "voice" to 514 indicate a voice telephone number, "fax" to indicate a facsimile 515 telephone number, "cell" to indicate a cellular telephone number, 516 "video" to indicate a video conferencing telephone number, "pager" to 517 indicate a paging device telephone number, "bbs" to indicate a 518 bulletin board system telephone number, "modem" to indicate a MODEM 519 connected telephone number, "car" to indicate a car-phone telephone 520 number, "isdn" to indicate an ISDN service telephone number, "pcs" to 521 indicate a personal communication services telephone number. The 522 default type is "voice". These type parameter values may specified as 523 a parameter list (i.e., "TYPE=work;TYPE=voice") or as a value list 524 (i.e., "TYPE=work,voice"). The default may be overridden to another 525 set of values by specifying one or more alternate values. For 526 example, the default TYPE of "voice" can be reset to a WORK and HOME, 527 VOICE and FAX telephone number by the value list 528 "TYPE=work,home,voice,fax". 530 Type example: 532 TEL;TYPE=work,voice,pref,msg:+1-213-555-1234 534 4.3.2 EMAIL Type Definition 536 To: ietf-mime-directory@imc.org 538 Subject: Registration of application/directory MIME type EMAIL 540 Type name: EMAIL 542 Type purpose: To specify the electronic mail address for 543 communication with the object the vCard represents. 545 Type encoding: 8bit. 547 Type value: text. 549 Type special notes: . The type may include the type parameter "TYPE" 550 to specify the format or preference of the electronic mail address. 551 The TYPE parameter values may include: "internet" to indicate an 552 Internet addressing type, "x400" to indicate a X.400 addressing type 553 or."pref" to indicate a preferred-use email address when more than 554 one is specified. Another IANA registered address type may also be 555 specified. The default email type is "internet". A non-standard value 556 may also be specified. 558 Type example: 560 EMAIL;TYPE=internet:jqpublic@xyz.dom1.com 562 Dawson & Howes [Page 10] Expires January 1998 563 vCard MIME Directory Profile 565 EMAIL;TYPE=internet:jdoe@isp.net 566 EMAIL;TYPE=internet,pref:jane_doe@abc.com 568 4.3.3 MAILER Type Definition 570 To: ietf-mime-directory@imc.org 572 Subject: Registration of application/directory MIME type MAILER 574 Type name: MAILER 576 Type purpose: To specify the type of electronic mail software that is 577 used by the individual associated with the vCard. 579 Type encoding: The default is 8bit. May also be reset to 7bit or 580 quoted-printable. 582 Type value: text. 584 Type special notes: This information may provide assistance to a 585 correspondent regarding the type of data representation which can be 586 used, and how they may be packaged. This property is based on the 587 private MIME type X-Mailer that is generally implemented by MIME user 588 agent products. 590 Type example: 592 MAILER:PigeonMail 2.1 594 4.4 Geographical Types 596 These types are concerned with information associated with 597 geographical positions or regions associated with the object the 598 vCard represents. 600 4.4.1 TZ Type Definition 602 To: ietf-mime-directory@imc.org 604 Subject: Registration of application/directory MIME type TZ 606 Type name: TZ 608 Type purpose: To specify information related to the time zone of the 609 object the vCard represents. 611 Type encoding: 8bit. 613 Type value: The default is utc-offset. It may also be reset to text. 615 Type examples: 617 TZ:-05:00 619 Dawson & Howes [Page 11] Expires January 1998 620 vCard MIME Directory Profile 622 TZ;VALUE=text:-05:00; EST; Raleigh/North America 624 4.4.2 GEO Type Definition 626 To: ietf-mime-directory@imc.org 628 Subject: Registration of application/directory MIME type GEO 630 Type name: GEO 632 Type purpose: To specify information related to the global 633 positioning of the object the vCard represents. 635 Type encoding: 8bit. 637 Type value: Two float values separated by the SEMI-COLON character 638 (ASCII decimal 59). 640 Type special notes: This type specifies information related to the 641 global position of the object associated with the vCard. The value 642 specifies latitude and longitude, in that order (i.e., "LAT LON" 643 ordering). The longitude represents the location east and west of the 644 prime meridian as a positive or negative real number, respectively. 645 The latitude represents the location north and south of the equator 646 as a positive or negative real number, respectively. The longitude 647 and latitude values must be specified as decimal degrees and should 648 be specified to six decimal places. This will allow for granularity 649 within a meter of the geographical position. The text components are 650 separated by the SEMI-COLON character (ASCII decimal 59). The simple 651 formula for converting degrees-minutes-seconds into decimal degrees 652 is: 654 decimal = degrees + minutes/60 + seconds/3600. 656 Type example: 658 GEO:37.386013;-122.082932 660 4.5 Organizational Types 662 These types are concerned with information associated with 663 characteristics of the organization or organizational units of the 664 object the vCard represents. 666 4.5.1 TITLE Type Definition 668 To: ietf-mime-directory@imc.org 670 Subject: Registration of application/directory MIME type TITLE 672 Type name: TITLE 674 Dawson & Howes [Page 12] Expires January 1998 675 vCard MIME Directory Profile 677 Type purpose: To specify the job title, functional position or 678 function of the object the vCard represents. 680 Type encoding: The default is 8bit. May also be reset to 7bit or 681 quoted-printable. 683 Type value: text. 685 Type special notes: This type is based on the X.520 Title attribute. 687 Type example: 689 TITLE:Director, Research and Development 691 4.5.2 ROLE Type Definition 693 To: ietf-mime-directory@imc.org 695 Subject: Registration of application/directory MIME type ROLE 697 Type name: ROLE 699 Type purpose: To specify information concerning the role, occupation, 700 or business category of the object the vCard represents. 702 Type encoding: The default is 8bit. May also be reset to 7bit or 703 quoted-printable. 705 Type value: text. 707 Type special notes: This type is based on the X.520 Business Category 708 explanatory attribute. This property is included as an organizational 709 type to avoid confusion with the semantics of the TITLE type and 710 incorrect usage of that type when the semantics of this type is 711 intended. 713 Type example: 715 ROLE:Programmer 717 4.5.3 LOGO Type Definition 719 To: ietf-mime-directory@imc.org 721 Subject: Registration of application/directory MIME type LOGO 723 Type name: LOGO 725 Type purpose: To specify a graphic image of a logo associated with 726 the object the vCard represents. 728 Type encoding: The default is 8bit. May also be reset to base64 in 729 order to permit inline encoded binary data. 731 Dawson & Howes [Page 13] Expires January 1998 732 vCard MIME Directory Profile 734 Type value: The default is binary. It may also be reset to url. The 735 url value may be used to specify a value outside of this MIME entity. 737 Type special notes: The type MAY include the type parameter "TYPE" to 738 specify the graphic image format type. The TYPE parameter values MUST 739 be one of the IANA registered image formats or a non-standard image 740 format. 742 Type example: 744 LOGO;VALUE=URL:http://www.abc.com/pub/logos/abccorp.jpg 746 4.5.4 AGENT Type Definition 748 To: ietf-mime-directory@imc.org 750 Subject: Registration of application/directory MIME type AGENT 752 Type name: AGENT 754 Type purpose: To specify information about another person who will 755 act on behalf of the individual or resource associated with the 756 vCard. 758 Type encoding: 8-bit. 760 Type value: The default is vcard. It may also be reset to text or 761 url. The text value may be used to specify textual information. The 762 url value may be used to specify information outside of this MIME 763 entity. 765 Type special notes: This type typically is used to specify an area 766 administrator, assistant, or secretary for the individual associated 767 with the vCard. A key characteristic of the Agent type is that it 768 represents somebody or something that is separately addressable. 770 Type example: 772 AGENT;VALUE=URL: 773 CID:JQPUBLIC.part3.960129T083020.xyzMail@host3.com 775 4.5.5 ORG Type Definition 777 To: ietf-mime-directory@imc.org 779 Subject: Registration of application/directory MIME type ORG 781 Type name: ORG 783 Type purpose: To specify the organizational name and units associated 784 with the vCard. 786 Dawson & Howes [Page 14] Expires January 1998 787 vCard MIME Directory Profile 789 Type encoding: The default is 8bit. May also be reset to 7bit or 790 quoted-printable. 792 Type value: text. 794 Type special notes: The type is based on the X.520 Organization Name 795 and Organization Unit attributes. The type value is a structured text 796 consisting of the organization name, followed by any organizational 797 units. The text components are separated the SEMI-COLON character 798 (ASCII decimal 59). 800 Type example: 802 ORG:ABC, Inc.;North American Division;Marketing 804 4.6 Explanatory Types 806 These types are concerned with additional explanations, such as that 807 related to informational notes or revisions specific to the vCard. 809 4.6.1 CATEGORIES Type Definition 811 To: ietf-mime-directory@imc.org 813 Subject: Registration of application/directory MIME type CATEGORIES 815 Type name: CATEGORIES 817 Type purpose: To specify application category information about the 818 vCard. 820 Type encoding: The default is 8bit. May also be reset to 7bit or 821 quoted-printable. 823 Type value: text. 825 Type special notes: More than one category may be specified as a list 826 of categories separated by a COMMA (ASCII Decimal 44) character. 828 Type example: 830 CATEGORIES:TRAVEL AGENT 832 CATEGORIES:INTERNET,IETF,INDUSTRY,INFORMATION TECHNOLOGY 834 4.6.2 NOTE Type Definition 836 To: ietf-mime-directory@imc.org 838 Subject: Registration of application/directory MIME type NOTE 840 Type name: NOTE 842 Dawson & Howes [Page 15] Expires January 1998 843 vCard MIME Directory Profile 845 Type purpose: To specify supplemental information or a comment that 846 is associated with the vCard. 848 Type encoding: The default is 8bit. May also be reset to 7bit or 849 quoted-printable. 851 Type value: text. 853 Type special notes: The type is based on the X.520 Description 854 attribute. 856 Type example: 858 NOTE:This fax number is operational 0800 to 1715 859 EST, Mon-Fri. 861 4.6.3 PRODID Type Definition 863 To: ietf-mime-directory@imc.org 865 Subject: Registration of application/directory MIME type PRODID 867 Type name: PRODID 869 Type purpose: To specify the identifier for the product that created 870 the vCard object. 872 Type encoding: 8-bit. 874 Type value: Text. 876 Type example: 878 PRODID:-//ONLINE DIRECTORY//NONSGML Version 1//EN 880 4.6.4 REV Type Definition 882 To: ietf-mime-directory@imc.org 884 Subject: Registration of application/directory MIME type REV 886 Type name: REV 888 Type purpose: To specify revision information about the current 889 vCard. 891 Type encoding: 8-bit. 893 Type value: The default is date-time. May also be reset to date. 895 Type special notes: The type value is a calendar date and time of day 896 in a form conforming to complete representation of ISO 8601 calendar 898 Dawson & Howes [Page 16] Expires January 1998 899 vCard MIME Directory Profile 901 date and time of day format. The value distinguishes the current 902 revision of the information defining this vCard. 904 Type example: 906 REV:1995-10-31T22:27:10Z 908 4.6.5 SOUND Type Definition 910 To: ietf-mime-directory@imc.org 912 Subject: Registration of application/directory MIME type SOUND 914 Type name: SOUND 916 Type purpose: To specify a digital sound content information that 917 annotates some aspect of the vCard. By default this type is used to 918 specify the proper pronunciation of the name type value of the vCard. 920 Type encoding: The default is 8bit. May also be reset to base64 in 921 order to permit inline encoded binary data. 923 Type value: The default is binary. It may also be reset to url. The 924 url value may be used to specify a value outside of this MIME entity. 926 Type special notes: The type MAY include the type parameter "TYPE" to 927 specify the audio format type. The TYPE parameter values MUST be one 928 of the IANA registered audio formats or a non-standard audio format. 930 Type example: 931 SOUND;TYPE=BASIC;VALUE=URL:CID:JOHNQPUBLIC.part8. 932 19960229T080000.xyzMail@host1.com 934 4.6.6 URL Type Definition 936 To: ietf-mime-directory@imc.org 938 Subject: Registration of application/directory MIME type URL 940 Type name: URL 942 Type purpose: To specify a uniform resource locator associated with 943 the object that the vCard refers to. 945 Type encoding: 8bit. 947 Type value: url. 949 Type example: 951 URL:http://www.swbyps.restaurant.french/~chezchic.html 953 Dawson & Howes [Page 17] Expires January 1998 954 vCard MIME Directory Profile 956 4.6.7 UID Type Definition 958 To: ietf-mime-directory@imc.org 960 Subject: Registration of application/directory MIME type UID 962 Type name: UID 964 Type purpose: To specify a value that represents a globally unique 965 identifier corresponding to the individual or resource associated 966 with the vCard. 968 Type encoding: 8bit. 970 Type value: text. 972 Type special notes: The type is used to uniquely identify the object 973 that the vCard represents. 975 The type may include the type parameter "TYPE" to specify the format 976 of the identifier. The TYPE parameter value may be any IANA 977 registered identifier format. The value may also be a non-standard 978 format. 980 Type example: 982 UID:19950401-080045-40000F192713-0052 984 4.6.8 Version Type Definition 986 To: ietf-mime-directory@imc.org 988 Subject: Registration of application/directory MIME type VERSION 990 Type name: VERSION 992 Type purpose: To specify the version of the vCard specification used 993 to format this vCard. 995 Type encoding: 8bit. 997 Type value: text. 999 Type special notes: The value must be "2.2" if the vCard version 1000 corresponds to this specification. 1002 Type example: 1004 VERSION: 2.2 1006 Dawson & Howes [Page 18] Expires January 1998 1007 vCard MIME Directory Profile 1009 4.7 Security Types 1011 These types are concerned with the security of communication pathways 1012 or access to the vCard. 1014 4.7.1 CLASSIFICATION Type Definition 1016 To: ietf-mime-directory@imc.org 1018 Subject: Registration of application/directory MIME type 1019 CLASSIFICATION 1021 Type name: CLASS 1023 Type purpose: To specify the access classification for a vCard 1024 object. 1026 Type encoding: The default is 8bit. May also be reset to 7bit or 1027 quoted-printable. 1029 Type value: text. 1031 Type special notes: An access classification is only one component of 1032 the general security model for a directory service. The 1033 classification attribute provides a method of capturing the intent of 1034 the owner for general access to information described by the vCard 1035 object. 1037 Type examples: 1039 CLASS:PUBLIC 1041 CLASS:PRIVATE 1043 CLASS:CONFIDENTIAL 1045 4.7.2 KEY Type Definition 1047 To: ietf-mime-directory@imc.org 1049 Subject: Registration of application/directory MIME type KEY 1051 Type name: KEY 1053 Type purpose: To specify a public key or authentication certificate 1054 associated with the object that the vCard represents. 1056 Type encoding: The default is 8bit. May also be reset to base64. 1058 Type value: The default is text. May also be reset to binary. 1060 Type special notes: The type may also include the type parameter TYPE 1061 to specify the public key or authentication certificate format. The 1063 Dawson & Howes [Page 19] Expires January 1998 1064 vCard MIME Directory Profile 1066 parameter type may specify any IANA registered public key or 1067 authentication certificate format. The parameter type may also 1068 specify a non-standard format. 1070 4.8 Extended Types 1072 The types defined by this document can be extended with private types 1073 using the non-standard, private values mechanism defined in [RFC- 1074 2045]. Non-standard, private types with a name starting with "X-" may 1075 be defined bilaterally between two cooperating agents without outside 1076 registration or standardization. 1078 5. Differences With vCard v2.1 1080 This specification has been reviewed by the IETF community. The 1081 review process introduced a number of differences with the [VCARD] 1082 version 2.1. These differences are minor, but require that vCard 1083 objects conforming to this specification have a different version 1084 number than a vCard conforming to [VCARD]. The differences include 1085 the following: 1087 � VERSION value corresponding to this specification must be 1088 "2.2". 1090 � The [MIME-DIR] predefined types of PROFILE, SOURCE, NAME are 1091 allowed. 1093 � The [MIME-DIR] VALUE type parameter for value data typing is 1094 allowed. 1096 � The [VCARD] CHARSET type parameter has been eliminated. 1097 Character set may only be specified on the CHARSET parameter 1098 on the Content-Type MIME header field. 1100 � The [VCARD] support for non-signficant LWSP character been 1101 eliminated. All LWSP is significant in this specification. 1103 � LOGO, PHOTO and SOUND multimedia formats need to be either 1104 IANA registered types or non-standard types. 1106 � TEL values may be identified as personal communication 1107 services telephone numbers with the PCS type parameter value. 1109 � The PRODID, CATEGORIES and CLASS types have been added. 1111 6. Formal Grammar 1113 The following formal grammar is provided to assist developers in 1114 building parsers for the vCard. 1116 This syntax is written according to the form described in RFC 822, 1117 but it references just this small subset of RFC 822 literals: 1119 Dawson & Howes [Page 20] Expires January 1998 1120 vCard MIME Directory Profile 1122 CR = ; (15, 13.) 1123 LF = ; (12,10.) 1124 CRLF = CR LF 1125 SPACE = ; (40,32.) 1126 HTAB = ; (11,9.) 1128 All literal property names are valid as upper, lower, or mixed case. 1130 word = 1132 groups = groups "." word 1133 / word 1135 vcard_entity = 1*(vcard) 1137 vcard = "BEGIN" ":" "VCARD" 1*CRLF 1138 items *CRLF 1139 "END" ":" "VCARD" 1*CRLF 1141 items = items *CRLF item 1142 / item 1143 ; these may be "folded" 1145 item = [groups "."] name 1146 [params] ":" value CRLF 1147 / [groups "."] "ADR" 1148 [params] ":" addressparts CRLF 1149 / [groups "."] "ORG" 1150 [params] ":" orgparts CRLF 1151 / [groups "."] "N" 1152 [params] ":" nameparts CRLF 1153 / [groups "."] "AGENT" 1154 [params] ":" vcard CRLF 1155 ; these may be "folded" 1157 name = "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE" 1158 / "SOUND" / "VERSION" / "TEL" / "EMAIL" / "TZ" 1159 / "GEO" / "NOTE" / "SOURCE" / "NAME" / "PROFILE" 1160 / "URL" / "BDAY" / "ROLE" / "REV" / "UID" / "KEY" 1161 / "MAILER" / "CATEGORIES" / "CLASS" / "PRODID" 1162 /"X-" word 1163 ; these may be "folded" 1165 value = 7bit / quoted-printable / base64 1167 7bit = <7bit us-ascii printable chars, excluding CR LF> 1169 8bit = 1171 quoted-printable = 1173 base64 = 1174 ; the end of the text is marked with two CRLF sequences 1176 Dawson & Howes [Page 21] Expires January 1998 1177 vCard MIME Directory Profile 1179 ; this results in one blank line before the start of the next 1180 ; property 1182 params = ";" paramlist 1184 paramlist = paramlist ";" param 1185 / param 1187 param = "TYPE" "=" ptypeval 1188 / "VALUE" "=" pvalueval 1189 / "ENCODING" "=" pencodingval 1190 / "LANGUAGE" "=" langval 1191 / "X-" word "=" word 1192 / knowntype / ianatype 1194 ptypeval = knowntype / "X-" word 1196 pvalueval = "URL" / "TEXT" / "DATE" / "TIME" / "DATE-TIME" 1197 / "INTEGER" / "BOOLEAN" / "FLOAT" / "BINARY" / 1198 / "VCARD" / "PHONE-NUMBER" / "UTC-OFFSET" / "X-" word 1200 pencodingval = "7BIT" / "8BIT" / "QUOTED-PRINTABLE" / "BASE64" 1201 / "X-" word 1203 langval = 1205 addressparts = 0*6(strnosemi ";") strnosemi 1206 ; PO Box, Extended Addr, Street, Locality, Region, Postal Code, 1207 ; Country Name 1209 orgparts = *(strnosemi ";") strnosemi 1210 ; First is Organization Name, remainder are Organization Units. 1212 nameparts = 0*4(strnosemi ";") strnosemi 1213 ; Family, Given, Middle, Prefix, Suffix. 1214 ; Example:Public;John;Q.;Reverend Dr.;III, Esq. 1216 strnosemi = *(*nonsemi ("\;" / "\" CRLF)) *nonsemi 1217 ; To include a semicolon in this string, it must be escaped 1218 ; with a "\" character. 1220 nonsemi = 1222 knowntype = "DOM" / "INTL" / "POSTAL" / "PARCEL" / "HOME" / "WORK" 1223 / "PREF" / "VOICE" / "FAX" / "MSG" / "CELL" / "PAGER" 1224 / "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO" / "PCS" 1225 / "INTERNET" / "X400" / "X509" / "PGP" 1227 ianatype = 1229 Dawson & Howes [Page 22] Expires January 1998 1230 vCard MIME Directory Profile 1232 6.1 Acknowledgements 1234 The authors would like to thank the participants in the IETF ASID 1235 working group, in addition to the following individuals, Roland 1236 Alden, Stephen Bartlett, Alec Dun, Daniel Gurney, Bruce Johnston, 1237 Daniel Klaussen, Chris Newman, Vinod Seraphin, Michelle Watkins; who 1238 provided numerous suggestions and comments on this work. 1240 6.2 Authors�s Addresses 1242 BEGIN:vCard 1243 FN:Frank Dawson 1244 ORG:IBM Corporation;Network Software Division 1245 ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002; 1246 3039 Cornwallis Rd.;Research Triangle Park; 1247 NC;27709;U.S.A. 1248 TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861 1249 TEL;TYPE=FAX,WORK: +1-919-543-6822 1250 EMAIL;TYPE=INTERNET,PREF:fdawson@raleigh.ibm.com 1251 EMAIL;TYPE=INTERNET:fdawson@earthlink.net 1252 URL:http://home.earthlink.net/~fdawson 1253 END:vCard 1255 BEGIN:vCard 1256 FN:Tim Howes 1257 ORG:Netscape Communications Corp. 1258 ADR;TYPE=WORK: 501 E. Middlefield Rd.;Mountain View; 1259 CA; 94043;U.S.A. 1260 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419 1261 TEL;TYPE=FAX,WORK:+1-415-528-4164 1262 EMAIL;TYPE=INTERNET:howes@netscape.com 1263 END:vCard 1265 6.3 References 1267 The following documents are referenced by this work. 1269 [ISO 8601] ISO 8601:1988 - Data elements and interchange formats - 1270 Information interchange - Representation of dates and times - The 1271 International Organization for Standardization, June, 1988. 1273 [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and 1274 interchange formats - Information interchange - Representation of 1275 dates and times - The International Organization for Standardization, 1276 May, 1991. 1278 [ISO 9070] ISO 9070, Information Processing - SGML support facilities 1279 - Registration Procedures for Public Text Owner Identifiers, April, 1280 1991. 1282 [CCITT E.163] Recommendation E.163 - Numbering Plan for The 1283 International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. 1284 128-134, November, 1988. 1286 Dawson & Howes [Page 23] Expires January 1998 1287 vCard MIME Directory Profile 1289 [CCITT X.121] Recommendation X.121 - International Numbering Plan for 1290 Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, 1291 November, 1988. 1293 [CCITT X.520] Recommendation X.520 - The Directory - Selected 1294 Attribute Types, November 1988. 1296 [CCITT X.521] Recommendation X.521 - The Directory - Selected Object 1297 Classes, November 1988. 1299 [MIME-DIR] Howes, T., Smith, M., "A MIME Content-Type for Directory 1300 Information", Internet-draft-ietf-asid-mime-direct-04.txt, July, 1301 1997. 1303 [RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text 1304 Messages", STD 11, RFC 822, August 1982. 1306 [RFC-2045] Freed, N., Borenstein, N., " Multipurpose Internet Mail 1307 Extensions (MIME) - Part One: Format of Internet Message Bodies", RFC 1308 2045, November 1996. 1310 [RFC-2046] Freed, N., Borenstein, N., " Multipurpose Internet Mail 1311 Extensions (MIME) - Part Two: Media Types", RFC 2046, November 1996. 1313 [RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) - 1314 Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, 1315 November 1996. 1317 [RFC-2048] Freed, N., J. Klensin, J. Postel, "Multipurpose Internet 1318 Mail Extensions (MIME) - Part Four: Registration Procedures", RFC 1319 2048, January 1997. 1321 [RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., "Uniform 1322 Resource Locators (URL)", RFC 1738, December 1994. 1324 [RFC-1766] Alvestrand, H., "Tags for the Identification of 1325 Languages", March 1995. 1327 [RFC-1872] Levinson, E., "The MIME Multipart/Related Content-type," 1328 RFC 1872, December 1995. 1330 [VCARD] VERSIT Consortium, "vCard - The Electronic Business Card 1331 Version 2.1", http://www.versit.com/pdi/vcard-21.txt, September 18, 1332 1996. 1334 Dawson & Howes [Page 24] Expires January 1998