Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 7718 AT&T Labs
Updates: 4656 December 2015
Category: Standards Track
ISSN: 2070-1721
Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 7718 AT&T Labs
Updates: 4656 December 2015
Category: Standards Track
ISSN: 2070-1721
Registries for the One-Way Active Measurement Protocol (OWAMP)
单向主动测量协议（OWAMP）的注册表
Abstract
摘要
This memo describes the registries for OWAMP -- the One-Way Active Measurement Protocol. The registries allow assignment of Mode bit positions and OWAMP Command numbers. Per this memo, IANA has established the registries for new features, called the OWAMP-Modes registry and the OWAMP Control Command Number registry. This memo updates RFC 4656.
本备忘录描述了OWAMP（单向主动测量协议）的注册表。注册表允许分配模式位位置和OWAMP命令号。根据这份备忘录，IANA为新功能建立了注册表，称为OWAMP模式注册表和OWAMP控制命令号注册表。本备忘录更新了RFC 4656。
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/rfc7718.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7718.
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
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations for OWAMP-Control Registries . . . . . . 3
3.1. Control Command Number Registry . . . . . . . . . . . . . 3
3.1.1. Registry Specification . . . . . . . . . . . . . . . 3
3.1.2. Registry Management . . . . . . . . . . . . . . . . . 3
3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 3
3.1.4. OWAMP-Control Command Numbers Initial Contents . . . 3
3.2. OWAMP-Modes . . . . . . . . . . . . . . . . . . . . . . . 4
3.2.1. Registry Specification . . . . . . . . . . . . . . . 4
3.2.2. Registry Management . . . . . . . . . . . . . . . . . 4
3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 4
3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations for OWAMP-Control Registries . . . . . . 3
3.1. Control Command Number Registry . . . . . . . . . . . . . 3
3.1.1. Registry Specification . . . . . . . . . . . . . . . 3
3.1.2. Registry Management . . . . . . . . . . . . . . . . . 3
3.1.3. Experimental Numbers . . . . . . . . . . . . . . . . 3
3.1.4. OWAMP-Control Command Numbers Initial Contents . . . 3
3.2. OWAMP-Modes . . . . . . . . . . . . . . . . . . . . . . . 4
3.2.1. Registry Specification . . . . . . . . . . . . . . . 4
3.2.2. Registry Management . . . . . . . . . . . . . . . . . 4
3.2.3. Experimental Numbers . . . . . . . . . . . . . . . . 4
3.2.4. OWAMP-Modes Initial Contents . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1. Normative References . . . . . . . . . . . . . . . . . . 6
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
The One-Way Active Measurement Protocol (OWAMP) [RFC4656] was prepared to support measurements of metrics specified by the IP Performance Metrics (IPPM) working group in the IETF. The Two-Way Active Measurement Protocol (TWAMP) [RFC5357] is an extension of OWAMP. The TWAMP specification gathered wide review as it approached completion, and the by-products were several recommendations for new features in TWAMP. As a result, a registry of new features was established for TWAMP. However, there were no new features proposed for OWAMP until recently [RFC7717].
编写单向主动测量协议（OWAMP）[RFC4656]是为了支持IETF中IP性能度量（IPPM）工作组指定的度量的测量。双向主动测量协议（TWAMP）[RFC5357]是OWAMP的扩展。TWAMP规范在接近完成时得到了广泛的审查，副产品是对TWAMP新特性的几项建议。因此，为TWAMP建立了一个新特性的注册表。然而，直到最近，还没有为OWAMP提出新功能[RFC7717]。
This memo establishes the needed registries for OWAMP and updates [RFC4656].
本备忘录建立了OWAMP和更新所需的注册表[RFC4656]。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
The purpose and scope of this memo is to describe and request the establishment of registries for future OWAMP [RFC4656] extensions. IANA already administers the "Two-way Active Measurement Protocol (TWAMP) Parameters", and this request follows a similar form (with one exception identified below).
本备忘录的目的和范围是描述并请求为未来的OWAMP[RFC4656]扩展建立注册中心。IANA已经管理“双向主动测量协议（TWAMP）参数”，并且该请求遵循类似的形式（下面识别了一个例外）。
This memo also provides the initial contents for the OWAMP registries.
本备忘录还提供了OWAMP注册表的初始内容。
The OWAMP-Control protocol coordinates the measurement capability. All OWAMP-Control messages follow specifications defined in Section 3 of [RFC4656].
OWAMP控制协议协调测量能力。所有OWAMP控制信息遵循[RFC4656]第3节中定义的规范。
IANA has created an OWAMP-Control Command Number registry.
IANA已经创建了一个OWAMP控制命令号注册表。
OWAMP-Control Commands follow specifications defined in Section 3.4 of [RFC4656].
OWAMP控制命令遵循[RFC4656]第3.4节中定义的规范。
OWAMP-Control Command Numbers are specified in the first octet of OWAMP-Control-Client command messages consistent with Section 3 of [RFC4656]. There are a maximum of 256 command numbers.
OWAMP控制命令编号在与[RFC4656]第3节一致的OWAMP控制客户端命令消息的第一个八位字节中指定。最多有256个命令编号。
Because the "OWAMP-Control Command Numbers" registry can contain only 256 values, and because OWAMP is an IETF protocol, these registries MUST be updated only by "IETF Review" as specified in [RFC5226] (an RFC that documents registry use and is approved by the IESG).
因为“OWAMP控制命令编号”注册表只能包含256个值，并且因为OWAMP是一个IETF协议，所以这些注册表只能通过[RFC5226]（记录注册表使用并经IESG批准的RFC）中指定的“IETF审查”来更新。
One experimental value is currently assigned in the Command Numbers Registry, as indicated in the initial contents below.
如以下初始内容所示，当前在命令编号注册表中分配了一个实验值。
OWAMP-Control Commands follows the procedure defined in Section 3.5 of [RFC4656] and in the remainder of Section 3 of that document.
OWAMP控制命令遵循[RFC4656]第3.5节和该文件第3节剩余部分中定义的程序。
The complete set of OWAMP-Control Command Numbers are as follows (including two reserved values):
全套OWAMP控制命令编号如下（包括两个保留值）：
OWAMP-Control Command Numbers
OWAMP控制命令编号
Value Description Semantics Reference
Definition
==========================================================
0 Reserved Section 3.1.4 RFC 7718
1 Request-Session Section 3.5 RFC 4656
2 Start-Sessions Section 3.7 RFC 4656
3 Stop-Sessions Section 3.8 RFC 4656
4 Fetch-Sessions Section 3.9 RFC 4656
5-253 Unassigned
254 Experimentation Section 3.1.4 RFC 7718
255 Reserved Section 3.1.4 RFC 7718
Value Description Semantics Reference
Definition
==========================================================
0 Reserved Section 3.1.4 RFC 7718
1 Request-Session Section 3.5 RFC 4656
2 Start-Sessions Section 3.7 RFC 4656
3 Stop-Sessions Section 3.8 RFC 4656
4 Fetch-Sessions Section 3.9 RFC 4656
5-253 Unassigned
254 Experimentation Section 3.1.4 RFC 7718
255 Reserved Section 3.1.4 RFC 7718
IANA has created an OWAMP-Modes registry.
IANA已经创建了OWAMP模式注册表。
OWAMP-Modes are specified in OWAMP Server Greeting messages and Set-up Response messages consistent with Section 3.1 of [RFC4656]. Modes are currently indicated by setting single bits in the 32-bit Modes field. However, more complex encoding may be used in the future.
OWAMP模式在OWAMP服务器问候信息和设置响应信息中指定，与[RFC4656]第3.1节一致。当前通过在32位模式字段中设置单个位来指示模式。然而，将来可能会使用更复杂的编码。
Because the "OWAMP-Modes" are based on only 32 bit positions with each position conveying a unique feature, and because OWAMP is an IETF protocol, these registries MUST be updated only by "IETF Review" as specified in [RFC5226] (an RFC that documents registry use and is approved by the IESG). IANA SHOULD allocate monotonically increasing bit positions when requested.
由于“OWAMP模式”仅基于32位位置，每个位置都传递一个独特的功能，并且由于OWAMP是一个IETF协议，因此这些注册表必须仅通过[RFC5226]中规定的“IETF审查”（记录注册表使用并经IESG批准的RFC）进行更新。IANA应在请求时分配单调递增的位位置。
No experimental bit positions are currently assigned in the Modes registry, as indicated in the initial contents below.
如以下初始内容所示，模式注册表中当前未分配任何实验位位置。
OWAMP-Control connection establishment follows the procedure defined in Section 3.1 of [RFC4656].
OWAMP控制连接的建立遵循[RFC4656]第3.1节中定义的程序。
In the OWAMP-Modes registry, assignments are straightforward on the basis of bit positions, and there are no references to values -- this is a difference from the comparable TWAMP registry (and a topic for improvement in the TWAMP-Modes registry that is reconciled in [RFC7717]).
在OWAMP模式注册表中，基于位位置的赋值是直接的，并且没有对值的引用——这与可比较的TWAMP注册表（以及[RFC7717]中协调的TWAMP模式注册表中的改进主题）不同。
An extension of the OWAMP-Modes is proposed in [RFC7717]. With this extension, the complete set of OWAMP Mode bit positions are as follows (including one reserved bit position):
[RFC7717]中提出了OWAMP模式的扩展。通过此扩展，完整的OWAMP模式位位置集如下所示（包括一个保留位位置）：
OWAMP-Modes
OWAMP模式
Bit Semantics
Pos. Description Definition Reference
=======================================================
0 Unauthenticated Section 3.1 RFC 4656
1 Authenticated Section 3.1 RFC 4656
2 Encrypted Section 3.1 RFC 4656
3 Reserved Section 3.2.4 RFC 7718
------------------------------------------------------
4 IKEv2-derived Shared Section 3.2.4 RFC 7718
Secret Key of RFC 7718,
Section 5 of RFC 7717
of RFC 7717
------------------------------------------------------
5-31 Unassigned
Bit Semantics
Pos. Description Definition Reference
=======================================================
0 Unauthenticated Section 3.1 RFC 4656
1 Authenticated Section 3.1 RFC 4656
2 Encrypted Section 3.1 RFC 4656
3 Reserved Section 3.2.4 RFC 7718
------------------------------------------------------
4 IKEv2-derived Shared Section 3.2.4 RFC 7718
Secret Key of RFC 7718,
Section 5 of RFC 7717
of RFC 7717
------------------------------------------------------
5-31 Unassigned
In the original OWAMP Modes field, setting bit position 0, 1, or 2 indicated the security mode of the Control protocol, and the Test protocol inherited the same mode (see Section 4 of [RFC4656]).
在原始OWAMP模式字段中，设置位位置0、1或2表示控制协议的安全模式，测试协议继承了相同的模式（参见[RFC4656]第4节）。
The value of the Modes field sent by the Server in the Server-Greeting message is the bit-wise OR of the modes (bit positions) that it is willing to support during this session. Thus, the five least significant bits of the 32-bit Modes field are used. When no other features are activated, the 27 most significant bits MUST be zero. A Control-Client conforming to [RFC4656] MAY ignore the values in the 29 most significant bits of the Modes field, or it MAY support features that are communicated in other bit positions, such as the IKEv2-derived Shared Secret Key extension [RFC7717].
服务器在服务器问候语消息中发送的模式字段的值是按位或在此会话期间它愿意支持的模式（位位置）的值。因此，使用32位模式字段的五个最低有效位。当没有激活其他功能时，27个最高有效位必须为零。符合[RFC4656]的控制客户端可以忽略模式字段的29个最高有效位中的值，或者它可以支持在其他位位置进行通信的功能，例如IKEv2派生的共享密钥扩展[RFC7717]。
OWAMP and TWAMP registries for Modes may grow to contain different features and functions due to the inherent differences in one-way and two-way measurement configurations and the metrics they measure. No attempt will be made to coordinate them unnecessarily, except for the Reserved bit position 3 above. This is available for assignment if a mixed security mode similar to [RFC5618] is defined for OWAMP; it would allow alignment with the comparable TWAMP feature.
由于单向和双向测量配置及其测量指标的固有差异，模式的OWAMP和TWAMP注册表可能会增加，以包含不同的特性和功能。除上述保留位位置3外，不会尝试不必要地协调它们。如果为OWAMP定义了类似于[RFC5618]的混合安全模式，则可进行分配；它将允许与类似的TWAMP功能对齐。
As this memo simply documents the creation of OWAMP registries, it presents no new security or privacy issues for the Internet.
由于本备忘录仅记录了OWAMP注册中心的创建，因此不会对互联网提出新的安全或隐私问题。
The security considerations that apply to any active measurement of live networks are relevant here as well. See [RFC4656] and [RFC5357].
适用于实时网络的任何主动测量的安全注意事项也与此相关。参见[RFC4656]和[RFC5357]。
Privacy considerations for measurement systems, particularly when Internet users participate in the tests in some way, are described in [RFC7594].
[RFC7594]中描述了测量系统的隐私注意事项，特别是当互联网用户以某种方式参与测试时。
[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>.
[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M. Zekauskas, "A One-way Active Measurement Protocol (OWAMP)", RFC 4656, DOI 10.17487/RFC4656, September 2006, <http://www.rfc-editor.org/info/rfc4656>.
[RFC4656]Shalunov，S.，Teitelbaum，B.，Karp，A.，Boote，J.，和M.Zekauskas，“单向主动测量协议（OWAMP）”，RFC 4656，DOI 10.17487/RFC4656，2006年9月<http://www.rfc-editor.org/info/rfc4656>.
[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>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)", RFC 5357, DOI 10.17487/RFC5357, October 2008, <http://www.rfc-editor.org/info/rfc5357>.
[RFC5357]Hedayat，K.，Krzanowski，R.，Morton，A.，Yum，K.，和J.Babiarz，“双向主动测量协议（TWAMP）”，RFC 5357，DOI 10.17487/RFC5357，2008年10月<http://www.rfc-editor.org/info/rfc5357>.
[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP)", RFC 5618, DOI 10.17487/RFC5618, August 2009, <http://www.rfc-editor.org/info/rfc5618>.
[RFC5618]Morton，A.和K.Hedayat，“双向主动测量协议（TWAMP）的混合安全模式”，RFC 5618，DOI 10.17487/RFC5618，2009年8月<http://www.rfc-editor.org/info/rfc5618>.
[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., Aitken, P., and A. Akhter, "A Framework for Large-Scale Measurement of Broadband Performance (LMAP)", RFC 7594, DOI 10.17487/RFC7594, September 2015, <http://www.rfc-editor.org/info/rfc7594>.
[RFC7594]Eardley，P.，Morton，A.，Bagnulo，M.，Burbridge，T.，Aitken，P.，和A.Akhter，“宽带性能的大规模测量框架（LMAP）”，RFC 7594，DOI 10.17487/RFC7594，2015年9月<http://www.rfc-editor.org/info/rfc7594>.
[RFC7717] Pentikousis, K., Ed., Zhang, E., and Y. Cui, "IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)", RFC 7717, DOI 10.17487/RFC7717, December 2015, <http://www.rfc-editor.org/info/rfc7717>.
[RFC7717]Pentikousis，K.，Ed.，Zhang，E.，和Y.Cui，“单向主动测量协议（OWAMP）和双向主动测量协议（TWAMP）的IKEv2衍生共享密钥”，RFC 7717，DOI 10.17487/RFC77172015年12月<http://www.rfc-editor.org/info/rfc7717>.
Acknowledgements
致谢
The author would like to thank Kostas Pentikousis, Nalini Elkins, Mike Ackermann, and Greg Mirsky for insightful reviews and comments. We thought Spencer Dawkins caught the last of the small errors in his AD review, but Nevil Brownlee found a few more during OPS-DIR review. Roni Even found our use of "IETF Consensus" was out of date with [RFC5226]. Michelle Cotton helped to clarify the IANA considerations.
作者要感谢Kostas Pentikousis、Nalini Elkins、Mike Ackermann和Greg Mirsky的深刻评论和评论。我们认为斯宾塞·道金斯在他的广告评论中抓住了最后一个小错误，但内维尔·布朗利在OPS-DIR评论中发现了更多的错误。Roni甚至发现我们对“IETF共识”的使用已经过时了[RFC5226]。Michelle Cotton帮助澄清了IANA的考虑事项。
Author's Address
作者地址
Al Morton AT&T Labs 200 Laurel Avenue South Middletown,, NJ 07748 United States
美国新泽西州劳雷尔大道南米德尔顿200号阿尔莫顿AT&T实验室，邮编：07748
Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com
URI: http://home.comcast.net/~acmacm/
Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com
URI: http://home.comcast.net/~acmacm/