idnits 2.17.1 draft-ietf-asid-mime-vcard-01.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. ** 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 22 longer pages, the longest (page 20) being 64 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 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 104: '...in a type value, MUST also be specifie...' RFC 2119 keyword, line 107: '... multiple lines) MUST be encoded using...' RFC 2119 keyword, line 375: '...acter in a value MUST be encoded using...' RFC 2119 keyword, line 427: '...acter in a value MUST be encoded using...' RFC 2119 keyword, line 1005: '... the vCard profile MUST be _2.1_....' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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.) -- The document date (November 26, 1996) is 10012 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 1215 looks like a reference -- Missing reference section? 'VCARD' on line 1243 looks like a reference -- Missing reference section? 'RFC 822' on line 120 looks like a reference -- Missing reference section? 'RFC 1521' on line 109 looks like a reference -- Missing reference section? 'ISO 8601' on line 1185 looks like a reference -- Missing reference section? 'ISO 9070' on line 1194 looks like a reference -- Missing reference section? 'MIME' on line 1010 looks like a reference -- Missing reference section? 'ISO 639' on line 1177 looks like a reference -- Missing reference section? 'ISO 3166' on line 1181 looks like a reference -- Missing reference section? 'MIME-REG' on line 1219 looks like a reference -- Missing reference section? 'RFC-822' on line 1223 looks like a reference -- Missing reference section? 'RFC-1521' on line 1226 looks like a reference -- Missing reference section? 'RFC-1522' on line 1230 looks like a reference -- Missing reference section? 'RFC-1738' on line 1234 looks like a reference -- Missing reference section? 'RFC-1766' on line 1237 looks like a reference -- Missing reference section? 'RFC-1872' on line 1240 looks like a reference Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Frank Dawson 2 INTERNET DRAFT Tim Howes 3 draft-ietf-asid-mime-vcard-01.txt IBM/Netscape Communications 4 November 26, 1996 6 An Application/Directory MIME Content-Type 7 Electronic Business Card 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 a directory information profile for a white pages 30 person, to be carried in an application/directory MIME Content-Type. 31 The profile consists of type definitions (e.g., for name and email 32 address) and the corresponding format of values that each type is 33 allowed to contain. 35 1. Overview 37 The application/directory MIME Content-Type defined in [MIME-DIR] is 38 used for representing directory information in MIME format. It 39 defines a general framework for carrying _type: value_ style 40 information in the body of a MIME message, but does not define 41 specific types or values. This document defines a profile containing 42 the types and corresponding value formats for representing 43 information about an electronic business card. The profile reflects 44 the vCard (The Electronic Business Card) schema defined in [VCARD]. 46 1.1 The vCard Profile 48 The profile is defined as follows, using the profile registration 49 template from Section 8 of [MIME-DIR]. 51 1.2 vCard Profile Definition 53 To: ietf-mime-direct@umich.edu 55 Subject: Registration of application/directory MIME profile vcard 57 Dawson & Howes [Page 1] Expires June 1997 58 vCard Application/Directory Content Type 60 Profile name: vcard 62 Profile purpose: To hold vcard information about an electronic 63 business card. 65 Profile types: BEGIN, END, FN, N, PHOTO, BDAY, ADR, LABEL, TEL, 66 EMAIL, MAILER, TZ, GEO, TITLE, ROLE, LOGO, AGENT, ORG, NOTE, REV, 67 SOUND, URL, UID, VERSION, KEY 69 Profile special notes: The content entity must begin with the type 70 BEGIN and end with the type END. There is no other ordering 71 limitations on types within the content entity. 73 The default transfer encoding for the vCard profile is _8BIT_. The 74 default transfer encoding can be overridden for an individual type 75 value by using the _ENCODING_ type parameter. The parameter value can 76 be reset to either _7BIT_, _BASE64_ or _QUOTED-PRINTABLE_. This type 77 parameter may be used on any profile type. 79 The usual line-folding technique described in [MIME-DIR] can be used 80 to represent type values consisting of long lines of text. For 81 example, individual lines in the content entity are delimited by the 82 [RFC 822] line break, which is a CRLF sequence (ASCII decimal 13, 83 followed by ASCII decimal 10). Long lines of text can be split into a 84 multiple-line representation using the RFC 822 _folding_ technique. 85 That is, wherever there may be linear white space (NOT simply LWSP- 86 chars), a CRLF immediately followed by at least one LWSP-char may 87 instead be inserted. For example the line: 89 NOTE:This is a long note that exists on a long line. 91 Can be represented as: 93 NOTE:This is a long note 94 that exists on a long line. 96 The process of moving from this folded multiple-line representation 97 of a type value to its single line representation is called 98 _unfolding_. Unfolding is accomplished by regarding CRLF immediately 99 followed by a LWSP-char as equivalent to the LWSP-char. 101 It is recommended that folding be limited to higher-level syntactic 102 breaks in structured components of the property definition. 104 A formatted text line break in a type value, MUST also be specified 105 by a (RFC 822) line break, which is a CRLF sequence. However, since 106 the CRLF sequence is used to delimit a line, type values with 107 formatted line breaks (i.e., multiple lines) MUST be encoded using an 108 alternate encoding of either Quoted-Printable or Base64, as defined 109 in [RFC 1521]. 111 For example, in the Quoted-Printable encoding the multiple lines of 112 formatted text are separated with a Quoted-Printable CRLF sequence of 113 _=0D_ followed by _=0A_ followed by a Quoted-Printable soft line 115 Dawson & Howes [Page 2] Expires June 1997 116 vCard Application/Directory Content Type 118 break sequence of _=_. Quoted-Printable lines of text must also be 119 limited to less than 76 characters. The 76 characters does not 120 include the CRLF [RFC 822] line break sequence. For example a 121 multiple line LABEL value of: 123 Mr. John Q. Public 124 123 Main Street 125 Any Town, CA 12345 127 Would be represented in a Quoted-Printable encoding as: 129 LABEL;ENCODING=QUOTED-PRINTABLE:Mr. John Q. Public=0D=0A= 130 123 Mail Street=0D=0A= 131 Any Town, CA 12345 133 Compound property values are delimited by a field delimiter, 134 specified by the SEMI-COLON character (ASCII decimal 59). A SEMI- 135 COLON in a component of a compound property value must be escaped 136 with a Backslash character 138 The default character set is _UTF-8_. The default character set can 139 be overridden for an individual type value by using the _CHARSET_ 140 type parameter. This type parameter may be used on any profile type. 141 However, the use of this parameter on some profile types may not make 142 sense. 144 The default language is _en-US_ (US English). The default language 145 can be overridden for an individual type value by using the 146 _LANGUAGE_ type parameter. This type parameter may be used on any 147 profile type. However, the use of this parameter on some profile 148 types may not make sense. 150 The default location of the type values is inline with the profile 151 type. However, for some profile types, such as those that specify 152 multimedia values, it is efficient to organize the type value as a 153 separate MIME entity. The type parameter _VALUE_ can be specified to 154 override the _INLINE_ location of the type value. The type value can 155 be specified as being located in a separate MIME entity with the 156 _CID_ value. In this case, the type value is the Content-ID for the 157 MIME entity containing the type value. In addition, the type value 158 can be specified as being located out on the network within some 159 Internet resource with the _URL_ value. In this case, the type value 160 is the Uniform Resource Locator for the Internet resource containing 161 the type value. This type parameter may be used on any profile type. 162 However, the use of this parameter on some profile types may not make 163 sense. 165 This profile supports the type grouping mechanism defined in [MIME- 166 DIR]. Grouping of related profile types is a useful technique to 167 communicate common semantics concerning the properties of a vCard 168 object. 170 Intended usage: COMMON 172 Dawson & Howes [Page 3] Expires June 1997 173 vCard Application/Directory Content Type 175 The associated type definitions follow, using the type registration 176 template from Section 9 of [MIME-DIR]. 178 1.3 Delimiter Profile Types 180 The following profile types are used to delimit the vCard data within 181 the content type. These types are necessary to completely define the 182 content type so that it might be identified as a vCard object when 183 the content type is in a persistent form outside of a MIME message. 185 1.3.1 BEGIN Type Definition 187 To: ietf-mime-direct@umich.edu 189 Subject: Registration of application/directory MIME type BEGIN 191 Type name: BEGIN 193 Type purpose: To delimit the beginning of the vCard content data. 195 Type encoding: text. 197 Type special notes: The only valid value is _vCard_. 199 Type example: 201 BEGIN:vCard 203 1.3.2 END Type Definition 205 To: ietf-mime-direct@umich.edu 207 Subject: Registration of application/directory MIME type END 209 Type name: END 211 Type purpose: To delimit the end of the vCard content data. 213 Type encoding: text. 215 Type special notes: The type either has no value or has the value 216 _vCard_. 218 Type example: 220 END: vCard 222 1.4 Identification Profile Types 224 These profile types are concerned with information associated with 225 the identification and naming of the individual or resource 226 associated with the vCard object. 228 Dawson & Howes [Page 4] Expires June 1997 229 vCard Application/Directory Content Type 231 1.4.1 FN Type Definition 233 To: ietf-mime-direct@umich.edu 235 Subject: Registration of application/directory MIME type FN 237 Type name:FN 239 Type purpose: To specify the formatted name string associated with 240 the vCard object. 242 Type encoding: text. 244 Type special notes: The value is intended to be used as a formatted 245 string corresponding to how the name of the individual or resource 246 associated with the vCard is to be displayed. This type is based on 247 the semantics of the X.520 Common Name attribute. 249 The type may specify the type parameters CHARSET, to specify a 250 character set for the type value, and LANGUAGE, to specify a language 251 for the type value. These are further defined in [MIME-DIR]. 253 Type example: 255 FN:Mr. John Q. Public, Esq. 257 1.4.2 N Type Definition 259 To: ietf-mime-direct@umich.edu 261 Subject: Registration of application/directory MIME type N 263 Type name: N 265 Type purpose: To specify the structured name strings associated with 266 the vCard object. 268 Type encoding: text. 270 Type special note: The type value is a structured string 271 corresponding, in sequence, to the Family Name, Given Name, 272 Additional Names, Honorific Prefixes, and Suffixes corresponding to 273 the individual or resource associated with the vCard. The component 274 strings are delimited by SEMI-COLON character (ASCII decimal 59) and 275 possibly one or more LWSP. This type is based on the semantics of the 276 X.520 individual name attributes. 278 The type may specify the type parameters CHARSET, to specify a 279 character set for the type value, and LANGUAGE, to specify a language 280 for the type value. These are further defined in [MIME-DIR]. 282 Type example: 284 N:Public;John;Quinlan;Mr.;Esq. 286 Dawson & Howes [Page 5] Expires June 1997 287 vCard Application/Directory Content Type 289 1.4.3 PHOTO Type Definition 291 To: ietf-mime-direct@umich.edu 293 Subject: Registration of application/directory MIME type PHOTO 295 Type name: PHOTO 297 Type purpose: To specify an image or photograph information that 298 annotates some aspect of the vCard object. By default this type is 299 used to specify a photograph or image of the individual or resource 300 associated with the vCard. 302 Type encoding: text. 304 Type special notes: The type may include the type parameter _TYPE_ to 305 specify the format of the graphic image. The TYPE parameter values 306 may include _GIF_ to indicate the GIF format and _JPEG_ to indicate 307 the JPEG format. The type may also include the type parameter 308 _ENCODING_ to specify the content encoding applied to the graphic 309 image. The ENCODING parameter value may include _7BIT_ to indicate 310 the 7-bit encoding, _8BIT_ to indicate the 8-bit encoding, _BASE64_ 311 to indicate the Base64 encoding or _QUOTED-PRINTABLE_ to indicate the 312 quoted printable encoding. The type may also include the type 313 parameter _VALUE_ to specify the location of the type value. The 314 VALUE parameter values may include _INLINE_ to indicate that the 315 graphic image value is included within the content type value, _URL_ 316 to indicate the uniform resource locator for where the content for 317 the graphic image can be found in the network, and _CID_ to indicate 318 the content-id for the MIME entity that encapsulates the content for 319 the graphic image. 321 Type example: 323 PHOTO;VALUE=URL:=http://www.abc.com/pub/photos 324 /jqpublic.gif 326 1.4.4 BDAY Type Definition 328 To: ietf-mime-direct@umich.edu 330 Subject: Registration of application/directory MIME type BDAY 332 Type name: BDAY 334 Type purpose: To specify the birthdate of the individual associated 335 with the vCard. 337 Type encoding: text. 339 Type special notes: The text value is a string conforming to the ISO 340 8601 calendar date, complete representation. 342 Type example: 344 Dawson & Howes [Page 6] Expires June 1997 345 vCard Application/Directory Content Type 347 BDAY:1996-04-15 349 1.5 Delivery Addressing Profile Types 351 These profile types are concerned with information associated with 352 the delivery addressing or label for the vCard object. 354 1.5.1 ADR Type Definition 356 To: ietf-mime-direct@umich.edu 358 Subject: Registration of application/directory MIME type ADR 360 Type name: ADR 362 Type purpose: To specify the structured delivery address strings of 363 the individual or resource associated with the vCard. 365 Type encoding: text 367 Type special notes: The type value is a string consisting of a 368 sequence of address components (i.e., extended address, street 369 address, locality, region, postal code, and country name) separated 370 by SEMI-COLON character (ASCII decimal 59) and optionally one or more 371 LWSP. 373 The usual line-folding technique described in [MIME-DIR] can be used 374 to represent type values consisting of long lines of text. However, a 375 line break character in a value MUST be encoded using either Base64 376 or Quoted-Printable methods. 378 The type may include the type parameter _TYPE_ to further qualify the 379 usage of the delivery address. The TYPE parameter values may include: 380 _DOM_ to indicate a domestic delivery address, _INTL_ to indicate an 381 international delivery address, _POSTAL_ to indicate a postal 382 delivery address, _PARCEL_ to indicate a parcel delivery address, 383 _HOME_ to indicate a delivery address for a residence, _WORK_ to 384 indicate delivery address for a place of work, and _PREF_ for the 385 preferred delivery address when more than one address might be 386 specified. These type parameter values may be specified as a 387 parameter list (i.e., _TYPE=DOM;TYPE=POSTAL_) or as a value list 388 (i.e., _TYPE=DOM;POSTAL_). This type is based on semantics of the 389 X.520 geographical and postal addressing attributes. The default is 390 _TYPE=INTL;POSTAL;PARCEL;WORK_. The default can be overridden to some 391 other set of values by specifying one or more alternate values. For 392 example, the default can be reset to _TYPE=DOM;POSTAL;WORK;HOME_ to 393 specify a domestic delivery address for postal delivery to a 394 residence that is also used for work. 396 The type may also specify the type parameters CHARSET, to specify a 397 character set for the type value, and LANGUAGE, to specify a language 398 for the type value. These are further defined in [MIME-DIR]. 400 Type example: 402 Dawson & Howes [Page 7] Expires June 1997 403 vCard Application/Directory Content Type 405 ADR;TYPE=DOM;HOME;POSTAL;PARCEL:123 Main 406 Street;Any Town;CA;91921-1234 408 1.5.2 LABEL Type Definition 410 To: ietf-mime-direct@umich.edu 412 Subject: Registration of application/directory MIME type LABEL 414 Type name: LABEL 416 Type purpose: To specify the formatted delivery address string of the 417 individual or resource associated with the vCard. 419 Type encoding: text 421 Type special notes: The type value is a string consisting of a 422 sequence of lines of formatted text corresponding to the delivery 423 address. 425 The usual line-folding technique described in [MIME-DIR] can be used 426 to represent type values consisting of long lines of text. However, a 427 formatted line break character in a value MUST be encoded using 428 either Base64 or Quoted-Printable methods. 430 The type may include the type parameter _TYPE_ to further qualify the 431 usage of the delivery label. The TYPE parameter values may include: 432 _DOM_ to indicate a domestic delivery label, _INTL_ to indicate an 433 international delivery label, _POSTAL_ to indicate a postal delivery 434 label, _PARCEL_ to indicate a parcel delivery label, _HOME_ to 435 indicate a delivery label for a residence, _WORK_ to indicate 436 delivery label for a place of work, and _PREF_ for the preferred 437 delivery label when more than one label might be specified. These 438 type parameter values may specified as a parameter list (i.e., 439 _TYPE=DOM;TYPE=POSTAL_) or as a value list (i.e., _TYPE=DOM;POSTAL_). 440 This type is based on semantics of the X.520 geographical and postal 441 addressing attributes. The default is _TYPE=INTL;POSTAL;PARCEL;WORK_. 442 The default can be overridden to some other set of values by 443 specifying one or more alternate values. For example, the default can 444 be reset to _TYPE=INTL;POST;PARCEL;HOME_ to specify an international 445 delivery label for both postal and parcel delivery to a residencial 446 location. 448 Type example: 450 LABEL;ENCODING=QUOTED-PRINTABLE;TYPE=DOM;HOME;= 451 POSTAL;PARCEL:Mr.John Q. Public, Esq.=0D=0A= 452 Mail Drop: TNE QB=0D=0A= 453 123 Main Street=0D=0A= 454 Any Town, CA 91921-1234=0D=0A= 455 U.S.A. 457 Dawson & Howes [Page 8] Expires June 1997 458 vCard Application/Directory Content Type 460 1.6 Telecommunications Addressing Profile Types 462 These profile types are concerned with information associated with 463 the telecommunications addressing of the vCard object. 465 1.6.1 TEL Type Definition 467 To: ietf-mime-direct@umich.edu 469 Subject: Registration of application/directory MIME type TEL 471 Type name: TEL 473 Type purpose: To specify the telephone number for telephony 474 communication with the individual or resource associated with the 475 vCard. 477 Type encoding: text. 479 Type special notes: .The value of this type is specified in a 480 canonical form in order to specify an unambiguous representation of 481 the globally unique telephone endpoint. This type is based on the 482 X.500 Telephone Number attribute. 484 The type may include the type parameter _TYPE_ to further qualify the 485 usage of the telephone number. The TYPE parameter values may include: 486 _HOME_ to indicate a telephone number associated with a residence, 487 _MSG_ to indicate the telephone line has voice messaging support, 488 _WORK_ to indicate a telephone number associated with a place of 489 work, _PREF_ to indicate a preferred-use telephone number, _VOICE_ to 490 indicate a voice telephone line, _FAX_ to indicate a facsimile 491 telephone line, _CELL_ to indicate a cellular telephone line, _VIDEO_ 492 to indicate a video conferencing telephone line, _PAGER_ to indicate 493 a paging device telephone line, _BBS_ to indicate a bulletin board 494 system telephone line, _MODEM_ to indicate a MODEM connected 495 telephone line, _CAR_ to indicate a car-phone telephone line, _ISDN_ 496 to indicate an ISDN service telephone line. The default type is 497 _VOICE_. These type parameter values may specified as a parameter 498 list (i.e., _TYPE=WORK;TYPE=VOICE_) or as a value list (i.e., 499 _TYPE=WORK;VOICE_). The default may be overridden to another set of 500 values by specifying one or more alternate values. For example, the 501 default TYPE of _VOICE_ can be reset to a WORK and HOME, VOICE and 502 FAX telephone number by the value list _TYPE=WORK;HOME;VOICE;FAX_. 504 Type example: 506 TEL;TYPE=WORK;VOICE;PREF;MSG:+1-213-555-1234 508 1.6.2 EMAIL Type Definition 510 To: ietf-mime-direct@umich.edu 512 Subject: Registration of application/directory MIME type EMAIL 514 Dawson & Howes [Page 9] Expires June 1997 515 vCard Application/Directory Content Type 517 Type name: EMAIL 519 Type purpose: To specify the address for electronic mail 520 communication with the vCard object. The address is in the form of a 521 specific addressing type. The default is an Internet addressing type. 523 Type encoding: text. 525 Type special notes: . The type may include the type parameter _TYPE_ 526 to specify the addressing type of the electronic mail address. The 527 TYPE parameter values may include: _INTERNET_ to indicate an Internet 528 addressing type or _X400_ to indicate a X.400 addressing type. Other 529 type values are allowed, but are to be specified by individual 530 electronic mail service providers. The default email type is 531 _INTERNET_. 533 Type example: 535 EMAIL;Type=INTERNET:jqpublic@xyz.dom1.com 537 1.6.3 MAILER Type Definition 539 To: ietf-mime-direct@umich.edu 541 Subject: Registration of application/directory MIME type MAILER 543 Type name: MAILER 545 Type purpose: To specify the type of electronic mail software that is 546 used by the individual associated with the vCard object. 548 Type encoding: text. 550 Type special notes: This information may provide assistance to a 551 correspondent regarding the type of data representation which can be 552 used, and how they may be packaged. This property is based on the 553 private MIME type X-Mailer that is generally accepted within the MIME 554 user agent product offerings. 556 Type example: 558 MAILER:GypsyMail 2.1 560 1.7 Geographical Profile Types 562 These profile types are concerned with information associated with 563 geographical positions or regions associated with the vCard object. 565 1.7.1 TZ Type Definition 567 To: ietf-mime-direct@umich.edu 569 Subject: Registration of application/directory MIME type TZ 571 Dawson & Howes [Page 10] Expires June 1997 572 vCard Application/Directory Content Type 574 Type name: TZ 576 Type purpose: To specify information related to the time zone of the 577 vCard object. 579 Type encoding: text. 581 Type special notes: the type value is specified as a string as 582 specified in a manner consistent with [ISO 8601]. It is an offset 583 from Coordinated Universal Time (UTC). An ISO 8601 UTC offset, in 584 basic format, is specified as a positive or negative difference in 585 units of hours and minutes (e.g., +hhmm). If minutes are zero, then 586 they may be omitted and the format would be specified in units of 587 hours (e.g., +hh). The time is specified as a 24-hour clock. Hour 588 values are from 00 to 24, and minute values are from 00 to 59. Hour 589 and minutes are 2-digits with high order zeroes required to maintain 590 digit count. The extended format for ISO 8601 makes use of a colon 591 character as a separator of the hour and minute substrings. 593 Type example: 595 TZ:-0500 597 1.7.2 GEO Type Definition 599 To: ietf-mime-direct@umich.edu 601 Subject: Registration of application/directory MIME type GEO 603 Type name: GEO 605 Type purpose: To specify information related to the global 606 positioning of the vCard object. 608 Type encoding: text. 610 Type special notes: the type value is a structured string that 611 specifies a longitude and latitude. The latitude represents the 612 location north and south of the equator as a positive or negative 613 number, respectively. The longitude represents the location east and 614 west of the prime meridian as a positive or negative number, 615 respectively. The string components are separated by the SEMI-COLON 616 character (ASCII decimal 59). 618 Type example: 620 GEO:37.24;-17.87 622 1.8 Organizational Profile Types 624 These profile types are concerned with information associated with 625 characteristics of the organization or organizational units 626 associated with the vCard object. 628 Dawson & Howes [Page 11] Expires June 1997 629 vCard Application/Directory Content Type 631 1.8.1 TITLE Type Definition 633 To: ietf-mime-direct@umich.edu 635 Subject: Registration of application/directory MIME type TITLE 637 Type name: TITLE 639 Type purpose: To specify the job title, functional position or 640 function of the individual or resource associated with the vCard 641 object within an organization 643 Type encoding: text. 645 Type special notes: This type is based on the X.520 Title attribute. 647 The usual line-folding technique described in [MIME-DIR] can be used 648 to represent type values consisting of long lines of text. 650 The type may specify the type parameters CHARSET, to specify a 651 character set for the type value, and LANGUAGE, to specify a language 652 for the type value. These are further defined in [MIME-DIR]. 654 Type example: 656 TITLE:Director, Research and Development 658 1.8.2 ROLE Type Definition 660 To: ietf-mime-direct@umich.edu 662 Subject: Registration of application/directory MIME type ROLE 664 Type name: ROLE 666 Type purpose: To specify information concerning the role, occupation, 667 or business category of the vCard object within an organization. 669 Type encoding: text. 671 Type special notes: This type is based on the X.520 Business Category 672 explanatory attribute. This property is included as an organizational 673 type to avoid confusion with the semantics of the TITLE type and 674 incorrect usage of that type when the semantics of this type is 675 intended. 677 The type may specify the type parameters CHARSET, to specify a 678 character set for the type value, and LANGUAGE, to specify a language 679 for the type value. These are further defined in [MIME-DIR]. 681 Type example: 683 ROLE:Programmer 685 Dawson & Howes [Page 12] Expires June 1997 686 vCard Application/Directory Content Type 688 1.8.3 LOGO Type Definition 690 To: ietf-mime-direct@umich.edu 692 Subject: Registration of application/directory MIME type LOGO 694 Type name: LOGO 696 Type purpose: To specify a graphic image of the logo of the 697 organization that is associated with the individual or resource the 698 vCard belongs to. 700 Type encoding: text. 702 Type special notes: The type may include the type parameter _TYPE_ to 703 specify the format of the graphic image. The TYPE parameter values 704 may include _GIF_ to indicate the GIF format and _JPEG_ to indicate 705 the JPEG format. The type may also include the type parameter 706 _ENCODING_ to specify the content encoding applied to the graphic 707 image. The ENCODING parameter value may include _BASE64_ to indicate 708 the Base64 encoding or _QUOTED-PRINTABLE_ to indicate the quoted- 709 printable encoding. The type may also include the type parameter 710 _VALUE_ to specify the location of the type value. The VALUE 711 parameter values may include _INLINE_ to indicate that the graphic 712 image value is included within the content type value, _URL_ to 713 indicate the uniform resource locator for where the content for the 714 graphic image can be found in the network, and _CID_ to indicate the 715 content-id for the MIME entity that encapsulates the content for the 716 graphic image. 718 Type example: 720 LOGO;VALUE=URL:http://www.abc.com/pub/logos/abccorp.jpg 722 1.8.4 AGENT Type Definition 724 To: ietf-mime-direct@umich.edu 726 Subject: Registration of application/directory MIME type AGENT 728 Type name: AGENT 730 Type purpose: To specify information about another person who will 731 act on behalf of the individual or resource associate with the vCard 732 object. 734 Type encoding: text. 736 Type special notes: This type typically is used to specify an area 737 administrator, assistant, or secretary for the individual associated 738 with the vCard object. A key characteristic of the Agent type is that 739 it represents somebody or something that is separately addressable. 740 The value for this type is the content message identifier or Uniform 742 Dawson & Howes [Page 13] Expires June 1997 743 vCard Application/Directory Content Type 745 Resource Locator associated with the vCard defining the Agent 746 individual or resource. 748 The type may include the type parameter _VALUE_ to specify the 749 location of the type value. The VALUE parameter values may include 750 _CID_ to indicate the value specifies the content identifier for the 751 MIME entity containing the value or _URL_ to indicate the value 752 specifies the uniform resource locator for the value. The type 753 parameter may also include _INLINE_; however, this is not a 754 recommended practice as MIME user agents will not be expected to be 755 able to process vCard objects nested in this manner. Nested vCard 756 object will be expected to be mailed within a single message as 757 multiple MIME entities. The INLINE nesting of vCard object may have 758 some limited utility in where a monolithic data stream is required. 760 Type example: 762 AGENT;VALUE=CID: 763 765 1.8.5 ORG Type Definition 767 To: ietf-mime-direct@umich.edu 769 Subject: Registration of application/directory MIME type ORG 771 Type name: ORG 773 Type purpose: To specify the organizational name and units associated 774 with the vCard object. 776 Type encoding: text. 778 Type special notes: The type is based on the X.520 Organization Name 779 and Organization Unit attributes. The type value is a structured 780 string consisting of the organization name, followed by any 781 organizational units. The string components are separated the SEMI- 782 COLON character (ASCII decimal 59). 784 The type may specify the type parameters CHARSET, to specify a 785 character set for the type value, and LANGUAGE, to specify a language 786 for the type value. These are further defined in [MIME-DIR]. 788 Type example: 790 ORG:ABC, Inc.;North American Division;Marketing 792 1.9 Explanatory Profile Types 794 These profile types are concerned with additional explanations, such 795 as that related to informational notes or revisions specific to the 796 vCard object. 798 Dawson & Howes [Page 14] Expires June 1997 799 vCard Application/Directory Content Type 801 1.9.1 NOTE Type Definition 803 To: ietf-mime-direct@umich.edu 805 Subject: Registration of application/directory MIME type NOTE 807 Type name: NOTE 809 Type purpose: To specify supplemental information or a comment that 810 is associated with the vCard object. 812 Type encoding: text. 814 Type special notes: The type is based on the X.520 Description 815 attribute. 817 The type may specify the type parameters CHARSET, to specify a 818 character set for the type value, and LANGUAGE, to specify a language 819 for the type value. These are further defined in [MIME-DIR]. 821 Type example: 823 NOTE:This fax number is operational 0800 to 1715 824 EST, Mon-Fri. 826 1.9.2 REV Type Definition 828 To: ietf-mime-direct@umich.edu 830 Subject: Registration of application/directory MIME type REV 832 Type name: REV 834 Type purpose: To specify revision information about the current vCard 835 object. 837 Type encoding: text. 839 Type special notes: The type value is a calendar date and time of day 840 in a form conforming to ISO 8601 complete representation. The value 841 distinguishes the current revision of the information defining this 842 vCard object. 844 Type example: 846 REV:1995-10-31T22:27:10Z 848 1.9.3 SOUND Type Definition 850 To: ietf-mime-direct@umich.edu 852 Subject: Registration of application/directory MIME type SOUND 854 Type name: SOUND 856 Dawson & Howes [Page 15] Expires June 1997 857 vCard Application/Directory Content Type 859 Type purpose: To specify a digital sound content information that 860 annotates some aspect of the vCard object. By default this type is 861 used to specify the proper pronunciation of the name type value of 862 the vCard object. 864 Type encoding: text. 866 Type special notes: The type may include the type parameter _TYPE_ to 867 specify the format of the digital sound. The TYPE parameter values 868 may include _PCM_ to indicate the MIME basic audio content type and 869 _WAVE_ to indicate the Wave format. The type may also include the 870 type parameter _ENCODING_ to specify the content encoding applied to 871 the digital sound. The ENCODING parameter value may include _BASE64_ 872 to indicate the Base64 encoding. The type may also include the type 873 parameter _VALUE_ to specify the location of the type value. The 874 VALUE parameter values may include _INLINE_ to indicate that the 875 digital sound is included within the content type value, _URL_ to 876 indicate the uniform resource locator for where the content for the 877 digital sound can be found in the network, and _CID_ to indicate the 878 content-id for the MIME entity that encapsulates the content for the 879 digital sound. 881 Type example: 882 SOUND;TYPE=PCM;VALUE=CID: 885 1.9.4 URL Type Definition 887 To: ietf-mime-direct@umich.edu 889 Subject: Registration of application/directory MIME type URL 891 Type name: URL 893 Type purpose: To specify an Internet location that can be used to 894 obtain real-time or more complete information about the individual or 895 resource associate with the vCard object. 897 Type encoding: text. 899 Type special notes: An application of this type might be to specify 900 the location of a publicly accessible directory, such as an Internet 901 whitepages, where up-to-date information can be found about the 902 individual specified by a vCard. 904 Type example: 906 URL:http://www.swbyps.restaurant.french/~chezchic.html 908 1.9.5 UID Type Definition 910 To: ietf-mime-direct@umich.edu 912 Subject: Registration of application/directory MIME type UID 914 Dawson & Howes [Page 16] Expires June 1997 915 vCard Application/Directory Content Type 917 Type name: UID 919 Type purpose: To specify a value that represents a globally unique 920 identifier corresponding to the individual or resource associated 921 with the vCard object. 923 Type encoding: text. 925 Type special notes: The type value can be used as a mechanism to 926 relate different vCard objects. Some examples of valid forms of 927 unique identifiers would include ISO 9070 formal public identifiers 928 (FPI) as defined in [ISO 9070], X.500 distinguished names, machine- 929 generated random numbers with a statistically high likelihood of 930 being globally unique, and Uniform Resource Locators (URL). If an URL 931 is specified, it is suggested that the URL reference a service which 932 will produce an updated version of the vCard associated with the 933 individual or resource. 935 The type may include the type parameter _TYPE_ to specify the format 936 of the unique identifier. The TYPE parameter values may include 937 _ISO9070_ to indicate the ISO 9070 FPI type of unique identifier, 938 _X500_ to indicate the X.500 DSN type of unique identifier, _MACH_ to 939 indicate a machine generated random number type of unique identifier, 940 and _URL_ to indicate a Uniform Resource Locator type of unique 941 identifier. 943 Type example: 945 UID;TYPE=MACH:19950401-080045-40000F192713-0052 947 1.9.6 Version Type Definition 949 To: ietf-mime-direct@umich.edu 951 Subject: Registration of application/directory MIME type UID 953 Type name: UID 955 Type purpose: To specify a value that represents a globally unique 956 identifier corresponding to the individual or resource associated 957 with the vCard object. 959 Type encoding: text. 961 Type special notes: The type value can be used as a mechanism to 962 relate different vCard objects. Some examples of valid forms of 963 unique identifiers would include ISO 9070 formal public identifiers 964 (FPI) as defined in [ISO 9070], X.500 distinguished names, machine- 965 generated random numbers with a statistically high likelihood of 966 being globally unique, and Uniform Resource Locators (URL). If an URL 967 is specified, it is suggested that the URL reference a service which 968 will produce an updated version of the vCard associated with the 969 individual or resource. 971 Dawson & Howes [Page 17] Expires June 1997 972 vCard Application/Directory Content Type 974 The type may include the type parameter _TYPE_ to specify the format 975 of the unique identifier. The TYPE parameter values may include 976 _ISO9070_ to indicate the ISO 9070 FPI type of unique identifier, 977 _X500_ to indicate the X.500 DSN type of unique identifier, _MACH_ to 978 indicate a machine generated random number type of unique identifier, 979 and _URL_ to indicate a Uniform Resource Locator type of unique 980 identifier. 982 Type example: 984 UID;TYPE=MACH:19950401-080045-40000F192713-0052 986 1.10 Security Profile Types 988 These profile types are concerned with the security of communication 989 pathways or access to the vCard object. 991 1.10.1 KEY Type Definition 993 To: ietf-mime-direct@umich.edu 995 Subject: Registration of application/directory MIME type VERSION 997 Type name: VERSION 999 Type purpose: To specify an identifier corresponding to the highest 1000 version of the vCard profile used in creating the vCard object. 1002 Type encoding: text. 1004 Type special notes: The type value corresponding to this version of 1005 the vCard profile MUST be _2.1_. 1007 1.11 Extended Profile Types 1009 The profile types defined by this document can be extended with 1010 private types using the private type mechanism defined in [MIME]. 1011 Private types with a name starting with _X-_ may be defined 1012 bilaterally between two cooperating agents without outside 1013 registration or standardization. 1015 2. Formal Grammar 1017 The following modified Backus-Naur Notation (BNF) is provided to 1018 assist developers in building parsers for the vCard. 1020 This syntax is written according to the form described in RFC 822, 1021 but it references just this small subset of RFC 822 literals: 1023 CR = ; (15, 13.) 1024 LF = ; (12,10.) 1025 CRLF = CR LF 1026 SPACE = ; (40,32.) 1027 HTAB = ; (11,9.) 1029 Dawson & Howes [Page 18] Expires June 1997 1030 vCard Application/Directory Content Type 1032 All literal property names are valid as upper, lower, or mixed case. 1034 ws = 1*(SPACE / HTAB) 1035 ; _whitespace,_ one or more spaces or tabs 1037 wsls = 1*(SPACE / HTAB / CRLF) 1038 ; whitespace with line separators 1040 word = 1042 groups = groups _._ word 1043 / word 1045 vcard_entity = 1*([wsls] vcard [wsls]) 1047 vcard = _BEGIN_ [ws] _:_ [ws] _VCARD_ [ws] 1*CRLF 1048 items *CRLF 1049 _END_ [ws] _:_ [ws] _VCARD_ 1*CRLF 1051 items = items *CRLF item 1052 / item 1053 ; these may be _folded_ 1055 item = [groups _._] name 1056 [params] _:_ value CRLF 1057 / [groups _._] _ADR_ 1058 [params] _:_ addressparts CRLF 1059 / [groups _._] _ORG_ 1060 [params] _:_ orgparts CRLF 1061 / [groups _._] _N_ 1062 [params] _:_ nameparts CRLF 1063 / [groups _._] _AGENT_ 1064 [params] _:_ vcard CRLF 1065 ; these may be _folded_ 1067 name = _LOGO_ / _PHOTO_ / _LABEL_ / _FN_ / _TITLE_ 1068 / _SOUND_ / _VERSION_ / _TEL_ / _EMAIL_ / _TZ_ 1069 / _GEO_ / _NOTE_ 1070 / _URL_ / _BDAY_ / _ROLE_ / _REV_ / _UID_ / _KEY_ 1071 / _MAILER_ / _X-_ word 1072 ; these may be _folded_ 1074 value = 7bit / quoted-printable / base64 1076 7bit = <7bit us-ascii printable chars, excluding CR LF> 1078 8bit = 1080 quoted-printable = 1082 base64 = 1083 ; the end of the text is marked with two CRLF sequences 1084 ; this results in one blank line before the start of the next 1085 ; property 1087 Dawson & Howes [Page 19] Expires June 1997 1088 vCard Application/Directory Content Type 1090 params = _;_ [ws] paramlist 1092 paramlist = paramlist [ws] _;_ [ws] param 1093 / param 1095 param = _TYPE_ [ws] _=_ [ws] ptypeval 1096 / _VALUE_ [ws] _=_ [ws] pvalueval 1097 / _ENCODING_ [ws] _=_ [ws] pencodingval 1098 / _CHARSET_ [ws] _=_ [ws] charsetval 1099 / _LANGUAGE_ [ws] _=_ [ws] langval 1100 / _X-_ word [ws] _=_ [ws] word 1101 / knowntype 1103 ptypeval = knowntype / _X-_ word 1105 pvalueval = _INLINE_ / _URL_ / _CONTENT-ID_ / _CID_ / _X-_ word 1107 pencodingval = _7BIT_ / 8BIT 1108 _ _ / _QUOTED-PRINTABLE_ / _BASE64_ 1109 / _X-_ word 1111 charsetval = 1114 langval = 1116 addressparts = 0*6(strnosemi _;_) strnosemi 1117 ; PO Box, Extended Addr, Street, Locality, Region, Postal Code, 1118 ; Country Name 1120 orgparts = *(strnosemi _;_) strnosemi 1121 ; First is Organization Name, remainder are Organization Units. 1123 nameparts = 0*4(strnosemi _;_) strnosemi 1124 ; Family, Given, Middle, Prefix, Suffix. 1125 ; Example:Public;John;Q.;Reverend Dr.;III, Esq. 1127 strnosemi = *(*nonsemi (_\;_ / _\_ CRLF)) *nonsemi 1128 ; To include a semicolon in this string, it must be escaped 1129 ; with a _\_ character. 1131 nonsemi = 1133 knowntype = _DOM_ / _INTL_ / _POSTAL_ / _PARCEL_ / _HOME_ / _WORK_ 1134 / _PREF_ / _VOICE_ / _FAX_ / _MSG_ / _CELL_ / _PAGER_ 1135 / _BBS_ / _MODEM_ / _CAR_ / _ISDN_ / _VIDEO_ 1136 / _INTERNET_ / _GIF_ / _JPEG_ / _PCM_ / _WAVE_ 1137 / _X509_ / _PGP_ 1139 2.1 Acknowledgements 1141 The authors would like to thank the participants in the IETF ASID 1142 working group, in addition to the following individuals, Roland 1143 Alden, Stephen Bartlett, Daniel Klaussen, Michelle Watkins; who 1144 provided numerous suggestions and comments on this work. 1146 Dawson & Howes [Page 20] Expires June 1997 1147 vCard Application/Directory Content Type 1149 2.2 Authors's Addresses 1151 BEGIN:vCard 1152 FN:Frank Dawson 1153 ORG:IBM Corporation;Network Software Division 1154 ADR;TYPE=WORK,POSTAL,PARCEL:APNA/CC-303/Bldg. 002; 1155 3039 Cornwallis Rd.;Research Triangle Park; 1156 NC;27709;U.S.A. 1157 TEL;TYPE=VOICE,MSG,WORK: +1 (919) 254-5861 1158 TEL;TYPE=FAX,WORK: +1-919-543-6822 1159 EMAIL;TYPE=INTERNET;PREF:fdawson@raleigh.ibm.com 1160 EMAIL;TYPE=INTERNET:fdawson@earthlink.net 1161 URL:http://home.earthlink.net/~fdawson 1162 END:vCard 1164 BEGIN:vCard 1165 FN:Tim Howes 1166 ORG:Netscape Communications Corp. 1167 ADR;TYPE=WORK: 501 E. Middlefield Rd.;Mountain View; 1168 CA; 94043;U.S.A. 1169 TEL;TYPE=VOICE,MSG,WORK:+1-415-937-3419 1170 EMAIL;TYPE=INTERNET:howes@netscape.com 1171 END:vCard 1173 2.3 References 1175 The following documents are referenced by this work. 1177 [ISO 639] ISO 639:1988 - Code for the representation of names of 1178 languages - The International Organization for Standardization, April 1179 1988. 1181 [ISO 3166] ISO 3166:1993 - Codes for the representation of names of 1182 countries - The International Organization for Standardization, 1183 December 1993. 1185 [ISO 8601] ISO 8601:1988 - Data elements and interchange formats - 1186 Information interchange - Representation of dates and times - The 1187 International Organization for Standardization, June, 1988. 1189 [ISO 8601 TC] ISO 8601, Technical Corrigendum 1 - Data elements and 1190 interchange formats - Information interchange - Representation of 1191 dates and times - The International Organization for Standardization, 1192 May, 1991. 1194 [ISO 9070] ISO 9070, Information Processing - SGML support facilities 1195 - Registration Procedures for Public Text Owner Identifiers, April, 1196 1991. 1198 [CCITT E.163] Recommendation E.163 - Numbering Plan for The 1199 International Telephone Service, CCITT Blue Book, Fascicle II.2, pp. 1200 128-134, November, 1988. 1202 Dawson & Howes [Page 21] Expires June 1997 1203 vCard Application/Directory Content Type 1205 [CCITT X.121] Recommendation X.121 - International Numbering Plan for 1206 Public Data Networks, CCITT Blue Book, Fascicle VIII.3, pp. 317-332, 1207 November, 1988. 1209 [CCITT X.520] Recommendation X.520 - The Directory - Selected 1210 Attribute Types, November 1988. 1212 [CCITT X.521] Recommendation X.521 - The Directory - Selected Object 1213 Classes, November 1988. 1215 [MIME-DIR] Howes, T., Smith, M., _A MIME Content-Type for Directory 1216 Information_, Internet-draft-ietf-asid-mime-direct-03.txt, November, 1217 1996. 1219 [MIME-REG] Freed, N., Postel, J., _Multipurpose Internet Mail 1220 Extensions (MIME) Part Four: Registration Procedures,_ Internet- 1221 Draft draft-ietf-822ext-mime-reg-02.txt, December 1995. 1223 [RFC-822] Crocker, D., _Standard for the Format of ARPA Internet Text 1224 Messages_, STD 11, RFC 822, August 1982. 1226 [RFC-1521] Borenstein, N., Freed, N., _MIME (Multipurpose Internet 1227 Mail Extensions) Part One: Mechanisms for Specifying and Describing 1228 the Format of Internet Message Bodies_, RFC 1521, September 1993. 1230 [RFC-1522] Moore, K., _MIME (Multipurpose Internet Mail Extensions) 1231 Part Two: Message Header Extensions for Non-ASCII Text_, RFC 1522, 1232 September 1993. 1234 [RFC-1738] Berners-Lee, T., Masinter, L., McCahill, M., _Uniform 1235 Resource Locators (URL)_, RFC 1738, December 1994. 1237 [RFC-1766] Alvestrand, H., _Tags for the Identification of 1238 Languages_, March 1995. 1240 [RFC-1872] Levinson, E., _The MIME Multipart/Related Content-type,_ 1241 RFC 1872, December 1995. 1243 [VCARD] VERSIT Consortium, _vCard - The Electronic Business Card 1244 Version 2.1_, http://www.versit.com/pdi, September 18, 1996. 1246 Dawson & Howes [Page 22] Expires June 1997