Network Working Group C. Allocchio
Request for Comments: 3191 GARR-Italy
Obsoletes: 2303 October 2001
Updates: 2846
Category: Standards Track
Network Working Group C. Allocchio
Request for Comments: 3191 GARR-Italy
Obsoletes: 2303 October 2001
Updates: 2846
Category: Standards Track
Minimal GSTN address format in Internet Mail
Internet邮件中的最小GSTN地址格式
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 (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This memo describes a simple method of encoding Global Switched Telephone Network (GSTN) addresses (commonly called "telephone numbers") in the local-part of Internet email addresses, along with an extension mechanism to allow encoding of additional standard attributes needed for email gateways to GSTN-based services.
本备忘录描述了一种在互联网电子邮件地址的本地部分对全球交换电话网络（GSTN）地址（通常称为“电话号码”）进行编码的简单方法，以及一种扩展机制，以允许对基于GSTN的服务的电子邮件网关所需的其他标准属性进行编码。
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 an MTA that handles messages for the domain given in the right-hand-side.
与所有Internet邮件地址一样，根据本规范生成的地址的左侧（本地部分）不能解释，除非由MTA处理右侧给定域的邮件。
Since the very first e-mail to GSTN services gateway appeared, a number of different methods to specify a GSTN address as an e-mail address have been used by implementors. Several objectives for this methods have been identified, like to enable an e-mail user to access GSTN services from his/her e-mail interface, to allow some kind of "GSTN over e-mail service" transport (possibly reducing the costs of GSTN long distance transmissions) while using the existing e-mail infrastructure.
自从第一个电子邮件到GSTN服务网关出现以来，实现者使用了许多不同的方法将GSTN地址指定为电子邮件地址。已经确定了这种方法的几个目标，如使电子邮件用户能够从其电子邮件接口访问GSTN服务，允许某种“通过电子邮件服务的GSTN”传输（可能降低GSTN远程传输的成本），同时使用现有的电子邮件基础设施。
This memo describes the MINIMAL addressing method to encode GSTN addresses into e-mail addresses and the standard extension mechanism to allow definition of further standard elements. The opposite problem, i.e., to allow a traditional numeric-only GSTN device user to access the e-mail transport service, is not discussed here.
本备忘录描述了将GSTN地址编码为电子邮件地址的最小寻址方法，以及允许定义更多标准元素的标准扩展机制。此处不讨论相反的问题，即允许传统的仅限数字的GSTN设备用户访问电子邮件传输服务。
The IANA registration templates which MUST be used to register any standard element defined according to this specification are given in the "IANA Considerations" chapter (section 7 of this document).
“IANA注意事项”一章（本文件第7节）中给出了必须用于注册根据本规范定义的任何标准元素的IANA注册模板。
All implementations supporting this GSTN over e-mail service MUST support as a minimum the specification described in this document. The generic complex case of converting the entirety of GTSN addressing into e-mail is out of scope in this minimal specification.
支持此GSTN over e-mail服务的所有实现必须至少支持本文档中描述的规范。将整个GTSN寻址转换为电子邮件的一般复杂情况超出了本最低规范的范围。
In this document the formal definitions are described using ABNF syntax, as defined into [7]. This memo also uses some of the "CORE DEFINITIONS" defined in "APPENDIX A - CORE" of that document. The exact meaning of the capitalized words
在本文档中，使用[7]中定义的ABNF语法描述正式定义。本备忘录还使用了该文件“附录A-核心”中定义的一些“核心定义”。大写单词的确切含义
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "OPTIONAL"
“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“推荐”、“可”、“可选”
is defined in reference [6].
定义见参考文献[6]。
In this document the following new terms are also defined:
本文件还定义了以下新术语：
I-pstn device: a device which has an Internet domain name and it is able to communicate either directly or indirectly with the GSTN network;
I-pstn设备：具有互联网域名且能够直接或间接与GSTN网络通信的设备；
mta-I-pstn: the Internet domain name which identifies uniquely an I-pstn device over the Internet;
mta-I-pstn：唯一标识Internet上I-pstn设备的Internet域名；
pstn-email: the complete Internet e-mail address structure which is used to transport a GSTN address over the Internet e-mail service.
pstn电子邮件：完整的Internet电子邮件地址结构，用于通过Internet电子邮件服务传输GSTN地址。
The minimal specification of a GSTN address within an e-mail address is as follows:
电子邮件地址中GSTN地址的最低规格如下：
pstn-address = pstn-mbox [ qualif-type1 ]
pstn地址=pstn mbox[qualif-type1]
pstn-mbox = service-selector "=" global-phone
pstn mbox=服务选择器“=”全球电话
service-selector = 1*( DIGIT / ALPHA / "-" )
; note that SP (space) is not allowed in
; service-selector.
; service-selector MUST be handled as a case
; INSENSITIVE string by implementations.
service-selector = 1*( DIGIT / ALPHA / "-" )
; note that SP (space) is not allowed in
; service-selector.
; service-selector MUST be handled as a case
; INSENSITIVE string by implementations.
Other specifications adopting the "pstn-address" definition MUST define and register with IANA a unique case insensitive "service-selector" element to identify the specific messaging service involved.
采用“pstn地址”定义的其他规范必须定义一个唯一的不区分大小写的“服务选择器”元素，并向IANA注册，以识别所涉及的特定消息服务。
These specifications and registrations MUST also define which minimal "qualif-type1" extensions, if any, MUST be supported for the specified messaging service.
这些规范和注册还必须定义指定的消息传递服务必须支持的最小“qualif-type1”扩展（如果有）。
Implementations confirming to this minimal requirements specification are allowed to ignore any other non-minimal extensions address element which is present in the "pstn-address". However, conforming implementations MUST preserve all "qualif-type1" address elements they receive.
允许符合此最低要求规范的实现忽略“pstn地址”中存在的任何其他非最低扩展地址元素。然而，一致性实现必须保留它们接收到的所有“qualif-type1”地址元素。
The generic "qualif-type1" element is defined as:
通用“qualif-type1”元素定义为：
qualif-type1 = "/" keyword "=" string
qualif-type1 = "/" keyword "=" string
keyword = 1*( DIGIT / ALPHA / "-" )
; note that SP (space) is not allowed in keyword
keyword = 1*( DIGIT / ALPHA / "-" )
; note that SP (space) is not allowed in keyword
string = PCHAR ; note that printable characters are %x20-7E
字符串=PCHAR；请注意，可打印字符为%x20-7E
As such, all "pstn-address" extension elements MUST be defined in the "qualif-type1" form at the time of registration with IANA.
因此，在IANA注册时，必须在“qualif-type1”表中定义所有“pstn地址”扩展元素。
The purpose of global-phone element is to represent standard E.164 numeric addresses [10] within a syntax for electronic mail addressing that is compliant with standard e-mail specifications given in [1] and [2].
global phone元素的用途是在符合[1]和[2]中给出的标准电子邮件规范的电子邮件寻址语法中表示标准E.164数字地址[10]。
The minimal supported syntax for global-phone element is as follows:
全局电话元素支持的最低语法如下：
global-phone = "+" 1*( DIGIT / written-sep )
global-phone = "+" 1*( DIGIT / written-sep )
written-sep = ( "-" / "." )
written-sep = ( "-" / "." )
The use of other dialing schemes for GSTN numbers (like private numbering plans or local dialing conventions) is also allowed. However, this does not preclude nor remove the mandatory requirement for support to the "global-phone" syntax within the minimal GSTN address format.
还允许对GSTN号码使用其他拨号方案（如专用号码计划或本地拨号约定）。然而，这并不排除也不删除在最小GSTN地址格式内支持“全局电话”语法的强制性要求。
Any other dialing schemes MUST NOT use the leading "+" defined here between the "=" sign and the dialing string. The "+" sign is strictly reserved for the standard "global-phone" syntax.
任何其他拨号方案不得使用此处定义的“=”符号和拨号字符串之间的前导“+”。“+”符号严格保留为标准的“全球电话”语法。
Note:
注:
The specification of alternate dialing schemas is out of scope for this minimal specification.
备用拨号模式的规范超出此最低规范的范围。
This document also permits the use of written-sep elements in order to improve human readability of GSTN e-mail addresses. The written-sep are elements which can be placed between dial elements such as digits etc.
本文档还允许使用书面sep元素，以提高GSTN电子邮件地址的可读性。写入的sep是可以放置在拨号元件之间的元件，如数字等。
Implementors' note:
实施者注意：
Use of the written-sep elements is allowed, but not recommended for transmission. Any occurrences of written-sep elements in a pstn-mbox MUST be ignored by all conformant implementations.
允许使用书面sep元素，但不建议用于传输。pstn mbox中出现的任何书面sep元素都必须被所有符合性实现忽略。
Some examples of minimal pstn-address are:
最小pstn地址的一些示例如下：
VOICE=+3940226338
语音=+3940226338
FAX=+12027653000/T33S=6377
FAX=+12027653000/T33S=6377
SMS=+33-1-88335215
SMS=+33-1-88335215
Note:
注:
these examples are given as illustrations only; they do not necessarily represent valid pstn-addresses.
这些示例仅作为插图给出；它们不一定代表有效的pstn地址。
An "I-pstn device" has, among its characteristics, a unique Internet domain name which identifies it on the Internet. Within Internet mail, this is the Right Hand Side (RHS) part of the address, i.e., the part on the right of the "@" sign. For purposes of this document we will call this "mta-I-pstn"
“I-pstn设备”的特点之一是具有唯一的互联网域名，可在互联网上识别该设备。在Internet mail中，这是地址的右侧（RHS）部分，即“@”符号右侧的部分。在本文档中，我们称之为“mta-I-pstn”
mta-I-pstn = domain
mta-I-pstn = domain
For "domain" strings used in SMTP transmissions, the string MUST conform to the requirements of that standards <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:
注:
the use of "domain names" or "domain literals" is permitted in addresses in both the SMTP envelope and message header fields.
SMTP信封和邮件头字段中的地址都允许使用“域名”或“域文字”。
The complete structure used to transfer a minimal GSTN address over the Internet e-mail transport system is called "pstn-email". This object is a an e-mail address which conforms to [2] and [3] "addr-spec" syntax, with structure refinements which allows the GSTN number to be identified.
用于通过Internet电子邮件传输系统传输最小GSTN地址的完整结构称为“pstn电子邮件”。此对象是一个符合[2]和[3]“addr spec”语法的电子邮件地址，具有允许标识GSTN号的结构改进。
pstn-email = ["""] ["/"] pstn-address ["/"] ["""] "@" mta-I-pstn
pstn-email = ["""] ["/"] pstn-address ["/"] ["""] "@" mta-I-pstn
Implementors' note:
实施者注意：
The optional "/" characters can result from translations from other transport gateways (such as some X.400 gateways) which have included the "/" as 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. The relevant standard [2], [3] define exactly when the optional "quotes" characters surrounding the entire local part (i.e., the part on the left of the "@" character into the pstn-email) MUST be added.
可选“/”字符可能来自其他传输网关（例如一些X.400网关）的翻译，这些网关将“/”作为可选元素。实现必须接受可选的斜杠，但不应生成它们。在转换为Internet邮件地址时，允许网关将其剥离。相关标准[2]、[3]明确规定了必须在何时添加围绕整个本地部分的可选“引号”字符（即pstn电子邮件中“@”字符左侧的部分）。
There are some instances in GSTN applications where multiple subaddresses are used. On the other hand in e-mail practice a separate and unique e-mail address is always used for each recipient.
GSTN应用程序中有一些实例使用了多个子地址。另一方面，在电子邮件实践中，每个收件人始终使用一个单独且唯一的电子邮件地址。
In the event a particular GSTN service requires multiple subaddresses (in any form defined by the standard specification for that GSTN service) that are associated with the same "pstn-mbox", then the use of multiple "pstn-email" elements is REQUIRED.
如果特定的GSTN服务需要多个子地址（以该GSTN服务的标准规范定义的任何形式）与同一个“pstn mbox”关联，则需要使用多个“pstn电子邮件”元素。
Implementors' note:
实施者注意：
The UA may accept multiple subaddress elements for the same global-phone, but it MUST generate multiple "pstn-mbox" elements when submitting the message to the MTA.
UA可以为同一个全局电话接受多个子地址元素，但在向MTA提交邮件时必须生成多个“pstn mbox”元素。
Some examples of minimal pstn-email addresses follows:
以下是一些最小pstn电子邮件地址的示例：
VOICE=+3940226338@worldvoice.com
VOICE=+3940226338@worldvoice.com
FAX=+1.202.7653000/T33S=6377@faxserv.org
FAX=+1.202.7653000/T33S=6377@faxserv.org
/SMS=+33-1-88335215/@telecom.com
/SMS=+33-1-88335215/@telecom.com
Note:
注:
these examples are given as illustrations only; they do not necessarily represent valid pstn-addresses.
这些示例仅作为插图给出；它们不一定代表有效的pstn地址。
This proposal creates a minimal standard encoding for GSTN addresses within the global e-mail transport system. It also defines the standard extension mechanism to be used to introduce new elements for GSTN addresses.
本提案为全球电子邮件传输系统内的GSTN地址创建了最低标准编码。它还定义了用于为GSTN地址引入新元素的标准扩展机制。
The proposal is consistent with existing e-mail standards. Each specific GSTN service using this proposal MUST define and register with IANA its own "service-selector" specification and MUST define and register the eventual other "qualif-type1" elements needed for its specific application. An example of such an application is contained in reference [13].
该提案符合现有的电子邮件标准。使用本建议书的每个特定GSTN服务必须定义并向IANA注册其自己的“服务选择器”规范，并且必须定义并注册其特定应用所需的最终其他“qualif-type1”元素。参考文献[13]中包含了此类应用的示例。
This document specifies a means by which GSTN addresses can be encoded into e-mail addresses. Since e-mail routing is determined by Domain Name System (DNS) data, a successful attack to DNS could disseminate tampered information, which causes e-mail messages to be diverted via some MTA or Gateway where the security of the software has been compromised.
本文件规定了将GSTN地址编码为电子邮件地址的方法。由于电子邮件路由由域名系统（DNS）数据决定，对DNS的成功攻击可能会传播被篡改的信息，从而导致电子邮件通过某些MTA或网关转移，而这些MTA或网关的软件安全性已受到损害。
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]得到更广泛的部署，客户端应该使用这些机制来验证邮件路由记录的真实性和完整性。
As the service-selector and qualif-type1 elements values are extensible, they MUST be registered with IANA.
由于服务选择器和qualif-type1元素值是可扩展的，因此必须向IANA注册它们。
To register a service-selector or a qualif-type1 element, the registration form templates given in 7.1 and 7.2 MUST be used. Any new registration MUST fulfill the "Specification Required" criteria, as defined in RFC 2434, section 2 [16]:
要注册服务选择器或qualif-type1元素，必须使用7.1和7.2中给出的注册表模板。任何新注册必须符合RFC 2434第2节[16]中定义的“所需规范”标准：
"Specification Required - Values and their meaning MUST be documented in an RFC or other permanent and readily available reference, in sufficient detail so that interoperability between independent implementations is possible."
“所需规范-值及其含义必须记录在RFC或其他永久性且随时可用的参考文件中，足够详细，以便独立实现之间的互操作性成为可能。”
IANA MUST NOT accept registrations which are not supplemented by a Specification as defined above and which are not fully specified according to the template forms given in 7.1 and 7.2. In case of need for further consultation about accepting a new registration, IANA SHOULD refer to the Application Area Director to be directed to the appropriate "expert" individual or IETF Working Group.
IANA不得接受未经上述规范补充且未根据7.1和7.2中给出的模板格式完全指定的注册。如果需要就接受新注册进行进一步协商，IANA应向应用领域主管咨询，并将其直接告知适当的“专家”个人或IETF工作组。
After successful registration, IANA should publish the registered new element in the appropriate on-line IANA WEB site, and include it into the updates of the "Assigned Numbers" RFC series.
注册成功后，IANA应将注册的新元素发布在适当的IANA在线网站上，并将其纳入“分配编号”RFC系列的更新中。
This section (including 7.1 and 7.2) updates the ones contained in [15].
本节（包括7.1和7.2）更新了[15]中包含的内容。
7.1 IANA Registration form template for new values of GSTN address service-selector
7.1 GSTN地址服务选择器新值的IANA注册表模板
To: IANA@iana.org Subject: Registration of new values for the GSTN address service-selector specifier "foo"
致：IANA@iana.org主题：为GSTN地址服务选择器说明符“foo”注册新值
service-selector name:
服务选择器名称：
foo
福
Description of Use:
使用说明：
foo - ("foo" is a fictional new service-selector used in this template as an example, it is to be replaced with the new value being registered. Include a short description of the use of the new value here. This MUST include reference to Standard Track RFCs and eventually to other Standard Bodies documents for the complete description; the use of the value must be defined completely enough for independent implementation).
foo-（“foo”此模板中使用的是虚构的新服务选择器。例如，它将替换为正在注册的新值。在此处包括新值使用的简短说明。这必须包括参考标准跟踪RFC，并最终参考其他标准机构文档以获得完整说明；值的使用定义得不够完整，无法独立实现）。
Security Considerations:
安全考虑：
(Any additional security considerations that may be introduced by use of the new service-selector parameter should be defined here or in the reference Standards Track RFCs)
（使用新服务选择器参数可能引入的任何其他安全注意事项应在此处或参考标准跟踪RFCs中定义）
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
(fill in contact information)
（填写联系方式）
INFORMATION TO THE SUBMITTER:
提交人的信息：
The accepted registrations will be listed in the "Assigned Numbers" series of RFCs. The information in the registration form is freely distributable.
接受的注册将列在RFC的“分配编号”系列中。登记表中的信息可自由分发。
7.2 IANA Registration form template for new values of GSTN address qualif-type1 keyword and value
7.2 GSTN地址qualif-type1关键字和值的新值的IANA注册表模板
To: IANA@iana.org Subject: Registration of new values for the GSTN address qualif-type1 element "bar"
致：IANA@iana.org主题：注册GSTN地址qualif-type1元素“bar”的新值
qualif-type1 "keyword" name:
qualif-type1“关键字”名称：
bar
酒吧
qualif-type1 "value" ABNF definition:
qualif-type1“值”ABNF定义：
abnf - ("abnf" MUST define the ABNF form of the qualif-type1 value. The ABNF specification MUST be self-contained, using as basic elements the tokens given in specification [4]. To avoid any duplication (when appropriate), it MUST also use any already
abnf-（“abnf”必须定义qualif-type1值的abnf形式。abnf规范必须是自包含的，使用规范[4]中给出的标记作为基本元素。为避免任何重复（适当时），它还必须使用任何已存在的标记
registered non-basic token from other qualif-type1 elements, i.e., it MUST use the same non-basic token name and then repeat its identical ABNF definition from basic tokens.
从其他qualif-type1元素注册的非基本令牌，即它必须使用相同的非基本令牌名称，然后从基本令牌重复其相同的ABNF定义。
Description of Use:
使用说明：
bar - ("bar" is a fictional description for a new qualif-type1 element used in this template as an example. It is to be replaced by the real description of qualif-type1 element being registered. Include a short description of the use of the new qualif-type1 here. This MUST include reference to Standards Track RFCs and eventually to other Standard Bodies documents for the complete description; the use of the value MUST be defined completely enough for independent implementation.)
酒吧-（“酒吧”是此模板中使用的新qualif-type1元素的虚构描述，作为示例。它将被正在注册的qualif-type1元素的真实描述所取代。在此处包含新qualif-type1使用的简短描述。这必须包括对标准跟踪RFC的引用，并最终引用其他标准机构文档完整描述的ents；必须充分定义值的使用，以便独立实现。）
Use Restriction:
使用限制：
(If the new qualif-type1 elements is meaningful only for a specific set of service-element, you MUST specify here the list of allowed service-element types. If there is no restriction, then specify the keyword "none")
（如果新的qualif-type1元素仅对一组特定的服务元素有意义，则必须在此处指定允许的服务元素类型列表。如果没有限制，则指定关键字“无”）
Security Considerations:
安全考虑：
(Any additional security considerations that may be introduced by use of the new service-selector parameter should be defined here or in the reference Standards Track RFCs)
（使用新服务选择器参数可能引入的任何其他安全注意事项应在此处或参考标准跟踪RFCs中定义）
Person & email address to contact for further information:
联系人和电子邮件地址，以获取更多信息：
(fill in contact information)
（填写联系方式）
INFORMATION TO THE SUBMITTER:
提交人的信息：
The accepted registrations will be listed in the "Assigned Numbers" series of RFCs. The information in the registration form is freely distributable.
接受的注册将列在RFC的“分配编号”系列中。登记表中的信息可自由分发。
Although there are no technical or major changes from RFC 2303 specification, this section briefly describes where updates and clarifications were introduced:
尽管RFC 2303规范没有技术或重大变更，但本节简要介绍了更新和澄清的内容：
- considering the case that telephony systems do not conform any more to the "single/few" Public Operator paradigm, the old definition "PSTN - Public Switched Telephone Network" was changed into the more adequate "GSTN - Global Switched Telephone Network" one. However, in order to remain consistent with the previous specification, the ABNF variables names were not changed.
- 考虑到电话系统不再符合“单一/少数”公共运营商模式的情况，旧的“PSTN-公共交换电话网络”定义被更改为更合适的“GSTN-全球交换电话网络”定义。但是，为了与先前的规范保持一致，ABNF变量名称没有更改。
- it was made clear that "GSTN addresses" correspond, in common language, to "telephone numbers" and that the "global-phone" is a representation of E.164 numeric addresses;
- 明确指出，“GSTN地址”在通用语言中对应于“电话号码”，“全球电话”是E.164数字地址的表示；
- an explicit list of "new terms" with explanations was added to section 1.1;
- 在第1.1节中增加了一份带有解释的“新术语”的明确清单；
- the fact that any other specification adopting the "pstn-address" definition MUST register with IANA the new "service-selector" and "qualif-type1" elements was made explicit throughout the document; the relevant mechanism to be used was added in section 7 "IANA considerations" (including the IANA Registration form templates); this is also consistent with RFC 2846;
- 采用“pstn地址”定义的任何其他规范必须向IANA注册新的“服务选择器”和“qualif-type1”元素，这一事实在整个文件中都得到了明确说明；第7节“IANA注意事项”（包括IANA登记表模板）中增加了拟使用的相关机制；这也符合RFC 2846；
- in section 2.1 the use and meaning of "written-sep" was clarified;
- 第2.1节澄清了“书面sep”的用法和含义；
- in section 4., the quoting rules of the "pstn-address" and their practical use was made explicit both in the definition of pstn-email" and in the Implementors' note;
- 在第4节中，“pstn地址”的引用规则及其实际使用在“pstn电子邮件”的定义和实施者说明中都有明确规定；
- section 4.1 was updated to clarify how to generate "pstn-email" when more than one subaddress is used;
- 更新了第4.1节，以澄清在使用多个子地址时如何生成“pstn电子邮件”；
- the Author's Address was updated;
- 更新了作者的地址；
- the References list was updated to include RFC 2846 and RFC 2434.
- 参考文献列表已更新，包括RFC 2846和RFC 2434。
Claudio Allocchio INFN-GARR c/o Sincrotrone Trieste SS 14 Km 163.5 Basovizza I 34012 Trieste Italy
Claudio Allocchio INFN-GARR c/o Sincrotrone Trieste SS 14 Km意大利的里雅斯特Basovizza I 34012
RFC2822: Claudio.Allocchio@garr.it
X.400: C=it;A=garr;P=garr;S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565
RFC2822: Claudio.Allocchio@garr.it
X.400: C=it;A=garr;P=garr;S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565
[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", STD 3, RFC 1123, October 1989.
[3] Braden，R.，“互联网主机的要求-应用和支持”，STD 3，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", BCP 14, RFC 2119, March 1997.
[6] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年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 - The International Public Telecommunication Numbering Plan E.164/I.331 (May 1997).
[10] ITU E.164——国际公共电信编号计划E.164/I.331（1997年5月）。
[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 3192, October 2001.
[13] Allocchio，C.，“因特网邮件中的最小传真地址格式”，RFC3192，2001年10月。
[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月。
[15] Allocchio, C. "GSTN address element extensions in e-mail services", RFC 2846, June 2000.
[15] Allocchio，C.“电子邮件服务中的GSTN地址元素扩展”，RFC 28462000年6月。
[16] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[16] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。