Internet Engineering Task Force (IETF) T. Hansen
Request for Comments: 7677 AT&T Laboratories
Updates: 5802 November 2015
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) T. Hansen
Request for Comments: 7677 AT&T Laboratories
Updates: 5802 November 2015
Category: Standards Track
ISSN: 2070-1721
SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms
SCRAM-SHA-256和SCRAM-SHA-256-PLUS简单身份验证和安全层（SASL）机制
Abstract
摘要
This document registers the Simple Authentication and Security Layer (SASL) mechanisms SCRAM-SHA-256 and SCRAM-SHA-256-PLUS, provides guidance for secure implementation of the original SCRAM-SHA-1-PLUS mechanism, and updates the SCRAM registration procedures of RFC 5802.
本文件注册了简单认证和安全层（SASL）机制SCRAM-SHA-256和SCRAM-SHA-256-PLUS，为原SCRAM-SHA-1-PLUS机制的安全实施提供了指导，并更新了RFC 5802的紧急停堆注册程序。
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/rfc7677.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7677.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 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. Key Word Definitions . . . . . . . . . . . . . . . . . . . . 2
3. SCRAM-SHA-256 and SCRAM-SHA-256-PLUS . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. Updates to SCRAM-* Registration . . . . . . . . . . . . . 4
5.2. SASL-SCRAM Family Mechanisms Registration Procedure . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Key Word Definitions . . . . . . . . . . . . . . . . . . . . 2
3. SCRAM-SHA-256 and SCRAM-SHA-256-PLUS . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. Updates to SCRAM-* Registration . . . . . . . . . . . . . 4
5.2. SASL-SCRAM Family Mechanisms Registration Procedure . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
This document registers the SASL mechanisms SCRAM-SHA-256 and SCRAM-SHA-256-PLUS. SHA-256 has stronger security properties than SHA-1, and it is expected that SCRAM mechanisms based on it will have greater predicted longevity than the SCRAM mechanisms based on SHA-1.
本文件登记了SASL机构SCRAM-SHA-256和SCRAM-SHA-256-PLUS。SHA-256比SHA-1具有更强的安全性能，预计基于SHA-256的紧急停堆机制将比基于SHA-1的紧急停堆机制具有更大的预测寿命。
The registration form for the SCRAM family of algorithms is also updated from [RFC5802].
紧急停堆系列算法的登记表也从[RFC5802]更新。
After publication of [RFC5802], it was discovered that Transport Layer Security (TLS) [RFC5246] does not have the expected properties for the "tls-unique" channel binding to be secure [RFC7627]. Therefore, this document contains normative text that applies to both the original SCRAM-SHA-1-PLUS and the newly introduced SCRAM-SHA-256-PLUS mechanism.
[RFC5802]发布后，发现传输层安全性（TLS）[RFC5246]没有“TLS唯一”通道绑定的预期安全属性[RFC7627]。因此，本文件包含适用于原SCRAM-SHA-1-PLUS和新引入的SCRAM-SHA-256-PLUS机制的规范性文本。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The SCRAM-SHA-256 and SCRAM-SHA-256-PLUS SASL mechanisms are defined in the same way that SCRAM-SHA-1 and SCRAM-SHA-1-PLUS are defined in [RFC5802], except that the hash function for HMAC() and H() uses SHA-256 instead of SHA-1 [RFC6234].
SCRAM-SHA-256和SCRAM-SHA-256-PLUS SASL机制的定义方式与[RFC5802]中对SCRAM-SHA-1和SCRAM-SHA-1-PLUS的定义方式相同，只是HMAC（）和H（）的哈希函数使用SHA-256而不是SHA-1[RFC6234]。
For the SCRAM-SHA-256 and SCRAM-SHA-256-PLUS SASL mechanisms, the hash iteration-count announced by a server SHOULD be at least 4096.
对于SCRAM-SHA-256和SCRAM-SHA-256-PLUS SASL机制，服务器宣布的哈希迭代计数应至少为4096。
The GSS-API mechanism OID for SCRAM-SHA-256 is 1.3.6.1.5.5.18 (see Section 5).
紧急停堆-SHA-256的GSS-API机构OID为1.3.6.1.5.5.18（见第5节）。
This is a simple example of a SCRAM-SHA-256 authentication exchange when the client doesn't support channel bindings. The username 'user' and password 'pencil' are being used.
这是当客户端不支持通道绑定时进行SCRAM-SHA-256身份验证交换的一个简单示例。正在使用用户名“user”和密码“pencil”。
C: n,,n=user,r=rOprNGfwEbeRWgbNEkqO
C: n,,n=user,r=rOprNGfwEbeRWgbNEkqO
S: r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0,
s=W22ZaJ0SNY7soEsUEjb6gQ==,i=4096
S: r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0,
s=W22ZaJ0SNY7soEsUEjb6gQ==,i=4096
C: c=biws,r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0,
p=dHzbZapWIk4jUhN+Ute9ytag9zjfMHgsqmmiz7AndVQ=
C: c=biws,r=rOprNGfwEbeRWgbNEkqO%hvYDpWUa2RaTCAfuxFIlj)hNlF$k0,
p=dHzbZapWIk4jUhN+Ute9ytag9zjfMHgsqmmiz7AndVQ=
S: v=6rriTRBi23WpRR/wtup+mMhUZUn/dB5nLTJRsjl95G4=
S: v=6rriTRBi23WpRR/wtup+mMhUZUn/dB5nLTJRsjl95G4=
The security considerations from [RFC5802] still apply.
[RFC5802]中的安全注意事项仍然适用。
To be secure, either SCRAM-SHA-256-PLUS and SCRAM-SHA-1-PLUS MUST be used over a TLS channel that has had the session hash extension [RFC7627] negotiated, or session resumption MUST NOT have been used.
为了安全起见，必须在已协商会话哈希扩展[RFC7627]的TLS信道上使用SCRAM-SHA-256-PLUS和SCRAM-SHA-1-PLUS，否则不得使用会话恢复。
See [RFC4270] and [RFC6194] for reasons to move from SHA-1 to a strong security mechanism like SHA-256.
请参阅[RFC4270]和[RFC6194]，了解从SHA-1转移到SHA-256等强大安全机制的原因。
The strength of this mechanism is dependent in part on the hash iteration-count, as denoted by "i" in [RFC5802]. As a rule of thumb, the hash iteration-count should be such that a modern machine will take 0.1 seconds to perform the complete algorithm; however, this is unlikely to be practical on mobile devices and other relatively low-performance systems. At the time this was written, the rule of thumb gives around 15,000 iterations required; however, a hash iteration-count of 4096 takes around 0.5 seconds on current mobile handsets. This computational cost can be avoided by caching the ClientKey (assuming the Salt and hash iteration-count is stable). Therefore, the recommendation of this specification is that the hash iteration-count SHOULD be at least 4096, but careful consideration ought to be given to using a significantly higher value, particularly where mobile use is less important.
该机制的强度部分取决于散列迭代计数，如[RFC5802]中的“i”所示。根据经验，散列迭代计数应确保现代机器执行完整算法需要0.1秒；然而，这不太可能在移动设备和其他性能相对较低的系统上实现。在编写时，经验法则给出了大约15000次迭代；然而，在当前的手机上，4096的哈希迭代计数大约需要0.5秒。通过缓存ClientKey（假设Salt和hash迭代计数是稳定的），可以避免这种计算开销。因此，本规范的建议是散列迭代计数应至少为4096，但应仔细考虑使用显著更高的值，尤其是在移动使用不太重要的情况下。
The IANA registry for SCRAM-* (the SCRAM family of SASL mechanisms) in the SASL mechanism registry ([RFC4422]) has been updated as follows. The email address for reviews has been updated, and the note at the end changed.
SASL机构注册表（[RFC4422]）中的紧急停堆IANA注册表-*（SASL机构的紧急停堆系列）已更新如下。评论的电子邮件地址已更新，结尾的注释已更改。
To: iana@iana.org Subject: Registration of a new SASL family SCRAM
致：iana@iana.org主题：新SASL系列紧急停堆的登记
SASL mechanism name (or prefix for the family): SCRAM-* Security considerations: Section 7 of [RFC5802] Published specification (optional, recommended): RFC 7677 Person & email address to contact for further information: IETF KITTEN WG <kitten@ietf.org> Intended usage: COMMON Owner/Change controller: IESG <iesg@ietf.org> Note: Members of this family MUST be explicitly registered using the "IETF Review" [RFC5226] registration procedure. Reviews MUST be requested on the KITTEN mailing list kitten@ietf.org (or a successor designated by the responsible Security AD).
SASL机构名称（或该系列的前缀）：紧急停堆-*安全注意事项：[RFC5802]发布规范第7节（可选，推荐）：RFC 7677联系人和电子邮件地址，以获取更多信息：IETF KITTEN WG<kitten@ietf.org>预期用途：通用所有者/变更控制者：IESG<iesg@ietf.org>注：该家族成员必须使用“IETF审查”[RFC5226]注册程序明确注册。必须在KITTEN邮件列表上请求审查kitten@ietf.org（或由负责的担保AD指定的继任者）。
Note to future SCRAM-mechanism designers: each new SASL SCRAM mechanism MUST be explicitly registered with IANA within the SASL SCRAM Family Mechanisms registry.
未来紧急停堆机制设计者注意：每个新的SASL紧急停堆机制必须在SASL紧急停堆系列机制注册表中向IANA明确注册。
A new IANA registry has been added for members of the SCRAM family of SASL mechanisms, named "SASL SCRAM Family Mechanisms". It adds two new fields to the existing SCRAM mechanism registry: Minimum iteration-count and Associated OID. Below is the template for registration of a new SASL family SCRAM. (Note that the string "TBD-BY-IANA" should be left as is, so that it may be filled in at registration time by IANA.)
为SASL机构的紧急停堆系列成员添加了一个新的IANA登记册，名为“SASL紧急停堆系列机构”。它向现有紧急停堆机制注册表添加了两个新字段：最小迭代次数和相关OID。以下是注册新SASL系列紧急停堆的模板。（请注意，字符串“TBD-BY-IANA”应保持原样，以便IANA在注册时填写。）
To: iana@iana.org Subject: Registration of a new SASL SCRAM family mechanism
致：iana@iana.org主题：新SASL紧急停堆系列机制的注册
SASL mechanism name (or prefix for the family): SCRAM-<NAME>
Security considerations: Section 7 of [RFC5802]
Published specification (optional, recommended): RFC 7677
Minimum iteration-count: The minimum hash iteration-count that
servers SHOULD announce
Associated OID: TBD-BY-IANA
Person & email address to contact for further information:
IETF KITTEN WG <kitten@ietf.org>
Intended usage: COMMON
Owner/Change controller: IESG <iesg@ietf.org>
SASL mechanism name (or prefix for the family): SCRAM-<NAME>
Security considerations: Section 7 of [RFC5802]
Published specification (optional, recommended): RFC 7677
Minimum iteration-count: The minimum hash iteration-count that
servers SHOULD announce
Associated OID: TBD-BY-IANA
Person & email address to contact for further information:
IETF KITTEN WG <kitten@ietf.org>
Intended usage: COMMON
Owner/Change controller: IESG <iesg@ietf.org>
Note: Members of this family MUST be explicitly registered using the "IETF Review" [RFC5226] registration procedure. Reviews MUST be requested on the KITTEN mailing list kitten@ietf.org (or a successor designated by the responsible Security Area Director).
注：该家族成员必须使用“IETF审查”[RFC5226]注册程序明确注册。必须在KITTEN邮件列表上请求审查kitten@ietf.org（或负责安全区域主任指定的继任者）。
Note: At publication of a new SASL SCRAM Family Mechanism, IANA SHOULD assign a GSS-API mechanism OID for this mechanism from the iso.org.dod.internet.security.mechanisms prefix (see the "SMI Security for Mechanism Codes" registry) and fill in the value for "TBD-BY-IANA" above. Only one OID needs to be assigned for a SCRAM-<NAME> and SCRAM-<NAME>-PLUS pair. The same OID should be assigned to both entries in the registry.
注：在发布新的SASL紧急停堆系列机制时，IANA应从iso.org.dod.internet.security.Mechanism前缀（参见“SMI安全机制代码”注册表）为该机制分配GSS-API机制OID，并填写上述“TBD-BY-IANA”的值。对于紧急停堆-<NAME>和紧急停堆-<NAME>-PLUS对，只需分配一个OID。应为注册表中的两个条目分配相同的OID。
Note to future SASL SCRAM mechanism designers: each new SASL SCRAM mechanism MUST be explicitly registered with IANA and MUST comply with the SCRAM-mechanism naming convention defined in Section 4 of [RFC5802].
未来SASL紧急停堆机制设计者注意：每个新的SASL紧急停堆机制必须向IANA明确注册，并且必须符合[RFC5802]第4节中定义的紧急停堆机制命名约定。
The existing entries for SASL SCRAM-SHA-1 and SCRAM-SHA-1-PLUS have been moved from the existing SASL mechanism registry to the "SASL SCRAM Family Mechanisms" registry. At that time, the following values were added:
SASL SCRAM-SHA-1和SCRAM-SHA-1-PLUS的现有条目已从现有SASL机制注册表移到“SASL SCRAM系列机制”注册表中。当时，添加了以下值：
Minimum iteration-count: 4096 OID: 1.3.6.1.5.5.14 (from [RFC5802])
最小迭代次数：4096 OID:1.3.6.1.5.5.14（来自[RFC5802]）
The following new SASL SCRAM mechanisms have been added to the "SASL SCRAM Family Mechanisms" registry:
以下新的SASL紧急停堆机制已添加到“SASL紧急停堆系列机制”注册表中：
To: iana@iana.org Subject: Registration of a new SASL SCRAM Family mechanism SCRAM-SHA-256
致：iana@iana.org主题：注册新SASL紧急停堆系列机构SCRAM-SHA-256
SASL mechanism name (or prefix for the family): SCRAM-SHA-256 Security considerations: Section 4 of RFC 7677 Published specification (optional, recommended): RFC 7677 Minimum iteration-count: 4096 OID: 1.3.6.1.5.5.18 Person & email address to contact for further information: IETF KITTEN WG <kitten@ietf.org> Intended usage: COMMON Owner/Change controller: IESG <iesg@ietf.org> Note:
SASL机构名称（或系列前缀）：SCRAM-SHA-256安全注意事项：RFC 7677发布规范第4节（可选，推荐）：RFC 7677最小迭代次数：4096 OID:1.3.6.1.5.5.18联系人和电子邮件地址：IETF KITTEN WG<kitten@ietf.org>预期用途：通用所有者/变更控制者：IESG<iesg@ietf.org>注:
To: iana@iana.org Subject: Registration of a new SASL SCRAM Family mechanism SCRAM-SHA-256-PLUS
致：iana@iana.org主题：注册新SASL紧急停堆系列机构SCRAM-SHA-256-PLUS
SASL mechanism name (or prefix for the family): SCRAM-SHA-256-PLUS Security considerations: Section 4 of RFC 7677 Published specification (optional, recommended): RFC 7677 Minimum iteration-count: 4096 OID: 1.3.6.1.5.5.18 Person & email address to contact for further information: IETF KITTEN WG <kitten@ietf.org> Intended usage: COMMON Owner/Change controller: IESG <iesg@ietf.org> Note:
SASL机构名称（或系列前缀）：SCRAM-SHA-256-PLUS安全注意事项：RFC 7677发布规范第4节（可选，推荐）：RFC 7677最小迭代次数：4096 OID:1.3.6.1.5.5.18联系人和电子邮件地址：IETF KITTEN WG<kitten@ietf.org>预期用途：通用所有者/变更控制者：IESG<iesg@ietf.org>注:
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC4422] Melnikov, A., Ed. and K. Zeilenga, Ed., "Simple Authentication and Security Layer (SASL)", RFC 4422, DOI 10.17487/RFC4422, June 2006, <http://www.rfc-editor.org/info/rfc4422>.
[RFC4422]Melnikov，A.，Ed.和K.Zeilenga，Ed.，“简单身份验证和安全层（SASL）”，RFC 4422，DOI 10.17487/RFC4422，2006年6月<http://www.rfc-editor.org/info/rfc4422>.
[RFC5802] Newman, C., Menon-Sen, A., Melnikov, A., and N. Williams, "Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms", RFC 5802, DOI 10.17487/RFC5802, July 2010, <http://www.rfc-editor.org/info/rfc5802>.
[RFC5802]Newman，C.，Menon Sen，A.，Melnikov，A.，和N.Williams，“盐渍挑战响应认证机制（SCRAM）SASL和GSS-API机制”，RFC 5802，DOI 10.17487/RFC5802，2010年7月<http://www.rfc-editor.org/info/rfc5802>.
[RFC6234] Eastlake 3rd, D. and T. Hansen, "US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)", RFC 6234, DOI 10.17487/RFC6234, May 2011, <http://www.rfc-editor.org/info/rfc6234>.
[RFC6234]Eastlake 3rd，D.和T.Hansen，“美国安全哈希算法（基于SHA和SHA的HMAC和HKDF）”，RFC 6234，DOI 10.17487/RFC6234，2011年5月<http://www.rfc-editor.org/info/rfc6234>.
[RFC7627] Bhargavan, K., Ed., Delignat-Lavaud, A., Pironti, A., Langley, A., and M. Ray, "Transport Layer Security (TLS) Session Hash and Extended Master Secret Extension", RFC 7627, DOI 10.17487/RFC7627, September 2015, <http://www.rfc-editor.org/info/rfc7627>.
[RFC7627]Bhargavan，K.，Ed.，Delignat Lavaud，A.，Pironti，A.，Langley，A.，和M.Ray，“传输层安全（TLS）会话哈希和扩展主秘密扩展”，RFC 7627，DOI 10.17487/RFC7627，2015年9月<http://www.rfc-editor.org/info/rfc7627>.
[RFC4270] Hoffman, P. and B. Schneier, "Attacks on Cryptographic Hashes in Internet Protocols", RFC 4270, DOI 10.17487/RFC4270, November 2005, <http://www.rfc-editor.org/info/rfc4270>.
[RFC4270]Hoffman，P.和B.Schneier，“对互联网协议中加密哈希的攻击”，RFC 4270，DOI 10.17487/RFC4270，2005年11月<http://www.rfc-editor.org/info/rfc4270>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，DOI 10.17487/RFC5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC6194] Polk, T., Chen, L., Turner, S., and P. Hoffman, "Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms", RFC 6194, DOI 10.17487/RFC6194, March 2011, <http://www.rfc-editor.org/info/rfc6194>.
[RFC6194]Polk，T.，Chen，L.，Turner，S.，和P.Hoffman，“SHA-0和SHA-1消息摘要算法的安全考虑”，RFC 6194，DOI 10.17487/RFC6194，2011年3月<http://www.rfc-editor.org/info/rfc6194>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，DOI 10.17487/RFC5246，2008年8月<http://www.rfc-editor.org/info/rfc5246>.
Acknowledgements
致谢
This document benefited from discussions on the KITTEN WG mailing list. The author would like to specially thank Russ Allbery, Dave Cridland, Shawn Emery, Stephen Farrell, Simon Josefsson, Pearl Liang, Alexey Melnikov, Peter Saint-Andre, Robert Sparks, Martin Thompson, and Nico Williams for their comments on this topic.
本文件得益于关于KITTEN工作组邮件列表的讨论。作者要特别感谢Russ Allbery、Dave Cridland、Shawn Emery、Stephen Farrell、Simon Josefsson、Pearl Liang、Alexey Melnikov、Peter Saint Andre、Robert Sparks、Martin Thompson和Nico Williams对此主题的评论。
Author's Address
作者地址
Tony Hansen AT&T Laboratories 200 Laurel Ave. South Middletown, NJ 07748 United States
美国新泽西州南米德尔顿劳雷尔大道200号托尼·汉森AT&T实验室，邮编：07748
Email: tony+scramsha256@maillennium.att.com
Email: tony+scramsha256@maillennium.att.com