Network Working Group                                      C. Allocchio
Request for Comments: 2304                                   GARR-Italy
Category: Standards Track                                    March 1998
        
Network Working Group                                      C. Allocchio
Request for Comments: 2304                                   GARR-Italy
Category: Standards Track                                    March 1998
        

Minimal FAX address format in Internet Mail

Internet邮件中的最小传真地址格式

Status of this Memo

本备忘录的状况

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

本文件规定了互联网社区的互联网标准跟踪协议,并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态,请参考当前版本的“互联网官方协议标准”(STD 1)。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (1998). All Rights Reserved.

版权所有(C)互联网协会(1998年)。版权所有。

IESG NOTE

IESG注释

This memo describes a simple method of encoding PSTN addresses of facsimile devices in the local-part of Internet email addresses.

本备忘录描述了在互联网电子邮件地址的本地部分对传真设备的PSTN地址进行编码的简单方法。

As with all Internet mail addresses, the left-hand-side (local- part) of an address generated according to this specification, is not to be interpreted except by the MTA that is named on the right-hand-side (domain).

与所有Internet邮件地址一样,根据本规范生成的地址的左侧(本地部分)不能解释,除非由右侧(域)命名的MTA解释。

1. Introduction
1. 介绍

Since the very first e-mail to fax gateway objects appeared, a number of different methods to specify a fax address as an e-mail address have been used by implementors. Two major objectives for this were

自从第一个电子邮件到传真网关对象出现以来,实现者使用了许多不同的方法来指定传真地址作为电子邮件地址。这方面的两个主要目标是:

- enable an e-mail user to send faxes from his/her e-mail interface;

- 允许电子邮件用户从其电子邮件界面发送传真;

- enable some kind of "fax over e-mail service" transport, to reduce the costs of fax transmissions, and use the existing e-mail infrastructure.

- 启用某种“电子邮件传真服务”传输,以降低传真传输成本,并使用现有的电子邮件基础架构。

This memo describes the MINIMAL addressing method and standard extensions to encode FAX addresses in e-mail addresses, as required in reference [13]. The opposite problem, i.e. to allow a traditional numeric-only fax device user to access the e-mail transport service, is not discussed here.

本备忘录描述了参考文献[13]中要求的在电子邮件地址中编码传真地址的最小寻址方法和标准扩展。此处不讨论相反的问题,即允许传统的纯数字传真设备用户访问电子邮件传输服务。

All implementations supporting this FAX over e-mail address format MUST support as a minimum the specification described in this document. The generic complex case of converting the whole PSTN addressing in e-mail is out of scope in this minimal specification: there is some work in progress in the field, where also a number of standard optional extensions are being defined.

支持此传真电子邮件地址格式的所有实现必须至少支持本文档中描述的规范。转换电子邮件中的整个PSTN地址的一般复杂情况超出了本最低规范的范围:该领域正在进行一些工作,其中还定义了一些标准可选扩展。

In this document the formal definitions are described using ABNF syntax, as defined into [7]. We will also use some of the "CORE DEFINITIONS" defined in "APPENDIX A - CORE" of that document. The exact meaning of the capitalised words

在本文档中,使用[7]中定义的ABNF语法描述正式定义。我们还将使用该文件“附录A-核心”中定义的一些“核心定义”。大写单词的确切含义

"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "OPTIONAL"

“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“推荐”、“可”、“可选”

is defined in reference [6].

定义见参考文献[6]。

2. Minimal Fax address
2. 最小传真地址

The "service-selector" defined in section 2 of reference [13] for the fax service is:

参考文献[13]第2节中定义的传真服务“服务选择器”为:

      service-selector = "FAX"
        
      service-selector = "FAX"
        

The minimal addressing for the fax service also requires support for a "qualif-type1" element (see section 2 of reference [13]). This element is an OPTIONAL element of the fax address, but its support, when present, is REQUIRED:

传真服务的最小地址还需要支持“qualif-type1”元素(见参考文献[13]第2节)。此元素是传真地址的可选元素,但需要其支持(如果存在):

      qualif-type1 = "/" t33-sep "=" sub-addr
        
      qualif-type1 = "/" t33-sep "=" sub-addr
        

where

哪里

      t33-sep = "T33S"
        
      t33-sep = "T33S"
        
      sub-addr = 1*( DIGIT )
        
      sub-addr = 1*( DIGIT )
        

Thus, the minimal specification of a fax in e-mail address is:

因此,传真电子邮件地址的最低规格为:

      fax-address = fax-mbox [ "/T33S=" sub-addr ]
        
      fax-address = fax-mbox [ "/T33S=" sub-addr ]
        

fax-mbox = "FAX=" global-phone

传真mbox=“传真=“全球电话

Note: See section 4.1 in case multiple sub-addr per fax-mbox need to be specified.

注:如果需要指定每个传真mbox的多个子地址,请参见第4.1节。

The Minimal supported syntax for global-phone (as described in section reference [13]) is:

全球电话支持的最低语法(如参考文献[13]中所述)为:

   global-phone = "+" 1*( DIGIT , written-sep )
        
   global-phone = "+" 1*( DIGIT , written-sep )
        
   written-sep = ( "-" / "." )
        
   written-sep = ( "-" / "." )
        

The use of other dialling schemas for PSTN numbers (like private numbering plans or local dialling conventions) is also allowed. However, this does not preclude nor remove the minimal compulsory requirement to support the "global-phone" syntax as defined above.

也允许对PSTN号码使用其他拨号模式(如专用编号计划或本地拨号约定)。但是,这并不排除或删除支持上述“全局电话”语法的最低强制要求。

Any non "global-phone" dialling schema MUST NOT use the leading "+" between the "=" sign and the dialling string. The "+" sign is strictly reserved for the standard "global-phone" syntax.

任何非“全局电话”拨号模式不得在“=”符号和拨号字符串之间使用前导“+”。“+”符号严格保留为标准的“全球电话”语法。

Note: The specification of these different dialling schemas is out of scope for this minimal specification.

注意:这些不同拨号模式的规范超出此最低规范的范围。

User specification of PSTN e-mail addresses will be facilitated if they can insert these separators between dial elements like digits etc. For this reason we allow them in the syntax the written-sep element.

如果PSTN电子邮件地址的用户可以在拨号元素(如数字等)之间插入分隔符,则可以方便地指定PSTN电子邮件地址。因此,我们允许在语法中使用书面sep元素。

Implementors' note: Use of the written-sep elements is allowed, but not recommended. Any occurences of written-sep elements in a pstn-mbox MUST be ignored by all conformant implementations. User Agents SHOULD remove written-sep elements before submitting messages to the Message Transport System.

实施者注意:允许使用书面的sep元素,但不推荐使用。在pstn mbox中出现的任何书面sep元素都必须被所有一致性实现忽略。在向消息传输系统提交消息之前,用户代理应删除已写入的sep元素。

2.2 Some examples of a minimal "fax-address"
2.2 最小“传真地址”的一些示例

FAX=+3940226338

传真:+3940226338

      FAX=+12027653000/T33S=1387
        
      FAX=+12027653000/T33S=1387
        

FAX=+33-1-88335215

传真=+33-1-88335215

3. The e-mail address of the I-fax device: mta-I-fax
3. I-fax设备的电子邮件地址:mta-I-fax

An "I-fax device" has an e-mail address, or to be more exact, a name which enables a mail system to identify it on the e-mail global system.

“I-fax设备”有一个电子邮件地址,或者更准确地说,是一个使邮件系统能够在电子邮件全局系统上识别它的名称。

In Internet mail, this is the Right Hand Side (RHS) part of the address, i.e. the part on the right of the "@" sign. We will call this mta-I-fax

在Internet邮件中,这是地址的右侧(RHS)部分,即“@”符号右侧的部分。我们称之为mta-I-fax

      mta-I-fax = domain
        
      mta-I-fax = domain
        

For "domain" strings used in SMTP transmissions, the string MUST conform to the requirements of that standard's <domain> specifications [1], [3]. For "domain" strings used in message content headers, the string MUST conform to the requirements of the relevant standards [2], [3].

对于SMTP传输中使用的“域”字符串,该字符串必须符合该标准的<domain>规范[1]、[3]的要求。对于消息内容头中使用的“域”字符串,该字符串必须符合相关标准[2]、[3]的要求。

Note: in both cases, the standards permit use of "domain names" or "domain literals" in addresses.

注:在这两种情况下,标准都允许在地址中使用“域名”或“域名文字”。

4. The fax-email
4. 传真电子邮件

The complete structure used to transfer a minimal FAX address over the Internet e-mail transport system is called "fax-email". This object is an e-mail address which conforms to RFC822 [2] and RFC1123 [3] "addr-spec" syntax, with some extra structure which allows the FAX number to be identified.

用于通过Internet电子邮件传输系统传输最小传真地址的完整结构称为“传真电子邮件”。此对象是一个符合RFC822[2]和RFC1123[3]“addr spec”语法的电子邮件地址,具有一些允许识别传真号码的额外结构。

         fax-email =  ["/"] fax-address ["/"] "@" mta-I-fax
        
         fax-email =  ["/"] fax-address ["/"] "@" mta-I-fax
        

Implementors' note: The optional "/" characters can result from other mail transport services gateways, where it is also an optional element. Implementations MUST accept the optional slashes but SHOULD NOT generate them. Gateways are allowed to strip them off when converting to Internet mail addressing.

实现者注意:可选的“/”字符可能来自其他邮件传输服务网关,在这些网关中它也是可选元素。实现必须接受可选的斜杠,但不应生成它们。在转换为Internet邮件地址时,允许网关将其剥离。

It is essential to remind that "fax-address" element MUST strictly follow the "quoting rules" spcified in the relevant standards [2], [3]

必须提醒的是,“传真地址”元素必须严格遵守相关标准[2]、[3]中规定的“报价规则”

4.1 Multiple subaddresses
4.1 多个子地址

In case a particular service requires multiple T.33 subaddresses, and these subaddresses need to be given on the same "fax-mbox", multiple "fax-email" elements will be used.

如果特定服务需要多个T.33子地址,并且这些子地址需要在同一个“传真mbox”上提供,则将使用多个“传真电子邮件”元素。

Implementors' note: The UA could accept multiple subaddress elements for the same global-phone, but it must generate multiple "fax-mbox" elements when passing the message to the MTA.

实施者注意:UA可以为同一个全局电话接受多个子地址元素,但在将消息传递给MTA时必须生成多个“fax mbox”元素。

4.2 Some examples of minimal "fax-email"
4.2 最小“传真电子邮件”的一些示例
      FAX=+3940226338@faxworld.org
        
      FAX=+3940226338@faxworld.org
        
      FAX=+12027653000/T33S=1387@faxworld.org
        
      FAX=+12027653000/T33S=1387@faxworld.org
        
      /FAX=+33-1-88335215/@faxworld.org
        
      /FAX=+33-1-88335215/@faxworld.org
        
5. Conclusion
5. 结论

This proposal creates a minimal standard encoding for FAX addresses within the global e-mail transport system. The proposal requires no changes to existing e-mail software.

该提案为全球电子邮件传输系统内的传真地址创建了最低标准编码。该提案不需要更改现有的电子邮件软件。

6. Security Considerations
6. 安全考虑

This document specifies a means by which FAX addresses can be encoded into e-mail addresses. As routing of e-mail messages is determined by Domain Name System (DNS) information, a successful attack on this service could force the mail path via some particular gateway or message transfer agent where mail security can be affected by compromised software.

本文件规定了将传真地址编码为电子邮件地址的方法。由于电子邮件的路由由域名系统(DNS)信息决定,因此对该服务的成功攻击可能会迫使邮件路径通过某个特定网关或邮件传输代理,其中邮件安全性可能会受到受损软件的影响。

There are several means by which an attacker might be able to deliver incorrect mail routing information to a client. These include: (a) compromise of a DNS server, (b) generating a counterfeit response to a client's DNS query, (c) returning incorrect "additional information" in response to an unrelated query. Clients SHOULD ensure that mail routing is based only on authoritative answers. Once DNS Security mechanisms [5] become more widely deployed, clients SHOULD employ those mechanisms to verify the authenticity and integrity of mail routing records.

攻击者可以通过多种方式向客户端发送错误的邮件路由信息。这些措施包括:(a)DNS服务器受损,(b)对客户端DNS查询生成伪造响应,(c)对不相关查询返回不正确的“附加信息”。客户端应确保邮件路由仅基于权威答案。一旦DNS安全机制[5]得到更广泛的部署,客户端应该使用这些机制来验证邮件路由记录的真实性和完整性。

7. Author's Address

7. 作者地址

Claudio Allocchio Sincrotrone Trieste SS 14 Km 163.5 Basovizza I 34012 Trieste Italy

Claudio Allocchio Sincrotrone Trieste SS 14 Km意大利的里雅斯特Basovizza I 34012

   RFC822: Claudio.Allocchio@elettra.trieste.it
   X.400:  C=it;A=garr;P=Trieste;O=Elettra;
           S=Allocchio;G=Claudio;
   Phone:  +39 40 3758523
   Fax:    +39 40 3758565
        
   RFC822: Claudio.Allocchio@elettra.trieste.it
   X.400:  C=it;A=garr;P=Trieste;O=Elettra;
           S=Allocchio;G=Claudio;
   Phone:  +39 40 3758523
   Fax:    +39 40 3758565
        
8. References
8. 工具书类

[1] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, August 1982.

[1] Postel,J.,“简单邮件传输协议”,STD 10,RFC 821,1982年8月。

[2] Crocker, D., " Standard for the format of ARPA Internet text messages", STD 11, RFC 822, August 1982.

[2] Crocker,D.,“ARPA互联网文本信息格式标准”,STD 11,RFC 822,1982年8月。

[3] Braden, R., "Requirements for Internet hosts - application and support", RFC 1123, October 1989.

[3] Braden,R.,“互联网主机的要求——应用和支持”,RFC 1123,1989年10月。

[4] Malamud, C. and M. Rose, "Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical Procedures", RFC 1528, October 1993.

[4] Malamud,C.和M.Rose,“TPC.INT子域的操作原则:远程打印——技术程序”,RFC 15281993年10月。

[5] Eastlake, D. and C. Kaufman, "Domain Name System Security Extensions", RFC 2065, January 1997.

[5] Eastlake,D.和C.Kaufman,“域名系统安全扩展”,RFC 20651997年1月。

[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997.

[6] Bradner,S.,“RFC中用于表示需求水平的关键词”,RFC 211997年3月。

[7] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications", RFC 2234, November 1997.

[7] Crocker,D.和P.Overell,“语法规范的扩充BNF”,RFC 2234,1997年11月。

[8] ITU F.401 - Message Handling Services: Naming and Addressing for Public Message Handling Service; recommendation F.401 (August 1992)

[8] ITU F.401-信息处理服务:公共信息处理服务的命名和寻址;建议F.401(1992年8月)

[9] ITU F.423 - Message Handling Services: Intercommunication Between the Interpersonal Messaging Service and the Telefax Service; recommendation F.423 (August 1992)

[9] ITU F.423-信息处理服务:人际信息服务和传真服务之间的相互通信;建议F.423(1992年8月)

[10] ITU E.164 - Numbering plan for the ISDN era; recommendation E.164/I.331 (August 1991)

[10] ITU E.164——ISDN时代的编号计划;建议E.164/I.331(1991年8月)

[11] ITU T.33 - Facsimile routing utilizing the subaddress; recommendation T.33 (July, 1996)

[11] ITU T.33-使用子地址的传真路由;建议T.33(1996年7月)

[12] ETSI I-ETS 300,380 - Universal Personal Telecommunication (UPT): Access Devices Dual Tone Multi Frequency (DTMF) sender for acoustical coupling to the microphone of a handset telephone (March 1995)

[12] ETSI I-ETS 300380-通用个人电信(UPT):接入设备-用于与手持电话麦克风进行声学耦合的双音多频(DTMF)发送器(1995年3月)

[13] Allocchio, C., " Minimal FAX address format in Internet Mail", RFC 2303, March 1998.

[13] Allocchio,C.,“因特网邮件中的最小传真地址格式”,RFC 2303,1998年3月。

[14] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998.

[14] Kille,S.,“混音器(Mime互联网X.400增强中继):X.400和RFC 822/Mime之间的映射”,RFC 2156,1998年1月。

9. Full Copyright Statement
9. 完整版权声明

Copyright (C) The Internet Society (1998). All Rights Reserved.

版权所有(C)互联网协会(1998年)。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人,对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发,不受任何限制,前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是,不得以任何方式修改本文件本身,例如删除版权通知或对互联网协会或其他互联网组织的引用,除非出于制定互联网标准的需要,在这种情况下,必须遵循互联网标准过程中定义的版权程序,或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

上述授予的有限许可是永久性的,互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

本文件和其中包含的信息是按“原样”提供的,互联网协会和互联网工程任务组否认所有明示或暗示的保证,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。