idnits 2.17.1 draft-ietf-asid-mime-vcard-00.txt: ** The Abstract section seems to be numbered 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-19) 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. ** 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 21 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 22 pages 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. ** There are 220 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 9 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 11 has weird spacing: '...fts are worki...' == Line 12 has weird spacing: '...ments of the ...' == Line 13 has weird spacing: '...t other group...' == Line 17 has weird spacing: '...and may be ...' == Line 21 has weird spacing: '...atus of any ...' == (215 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- 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 1034 looks like a reference -- Missing reference section? 'VERSIT-VCARD' on line 1072 looks like a reference -- Missing reference section? 'MIME- DIR' on line 691 looks like a reference -- Missing reference section? 'ISO 8601' on line 998 looks like a reference -- Missing reference section? 'ISO 9070' on line 1012 looks like a reference -- Missing reference section? 'MIME' on line 840 looks like a reference -- Missing reference section? 'ISO 639' on line 989 looks like a reference -- Missing reference section? 'ISO 3166' on line 993 looks like a reference -- Missing reference section? 'MIME-REG' on line 1038 looks like a reference -- Missing reference section? 'RFC-822' on line 1043 looks like a reference -- Missing reference section? 'RFC-1521' on line 1047 looks like a reference -- Missing reference section? 'RFC-1522' on line 1052 looks like a reference -- Missing reference section? 'RFC-1738' on line 1057 looks like a reference -- Missing reference section? 'RFC-1766' on line 1064 looks like a reference -- Missing reference section? 'RFC-1872' on line 1068 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 9 warnings (==), 17 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Frank Dawson 2 INTERNET DRAFT IBM 3 draft-ietf-asid-mime-vcard-00.txt Tim Howes 4 Netscape 6 An Application/Directory MIME Content-Type 7 Electronic Business Card Profile 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working docu- 12 ments of the Internet Engineering Task Force (IETF), its areas, and its 13 working groups. Note that other groups may also distribute working 14 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 material 19 or to cite them other than as "work in progress." 21 To learn the current status of any Internet-Draft, please check the 22 ``id-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 2. Abstract 29 This memo defines a directory information profile for a white pages per- 30 son, to be carried in an application/directory MIME Content-Type. The 31 profile consists of type definitions (e.g., for name and email address) 32 and the corresponding format of values that each type is allowed to con- 33 tain. 35 3. Overview 37 The application/directory MIME Content-Type defined in [MIME-DIR] is 38 used for representing directory information in MIME format. It defines 39 a general framework for carrying "type: value" style information in the 40 body of a MIME message, but does not define specific types or values. 41 This document defines a profile containing the types and corresponding 42 value formats for representing information about an electronic business 43 card. The profile reflects the Versit Electronic Business Card (vCard) 44 schema defined in [VERSIT-VCARD]. 46 Expires November 1996 INTERNET DRAFT 48 3.1. The vCard Profile 50 The profile is defined as follows, using the profile registration tem- 51 plate from Section 8 of [MIME-DIR]. 53 3.2. vCard Profile Definition 55 To: ietf-mime-direct@umich.edu 56 Subject: Registration of application/directory MIME profile vcard 58 Profile name: vcard 60 Profile purpose: To hold vcard information about an electronic busi- 61 ness card. 63 Profile types: BEGIN, END, FN, N, PHOTO, BDAY, ADR, FADR, TEL, EMAIL, 64 MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV, SOUND, 65 URL, UID, KEY 67 Profile special notes: The content entity must begin with the type 68 BEGIN and end with the type END. There is no other ordering limita- 69 tions on types within the content entity. 71 The default transfer encoding for the vCard profile is 7-Bit. Multi- 72 ple line type values are not allowed for 7-Bit encoding. The default 73 transfer encoding can be overridden for an individual type value by 74 using the "ENCODING" type parameter. The parameter value can be 75 reset to either "BASE64" or "QUOTED-PRINTABLE". This type parameter 76 may be used on any profile type. 78 The default character set is ASCII. The default character set can be 79 overridden for an individual type value by using the "CHARSET" type 80 parameter. This type parameter may be used on any profile type. 81 However, the use of this parameter on some profile types may not make 82 sense. 84 The default language is "en-US" (US English). The default language 85 can be overridden for an individual type value by using the 86 "LANGUAGE" type parameter. This type parameter may be used on any 87 profile type. However, the use of this parameter on some profile 88 types may not make sense. 90 The default location of the type values is inline with the profile 91 type. However, for some profile types, such as those that specify 92 multimedia values, it is efficient to organize the type value as a 93 separate MIME entity. The type parameter "VALUE" can be specified to 94 override the "INLINE" location of the type value. The type value can 95 be specified as being located in a separate MIME entity with the 97 Expires November 1996 INTERNET DRAFT 99 "CID" value. In this case, the type value is the Content- ID for the 100 MIME entity containing the type value. In addition, the type value 101 can be specified as being located out on the network within some 102 Internet resource with the "URL" value. In this case, the type value 103 is the Uniform Resource Locator for the Internet resource containing 104 the type value. This type parameter may be used on any profile type. 105 However, the use of this parameter on some profile types may not make 106 sense. 108 This profile supports the type grouping mechanism defined in [MIME- 109 DIR]. Grouping of related profile types is a useful technique to 110 communicate common semantics concerning the properties of a vCard 111 object. 113 Intended usage: COMMON 115 The associated type definitions follow, using the type registration tem- 116 plate from Section 9 of [MIME-DIR]. 118 3.3. Delimiter Profile Types 120 The following profile types are used to delimit the vCard data within 121 the content type. These types are useful to completely define the con- 122 tent type so that it might be identified as a vCard object when the con- 123 tent type is in a persistent form outside of a MIME message. 125 3.3.1. BEGIN Type Definition 127 To: ietf-mime-direct@umich.edu 128 Subject: Registration of application/directory MIME type BEGIN 130 Type name: BEGIN 132 Type purpose: To delimit the beginning of the vCard content data. 134 Type encoding: text. 136 Type special notes: The only valid value is "vCard". 138 Type example: BEGIN: vCard 140 3.3.2. END Type Definition 142 To: ietf-mime-direct@umich.edu 143 Subject: Registration of application/directory MIME type END 145 Type name: END 147 Expires November 1996 INTERNET DRAFT 149 Type purpose: To delimit the end of the vCard content data. 151 Type encoding: text. 153 Type special notes: The type either has no value or has the value 154 "vCard". 156 Type example: 157 END: vCard 159 3.4. Identification Profile Types 161 These profile types are concerned with information associated with the 162 identification and naming of the individual or resource associated with 163 the vCard object. 165 3.4.1. FN Type Definition 167 To: ietf-mime-direct@umich.edu 168 Subject: Registration of application/directory MIME type FN 170 Type name:FN 172 Type purpose: To specify the formatted name string associated with 173 the vCard object. 175 Type encoding: text. 177 Type special notes: The value is intended to be used as a formatted 178 string corresponding to how the name of the individual or resource 179 associated with the vCard is to be displayed. This type is based on 180 the semantics of the X.520 Common Name attribute. The type may 181 specify the type parameters CHARSET, to specify a character set for 182 the type value, and LANGUAGE, to specify a language for the type 183 value. These are further defined in [MIME- DIR]. 185 Type example: 186 FN: Mr. John Q. Public, Esq. 188 3.4.2. N Type Definition 190 To: ietf-mime-direct@umich.edu 191 Subject: Registration of application/directory MIME type N 193 Type name: N 195 Type purpose: To specify the structured name strings associated with 196 the vCard object. 198 Expires November 1996 INTERNET DRAFT 200 Type encoding: text. 202 Type special note: The type value is a structured string correspond- 203 ing, in sequence, to the Family Name, Given Name, Additional Names, 204 Honorific Prefixes, and Suffixes corresponding to the individual or 205 resource associated with the vCard. The component strings are delim- 206 ited by SEMI-COLON characters and possibly one or more LWSP. This 207 type is based on the semantics of the X.520 individual name attri- 208 butes. The type may specify the type parameters CHARSET, to specify 209 a character set for the type value, and LANGUAGE, to specify a 210 language for the type value. These are further defined in [MIME- 211 DIR]. 213 Type example: 214 N: Public;John;Quinlan;Mr.;Esq. 216 3.4.3. PHOTO Type Definition 218 To: ietf-mime-direct@umich.edu 219 Subject: Registration of application/directory MIME type PHOTO 221 Type name: PHOTO 223 Type purpose: To specify an image or photograph information that 224 annotates some aspect of the vCard object. By default this type is 225 used to specify a photograph or image of the individual or resource 226 associated with the vCard. 228 Type encoding: text. 230 Type special notes: The type may include the type parameter "TYPE" to 231 specify the format of the graphic image. The TYPE parameter values 232 may include "GIF" to indicate the GIF format and "JPEG" to indicate 233 the JPEG format. The type may also include the type parameter 234 "ENCODING" to specify the content encoding applied to the graphic 235 image. The ENCODING parameter value may include "BASE64" to indicate 236 the Base64 encoding or "QUOTED-PRINTABLE" to indicate the quoted 237 printable encoding. The type may also include the type parameter 238 "VALUE" to specify the location of the type value. The VALUE parame- 239 ter values may include "INLINE" to indicate that the graphic image 240 value is included within the content type value, "URL" to indicate 241 the uniform resource locator for where the content for the graphic 242 image can be found in the network, and "CID" to indicate the 243 content-id for the MIME entity that encapsulates the content for the 244 graphic image. 246 Type example: 247 PHOTO;TYPE=GIF;ENCODE=QUOTED-PRINTABLE;VALUE=URL: = 249 Expires November 1996 INTERNET DRAFT 251 http://www.abc.com/pub/photos/jqpublic.gif 253 3.4.4. BDAY Type Definition 255 To: ietf-mime-direct@umich.edu Subject: Registration of 256 application/directory MIME type BDAY 258 Type name: BDAY 260 Type purpose: To specify the birthdate of the individual associated 261 with the vCard. 263 Type encoding: text. 265 Type special notes: The text value is a string conforming to the ISO 266 8601 calendar date, complete representation. 268 Type example: 269 BDAY: 1996-04-15 271 3.5. Delivery Addressing Profile Types 273 These profile types are concerned with information associated with the 274 delivery addressing or label for the vCard object. 276 3.5.1. ADR Type Definition 278 To: ietf-mime-direct@umich.edu 279 Subject: Registration of application/directory MIME type ADR 281 Type name: ADR 283 Type purpose: To specify the structured delivery address strings of 284 the individual or resource associated with the vCard. 286 Type encoding: text 288 Type special notes: The type value is a string consisting of a 289 sequence of address components (i.e., extended address, street 290 address, locality, region, postal code, and country name) separated 291 by SEMI-COLON and optionally one or more LWSP. 293 The usual line-folding technique described in [MIME-DIR] can be used 294 to represent multi-line addresses. For example, a line break in a 295 value should be encoded using either Base64 or Quoted- Printable 296 methods. 298 The type may include the type parameter "TYPE" to further qualify the 300 Expires November 1996 INTERNET DRAFT 302 usage of the delivery address. The TYPE parameter values may 303 include: "DOM" to indicate a domestic delivery address, "INTL" to 304 indicate an international delivery address, "POSTAL" to indicate a 305 postal delivery address, "PARCEL" to indicate a parcel delivery 306 address, "HOME" to indicate a delivery address for a residence, 307 "WORK" to indicate delivery address for a place of work, and "PREF" 308 for the preferred delivery address when more than one address might 309 be specified. These type parameter values may be specified as a 310 parameter list (i.e., "TYPE=DOM, TYPE=POSTAL") or as a value list 311 (i.e., "TYPE=DOM, POSTAL"). This type is based on semantics of the 312 X.520 geographical and postal addressing attributes. The type may 313 also specify the type parameters CHARSET, to specify a character set 314 for the type value, and LANGUAGE, to specify a language for the type 315 value. These are further defined in [MIME- DIR]. 317 Type example: 318 ADR;ENCODING=QUOTED-PRINTABLE;TYPE=DOM,HOME,= 319 POSTAL,PARCEL: 123 Main Street;Any Town; CA;91921-1234 321 3.5.2. FADR Type Definition 323 To: ietf-mime-direct@umich.edu 324 Subject: Registration of application/directory MIME type FADR 326 Type name: FADR 328 Type purpose: To specify the formatted delivery address string of the 329 individual or resource associated with the vCard. 331 Type encoding: text 333 Type special notes: The type value is a string consisting of a 334 sequence of lines of formatted text corresponding to the delivery 335 address. 337 The usual line-folding technique described in [MIME-DIR] can be used 338 to represent multi-line addresses. For example, a formatted line 339 break in a value should be encoded using either Base64 or Quoted- 340 Printable methods. 342 The type may include the type parameter "TYPE" to further qualify the 343 usage of the delivery label. The TYPE parameter values may include: 344 "DOM" to indicate a domestic delivery label, "INTL" to indicate an 345 international delivery label, "POSTAL" to indicate a postal delivery 346 label, "PARCEL" to indicate a parcel delivery label, "HOME" to indi- 347 cate a delivery label for a residence, "WORK" to indicate delivery 348 label for a place of work, and "PREF" for the preferred delivery 349 label when more than one label might be specified. These type 351 Expires November 1996 INTERNET DRAFT 353 parameter values may specified as a parameter list (i.e., "TYPE=DOM, 354 TYPE=POSTAL") or as a value list (i.e., "TYPE=DOM, POSTAL"). This 355 type is based on semantics of the X.520 geographical and postal 356 addressing attributes. 358 Type example: 359 FADR;ENCODING=QUOTED-PRINTABLE;TYPE=DOM,HOME,= 360 POSTAL,PARCEL: Mr.John Q. Public, Esq.=0A= 361 Mail Drop: TNE QB=0A= 362 123 Main Street=0A= 363 Any Town, CA 91921-1234=0A= 364 U.S.A.= 366 3.6. Telecommunications Addressing Profile Types 368 These profile types are concerned with information associated with 369 the telecommunications addressing of the vCard object. 371 3.6.1. TEL Type Definition 373 To: ietf-mime-direct@umich.edu 374 Subject: Registration of application/directory MIME type TEL 376 Type name: TEL 378 Type purpose: To specify the telephone number for telephony communi- 379 cation with the individual or resource associated with the vCard. 381 Type encoding: text. 383 Type special notes: .The value of this type is specified in a canoni- 384 cal form in order to specify an unambiguous representation of the 385 globally unique telephone endpoint. This type is based on the X.500 386 Telephone Number attribute. 388 The type may include the type parameter "TYPE" to further qualify the 389 usage of the telephone number. The TYPE parameter values may 390 include: "HOME" to indicate a telephone number associated with a 391 residence, "MSG" to indicate the telephone line has voice messaging 392 support, "WORK" to indicate a telephone number associated with a 393 place of work, "PREF" to indicate a preferred-use telephone number, 394 "VOICE" to indicate a voice telephone line, "FAX" to indicate a fac- 395 simile telephone line, "CELL" to indicate a cellular telephone line, 396 "VIDEO" to indicate a video conferencing telephone line, "PAGER" to 397 indicate a paging device telephone line, "BBS" to indicate a bulletin 398 board system telephone line, "MODEM" to indicate a MODEM connected 399 telephone line, "CAR" to indicate a car- phone telephone line, "ISDN" 400 to indicate an ISDN service telephone line. These type parameter 402 Expires November 1996 INTERNET DRAFT 404 values may specified as a parameter list (i.e., "TYPE=WORK, 405 TYPE=VOICE") or as a value list (i.e., "TYPE=WORK, VOICE"). 407 Type example: 408 TEL;TYPE=WORK,VOICE,PREF,MSG: +1-213-555-1234 410 3.6.2. EMAIL Type Definition 412 To: ietf-mime-direct@umich.edu 413 Subject: Registration of application/directory MIME type EMAIL 415 Type name: EMAIL 417 Type purpose: To specify the address for electronic mail communica- 418 tion with the vCard object. The address is in the form of a specific 419 addressing type. The default is an Internet addressing type. 421 Type encoding: text. 423 Type special notes: . The type may include the type parameter "TYPE" 424 to specify the addressing type of the electronic mail address. The 425 TYPE parameter values may include: "INTERNET" to indicate an Internet 426 addressing type or "X400" to indicate a X.400 addressing type. Other 427 type values are allowed, but are to be specified by individual elec- 428 tronic mail service providers. 430 Type example: 431 EMAIL;Type=INTERNET: jqpublic@xyz.dom1.com 433 3.6.3. MAILER Type Definition 435 To: ietf-mime-direct@umich.edu 436 Subject: Registration of application/directory MIME type MAILER 438 Type name: MAILER 440 Type purpose: To specify the type of electronic mail software that is 441 used by the individual associated with the vCard object. 443 Type encoding: text. 445 Type special notes: This information may provide assistance to a 446 correspondent regarding the type of data representation which can be 447 used, and how they may be packaged. This property is based on the 448 private MIME type X-Mailer that is generally accepted within the MIME 449 user agent product offerings. 451 Type example: 453 Expires November 1996 INTERNET DRAFT 455 MAILER: cc:Mail Mobil 2.2 457 3.7. Geographical Profile Types 459 These profile types are concerned with information associated with geo- 460 graphical positions or regions associated with the vCard object. 462 3.7.1. TZ Type Definition 464 To: ietf-mime-direct@umich.edu 465 Subject: Registration of application/directory MIME type TZ 467 Type name: TZ 469 Type purpose: To specify information related to the time zone of the 470 vCard object. 472 Type encoding: text. 474 Type special notes: the type value is specified as a string as speci- 475 fied in a manner consistent with [ISO 8601]. It is an offset from 476 Coordinated Universal Time (UTC). An ISO 8601 UTC offset, in basic 477 format, is specified as a positive or negative difference in units of 478 hours and minutes (e.g., +hhmm). If minutes are zero, then they may 479 be omitted and the format would be specified in units of hours (e.g., 480 +hh). The time is specified as a 24-hour clock. Hour values are from 481 00 to 24, and minute values are from 00 to 59. Hour and minutes are 482 2-digits with high order zeroes required to maintain digit count. 483 The extended format for ISO 8601 makes use of a colon character as a 484 separator of the hour and minute substrings. 486 Type example: 487 TZ: -05 489 3.7.2. GEO Type Definition 491 To: ietf-mime-direct@umich.edu 492 Subject: Registration of application/directory MIME type GEO 494 Type name: GEO 496 Type purpose: To specify information related to the global position- 497 ing of the vCard object. 499 Type encoding: text. 501 Type special notes: the type value is a structured string that speci- 502 fies a longitude and latitude. The latitude represents the location 504 Expires November 1996 INTERNET DRAFT 506 north and south of the equator as a positive or negative number, 507 respectively. The longitude represents the location east and west of 508 the prime meridian as a positive or negative number, respectively. 509 The string components are separated by the SEMI- COLON character. 511 Type example: 512 GEO: 37.24; -17.87 514 3.8. Organizational Profile Types 516 These profile types are concerned with information associated with 517 characteristics of the organization or organizational units associated 518 with the vCard object. 520 3.8.1. TITLE Type Definition 522 To: ietf-mime-direct@umich.edu 523 Subject: Registration of application/directory MIME type TITLE 525 Type name: TITLE 527 Type purpose: To specify the job title, functional position or func- 528 tion of the individual or resource associated with the vCard object 529 within an organization 531 Type encoding: text. 533 Type special notes: This type is based on the X.520 Title attribute. 535 The type may specify the type parameters CHARSET, to specify a char- 536 acter set for the type value, and LANGUAGE, to specify a language for 537 the type value. These are further defined in [MIME- DIR]. 539 Type example: 540 TITLE: Director, Research and Development 542 3.8.2. ROLE Type Definition 544 To: ietf-mime-direct@umich.edu 545 Subject: Registration of application/directory MIME type ROLE 547 Type name: ROLE 549 Type purpose: To specify information concerning the role, occupation, 550 or business category of the vCard object within an organization. 552 Type encoding: text. 554 Expires November 1996 INTERNET DRAFT 556 Type special notes: This type is based on the X.520 Business Category 557 explanatory attribute. This property is included as an organiza- 558 tional type to avoid confusion with the semantics of the TITLE type 559 and incorrect usage of that type when the semantics of this type is 560 intended. 562 The type may specify the type parameters CHARSET, to specify a char- 563 acter set for the type value, and LANGUAGE, to specify a language for 564 the type value. These are further defined in [MIME- DIR]. 566 Type example: 567 ROLE: Programmer 569 3.8.3. LOGO Type Definition 571 To: ietf-mime-direct@umich.edu 572 Subject: Registration of application/directory MIME type LOGO 574 Type name: LOGO 576 Type purpose: To specify a graphic image of the logo of the organiza- 577 tion that is associated with the individual or resource the vCard 578 belongs to. 580 Type encoding: text. 582 Type special notes: The type may include the type parameter "TYPE" to 583 specify the format of the graphic image. The TYPE parameter values 584 may include "GIF" to indicate the GIF format and "JPEG" to indicate 585 the JPEG format. The type may also include the type parameter 586 "ENCODING" to specify the content encoding applied to the graphic 587 image. The ENCODING parameter value may include "BASE64" to indicate 588 the Base64 encoding or "QUOTED-PRINTABLE" to indicate the quoted- 589 printable encoding. The type may also include the type parameter 590 "VALUE" to specify the location of the type value. The VALUE parame- 591 ter values may include "INLINE" to indicate that the graphic image 592 value is included within the content type value, "URL" to indicate 593 the uniform resource locator for where the content for the graphic 594 image can be found in the network, and "CID" to indicate the 595 content-id for the MIME entity that encapsulates the content for the 596 graphic image. 598 Type example: 599 LOGO;TYPE=JPEG;VALUE=URL: http://www.abc.com/pub/logos/abccorp.jpg 601 3.8.4. AGENT Type Definition 603 To: ietf-mime-direct@umich.edu 605 Expires November 1996 INTERNET DRAFT 607 Subject: Registration of application/directory MIME type AGENT 609 Type name: AGENT 611 Type purpose: To specify information about another person who will 612 act on behalf of the individual or resource associate with the vCard 613 object. 615 Type encoding: text. 617 Type special notes: This type typically is used to specify an area 618 administrator, assistant, or secretary for the individual associated 619 with the vCard object. A key characteristic of the Agent type is 620 that it represents somebody or something that is separately address- 621 able. The value for this type is the content message identifier or 622 Uniform Resource Locator associated with the vCard defining the Agent 623 individual or resource. 625 The type may include the type parameter "VALUE" to specify the loca- 626 tion of the type value. The VALUE parameter values may include "CID" 627 to indicate the value specifies the content identifier for the MIME 628 entity containing the value or "URL" to indicate the value specifies 629 the uniform resource locator for the value. The type parameter may 630 also include "INLINE"; however, this is not a recommended practice as 631 MIME user agents will not be expected to be able to process vCard 632 objects nested in this manner. Nested vCard object will be expected 633 to be mailed within a single message as multiple MIME entities. The 634 INLINE nesting of vCard object may have some limited utility in where 635 a monolithic data stream is required. 637 Type example: 638 AGENT;VALUE=CID: 640 3.8.5. ORG Type Definition 642 To: ietf-mime-direct@umich.edu 643 Subject: Registration of application/directory MIME type ORG 645 Type name: ORG 647 Type purpose: To specify the organizational name and units associated 648 with the vCard object. 650 Type encoding: text. 652 Type special notes: The type is based on the X.520 Organization Name 653 and Organization Unit attributes. The type value is a structured 654 string consisting of the organization name, followed by any 656 Expires November 1996 INTERNET DRAFT 658 organizational units. The string components are separated the SEMI- 659 COLON character. 661 The type may specify the type parameters CHARSET, to specify a char- 662 acter set for the type value, and LANGUAGE, to specify a language for 663 the type value. These are further defined in [MIME- DIR]. 665 Type example: 666 ORG: ABC, Inc.;North American Division;Marketing 668 3.9. Explanatory Profile Types 670 These profile types are concerned with additional explanations, such as 671 that related to informational notes or revisions specific to the vCard 672 object. 674 3.9.1. NOTE Type Definition 676 To: ietf-mime-direct@umich.edu 677 Subject: Registration of application/directory MIME type NOTE 679 Type name: NOTE 681 Type purpose: To specify supplemental information or a comment that 682 is associated with the vCard object. 684 Type encoding: text. 686 Type special notes: The type is based on the X.520 Description attri- 687 bute. 689 The type may specify the type parameters CHARSET, to specify a char- 690 acter set for the type value, and LANGUAGE, to specify a language for 691 the type value. These are further defined in [MIME- DIR]. 693 Type example: 694 NOTE: This fax number is operational 0800 to 1715 EST, Mon-Fri. 696 3.9.2. REV Type Definition 698 To: ietf-mime-direct@umich.edu 699 Subject: Registration of application/directory MIME type REV 701 Type name: REV 703 Type purpose: To specify revision information about the current vCard 704 object. 706 Expires November 1996 INTERNET DRAFT 708 Type encoding: text. 710 Type special notes: The type value is a calendar date and time of day 711 in a form conforming to ISO 8601 complete representation. The value 712 distinguishes the current revision of the information defining this 713 vCard object. 715 Type example: 716 REV: 19951031T222710Z 718 3.9.3. SOUND Type Definition 720 To: ietf-mime-direct@umich.edu 721 Subject: Registration of application/directory MIME type SOUND 723 Type name: SOUND 725 Type purpose: To specify a digital sound content information that 726 annotates some aspect of the vCard object. By default this type is 727 used to specify the proper pronunciation of the name type value of 728 the vCard object. 730 Type encoding: text. 732 Type special notes: The type may include the type parameter "TYPE" to 733 specify the format of the digital sound. The TYPE parameter values 734 may include "PCM" to indicate the MIME basic audio content type and 735 "WAVE" to indicate the Wave format. The type may also include the 736 type parameter "ENCODING" to specify the content encoding applied to 737 the digital sound. The ENCODING parameter value may include "BASE64" 738 to indicate the Base64 encoding. The type may also include the type 739 parameter "VALUE" to specify the location of the type value. The 740 VALUE parameter values may include "INLINE" to indicate that the 741 digital sound is included within the content type value, "URL" to 742 indicate the uniform resource locator for where the content for the 743 digital sound can be found in the network, and "CID" to indicate the 744 content-id for the MIME entity that encapsulates the content for the 745 digital sound. 747 Type example: 748 SOUND;TYPE=PCM;ENCODE=QUOTED-PRINTABLE;VALUE=CID: = 749 751 3.9.4. URL Type Definition 753 To: ietf-mime-direct@umich.edu 754 Subject: Registration of application/directory MIME type URL 756 Expires November 1996 INTERNET DRAFT 758 Type name: URL 760 Type purpose: To specify an Internet location that can be used to 761 obtain real-time or more complete information about the individual or 762 resource associate with the vCard object. 764 Type encoding: text. 766 Type special notes: An application of this type might be to specify 767 the location of a publicly accessible directory, such as an Internet 768 whitepages, where up-todate information can be found about the indi- 769 vidual specified by a vCard. 771 Type example: 772 URL: http://www.swbyps.restaurant.french/~chezchic.html 774 3.9.5. UID Type Definition 776 To: ietf-mime-direct@umich.edu 777 Subject: Registration of application/directory MIME type UID 779 Type name: UID 781 Type purpose: To specify a value that represents a globally unique 782 identifier corresponding to the individual or resource associated 783 with the vCard object. 785 Type encoding: text. 787 Type special notes: The type value can be used as a mechanism to 788 relate different vCard objects. Some examples of valid forms of 789 unique identifiers would include ISO 9070 formal public identifiers 790 (FPI) as defined in [ISO 9070], X.500 distinguished names, machine- 791 generated random numbers with a statistically high likelihood of 792 being globally unique, and Uniform Resource Locators (URL). If an 793 URL is specified, it is suggested that the URL reference a service 794 which will produce an updated version of the vCard associated with 795 the individual or resource. 797 The type may include the type parameter "TYPE" to specify the format 798 of the unique identifier. The TYPE parameter values may include 799 "ISO9070" to indicate the ISO 9070 FPI type of unique identifier, 800 "X500" to indicate the X.500 DSN type of unique identifier, "MACH" to 801 indicate a machine generated random number type of unique identifier, 802 and "URL" to indicate a Uniform Resource Locator type of unique iden- 803 tifier. 805 Type example: 807 Expires November 1996 INTERNET DRAFT 809 UID;TYPE=MACH: 19950401-080045-40000F192713-0052 811 3.10. Security Profile Types 813 These profile types are concerned with the security of communication 814 pathways or access to the vCard object. 816 3.10.1. KEY Type Definition 818 To: ietf-mime-direct@umich.edu 819 Subject: Registration of application/directory MIME type KEY 821 Type name: KEY 823 Type purpose: To specify a public key that conforms to a bilaterally 824 agreed to representation. 826 Type encoding: text. 828 Type special notes: The type may include the type parameter "ENCOD- 829 ING" to specify the content encoding applied to the public key. The 830 ENCODING parameter value may include "BASE64" to indicate the Base64 831 encoding or "QUOTED-PRINTABLE" to indicate the quoted- printable 832 encoding. The type may also include the type parameter "TYPE" to 833 specify the type of the public key. The TYPE parameter value may 834 include "X509" to indicate a X.509 public key certificate or "PGP" to 835 indicate an PGP public key. 837 3.11. Extended Profile Types 839 The profile types defined by this document can be extended with private 840 types using the private type mechanism defined in [MIME]. Private types 841 with a name starting with "X-" may be defined bilaterally between two 842 cooperating agents without outside registration or standardization. 844 4. Formal Grammar 846 The following grammar defines the content entity specified by this pro- 847 file. 849 This syntax is written according to the form described in RFC 822, but 850 it references just this small subset of RFC 822 literals: 852 CR = ; ( 15, 13.) 853 LF = ; ( 12, 10.) 854 CRLF = CR LF 855 SPACE = ; ( 40, 32.) 856 HTAB = ; ( 11, 9.) 858 Expires November 1996 INTERNET DRAFT 860 All literal property names are valid as upper, lower, or mixed case. 862 vcard_file = [wsls] vcard [wsls] 864 vcard = "BEGIN:VCARD" CRLF items "END:VCARD" 866 ws = 1*(SPACE / HTAB) 867 ; "whitespace," one or more spaces or tabs 869 wsls = 1*(SPACE / HTAB / CRLF) 870 ; whitespace with line separators 872 items = items item 873 / item 875 item = [ws] [groups "."] name 876 [params] ":" value CRLF 877 / [ws] [groups "."] "ADR" 878 [params] ":" addressparts CRLF 879 / [ws] [groups "."] "ORG" 880 [params] ":" orgparts CRLF 881 / [ws] [groups "."] "N" 882 [params] ":" nameparts CRLF 883 / [ws] [groups "."] "AGENT" 884 [params] ":" vcard CRLF 886 value = 7bit / quoted-printable / base64 888 7bit = <7bit us-ascii printable chars, excluding CR LF> 890 quoted-printable = 892 base64 = 894 groups = groups "." word 895 / word 897 word = 899 params = ";" param / paramlist 901 paramlist = paramlist ";" param 902 / param 904 param = "TYPE" "=" ptypeval 905 / "VALUE" "=" pvalueval 906 / "ENCODING" "=" pencodingval 907 / "CHARSET" "=" charsetval 909 Expires November 1996 INTERNET DRAFT 911 / "LANGUAGE" "=" langval 912 / "X-" word "=" word 913 / knowntype 915 ptypeval = knowntype / "X-" word 917 pvalueval = "INLINE" / "URL" / "CID" / "X-" word 919 pencodingval = "7BIT" / "QUOTED-PRINTABLE" / "BASE64" / "X-" word 921 charsetval = 924 langval = 926 addressparts = 5*5(strnosemi ";") strnosemi 928 orgparts = *(strnosemi ";") strnosemi 929 ; First is Organization Name, remainder are Organization Units. 931 nameparts = 0*4(strnosemi ";") strnosemi 932 ; Family, Given, Middle, Prefix, Suffix. 933 ; Example: Public;John;Q.;Reverend Dr.;III, Esq. 935 strnosemi = *(*nonsemi (";" / " 936 ; To include a semicolon in this string, it must be escaped 937 ; with a " 939 nonsemi = 941 name = "LOGO" / "PHOTO" / "LABEL" / "FN" / "TITLE" 942 / "SOUND" / "LANG" / "TEL" / "EMAIL" / "TZ" / "GEO" / "NOTE" 943 / "URL" / "BDAY" / "ROLE" / "REV" / "UID" / "KEY" 944 / "MAILER" / "X-" word 946 knowntype = "DOM" / "INTL" / "POSTAL" / "PARCEL" / "HOME" / "WORK" 947 / "PREF" / "VOICE" / "FAX" / "MSG" / "CELL" / "PAGER" 948 / "BBS" / "MODEM" / "CAR" / "ISDN" / "VIDEO" 949 / "AOL" / "APPLELINK" / "ATTMAIL" / "CIS" / "EWORLD" 950 / "INTERNET" / "IBMMAIL" / "MSN" / "MCIMAIL" 951 / "POWERSHARE" / "PRODIGY" / "TLX" / "X400" 952 / "GIF" / "CGM" / "WMF" / "BMP" / "MET" / "PMB" / "DIB" 953 / "PICT" / "TIFF" / "ACROBAT" / "PS" / "JPEG" / "QTIME" 954 / "MPEG" / "MPEG2" / "AVI" 955 / "WAVE" / "AIFF" / "PCM" 956 / "X509" / "PGP" 958 Expires November 1996 INTERNET DRAFT 960 4.1. Acknowledgements 962 The authors would like to thank the participants in the IETF ASID work- 963 ing group, in addition to the following individuals, Roland Alden, 964 Stephen Bartlett, Daniel Klaussen, Michelle Watkins; who provided 965 numerous suggestions and comments on this work. 967 4.2. Authors's Addresses 969 BEGIN: vCard 970 FN: Frank Dawson 971 ORG: IBM Corporation;Network Software Division 972 ADR;TYPE=WORK,POSTAL,PARCEL;ENCODING=QUOTED-PRINTABLE: APNA/CC-303/Bldg. 002;= 973 3039 Cornwallis Rd.;Research Triangle Park;NC;27709;U.S.A. 974 TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861 975 TEL;TYPE=FAX,WORK: +1-919-543-6822 976 EMAIL;TYPE=INTERNET: frank_dawson@vnet.ibm.com 977 END: vCard 979 BEGIN: vCard 980 FN: Tim Howes 981 ORG: Netscape Communications Corp. 982 ADR;TYPE=WORK: 685 E. Middlefield Rd.;Mountain View;CA;94043;U.S.A. 983 TEL;TYPE=VOICE,MSG,WORK: +1-415-254-1900 984 EMAIL;TYPE=INTERNET: howes@netscape.com 985 END: vCard 987 4.3. References 989 [ISO 639] 990 ISO 639:1988 - Code for the representation of names of languages - 991 The International Organization for Standardization, April 1988. 993 [ISO 3166] 994 ISO 3166:1993 - Codes for the representation of names of countries 995 - The International Organization for Standardization, December 996 1993. 998 [ISO 8601] 999 ISO 8601:1988 - Data elements and interchange formats - Information 1000 interchange - Representation of dates and times - The International 1001 Organization for Standardization, June, 1988. 1003 [ISO 8601 TC] 1004 ISO 8601, Technical Corrigendum 1 - Data elements and interchange 1005 formats - Information interchange - Representation of dates and 1006 times - The International Organization for Standardization, May, 1008 Expires November 1996 INTERNET DRAFT 1010 1991. 1012 [ISO 9070] 1013 ISO 9070, Information Processing - SGML support facilities - Regis- 1014 tration Procedures for Public Text Owner Identifiers, April, 1991. 1016 [CCITT E.163] 1017 Recommendation E.163 - Numbering Plan for The International Tele- 1018 phone Service, CCITT Blue Book, Fascicle II.2, pp. 128-134, 1019 November, 1988. 1021 [CCITT X.121] 1022 Recommendation X.121 - International Numbering Plan for Public Data 1023 Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, November, 1024 1988. 1026 [CCITT X.520] 1027 Recommendation X.520 - The Directory - Selected Attribute Types, 1028 November 1988. 1030 [CCITT X.521] 1031 Recommendation X.521 - The Directory - Selected Object Classes, 1032 November 1988. 1034 [MIME-DIR] 1035 Howes, T., Smith, M., "A MIME Content-Type for Directory Informa- 1036 tion", Internet-draft-ietf-asid-mime-direct-01.txt, February, 1996. 1038 [MIME-REG] 1039 Freed, N., Postel, J., "Multipurpose Internet Mail Extensions 1040 (MIME) Part Four: Registration Procedures," Internet- Draft 1041 draft-ietf-822ext-mime-reg-02.txt, December 1995. 1043 [RFC-822] 1044 Crocker, D., "Standard for the Format of ARPA Internet Text Mes- 1045 sages", STD 11, RFC 822, August 1982. 1047 [RFC-1521] 1048 Borenstein, N., Freed, N., "MIME (Multipurpose Internet Mail Exten- 1049 sions) Part One: Mechanisms for Specifying and Describing the For- 1050 mat of Internet Message Bodies", RFC 1521, September 1993. 1052 [RFC-1522] 1053 Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Two: 1054 Message Header Extensions for Non-ASCII Text", RFC 1522, September 1055 1993. 1057 [RFC-1738] 1059 Expires November 1996 INTERNET DRAFT 1061 Berners-Lee, T., Masinter, L., McCahill, M., "Uniform Resource 1062 Locators (URL)", RFC 1738, December 1994. 1064 [RFC-1766] 1065 Alvestrand, H., "Tags for the Identification of Languages", March 1066 1995. 1068 [RFC-1872] 1069 Levinson, E., "The MIME Multipart/Related Content-type," RFC 1872, 1070 December 1995. 1072 [VERSIT-VCARD] 1073 VERSIT Consortium, "Electronic Business Card (vCard) Specifica- 1074 tion", http://www.versit.com, March, 1996. vCard 1075 Application/Directory Content Type