Internet Engineering Task Force (IETF) W. Cerveny
Request for Comments: 8161 Arbor Networks
Category: Informational R. Bonica
ISSN: 2070-1721 R. Thomas
Juniper Networks
May 2017
Internet Engineering Task Force (IETF) W. Cerveny
Request for Comments: 8161 Arbor Networks
Category: Informational R. Bonica
ISSN: 2070-1721 R. Thomas
Juniper Networks
May 2017
Benchmarking the Neighbor Discovery Protocol
邻居发现协议的基准测试
Abstract
摘要
This document provides benchmarking procedures for the Neighbor Discovery Protocol (NDP). It also proposes metrics by which an NDP implementation's scaling capabilities can be measured.
本文档提供了邻居发现协议（NDP）的基准测试过程。它还提出了衡量NDP实现的扩展能力的指标。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第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/rfc8161.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8161.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 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 ......................................4
2. Test Setup ......................................................4
2.1. Device Under Test (DUT) ....................................4
2.1.1. Interfaces ..........................................4
2.1.2. Neighbor Discovery Protocol (NDP) ...................5
2.1.3. Routing .............................................5
2.2. Tester .....................................................6
2.2.1. Interfaces ..........................................6
2.2.2. Neighbor Discovery Protocol (NDP) ...................6
2.2.3. Routing .............................................6
2.2.4. Test Traffic ........................................7
2.2.5. Counters ............................................8
3. Tests ...........................................................8
3.1. Baseline Test ..............................................8
3.1.1. Procedure ...........................................9
3.1.2. Baseline Test Procedure Flow Chart ..................9
3.1.3. Results ............................................11
3.2. Scaling Test ..............................................11
3.2.1. Procedure ..........................................11
3.2.2. Scaling Test Procedure Flow Chart ..................13
3.2.3. Results ............................................15
4. Measurements Explicitly Excluded ...............................15
4.1. DUT CPU Utilization .......................................15
4.2. Malformed Packets .........................................15
5. IANA Considerations ............................................16
6. Security Considerations ........................................16
7. Normative References ...........................................16
Acknowledgments ...................................................16
Authors' Addresses ................................................17
1. Introduction ....................................................2
1.1. Requirements Language ......................................4
2. Test Setup ......................................................4
2.1. Device Under Test (DUT) ....................................4
2.1.1. Interfaces ..........................................4
2.1.2. Neighbor Discovery Protocol (NDP) ...................5
2.1.3. Routing .............................................5
2.2. Tester .....................................................6
2.2.1. Interfaces ..........................................6
2.2.2. Neighbor Discovery Protocol (NDP) ...................6
2.2.3. Routing .............................................6
2.2.4. Test Traffic ........................................7
2.2.5. Counters ............................................8
3. Tests ...........................................................8
3.1. Baseline Test ..............................................8
3.1.1. Procedure ...........................................9
3.1.2. Baseline Test Procedure Flow Chart ..................9
3.1.3. Results ............................................11
3.2. Scaling Test ..............................................11
3.2.1. Procedure ..........................................11
3.2.2. Scaling Test Procedure Flow Chart ..................13
3.2.3. Results ............................................15
4. Measurements Explicitly Excluded ...............................15
4.1. DUT CPU Utilization .......................................15
4.2. Malformed Packets .........................................15
5. IANA Considerations ............................................16
6. Security Considerations ........................................16
7. Normative References ...........................................16
Acknowledgments ...................................................16
Authors' Addresses ................................................17
When an IPv6 node forwards a packet, it executes the following procedure:
IPv6节点转发数据包时，将执行以下过程：
o Identifies the outbound interface and IPv6 next hop.
o 标识出站接口和IPv6下一跳。
o Queries a local Neighbor Cache (NC) to determine the IPv6 next hop's link-layer address.
o 查询本地邻居缓存（NC）以确定IPv6下一跳的链路层地址。
o Encapsulates the packet in a link-layer header. The link-layer header includes the IPv6 next hop's link-layer address.
o 将数据包封装在链路层报头中。链路层标头包括IPv6下一跳的链路层地址。
o Forwards the packet to the IPv6 next hop.
o 将数据包转发到IPv6下一跳。
IPv6 nodes use the Neighbor Discovery Protocol (NDP) [RFC4861] to maintain the NC. Operational experience [RFC6583] shows that when an implementation cannot maintain a sufficiently complete NC, its ability to forward packets is impaired.
IPv6节点使用邻居发现协议（NDP）[RFC4861]来维护NC。运营经验[RFC6583]表明，当一个实现无法维持一个足够完整的NC时，它转发数据包的能力就会受到损害。
NDP, like any other protocol, consumes processing, memory, and bandwidth resources. Its ability to maintain a sufficiently complete NC depends upon the availability of the above-mentioned resources.
与任何其他协议一样，NDP消耗处理、内存和带宽资源。其维持足够完整的NC的能力取决于上述资源的可用性。
This document provides benchmarking procedures for NDP. Benchmarking procedures include a Baseline Test and an NDP Scaling Test. In both tests, the Device Under Test (DUT) is an IPv6 router. Two physical links (A and B) connect the DUT to a Tester. The Tester sends traffic through Link A to the DUT. The DUT forwards that traffic, through Link B, back to the Tester.
本文件提供了NDP的基准测试程序。基准测试程序包括基线测试和NDP比例测试。在这两个测试中，被测设备（DUT）都是IPv6路由器。两个物理链路（A和B）将DUT连接至测试仪。测试仪通过链路A向DUT发送通信量。DUT通过链路B将该通信转发回测试仪。
The above-mentioned traffic stream contains one or more interleaved flows. An IPv6 Destination Address uniquely identifies each flow. Or, said another way, every packet within a flow has the same IPv6 Destination Address.
上述业务流包含一个或多个交织流。IPv6目标地址唯一标识每个流。或者，换句话说，流中的每个数据包都具有相同的IPv6目标地址。
In the Baseline Test, the traffic stream contains exactly one flow. Because every packet in the stream has the same IPv6 Destination Address, the DUT can forward the entire stream using exactly one NC entry. NDP is exercised minimally, and no packet loss should be observed.
在基线测试中，业务流正好包含一个流。因为流中的每个数据包都具有相同的IPv6目标地址，DUT可以使用一个NC条目转发整个流。NDP的执行最少，并且不应观察到数据包丢失。
The NDP Scaling Test is identical to the Baseline Test, except that the traffic stream contains many flows. In order to forward the stream without loss, the DUT must maintain one NC entry for each flow. If the DUT cannot maintain one NC entry for each flow, packet loss will be observed and attributed to NDP scaling limitations.
NDP缩放测试与基线测试相同，只是交通流包含许多流。为了在不丢失的情况下转发流，DUT必须为每个流保留一个NC条目。如果DUT不能为每个流维护一个NC条目，则将观察到数据包丢失，并将其归因于NDP扩展限制。
This document proposes an NDP scaling metric, called NDP-MAX-NEIGHBORS. NDP-MAX-NEIGHBORS is the maximum number of neighbors to which an IPv6 node can send traffic during periods of high NDP activity.
本文档提出了一种NDP缩放度量，称为NDP-MAX-NEXTORIES。NDP-MAX-Neights是IPv6节点在NDP活动频繁期间可以向其发送流量的最大邻居数。
The procedures described herein reveal how many IPv6 neighbors an NDP implementation can discover. They also provide a rough estimate of the time required to discover those neighbors. However, that estimate does not reflect the maximum rate at which the implementation can discover neighbors. Maximum rate discovery is a topic for further exploration.
本文描述的过程揭示了NDP实现可以发现多少IPv6邻居。它们还粗略估计了发现这些邻居所需的时间。但是，该估计并没有反映实现可以发现邻居的最大速率。最大速率发现是一个有待进一步探索的主题。
The test procedures described herein assume that NDP does not compete with other applications for resources on the DUT. When NDP competes for resources, its scaling characteristics may differ from those reported by the benchmarks described and may vary over time.
本文描述的测试程序假设NDP不会与其他应用程序竞争DUT上的资源。当NDP争夺资源时，其规模特征可能不同于所述基准报告的规模特征，并且可能随时间而变化。
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]中所述进行解释。
+---------------+ +-----------+
| | | |
| | Link A | Device |
| |------------>| Under |
| Tester | | Test |
| |<------------| (DUT) |
| | Link B | |
+---------------+ +-----------+
+---------------+ +-----------+
| | | |
| | Link A | Device |
| |------------>| Under |
| Tester | | Test |
| |<------------| (DUT) |
| | Link B | |
+---------------+ +-----------+
Figure 1: Test Setup
图1：测试设置
The DUT is an IPv6 router. Two links (A and B) connect the DUT to the Tester. Link A capabilities must be identical to Link B capabilities. For example, if the interface to Link A is a 10 Gigabit Ethernet port, the interface to Link B must also be a 10 Gigabit Ethernet port.
DUT是一个IPv6路由器。两个连杆（A和B）将DUT连接至测试仪。链路A功能必须与链路B功能相同。例如，如果链接A的接口是万兆以太网端口，那么链接B的接口也必须是万兆以太网端口。
DUT interfaces are numbered as follows:
DUT接口编号如下：
o Link A - 2001:2:0:0::2/64
o 链接A-2001:2:0:0:：2/64
o Link B - 2001:2:0:1::1/64
o 链接B-2001:2:0:1:：1/64
Both DUT interfaces should be configured with a 1500-byte MTU. However, if they cannot support a 1500-byte MTU, they may be configured with a 1280-byte MTU.
两个DUT接口均应配置1500字节的MTU。但是，如果它们不能支持1500字节的MTU，则可以配置1280字节的MTU。
NDP is enabled on both DUT interfaces. Therefore, the DUT emits both solicited and unsolicited Router Advertisement (RA) messages. The DUT emits an RA message at least once every 600 seconds and no more frequently than once every 200 seconds.
NDP在两个DUT接口上都启用。因此，DUT发出请求和非请求的路由器广告（RA）消息。DUT至少每600秒发出一次RA消息，频率不超过每200秒一次。
When the DUT sends an RA message, it includes the following information:
当DUT发送RA消息时，它包括以下信息：
o Router Lifetime - 1800 seconds
o 路由器寿命-1800秒
o Reachable Time - 0 seconds
o 可到达时间-0秒
o Retrans Time - 0 seconds
o 重传时间-0秒
o Source Link-Layer Address - link-layer address of DUT interface
o 源链路层地址-DUT接口的链路层地址
o M-bit is clear (0)
o M位清除（0）
o O-bit is clear (0)
o O位清除（0）
The above-mentioned values are chosen because they are the default values specified in RFC 4861.
选择上述值是因为它们是RFC 4861中指定的默认值。
NDP manages the NC. Each NC entry represents an on-link neighbor and is identified by the neighbor's on-link unicast IP address. As per RFC 4861, each NC entry needs to be refreshed periodically. NDP refreshes NC entries by exchanging Neighbor Solicitation (NS) and Neighbor Advertisement (NA) messages.
NDP管理NC。每个NC条目表示一个链路上邻居，并由邻居的链路上单播IP地址标识。根据RFC 4861，每个NC条目需要定期刷新。NDP通过交换邻居请求（NS）和邻居公告（NA）消息来刷新NC条目。
No static NC entries are configured on the DUT.
DUT上未配置静态NC条目。
The DUT maintains a direct route to 2001:2:0:0/64 through Link A. It also maintains a direct route to 2001:2:0:1/64 through Link B. No static routes or dynamic routing protocols are configured on the DUT.
DUT通过链路a维护到2001:2:0:0/64的直接路由。它还通过链路B维护到2001:2:0:1/64的直接路由。DUT上未配置静态路由或动态路由协议。
Interfaces are numbered as follows:
接口编号如下：
o Link A - 2001:2:0:0::1/64
o 链接A-2001:2:0:0:：1/64
o Link B - Multiple addresses are configured on Link B. These addresses are drawn sequentially from the 2001:2:0:1::/64 address block. The first address is 2001:2:0:1::2/64. Subsequent addresses are 2001:2:0:1::3/64, 2001:2:0:1::4/64, 2001:2:0:1::5/64, etc. The number of configured addresses should be the expected value of NDP-MAX-NEIGHBORS times 1.1.
o 链路B-在链路B上配置了多个地址。这些地址从2001:2:0:1:：/64地址块顺序绘制。第一个地址是2001:2:0:1:：2/64。后续地址为2001:2:0:1:：3/64、2001:2:0:1:：4/64、2001:2:0:1:：5/64等。配置的地址数应为NDP-MAX-Neights的预期值乘以1.1。
Both Tester interfaces should be configured with a 1500-byte MTU. However, if they cannot support a 1500-byte MTU, they may be configured with a 1280-byte MTU.
两个测试仪接口均应配置1500字节的MTU。但是，如果它们不能支持1500字节的MTU，则可以配置1280字节的MTU。
NDP is enabled on both Tester interfaces. Therefore, upon initiation, the Tester sends Router Solicitation (RS) messages and waits for Router Advertisement (RA) messages. The Tester also exchanges Neighbor Solicitation (NS) and Neighbor Advertisement (NA) messages with the DUT.
NDP在两个测试仪接口上都已启用。因此，在启动时，测试仪发送路由器请求（RS）消息并等待路由器公告（RA）消息。测试仪还与DUT交换邻居请求（NS）和邻居公告（NA）消息。
No static NC entries are configured on the Tester.
测试仪上未配置静态NC条目。
The Tester maintains a direct route to 2001:2:0:0/64 through Link A. It also maintains a direct route to 2001:2:0:1/64 through Link B. No static routes or dynamic routing protocols are configured on the Tester.
测试仪通过链路a维护到2001:2:0:0/64的直接路由。它还通过链路B维护到2001:2:0:1/64的直接路由。测试仪上未配置静态路由或动态路由协议。
The Tester sends a stream of test traffic through Link A to the DUT. The test traffic stream contains one or more interleaved flows. Flows are numbered 1 through N, sequentially.
测试仪通过链路a向DUT发送测试通信流。测试业务流包含一个或多个交织流。流按顺序编号为1到N。
Within each flow, each packet contains an IPv6 header, and each IPv6 header contains the following information:
在每个流中，每个数据包包含一个IPv6标头，每个IPv6标头包含以下信息：
o Version - 6
o 版本-6
o Traffic Class - 0
o 交通等级-0
o Flow Label - 0
o 流标签-0
o Payload Length - 0
o 有效载荷长度-0
o Next Header - IPv6-NoNxt (59)
o 下一个标头-IPv6非文本（59）
o Hop Limit - 255
o 跃点限制-255
o Source Address - 2001:2:0:0::1
o 源地址-2001:2:0:0:：1
o Destination Address - The first 64 bits of the Destination Address are 2001:2:0:1::. The next 64 are uniquely associated with the flow. Every packet in the first flow carries the Destination Address 2001:2:0:1::2. Every subsequent flow has an IP address one greater than the last (i.e., 2001:2:0:1::3, 2001:2:0:1::4, etc.).
o 目标地址-目标地址的前64位是2001:2:0:1:：。下一个64与流唯一关联。第一个流中的每个数据包都携带目标地址2001:2:0:1:：2。每个后续流的IP地址都比最后一个流大一个（即，2001:2:0:1:：3、2001:2:0:1:：4等）。
In order to avoid link congestion, test traffic is offered at a rate not to exceed 50% of available link bandwidth. In order to avoid burstiness and buffer occupancy, every packet in the stream is exactly 40 bytes long (i.e., the length of an IPv6 header with no IPv6 payload). Furthermore, the gap between packets is identical.
为了避免链路拥塞，以不超过可用链路带宽50%的速率提供测试流量。为了避免突发性和缓冲区占用，流中的每个数据包的长度正好为40字节（即，没有IPv6负载的IPv6报头的长度）。此外，分组之间的间隔是相同的。
During the course of a test, the number of flows that the test stream contains may increase. When this occurs, the rate at which test traffic is offered remains constant. For example, assume that a test stream is offered at a rate of 1,000 packets per second. This stream contains two flows, each contributing 500 packets per second to the 1,000 packet per second aggregate. When a third stream is added to the flow, all three streams must contribute 333 packets per second in order to maintain the 1,000 packet per second limit. (As in this example, rounding error is acceptable.)
在测试过程中，测试流包含的流的数量可能会增加。发生这种情况时，提供测试流量的速率保持不变。例如，假设以每秒1000个包的速率提供测试流。此流包含两个流，每个流每秒贡献500个数据包到每秒1000个数据包的聚合。当第三个流被添加到流中时，所有三个流必须每秒贡献333个分组，以保持每秒1000个分组的限制。（如本例所示，舍入误差是可以接受的。）
The DUT attempts to forward every packet in the test stream through Link B to the Tester. It does this because:
DUT尝试通过链路B将测试流中的每个数据包转发给测试仪。它这样做是因为：
o Every packet in the test stream has a Destination Address drawn from the 2001:2:0:1::/64 address block.
o Every packet in the test stream has a Destination Address drawn from the 2001:2:0:1::/64 address block.translate error, please retry
o The DUT has a direct route to 2001:2:0:1/64 through Link B.
o DUT可通过链路B直达2001:2:0:1/64。
On the Tester, two counters are configured for each flow. One counter, configured on Link A, increments when the Tester sends a packet belonging to the flow. The other counter, configured on Link B, increments when the Tester receives a packet from the flow. In order for a packet to be associated with a flow, the following conditions must all be true:
在测试仪上，为每个流配置两个计数器。当测试仪发送属于流的数据包时，在链路A上配置的一个计数器递增。在链路B上配置的另一个计数器在测试仪从流接收到数据包时递增。为了使数据包与流相关联，以下条件必须全部为真：
o The IPv6 Destination Address must be that of the flow.
o IPv6目标地址必须是流的目标地址。
o The IPv6 Next Header must be IPv6-NoNxt (59).
o IPv6下一个标头必须是IPv6 NoNxt（59）。
The following counters also are configured on both Tester Interfaces:
两个测试仪接口上也配置了以下计数器：
o RS packets sent
o 发送的RS数据包
o RA packets received
o 收到的RA数据包
o NS packets sent
o 已发送NS数据包
o NS packets received
o 收到NS数据包
o NA packets sent
o 已发送数据包
o NA packets received
o 收到的NA数据包
o Total packets sent
o 发送的数据包总数
o Total packets received
o 收到的数据包总数
The purpose of the Baseline Test is to ensure that the DUT can forward every packet in the test stream, without loss, when NDP is minimally exercised and not operating near its scaling limit.
基线测试的目的是确保当NDP被最小限度地执行并且没有在其缩放限制附近操作时，DUT可以在不丢失的情况下转发测试流中的每个数据包。
o On the DUT, clear the NC.
o 在DUT上，清除NC。
o On the Tester, clear all counters.
o 在检测仪上，清除所有计数器。
o On the Tester, set a timer to expire in 60 seconds.
o 在检测仪上，将计时器设置为60秒后过期。
o On the Tester, start the test stream with exactly one flow (i.e., IPv6 Destination Address equals 2001:2:0:1::2).
o 在测试仪上，仅使用一个流启动测试流（即IPv6目标地址等于2001:2:0:1:：2）。
o Wait for either the timer to expire or the packets-received counter associated with the flow to increment.
o 等待计时器过期或与流相关联的已接收数据包计数器递增。
o If the timer expires, stop the test stream and end the test.
o 如果计时器过期，停止测试流并结束测试。
o If the packets-received counter increments, pause the traffic stream, log the initial counter values, clear the counters, reset the timer to expire in 1800 seconds, and restart the traffic stream.
o 如果收到的数据包计数器递增，则暂停流量流，记录初始计数器值，清除计数器，将计时器重置为1800秒后过期，然后重新启动流量流。
o When the timer expires, stop the test stream, wait sufficient time for any queued packets to exit, log the final counter values, and end the test.
o 计时器过期时，停止测试流，等待足够的时间让任何排队的数据包退出，记录最终计数器值，然后结束测试。
+--------------------------+
| On the DUT, clear the NC |
+-------------|------------+
|
+------------------v------------------+
| On the Tester, clear all counters |
+------------------|------------------+
|
+------------------v-----------------+
| On the Tester, set a |
| timer to expire in |
| 60 seconds |
+------------------|-----------------+
|
+------------------v-----------------+
|On the Tester, start the test stream|
|with exactly one flow (i.e., IPv6 |
|Destination Address equals |
|2001:2:0:0:1::2) |
+------------------|-----------------+
|
+--------------------------+
| On the DUT, clear the NC |
+-------------|------------+
|
+------------------v------------------+
| On the Tester, clear all counters |
+------------------|------------------+
|
+------------------v-----------------+
| On the Tester, set a |
| timer to expire in |
| 60 seconds |
+------------------|-----------------+
|
+------------------v-----------------+
|On the Tester, start the test stream|
|with exactly one flow (i.e., IPv6 |
|Destination Address equals |
|2001:2:0:0:1::2) |
+------------------|-----------------+
|
|
+------------------v-----------------+
|Wait for either the timer to expire |
|or packets-received counter |
|associated with the flow to |
|increment |
+------------------|-----------------+
|
/-------v-------\
/ \ Yes +--------------+
|Did timer expire?|-------| End the test |
\ / +--------------+
\-------|-------/
| No
|
/---------v--------\
/ \ No +--------------+
|Did packets-received|------| End the test |
|counter increment? | +--------------+
\ /
\---------|--------/
| Yes
|
+------------------v-----------------+
|Pause traffic stream, log initial |
|counter values, clear the counters, |
|reset the timer to expire in 1800 |
|seconds, and restart traffic stream |
+------------------|-----------------+
|
+------------------v-----------------+
|When timer expires, stop the test |
|stream, wait sufficient time for |
|any queued packets to exit, log the |
|final counter values |
+------------------|-----------------+
|
+----v---+
|End test|
+--------+
|
+------------------v-----------------+
|Wait for either the timer to expire |
|or packets-received counter |
|associated with the flow to |
|increment |
+------------------|-----------------+
|
/-------v-------\
/ \ Yes +--------------+
|Did timer expire?|-------| End the test |
\ / +--------------+
\-------|-------/
| No
|
/---------v--------\
/ \ No +--------------+
|Did packets-received|------| End the test |
|counter increment? | +--------------+
\ /
\---------|--------/
| Yes
|
+------------------v-----------------+
|Pause traffic stream, log initial |
|counter values, clear the counters, |
|reset the timer to expire in 1800 |
|seconds, and restart traffic stream |
+------------------|-----------------+
|
+------------------v-----------------+
|When timer expires, stop the test |
|stream, wait sufficient time for |
|any queued packets to exit, log the |
|final counter values |
+------------------|-----------------+
|
+----v---+
|End test|
+--------+
Figure 2: Baseline Test Procedure Flow Chart
图2：基线测试程序流程图
The log contains initial and final values for the following counters:
日志包含以下计数器的初始值和最终值：
o packets-sent
o 发送的数据包
o packets-received
o 收到的数据包
The initial values of packets-sent and packets-received may be equal to one another. If these values are identical, none of the initial packets belonging to the flow were lost. However, if the initial value of packets-sent is greater than the initial value of packets-received, initial packets were lost. This loss of initial packets is acceptable.
发送的分组和接收的分组的初始值可以彼此相等。如果这些值相同，则属于流的所有初始数据包都不会丢失。但是，如果发送的数据包的初始值大于接收的数据包的初始值，则初始数据包丢失。初始数据包的这种丢失是可以接受的。
The final values of packets-sent and packets-received should be equal to one another. If they are not, an error has occurred. Because this error is likely to affect Scaling Test results, the error must be corrected before the Scaling Test is executed.
发送的数据包和接收的数据包的最终值应彼此相等。如果没有，则发生错误。由于此错误可能会影响缩放测试结果，因此必须在执行缩放测试之前更正此错误。
The purpose of the Scaling Test is to discover the number of neighbors to which an IPv6 node can send traffic during periods of high NDP activity. We call this number NDP-MAX-NEIGHBORS.
缩放测试的目的是发现IPv6节点在NDP活动频繁期间可以向其发送流量的邻居数量。我们称这个号码为NDP-MAX-Neights。
Execute the following procedure:
执行以下过程：
o On the DUT, clear the NC.
o 在DUT上，清除NC。
o On the Tester, clear all counters.
o 在检测仪上，清除所有计数器。
o On the Tester, set a timer to expire in 60 seconds.
o 在检测仪上，将计时器设置为60秒后过期。
o On the Tester, start the test stream with exactly one flow (i.e., IPv6 Destination Address equals 2001:2:0:1::2).
o 在测试仪上，仅使用一个流启动测试流（即IPv6目标地址等于2001:2:0:1:：2）。
o Wait for either the timer to expire or the packets-received counter associated with the flow to increment.
o 等待计时器过期或与流相关联的已接收数据包计数器递增。
o If the timer expires, stop the test stream and end the test.
o 如果计时器过期，停止测试流并结束测试。
o If the packets-received counter increments, execute the following procedure N times, starting at 2 and ending at the expected value of NDP-MAX-NEIGHBORS times 1.1.
o 如果接收到的数据包计数器递增，则执行以下过程N次，从2开始，以预期值NDP-MAX-neighbories乘以1.1结束。
* Pause the test stream.
* 暂停测试流。
* Log the time and the value of N minus one.
* 记录时间和N减1的值。
* Clear the packets-sent and packets-received counters associated with the previous flow (i.e., N minus one).
* 清除与前一个流相关联的已发送数据包和已接收数据包计数器（即N减去1）。
* Reset the timer to expire in 60 seconds.
* 将计时器重置为60秒后过期。
* Add the next flow to the test stream (i.e., IPv6 Destination Address is a function of N).
* 将下一个流添加到测试流（即，IPv6目标地址是N的函数）。
* Restart the test stream.
* 重新启动测试流。
* Wait for either the timer to expire or the packets-received counter associated with the new flow to increment.
* 等待计时器过期或与新流相关联的接收数据包计数器递增。
After the procedure described above has been executed N times, clear the timer and reset it to expire in 1800 seconds. When the timer expires, stop the stream, log all counters, and end the test (after waiting sufficient time for any queued packets to exit).
执行上述步骤N次后，清除计时器并将其重置为1800秒后过期。当计时器过期时，停止流，记录所有计数器，并结束测试（等待足够的时间让任何排队的数据包退出）。
+--------------------------+
| On the DUT, clear the NC |
+-------------|------------+
|
+------------------v------------------+
| On the Tester, clear all counters |
+------------------|------------------+
|
+------------------v-----------------+
| On the Tester, set a |
| timer to expire in |
| 60 seconds |
+------------------|-----------------+
|
+------------------v-----------------+
|On the Tester, start the test stream|
|with exactly one flow (i.e., IPv6 |
|Destination Address equals |
|2001:2:0:0:1::2) |
+------------------|-----------------+
|
+------------------v-----------------+
|Wait for either the timer to expire |
|or packets-received counter |
|associated with the flow to |
|increment |
+------------------|-----------------+
|
/-------v-------\
/ \ Yes +--------------+
|Did timer expire?|-------| End test |
\ / | and return |
\-------|-------/ +--------------+
| No
|
/---------v--------\
/ \ No +--------------+
|Did packets-received|------| End test |
|counter increment? | | and return |
\ / +--------------+
\---------|--------/
| Yes
|
+------v------+
| N=2 |
+------|------+
+--------------------------+
| On the DUT, clear the NC |
+-------------|------------+
|
+------------------v------------------+
| On the Tester, clear all counters |
+------------------|------------------+
|
+------------------v-----------------+
| On the Tester, set a |
| timer to expire in |
| 60 seconds |
+------------------|-----------------+
|
+------------------v-----------------+
|On the Tester, start the test stream|
|with exactly one flow (i.e., IPv6 |
|Destination Address equals |
|2001:2:0:0:1::2) |
+------------------|-----------------+
|
+------------------v-----------------+
|Wait for either the timer to expire |
|or packets-received counter |
|associated with the flow to |
|increment |
+------------------|-----------------+
|
/-------v-------\
/ \ Yes +--------------+
|Did timer expire?|-------| End test |
\ / | and return |
\-------|-------/ +--------------+
| No
|
/---------v--------\
/ \ No +--------------+
|Did packets-received|------| End test |
|counter increment? | | and return |
\ / +--------------+
\---------|--------/
| Yes
|
+------v------+
| N=2 |
+------|------+
|
/--------------v-------------\
/ Is \ No +----------+
| N < NDP-MAX-NEIGHBORS |----| End test |
-------| times 1.1 | +----------+
| \ /
| \--------------|-------------/
| | Yes
| +-----------v----------+
| |Pause the test stream |
| +-----------|----------+
| |
| +----------v----------+
| |Log the time and the |
| |value of N minus one |
| +----------|----------+
| |
| +-----------v-----------+
| |Clear the packets-sent |
| |and packets-received |
| |counters associated |
| |with the previous flow |
| |(i.e., N minus one) |
| +-----------|-----------+
| |
| +----------v----------+
| |Reset the timer to |
| |expire in 60 seconds |
| +----------|----------+
| |
| +--------------v---------------+
| |Add the next flow to the test |
| |stream (i.e., IPv6 Destination|
| |Address is a function of N) |
| +--------------|---------------+
| |
| +------v------+
| | N=N+1 |
| +------|------+
| |
| +----------v------------+
------------|Restart the test stream|
+-----------------------+
|
/--------------v-------------\
/ Is \ No +----------+
| N < NDP-MAX-NEIGHBORS |----| End test |
-------| times 1.1 | +----------+
| \ /
| \--------------|-------------/
| | Yes
| +-----------v----------+
| |Pause the test stream |
| +-----------|----------+
| |
| +----------v----------+
| |Log the time and the |
| |value of N minus one |
| +----------|----------+
| |
| +-----------v-----------+
| |Clear the packets-sent |
| |and packets-received |
| |counters associated |
| |with the previous flow |
| |(i.e., N minus one) |
| +-----------|-----------+
| |
| +----------v----------+
| |Reset the timer to |
| |expire in 60 seconds |
| +----------|----------+
| |
| +--------------v---------------+
| |Add the next flow to the test |
| |stream (i.e., IPv6 Destination|
| |Address is a function of N) |
| +--------------|---------------+
| |
| +------v------+
| | N=N+1 |
| +------|------+
| |
| +----------v------------+
------------|Restart the test stream|
+-----------------------+
Figure 3: Scaling Test Procedure Flow Chart
图3：缩放测试程序流程图
The test report includes the following:
测试报告包括以下内容：
o A description of the DUT (make, model, processor, memory, and interfaces)
o DUT的说明（品牌、型号、处理器、内存和接口）
o Rate at which the Tester offers test traffic to the DUT (measured in packets per second)
o 测试仪向DUT提供测试流量的速率（以每秒数据包为单位）
o A log that records the time at which each flow was introduced to the test stream and the final value of all counters
o 记录每个流引入测试流的时间和所有计数器的最终值的日志
o The expected value of NDP-MAX-NEIGHBORS
o NDP-MAX-Neights的期望值
o The actual value of NDP-MAX-NEIGHBORS
o NDP-MAX-Neights的实际值
NDP-MAX-NEIGHBORS is equal to the number of counter pairs where packets-sent is equal to packets-received. Two counters are members of a pair if they are both associated with the same flow. If packets-sent is equal to packets-received for every counter pair, the test should be repeated with a larger expected value of NDP-MAX-NEIGHBORS.
NDP-MAX-Neights等于发送的数据包等于接收的数据包的计数器对数。如果两个计数器都与同一个流关联，则它们是一对的成员。如果发送的数据包等于每个计数器对接收的数据包，则应使用更大的预期值NDP-MAX-neights重复测试。
If an implementation abides by the recommendation of Section 7.1 of RFC 6583, for any given counter pair, packets-received will either be equal to zero or packets-sent.
如果实现符合RFC 6583第7.1节的建议，对于任何给定的计数器对，接收的数据包将等于零或发送的数据包。
The log documents the time at which each flow was introduced to the test stream. This log reveals the effect of NC size to the time required to discover a new IPv6 neighbor.
日志记录将每个流引入测试流的时间。此日志显示NC大小对发现新IPv6邻居所需时间的影响。
These measurements aren't recommended because of the itemized reasons below:
由于以下逐项原因，不建议进行这些测量：
This measurement relies on the DUT to provide utilization information, which is not externally observable (not black-box). However, some testing organizations may find the CPU utilization is useful auxiliary information specific to the DUT model, etc.
该测量依赖于DUT提供利用率信息，这是外部无法观察到的（非黑匣子）。然而，一些测试机构可能会发现CPU利用率是DUT模型等的有用辅助信息。
This benchmarking test is not intended to test DUT behavior in the presence of malformed packets.
此基准测试的目的不是在存在格式错误的数据包的情况下测试DUT的行为。
This document does not require any IANA actions.
本文件不要求IANA采取任何行动。
Benchmarking activities as described in this memo are limited to technology characterization using controlled stimuli in a laboratory environment, with dedicated address space and the constraints specified in the sections above.
本备忘录中所述的基准测试活动仅限于在实验室环境中使用受控刺激进行技术表征，具有专用地址空间和上述章节中规定的约束条件。
The benchmarking network topology will be an independent test setup and MUST NOT be connected to devices that may forward the test traffic into a production network or misroute traffic to the test management network.
基准网络拓扑将是一个独立的测试设置，不得连接到可能将测试流量转发到生产网络或将流量错误路由到测试管理网络的设备。
Further, benchmarking is performed on a "black-box" basis, relying solely on measurements observable external to the DUT or System Under Test (SUT). Special capabilities SHOULD NOT exist in the DUT/SUT specifically for benchmarking purposes.
此外，基准测试是在“黑盒”基础上进行的，仅依赖于DUT或被测系统（SUT）外部可观察到的测量值。DUT/SUT中不应存在专门用于基准测试的特殊能力。
Any implications for network security arising from the DUT/SUT SHOULD be identical in the lab and in production networks.
DUT/SUT对网络安全的任何影响应在实验室和生产网络中相同。
[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>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, DOI 10.17487/RFC4861, September 2007, <http://www.rfc-editor.org/info/rfc4861>.
[RFC4861]Narten，T.，Nordmark，E.，Simpson，W.，和H.Soliman，“IP版本6（IPv6）的邻居发现”，RFC 4861，DOI 10.17487/RFC48612007年9月<http://www.rfc-editor.org/info/rfc4861>.
[RFC6583] Gashinsky, I., Jaeggli, J., and W. Kumari, "Operational Neighbor Discovery Problems", RFC 6583, DOI 10.17487/RFC6583, March 2012, <http://www.rfc-editor.org/info/rfc6583>.
[RFC6583]Gashinsky，I.，Jaeggli，J.，和W.Kumari，“操作邻居发现问题”，RFC 6583，DOI 10.17487/RFC6583，2012年3月<http://www.rfc-editor.org/info/rfc6583>.
Acknowledgments
致谢
Helpful comments and suggestions were offered by Al Morton, Joel Jaeggli, Nalini Elkins, Scott Bradner, and Ram Krishnan on the BMWG email list and at BMWG meetings. Precise grammatical corrections and suggestions were offered by Ann Cerveny.
Al Morton、Joel Jaeggli、Nalini Elkins、Scott Bradner和Ram Krishnan在BMWG电子邮件列表和BMWG会议上提出了有益的意见和建议。Ann Cerveny提供了精确的语法更正和建议。
Authors' Addresses
作者地址
Bill Cerveny Arbor Networks 2727 South State Street Ann Arbor, MI 48104 United States of America
美国密歇根州安阿伯南州立街2727号比尔·塞维尼·阿伯网络公司，邮编：48104
Email: wcerveny@arbor.net
Email: wcerveny@arbor.net
Ron Bonica Juniper Networks 2251 Corporate Park Drive Herndon, VA 20170 United States of America
Ron Bonica Juniper Networks 2251美国弗吉尼亚州赫恩登市企业园大道，邮编：20170
Email: rbonica@juniper.net
Email: rbonica@juniper.net
Reji Thomas Juniper Networks Elnath-Exora Business Park Survey Bangalore, KA 560103 India
Reji Thomas Juniper Networks Elnath Exora商业园调查，印度，堪萨斯州班加罗尔560103
Email: rejithomas@juniper.net
Email: rejithomas@juniper.net