idnits 2.17.1 draft-ietf-acap-abook-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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.) ** There are 6 instances of too long lines in the document, the longest one being 6 characters in excess of 72. ** The abstract seems to contain references ([ACAP], [IMAP4]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 121: '...cal addressbooks SHOULD be represented...' RFC 2119 keyword, line 128: '...owing attributes MAY be used in an ACA...' RFC 2119 keyword, line 129: '...ddressbook entry MUST have an "entry" ...' RFC 2119 keyword, line 135: '...ddressbook entry MUST have at most one...' RFC 2119 keyword, line 142: '...ence" attributes MUST be ignored. If t...' (14 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 515 has weird spacing: '...Address paf...' == Line 525 has weird spacing: '...Address gra...' == Line 533 has weird spacing: '...Address paf...' == Line 545 has weird spacing: '...Address paf...' == Line 551 has weird spacing: '...Address gra...' == (1 more instance...) -- 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 1997) is 9652 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? 'IMAP4' on line 621 looks like a reference -- Missing reference section? 'ACAP' on line 607 looks like a reference -- Missing reference section? 'KEYWORDS' on line 626 looks like a reference -- Missing reference section? 'ABNF' on line 601 looks like a reference -- Missing reference section? 'UTF8' on line 657 looks like a reference -- Missing reference section? 'WHITE-SCHEMA' on line 665 looks like a reference -- Missing reference section? 'VCARD' on line 662 looks like a reference -- Missing reference section? 'IMAIL' on line 616 looks like a reference -- Missing reference section? 'MIME-HDRS' on line 247 looks like a reference -- Missing reference section? 'REL-URL' on line 647 looks like a reference -- Missing reference section? 'SMTP' on line 652 looks like a reference -- Missing reference section? 'MBOX-NAMES' on line 636 looks like a reference -- Missing reference section? 'MIME-TYPES' on line 361 looks like a reference -- Missing reference section? 'BASIC-URL' on line 610 looks like a reference -- Missing reference section? 'LANG-TAGS' on line 631 looks like a reference -- Missing reference section? 'PGP-FMT' on line 641 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 8 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Newman 3 Internet Draft: ACAP Addressbook Dataset Class Innosoft 4 Document: draft-ietf-acap-abook-01.txt S. Hubert 5 University of Washington 6 November 1997 7 Expires in six months 9 ACAP Personal Addressbook Dataset Class 11 Status of this memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet-Drafts 21 as reference material or to cite them other than as "work in 22 progress." 24 To view the entire list of current Internet-Drafts, please check 25 the "1id-abstracts.txt" listing contained in the Internet-Drafts 26 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 27 (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East 28 Coast), or ftp.isi.edu (US West Coast). 30 Copyright Notice 32 Copyright (C) The Internet Society 1997. All Rights Reserved. 34 Abstract 36 IMAP [IMAP4] allows nomadic users to access their mailstore from 37 any client, but it does not support storage of personal 38 addressbooks. Application Configuration Access Protocol [ACAP] 39 provides an ideal mechanism for storage of personal addressbooks. 40 While ACAP permits the definition of vendor specific solutions to 41 this problem, having a standard addressbook dataset class permits 42 clients from different vendors to interoperably share the same 43 personal addressbooks. This specification defines a standard 44 dataset class for personal addressbooks. 46 Table of Contents 48 Status of this memo ............................................... i 49 Copyright Notice .................................................. i 50 Abstract .......................................................... i 51 1. Conventions Used in this Document ............................ 1 52 2. Design Issues ................................................ 1 53 3. ACAP Personal Addressbooks ................................... 1 54 3.1. ACAP Addressbook Dataset Class ............................... 1 55 3.2. ACAP Addressbook Capability .................................. 1 56 3.3. ACAP Addressbook Hierarchy ................................... 1 57 3. Recommended ACAP Attributes .................................. 2 58 3.1. Basic Attributes ............................................. 2 59 4.2. Naming Attributes ............................................ 3 60 4.3. Reference Attribute .......................................... 4 61 4.4. Computer Communication Attributes ............................ 5 62 4.5. Telephone Number Attributes .................................. 7 63 4.6. Postal Address Attributes .................................... 8 64 4.7. Commentary Attributes ........................................ 8 65 4.8. Locational Attributes ........................................ 9 66 4.9. PGP Public Keys .............................................. 9 67 5. Examples ..................................................... 10 68 6. Mapping vCards to ACAP addressbooks .......................... 11 69 6.1. Name Attributes .............................................. 11 70 6.2. Telephone Attributes ......................................... 12 71 6.3. Other Attributes ............................................. 12 72 7. References ................................................... 12 73 8. Security Considerations ...................................... 13 74 9. Full Copyright ............................................... 14 75 10. Authors' Addresses ........................................... 14 76 Appendix .......................................................... 15 77 A. Attribute Index .............................................. 15 78 1. Conventions Used in this Document 80 The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" 81 in this document are to be interpreted as defined in "Key words for 82 use in RFCs to Indicate Requirement Levels" [KEYWORDS]. 84 The attribute syntax specifications use the Augmented Backus-Naur 85 Form (ABNF) notation as specified in [ABNF]. 87 When UTF-8 [UTF8] is referred to in this document, it refers to 88 Unicode version 2.0, and not Unicode version 1.1. 90 2. Design Issues 92 Although this is not a white pages service, in order to provide 93 more consistancy, this was designed to match the Common Schema for 94 Internet White Pages [WHITE-SCHEMA]. It was also designed to 95 minimize email client complexity, provide a clean model for 96 personal distribution lists and hierarchical addressbooks and 97 permit storage of vCards [VCARD] for correspondants. 99 Personal addressbooks differ from white pages services because all 100 the attributes and entries are controlled by the user who owns the 101 addressbook rather than a directory administrator. The user or the 102 clients he uses may add new attributes at any time and some of 103 these attributes are not suitable for a white pages service. 105 3. ACAP Personal Addressbooks 107 3.1. ACAP Addressbook Dataset Class 109 Datasets whose names begin with "/addressbook" are assumed to 110 contain addressbook entries as defined in this specification. 112 3.2. ACAP Addressbook Capability 114 The "addressbook.Expand.Address" and "addressbook.Expand.Complete" 115 attributes require active client or server support. The attribute 116 "capability.addressbook.expand" in the "/capability/~/addressbook" 117 entry is non-NIL if they are supported. 119 3.3. ACAP Addressbook Hierarchy 121 Hierarchical addressbooks SHOULD be represented using ACAP 122 hierarchy. Any entry in an addressbook can also be a hierarchy 123 node by setting the "subdataset" attribute. This structure is used 124 to represent both sub-addressbooks and mailing lists. 126 3. Recommended ACAP Attributes 128 The following attributes MAY be used in an ACAP addressbook entry. 129 An addressbook entry MUST have an "entry" attribute, and one or 130 more of "addressbook.Alias", "addressbook.CommonName" and 131 "addressbook.Email" attributes. The purpose of this rule is to 132 make it possible to easily select an attribute which can be 133 displayed to a user. 135 An addressbook entry MUST have at most one of the attributes 136 "addressbook.List", "addressbook.Reference", and 137 "addressbook.Email". The purpose of this rule is to force each 138 entry to be either a regular addressbook entry with an Email 139 address, a pointer to another addressbook entry, or a distribution 140 list. In order to resolve ambiguities, if there is an 141 "addressbook.List" attribute, both "addressbook.Email" and 142 "addressbook.Reference" attributes MUST be ignored. If there is no 143 "addressbook.List" attribute but there is an "addressbook.Email" 144 attribute, then the "addressbook.Reference" attribute MUST be 145 ignored. Beyond these rule, clients MAY choose any subset of these 146 attributes as well as using registered private attributes. Clients 147 are encouraged to provide a way to view all textual attributes in 148 an entry regardless of whether the client knows the special 149 semantics associated with them. 151 The ABNF defines the content of the attribute values prior to their 152 encoding as an ACAP string. Clients MUST conform to the syntax 153 when generating these attributes, but MUST NOT assume that the 154 attribute values will conform to this syntax on access. Servers 155 MUST NOT enforce the syntax. 157 Unless otherwise stated, all attributes in this specification are 158 single-valued and textual. 160 3.1. Basic Attributes 162 These attributes are defined in ACAP [ACAP] and have meaning in all 163 dataset classes. This section describes how they are used in an 164 addressbook dataset. 166 entry 167 The "entry" attribute is a unique string used to refer to an 168 addressbook entry within an addressbook dataset. It is client 169 defined and may not be suitable for display to users. 171 subdataset 172 The "subdataset" attribute is used both for addressbook 173 hierarchy and for addressbook distribution lists. It 174 indicates there is another addressbook dataset underneath this 175 entry. If there is also an "addressbook.List" attribute, then 176 this entry is an email distribution list and the subdataset 177 contains the members of that list. If "subdataset" exists, 178 then any "addressbook.Email" or "addressbook.Reference" 179 attributes SHOULD be ignored. 181 4.2. Naming Attributes 183 These attributes contain information about the name of the person 184 or entity to which the entry refers. 186 addressbook.CommonName 187 The "addressbook.CommonName" attribute holds the full common 188 name of the person or entity to which the addressbook entry 189 refers. If a person has multiple names, they may be stored in 190 the "addressbook.AlternateNames" attribute. 192 abook-common-name = 1*TEXT-UTF8-CHAR 194 addressbook.GivenName 195 The "addressbook.GivenName" attribute holds the given name of 196 the person to which the addressbook entry refers. 198 abook-given-name = 1*TEXT-UTF8-CHAR 200 addressbook.Surname 201 The "addressbook.Surname" attribute holds the surname (or 202 family name) of the person to which the addressbook entry 203 refers. 205 abook-surname = 1*TEXT-UTF8-CHAR 207 addressbook.MiddleName 208 This holds the middle name(s) or initial(s) of the person to 209 which the addressbook entry refers. 211 abook-middle = 1*TEXT-UTF8-CHAR 213 addressbook.Prefix 214 This holds any prefixes (e.g., "Mr.", "Mrs.") for the person 215 to which the addressbook entry refers. 217 abook-prefix = 1*TEXT-UTF8-CHAR 219 addressbook.Suffix 220 This holds any suffixes (e.g., "Jr.", "M.D.") for the person 221 to which the addressbook entry refers. 223 abook-suffix = 1*TEXT-UTF8-CHAR 225 addressbook.AlternateNames 226 This is a multi-value attribute containing a list of alternate 227 names for the entry. 229 abook-alt-name = 1*TEXT-UTF8-CHAR 230 ;; multi-valued 232 addressbook.Alias 233 A shorthand way to refer to this entry (e.g. a nickname). 234 Clients MUST NOT store characters which fall into the class of 235 "white-space" or "specials" as defined in Internet Message 236 Format [IMAIL] with the exception of period ("."). The alias 237 is typically used by clients as as a way for users to quickly 238 refer to a particular addressbook entry via a type-in field. 239 For this to work best, clients are encouraged to avoid using 240 the same alias in multiple entries within a dataset. 242 abook-alias = 1*<"." or any TEXT-UTF8-CHAR except 243 white-space or specials as defined in [IMAIL]> 245 addressbook.CommonName.MIME 246 This contains the CommonName encoded as a US-ASCII string 247 according to the rules in MIME Headers [MIME-HDRS]. This is 248 set when a personal addressbook entry is created from an 249 Internet Mail Address [IMAIL] which uses MIME Header encoding 250 for the common name portion of the address. This is the 251 preferred attribute to use for the phrase portion of the 252 Internet Mail Address as it preserves the sender's preferred 253 character set. Otherwise, the phrase is constructed from the 254 "addressbook.CommonName" field with all non US-ASCII 255 characters encoded according to MIME headers using UTF-8. 256 This attribute SHOULD be NIL if the CommonName is made up of 257 only US-ASCII characters or the sender's preferred character 258 set is UTF-8. 260 abook-mime-hdr = phrase 261 ;; as defined in [IMAIL] 263 4.3. Reference Attribute 264 addressbook.Reference 265 This addressbook entry is a reference to another ACAP 266 addressbook entry, or an LDAP white pages entry. The 267 reference is in the form of a relative URL. Clients SHOULD 268 support this attribute for the local ACAP server and MAY 269 support it for other ACAP or LDAP servers. 271 abook-reference = relativeURL 272 ;; as defined in [REL-URL] 273 ;; ACAP relative URL is defined in [ACAP] 275 4.4. Computer Communication Attributes 277 These attributes are related to computer communication. The format 278 for email addresses MUST be canonicalized so it is suitable for use 279 in both [IMAIL] and [SMTP]. This restricts the format for an 280 addr-spec as follows. This uses terminals from [IMAIL], except 281 that free insertion of linear-white-space is not permitted. 283 canon-addr-spec = canon-local-part "@" domain 285 canon-local-part = quoted-string / (atom *("." atom)) 287 addressbook.Email 288 The primary email address for contacting this entry. 289 Alternate email addresses may be indicated by appending an 290 appropriate qualifer to the end of the attribute name, such as 291 ".work" for a work-related email address, ".personal" for a 292 personal email address, or ".alt" for a multi-valued list of 293 alternate email addresses of equal weight. 295 abook-email = canon-addr-spec 297 addressbook.List 298 If both this attribute and the "subdataset" attribute exist 299 then this entry is an email distribution list. The entries in 300 the subdataset are the members of the list. When this 301 attribute exists, then any "addressbook.Email" or 302 "addressbook.Reference" attributes should be ignored. If this 303 attribute exists but no "subdataset" attribute exists, then 304 this attribute should be ignored. 306 abook-list = "1" 308 addressbook.Expand.Address 309 This is an operational attribute which is present if the ACAP 310 server announces the ADDRESSBOOK capability. It's value is 311 computed by the ACAP server. The result is a CRLF-separated 312 list of all the addr-spec from the addressbook.Email 313 attributes of this entry, any entry referred to by 314 "addressbook.Reference" on the local server, and any entries 315 contained in the "subdataset" on this server. This expansion 316 is recursive. 318 abook-expand-addr = canon-addr-spec *(CRLF canon-addr-spec) 320 addressbook.Expand.Complete 321 This is an operational attribute which is present if the ACAP 322 server announces the ADDRESSBOOK capability. It's value is 323 computed by the ACAP server. The result is a CRLF-separated 324 list of all the Internet Mail Addresses as computed from the 325 addressbook.Email, addressbook.CommonName, and 326 addressbook.CommonName.MIME attributes. The entry itself, any 327 entry referred to by "addressbook.Reference" on the local 328 server, and any entries contained in the "subdataset" on the 329 local server are expanded. This expansion is recursive. 331 abook-expand-compl = mailbox *(CRLF mailbox) 332 ;; mailbox defined in [IMAIL] without folding 334 addressbook.RequestAddress 335 If the entry refers to a mailing list address rather than a 336 person, then this attribute may be used to store the address 337 used to subscribe or unsubscribe from the mailing list. If 338 not present, clients should default the value to the standard 339 request address defined in [MBOX-NAMES]. 341 abook-request = canon-addr-spec 343 addressbook.Subscribed 344 If this attribute is non-NIL, then the entry refers to a 345 mailing list address to which the addressbook's owner is 346 currently subscribed. 348 abook-subscribed = "1" 350 addressbook.PreferredTextFormat 351 This attribute contains the media type and parameters for the 352 preferred text format of for the mailbox referred to by the 353 "addressbook.Email" attribute. The syntax does not permit 354 free insertion of linear white space as defined in [IMAIL]. 355 Values can include "text/enriched", "text/html", "text/plain", 356 "multipart/alternative". There is no defined default value, 357 although clients should be aware that the only format all 358 recipients support is "text/plain; charset=us-ascii". 360 abook-text-format = type "/" subtype *(";" SPACE parameter) 361 ;; as defined in [MIME-TYPES] 363 addressbook.HomePage 364 This contains the URL [BASIC-URL] to the home page describing 365 the person or entity to which the addressbook entry refers. 367 abook-home-page = url 368 ;; as defined in [BASIC-URL] 370 4.5. Telephone Number Attributes 372 Fully qualified international form is preferred for telephone 373 numbers 374 +1 555 555 1234 ext 54 375 but as these are likely to be human-entered any form is permitted. 377 The character "$" is reserved as a separator and is used to 378 describe the function of the telephone number. The following 379 functions are initialially defined: 381 home This is a residence phone number 382 work This is an office phone number 383 msg This number has voice messaging support 384 cell This is a cellular telephone number 385 voice This number is a voice number 386 fax This number has fax support 387 modem This number has modem support 388 pager This is a pager number 390 Thus a number such as: 392 +1 555 555 1234 ext 54$office$voice$msg 394 Indicates an office voice phone with voice messaging. Additional 395 functions MAY be used as long as they match the functions defined 396 in vCard [VCARD]. 398 The formal syntax is as follows: 400 abook-phone = 1* 401 *("$" abook-use-attribute) 403 abook-use-attribute = "home" / "work" / "msg" / "cell" / "voice" / 404 "fax" / "modem" / "pager" / abook-use-ext 406 abook-use-ext = 1*ATOM-CHAR 407 ;; as defined by vCard [VCARD] 409 addressbook.TelephonePrimary 410 This is the primary telephone number for the person referred 411 to by the entry. 413 addressbook.TelephoneOther 414 This multi-valued attribute may hold additional telephone 415 numbers. 417 4.6. Postal Address Attributes 419 Postal addresses should be in the same format that they appear on 420 an envelope, preferably fully qualified. The multiple lines are 421 CRLF separated within the attribute. 423 addressbook.Postal 424 This contains the preferred postal address for the person or 425 entity referred to by the entry. A suffix such as ".work" or 426 ".home" can be added to indicate alternate addresses. 428 abook-postal = 1*TEXT-UTF8-CHAR *(CRLF *TEXT-UTF8-CHAR) 430 4.7. Commentary Attributes 432 These are free-form text attributes used to store commentary about 433 the entry. 435 addressbook.Comment 436 This is a freeform comment field where the owner of the 437 addressbook may put comments about the person or entity 438 referred to by the entry. 440 abook-comment = 1*UTF8-CHAR 442 addressbook.Description 443 This is a freeform comment field for a self-description of the 444 person or entity referred to by the entry. It is primarily 445 used when an entry is imported from a remote directory. 447 abook-description = 1*UTF8-CHAR 449 4.8. Locational Attributes 451 These contain information about the location of the person or 452 entity referred to by this entry. 454 addressbook.Organization 455 This is the name of the organization with which the person or 456 entity is associated. 458 abook-organization = 1*TEXT-UTF8-CHAR 460 addressbook.Title 461 This is the title of the person referred to by the entry. 463 abook-title = 1*TEXT-UTF8-CHAR 465 addressbook.Locality 466 This is the name of the locality where the person or entity is 467 normally located. 469 abook-locality = 1*TEXT-UTF8-CHAR 471 addressbook.Country 472 This is the ISO 3166 country code where the person or entity 473 is normally located. 475 abook-country = 2*3ALPHA 477 addressbook.LanguageSpoken 478 This is the language code [LANG-TAGS] for the language which 479 the person or entity prefers to speak. 481 abook-language = Language-Tag 482 ;; as defined in [LANG-TAGS] 484 4.9. PGP Public Keys 486 The PGP public key for a correspondant MAY be included in the 487 addressbook entry. Note that a field is not defined at this time 488 for X.509 public keys as their trust structure makes them more 489 suitable in a global directory rather than a personal 490 configuration. 492 addressbook.PGP.bin 493 This holds the binary form of a PGP public key for the person 494 or entity referred to by the addressbook entry. The format is 495 as documented in [PGP-FMT]. Clients MUST check the version 496 number field to permit future versions. 498 abook-pgp = *OCTET 499 ;; as defined in [PGP-FMT] 501 5. Examples 503 Some sample entries: 505 In addressbook /addressbook/user/hubert 507 attribute name value 508 -------------- ----- 509 entry ABC123 510 addressbook.CommonName Patrik Faltstrom 511 addressbook.GivenName Patrik 512 addressbook.Surname Faltstrom 513 addressbook.Email paf@swip.net 514 addressbook.CommonName.MIME =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= 515 addressbook.Expand.Address paf@swip.net 516 addressbook.Expand.Complete 517 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= 519 entry ABC567 520 addressbook.CommonName Terry Gray 521 addressbook.GivenName Terry 522 addressbook.Surname Gray 523 addressbook.Alias teg 524 addressbook.Email gray@cac.washington.edu 525 addressbook.Expand.Address gray@cac.washington.edu 526 addressbook.Expand.Complete Terry Gray 528 entry defghi 529 subdataset . 530 addressbook.List "1" 531 addressbook.CommonName List of Two 532 addressbook.CommonName.MIME List of Two 533 addressbook.Expand.Address paf@swip.net 534 gray@cac.washington.edu 535 fred@bedrock.com 536 addressbook.Expand.Complete 537 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= 538 Terry Gray 539 Fred Flintstone 541 In dataset /addressbook/user/hubert/defghi 543 entry xyz1 544 addressbook.Reference ../ABC123 545 addressbook.Expand.Address paf@swip.net 546 addressbook.Expand.Complete 547 =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= 549 entry xyz2 550 addressbook.Reference ../ABC567 551 addressbook.Expand.Address gray@cac.washington.edu 552 addressbook.Expand.Complete Terry Gray 554 entry z2t 555 addressbook.CommonName Fred Flintstone 556 addressbook.GivenName Fred 557 addressbook.Surname Flintstone 558 addressbook.Email fred@bedrock.com 559 addressbook.CommonName.MIME Fred Flintstone 560 addressbook.Expand.Address fred@bedrock.com 561 addressbook.Expand.Complete Fred Flintstone 563 6. Mapping vCards to ACAP addressbooks 565 An ACAP addressbook is a perfect place to store vCards [VCARD]. It 566 provides access to business cards of your contacts from any machine 567 you use regularly, complete with the ability to annotate the 568 contact information. This section describes a preliminary mapping 569 from vCards. All vCard attributes which do not have equivalents in 570 this specification can be mapped directly to an 571 "addressbook." entry where is the attribute name of 572 the vCard attribute converted to all lower case. 574 All vCard encodings are removed and vCard newlines are replaced 575 with CRLF octet sequences when converting values. 577 6.1. Name Attributes 579 The vCard attribute "FN" maps to "addressbook.CommonName". The 580 vCard attribute "N" is divided and saved in "addressbook.Surname", 581 "addressbook.GivenName", "addressbook.MiddleName", 582 "addressbook.Prefix" and "addressbook.Suffix". This division 583 permits more sophisticated searching. 585 6.2. Telephone Attributes 587 The vCard "TEL" attribute is mapped to 588 "addressbook.TelephonePrimary" if the "pref" type is specified or 589 there is only one, and "addressbook.TelephoneOther" otherwise. 590 Other TYPE property parameters are encoded after a "$" at the end 591 of the value of the telephone number as specified above to simplify 592 searching. 594 6.3. Other Attributes 596 Other attributes are mapped directly and other property parameters 597 may be encoded in the attribute name if appropriate. 599 7. References 601 [ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications: 602 ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd, 603 November 1997. 605 607 [ACAP] Newman, Myers, "ACAP -- Application Configuration Access 608 Protocol", work in progress, June 1997. 610 [BASIC-URL] Berners-Lee, Masinter, McCahill, "Uniform Resource 611 Locators (URL)", RFC 1738, CERN, Xerox Coproration, University of 612 Minnesota, December 1994. 614 616 [IMAIL] Crocker, "Standard for the Format of ARPA Internet Text 617 Messages", STD 11, RFC 822, University of Delaware, August 1982. 619 621 [IMAP4] Crispin, "Internet Message Access Protocol - Version 622 4rev1", RFC 2060, University of Washington, December 1996. 624 626 [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate 627 Requirement Levels", RFC 2119, Harvard University, March 1997. 629 631 [LANG-TAGS] Alvestrand, H., "Tags for the Identification of 632 Languages", RFC 1766. 634 636 [MBOX-NAMES] Crocker, D., "Mailbox Names for Common Services, Roles 637 and Functions", RFC 2142, Internet Mail Consortium, May 1997. 639 641 [PGP-FMT] Atkins, Stallings, Zimmermann, "PGP Message Exchange 642 Formats", RFC 1991, MIT, Comp-Comm Consulting, Boulder Software 643 Engineering, August 1996. 645 647 [REL-URL] Fielding, "Relative Uniform Resource Locators", RFC 1808, 648 UC Irvine, June 1995. 650 652 [SMTP] Postel, "Simple Mail Transfer Protocol", RFC 821, 653 Information Sciences Institute, August 1982. 655 657 [UTF8] Yergeau, "UTF-8, a transformation format of Unicode and ISO 658 10646", RFC 2044, Alis Technologies, October 1996. 660 662 [VCARD] Dawson, Howes, "vCard MIME Directory Profile", Lotus, 663 Netscape Communications, Work in Progress. 665 [WHITE-SCHEMA] Genovese, Jennings, "A Common Schema for the 666 Internet White Pages Service", RFC 2218, Microsoft, Sandia National 667 Laboratory, October 1997. 669 671 8. Security Considerations 673 It is important to make sure that access controls are set correctly 674 on personal addressbooks. One should be careful of sharing 675 information which might contain personal comments. 677 If PGP public keys are stored in a personal addressbook it would be 678 wise to use an ACAP protocol security layer which provides at least 679 integrity protection. 681 9. Full Copyright 683 Copyright (C) The Internet Society 1997. All Rights Reserved. 685 This document and translations of it may be copied and furnished to 686 others, and derivative works that comment on or otherwise explain 687 it or assist in its implmentation may be prepared, copied, 688 published and distributed, in whole or in part, without restriction 689 of any kind, provided that the above copyright notice and this 690 paragraph are included on all such copies and derivative works. 691 However, this document itself may not be modified in any way, such 692 as by removing the copyright notice or references to the Internet 693 Society or other Internet organizations, except as needed for the 694 purpose of developing Internet standards in which case the 695 procedures for copyrights defined in the Internet Standards process 696 must be followed, or as required to translate it into languages 697 other than English. 699 The limited permissions granted above are perpetual and will not be 700 revoked by the Internet Society or its successors or assigns. 702 This document and the information contained herein is provided on 703 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 704 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 705 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 706 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 707 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 709 10. Authors' Addresses 711 Chris Newman 712 Innosoft International, Inc. 713 1050 Lakes Drive 714 West Covina, CA 91790 USA 716 Email: chris.newman@innosoft.com 718 Steve Hubert 719 Networks and Distributed Computing 720 University of Washington 721 4545 15th Ave. NorthEast 722 Seattle, WA 98105-4527 USA 724 Email: hubert@cac.washington.edu 726 Appendix 728 A. Attribute Index 730 addressbook.Alias .......................................... 4 731 addressbook.AlternateNames ................................. 4 732 addressbook.Comment ........................................ 8 733 addressbook.CommonName ..................................... 3 734 addressbook.CommonName.MIME ................................ 4 735 addressbook.Country ........................................ 9 736 addressbook.Description .................................... 9 737 addressbook.Email .......................................... 5 738 addressbook.Expand.Address ................................. 6 739 addressbook.Expand.Complete ................................ 6 740 addressbook.GivenName ...................................... 3 741 addressbook.HomePage ....................................... 7 742 addressbook.LanguageSpoken ................................. 9 743 addressbook.List ........................................... 5 744 addressbook.Locality ....................................... 9 745 addressbook.MiddleName ..................................... 3 746 addressbook.Organization ................................... 9 747 addressbook.PGP.bin ........................................ 10 748 addressbook.Postal ......................................... 8 749 addressbook.PreferredTextFormat ............................ 7 750 addressbook.Prefix ......................................... 3 751 addressbook.Reference ...................................... 5 752 addressbook.RequestAddress ................................. 6 753 addressbook.Subscribed ..................................... 6 754 addressbook.Suffix ......................................... 3 755 addressbook.Surname ........................................ 3 756 addressbook.TelephoneOther ................................. 8 757 addressbook.TelephonePrimary ............................... 8 758 addressbook.Title .......................................... 9 759 entry ...................................................... 2 760 subdataset ................................................. 2