idnits 2.17.1 draft-ietf-fax-fulladdr-05.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 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 1 longer page, the longest (page 1) being 1548 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 62 instances of too long lines in the document, the longest one being 7 characters in excess of 72. == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 591 has weird spacing: '...for the purpo...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 (February 1999) is 9202 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: '10' is defined on line 1493, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2303 (ref. '1') (Obsoleted by RFC 3191) ** Obsolete normative reference: RFC 2304 (ref. '2') (Obsoleted by RFC 3192) ** Obsolete normative reference: RFC 2234 (ref. '4') (Obsoleted by RFC 4234) -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' -- Possible downref: Non-RFC (?) normative reference: ref. '10' ** Obsolete normative reference: RFC 822 (ref. '11') (Obsoleted by RFC 2822) Summary: 11 errors (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working C. Allocchio 2 Group GARR-Italy 3 INTERNET-DRAFT February 1999 4 Expires: August 1999 5 File: draft-ietf-fax-fulladdr-05.txt 7 GSTN address element extensions in e-mail services 9 Status of this Memo 11 This document is an Internet Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute 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 documents 20 at any time. It is inappropriate to use Internet-Drafts as 21 reference material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 1. Introduction 31 The possible elements composing a "Global Switched Telephone Network 32 (GSTN) address in e-mail" (formerly known also as Public Switched 33 Telephone Network - PSTN) can vary from a minimum number up to a 34 really large and complex collection: the minimal format and general 35 address syntax are defined in [1], together with the syntax to define 36 additional address elements. 38 To ensure interoperability among different applications, also the 39 additional, and in most cases optional, address elements must be 40 defined in a standard syntax. In this memo we define some of these 41 additional address elements: 43 - the detailed definition of GSTN number formats, in order to cover 44 all the possible and different GSTN numbering schema (gstn-phone, 45 sub-addr-spec and post-dial) 47 - the message originator / recipient specification (pstn-recipient) 49 The definitions included in this memo always superset the minimal 50 profile defined in [1]. The "incremental alternatives" syntax defined 51 in [4] is used to describe this fact. 53 GSTN addresses in e-mail MAY contain additional elements defined in 54 other specifications (see for example "T33S" element in [2]), but 55 they MUST use definitions contained in this memo for those elements 56 already specified here. 58 In particular, "service-selector" names and "qualif-type1" elements 59 MUST be registered with IANA, and published within the "ASSIGNED 60 NUMBERS" document. This will ensure an easy mechanism for extending 61 the element sets and will avoid unecessary duplication. IANA 62 Registration form templates are provided in Appendix B. 63 A collection of forms for already defined "serivce-selector" and 64 "qualif-type1" elements is listed in appendix C and appendix D 65 respectively. Standard Track RFC specification MUST supplement the 66 definition of any new element registered with IANA. The use of 67 unregistered "X-" type "service-selector" and "qualif-type1" elements 68 is deprecated. See Appendix B - IANA Considerations for further details. 70 Even if in this memo we focus on e-mail addresses, a number of elements 71 defined in this specification can also be used for other specifications 72 dealing with embedding GSTN addresses into other addresses: for example 73 there is some work in progress about URLs specification which adopts 74 similar definitions, with slight changes in the global syntax due to 75 specific URL format. 77 Finally, in this memo we try to maintain maximum compatibility 78 with existing e-mail gateway services and standard specifications. 79 In particular we will use as much as possible compatible definitions 80 with MIXER [3] gateways specifications, in order to facilitate 81 transparent e-mail address translations without unduly complex mappings. 83 In this document the formal definitions are described using ABNF 84 syntax, as defined into [4]. We will also use some of the "CORE 85 DEFINITIONS" defined in "APPENDIX A - CORE" of that document. The 86 exact meaning of the capitalised words 88 "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 89 "SHOULD NOT", "RECOMMENDED", "MAY", "OPTIONAL" 91 is defined in reference [5]. 93 2. GSTN extended number and pstn-mbox extended format 95 In reference [1], section 2, the minimal definition of pstn-mbox 96 includes the global-phone element, and further details are defined 97 in [1] section 2.1. 99 However other non global-phone numbering schema are allowed, too. 100 In order to describe these more general schema, we thus expand the 101 scenario defining the GSTN extended number format: 103 gstn-phone = ( global-phone / local-phone ) 105 The complexity of the GSTN system includes also the optional use of 106 subaddresses and post dialling sequences. As a consequence the extended 107 definition of pstn-mbox becomes: 109 pstn-mbox = service-selector "=" global-phone 111 pstn-mbox =/ service-selector "=" gstn-phone 112 [ sub-addr-spec ] [post-sep post-dial] 114 NOTE: see section 4 in case multiple sub-addr-spec per pstn-mbox need 115 to be specified. 117 2.1 The local-phone syntax 119 The local-phone element can be used to represent all possible cases 120 where the global-phone does not apply. In order to cover all possible 121 different and complex conventions in use in the GSTN system, the 122 local-phone definition allows a large number of elements. Please 123 note that local-phone MUST NOT start with a "+" sign, as this is 124 reserved for global-phone definition. 126 We now define in details local-phone: 128 local-phone = [ exit-code ] [ dial-number ] 130 exit-code = phone-string 131 ; this include anything needed to enable dialling, like 132 ; the digit to access outside line, the long distance 133 ; carrier access code, the access password to the service, 134 ; etc... 136 dial-number = phone-string 137 ; this is in many cases composed of different elements 138 ; like the local phone number, the area code (if needed), 139 ; the international country code (if needed), etc... 141 phone-string = 1*( DTMF / pause / tonewait / written-sep ) 143 DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" ) 144 ; special DTMF codes like "*", "#", "A", "B", 145 ; "C", "D" are defined in [6] 146 ; Important Note: this is NOT the alpha to digit 147 ; convention in use in some countries. 149 pause = "p" 151 tonewait = "w" 153 NOTE: "pause" and "tonewait" character interpretation in local-phone numbers 154 depends on the specific MTA implementation. Thus its exact meaning 155 need not to be defined here. Both "pause" and "tonewait" are case 156 insensitive. 158 The written-sep is defined in [1], section 2.1; other specification for 159 some particular services (like for example voice messaging service) CAN 160 allow additional separators. Their definition MUST be detailed into 161 the documents defining the addressing for the specific service. 163 Important Note: 164 A local-phone specification is a sequence which should be dialled 165 by the MTA specified by mta-I-pstn (see [1], section 3) to reach 166 the destination device. Other MTAs should only transfer the message 167 around without modification until the destination MTA is reached. 168 However, this implementation scenario is extremely complex and full 169 discussion of it is outside the scope of this document. 171 2.2 The sub-addr-spec element 173 In GSTN service there are cases where a sub-addr-spec is required to 174 specify the final destination. In particular there are ISDN subaddresses 175 [7], which apply to all possible services, while other types are 176 limited to specific services (see the fax service T.33 subaddress [8], 177 [2]). 179 We must thus be able to specify at least the ISDN subaddress, remembering 180 that an ISDN subaddress could be supplemented by other subaddress types 181 (like a fax T.33 [8] subaddress). 183 As a consequence, the definition of sub-addr-spec is: 185 sub-addr-spec = [ isdn-sep isub-addr ] 187 In detail: 189 isdn-sep = "/ISUB=" 190 ; note that "/ISUB=" is case INSENSITIVE 192 isub-addr = 1*( DIGIT ) 194 isub-addr =/ 1*( DIGIT / written-sep ) 196 The IANA registration form for sub-addr-spec is given in appendix D.2 198 2.3 The post-dial element 200 In some cases, after the connection with the destination GSTN 201 device has been established, a further dialling sequence can be 202 required to access further services; a typical example are the 203 automated menu-driven services using DTMF sequences on the 204 telephone services. These sequences are defined as a separator 205 and a post dial sequence: 207 post-sep = "/POSTD=" 208 ; note that "/POSTD=" is case INSENSITIVE 210 post-dial = phone-string 212 A number of gstn-phone examples are listed in section 4. 214 The IANA registration form for post-sep and post-dial are given in 215 appendix D.3 217 3. The pstn-recipient 219 The pstn-mbox element is sometimes not enough to specify additional 220 Details, like the originator / recipient name, physical address, etc. 221 The optional pstn-recipient element provides information which could 222 also be used by the onramp / offramp gateway to specify the originator / 223 recipient exactly. In many cases the pstn-recipient element will be 224 used for recipient addresses: however also originator addresses could 225 be specified using pstn-mbox and pstn-recipient, in particular if onramp 226 gateways are involved. 228 As an example, when an offramp fax gateway is involved, the 229 pstn-recipient element could be used to specify the intended recipient 230 on a fax cover page; again the fax cover page headers could be qualified 231 using the originator pstn-recipient information. 233 Please note: in this document many ABNF variables contain the "recipient" 234 token, but all these elements can be applied both to originator / recipient 235 addresses. 237 The pstn-recipient is a sequence of qualif-type1 elements, as defined 238 in [1], section 2: 240 pstn-recipient = [ recipient-name ] 241 [ 1*( recipient-qualifier ) ] 243 As a consequence, the extended definition of pstn-address becomes: 245 pstn-address = pstn-mbox [ qualif-type1 ] 247 pstn-address =/ pstn-mbox [ pstn-recipient ] [ qualif-type1 ] 249 3.1 The recipient-name 251 The recipient-name specifies the personal name of the originator / 252 recipient: 254 recipient-name = "/ATTN=" pers-name 256 pers-name = [ givenname "." ] 257 [ initials "." ] 258 surname 260 The following definitions come directly from MIXER specification [3]: 262 surname = printablestring 264 givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" / 265 "," / "-" / "/" / ":" / "=" / "?" ) 267 initials = 1*ALPHA 269 NOTE: the "initials" element does not simply specify the 270 middle initial which is common in some countries; it 271 allows the complete set of givennames initials in any 272 possible combination. See examples at section 5.2 274 It is essential to remember that "pstn-address" element (in all its 275 components and extensions) MUST strictly follow the "quoting rules" 276 spcified in the relevant standards [11], [12]. 278 The IANA registration form for recipient-name is given in appendix D.4 280 3.2 The extensible recipient-qualifier 282 The recipient-name is sometimes not enough to specify completely the 283 originator / recipient. An additional set of optional elements, whose 284 specific definition is in most cases application dependent, is thus 285 defined: 287 recipient-qualifier = ( qualif-type1 / qualif-type2 ) 289 The recipient-qualifier is a qualif-type1 element, and contains 290 a qualif-type1 element in a recursive definition which allows an 291 extensible format. However we define at least a number of these 292 elements, calling them "qualif-type2" 294 qualif-type2 = "/" qual2-label "=" string 296 qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR" 297 "ADDU" / "ADDL" / "POB" / "ZIP" / "CO" 299 string = PCHAR 300 ; note that printable characters are %x20-7E 302 printablestring = 1*( DIGIT / ALPHA / SP / 303 "'" / "(" / ")" / "+" / "," / "-" / 304 "." / "/" / ":" / "=" / "?" ) 305 ; this definition comes from ITU F.401 [9] 306 ; and MIXER [3] 308 We briefly describe in Table 1 the meaning of qual2-label fields: 310 Table 1 - qual2-label 312 qual2-label Description 313 ----------------------------------------------------------------- 314 "ORG" Organization Name for Physical Delivery (example: ACME Inc) 316 "OFNO" Office Number for physical delivery (example: BLD2-44) 318 "OFNA" Office Name for physical delivery (example: Sales) 320 "STR" Street address for physical delivery (example: 321 45, Main Street) 323 "ADDR" Unformatted postal address for physical delivery 324 (example: HWY 14, Km 94.5 - Loc. Redhill) 326 "ADDU" Unique postal name for physical delivery (example: 327 ACMETELEX) 329 "ADDL" Local postal attributes for physical delivery (example: 330 Entrance 3, 3rd floor, Suite 296) 332 "POB" Post Office Box for physical delivery 334 "ZIP" Postal ZIP code for physical delivery 336 "CO" Country Name for physical delivery 337 ----------------------------------------------------------------- 339 One or a combination of some of the above elements are usually enough 340 to exactly specify the originator / recipient of the message. The use 341 of a large number of these elements could in fact create a very long 342 recipient-qualifier. Thus only the strictly needed elements SHOULD 343 be used. The maximum total length of the pstn-email MUST in fact 344 not exceed the limits specified in the relevant standards [11] [12]. 346 IMPORTANT NOTE: even if the meaning of the above elements is derived 347 directly from similar elements available in F.401 specification [9] 348 their names is explicitly different, in order not to conflict with 349 specific X.400 addressing rules. Also any additional qualif-type1 350 element defined in different specification SHOULD use different 351 label names to avoid possible conflicts. 353 The IANA registration form for these elements is given in appendix 354 D.5 to D.14 356 4. Multiple sub-addr-spec cases 358 In case there are multiple sub-addr-spec to be given on the same 359 pstn-mbox then multiple pstn-email elements will be used. The UA could 360 accept multiple sub-addr-spec elements for the same global-phone / 361 local-phone, but it MUST generate multiple pstn-mbox, when passing the 362 message to the MTA. 364 5. Examples 366 In order to clarify the specification we present here a limited 367 set of examples. Many of the examples refer to the fax service, 368 but also additional possible services are included. Check also 369 the examples in [1] and [2] for additional information. 371 5.1 pstn-mbox examples 373 A pstn-mbox address in Italy for the fax service, dialled from 374 U.S.A., using local-phone, without sub-addr-spec and without 375 written-sep: 377 FAX=0103940226338 379 A pstn-mbox address in Germany for an hypotetical XYZ service, using 380 global-phone, with ISDN sub-addr-spec 1234 and written-sep ".": 382 XYZ=+49.81.7856345/ISUB=1234 384 A pstn-mbox address in U.S.A. for fax service, using global-phone, 385 with T.33 sub-addr-spec 8745, with written-sep "-" and post-dial sequence 386 p1w7005393w373 388 FAX=+1-202-455-7622/T33S=8745/PostD=p1w7005393w373 390 A pstn-mbox address in Italy for fax service, using local-phone, 391 dialed from an MTA in Germany, (international access code "00", 392 with ISDN subaddress 9823, with T.33 subaddress "4312" and without 393 pause or written-sep: 395 FAX=003940226338/Isub=9823/T33S=4312 397 The same pstn-mbox address in Italy, using local-phone dialed from 398 an MTA in Italy (long distance call), with long distant access "0", 399 with exit-code "9", T.33 subaddress "4312", pause "p" and written-sep 400 ".": 402 FAX=9p040p22.63.38/t33s=4312 404 A pstn-mbox address in North America for hypotetical service XYZ, 405 using global-phone, without sub-addr-spec and written-sep "-" and ".": 407 XYZ=+1.202.344-5723 409 A pstn-mbox address for fax service in France, using local-phone 410 dialed from an MTA in France (long distance call), with exit-code 411 "0", T.33 subaddress "3345" and pause "p": 413 FAX=0p0134782289/T33s=3345 415 A pstn-mbox address for fax service in North America, using local-phone, 416 without sub-addr-spec, without local-number, using only post-dial 417 sequences to reach numbers stored in a locally defined short-dial numbers 418 database, where 6743 is an access password, and 99p51 is the sequence to 419 access the local short-dial number: 421 FAX=/postd=w6743w99p51 423 5.2 pstn-recipient examples 425 Here are a number of pstn-recipient examples. Please note that 426 pstn-recipient is just an optional element, and thus a pstn-mbox 427 element also is required in a pstn-address. 429 A pstn-recipient using only recipient-name, with givenname initials 430 and surname: 432 /ATTN=Tom.J.Smiths 434 A pstn-recipient using only recipient-name, with givenname, a 435 complete set of initials (including the first name initial "C") and 436 surname (where the "real life" givennames are "Carlo Maria Luis 437 Santo" and the surname is "Nascimento"): 439 /ATTN=Carlo.CMLS.Nascimento 441 A pstn-recipient using only recipient-name, with givenname and 442 surname: 444 /ATTN=Mark.Collins 446 A pstn-recipient using only recipient-name, with surname only: 448 /ATTN=Smiths 450 A pstn-recipient using recipient-name, and one recipient-qualifier 451 element: 453 /ATTN=J.Smiths/OFNA=Quaility-control 455 A pstn-recipient using two recipient-qualifier extension, only: 457 /OFNO=T2-33A/OFNA=Quality-Ccontrol 459 A fax-recipient using some recipient-qualifier for physical delivery: 461 /STR=45, Main.Street/OFNA=Sales.dept 463 5.3 pstn-address examples 465 Some pstn-address examples, obtained combining elements from 466 previous examples. There are complete addresses which can 467 be used as "local part" (LHS) element of an e-mail address. 469 Without optional pstn-recipient (fax service): 471 FAX=+12023445723 473 With pstn-recipient (XYZ service): 475 XYZ=+3940226338/ATTN=Mark.Collins 477 With pstn-recipient made of two recipient-qualifier extensions 478 (fax service): 480 FAX=9p040p22.63.38/t33s=4312/ofno=T2-33A/OFNA=Q-C 482 5.4 pstn-email examples 484 Here are the same addresses as before, where "faxgw" is the 485 mta-I-pstn field for the fax service. 487 FAX=+12023445723@faxgw 489 FAX=+39-40-226338/ATTN=Mark.Collins@faxgw 491 FAX=9p040p226338/T33S=4312/OFNO=T2-33A/OFNA=Q-C@faxgw 493 FAX=+39040226338/ATTN=Mark.Collins/@faxgw 495 NOTE: the optional "/" in front for the "@" sign can be generated 496 by gateways to other services, like MIXER [3]. 498 5.5 A complete SMTP transaction example: 500 Here is an example of complete SMTP transaction. 502 S: 503 C: 504 S: 220 foo.domain.com ESMTP service ready 505 C: EHLO pc.mailfax.com 506 S: 250 foo.domain.com says hello 507 C: MAIL FROM: 508 S: 250 Sender ok 509 C: RCPT TO: 510 S: 250 recipient ok 511 C: DATA 512 S: 354 Enter your data 513 C: From: Thomas Blake 514 C: To: Jim Burton 515 C: Subject: Hello there 516 C: MIME-version: 1.0 517 C: Date: Mon, 01 Sep 1997 18:14:23 -0700 518 C: Content-Type: multipart/mixed; boundary=16820115-1435684603#2306 519 C: 520 C: This is a MIME message. It contains a 521 C: TIFF fax bodypart 522 C: 523 C: --16820115-1435684603#2306 524 C: Content-Type: image/TIFF 525 C: Content-Transfer-Encoding: BASE64 526 C: Content-Description: FAX 527 C: 528 C: ABAA745HDKLSW932ALSDL3ANCVSASDFLALSDFA 529 C: 87AASS2999499ASDANASDF0000ASDFASDFNANN 530 C: 87BBHDXBADS00288SADFNAZBZNNDNNSNNA11A0 531 C: H8V73KS0C8JS6BFJEH78CDWWDUJEDF7JKES8== 532 C: --16820115-1435684603#2306-- 533 C: . 534 S: 250 Okay 535 C: QUIT 536 S: 221 Goodbye 538 6. Conclusion 540 This proposal creates a standard set of extensions for GSTN addresses, 541 enriching the existing minimal specification [1]. The proposal requires 542 no changes to existing e-mail software, and allows a more detailed 543 address specification, including per originator / recipient specific 544 elements. The IANA registration mechanism to add easily new services 545 and qualifiers using the GSTN addresses is also defined. 547 7. Security Considerations 549 This document specifies a means by which GSTN addresses and more 550 can be encoded into e-mail addresses. As routing of e-mail messages 551 is determined by Domain Name System (DNS) information, a successful 552 attack on this service could force the mail path via some particular 553 gateway or message transfer agent where mail security can be 554 affected by compromised software. 556 There are several means by which an attacker might be able to 557 deliver incorrect mail routing information to a client. These 558 include: (a) compromise of a DNS server, (b) generating a 559 counterfeit response to a client's DNS query, (c) returning 560 incorrect "additional information" in response to an unrelated 561 query. Clients SHOULD ensure that mail routing are based only 562 on authoritative answers. Once DNS Security mechanisms [7] 563 become more widely deployed, clients SHOULD employ those mechanisms 564 to verify the authenticity and integrity of mail routing records. 566 Some GSTN service require dialing of private codes, like Personal 567 Identification Numbers, to dial a G3 fax recipient or to access 568 special services. As e-mail addresses are transmitted without 569 encoding over the MTAs transport service, this could allow 570 unauthorized people to gain access to these codes when used inside 571 local-phone. More over these codes might appear in some cases in the 572 originator / recipient addresses on cover pages delivered via offramp 573 gateways to G3 fax recipients. Senders SHOULD be provided methods to 574 prevent this disclosure, like code encryption, or masquerading 575 techniques: out-of-band communication of authorization information or 576 use of encrypted data in special fields are the available non-standard 577 techniques. 579 8. Copyright 581 "Copyright (C) The Internet Society (date). All Rights Reserved. 583 This document and translations of it may be copied and furnished to 584 others, and derivative works that comment on or otherwise explain it 585 or assist in its implmentation may be prepared, copied, published and 586 distributed, in whole or in part, without restriction of any kind, 587 provided that the above copyright notice and this paragraph are 588 included on all such copies and derivative works. However, this 589 document itself may not be modified in any way, such as by removing 590 the copyright notice or references to the Internet Society or other 591 Internet organizations, except as needed for the purpose of 592 developing Internet standards in which case the procedures for 593 copyrights defined in the Internet Standards process must be followed, 594 or as required to translate it into languages other than English. 596 The limited permissions granted above are perpetual and will not be 597 revoked by the Internet Society or its successors or assigns. 599 This document and the information contained herein is provided on an 600 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 601 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 602 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 603 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 604 FITNESS FOR A PARTICULAR PURPOSE." 606 9. Appendix A: Collected ABNF Syntax 608 In this section we provide a summary of ABNF specifications defining both 609 the minimal [1] and the extended elements of pstn-address. 611 pstn-email = ["/"] pstn-address ["/"] "@" mta-I-pstn 613 mta-I-pstn = domain 615 pstn-address = pstn-mbox [ qualif-type1 ] 617 pstn-address =/ pstn-mbox [ pstn-recipient ] [ qualif-type1 ] 619 pstn-mbox = service-selector "=" global-phone 621 pstn-mbox =/ service-selector "=" gstn-phone 622 [ sub-addr-spec ] [post-sep post-dial] 624 service-selector = 1*( DIGIT / ALPHA / "-" ) 626 qualif-type1 = "/" keyword "=" string 628 keyword = 1*( DIGIT / ALPHA / "-" ) 630 string = PCHAR 632 gstn-phone = ( global-phone / local-phone ) 634 global-phone = "+" 1*( DIGIT , written-sep ) 636 local-phone = [ exit-code ] [ dial-number ] 638 exit-code = phone-string 640 dial-number = phone-string 642 phone-string = 1*( DTMF / pause / tonewait / written-sep ) 644 DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" ) 646 written-sep = ( "-" / "." ) 648 pause = "p" 650 tonewait = "w" 652 sub-addr-spec = [ isdn-sep isub-addr ] 654 isdn-sep = "/ISUB=" 656 isub-addr = 1*( DIGIT ) 658 isub-addr =/ 1*( DIGIT / written-sep ) 660 post-sep = "/POSTD=" 662 post-dial = phone-string 664 pstn-recipient = [ recipient-name ] 665 [ 1*( recipient-qualifier ) ] 667 recipient-name = "/ATTN=" pers-name 669 pers-name = [ givenname "." ] 670 [ initials "." ] 671 surname 673 surname = printablestring 675 givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" / 676 "," / "-" / "/" / ":" / "=" / "?" ) 678 initials = 1*ALPHA 680 recipient-qualifier = ( qualif-type1 / qualif-type2 ) 682 qualif-type2 = "/" qual2-label "=" string 684 qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR" 685 "ADDU" / "ADDL" / "POB" / "ZIP" / "CO" 687 printablestring = 1*( DIGIT / ALPHA / SP / 688 "'" / "(" / ")" / "+" / "," / "-" / 689 "." / "/" / ":" / "=" / "?" ) 691 10. Appendix B: IANA Considerations 693 As the service-selector and qualif-type1 elements values are 694 extensible ones, they MUST be registered with IANA. 696 To register a service-selector or a qualif-type1 element, the 697 registration form templates given in B.1 and B.2 MUST be used. In 698 order to detail the specification, any new registration MUST refer 699 to at least one Standard Track RFC where the element is described. 701 IANA MUST NOT accept registrations which are not supplemented by 702 a Standard Track RFC and which are not fully specified accoding to 703 the template forms given in B.1 and B.2. In case of need for further 704 consultation about accepting a new registration, IANA SHOULD refer 705 to the Application Area Director to be directed to the approrpiate 706 "expert" individal or IETF Working Group. 708 After succesful registration, IANA should publish the registered new 709 element in the appropriate on-line IANA WEB site, and include it 710 into the updates of the "Assigned Numbers" RFC series. 712 B.1: IANA Registration form template for new values of GSTN 713 address service-selector 715 To: IANA@isi.edu 716 Subject: Registration of new values for the GSTN address 717 service-selector specifier "foo" 719 service-selector name: 721 foo 723 Description of Use: 725 foo - ("foo" is a fictional new service-selector used in this 726 template as an example, it is to be replaced with the new value 727 being registered. Include a short description of the use of the 728 new value here. This MUST include reference to Standard Track RFCs 729 and eventaully to other Standard Bodies documents for the complete 730 description; the use of the value must be defined completely 731 enough for independent implementation). 733 Security Considerations: 735 (Any additional security considerations that may be introduced by 736 use of the new service-selector parameter should be defined here or 737 in the reference Standards Track RFCs) 739 Person & email address to contact for further information: 741 (fill in contact information) 743 INFORMATION TO THE SUBMITTER: 745 The accepted registrations will be listed in the "Assigned Numbers" 746 series of RFCs. The information in the registration form is freely 747 distributable. 749 B.2: IANA Registration form template for new values of GSTN 750 address qualif-type1 keyword and value 752 To: IANA@isi.edu 753 Subject: Registration of new values for the GSTN address 754 qualif-type1 element "bar" 756 qualif-type1 "keyword" name: 758 bar 760 qualif-type1 "value" ABNF definition: 762 abnf - ("abnf" MUST define the ABNF form of the qualif-type1 value. 763 The ABNF specification MUST be self-contained, using as basic 764 elements the tokens given in specification [4]. To avoid any 765 duplication (when appropriate), it MUST also use as building 766 non-basic tokens any already registered non-basic token from other 767 qualif-type1 elements, i.e. it MUST use the same non-basic token 768 name and then repeat its identical ABNF definition from basic 769 tokens; see appendix E for examples). 771 Description of Use: 773 bar - ("bar" is a fictional description for a new qualif-type1 774 element used in this template as an example. It is to be replaced 775 by the real description of qualif-type1 element being registered. 776 Include a short description of the use of the new qualif-type1 here. 777 This MUST include reference to Standards Track RFCs and eventually 778 to other Standard Bodies documents for the complete description; the 779 use of the value MUST be defined completely enough for independent 780 implementation.) 782 Use Restriction: 784 (If the new qualif-type1 elements is meaningful only for a specific 785 set of service-element, you MUST specify here the list of allowed 786 service-element types. If there is no restriction, then specify the 787 keyword "none") 789 Security Considerations: 791 (Any additional security considerations that may be introduced by 792 use of the new service-selector parameter should be defined here or 793 in the reference Standards Track RFCs) 795 Person & email address to contact for further information: 797 (fill in contact information) 799 INFORMATION TO THE SUBMITTER: 801 The accepted registrations will be listed in the "Assigned Numbers" 802 series of RFCs. The information in the registration form is freely 803 distributable. 805 11. Appendix C: IANA Registration form for new value of GSTN 806 address service-selector "FAX" 808 To: IANA@isi.edu 809 Subject: Registration of new values for the GSTN address 810 service-selector specifier "FAX" 812 service-selector name: 814 FAX 816 Description of Use: 818 FAX - specify that the GSTN address refers either to an 819 Internet Fax device, or an onramp/offramp Fax gateway. 821 For a complete description refer to RFC2304 and RFC2303 823 Security Considerations: 825 See the Security Consideration section of RFC2304. 827 Person & email address to contact for further information: 829 Claudio Allocchio 830 Sincrotrone Trieste 831 SS 14 Km 163.5 Basovizza 832 I 34012 Trieste 833 Italy 835 RFC822: Claudio.Allocchio@elettra.trieste.it 836 X.400: C=it;A=garr;P=Trieste;O=Elettra; 837 S=Allocchio;G=Claudio; 838 Phone: +39 40 3758523 839 Fax: +39 40 3758565 841 12. Appendix D: IANA Registration forms for new values of GSTN 842 address qualit-type1 keyword and value 844 D.1 - T33S 846 To: IANA@isi.edu 847 Subject: Registration of new values for the GSTN address 848 qualif-type1 element "T33S" 850 qualif-type1 "keyword" name: 852 T33S 854 qualif-type1 "value" ABNF definition: 856 sub-addr = 1*( DIGIT ) 858 Description of Use: 860 T33S is used to specify the numeric only optional fax sub-address 861 element described in "ITU T.33 - Facsimile routing utilizing the 862 subaddress; recommendation T.33 (July, 1996)". Further detailed 863 description is available in RFC2304. 865 Use Restriction: 867 The use of "T33S" is restricted to "FAX" service-selector, is it has 868 no meaning outside the fax service. 870 Security Considerations: 872 See the Security Consideration section of RFC2304. 874 Person & email address to contact for further information: 876 Claudio Allocchio 877 Sincrotrone Trieste 878 SS 14 Km 163.5 Basovizza 879 I 34012 Trieste 880 Italy 882 RFC822: Claudio.Allocchio@elettra.trieste.it 883 X.400: C=it;A=garr;P=Trieste;O=Elettra; 884 S=Allocchio;G=Claudio; 885 Phone: +39 40 3758523 886 Fax: +39 40 3758565 888 D.2 - ISUB 890 To: IANA@isi.edu 891 Subject: Registration of new values for the GSTN address 892 qualif-type1 element "ISUB" 894 qualif-type1 "keyword" name: 896 ISUB 898 qualif-type1 "value" ABNF definition: 900 isub-addr = 1*( DIGIT ) 902 isub-addr =/ 1*( DIGIT / written-sep ) 904 written-sep = ( "-" / "." ) 906 Description of Use: 908 "ISUB" is used to specify the optional ISDN sub-address elements used 909 in ISDN service to reach specific objects on the ISDN service. It can 910 eventually embed written separator elemens for the only scope to 911 enhance human readability. See for further details. 913 Use Restriction: 915 none. 917 Security Considerations: 919 See the Security Consideration section of . 921 Person & email address to contact for further information: 923 Claudio Allocchio 924 Sincrotrone Trieste 925 SS 14 Km 163.5 Basovizza 926 I 34012 Trieste 927 Italy 929 RFC822: Claudio.Allocchio@elettra.trieste.it 930 X.400: C=it;A=garr;P=Trieste;O=Elettra; 931 S=Allocchio;G=Claudio; 932 Phone: +39 40 3758523 933 Fax: +39 40 3758565 935 D.3 - POSTD 937 To: IANA@isi.edu 938 Subject: Registration of new values for the GSTN address 939 qualif-type1 element "POSTD" 941 qualif-type1 "keyword" name: 943 POSTD 945 qualif-type1 "value" ABNF definition: 947 phone-string = 1*( DTMF / pause / tonewait / written-sep ) 949 DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" ) 951 pause = "p" 953 tonewait = "w" 955 written-sep = ( "-" / "." ) 957 Description of Use: 959 POSTD is the optional further dialling sequence needed to access 960 additional services (for example a menu' driven interface) available 961 after the service site has been accessed using gstn-phone. See 962 for further details. 964 Use Restriction: 966 none. 968 Security Considerations: 970 See the Security Consideration section of . 972 Person & email address to contact for further information: 974 Claudio Allocchio 975 Sincrotrone Trieste 976 SS 14 Km 163.5 Basovizza 977 I 34012 Trieste 978 Italy 980 RFC822: Claudio.Allocchio@elettra.trieste.it 981 X.400: C=it;A=garr;P=Trieste;O=Elettra; 982 S=Allocchio;G=Claudio; 983 Phone: +39 40 3758523 984 Fax: +39 40 3758565 986 D.4 - ATTN 988 To: IANA@isi.edu 989 Subject: Registration of new values for the GSTN address 990 qualif-type1 element "ATTN" 992 qualif-type1 "keyword" name: 994 ATTN 996 qualif-type1 "value" ABNF definition: 998 pers-name = [ givenname "." ] [ initials "." ] surname 1000 surname = printablestring 1002 givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" / 1003 "," / "-" / "/" / ":" / "=" / "?" ) 1005 initials = 1*ALPHA 1007 printablestring = 1*( DIGIT / ALPHA / SP / 1008 "'" / "(" / ")" / "+" / "," / "-" / 1009 "." / "/" / ":" / "=" / "?" ) 1011 Description of Use: 1013 To specify the personal name of the individual intended as the 1014 originator or the recipient of the message. See for 1015 further details. 1017 Use Restriction: 1019 none. 1021 Security Considerations: 1023 See the Security Consideration section of . 1025 Person & email address to contact for further information: 1027 Claudio Allocchio 1028 Sincrotrone Trieste 1029 SS 14 Km 163.5 Basovizza 1030 I 34012 Trieste 1031 Italy 1033 RFC822: Claudio.Allocchio@elettra.trieste.it 1034 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1035 S=Allocchio;G=Claudio; 1036 Phone: +39 40 3758523 1037 Fax: +39 40 3758565 1039 D.5 - ORG 1041 To: IANA@isi.edu 1042 Subject: Registration of new values for the GSTN address 1043 qualif-type1 element "ORG" 1045 qualif-type1 "keyword" name: 1047 ORG 1049 qualif-type1 "value" ABNF definition: 1051 string = PCHAR 1053 Description of Use: 1055 To specify the Organization Name (example: ACME Inc.) See 1056 for further details. 1058 Use Restriction: 1060 none. 1062 Security Considerations: 1064 See the Security Consideration section of . 1066 Person & email address to contact for further information: 1068 Claudio Allocchio 1069 Sincrotrone Trieste 1070 SS 14 Km 163.5 Basovizza 1071 I 34012 Trieste 1072 Italy 1074 RFC822: Claudio.Allocchio@elettra.trieste.it 1075 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1076 S=Allocchio;G=Claudio; 1077 Phone: +39 40 3758523 1078 Fax: +39 40 3758565 1080 D.6 - OFNO 1082 To: IANA@isi.edu 1083 Subject: Registration of new values for the GSTN address 1084 qualif-type1 element "OFNO" 1086 qualif-type1 "keyword" name: 1088 OFNO 1090 qualif-type1 "value" ABNF definition: 1092 string = PCHAR 1094 Description of Use: 1096 To specify the Office Number (example: BLD2-44) See 1097 for further details. 1099 Use Restriction: 1101 none. 1103 Security Considerations: 1105 See the Security Consideration section of . 1107 Person & email address to contact for further information: 1109 Claudio Allocchio 1110 Sincrotrone Trieste 1111 SS 14 Km 163.5 Basovizza 1112 I 34012 Trieste 1113 Italy 1115 RFC822: Claudio.Allocchio@elettra.trieste.it 1116 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1117 S=Allocchio;G=Claudio; 1118 Phone: +39 40 3758523 1119 Fax: +39 40 3758565 1121 D.7 - OFNA 1123 To: IANA@isi.edu 1124 Subject: Registration of new values for the GSTN address 1125 qualif-type1 element "OFNA" 1127 qualif-type1 "keyword" name: 1129 OFNA 1131 qualif-type1 "value" ABNF definition: 1133 string = PCHAR 1135 Description of Use: 1137 To specify the Office Name (example: Sales) See 1138 for further details. 1140 Use Restriction: 1142 none. 1144 Security Considerations: 1146 See the Security Consideration section of . 1148 Person & email address to contact for further information: 1150 Claudio Allocchio 1151 Sincrotrone Trieste 1152 SS 14 Km 163.5 Basovizza 1153 I 34012 Trieste 1154 Italy 1156 RFC822: Claudio.Allocchio@elettra.trieste.it 1157 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1158 S=Allocchio;G=Claudio; 1159 Phone: +39 40 3758523 1160 Fax: +39 40 3758565 1162 D.8 - STR 1164 To: IANA@isi.edu 1165 Subject: Registration of new values for the GSTN address 1166 qualif-type1 element "STR" 1168 qualif-type1 "keyword" name: 1170 STR 1172 qualif-type1 "value" ABNF definition: 1174 string = PCHAR 1176 Description of Use: 1178 To specify the Street Address (example: 45, Main Street). 1179 See for further details. 1181 Use Restriction: 1183 none. 1185 Security Considerations: 1187 See the Security Consideration section of . 1189 Person & email address to contact for further information: 1191 Claudio Allocchio 1192 Sincrotrone Trieste 1193 SS 14 Km 163.5 Basovizza 1194 I 34012 Trieste 1195 Italy 1197 RFC822: Claudio.Allocchio@elettra.trieste.it 1198 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1199 S=Allocchio;G=Claudio; 1200 Phone: +39 40 3758523 1201 Fax: +39 40 3758565 1203 D.9 - ADDR 1205 To: IANA@isi.edu 1206 Subject: Registration of new values for the GSTN address 1207 qualif-type1 element "ADDR" 1209 qualif-type1 "keyword" name: 1211 ADDR 1213 qualif-type1 "value" ABNF definition: 1215 string = PCHAR 1217 Description of Use: 1219 To specify the Unformatted Postal Address (example: HWY 14, 1220 Km 94.5 - Loc. Redhill). See for further details. 1222 Use Restriction: 1224 none. 1226 Security Considerations: 1228 See the Security Consideration section of . 1230 Person & email address to contact for further information: 1232 Claudio Allocchio 1233 Sincrotrone Trieste 1234 SS 14 Km 163.5 Basovizza 1235 I 34012 Trieste 1236 Italy 1238 RFC822: Claudio.Allocchio@elettra.trieste.it 1239 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1240 S=Allocchio;G=Claudio; 1241 Phone: +39 40 3758523 1242 Fax: +39 40 3758565 1244 D.10 - ADDU 1246 To: IANA@isi.edu 1247 Subject: Registration of new values for the GSTN address 1248 qualif-type1 element "ADDU" 1250 qualif-type1 "keyword" name: 1252 ADDU 1254 qualif-type1 "value" ABNF definition: 1256 string = PCHAR 1258 Description of Use: 1260 To specify the Unique Postal Name (example: ACMETELEX). See 1261 for further details. 1263 Use Restriction: 1265 none. 1267 Security Considerations: 1269 See the Security Consideration section of . 1271 Person & email address to contact for further information: 1273 Claudio Allocchio 1274 Sincrotrone Trieste 1275 SS 14 Km 163.5 Basovizza 1276 I 34012 Trieste 1277 Italy 1279 RFC822: Claudio.Allocchio@elettra.trieste.it 1280 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1281 S=Allocchio;G=Claudio; 1282 Phone: +39 40 3758523 1283 Fax: +39 40 3758565 1285 D.11 - ADDL 1287 To: IANA@isi.edu 1288 Subject: Registration of new values for the GSTN address 1289 qualif-type1 element "ADDL" 1291 qualif-type1 "keyword" name: 1293 ADDL 1295 qualif-type1 "value" ABNF definition: 1297 string = PCHAR 1299 Description of Use: 1301 To specify the Local Postal Attributes (example: Entrance 3, 1302 3rd floor, Suite 296). See for further details. 1304 Use Restriction: 1306 none. 1308 Security Considerations: 1310 See the Security Consideration section of . 1312 Person & email address to contact for further information: 1314 Claudio Allocchio 1315 Sincrotrone Trieste 1316 SS 14 Km 163.5 Basovizza 1317 I 34012 Trieste 1318 Italy 1320 RFC822: Claudio.Allocchio@elettra.trieste.it 1321 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1322 S=Allocchio;G=Claudio; 1323 Phone: +39 40 3758523 1324 Fax: +39 40 3758565 1326 D.12 - POB 1328 To: IANA@isi.edu 1329 Subject: Registration of new values for the GSTN address 1330 qualif-type1 element "POB" 1332 qualif-type1 "keyword" name: 1334 POB 1336 qualif-type1 "value" ABNF definition: 1338 string = PCHAR 1340 Description of Use: 1342 To specify the Post Office Box (example: CP 1374). See 1343 for further details. 1345 Use Restriction: 1347 none. 1349 Security Considerations: 1351 See the Security Consideration section of . 1353 Person & email address to contact for further information: 1355 Claudio Allocchio 1356 Sincrotrone Trieste 1357 SS 14 Km 163.5 Basovizza 1358 I 34012 Trieste 1359 Italy 1361 RFC822: Claudio.Allocchio@elettra.trieste.it 1362 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1363 S=Allocchio;G=Claudio; 1364 Phone: +39 40 3758523 1365 Fax: +39 40 3758565 1367 D.13 - ZIP 1369 To: IANA@isi.edu 1370 Subject: Registration of new values for the GSTN address 1371 qualif-type1 element "ZIP" 1373 qualif-type1 "keyword" name: 1375 ZIP 1377 qualif-type1 "value" ABNF definition: 1379 string = PCHAR 1381 Description of Use: 1383 To specify Postal ZIP code (example: I 34012). See 1384 for further details. 1386 Use Restriction: 1388 none. 1390 Security Considerations: 1392 See the Security Consideration section of . 1394 Person & email address to contact for further information: 1396 Claudio Allocchio 1397 Sincrotrone Trieste 1398 SS 14 Km 163.5 Basovizza 1399 I 34012 Trieste 1400 Italy 1402 RFC822: Claudio.Allocchio@elettra.trieste.it 1403 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1404 S=Allocchio;G=Claudio; 1405 Phone: +39 40 3758523 1406 Fax: +39 40 3758565 1408 D.14 - CO 1410 To: IANA@isi.edu 1411 Subject: Registration of new values for the GSTN address 1412 qualif-type1 element "CO" 1414 qualif-type1 "keyword" name: 1416 CO 1418 qualif-type1 "value" ABNF definition: 1420 string = PCHAR 1422 Description of Use: 1424 To specify the Country Name (example: Belgium) See 1425 for further details. 1427 Use Restriction: 1429 none. 1431 Security Considerations: 1433 See the Security Consideration section of . 1435 Person & email address to contact for further information: 1437 Claudio Allocchio 1438 Sincrotrone Trieste 1439 SS 14 Km 163.5 Basovizza 1440 I 34012 Trieste 1441 Italy 1443 RFC822: Claudio.Allocchio@elettra.trieste.it 1444 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1445 S=Allocchio;G=Claudio; 1446 Phone: +39 40 3758523 1447 Fax: +39 40 3758565 1449 13. Author's Address 1451 Claudio Allocchio 1452 Sincrotrone Trieste 1453 SS 14 Km 163.5 Basovizza 1454 I 34012 Trieste 1455 Italy 1457 RFC822: Claudio.Allocchio@elettra.trieste.it 1458 X.400: C=it;A=garr;P=Trieste;O=Elettra; 1459 S=Allocchio;G=Claudio; 1460 Phone: +39 40 3758523 1461 Fax: +39 40 3758565 1463 14. References 1465 [1] Allocchio, C., "Minimal PSTN address format in Internet Mail", 1466 RFC 2303, March 1998. 1468 [2] Allocchio, C., "Minimal FAX address format in Internet Mail", 1469 RFC 2304, March 1998. 1471 [3] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping 1472 between X.400 and RFC 822/MIME", RFC 2156, January 1998. 1474 [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax 1475 Specifications", RFC 2234, November 1997. 1477 [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1478 Levels", RFC 2119, March 1997. 1480 [6] ETSI I-ETS 300,380 - Universal Personal Telecommunication (UPT): 1481 Access Devices Dual Tone Multi Frequency (DTMF) sender for acoustical 1482 coupling to the microphone of a handset telephone (March 1995) 1484 [7] ITU E.164 - Numbering plan for the ISDN era; recommendation 1485 E.164/I.331 (August 1991) 1487 [8] ITU T.33 - Facsimile routing utilizing the subaddress; recommendation 1488 T.33 (July, 1996) 1490 [9] ITU F.401 - Message Handling Services: Naming and Addressing for 1491 Public Massage Handling Service; reccommendation F.401 (August 1992) 1493 [10] ITU F.423 - Message Handling Services: Intercommunication Between 1494 the Interpersonal Messaging Service and the Telefax Service; 1495 reccommendation F.423 (August 1992) 1497 [11] Crocker, D., " Standard for the format of ARPA Internet text 1498 messages", STD 11, RFC 822, August 1982. 1500 [12] Braden, R., "Requirements for Internet hosts - application and 1501 support", RFC 1123, October 1989.