idnits 2.17.1 draft-ietf-fax-mime-fullmode-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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 29 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 69 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 == Line 12 has weird spacing: '...cuments of th...' == Line 481 has weird spacing: '...nent of the m...' == Line 727 has weird spacing: '... LSB of octet...' == Line 787 has weird spacing: '... LSB of octet...' == Line 1017 has weird spacing: '...rnished to...' == (7 more instances...) == 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 (20 October 1998) is 9319 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: '1' is defined on line 981, but no explicit reference was found in the text ** Obsolete normative reference: RFC 821 (ref. '1') (Obsoleted by RFC 2821) ** Obsolete normative reference: RFC 822 (ref. '2') (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 2298 (ref. '3') (Obsoleted by RFC 3798) -- Possible downref: Non-RFC (?) normative reference: ref. '5' ** Obsolete normative reference: RFC 1892 (ref. '6') (Obsoleted by RFC 3462) -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' Summary: 13 errors (**), 0 flaws (~~), 11 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Fax Working Group Toru Maeda 2 Internet Draft CANON Inc 3 Expires: April 1999 20 October 1998 5 MIME content-type for Internet Fax Full Mode 7 draft-ietf-fax-mime-fullmode-01.txt 9 Status of this memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet-Drafts as reference 19 material or to cite them other than as "work in progress." 21 To view the entire list of current Internet-Drafts, please check 22 the "1id-abstracts.txt" listing contained in the Internet-Drafts 23 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 24 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 25 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 26 (US West Coast). 28 Abstract 30 This memo defines a mechanism and formats for the Internet FAX Full 31 Mode using a MIME content-type and an extended Message Disposition 32 Notifications (MDN). Both of the MIME content-type and the extended 33 MDN should be used by a mail user agent (UA) which is capable of 34 Internet Fax Full Mode with capabilities exchange and confirmation of 35 receipt. 37 The MIME content-type that is used by Internet Fax Full Mode capable 38 agent (UA) or electronic mail gateway to request, to response, and to 39 receive the capabilities of recipient. This content-type is intended 40 to be machine-processable. Additional message headers are also defined 41 to permit capabilities exchange in the Internet Fax Full Mode. 43 The extended Message Disposition Notifications (MDN) that is used by a 44 mail user agent (UA) which is capable of Internet Fax Full Mode for 45 processing confirmation. This content-type is intended to be 46 machine-processable. Additional message headers are also defined to 47 permit that the sender (of the message) requires Message Disposition 48 Notifications (MDNs). MDN is "An Extensible Message Format for Message 49 Disposition Notification" in RFC2298. 51 MIME for Internet Fax Full Mode 20 October 1998 52 Internet Draft 54 Table of Contents 56 1. Introduction ...........................................3 58 2. Method of capability exchange and confirmation .........6 60 3. Capability exchange phase ..............................8 62 4. Message transmission and confirmation phase ...........12 64 5. Security considerations ...............................16 66 6. Collected Grammar .....................................17 68 7. Example ...............................................25 70 8. Acknowledgments .......................................28 72 9. References ............................................28 74 10. Copyright .............................................29 76 11. Author's Address ......................................29 78 MIME for Internet Fax Full Mode 20 October 1998 79 Internet Draft 81 1. Introduction 83 This memo defines a mechanism and format for Internet FAX Full Mode 84 with capabilities exchange and confirmation using a MIME content-type fax 85 and an extended message disposition notifications (MDNs). Internet FAX 86 Full Mode which has capabilities exchange and confirmation is defined in 87 ITU-T F.185 [7] and T.37 [8]. The MIME content-type fax can be used to 88 exchange Internet FAX recipient capabilities. An extended MDN will be 89 used for terminal to terminal processing confirmation in Internet FAX 90 Full Mode. 92 The purpose is to extend Internet Mail to support functionality of 93 Internet Fax Full Mode. The protocol described 94 in this memo provides for the capabilities exchange, in addition to 95 those normally used in Internet Mail. 97 The MIME content-type fax will be used for terminal to terminal 98 capabilities exchange in Internet FAX Full Mode. 99 Capability exchange more than Internet FAX such as MS Word 100 application or PDF file are out of scope. 102 The extended message disposition notifications (MDNs) for Internet FAX 103 Full Mode. MDN is defined in "An Extensible Message Format for Message 104 Disposition Notification" in RFC2298 [3]. An extended MDN can be used 105 to notify the sender of a message of any of several conditions that may 106 occur after successful delivery, such as reception of the Internet FAX 107 Full Mode or the recipient error in process of the Internet FAX Full Mode. 108 The "message/disposition-notification" content-type defined herein is 109 intended for use within the framework of the "multipart/report" 110 content type defined in RFC 1892 [6]. 112 Additional attributes may also be defined to support "tunneling" of 113 Internet Fax Full Mode through Internet Mail. 115 Internet FAX Full Mode is defined in F.185 as follows; 117 (a) Capabilities of the terminals are exchanged. 119 (b) An acknowledgment of receipt is exchanged between gateways 120 and may be transferred from the receiving terminal to sending 121 terminal 123 (c) The contents of standard messages used by the transmitting 124 terminal are preserved 126 The key words "MUST","MUST NOT","REQUIRED","SHALL","SHALL NOT", 127 "SHOULD","SHOULD NOT","RECOMENDED","MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC 2119. 130 MIME for Internet Fax Full Mode 20 October 1998 131 Internet Draft 133 1.1 Purposes 135 The MIME content-type fax and the additional MIME content-type for 136 extended message disposition notifications (MDNs)defined in this memo 137 are expected to serve several purposes: 139 (a) Allow a sender of Internet FAX Full Mode to request 140 capabilities of recipient's Internet FAX Full Mode in terminal 141 to terminal communication; 143 (b) Notify capabilities of recipient's Internet FAX Full Mode to 144 the sender of Internet FAX Full Mode. 146 (c) Allow a sender of Internet FAX Full Mode to send image using 147 full function of TIFF-FX based on notified capabilities of 148 recipient's Internet FAX Full Mode and to send command and to 149 request report of recipient's Internet FAX Full Mode; 151 (d) Notify report of recipient's Internet FAX Full Mode to the 152 sender of Internet FAX Full Mode with part of received message, 153 and may notify capabilities 155 (e) Inform human beings of the disposition of messages after 156 Successful delivery of Internet FAX Full Mode message, in a 157 manner which is largely independent of human language; 159 (f) Allow Language-independed, yet reasonably precise, indications 160 of the disposition of a message to be delivered in Internet 161 FAX Full Mode. 163 (g) Allow G3FAX applications such as Polling, Selective Polling, 164 Subaddress, Relay, Password, BFT and NSF based on ITU-T T.30 165 protocol. 167 MIME for Internet Fax Full Mode 20 October 1998 168 Internet Draft 170 1.2 Requirements 172 These purposes place the following constraints on the capability 173 exchange and confirmation protocol: 175 (a) It must be readable by humans as well as being machine 176 parsable for Internet FAX Full mode. 178 (b) It must be provide enough information to allow Internet FAX 179 Full Mode message senders to unambiguously associate 180 the MIME content-type fax with the message that was sent and 181 the original recipient 182 address for which the MIME content-type fax is issued. 184 (c) It must also be able to describe the disposition of a Internet 185 FAX Full Mode message independent of any particular human 186 language or of the terminology of any particular mail system. 188 (d) The specification must be extensible in order to accommodate 189 future requirements of Internet FAX Full Mode. 191 1.3 The MIME content-type fax 193 For the purposes, the MIME content-type fax is defines as 194 follows for Internet FAX Full Mode. 196 (a) The MIME content-type fax is send automatically. 197 The operator should recognize that 198 Internet FAX full Mode sends the MIME content-type fax 199 by default setting. 201 (b) An empty message may be used for capability request. 203 1.4 Extension from MDN 205 For the purposes, MDS in RFC2298 [3] is extended and modified as 206 follows for Internet FAX Full Mode. 208 (a)MDN is send automatically. The operator should recognize that 209 Internet FAX full Mode sends MDN by default setting. 211 MIME for Internet Fax Full Mode 20 October 1998 212 Internet Draft 214 2. Method of capability exchange and confirmation 216 A communication between Internet FAX Full Mode machines consists of 217 two phases that are the capability exchange phase and the message 218 transmission and confirmation phase. 220 In the capability exchange phase, a sender of Internet FAX Full Mode 221 sends a capability request using the MIME content-type fax. 222 A recipient of Internet FAX Full Mode must immediately return message 223 with its capabilities using the MIME content-type fax. 225 In the message transmission and confirmation phase, based on this 226 reply messages, the sender sends message and command data using the 227 MIME content-type fax and sends confirmation request using a request 228 for extended MDN. The recipient must immediately returns confirmation 229 message after the processing of image using the extended MDN. 230 The confirmation message of the extended MDN includes human 231 readable message, completion code, total received page, error page 232 numbers, partial or full received message. The confirmation message 233 may include capabilities of recipient using the MIME content-type fax. 235 Capability exchange phase and message transmission and confirmation 236 phase are independent, and not required to succeeded. A sender may 237 perform capability exchange phase only when capabilities of the 238 destination is registered in machine, and perform the message 239 transmission and confirmation phase for every transmission. 241 A sender may not perform capability exchange phase when the 242 transmitting message is LCD. 244 MIME for Internet Fax Full Mode 20 October 1998 245 Internet Draft 247 2.1 The message/fax content-type 249 The message/fax content-type is defined as follows: 251 MIME type name: message 252 MIME subtype name: fax 253 Optional parameters: none 254 Encoding considerations: "7bit" encoding is sufficient and 255 MUST be used to maintain readability 256 when viewed by non-MIME mail 257 readers. 258 Security considerations: discussed in section 5 of this memo. 260 The message/fax report type for use in the multipart/report is "fax". 262 The body of a message/fax consists of one or more "fields" formatted 263 according to the ABNF of RFC 822 header "fields" (see [2]). 264 Using the ABNF of RFC 822, the syntax of the message/fax content is as 265 follows: 267 fax-content = [ reporting-ua-field CRLF ] 268 [ fax-gateway-field CRLF ] 269 [ original-recipient-field CRLF ] 270 final-recipient-field CRLF 271 [ original-message-id-field CRLF ] 272 disposition-field CRLF 273 *( failure-field CRLF ) 274 *( error-field CRLF ) 275 *( warning-field CRLF ) 276 *( extension-field CRLF ) 278 MIME for Internet Fax Full Mode 20 October 1998 279 Internet Draft 281 3. Capability exchange phase 283 A sender of Internet FAX Full Mode sends a capability request using a 284 request for the MIME content-type fax. A recipient of Internet FAX Full 285 Mode must immediately return a message with capabilities of Internet FAX 286 Full Mode using the MIME content-type fax. Capabilities of Internet FAX 287 Full Mode is expressed using FCF and FIF in CCITT T.30. 289 3.1 Capability request 291 Capability request is requested by including the MIME content-type fax. 292 Further information to be used by the recipient of Internet FAX Full 293 Mode in generating the capability request may be provided. 295 A capability request should contain a Message-ID header as specified 296 in RFC 822[2]. 298 3.1.1 Fax-To Header 300 A request that the receiving Internet FAX Full Mode user agent issue 301 fax notifications is made by placing a Fax-To header 302 into the message. The syntax of the header, using the ABNF of RFC 303 822 [2], is 305 fax-request-header = "Fax-To" ":" 1#mailbox 307 The mailbox token is as specified in RFC 822 [2]. 309 MIME for Internet Fax Full Mode 20 October 1998 310 Internet Draft 312 3.1.2 Fax-Options Header 314 Fax-Options header provides a request of capability exchange 315 in Internet FAX Full Mode. 317 Fax-Options = 318 "Fax-Options" ":" 319 fax-parameters 321 fax-parameters = 322 parameter *(";" parameter) 324 parameter = "G3Fax-capability-request" "=" "required" 326 3.1.3 Message-ID 328 A message that contains capability request for Internet FAX Full Mode 329 should contain a Message-ID header as specified in RFC 822[2]. 331 MIME for Internet Fax Full Mode 20 October 1998 332 Internet Draft 334 3.2 capability response 336 A capability response message is the MIME content-type fax. 338 (a) The report-type parameter of the multipart/report content is 339 "fax". 341 (b) The first component of the multipart/report contains a human 342 readable explanation, as described in RFC 1892 [6]. 344 (c) The second component of the multipart/report is of 345 content-type message/fax, described in 346 section of this document. 348 The capability response must be addressed to the address from the 349 Fax-To header from the original message for which 350 the capability response is being generated. 352 The RFC822 From filed of the capability response MUST 353 contain the address of the Internet FAX Full Mode machine for which 354 the capability response is being issued. 356 3.2.1 The message/fax content-type 358 The message/fax content-type for capability 359 response message is as defined in the section of this document. 361 The syntax of the message/fax content is 362 as defined in the section of this document. 364 3.2.2 Final-Recipient-field 366 The Final-Recipient field indicates the recipient for which the 367 capability response is being issued. 369 3.2.3 Original-message-ID 371 The Original-Message-ID field indicates the message-ID of the message 372 for which the capability response is being issued. This field must be 373 present. 375 MIME for Internet Fax Full Mode 20 October 1998 376 Internet Draft 378 3.2.4 Fax-field 380 The Fax filed indicates the action performed by the recipient 381 of Internet FAX Full Mode. This filed must be present. 382 Fax-modifier（ G3Fax-capability-request） will be used for 383 capability response. 385 The syntax for the Fax filed is: 387 Fax: automatic-action/FAX-sent-Automatically 388 ; processed / G3Fax-capability-request 390 3.2.5 Extension-field 392 Additional Fax field is defined for capability response. Capabilities 393 of recipient is expressed using FCF and FIF in T30 frame format [5]. 395 field = "G3Fax-t30frame" ":" G3Fax-t30frame-field 397 G3Fax-t30frame-field = parameter * ( ";" parameter ) 399 parameter = "G3Fax-t30frame-parameter" 401 G3Fax-t30frame-parameter = 402 "G3Fax-t30frame" "=" t30-fcf [ "," t30-fif ] 404 MIME for Internet Fax Full Mode 20 October 1998 405 Internet Draft 407 4. message transmission and confirmation phase 409 The sender sends message and command data using the MIME content-type 410 fax based on previously received messages from the recipient Internet 411 FAX Full Mode and sends confirmation request using extended MDN. 413 The recipient SHOULD return confirmation message immediately after the 414 processing of image using extended MDN. 415 The confirmation message includes human readable message, completion 416 code, total received page, error page numbers, part or full message of 417 received using extended MDN and capabilities of recipient using the MIME 418 content-type fax. 420 4.1 message 422 The sender sends message and command data based on previous knowledge of 423 recipient Internet FAX Full Mode using the MIME content-type fax. 425 4.2 Message transmission and confirmation request 427 Confirmation request message is requested by including 428 the extended MDN with the message. Further information to be used by the 429 recipient Internet FAX Full Mode in generating the confirmation request 430 may be provided by including the extended MDN. 432 A message that contains confirmation request, should contain 433 the extended MDN. 435 A message that contains confirmation request, should contain a 436 Message-ID header as specified in RFC 822[2]. 438 4.2.1 Fax-To Header 440 A request that the receiving Internet FAX Full mode issue confirmation 441 is made by placing a Fax-To header into the message. 443 MIME for Internet Fax Full Mode 20 October 1998 444 Internet Draft 446 4.2.2 Disposition-Notification-Options Header 448 Disposition-Notification-Options header provides a request of 449 confirmation and command in Internet FAX Full Mode. Command is 450 expressed using FCF and FIF defined in CCITT T.30 frame[5]. 452 Disposition-Notification-Options = 453 "Disposition-Notification-Options" ":" 454 disposition-notification-parameters 456 disposition-notification-parameters = parameter *(";" parameter) 458 parameter = "G3Fax-report-request" "=" "required" 460 parameter = "G3Fax-frame" "=" t30-fcf [ "," t30-fif ] 462 4.2.3 Message-ID 464 A message that contains confirmation request for Internet FAX Full Mode 465 should contain a Message-ID header as specified in RFC 822 [2]. 467 MIME for Internet Fax Full Mode 20 October 1998 468 Internet Draft 470 4.3 confirmation 472 A confirmation message is a MIME message with a top level content-type 473 of multipart/report (defined in RFC 1892 [6]). 475 (a) The report-type parameter of the multipart/report content is 476 "disposition-notification". 478 (b) The first component of the multipart/report contains a human 479 readable explanation of the MDN, as described in RFC 1892. 481 (c) The second component of the multipart/report is of content- 482 type message/disposition-notification, described in section 483 of this document. 485 (d) If the original message or a portion of the message or report 486 is to be returned to the sender. The decision of whether or 487 not to return the message or report is up to the Internet FAX 488 Full Mode recipient. 490 The confirmation must be addressed to the address from the Disposition- 491 Notification-To header from the original message for which the 492 confirmation is being generated. 494 The From filed of the message header of the confirmation must contain 495 the address of the Internet FAX Full Mode machine for which 496 confirmation is being issued. 498 4.3.1 The message/disposition-notification content-type 500 The message/disposition-notification content-type for confirmation 501 message is as defined in RFC2298[3]. 503 The syntax of the message/disposition-notification content is 504 as defined in RFC2298[3]. 506 4.3.2 final-recipient-field 508 The Final-Recipient field indicates the recipient of Internet FAX for 509 which the confirmation is being issued. 511 MIME for Internet Fax Full Mode 20 October 1998 512 Internet Draft 514 4.3.3 Original-message-ID 516 The Original-Message-ID field indicates the message-ID of the message 517 for which the confirmation is being issued. This field must be present. 519 4.3.4 disposition-field 521 The Disposition filed indicates the action performed by the recipient 522 of Internet FAX Full Mode. This filed must be present. disposition- 523 modifier（ G3Fax-report-request） will be used for confirmation. 525 The syntax for the Disposition filed is: 527 Disposition: automatic-action/MDN-sent-Automatically 528 ; processed / G3Fax-report-request 530 4.3.5　extension-field 532 (1) confirmation 533 Additional MDN field is defined for confirmation. confirmation of 534 recipient is expressed using result code, received page number and 535 error page number. 537 G3Fax-Report: G3Fax-Results=code 538 ;G3Fax-Pages=received page number 539 ;G3Fax-Errorpage=error page number 541 4.3.6 capability response 543 A capability response message is the MIME content-type fax as defined 544 in Sec. 3.2. 546 MIME for Internet Fax Full Mode 20 October 1998 547 Internet Draft 549 5. Security considerations 551 The following security considerations apply when using 552 the MIME content-type fax for Internet FAX Full Mode: 554 MIME for Internet Fax Full Mode 20 October 1998 555 Internet Draft 557 6. Collected Grammar 559 6.1 MIME content-type fax 561 The grammar for the MIME content-type fax will be described. 563 NOTE: The following lexical tokens are defined in RFC 822: atom, 564 CRLF, mailbox, msg-id, text. The definitions of attribute and value 565 are as in the definition of the Content-Type header in RFC 2045 [4]. 567 Message headers: 569 fax-request-header = "Fax-To" ":" 1#mailbox 571 Fax-Options = 572 "Fax-Options" ":" 573 fax-parameters 575 fax-parameters = parameter *(";" parameter) 577 parameter = attribute "=" importance "," 1#value 579 importance = "required" / "optional" 581 original-recipient-header = 582 "Original-Recipient" ":" address-type ";" generic-address 584 Report content: 586 fax-content = [ reporting-ua-field CRLF ] 587 [ fax-gateway-field CRLF ] 588 [ original-recipient-field CRLF ] 589 final-recipient-field CRLF 590 [ original-message-id-field CRLF ] 591 fax-field CRLF 592 *( failure-field CRLF ) 593 *( error-field CRLF ) 594 *( warning-field CRLF ) 595 *( extension-field CRLF ) 597 address-type = atom 599 mta-name-type = atom 601 reporting-ua-field = "Reporting-UA" ":" ua-name 602 [ ";" ua-product ] 604 MIME for Internet Fax Full Mode 20 October 1998 605 Internet Draft 607 ua-name = *text 609 ua-product = *text 611 fax-gateway-field = "FAX-Gateway" ":" mta-name-type ";" mta-name 613 mta-name = *text 615 original-recipient-field = 616 "Original-Recipient" ":" address-type ";" generic-address 618 generic-address = *text 620 final-recipient-field = 621 "Final-Recipient" ":" address-type ";" generic-address 623 fax-field = "Fax" ":" fax-mode ";" 624 fax-type 625 [ '/' fax-modifier 626 *( "," fax-modifier ) ] 628 fax-mode = action-mode "/" sending-mode 630 action-mode = "manual-action" / "automatic-action" 632 sending-mode = "FAX-sent-manually" / "FAX-sent-automatically" 634 disposition-type = "displayed" 635 / "dispatched" 636 / "processed" 637 / "deleted" 638 / "denied" 639 / "failed" 641 fax-modifier = ( "error" / "warning" ) 642 / ( "superseded" / "expired" / 643 "mailbox-terminated" ) 644 / fax-modifier-extension 646 fax-modifier-extension = atom 648 original-message-id-field = "Original-Message-ID" ":" msg-id 650 failure-field = "Failure" ":" *text 652 error-field = "Error" ":" *text 654 warning-field = "Warning" ":" *text 656 extension-field = extension-field-name ":" *text 658 extension-field-name = atom 660 MIME for Internet Fax Full Mode 20 October 1998 661 Internet Draft 663 6.1.1 Fax-Options header parameter names 665 6.1.1.1 G3Fax-capability-request 667 This is the parameter for Internet FAX capability request. 669 (a)proposed parameter name 671 G3Fax-capability-request 673 (b)syntax 675 Fax-Options : 676 "Fax-Options" ":" 677 "G3Fax-capability-request"　"=" "required" 679 (c)parameter values 681 G3Fax-capability-request is capability request of Internet 682 FAX Full mode 684 MIME for Internet Fax Full Mode 20 October 1998 685 Internet Draft 687 6.1.1.2 G3Fax-t30frame-parameter 689 This is the parameter for Recipient capabilities of Internet FAX Full 690 Mode. 692 (a)proposed parameter name 694 G3Fax-t30frame-parametert 696 (b)syntax 698 Fax-Options : 699 "Fax-Options" ":" 700 fax-parameters 702 fax-parameters = 703 parameter * ( ";" parameter ) 705 parameter = "G3Fax-t30frame-parameter" 707 G3Fax-t30frame-parameter = 708 "G3Fax-t30frame" "=" t30-fcf [ "," t30-fif ] 710 t30-fcf = *text 712 t30-fif = *text 714 (c)parameter values 716 t30-fcf =*text is hexadecimal expression of FCF octet in T.30. 717 Some FCFs are as follows; 718 NSF 20 719 CSI 40 720 DIS 80 721 NSS 23 722 TSI 43 723 DCS 83 725 t30-fif =*text is Hexadecimal expression of FIF octets in T.30. 726 The first octet of FIF is located in first character in text. 727 LSB of octet is the first bit of FIF. 729 MIME for Internet Fax Full Mode 20 October 1998 730 Internet Draft 732 6.1.2 fax modifier names 734 6.1.2.1 G3Fax-capability-request 736 (a)fax-modifier name 738 G3Fax-capability-request 740 (b)semantics 742 capability request of Internet FAX full Mode 744 MIME for Internet Fax Full Mode 20 October 1998 745 Internet Draft 747 6.1.3 MIME field names 749 6.1.3.1 G3Fax-t30frame 751 This is the field for Command data from sender in Internet FAX Full 752 Mode. 754 (a)field name 756 G3Fax-t30frame-field 758 (b)syntax 760 field = "G3Fax-t30frame" ":" G3Fax-t30frame-field 762 G3Fax-t30frame-field = parameter * ( ";" parameter ) 764 parameter = "G3Fax-t30frame-parameter" 766 G3Fax-t30frame-parameter = 767 "G3Fax-t30frame" "=" t30-fcf [ "," t30-fif ] 769 t30-fcf = *text 771 t30-fif = *text 773 (c)field value 775 t30-fcf =*text is hexadecimal expression of FCF in T.30 777 Some FCFs are as follows; 778 NSF 20 779 CSI 40 780 DIS 80 781 NSS 23 782 TSI 43 783 DCS 83 785 t30-fif =*text is Hexadecimal expression of FIF octets in T.30. 786 The first octet of FIF is located in first character in text. 787 LSB of octet is the first bit of FIF. 789 MIME for Internet Fax Full Mode 20 October 1998 790 Internet Draft 792 6.2 Additional grammar for MDN 794 Additional grammar for MDN is described in IANA registration form. 796 6.2.1 IANA registration for Disposition-Notification-Options header 797 parameter names 799 6.2.1.1 G3Fax-report-request 801 This is the parameter for Internet FAX confirmation request. 803 (a)proposed parameter name 805 G3Fax-report-request 807 (b)syntax 809 Disposition-Notification-Options : 810 "Disposition-Notification-Options" ":" 811 "G3Fax-report-request"　"=" "required" 813 (c)parameter values 815 G3Fax-report-request is confirmation request of Internet 816 FAX Full Mode. 818 6.2.2 IANA registration for disposition modifier names 820 6.2.2.1 G3Fax-report-request 822 (a)disposition-modifier name 824 G3Fax-report-request 826 (b)semantics 828 capability request of Internet FAX Full Mode 830 MIME for Internet Fax Full Mode 20 October 1998 831 Internet Draft 833 6.2.3 IANA registration for MDN extension field names 835 6.2.3.1 G3Fax-Report 837 This is the field foe confirmation of Internet FAX Full Mode 839 (a)field name 841 G3Fax-Report-field 843 (b)syntax 845 field = "G3Fax-Report" ":" results 846 ; pages 847 ; errorpage 849 results = "G3Fax-Results" "=" code 851 pages = "G3Fax-Pages" "=" numeric 853 errorpage = "G3Fax-Errorpage" "=" numeric * ( "," numeric ) 855 (c)field value 857 results =code is as follows; 858 "00" Successful reception 859 "01" Unsuccessful reception 860 "02" Capabilities mismatch. The receiving terminal cannot 861 interpret the message data correctly 862 "03" does not support the format used in this message 863 "04" does not support relay feature 865 pages =numeric is total page. 867 errorpage =numeric is error page number 869 MIME for Internet Fax Full Mode 20 October 1998 870 Internet Draft 872 7. Example 874 7.1 Capability request 876 Date: Wed,20 Sep 1995 00:19:00 (EDT)-0400 877 From: Jane Sender 878 Message-Id: <199509200019.12345@huge.com> 879 Subject: Internet FAX Full Mode Capability Request 880 To: Tom Recipient 881 Fax-To: Jane_Sender@huge.com 882 Fax-Options: G3Fax-capability-request=required 884 7.2 Capability response 886 Date: Wed,20 Sep 1995 00:19:00 (EDT)-0400 887 From: Tom Recipient 888 Message-Id: <199509200020.12345@mega.edu> 889 Subject: Internet FAX Full Mode Capability Response 890 To: Jane Sender 891 MIME-Version: 1.0 892 Content-Type: multipart/report; report-type=fax; 893 boundary="RAA14128.773615766/mega.edu" 895 --RAA14128.773615766/mega.edu 897 The message sent on 1995 Sep 19 at 00:18:00 (EDT) -0400 to 898 Tom Recipient with subject " Internet FAX Full 899 Mode Capability Request " has been processed in Internet FAX Full Mode. 901 --RAA14128.773615766/mega.edu 902 Content-Type: message/fax 904 Reporting-UA: Toms-pc.cs.mega.edu; IFAX-FullMode 905 Original-Recipient: rfc822;Tom-Recipient@mega.edu 906 Final-Recipient: rfc822;Tom-Recipient@mega.edu 907 Original-Message-ID: <199509200019.12345@huge.com> 908 Disposition: automatic-action/FAX-sent-automatically; 909 processed / G3Fax-capability-request 910 G3Fax-t30frame:G3Fax-frame=40,3333333320323220313131; 911 G3Fax-frame=20,000011; 912 G3Fax-frame=80,00CF79 914 --RAA14128.773615766/mega.edu-- 916 MIME for Internet Fax Full Mode 20 October 1998 917 Internet Draft 919 7.3 Message and confirmation request 921 Date: Wed,20 Sep 1995 00:21:00 (EDT)-0400 922 From: Jane Sender < Jane_Sender@huge.com> 923 Message-Id: <199509200021.12345@huge.com> 924 Subject: Internet FAX Full Mode Image Transmission 925 To: Tom Recipient 926 MIME-Version: 1.0 927 Disposition-Notification-To: Jane_Sender@huge.com 928 Fax-To: Jane_Sender@huge.com 929 Fax-Options:G3Fax-report-request=required; 930 G3Fax-frame=43,3737373720383820393939; 931 G3Fax-frame=23,000011; 932 G3Fax-frame=83,00C679 933 Content-Type: multipart/ mixed; 934 boundary="RAA14128.773615768/ huge.com" 936 --RAA14128.773615768/huge.com 937 Content-type: text/plain; charset=us-ascii 939 [original text message goes here] 941 --RAA14128.773615768huge.com 942 Content-type: image/ tiff; application=faxbw 943 Content-Transfer-Encoding: base64 945 [original TIFF-FX message goes here] 947 --RAA14128.773615768/ huge.com-- 949 MIME for Internet Fax Full Mode 20 October 1998 950 Internet Draft 952 7.4 Confirmation 954 Date: Wed,20 Sep 1995 00:22:00 (EDT)-0400 955 From: Tom Recipient 956 Message-Id: <199509200022.12345@mega.edu> 957 Subject: Internet FAX Full Mode Disposition notification 958 To: Jane Sender 959 MIME-Version: 1.0 960 Content-Type: message/disposition-notification 962 Reporting-UA: Toms-pc.cs.mega.edu; IFAX-FullMode 963 Original-Recipient: rfc822;Tom-Recipient@mega.edu 964 Final-Recipient: rfc822;Tom-Recipient@mega.edu 965 Original-Message-ID: <199509200021.12345@huge.com> 966 Disposition: automatic-action/MDN-sent-automatically; 967 processed / G3Fax-report-request 968 G3Fax-Report:G3Fax-Results=00; 969 G3Fax-Pages=5 971 --RAA14128.773615769/mega.edu-- 973 MIME for Internet Fax Full Mode 20 October 1998 974 Internet Draft 976 8. Acknowledgments 978 Dan Wing provided valuable comments on this draft. 980 9. References 981 [1] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, 982 August 1982. 984 [2] Crocker, D., "Standard for the Format of ARPA Internet Text 985 Messages", STD 11, RFC 822, August l982. 987 [3] Fajman, R. "An Extensible Message Format for Message Disposition 988 Notification", RFC 2298, March 1998. 990 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 991 Levels", RFC 2119, March 1997. 993 [5] ITU-T (CCITT), "Procedures for Document Facsimile Transmission in 994 the General Switched Telephone Network ", ITU-T (CCITT) 995 Recommendation T.30. 997 [6] Vaudreuil, G., "The Multipart/Report Content Type for the 998 Reporting of Mail System Administrative Messages", RFC 1892, 999 Octel Network Services, January 1996. 1001 [7] ITU-T, "Internet Facsimile: Guidelines for the Support of the 1002 Communication of Facsimile Documents", ITU-T Recommendation 1003 F.185 1005 [8] ITU-T, "Procedures for the Transfer of Facsimile Data via Store 1006 and Forward on the Internet", ITU-T Recommendation 1007 T.37 1009 MIME for Internet Fax Full Mode 20 October 1998 1010 Internet Draft 1012 10. Copyright 1014 Copyright (C) The Internet Society (1997, 1998). All Rights 1015 Reserved. 1017 This document and translations of it may be copied and furnished to 1018 others, and derivative works that comment on or otherwise explain it 1019 or assist in its implementation may be prepared, copied, published and 1020 distributed, in whole or in part, without restriction of any kind, 1021 provided that the above copyright notice and this paragraph are 1022 included on all such copies and derivative works. However, this 1023 document itself may not be modified in any way, such as by removing 1024 the copyright notice or references to the Internet Society or other 1025 Internet organizations, except as needed for the purpose of developing 1026 Internet standards in which case the procedures for copyrights defined 1027 in the Internet Standards process must be followed, or as required to 1028 translate it into languages other than English. 1030 The limited permissions granted above are perpetual and will not be 1031 revoked by the Internet Society or its successors or assigns. 1033 This document and the information contained herein is provided on an 1034 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1035 TASK FORCE DISCLAIMS ALLWARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1036 BUT NOT LIMITED TOANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 1037 WILL NOTINFRINGE ANY RIGHTS OR ANY IMPLIED 1039 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1041 11. Author's Address 1043 Toru MAEDA 1044 CANON Inc 1045 3-30-2,Shimomaruko, Ohtaku, 1046 Tokyo, Japan 1048 Email: maeda@ffm.canon.co.jp 1049 Voice: +81 3 3757 9738 1050 Fax: +81 3 3757 8205