idnits 2.17.1 draft-ietf-vpim-address-03.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 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. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (June 28, 2002) is 7970 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) == Unused Reference: 'RFC822' is defined on line 623, but no explicit reference was found in the text ** Obsolete normative reference: RFC 822 (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 2421 (ref. 'VPIM2') (Obsoleted by RFC 3801) -- Possible downref: Non-RFC (?) normative reference: ref. 'VPIMV2R2' Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 VPIM Working Group Glenn Parsons 2 Internet Draft Nortel Networks 3 Document: June 28, 2002 4 Category: Standards Track 6 VPIM (Voice Profile for Internet Mail) Addressing 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with all 11 provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering Task 14 Force (IETF), its areas, and its working groups. Note that other 15 groups may also distribute 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." 20 The list of current Internet-Drafts can be accessed at 21 http://www.ietf.org/ietf/1id-abstracts.txt 22 The list of Internet-Draft Shadow Directories can be accessed at 23 http://www.ietf.org/shadow.html. 25 Abstract 27 This document lists the various VPIM (Voice Profile for Internet Mail) 28 email address formats that are currently in common use and defines 29 several new address formats for special case usage. Requirements are 30 imposed on the formats of addresses used in VPIM submission mode. 32 Copyright Statement 34 Copyright (C) The Internet Society (2002). All Rights Reserved. 36 Parsons Expires: 28/01/03 1 37 Table of Contents 39 1. Introduction.....................................................3 40 2. Conventions used in this document................................3 41 3. VPIM v2 Addressing...............................................3 42 4. VPIM Addressing..................................................4 43 4.1 VPIM Gateways................................................4 44 4.2 VPIM Submission LHS..........................................4 45 4.3 VPIM Submission Addresses....................................7 46 5. Security Considerations..........................................8 47 6. IANA Consideration...............................................9 48 6.1: IANA Registration form for new value of GSTN address 49 service-selector "VPIM".....................................9 50 6.2: IANA Registration form for new value of GSTN address 51 service-selector "VOICE"...................................10 52 6.3: IANA Registration form for new value of GSTN address 53 service-selector "AMIS"....................................10 54 6.4: IANA Registration form for new value of GSTN address 55 qualif-type1 keyword and value "SYSNUM"....................11 56 6.5: IANA Registration form for new value of GSTN address 57 qualif-type1 keyword and value "EXT".......................12 58 6.6: IANA Registration form for new value of GSTN address 59 qualif-type1 keyword and value "DL"........................13 60 7. References......................................................12 61 7.1 Normative References........................................14 62 7.1 Non-Normative References....................................14 63 8. Author's Address................................................15 64 9. Full Copyright Statement........................................15 66 Parsons Expires: 28/01/03 2 67 1. Introduction 69 This document lists the various VPIM email address formats that are 70 currently in common use and defines several new address formats for 71 special case usage. Requirements are imposed on the formats of 72 addresses used in VPIM submission mode 74 [VPIM2] does not place any restrictions on the email address format. 75 However, it does recommend the use of a numeric LHS since many legacy 76 voice mail systems only use digits to identify mailboxes. Further, it 77 recommends a structure to handle private, international and 78 extensions. The private format has become deployed in most existing 79 VPIM v2 systems, further some systems will only accept messages from 80 addresses with a numeric LHS. 82 [IVM] does not describe addressing at all. The LHS format is left to 83 the discretion of the mailbox owner. However, it is useful in some 84 cases (like submission or tunneling) to specify a LHS format. A format 85 based on GSTN addressing [GSTN] is presented. 87 This document defines the various recipient (i.e., TO) addresses for 88 VPIM and IVM messages. 90 2. Conventions used in this document 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC-2119. 96 "LHS" as used in this document is to be interpreted as the left side 97 of the "@" in an email address. It is defined as "local-part" in RFC- 98 822. 100 "RHS" as used in this document is to be interpreted as the right side 101 of the "@" in an email address. It is defined as "domain" in RFC-822. 103 3. VPIM v2 Addressing 105 This is defined in section 4.2.1 of [VPIM2] & [VPIMV2R2]. Of the four 106 groups of addresses defined, the mailbox number format is the most 107 commonly used in VPIM v2 systems. 109 Example: 6137637582@nortelnetworks.com 111 Parsons Expires: 28/01/03 3 112 4. VPIM Addressing 114 VPIM places no restrictions on the form of the Internet address. VPIM 115 systems must be capable of receiving an arbitrary email address and 116 generating a reply to that address. No inferences about the structure 117 of the local part (LHS) should be necessary. 119 Recipients email addresses must be created in a form compatible with 120 the recipients system and consistent with the address entry 121 capabilities of a telephone user interface. 123 The following sections use formal syntax compliant with RFC 2234, 124 "Augmented BNF for Syntax Specifications: ABNF". 126 4.1 VPIM Gateways 128 A gateway translates between dissimilar environments. For VPIM, a 129 gateway connects between the VPIM profile of Internet mail and other 130 voice mail networking protocols (including voice call answer and 131 delivery). These may be proprietary or standard (like AMIS [AMIS-A]). 132 VPIM gateways typically service multiple voice mail users or, in the 133 case of call answer, service only one. In the former case, they serve 134 as a classic "mail transfer agent" (MTA) and in the latter as a 135 classic "mail user agent" (UA). 137 An onramp is a gateway which connects from another voice mail 138 networking protocl to VPIM. An offramp is a gateway which connects 139 from VPIM to another voice mail networking protocol. Behavior of 140 onramps and offramps is out of scope for this specification. 142 This specification describes the VPIM service portion of onramp and 143 offramp addressing. 145 4.2 VPIM Submission LHS 147 Limited capability voice mail machines may send messages by default to 148 an external message submission gateway. These gateways will convert 149 the unresolved telephone number of the recipient into a legitimate 150 email address. Messages requiring address resolution must be sent to 151 a submission system which will convert the submitted address into the 152 route-able email address. 154 Additionally, limited capability email systems may send messages to a 155 VPIM onramp system indicated on the RHS. The LHS would indicate that 156 the message is to be sent as a VPIM message to the telephone number 157 indicated. In this case, address and message translation is performed 158 by the gateway. 160 Parsons Expires: 28/01/03 4 161 Telephone numbers sent in a VPIM submission mode MUST be sent in one 162 of the following forms. 164 This is based on the format defined in [GSTN-ADDR] and extensions in 165 [GSTN]. 167 4.2.1 The VPIM address 169 For voice messages that are intended to be sent as VPIM messages the 170 service-selector element is defined to be: 172 vpim-service-selector = "VPIM" 174 The resultant vpim-address and vpim-mbox are formally 176 vpim-address = vpim-mbox 177 [ pstn-recipient ] 179 vpim-mbox = [ "VPIM=" ] ( global-phone / local-phone ) 180 [ sub-addr-spec ext-addr-spec dl-addr-spec] 182 dl-addr-spec = "/DL=" sub-addr 183 ;note that "/DL=" is case INSENSITIVE 184 ext-addr-spec = [ ext-sep sub-addr ] 185 ext-sep = ( "/EXT=" / "+" ) 186 ; note that "/EXT=" is case INSENSITIVE 187 ; "+" is used for compatibility with current 188 ; VPIM v2 addressing 190 For clarity, here is an example of a very simple vpim-mbox: 191 VPIM=6137637582 193 The extension syntax, that is a phone number followed by "/EXT=" 194 defining the extension, would be used where the mailbox does not have 195 a direct dial number associated with it (e.g., typically behind a non- 196 ISDN PBX). For example: 198 VPIM=7035255550/EXT=227 200 The distribution list syntax, that is a phone number followed by 201 "/DL=" defining the list, would be used to refer to a distribution 202 list associated with the phone number (with or without an extension). 203 For example: 205 VPIM=+14165977230/DL=93 207 Parsons Expires: 28/01/03 5 208 4.2.2 The Voice address 210 For voice messages that are intended to be sent as a voice outdialing 211 at the destination system, the service-selector element is defined to 212 be: 214 voice-service-selector = "VOICE" 216 The resultant voice-address and voice-mbox are formally 218 voice-address = voice-mbox 219 [ pstn-recipient ] 221 voice-mbox = "VOICE=" ( global-phone / local-phone ) 222 [ sub-addr spec ] [post-sep post-dial] 224 For more clarity, here is an example of a very simple voice-mbox: 226 VOICE=+3940226338 228 4.2.3 The AMIS address 230 For voice messages that are intended to be sent as AMIS (Audio 231 Messaging Interchange Specification) voice mail messages (as defined 232 in [AMIS-A] & [AMIS-D]), the service-selector element is defined to 233 be: 235 amis-service-selector = "AMIS" 237 The resultant amis-address and amis-mbox are formally 239 amis-address = amis-mbox 241 amis-mbox = "AMIS=" amis-mailbox 242 [ "/SYSNUM=" amis-sysnum ] 243 ; note that "/SYSNUM=" is case INSENSITIVE 245 amis-mailbox = ( amis-a / amis-d ) 247 amis-a = amis-a-number 249 amis-d = [ amis-mailbox-numberplan ][ "+" ] amis-mailbox-id 250 [ "+" ] [ amis-mailbox-extension ] 251 ; The "+" separators are used to be compatible 252 ; the X.400 AMIS-D mailbox definition -- 253 ; if more than one element is present, both 254 ; "+" must appear. Note also that the total 255 ; length of this field is restricted to 32 256 ; characters by AMIS-D. 258 Parsons Expires: 28/01/03 6 259 amis-mailbox-numberplan = 1*VCHAR 261 amis-mailbox-id = 1*16(VCHAR) 263 amis-mailbox-extension = 1*VCHAR 265 amis-sysnum = amis-a-number 267 amis-a-number = ( amis-PSTN-number / amis-private-number ) 269 amis-PSTN-number = int-country-code "+" 270 area-code "+" 271 local-number "+" 272 ; This is in agreement with ITU [E.164] 273 ; specification and per [AMIS-A] - the 274 ; maximum length is 15 numeric digits. 275 ; The "+" separators are used to be 276 ; compatible with the X.400 AMIS-D 277 ; mailbox definition and replace the '#' 278 ; separators of AMIS-A 280 amis-private-number = "0++" local-number "+" 281 ; [AMIS-A] indicates that maximum permitted 282 ; length of the private number is 14 283 ; digits 285 int-country-code = 1*4(DIGIT) 287 area-code = 1*(DIGIT) 289 local-number = 1*(DIGIT) 291 For more clarity, here is an example of a simple AMIS-A amis-mbox: 293 AMIS=+1/401+3278144+/SYSNUM=1+401+3279542+ 295 4.2.4 The fax address 297 Fax addresses used in VPIM are formatted as defined in [FAX- 298 ADDR],section 2. 300 4.3 VPIM Submission Addresses 302 Based on [GSTN-ADDR], these are the resultant email addresses for the 303 LHS presented above. VPIM and IVM systems that support submission 304 MUST accept, translate (if necessary), and forward messages sent to 305 these addresses. 307 Parsons Expires: 28/01/03 7 308 4.3.1 The vpim-email 310 The vpim-email element is a specific version of pstn-email for VPIM 311 over the Internet e-mail transport system, where the service-selector 312 distinction is set to "VPIM". 314 vpim-email = ["/"] vpim-address ["/"] "@" mta-I-pstn 316 In this case the mta-I-pstn will usually point to a VPIM capable 317 messaging system where the attached message will be delivered 318 properly. 320 4.3.2 The voice-email 322 The voice-email element is a specific version of pstn-email for the 323 voice outdialing over the Internet e-mail transport system, where the 324 service-selector distinction is set to "VOICE". 326 voice-email = ["/"] voice-address ["/"] "@" mta-I-pstn 328 In this case the mta-I-pstn will usually point to a device that will 329 perform an outdial, that is for example, make a telephone call to the 330 specified number and play a voice attachment. 332 4.3.3 The amis-email 334 The amis-email element is a specific version of pstn-email for the 335 AMIS over the Internet e-mail transport system, where the service- 336 selector distinction is set to "AMIS". 338 amis-email = ["/"] amis-address ["/"] "@" mta-I-pstn 340 In this case the mta-I-pstn will usually point to a device that acts 341 as a gateway to an AMIS network where the attached voice message will 342 be delivered properly. 344 4.3.4 The fax-email 346 Fax email addresses used in VPIM are formatted as defined in [FAX- 347 ADDR], section 4. 349 5. Security Considerations 351 Most security considerations are already identified in [VPIM2] and 352 [IVM]. 354 Parsons Expires: 28/01/03 8 355 An additional concern would be that the sender must trust and also be 356 aware of the policies of the submission MTA to which the message is 357 submitted. This is because, that MTA will make the determination of 358 where the final destination is and how it will be delivered based on 359 the VPIM submission LHS. 361 Submission MTAs should take care to not blindly place outdial calls to 362 any number submitted (e.g., international numbers or "1-900" numbers). 363 Ideally, senders should be authenticated to confirm their outdialing 364 privileges. 366 6. IANA Considerations 368 6.1: IANA Registration form for new value of GSTN address 369 service-selector "VPIM" 371 To: IANA@iana.org 373 Subject: Registration of new values for the GSTN address 374 service-selector specifier "VPIM" 376 service-selector name: 378 VPIM 380 Description of Use: 382 VPIM - specify that the GSTN address refers to a voice 383 mailbox that is intended to accept a VPIM message. 385 For a complete description refer to "VPIM Addressing", 386 draft-ietf-vpim-address-03.txt. 388 Security Considerations: 390 See the Security Consideration section of "VPIM 391 Addressing", draft-ietf-vpim-address-03.txt. 393 Person & email address to contact for further information: 395 Glenn W. Parsons 396 Nortel Networks 397 P.0. Box 3511 Station C 398 Ottawa, On K1Y 4H7 399 Canada 400 Phone: +1-613-763-7582 401 Fax : +1-613-763-2697 402 Email: gparsons@nortelnetworks.com 404 Parsons Expires: 28/01/03 9 405 6.2: IANA Registration form for new value of GSTN address 406 service-selector "VOICE" 408 To: IANA@iana.org 410 Subject: Registration of new values for the GSTN address 411 service-selector specifier "VOICE" 413 service-selector name: 415 VOICE 417 Description of Use: 419 VOICE - specify that the GSTN address refers to a voice 420 device that is intended to be sent a voice message via an 421 'outdialing'. 423 For a complete description refer to "VPIM Addressing", 424 draft-ietf-vpim-address-03.txt. 426 Security Considerations: 428 See the Security Consideration section of "VPIM 429 Addressing", draft-ietf-vpim-address-03.txt. 431 Person & email address to contact for further information: 433 Glenn W. Parsons 434 Nortel Networks 435 P.0. Box 3511 Station C 436 Ottawa, On K1Y 4H7 437 Canada 438 Phone: +1-613-763-7582 439 Fax : +1-613-763-2697 440 Email: gparsons@nortelnetworks.com 442 6.3: IANA Registration form for new value of GSTN address 443 service-selector "AMIS" 445 To: IANA@iana.org 447 Subject: Registration of new values for the GSTN address 448 service-selector specifier "AMIS" 450 service-selector name: 452 AMIS 454 Parsons Expires: 28/01/03 10 455 Description of Use: 457 AMIS - specify that the GSTN address refers to a voice 458 mailbox that is intended to be sent an AMIS (Audio 459 Messaging Interchange Specification) voice mail message. 461 For a complete description refer to "VPIM Addressing", 462 draft-ietf-vpim-address-03.txt. 464 Security Considerations: 466 See the Security Consideration section of "VPIM 467 Addressing", draft-ietf-vpim-address-03.txt. 469 Person & email address to contact for further information: 471 Glenn W. Parsons 472 Nortel Networks 473 P.0. Box 3511 Station C 474 Ottawa, On K1Y 4H7 475 Canada 476 Phone: +1-613-763-7582 477 Fax : +1-613-763-2697 478 Email: gparsons@nortelnetworks.com 480 6.4: IANA Registration form for new value of GSTN address 481 qualif-type1 keyword and value "SYSNUM" 483 To: IANA@iana.org 485 Subject: Registration of new values for the GSTN address 486 qualif-type1 element "sysnum" 488 qualif-type1 "keyword" name: 490 sysnum 492 qualif-type1 "value" ABNF definition: 494 sysnum = 1*(DIGIT / "+") 496 Description of Use: 498 sysnum is used to specify the numeric optional AMIS sub- 499 address element as described in "VPIM Addressing", 500 draft-ietf-vpim-address-03.txt. 502 Use Restriction: 504 The use of "SYSNUM" is restricted to "AMIS" service- 505 selector, is it has no meaning outside the AMIS service. 507 Parsons Expires: 28/01/03 11 508 Security Considerations: 510 See the Security Consideration section of "VPIM 511 Addressing", draft-ietf-vpim-address-03.txt. 513 Person & email address to contact for further information: 515 Glenn W. Parsons 516 Nortel Networks 517 P.0. Box 3511 Station C 518 Ottawa, On K1Y 4H7 519 Canada 520 Phone: +1-613-763-7582 521 Fax : +1-613-763-2697 522 Email: gparsons@nortelnetworks.com 524 6.5: IANA Registration form for new value of GSTN address qualif-type1 525 keyword and value "EXT" 527 To: IANA@iana.org 529 Subject: Registration of new values for the GSTN address 530 qualif-type1 element "EXT" 532 qualif-type1 "keyword" name: 534 ext 536 qualif-type1 "value" ABNF definition: 538 ext = 1*(DIGIT) 540 Description of Use: 542 EXT is used to specify the numeric optional extension 543 That idenitifies a particular VPIM mailbox as 544 described in "VPIM Addressing", 545 draft-ietf-vpim-address-03.txt. 547 Use Restriction: 549 The use of "EXT" is intended for the "VPIM" service- 550 selector, however is may have meaning and be used outside 551 the VPIM service. 553 Security Considerations: 555 See the Security Consideration section of "VPIM 556 Addressing", draft-ietf-vpim-address-03.txt. 558 Parsons Expires: 28/01/03 12 559 Person & email address to contact for further information: 561 Glenn W. Parsons 562 Nortel Networks 563 P.0. Box 3511 Station C 564 Ottawa, On K1Y 4H7 565 Canada 566 Phone: +1-613-763-7582 567 Fax : +1-613-763-2697 568 Email: gparsons@nortelnetworks.com 570 6.6: IANA Registration form for new value of GSTN address qualif-type1 571 keyword and value "DL" 573 To: IANA@iana.org 575 Subject: Registration of new values for the GSTN address 576 qualif-type1 element "DL" 578 qualif-type1 "keyword" name: 580 dl 582 qualif-type1 "value" ABNF definition: 584 dl = 1*(DIGIT) 586 Description of Use: 588 DL is used to specify the numeric optional personal 589 Distribution list for a particular VPIM mailbox as 590 described in "VPIM Addressing", 591 draft-ietf-vpim-address-03.txt. 593 Use Restriction: 595 The use of "DL" is intended for the "VPIM" service- 596 selector, however is may have meaning and be used outside 597 the VPIM service. 599 Security Considerations: 601 See the Security Consideration section of "VPIM 602 Addressing", draft-ietf-vpim-address-03.txt. 604 Parsons Expires: 28/01/03 13 605 Person & email address to contact for further information: 607 Glenn W. Parsons 608 Nortel Networks 609 P.0. Box 3511 Station C 610 Ottawa, On K1Y 4H7 611 Canada 612 Phone: +1-613-763-7582 613 Fax : +1-613-763-2697 614 Email: gparsons@nortelnetworks.com 616 7. References 618 7.1 Normative References 620 [GSTN] Allocchio, C., "GSTN Address Element Extensions in e-mail 621 Services", RFC 2846, June 2000. 623 [RFC822] Crocker, D., "Standard for the Format of ARPA Internet Text 624 Messages", STD 11, RFC 822, UDEL, August 1982. 626 [VPIM2] Vaudreuil, Greg, Parsons, Glenn, "Voice Profile for Internet 627 Mail, Version 2", RFC 2421, September 1998. 629 [VPIMV2R2] Vaudreuil, Greg, Parsons, Glenn, "Voice Profile for 630 Internet Mail, version 2", , February 631 2002. 633 [FAX-ADDR] Allocchio, C., "Minimal FAX address format in Internet 634 Mail", RFC 3192 October 2001. 636 [GSTN-ADDR] Allocchio, C., "Minimal GSTN address format in Internet 637 Mail", RFC 3191 October 2001. 639 7.1 Non-Normative References 641 [AMIS-A] Audio Messaging Interchange Specifications (AMIS) - Analog 642 Protocol Version 1, Issue 2, February 1992. 644 [AMIS-D] Audio Messaging Interchange Specifications (AMIS) - Digital 645 Protocol Version 1, Issue 3, August 1993. 647 [E.164] CCITT Recommendation E.164 (1991), Telephone Network and ISDN 648 Operation, Numbering, Routing and Mobile Service - Numbering Plan for 649 the ISDN Era. 651 [IVM] McRae, Stuart, Parsons, Glenn, "Internet Voice Mail", , June 2002. 654 Parsons Expires: 28/01/03 14 655 8. Author's Address 657 Glenn W. Parsons 658 Nortel Networks 659 Ottawa, ON K1Y 4H7 660 Phone: +1-613-763-7582 661 Fax : +1-613-967-5060 662 Email: gparsons@nortelnetworks.com 664 9. Full Copyright Statement 666 Copyright (C) The Internet Society (2002). All Rights Reserved. 668 This document and translations of it may be copied and furnished to 669 others, and derivative works that comment on or otherwise explain it 670 or assist in its implementation may be prepared, copied, published and 671 distributed, in whole or in part, without restriction of any kind, 672 provided that the above copyright notice and this paragraph are 673 included on all such copies and derivative works. However, this 674 document itself may not be modified in any way, such as by removing 675 the copyright notice or references to the Internet Society or other 676 Internet organizations, except as needed for the purpose of developing 677 Internet standards in which case the procedures for copyrights defined 678 in the Internet Standards process must be followed, or as required to 679 translate it into languages other than English. 681 The limited permissions granted above are perpetual and will not be 682 revoked by the Internet Society or its successors or assigns. 684 This document and the information contained herein is provided on an 685 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 686 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 687 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 688 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 689 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 691 Parsons Expires: 28/01/03 15