Internet Engineering Task Force (IETF) M. Kucherawy
Request for Comments: 6577 Cloudmark, Inc.
Updates: 5451 March 2012
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) M. Kucherawy
Request for Comments: 6577 Cloudmark, Inc.
Updates: 5451 March 2012
Category: Standards Track
ISSN: 2070-1721
Authentication-Results Registration Update for Sender Policy Framework (SPF) Results
发件人策略框架（SPF）结果的身份验证结果注册更新
Abstract
摘要
This memo updates the registry of authentication method results in Authentication-Results: message header fields, correcting a discontinuity between the original registry creation and the Sender Policy Framework (SPF) specification.
此备忘录在“身份验证结果：消息头”字段中更新身份验证方法结果的注册表，纠正原始注册表创建与发件人策略框架（SPF）规范之间的不连续性。
This memo updates RFC 5451.
本备忘录更新了RFC 5451。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6577.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6577.
Copyright Notice
版权公告
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
2. Keywords ........................................................2
3. New 'fail' Definition ...........................................2
4. IANA Considerations .............................................2
4.1. Addition of 'Status' Columns ...............................3
4.2. Update to Result Names .....................................3
5. Security Considerations .........................................3
6. References ......................................................4
6.1. Normative References .......................................4
6.2. Informative References .....................................4
Appendix A. Examples in RFC 5451 ...................................5
Appendix B. Acknowledgements .......................................5
1. Introduction ....................................................2
2. Keywords ........................................................2
3. New 'fail' Definition ...........................................2
4. IANA Considerations .............................................2
4.1. Addition of 'Status' Columns ...............................3
4.2. Update to Result Names .....................................3
5. Security Considerations .........................................3
6. References ......................................................4
6.1. Normative References .......................................4
6.2. Informative References .....................................4
Appendix A. Examples in RFC 5451 ...................................5
Appendix B. Acknowledgements .......................................5
[AUTHRES] defined a new header field for electronic mail messages that presents the results of a message authentication effort in a machine-readable format. That Request for Comments created a registry of results for a few message authentication mechanisms, one of which was the Sender Policy Framework [SPF]. The registry contains one entry that is inconsistent with the latter specification, which was noted in an erratum [ERR2617] filed with the RFC Editor. This memo updates the IANA registries accordingly.
[AUTHRES]为电子邮件定义了一个新的标题字段，该字段以机器可读的格式显示邮件身份验证工作的结果。该注释请求为一些消息身份验证机制创建了一个结果注册表，其中之一就是发送方策略框架[SPF]。注册表包含一个与后一个规范不一致的条目，RFC编辑器存档的勘误表[ERR2617]中指出了这一点。本备忘录相应地更新了IANA登记册。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [KEYWORDS].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[关键词]中所述进行解释。
The new "fail" result, replacing the existing "hardfail" result for [SPF] (and thus also for [SENDER-ID]) has the same definition for "hardfail" that was used in Section 2.4.2 of [AUTHRES], namely:
新的“失败”结果取代了[SPF]（以及[SENDER-ID]）的现有“硬失败”结果，具有与[AUTHRES]第2.4.2节中使用的“硬失败”相同的定义，即：
This client is explicitly not authorized to inject or relay mail using the sender's DNS domain.
此客户端未明确授权使用发件人的DNS域注入或中继邮件。
This section enumerates requested actions of IANA, per [IANA].
本节列举了IANA根据[IANA]要求采取的行动。
IANA has amended the Email Authentication Methods and Email Authentication Result Names registries, both in the Email Authentication Parameters group, by adding to each a column called "Status" that will indicate for each entry its current status. Legal values for these columns are as follows:
IANA修改了电子邮件身份验证参数组中的电子邮件身份验证方法和电子邮件身份验证结果名称注册表，在每个注册表中添加一个名为“状态”的列，该列将指示每个条目的当前状态。这些列的法定值如下所示：
active: The entry is in current use.
活动：该条目当前正在使用中。
deprecated: The entry is no longer in current use.
已弃用：该条目不再在当前使用中。
New registrations to either table MUST specify one of these values.
对任一表的新注册必须指定其中一个值。
All existing entries, except as specified below, are to be noted as "active" as of publication of this memo.
除以下规定外，所有现有条目应在本备忘录发布时注明为“有效”。
[AUTHRES] listed "hardfail" as the result to be used when a message fails an [SPF] evaluation. However, this latter specification used the string "fail" to denote such failures.
[AUTHRES]列出了“hardfail”，作为消息未通过[SPF]评估时使用的结果。然而，后一个规范使用字符串“fail”来表示此类故障。
Therefore, IANA has marked "hardfail" in the Email Authentication Result Names registry as "deprecated" and amended the "fail" entry as follows:
因此，IANA已将电子邮件身份验证结果名称注册表中的“hardfail”标记为“已弃用”，并对“fail”条目进行了如下修改：
Code: fail
代码：失败
Defined: [AUTHRES]
定义：[作者]
Auth Method: spf, sender-id
身份验证方法：spf，发件人id
Meaning: [this memo] Section 3
意思：[本备忘录]第3节
Status: active
状态：活动
This memo corrects a registry error. It is possible that older implementations will not recognize or use the corrected entry. Thus, implementers are advised to support both result strings for some period of time. However, it is known that some implementations are already using the SPF-defined result string.
此备忘录更正了注册表错误。旧的实现可能无法识别或使用更正的条目。因此，建议实现者在一段时间内支持两个结果字符串。但是，众所周知，一些实现已经在使用SPF定义的结果字符串。
[AUTHRES] Kucherawy, M., "Message Header Field for Indicating Message Authentication Status", RFC 5451, April 2009.
[AUTHRES]Kucherawy，M.，“用于指示消息身份验证状态的消息头字段”，RFC 54512009年4月。
[ERR2617] "RFC Errata", Errata ID 2617, RFC 5451, <http://www.rfc-editor.org>.
[ERR2617]“RFC勘误表”，勘误表ID 2617，RFC 5451<http://www.rfc-editor.org>.
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[ERR2818] "RFC Errata", Errata ID 2818, RFC 5451, <http://www.rfc-editor.org>.
[ERR2818]“RFC勘误表”，勘误表ID 2818，RFC 5451<http://www.rfc-editor.org>.
[IANA] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[IANA]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[SENDER-ID] Lyon, J. and M. Wong, "Sender ID: Authenticating E-Mail", RFC 4406, April 2006.
[SENDER-ID]Lyon，J.和M.Wong，“发件人ID:验证电子邮件”，RFC 4406，2006年4月。
[SPF] Wong, M. and W. Schlitt, "Sender Policy Framework (SPF) for Authorizing Use of Domains in E-Mail, Version 1", RFC 4408, April 2006.
[SPF]Wong，M.和W.Schlitt，“授权在电子邮件中使用域的发件人策略框架（SPF），第1版”，RFC 4408，2006年4月。
It should be noted that this update also applies to the examples in [AUTHRES], specifically the one in Appendix B.5. The error there [ERR2818] is not corrected by this update, which only deals with the normative portions of that specification and the related IANA registrations. However, it is assumed one could easily see what needs to be corrected there.
应注意的是，此更新也适用于[AUTHRES]中的示例，特别是附录B.5中的示例。此处的错误[ERR2818]未通过本次更新得到纠正，本次更新仅涉及该规范的规范部分和相关IANA注册。然而，人们可以很容易地看到需要纠正的地方。
Corrected examples will be included in a full update to [AUTHRES] at some future time.
更正后的示例将在将来某个时候包含在[AUTHRES]的完整更新中。
The author wishes to acknowledge the following for their review and constructive criticism of this proposal: S. Moonesamy, Scott Kitterman.
作者希望感谢以下各方对本提案的审查和建设性批评：S.Moonesamy，Scott Kitterman。
Author's Address
作者地址
Murray S. Kucherawy Cloudmark, Inc. 128 King St., 2nd Floor San Francisco, CA 94107 US
MurayS.KuCaWaWy CuldMax公司，128国王圣，第二楼旧金山，CA 94107美国
Phone: +1 415 946 3800
EMail: msk@cloudmark.com
Phone: +1 415 946 3800
EMail: msk@cloudmark.com