1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU T.37 (06/98) SERIES T: TERMINALS FOR TELEMATIC SERVICES Procedures for the transfer of facsimile data via store-and-forward on the Internet ITU-T Recommendation T.37 (Previously CCIlT Recommendation) COPYRIGH
2、T International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesSTD-ITU-T RECMN T.37-ENGL 1998 48b2591 Ob52947 9TL ITU-T T-SERIES RECOMMENDATIONS TERMINALS FOR TELEMATIC SERVICES For furiher details, please refer to ITU-T List of Recommendations. COPYRIGHT Int
3、ernational Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesITU-T RECOMMENDATION T.37 PROCEDURES FOR THE TRANSFER OF FACSIMILE DATA VIA STORE-AND-FORWARD ON THE INTERNET Summary Recommendation T.37 describes the technical features necessary for the Store-and-Fo
4、rward Simple mode of operation of facsimile document transmission via Internet Mail. The general guidelines for the modes of operation of facsimile over the Internet are contained in Recommendation F. 185. Source ITU-T Recommendation T.37 was prepared by ITU-T Study Group 8 (1997-2000) and was appro
5、ved under the WTSC Resolution No. i procedure on the 18th of June 1998. Recommendation T.37 (06/98) 1 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesFOREWORD ITU (International Telecommunication Union) is the United Nations Specialized
6、 Agency in the field of telecommuni- cations. The IT Telecommunication Standardization Sector (IT-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and miff questions and issuing Recommendations on them with a view to standardizing telecommunications on a
7、 worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the IT-T is cover
8、ed by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within IT-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. I I NOTE In this Recommendation, the expression “Administration“ is used for conciseness to
9、 indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no posit
10、ion concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, pr
11、otected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publication may be r
12、eproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recornmendation T.37 (0698) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Servic
13、es - STD-ITU-T RECFN T-3-ENGL 1998 m 48b259l1 Ob52950 496 W CONTENTS Scope Introduction and background References Definitions and abbreviations . 4.1 Definitions . 4.2 Abbreviations Addressing Modes of operation . 6.1 Simple Mode . 6.1.1 Introduction . 6.1.2 Procedures for Simple Mode . 6.2 Full Mod
14、e 6.2.1 Introduction . 6.2.2 Procedures for Full Mode Appendix I . Summary of implementation requirements Simple Mode implementation requirement . Appendix II - Simple Mode coding example Simple Mode coding example . I . 1 11.1 Recommendation T.37 (06198) Page 1 1 1 2 2 2 3 3 3 3 3 4 4 4 4 5 6 6 iii
15、 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesRecommendation T.37 PROCEDURES FOR THE TRANSFER OF FACSIMILE DATA VIA STORE-AND-FORWARD ON THE INTERNET (Geneva, 1998) 1 Scope This Recommendation: a) b) c) d) e) f) defines procedures th
16、at enable facsimile data to be transferred using Internet Email as a store and forward system; supports the requirements of Recommendation F.185; identifies a method for determining the capabilities of a receiving device; identifies a method for providing notification of delivery; does not require c
17、hanges to current IT facsimile Recommendations; permits extensive interworking between facsimile and Internet mail users and facilities, sharing common services where possible. , 2 Introduction and background Recommendation F. 185 defines the guidelines for the support of facsimile document communic
18、ation for both real-time and store-and-forward modes over the Intemet. For store-and-forward facsimile, this Recommendation defines the procedures and message formats. Internet store-and-forward facsimile uses approved IETF protocols for posting, relaying and delivery of documents. It requires no ch
19、anges to Internet standards or to ITU facsimile Recommendations. Such an approach leads to a system that can be used to accomplish interworking between facsimile store-and-forward users and users of general Internet mail. The use of the message formats defined in this Recommendation with other store
20、 and forward systems is outside the scope of this Recommendation. 3 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were vali
21、d. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendati
22、ons is regularly published. - ITU-T Recommendation T.30 ( 1996), Procedures for document facsimile transmission in the general switched telephone network. ITU-T Recommendation T.4 ( 1996), Standardization of Group 3 facsimile terminals for document transmission. CCITT Recommendation T.6 ( 1988), Fac
23、simile coding schemes and coding control functions for Group 4 facsimile apparatus, ITU-T Recommendation E. 164 ( 1997), The international public telecommunications numberingplan. ITU-T Recommendation T.563 ( 1996), Terminal characteristics for Group 4 facsimile apparatus. ITU-T Recommendation F. 18
24、5 (1998), Internet facsimile: Guidelines for the support of the communication of facsimile documents. - - - - - Recommendation T.37 (06/98) 1 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services- - - - - - - - - RFC 822, Standard for the fo
25、rmat of ARPA Internet text messages. RFC 821, Simple Mail Transfer Protocol. RFC 1123, Requirements for Internet hosts -Application andsupport. RFC 1725, Post Ofice Protocol - Version 3. RFC 1891, SMTP Service Extension for Delivery Status Notifications. RFC 1894, An Extensible Message Format for De
26、livery Status Notijcation. RFC 2045, Multipurpose Internet Mail Extensions (MME) Part One: Format of Internet Message Bodies. RFC 2046, Multipurpose Internet Mail Extensions (MME) Part Two: Media Types. RFC 2047, MME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for N
27、on-ASCII Text. RFC 2048, Multipurpose Internet Mail Extensions (MM) Part Four: Registration Procedures. RFC 2049, Multipurpose Internet Mail Extensions (MME) Part Five: Conformance Criteria and Examples. - - I - RFC 230 1, File Format for Internet Fax. - - RFC 2303, Minimal PSTN address format in In
28、ternet Mail. RFC 2304, Minimal FAXaddress format in Internet Mail. - RFC 2305, A Simple Mode of Facsimile Using Internet Mail. 4 Definitions and abbreviations 4.1 Definitions This Recommendation defines the following terms: 4.1.1 4.1.2 receiver: User agent capable of receiving or retrieving Email. s
29、ender: User agent capable of sending Email. I 4.1.3 device: Terminal containing a receiver and/or a sender. 4.1.4 terminals. offramp gateway: Equipment capable of receiving Email and relaying it to one or more G3/G4 facsimile 4.1.5 mailstore: Equipment capable of receiving Email and storing it for l
30、ater retrieval by a receiver 4.1.6 device. The method to be used is outside the scope of this Recommendation. notice: Provision of status information to the originator or recipient in a manner to be determined by the 4.2 Abbreviations All abbreviations are as defined in Recommendations T.30 and F. 1
31、85 unless specifically stated otherwise. DSN Delivery Status Notification Email Electronic Mail ESMTP Extended Simple Mail Transfer Protocol 2 Recommendation T.37 (06/98) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesG3 G4 IETF IFD MA
32、P4 MDN MIME POP3 RFC SMTP TIFF I Addressing Group 3 facsimile Group 4 facsimile Internet Engineering Task Force TIFF Image File Directory Interactive Message Access Protocol Message Disposition Notification Multipurpose Internet Mail Extensions Post Office Protocol version 3 Request For Comment Simp
33、le Mail Transfer Protocol Tagged Image File Format Relevant IETF RFCs 5 Addressing Transport/retneval Internet mail addressing is used to specify the addresses of sending and receiving terminals. Addressing information for the GSTN and ISDN conforms to Recommendation E.164. Mechanisms such as SMTP,
34、ESMTP, POP3.1MAP4 (IETF RFCs) 6 Modes of operation Store-and-forward facsimile may operate in one of two modes. Interoperability is provided by communicating in the Simple Mode as defined below. Ali terminals conforming to this Recommendation and capable of reception must be able to receive in Simpl
35、e Mode. It is recommended that terminals conforming to this Recommendation and capable of transmitting should, as a minimum, be capable of transmitting in Simple Mode. 6.1 Simple Mode This supports the transfer of image data. Capabilities exchange and confirmation of receipt are not required for Sim
36、ple Mode but may be provided using optional Email functions outside the scope of this Recommendation. 6.1.1 Introduction A functional summary of the procedures and related references for Simple Mode is included below. I Image format I RFC 2301 Profile S I 6.1.2 Procedures for Simple Mode Simple Mode
37、 facsimile is achieved when the prescribed image format is sent and received using the prescribed addressing and transportlretrieval systems listed above and as described in sections 2,3 and 4 of RFC 2305. Recommendation T.37 (06/98) 3 COPYRIGHT International Telecommunications Union/ITU Telecommuni
38、cationsLicensed by Information Handling ServicesSTD-ITU-T RECMN T.37-ENGL 3998 4862573 Ob52954 031 mage format Zonfirmation of receipt Note 1) Zapabilities exchange :Note 2) 6.2 Full Mode NOTE - This section is for further study. The information below represents guidelines for the work required to c
39、omplete this section. This supports the transfer of image data. Capabilities exchange and confirmation are required for Full Mode. 6.2.1 Introduction A functional summary of the procedures and related references for Full Mode is included below. RFC 2301 For mailstores and offramp gateways: DSN (RFC
40、1894) For senders and receivers: MDN Required mechanism to emulate the end-to-end nature of facsimile between senders and receivers: MDN Table 2f.37 - Functional summary of procedures for FuU Mode iddressing 1 Relevant IETF RFCs ranspodretrieval (Note 3) Mechanisms such as SMTP, ESMTP, FOP3, IMAP4 (
41、IETF RFCs) NOTE 1 - MDN is defined within the IETF. NOTE 2 - Extensions to MDN are discussed in on-going work within the IETF. It is likely that there will be many aitemativi mechanisms for the requestldelivery of capabilities but this Recommendation will identify a default mechanism which will bi r
42、equired by all senders and receivers using Full Mode. This Recommendation will also identify mechanisms which will be requirec by gateways and mailstores and which may be strongly recommended or optional for senders, receivers, gateways and mailstore. The capability parameters to be provided are dis
43、cussed in on-going work within the IETF. This Recommendation will identif facsimile-related parameters that may be requested by senders and which are required to be provided by receivers. Thi Recommendation will also identify parameters which will be required by gateways and mailstore and which may
44、be strong1 recommended or optional for senders, receivers, gateways and mailstores. NOTE 3 - Devices supporting Full Mode may use any currently approved Internet Mail transport or security mechanisms or any such mechanisms, or extension to such mechanisms, which may be approved in the future. The sp
45、ecific definition of these mechanisms, or future extensions to these mechanisms, is outside the scope of this Recommendation. NOTE 4 -The requirement for onramp and offramp gateways to support G4 facsimile terminals is for further study. 6.2.2 Procedures for Full Mode Full Mode facsimile is achieved
46、 when the prescribed image format is sent and received using the prescribed addressing and transpodretrieval systems listed above. These procedures are for further study. Appendix I Summary of implementation requirements This appendix summarises and indexes the key implementation points covered else
47、where in this Recommendation. It is provided for information only. 4 Recommendation T.37 (06/98) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesSTD=ITU-T RECMN T.37-ENGL 1998 48b2591 Ob52955 T78 Provide notice on receipt of DSN or othe
48、r notifications 1.1 Simple Mode implementation requirement Table I.lR.37 - Implementation requirements for Simple Mode RFC 1894 I Sender Required Be MIME compliant except that it is not required to offer to place a MIME attachment in a file and may print a received file rather than display Be capabl
49、e of processing multiple MIME RFC 2301 Profile S image files within a single message Provide notice in case of reception or processing problems Use other TIFF Profiles (e.g. RFC 2301 Profile F for G4) Optional Required L RFC 2305 0 2.2.2 RFC 2305 0 2.2.4 RFC 2305 0 2.3.2 RFC 2305 8 4 Strongly recommended Use a mailbox access protocol when serving a single mail recipient Optional L RFC 2305 0 2.1.3 Send image data as a single MIME multi-page RFC 2301 Profile S file I RFC 2305 4 2.2.3 Mailstore (When implemented) Required Be SMTP compliant RFC
