Internet Engineering Task Force (IETF)                       S. Poretsky
Request for Comments: 6412                          Allot Communications
Category: Informational                                        B. Imhoff
ISSN: 2070-1721                                              F5 Networks
                                                           K. Michielsen
                                                           Cisco Systems
                                                           November 2011
        
Internet Engineering Task Force (IETF)                       S. Poretsky
Request for Comments: 6412                          Allot Communications
Category: Informational                                        B. Imhoff
ISSN: 2070-1721                                              F5 Networks
                                                           K. Michielsen
                                                           Cisco Systems
                                                           November 2011
        

Terminology for Benchmarking Link-State IGP Data-Plane Route Convergence

基准链路状态IGP数据平面路由收敛术语

Abstract

摘要

This document describes the terminology for benchmarking link-state Interior Gateway Protocol (IGP) route convergence. The terminology is to be used for benchmarking IGP convergence time through externally observable (black-box) data-plane measurements. The terminology can be applied to any link-state IGP, such as IS-IS and OSPF.

本文档描述了链路状态内部网关协议(IGP)路由聚合基准测试术语。该术语用于通过外部可观测(黑箱)数据平面测量对IGP收敛时间进行基准测试。该术语可应用于任何链路状态IGP,如IS-IS和OSPF。

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 5741.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。并非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/rfc6412.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc6412.

Copyright Notice

版权公告

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2011 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

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从该文档中提取的代码组件必须

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.

包括信托法律条款第4.e节中所述的简化BSD许可证文本,且不提供简化BSD许可证中所述的担保。

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.

本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下,不得在IETF标准流程之外修改本文件,也不得在IETF标准流程之外创建其衍生作品,除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。

Table of Contents

目录

   1.  Introduction and Scope . . . . . . . . . . . . . . . . . . . .  4
   2.  Existing Definitions . . . . . . . . . . . . . . . . . . . . .  4
   3.  Term Definitions . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Convergence Types  . . . . . . . . . . . . . . . . . . . .  5
       3.1.1.  Route Convergence  . . . . . . . . . . . . . . . . . .  5
       3.1.2.  Full Convergence . . . . . . . . . . . . . . . . . . .  5
     3.2.  Instants . . . . . . . . . . . . . . . . . . . . . . . . .  6
       3.2.1.  Traffic Start Instant  . . . . . . . . . . . . . . . .  6
       3.2.2.  Convergence Event Instant  . . . . . . . . . . . . . .  6
       3.2.3.  Convergence Recovery Instant . . . . . . . . . . . . .  7
       3.2.4.  First Route Convergence Instant  . . . . . . . . . . .  8
     3.3.  Transitions  . . . . . . . . . . . . . . . . . . . . . . .  8
       3.3.1.  Convergence Event Transition . . . . . . . . . . . . .  8
       3.3.2.  Convergence Recovery Transition  . . . . . . . . . . .  9
     3.4.  Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.4.1.  Local Interface  . . . . . . . . . . . . . . . . . . . 10
       3.4.2.  Remote Interface . . . . . . . . . . . . . . . . . . . 10
       3.4.3.  Preferred Egress Interface . . . . . . . . . . . . . . 10
       3.4.4.  Next-Best Egress Interface . . . . . . . . . . . . . . 11
     3.5.  Benchmarking Methods . . . . . . . . . . . . . . . . . . . 11
       3.5.1.  Rate-Derived Method  . . . . . . . . . . . . . . . . . 11
       3.5.2.  Loss-Derived Method  . . . . . . . . . . . . . . . . . 14
       3.5.3.  Route-Specific Loss-Derived Method . . . . . . . . . . 15
     3.6.  Benchmarks . . . . . . . . . . . . . . . . . . . . . . . . 17
       3.6.1.  Full Convergence Time  . . . . . . . . . . . . . . . . 17
       3.6.2.  First Route Convergence Time . . . . . . . . . . . . . 18
       3.6.3.  Route-Specific Convergence Time  . . . . . . . . . . . 18
       3.6.4.  Loss-Derived Convergence Time  . . . . . . . . . . . . 20
       3.6.5.  Route Loss of Connectivity Period  . . . . . . . . . . 21
       3.6.6.  Loss-Derived Loss of Connectivity Period . . . . . . . 22
     3.7.  Measurement Terms  . . . . . . . . . . . . . . . . . . . . 23
       3.7.1.  Convergence Event  . . . . . . . . . . . . . . . . . . 23
       3.7.2.  Convergence Packet Loss  . . . . . . . . . . . . . . . 23
       3.7.3.  Connectivity Packet Loss . . . . . . . . . . . . . . . 24
       3.7.4.  Packet Sampling Interval . . . . . . . . . . . . . . . 24
       3.7.5.  Sustained Convergence Validation Time  . . . . . . . . 25
       3.7.6.  Forwarding Delay Threshold . . . . . . . . . . . . . . 26
     3.8.  Miscellaneous Terms  . . . . . . . . . . . . . . . . . . . 26
       3.8.1.  Impaired Packet  . . . . . . . . . . . . . . . . . . . 26
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 27
   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
   6.  Normative References . . . . . . . . . . . . . . . . . . . . . 27
        
   1.  Introduction and Scope . . . . . . . . . . . . . . . . . . . .  4
   2.  Existing Definitions . . . . . . . . . . . . . . . . . . . . .  4
   3.  Term Definitions . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Convergence Types  . . . . . . . . . . . . . . . . . . . .  5
       3.1.1.  Route Convergence  . . . . . . . . . . . . . . . . . .  5
       3.1.2.  Full Convergence . . . . . . . . . . . . . . . . . . .  5
     3.2.  Instants . . . . . . . . . . . . . . . . . . . . . . . . .  6
       3.2.1.  Traffic Start Instant  . . . . . . . . . . . . . . . .  6
       3.2.2.  Convergence Event Instant  . . . . . . . . . . . . . .  6
       3.2.3.  Convergence Recovery Instant . . . . . . . . . . . . .  7
       3.2.4.  First Route Convergence Instant  . . . . . . . . . . .  8
     3.3.  Transitions  . . . . . . . . . . . . . . . . . . . . . . .  8
       3.3.1.  Convergence Event Transition . . . . . . . . . . . . .  8
       3.3.2.  Convergence Recovery Transition  . . . . . . . . . . .  9
     3.4.  Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.4.1.  Local Interface  . . . . . . . . . . . . . . . . . . . 10
       3.4.2.  Remote Interface . . . . . . . . . . . . . . . . . . . 10
       3.4.3.  Preferred Egress Interface . . . . . . . . . . . . . . 10
       3.4.4.  Next-Best Egress Interface . . . . . . . . . . . . . . 11
     3.5.  Benchmarking Methods . . . . . . . . . . . . . . . . . . . 11
       3.5.1.  Rate-Derived Method  . . . . . . . . . . . . . . . . . 11
       3.5.2.  Loss-Derived Method  . . . . . . . . . . . . . . . . . 14
       3.5.3.  Route-Specific Loss-Derived Method . . . . . . . . . . 15
     3.6.  Benchmarks . . . . . . . . . . . . . . . . . . . . . . . . 17
       3.6.1.  Full Convergence Time  . . . . . . . . . . . . . . . . 17
       3.6.2.  First Route Convergence Time . . . . . . . . . . . . . 18
       3.6.3.  Route-Specific Convergence Time  . . . . . . . . . . . 18
       3.6.4.  Loss-Derived Convergence Time  . . . . . . . . . . . . 20
       3.6.5.  Route Loss of Connectivity Period  . . . . . . . . . . 21
       3.6.6.  Loss-Derived Loss of Connectivity Period . . . . . . . 22
     3.7.  Measurement Terms  . . . . . . . . . . . . . . . . . . . . 23
       3.7.1.  Convergence Event  . . . . . . . . . . . . . . . . . . 23
       3.7.2.  Convergence Packet Loss  . . . . . . . . . . . . . . . 23
       3.7.3.  Connectivity Packet Loss . . . . . . . . . . . . . . . 24
       3.7.4.  Packet Sampling Interval . . . . . . . . . . . . . . . 24
       3.7.5.  Sustained Convergence Validation Time  . . . . . . . . 25
       3.7.6.  Forwarding Delay Threshold . . . . . . . . . . . . . . 26
     3.8.  Miscellaneous Terms  . . . . . . . . . . . . . . . . . . . 26
       3.8.1.  Impaired Packet  . . . . . . . . . . . . . . . . . . . 26
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 27
   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
   6.  Normative References . . . . . . . . . . . . . . . . . . . . . 27
        
1. Introduction and Scope
1. 导言和范围

This document is a companion to [Po11m], which contains the methodology to be used for benchmarking link-state Interior Gateway Protocol (IGP) convergence by observing the data plane. The purpose of this document is to introduce new terms required to complete execution of the Link-State IGP Data-Plane Route Convergence methodology [Po11m].

本文件是[Po11m]的配套文件,其中包含通过观察数据平面对链路状态内部网关协议(IGP)收敛进行基准测试的方法。本文件旨在介绍完成链路状态IGP数据平面路由收敛方法[Po11m]执行所需的新术语。

IGP convergence time is measured by observing the data plane through the Device Under Test (DUT) at the Tester. The methodology and terminology to be used for benchmarking IGP convergence can be applied to IPv4 and IPv6 traffic and link-state IGPs such as Intermediate System to Intermediate System (IS-IS) [Ca90][Ho08], Open Shortest Path First (OSPF) [Mo98] [Co08], and others.

IGP收敛时间通过在测试仪上通过被测设备(DUT)观察数据平面来测量。用于基准IGP融合的方法和术语可应用于IPv4和IPv6流量和链路状态IGP,如中间系统到中间系统(IS-IS)[Ca90][Ho08]、开放最短路径优先(OSPF)[Mo98][Co08]等。

2. Existing Definitions
2. 现有定义

This document uses existing terminology defined in other IETF documents. Examples include, but are not limited to:

本文件使用其他IETF文件中定义的现有术语。示例包括但不限于:

Throughput [Br91], Section 3.17 Offered Load [Ma98], Section 3.5.2 Forwarding Rate [Ma98], Section 3.6.1 Device Under Test (DUT) [Ma98], Section 3.1.1 System Under Test (SUT) [Ma98], Section 3.1.2 Out-of-Order Packet [Po06], Section 3.3.4 Duplicate Packet [Po06], Section 3.3.5 Stream [Po06], Section 3.3.2 Forwarding Delay [Po06], Section 3.2.4 IP Packet Delay Variation (IPDV) [De02], Section 1.2 Loss Period [Ko02], Section 4

吞吐量[Br91],第3.17节提供负载[Ma98],第3.5.2节转发速率[Ma98],第3.6.1节被测设备(DUT)[Ma98],第3.1.1节被测系统(SUT)[Ma98],第3.1.2节无序数据包[Po06],第3.3.4节重复数据包[Po06],第3.3.5节流[Po06],第3.3.2节转发延迟[Po06],第3.2.4节IP数据包延迟变化(IPDV)[De02],第1.2节丢失周期[Ko02],第4节

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [Br97]. RFC 2119 defines the use of these keywords to help make the intent of Standards Track documents as clear as possible. While this document uses these keywords, this document is not a Standards Track document.

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[Br97]中的描述进行解释。RFC 2119定义了这些关键字的使用,以帮助使标准跟踪文档的意图尽可能清晰。虽然本文档使用这些关键字,但本文档不是标准跟踪文档。

3. Term Definitions
3. 术语定义
3.1. Convergence Types
3.1. 收敛类型
3.1.1. Route Convergence
3.1.1. 路由收敛

Definition:

定义:

The process of updating all components of the router, including the Routing Information Base (RIB) and Forwarding Information Base (FIB), along with software and hardware tables, with the most recent route change(s) such that forwarding for a route entry is successful on the Next-Best Egress Interface (Section 3.4.4).

更新路由器所有组件的过程,包括路由信息库(RIB)和转发信息库(FIB)以及软件和硬件表,以及最新的路由更改,以便在次优出口接口上成功转发路由条目(第3.4.4节)。

Discussion:

讨论:

In general, IGP convergence does not necessarily result in a change in forwarding. But the test cases in [Po11m] are specified such that the IGP convergence results in a change of egress interface for the measurement data-plane traffic. Due to this property of the test case specifications, Route Convergence can be observed externally by the rerouting of the measurement data-plane traffic to the Next-Best Egress Interface (Section 3.4.4).

一般来说,IGP收敛不一定会导致转发的改变。但是[Po11m]中规定的测试用例使得IGP收敛导致测量数据平面业务的出口接口发生变化。由于测试用例规范的这一特性,通过将测量数据平面流量重新路由到下一个最佳出口接口(第3.4.4节),可以从外部观察到路由收敛。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Next-Best Egress Interface, Full Convergence

次优出口接口,完全收敛

3.1.2. Full Convergence
3.1.2. 完全收敛

Definition:

定义:

Route Convergence for all routes in the Forwarding Information Base (FIB).

转发信息库(FIB)中所有路由的路由聚合。

Discussion:

讨论:

In general, IGP convergence does not necessarily result in a change in forwarding. But the test cases in [Po11m] are specified such that the IGP convergence results in a change of egress interface for the measurement data-plane traffic. Due to this property of the test cases specifications, Full Convergence can be observed externally by the rerouting of the measurement data-plane traffic to the Next-Best Egress Interface (Section 3.4.4).

一般来说,IGP收敛不一定会导致转发的改变。但是[Po11m]中规定的测试用例使得IGP收敛导致测量数据平面业务的出口接口发生变化。由于测试用例规范的这一特性,通过将测量数据平面流量重新路由到下一个最佳出口接口(第3.4.4节),可以在外部观察到完全收敛。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Next-Best Egress Interface, Route Convergence

次优出口接口,路由收敛

3.2. Instants
3.2. 瞬间
3.2.1. Traffic Start Instant
3.2.1. 交通启动瞬间

Definition:

定义:

The time instant the Tester sends out the first data packet to the DUT.

测试仪向DUT发送第一个数据包的瞬间。

Discussion:

讨论:

If using the Loss-Derived Method (Section 3.5.2) or the Route-Specific Loss-Derived Method (Section 3.5.3) to benchmark IGP convergence time, and the applied Convergence Event (Section 3.7.1) does not cause instantaneous traffic loss for all routes at the Convergence Event Instant (Section 3.2.2), then the Tester SHOULD collect a timestamp on the Traffic Start Instant in order to measure the period of time between the Traffic Start Instant and Convergence Event Instant.

如果使用损耗推导法(第3.5.2节)或路线特定损耗推导法(第3.5.3节)来基准IGP收敛时间,且应用的收敛事件(第3.7.1节)在收敛事件瞬间(第3.2.2节)不会导致所有路线的瞬时交通损耗,然后,测试仪应收集流量开始瞬间的时间戳,以测量流量开始瞬间和汇聚事件瞬间之间的时间段。

Measurement Units:

计量单位:

seconds (and fractions), reported with resolution sufficient to distinguish between different instants

秒(和分数),报告分辨率足以区分不同的瞬间

See Also:

另见:

Loss-Derived Method, Route-Specific Loss-Derived Method, Convergence Event, Convergence Event Instant

损失导出法,路由特定损失导出法,收敛事件,收敛事件

3.2.2. Convergence Event Instant
3.2.2. 会聚事件瞬间

Definition:

定义:

The time instant that a Convergence Event (Section 3.7.1) occurs.

收敛事件(第3.7.1节)发生的瞬间时间。

Discussion:

讨论:

If the Convergence Event (Section 3.7.1) causes instantaneous traffic loss on the Preferred Egress Interface (Section 3.4.3), the Convergence Event Instant is observable from the data plane as the instant that no more packets are received on the Preferred Egress Interface.

如果汇聚事件(第3.7.1节)导致首选出口接口(第3.4.3节)上的瞬时流量损失,则可从数据平面观察到汇聚事件瞬间,即首选出口接口上不再接收数据包的瞬间。

The Tester SHOULD collect a timestamp on the Convergence Event Instant if the Convergence Event does not cause instantaneous traffic loss on the Preferred Egress Interface (Section 3.4.3).

如果会聚事件不会导致首选出口接口上的瞬时交通损失,则测试仪应在会聚事件瞬间收集时间戳(第3.4.3节)。

Measurement Units:

计量单位:

seconds (and fractions), reported with resolution sufficient to distinguish between different instants

秒(和分数),报告分辨率足以区分不同的瞬间

See Also:

另见:

Convergence Event, Preferred Egress Interface

会聚事件,首选出口接口

3.2.3. Convergence Recovery Instant
3.2.3. 收敛恢复瞬间

Definition:

定义:

The time instant that Full Convergence (Section 3.1.2) has completed.

完全收敛(第3.1.2节)完成的时间。

Discussion:

讨论:

The Full Convergence completed state MUST be maintained for an interval of duration equal to the Sustained Convergence Validation Time (Section 3.7.5) in order to validate the Convergence Recovery Instant.

为了验证收敛恢复瞬间,必须在等于持续收敛验证时间(第3.7.5节)的时间间隔内保持完全收敛完成状态。

The Convergence Recovery Instant is observable from the data plane as the instant the DUT forwards traffic to all destinations over the Next-Best Egress Interface (Section 3.4.4) without impairments.

当DUT通过下一个最佳出口接口(第3.4.4节)将流量转发到所有目的地时,可以从数据平面观察到收敛恢复瞬间,而不会造成损害。

Measurement Units:

计量单位:

seconds (and fractions), reported with resolution sufficient to distinguish between different instants

秒(和分数),报告分辨率足以区分不同的瞬间

See Also:

另见:

Sustained Convergence Validation Time, Full Convergence, Next-Best Egress Interface

持续收敛验证时间,完全收敛,次优出口界面

3.2.4. First Route Convergence Instant
3.2.4. 第一路收敛瞬间

Definition:

定义:

The time instant the first route entry completes Route Convergence (Section 3.1.1)

第一条路线入口完成路线汇合的瞬间(第3.1.1节)

Discussion:

讨论:

Any route may be the first to complete Route Convergence. The First Route Convergence Instant is observable from the data plane as the instant that the first packet that is not an Impaired Packet (Section 3.8.1) is received from the Next-Best Egress Interface (Section 3.4.4) or, for the test cases with Equal Cost Multi-Path (ECMP) or Parallel Links, the instant that the Forwarding Rate on the Next-Best Egress Interface (Section 3.4.4) starts to increase.

任何路线都可能是第一个完成路线会聚的路线。从数据平面可以观察到第一个路由收敛瞬间,即从下一个最佳出口接口(第3.4.4节)接收到非受损分组的第一个分组(第3.8.1节)的瞬间,或者对于具有等成本多径(ECMP)或并行链路的测试用例,下一个最佳出口接口(第3.4.4节)上的转发速率开始增加的瞬间。

Measurement Units:

计量单位:

seconds (and fractions), reported with resolution sufficient to distinguish between different instants

秒(和分数),报告分辨率足以区分不同的瞬间

See Also:

另见:

Route Convergence, Impaired Packet, Next-Best Egress Interface

路由收敛、受损数据包、次优出口接口

3.3. Transitions
3.3. 过渡
3.3.1. Convergence Event Transition
3.3.1. 会聚事件转换

Definition:

定义:

A time interval following a Convergence Event (Section 3.7.1) in which the Forwarding Rate on the Preferred Egress Interface (Section 3.4.3) gradually reduces to zero.

会聚事件(第3.7.1节)之后的时间间隔,其中首选出口接口(第3.4.3节)上的转发速率逐渐降低至零。

Discussion:

讨论:

The Forwarding Rate during a Convergence Event Transition may or may not decrease linearly.

会聚事件转换期间的转发速率可能会线性降低,也可能不会线性降低。

The Forwarding Rate observed on the DUT egress interface(s) may or may not decrease to zero.

在DUT出口接口上观察到的转发速率可以降低到零,也可以不降低到零。

The Offered Load, the number of routes, and the Packet Sampling Interval (Section 3.7.4) influence the observations of the Convergence Event Transition using the Rate-Derived Method (Section 3.5.1).

提供的负载、路由数量和数据包采样间隔(第3.7.4节)影响使用速率导出方法(第3.5.1节)观察到的收敛事件转换。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Convergence Event, Preferred Egress Interface, Packet Sampling Interval, Rate-Derived Method

收敛事件、首选出口接口、数据包采样间隔、速率导出方法

3.3.2. Convergence Recovery Transition
3.3.2. 收敛恢复过渡

Definition:

定义:

A time interval following the First Route Convergence Instant (Section 3.4.4) in which the Forwarding Rate on the DUT egress interface(s) gradually increases to equal to the Offered Load.

第一个路由会聚瞬间(第3.4.4节)之后的时间间隔,其中DUT出口接口上的转发速率逐渐增加,等于提供的负载。

Discussion:

讨论:

The Forwarding Rate observed during a Convergence Recovery Transition may or may not increase linearly.

在收敛-恢复转换期间观察到的转发速率可以线性增加,也可以不线性增加。

The Offered Load, the number of routes, and the Packet Sampling Interval (Section 3.7.4) influence the observations of the Convergence Recovery Transition using the Rate-Derived Method (Section 3.5.1).

提供的负载、路由数量和数据包采样间隔(第3.7.4节)影响使用速率导出方法(第3.5.1节)观察到的收敛-恢复过渡。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

First Route Convergence Instant, Packet Sampling Interval, Rate-Derived Method

第一路由收敛瞬间,包采样间隔,速率导出法

3.4. Interfaces
3.4. 接口
3.4.1. Local Interface
3.4.1. 本地接口

Definition:

定义:

An interface on the DUT.

DUT上的接口。

Discussion:

讨论:

A failure of a Local Interface indicates that the failure occurred directly on the DUT.

本地接口故障表示故障直接发生在DUT上。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Remote Interface

远程接口

3.4.2. Remote Interface
3.4.2. 远程接口

Definition:

定义:

An interface on a neighboring router that is not directly connected to any interface on the DUT.

相邻路由器上的一种接口,不直接连接到DUT上的任何接口。

Discussion:

讨论:

A failure of a Remote Interface indicates that the failure occurred on a neighbor router's interface that is not directly connected to the DUT.

远程接口故障表示故障发生在未直接连接到DUT的邻居路由器接口上。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Local Interface

本地接口

3.4.3. Preferred Egress Interface
3.4.3. 首选出口接口

Definition:

定义:

The outbound interface from the DUT for traffic routed to the preferred next-hop.

来自DUT的出站接口,用于路由到首选下一跳的流量。

Discussion:

讨论:

The Preferred Egress Interface is the egress interface prior to a Convergence Event (Section 3.7.1).

首选出口接口是会聚事件之前的出口接口(第3.7.1节)。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Convergence Event, Next-Best Egress Interface

汇聚事件,次优出口接口

3.4.4. Next-Best Egress Interface
3.4.4. 次优出口接口

Definition:

定义:

The outbound interface or set of outbound interfaces in an Equal Cost Multipath (ECMP) set or parallel link set of the Device Under Test (DUT) for traffic routed to the second-best next-hop.

被测设备(DUT)的等成本多路径(ECMP)集合或并行链路集合中的出站接口或出站接口集合,用于路由到第二最佳下一跳的流量。

Discussion:

讨论:

The Next-Best Egress Interface becomes the egress interface after a Convergence Event (Section 3.4.4).

下一个最佳出口接口在会聚事件后成为出口接口(第3.4.4节)。

For the test cases in [Po11m] using test topologies with an ECMP set or parallel link set, the term Preferred Egress Interface refers to all members of the link set.

对于[Po11m]中使用带有ECMP集或并行链路集的测试拓扑的测试用例,术语首选出口接口指链路集的所有成员。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Convergence Event, Preferred Egress Interface

会聚事件,首选出口接口

3.5. Benchmarking Methods
3.5. 基准测试方法
3.5.1. Rate-Derived Method
3.5.1. 速率导出法

Definition:

定义:

The method to calculate convergence time benchmarks from observing the Forwarding Rate each Packet Sampling Interval (Section 3.7.4).

通过观察每个数据包采样间隔的转发速率来计算收敛时间基准的方法(第3.7.4节)。

Discussion:

讨论:

Figure 1 shows an example of the Forwarding Rate change in time during convergence as observed when using the Rate-Derived Method.

图1显示了使用速率导出方法时观察到的在收敛期间转发速率随时间变化的示例。

           ^         Traffic                      Convergence
      Fwd  |         Start                        Recovery
      Rate |         Instant                      Instant
           | Offered  ^                             ^
           | Load --> ----------\                   /-----------
           |                     \                 /<--- Convergence
           |                      \     Packet    /      Recovery
           |       Convergence --->\     Loss    /       Transition
           |       Event            \           /
           |       Transition        \---------/ <-- Max Packet Loss
           |
           +--------------------------------------------------------->
                           ^                   ^                 time
                      Convergence         First Route
                      Event Instant       Convergence Instant
        
           ^         Traffic                      Convergence
      Fwd  |         Start                        Recovery
      Rate |         Instant                      Instant
           | Offered  ^                             ^
           | Load --> ----------\                   /-----------
           |                     \                 /<--- Convergence
           |                      \     Packet    /      Recovery
           |       Convergence --->\     Loss    /       Transition
           |       Event            \           /
           |       Transition        \---------/ <-- Max Packet Loss
           |
           +--------------------------------------------------------->
                           ^                   ^                 time
                      Convergence         First Route
                      Event Instant       Convergence Instant
        

Figure 1: Rate-Derived Convergence Graph

图1:速率导出的收敛图

To enable collecting statistics of Out-of-Order Packets per flow (see [Th00], Section 3), the Offered Load SHOULD consist of multiple Streams [Po06], and each Stream SHOULD consist of a single flow . If sending multiple Streams, the measured traffic statistics for all Streams MUST be added together.

为了能够收集每个流的无序数据包的统计信息(参见[Th00],第3节),提供的负载应包括多个流[Po06],每个流应包括一个流。如果发送多个流,则必须将所有流的测量流量统计数据相加。

The destination addresses for the Offered Load MUST be distributed such that all routes or a statistically representative subset of all routes are matched and each of these routes is offered an equal share of the Offered Load. It is RECOMMENDED to send traffic to all routes, but a statistically representative subset of all routes can be used if required.

所提供负载的目的地地址必须进行分配,以便所有路由或所有路由的统计代表子集都匹配,并且这些路由中的每一个路由都提供了所提供负载的相等份额。建议将流量发送到所有路由,但如果需要,可以使用所有路由的统计代表子集。

At least one packet per route for all routes matched in the Offered Load MUST be offered to the DUT within each Packet Sampling Interval. For maximum accuracy, the value of the Packet Sampling Interval SHOULD be as small as possible, but the presence of IP Packet Delay Variation (IPDV) [De02] may require that a larger Packet Sampling Interval be used.

在每个数据包采样间隔内,必须向DUT提供所提供负载中匹配的所有路由的每个路由至少一个数据包。为了获得最大精度,分组采样间隔的值应尽可能小,但是IP分组延迟变化(IPDV)[De02]的存在可能要求使用更大的分组采样间隔。

The Offered Load, IPDV, the number of routes, and the Packet Sampling Interval influence the observations for the Rate-Derived Method. It may be difficult to identify the different convergence time instants in the Rate-Derived Convergence Graph. For example,

提供的负载、IPDV、路由数和数据包采样间隔会影响速率导出方法的观测值。在速率导出的收敛图中,可能很难识别不同的收敛时间点。例如

it is possible that a Convergence Event causes the Forwarding Rate to drop to zero, while this may not be observed in the Forwarding Rate measurements if the Packet Sampling Interval is too large.

收敛事件可能导致转发速率降至零,而如果分组采样间隔过大,则在转发速率测量中可能无法观察到这一情况。

IPDV causes fluctuations in the number of received packets during each Packet Sampling Interval. To account for the presence of IPDV in determining if a convergence instant has been reached, Forwarding Delay SHOULD be observed during each Packet Sampling Interval. The minimum and maximum number of packets expected in a Packet Sampling Interval in presence of IPDV can be calculated with Equation 1.

IPDV在每个数据包采样间隔期间引起接收数据包数量的波动。为了说明IPDV在确定是否已达到收敛时刻时的存在,应在每个数据包采样间隔期间观察转发延迟。在存在IPDV的情况下,在分组采样间隔中预期的分组的最小和最大数目可以用等式1计算。

number of packets expected in a Packet Sampling Interval in presence of IP Packet Delay Variation = expected number of packets without IP Packet Delay Variation +/-( (maxDelay - minDelay) * Offered Load) where minDelay and maxDelay indicate (respectively) the minimum and maximum Forwarding Delay of packets received during the Packet Sampling Interval

在存在IP数据包延迟变化的情况下,数据包采样间隔内预期的数据包数量=不存在IP数据包延迟变化的预期数据包数量+/-((maxDelay-minDelay)*提供的负载),其中minDelay和maxDelay分别表示在数据包采样间隔期间接收的数据包的最小和最大转发延迟

Equation 1

方程式1

To determine if a convergence instant has been reached, the number of packets received in a Packet Sampling Interval is compared with the range of expected number of packets calculated in Equation 1.

为了确定是否已达到收敛时刻,将分组采样间隔中接收的分组数量与等式1中计算的分组预期数量的范围进行比较。

If packets are going over multiple ECMP members and one or more of the members has failed, then the number of received packets during each Packet Sampling Interval may vary, even excluding presence of IPDV. To prevent fluctuation of the number of received packets during each Packet Sampling Interval for this reason, the Packet Sampling Interval duration SHOULD be a whole multiple of the time between two consecutive packets sent to the same destination.

如果数据包经过多个ECMP成员并且一个或多个成员失败,则在每个数据包采样间隔期间接收的数据包的数量可能会变化,甚至排除IPDV的存在。为了防止由于这个原因在每个分组采样间隔期间接收到的分组的数量的波动,分组采样间隔持续时间应该是发送到同一目的地的两个连续分组之间的时间的整数倍。

Metrics measured at the Packet Sampling Interval MUST include Forwarding Rate and Impaired Packet count.

在数据包采样间隔测量的指标必须包括转发速率和受损数据包计数。

To measure convergence time benchmarks for Convergence Events (Section 3.7.1) that do not cause instantaneous traffic loss for all routes at the Convergence Event Instant, the Tester SHOULD collect a timestamp of the Convergence Event Instant (Section 3.2.2), and the Tester SHOULD observe Forwarding Rate separately on the Next-Best Egress Interface.

为了测量会聚事件(第3.7.1节)的会聚时间基准,该会聚事件(第3.7.1节)不会在会聚事件瞬间导致所有路线的瞬时交通损失,测试人员应收集会聚事件瞬间的时间戳(第3.2.2节),测试人员应在次优出口界面上单独观察转发速率。

Since the Rate-Derived Method does not distinguish between individual traffic destinations, it SHOULD NOT be used for any route specific measurements. Therefore, the Rate-Derived Method SHOULD NOT be used to benchmark Route Loss of Connectivity Period (Section 3.6.5).

由于速率导出方法不区分各个交通目的地,因此不应将其用于任何特定于路线的测量。因此,速率衍生方法不应用于基准线路连通性损失周期(第3.6.5节)。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Packet Sampling Interval, Convergence Event, Convergence Event Instant, Next-Best Egress Interface, Route Loss of Connectivity Period

数据包采样间隔、收敛事件、收敛事件瞬间、次优出口接口、路由连接丢失周期

3.5.2. Loss-Derived Method
3.5.2. 损失导出法

Definition:

定义:

The method to calculate the Loss-Derived Convergence Time (Section 3.6.4) and Loss-Derived Loss of Connectivity Period (Section 3.6.6) benchmarks from the amount of Impaired Packets (Section 3.8.1).

根据受损数据包的数量(第3.8.1节)计算损失衍生收敛时间(第3.6.4节)和损失衍生连接损失周期(第3.6.6节)基准的方法。

Discussion:

讨论:

To enable collecting statistics of Out-of-Order Packets per flow (see [Th00], Section 3), the Offered Load SHOULD consist of multiple Streams [Po06], and each Stream SHOULD consist of a single flow . If sending multiple Streams, the measured traffic statistics for all Streams MUST be added together.

为了能够收集每个流的无序数据包的统计信息(参见[Th00],第3节),提供的负载应包括多个流[Po06],每个流应包括一个流。如果发送多个流,则必须将所有流的测量流量统计数据相加。

The destination addresses for the Offered Load MUST be distributed such that all routes or a statistically representative subset of all routes are matched and each of these routes is offered an equal share of the Offered Load. It is RECOMMENDED to send traffic to all routes, but a statistically representative subset of all routes can be used if required.

所提供负载的目的地地址必须进行分配,以便所有路由或所有路由的统计代表子集都匹配,并且这些路由中的每一个路由都提供了所提供负载的相等份额。建议将流量发送到所有路由,但如果需要,可以使用所有路由的统计代表子集。

Loss-Derived Method SHOULD always be combined with the Rate-Derived Method in order to observe Full Convergence completion. The total amount of Convergence Packet Loss is collected after Full Convergence completion.

损失导出法应始终与速率导出法相结合,以观察完全收敛。在完全收敛完成后收集收敛数据包丢失的总量。

To measure convergence time and loss of connectivity benchmarks for Convergence Events that cause instantaneous traffic loss for all routes at the Convergence Event Instant, the Tester SHOULD observe the Impaired Packet count on all DUT egress interfaces (see Connectivity Packet Loss (Section 3.7.3)).

为了测量会聚事件的会聚时间和连接损失基准,该会聚事件在会聚事件瞬间导致所有路由的瞬时流量损失,测试仪应观察所有DUT出口接口上受损的数据包计数(见连接数据包损失(第3.7.3节))。

To measure convergence time benchmarks for Convergence Events that do not cause instantaneous traffic loss for all routes at the Convergence Event Instant, the Tester SHOULD collect timestamps of the Start Traffic Instant and of the Convergence Event Instant, and the Tester SHOULD observe Impaired Packet count separately on the Next-Best Egress Interface (see Convergence Packet Loss (Section 3.7.2)).

为了测量在汇聚事件瞬间不会导致所有路线瞬时流量损失的汇聚事件的汇聚时间基准,测试人员应收集开始流量瞬间和汇聚事件瞬间的时间戳,测试人员应在下一个最佳出口接口上单独观察受损数据包计数(见汇聚数据包丢失(第3.7.2节))。

Since Loss-Derived Method does not distinguish between traffic destinations and the Impaired Packet statistics are only collected after Full Convergence completion, this method can only be used to measure average values over all routes. For these reasons, Loss-Derived Method can only be used to benchmark Loss-Derived Convergence Time (Section 3.6.4) and Loss-Derived Loss of Connectivity Period (Section 3.6.6).

由于丢失衍生方法不区分业务目的地,并且只有在完全收敛完成后才收集受损数据包统计信息,因此该方法只能用于测量所有路由的平均值。由于这些原因,损耗推导方法只能用于基准损耗推导的收敛时间(第3.6.4节)和损耗推导的连通性损耗周期(第3.6.6节)。

Note that the Loss-Derived Method measures an average over all routes, including the routes that may not be impacted by the Convergence Event, such as routes via non-impacted members of ECMP or parallel links.

请注意,损失衍生方法测量所有路由的平均值,包括可能不受收敛事件影响的路由,例如通过ECMP的非受影响成员或并行链路的路由。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Loss-Derived Convergence Time, Loss-Derived Loss of Connectivity Period, Connectivity Packet Loss, Convergence Packet Loss

损失衍生的收敛时间、损失衍生的连接丢失周期、连接数据包丢失、收敛数据包丢失

3.5.3. Route-Specific Loss-Derived Method
3.5.3. 路由比损耗导出法

Definition:

定义:

The method to calculate the Route-Specific Convergence Time (Section 3.6.3) benchmark from the amount of Impaired Packets (Section 3.8.1) during convergence for a specific route entry.

根据特定路由入口聚合期间受损数据包的数量(第3.8.1节),计算路由特定聚合时间(第3.6.3节)基准的方法。

Discussion:

讨论:

To benchmark Route-Specific Convergence Time, the Tester provides an Offered Load that consists of multiple Streams [Po06]. Each Stream has a single destination address matching a different route entry, for all routes or a statistically representative subset of all routes. Each Stream SHOULD consist of a single flow (see [Th00], Section 3). Convergence Packet Loss is measured for each Stream separately.

为了对特定于路由的收敛时间进行基准测试,测试仪提供了一个由多个流组成的负载[Po06]。对于所有路由或所有路由的统计代表子集,每个流都有一个与不同路由条目匹配的目的地地址。每条流应包含一条流(见[Th00],第3节)。对每个流分别测量收敛分组丢失。

Route-Specific Loss-Derived Method SHOULD always be combined with the Rate-Derived Method in order to observe Full Convergence completion. The total amount of Convergence Packet Loss (Section 3.7.2) for each Stream is collected after Full Convergence completion.

路线特定损失导出方法应始终与速率导出方法相结合,以观察完全收敛。在完全聚合完成后,收集每个流的聚合数据包丢失总量(第3.7.2节)。

Route-Specific Loss-Derived Method is the RECOMMENDED method to measure convergence time benchmarks.

路由特定损耗导出法是衡量收敛时间基准的推荐方法。

To measure convergence time and loss of connectivity benchmarks for Convergence Events that cause instantaneous traffic loss for all routes at the Convergence Event Instant, the Tester SHOULD observe Impaired Packet count on all DUT egress interfaces (see Connectivity Packet Loss (Section 3.7.3)).

为了测量会聚事件的会聚时间和连接损失基准,该会聚事件会在会聚事件瞬间导致所有路由的瞬时流量损失,测试仪应观察所有DUT出口接口上受损的数据包计数(见连接数据包损失(第3.7.3节))。

To measure convergence time benchmarks for Convergence Events that do not cause instantaneous traffic loss for all routes at the Convergence Event Instant, the Tester SHOULD collect timestamps of the Start Traffic Instant and of the Convergence Event Instant, and the Tester SHOULD observe packet loss separately on the Next-Best Egress Interface (see Convergence Packet Loss (Section 3.7.2)).

为了测量在汇聚事件瞬间不会导致所有路由瞬时流量丢失的汇聚事件的汇聚时间基准,测试仪应收集开始流量瞬间和汇聚事件瞬间的时间戳,并且测试仪应在次优出口接口上单独观察包丢失(参见汇聚数据包丢失(第3.7.2节))。

Since Route-Specific Loss-Derived Method uses traffic streams to individual routes, it observes Impaired Packet count as it would be experienced by a network user. For this reason, Route-Specific Loss-Derived Method is RECOMMENDED to measure Route-Specific Convergence Time benchmarks and Route Loss of Connectivity Period benchmarks.

由于特定于路由的丢失衍生方法使用到各个路由的业务流,所以它观察网络用户将经历的受损数据包计数。因此,建议使用特定于路由的损耗导出方法来测量特定于路由的收敛时间基准和连接周期基准的路由损耗。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Route-Specific Convergence Time, Route Loss of Connectivity Period, Connectivity Packet Loss, Convergence Packet Loss

特定于路由的收敛时间、连接周期的路由丢失、连接数据包丢失、收敛数据包丢失

3.6. Benchmarks
3.6. 基准
3.6.1. Full Convergence Time
3.6.1. 完全收敛时间

Definition:

定义:

The time duration of the period between the Convergence Event Instant and the Convergence Recovery Instant as observed using the Rate-Derived Method.

使用速率导出方法观察到的收敛事件瞬间和收敛恢复瞬间之间的时间持续时间。

Discussion:

讨论:

Using the Rate-Derived Method, Full Convergence Time can be calculated as the time difference between the Convergence Event Instant and the Convergence Recovery Instant, as shown in Equation 2.

使用速率导出法,完全收敛时间可以计算为收敛事件瞬间和收敛恢复瞬间之间的时间差,如等式2所示。

Full Convergence Time = Convergence Recovery Instant - Convergence Event Instant

完全收敛时间=收敛恢复瞬间-收敛事件瞬间

Equation 2

方程式2

The Convergence Event Instant can be derived from the Forwarding Rate observation or from a timestamp collected by the Tester.

收敛事件瞬间可以从转发速率观察或测试仪收集的时间戳中得出。

For the test cases described in [Po11m], it is expected that Full Convergence Time equals the maximum Route-Specific Convergence Time when benchmarking all routes in the FIB using the Route-Specific Loss-Derived Method.

对于[Po11m]中描述的测试用例,当使用路由特定损耗衍生方法对FIB中的所有路由进行基准测试时,预计完全收敛时间等于最大路由特定收敛时间。

It is not possible to measure Full Convergence Time using the Loss-Derived Method.

使用损失导出方法无法测量完全收敛时间。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Full Convergence, Rate-Derived Method, Route-Specific Loss-Derived Method, Convergence Event Instant, Convergence Recovery Instant

完全收敛、速率导出法、路由特定损失导出法、收敛事件瞬间、收敛恢复瞬间

3.6.2. First Route Convergence Time
3.6.2. 第一路径收敛时间

Definition:

定义:

The duration of the period between the Convergence Event Instant and the First Route Convergence Instant as observed using the Rate-Derived Method.

使用速率导出方法观察到的收敛事件瞬间和第一条路线收敛瞬间之间的持续时间。

Discussion:

讨论:

Using the Rate-Derived Method, First Route Convergence Time can be calculated as the time difference between the Convergence Event Instant and the First Route Convergence Instant, as shown with Equation 3.

使用速率导出法,第一路径收敛时间可以计算为收敛事件瞬间和第一路径收敛瞬间之间的时间差,如等式3所示。

First Route Convergence Time = First Route Convergence Instant - Convergence Event Instant

第一路收敛时间=第一路收敛瞬间-收敛事件瞬间

Equation 3

方程式3

The Convergence Event Instant can be derived from the Forwarding Rate observation or from a timestamp collected by the Tester.

收敛事件瞬间可以从转发速率观察或测试仪收集的时间戳中得出。

For the test cases described in [Po11m], it is expected that First Route Convergence Time equals the minimum Route-Specific Convergence Time when benchmarking all routes in the FIB using the Route-Specific Loss-Derived Method.

对于[Po11m]中描述的测试用例,当使用路由特定损耗衍生方法对FIB中的所有路由进行基准测试时,预计第一路由收敛时间等于最小路由特定收敛时间。

It is not possible to measure First Route Convergence Time using the Loss-Derived Method.

不可能使用损失导出方法测量第一条路线的收敛时间。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Rate-Derived Method, Route-Specific Loss-Derived Method, Convergence Event Instant, First Route Convergence Instant

速率导出法,路由特定损耗导出法,收敛事件瞬间,第一路由收敛瞬间

3.6.3. Route-Specific Convergence Time
3.6.3. 特定路线收敛时间

Definition:

定义:

The amount of time it takes for Route Convergence to be completed for a specific route, as calculated from the amount of Impaired Packets (Section 3.8.1) during convergence for a single route entry.

特定路由完成路由收敛所需的时间量,根据单一路由入口收敛期间受损数据包的数量(第3.8.1节)计算得出。

Discussion:

讨论:

Route-Specific Convergence Time can only be measured using the Route-Specific Loss-Derived Method.

特定于路线的收敛时间只能使用特定于路线的损耗推导方法进行测量。

If the applied Convergence Event causes instantaneous traffic loss for all routes at the Convergence Event Instant, Connectivity Packet Loss should be observed. Connectivity Packet Loss is the combined Impaired Packet count observed on Preferred Egress Interface and Next-Best Egress Interface. When benchmarking Route-Specific Convergence Time, Connectivity Packet Loss is measured, and Equation 4 is applied for each measured route. The calculation is equal to Equation 8 in Section 3.6.5.

如果应用的聚合事件在聚合事件瞬间导致所有路由的瞬时流量损失,则应观察连接数据包丢失。连通性数据包丢失是在首选出口接口和次优出口接口上观察到的组合受损数据包计数。当基准测试特定于路由的收敛时间时,测量连接性分组丢失,并对每个测量的路由应用等式4。计算结果等于第3.6.5节中的方程式8。

Route-Specific Convergence Time = Connectivity Packet Loss for specific route / Offered Load per route

路由特定聚合时间=特定路由的连接数据包丢失/每条路由提供的负载

Equation 4

方程式4

If the applied Convergence Event does not cause instantaneous traffic loss for all routes at the Convergence Event Instant, then the Tester SHOULD collect timestamps of the Traffic Start Instant and of the Convergence Event Instant, and the Tester SHOULD observe Convergence Packet Loss separately on the Next-Best Egress Interface. When benchmarking Route-Specific Convergence Time, Convergence Packet Loss is measured, and Equation 5 is applied for each measured route.

如果应用的汇聚事件在汇聚事件瞬间不会导致所有路由的瞬时流量丢失,则测试仪应收集流量开始瞬间和汇聚事件瞬间的时间戳,并且测试仪应在次优出口接口上单独观察汇聚包丢失。当基准测试特定于路由的收敛时间时,测量收敛分组丢失,并对每个测量的路由应用等式5。

Route-Specific Convergence Time = Convergence Packet Loss for specific route / Offered Load per route - (Convergence Event Instant - Traffic Start Instant)

路由特定汇聚时间=特定路由的汇聚数据包丢失/每条路由的提供负载-(汇聚事件瞬间-流量开始瞬间)

Equation 5

方程式5

The Route-Specific Convergence Time benchmarks enable minimum, maximum, average, and median convergence time measurements to be reported by comparing the results for the different route entries. It also enables benchmarking of convergence time when configuring a priority value for the route entry or entries. Since multiple Route-Specific Convergence Times can be measured, it is possible to have an array of results. The format for reporting Route-Specific Convergence Time is provided in [Po11m].

特定于路线的收敛时间基准通过比较不同路线入口的结果来报告最小、最大、平均和中值收敛时间测量值。它还可以在为一个或多个路由条目配置优先级值时,对聚合时间进行基准测试。由于可以测量多个特定于路由的收敛时间,因此可以得到一系列结果。[Po11m]中提供了报告特定路线收敛时间的格式。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Route-Specific Loss-Derived Method, Convergence Event, Convergence Event Instant, Convergence Packet Loss, Connectivity Packet Loss, Route Convergence

路由特定丢失导出方法,收敛事件,收敛事件瞬间,收敛丢包,连通丢包,路由收敛

3.6.4. Loss-Derived Convergence Time
3.6.4. 损失导出收敛时间

Definition:

定义:

The average Route Convergence time for all routes in the Forwarding Information Base (FIB), as calculated from the amount of Impaired Packets (Section 3.8.1) during convergence.

转发信息库(FIB)中所有路由的平均路由聚合时间,根据聚合期间受损数据包的数量(第3.8.1节)计算得出。

Discussion:

讨论:

Loss-Derived Convergence Time is measured using the Loss-Derived Method.

使用损耗导出方法测量损耗导出的收敛时间。

If the applied Convergence Event causes instantaneous traffic loss for all routes at the Convergence Event Instant, Connectivity Packet Loss (Section 3.7.3) should be observed. Connectivity Packet Loss is the combined Impaired Packet count observed on Preferred Egress Interface and Next-Best Egress Interface. When benchmarking Loss-Derived Convergence Time, Connectivity Packet Loss is measured, and Equation 6 is applied.

如果应用的汇聚事件在汇聚事件瞬间导致所有路由的瞬时流量损失,则应遵守连接数据包损失(第3.7.3节)。连通性数据包丢失是在首选出口接口和次优出口接口上观察到的组合受损数据包计数。当基准测试损失导出的收敛时间时,测量连通性分组损失,并应用等式6。

Loss-Derived Convergence Time = Connectivity Packet Loss / Offered Load

丢失衍生收敛时间=连接数据包丢失/提供的负载

Equation 6

方程式6

If the applied Convergence Event does not cause instantaneous traffic loss for all routes at the Convergence Event Instant, then the Tester SHOULD collect timestamps of the Start Traffic Instant and of the Convergence Event Instant, and the Tester SHOULD observe Convergence Packet Loss (Section 3.7.2) separately on the Next-Best Egress Interface. When benchmarking Loss-Derived Convergence Time, Convergence Packet Loss is measured and Equation 7 is applied.

如果应用的汇聚事件在汇聚事件瞬间不会导致所有路由的瞬时流量损失,则测试仪应收集开始流量瞬间和汇聚事件瞬间的时间戳,并且测试仪应在次优出口接口上分别观察汇聚包损失(第3.7.2节)。当基准测试损失导出的收敛时间时,测量收敛分组损失并应用等式7。

Loss-Derived Convergence Time = Convergence Packet Loss / Offered Load - (Convergence Event Instant - Traffic Start Instant)

损失衍生收敛时间=收敛包丢失/提供负载-(收敛事件瞬间-流量开始瞬间)

Equation 7

方程式7

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Convergence Packet Loss, Connectivity Packet Loss, Route Convergence, Loss-Derived Method

收敛丢包,连通丢包,路由收敛,丢包导出方法

3.6.5. Route Loss of Connectivity Period
3.6.5. 路由连接丢失周期

Definition:

定义:

The time duration of packet impairments for a specific route entry following a Convergence Event until Full Convergence completion, as observed using the Route-Specific Loss-Derived Method.

在收敛事件之后,特定路由条目的数据包损伤持续时间,直至完全收敛完成,如使用路由特定丢失导出方法观察到的。

Discussion:

讨论:

In general, the Route Loss of Connectivity Period is not equal to the Route-Specific Convergence Time. If the DUT continues to forward traffic to the Preferred Egress Interface after the Convergence Event is applied, then the Route Loss of Connectivity Period will be smaller than the Route-Specific Convergence Time. This is also specifically the case after reversing a failure event.

一般来说,路由连通性损失周期不等于路由特定的收敛时间。如果在应用会聚事件后DUT继续将业务转发到优选出口接口,则路由连接丢失周期将小于路由特定会聚时间。在逆转故障事件后,情况也是如此。

The Route Loss of Connectivity Period may be equal to the Route-Specific Convergence Time if, as a characteristic of the Convergence Event, traffic for all routes starts dropping instantaneously on the Convergence Event Instant. See discussion in [Po11m].

如果作为会聚事件的特征,所有路由的流量在会聚事件瞬间开始下降,则路由连接丢失周期可等于路由特定的会聚时间。见[Po11m]中的讨论。

For the test cases described in [Po11m], the Route Loss of Connectivity Period is expected to be a single Loss Period [Ko02].

对于[Po11m]中描述的测试用例,连接的路由丢失周期预计为单个丢失周期[Ko02]。

When benchmarking the Route Loss of Connectivity Period, Connectivity Packet Loss is measured for each route, and Equation 8 is applied for each measured route entry. The calculation is equal to Equation 4 in Section 3.6.3.

当基准测试连接期间的路由丢失时,测量每个路由的连接分组丢失,并对每个测量的路由条目应用等式8。计算结果等于第3.6.3节中的方程式4。

Route Loss of Connectivity Period = Connectivity Packet Loss for specific route / Offered Load per route

Route Loss of Connectivity Period=特定路由的连接数据包丢失/每条路由提供的负载

Equation 8

方程式8

Route Loss of Connectivity Period SHOULD be measured using Route-Specific Loss-Derived Method.

应使用特定于路由的损耗导出方法测量连接周期的路由损耗。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Route-Specific Convergence Time, Route-Specific Loss-Derived Method, Connectivity Packet Loss

路由特定收敛时间、路由特定损耗导出方法、连通性丢包

3.6.6. Loss-Derived Loss of Connectivity Period
3.6.6. 损失衍生的连通性损失周期

Definition:

定义:

The average time duration of packet impairments for all routes following a Convergence Event until Full Convergence completion, as observed using the Loss-Derived Method.

收敛事件发生后所有路由到完全收敛完成的数据包损坏的平均持续时间,如使用损耗导出方法观察到的。

Discussion:

讨论:

In general, the Loss-Derived Loss of Connectivity Period is not equal to the Loss-Derived Convergence Time. If the DUT continues to forward traffic to the Preferred Egress Interface after the Convergence Event is applied, then the Loss-Derived Loss of Connectivity Period will be smaller than the Loss-Derived Convergence Time. This is also specifically the case after reversing a failure event.

一般来说,由损失导出的连通性损失周期不等于由损失导出的收敛时间。如果在应用会聚事件之后DUT继续将业务转发到优选出口接口,则由损失导出的连接丢失周期将小于由损失导出的会聚时间。在逆转故障事件后,情况也是如此。

The Loss-Derived Loss of Connectivity Period may be equal to the Loss-Derived Convergence Time if, as a characteristic of the Convergence Event, traffic for all routes starts dropping instantaneously on the Convergence Event Instant. See discussion in [Po11m].

如果作为会聚事件的特征,所有路由的流量在会聚事件瞬间开始下降,则由损失衍生的连接损失周期可能等于由损失衍生的会聚时间。见[Po11m]中的讨论。

For the test cases described in [Po11m], each route's Route Loss of Connectivity Period is expected to be a single Loss Period [Ko02].

对于[Po11m]中描述的测试用例,每条路由的连接丢失周期预计为单个丢失周期[Ko02]。

When benchmarking the Loss-Derived Loss of Connectivity Period, Connectivity Packet Loss is measured for all routes, and Equation 9 is applied. The calculation is equal to Equation 6 in Section 3.6.4.

当基准测试损失衍生的连接丢失周期时,测量所有路由的连接数据包丢失,并应用等式9。计算结果等于第3.6.4节中的方程式6。

Loss-Derived Loss of Connectivity Period = Connectivity Packet Loss for all routes / Offered Load

丢失衍生的连接丢失周期=所有路由/提供负载的连接数据包丢失

Equation 9

等式9

The Loss-Derived Loss of Connectivity Period SHOULD be measured using the Loss-Derived Method.

应使用损耗衍生法测量由损耗衍生的连接损耗周期。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Loss-Derived Convergence Time, Loss-Derived Method, Connectivity Packet Loss

损失导出收敛时间,损失导出方法,连通性丢包

3.7. Measurement Terms
3.7. 测量术语
3.7.1. Convergence Event
3.7.1. 会聚事件

Definition:

定义:

The occurrence of an event in the network that will result in a change in the egress interface of the DUT for routed packets.

网络中发生的事件,将导致路由数据包的DUT出口接口发生变化。

Discussion:

讨论:

All test cases in [Po11m] are defined such that a Convergence Event results in a change of egress interface of the DUT. Local or remote triggers that cause a route calculation that does not result in a change in forwarding are not considered.

[Po11m]中的所有测试用例的定义应确保收敛事件导致DUT出口接口的变化。不考虑导致路由计算而不会导致转发更改的本地或远程触发器。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Convergence Event Instant

会聚事件瞬间

3.7.2. Convergence Packet Loss
3.7.2. 收敛丢包

Definition:

定义:

The number of Impaired Packets (Section 3.8.1) as observed on the Next-Best Egress Interface of the DUT during convergence.

收敛期间在DUT的次优出口接口上观察到的受损数据包数量(第3.8.1节)。

Discussion:

讨论:

An Impaired Packet is considered as a lost packet.

受损的数据包被视为丢失的数据包。

Measurement Units:

计量单位:

number of packets

数据包数

See Also:

另见:

Connectivity Packet Loss

连接数据包丢失

3.7.3. Connectivity Packet Loss
3.7.3. 连接数据包丢失

Definition:

定义:

The number of Impaired Packets observed on all DUT egress interfaces during convergence.

聚合期间在所有DUT出口接口上观察到的受损数据包的数量。

Discussion:

讨论:

An Impaired Packet is considered as a lost packet. Connectivity Packet Loss is equal to Convergence Packet Loss if the Convergence Event causes instantaneous traffic loss for all egress interfaces of the DUT except for the Next-Best Egress Interface.

受损的数据包被视为丢失的数据包。如果收敛事件导致DUT的所有出口接口(下一个最佳出口接口除外)的瞬时通信量丢失,则连通性分组丢失等于收敛分组丢失。

Measurement Units:

计量单位:

number of packets

数据包数

See Also:

另见:

Convergence Packet Loss

收敛丢包

3.7.4. Packet Sampling Interval
3.7.4. 数据包采样间隔

Definition:

定义:

The interval at which the Tester (test equipment) polls to make measurements for arriving packets.

测试仪(测试设备)轮询以对到达的数据包进行测量的间隔。

Discussion:

讨论:

At least one packet per route for all routes matched in the Offered Load MUST be offered to the DUT within the Packet Sampling Interval. Metrics measured at the Packet Sampling Interval MUST include Forwarding Rate and received packets.

在数据包采样间隔内,必须向DUT提供所提供负载中匹配的所有路由的每个路由至少一个数据包。在数据包采样间隔测量的指标必须包括转发速率和接收的数据包。

Packet Sampling Interval can influence the convergence graph as observed with the Rate-Derived Method. This is particularly true when implementations complete Full Convergence in less time than the Packet Sampling Interval. The Convergence Event Instant and

数据包采样间隔会影响收敛图,正如用速率导出方法观察到的那样。当实现在比数据包采样间隔更短的时间内完成完全收敛时,尤其如此。会聚事件

First Route Convergence Instant may not be easily identifiable, and the Rate-Derived Method may produce a larger than actual convergence time.

第一条路径的收敛时刻可能不容易识别,并且速率导出方法可能产生比实际收敛时间更大的收敛时间。

Using a small Packet Sampling Interval in the presence of IPDV [De02] may cause fluctuations of the Forwarding Rate observation and can prevent correct observation of the different convergence time instants.

在存在IPDV[De02]的情况下使用小的分组采样间隔可能导致转发速率观测的波动,并且可能阻止对不同收敛时间瞬间的正确观测。

The value of the Packet Sampling Interval only contributes to the measurement accuracy of the Rate-Derived Method. For maximum accuracy, the value for the Packet Sampling Interval SHOULD be as small as possible, but the presence of IPDV may enforce using a larger Packet Sampling Interval.

数据包采样间隔的值仅对速率导出方法的测量精度有贡献。为了获得最大精度,数据包采样间隔的值应尽可能小,但IPDV的存在可能会强制使用更大的数据包采样间隔。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Rate-Derived Method

速率导出法

3.7.5. Sustained Convergence Validation Time
3.7.5. 持续收敛验证时间

Definition:

定义:

The amount of time for which the completion of Full Convergence is maintained without additional Impaired Packets being observed.

在没有观察到其他受损数据包的情况下,保持完全收敛完成的时间量。

Discussion:

讨论:

The purpose of the Sustained Convergence Validation Time is to produce convergence benchmarks protected against fluctuation in Forwarding Rate after the completion of Full Convergence is observed. The RECOMMENDED Sustained Convergence Validation Time to be used is the time to send 5 consecutive packets to each destination with a minimum of 5 seconds. The Benchmarking Methodology Working Group (BMWG) selected 5 seconds based upon [Br99], which recommends waiting 2 seconds for residual frames to arrive (this is the Forwarding Delay Threshold for the last packet sent) and 5 seconds for DUT restabilization.

持续收敛验证时间的目的是在观察到完全收敛完成后,生成防止转发速率波动的收敛基准。建议使用的持续收敛验证时间是以至少5秒的时间向每个目的地发送5个连续数据包的时间。基准测试方法工作组(BMWG)根据[Br99]选择5秒,建议等待2秒剩余帧到达(这是最后发送的数据包的转发延迟阈值),等待5秒DUT重新稳定。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Full Convergence, Convergence Recovery Instant

完全收敛,收敛恢复瞬间

3.7.6. Forwarding Delay Threshold
3.7.6. 转发延迟阈值

Definition:

定义:

The maximum waiting time threshold used to distinguish between packets with very long delay and lost packets that will never arrive.

用于区分延迟很长的数据包和永远不会到达的丢失数据包的最大等待时间阈值。

Discussion:

讨论:

Applying a Forwarding Delay Threshold allows packets with a too large Forwarding Delay to be considered lost, as is required for some applications (e.g. voice, video, etc.). The Forwarding Delay Threshold is a parameter of the methodology, and it MUST be reported. [Br99] recommends waiting 2 seconds for residual frames to arrive.

应用转发延迟阈值可使转发延迟过大的数据包被视为丢失,这是某些应用(如语音、视频等)所需的。转发延迟阈值是该方法的一个参数,必须报告。[Br99]建议等待2秒钟,等待剩余帧到达。

Measurement Units:

计量单位:

seconds (and fractions)

秒(和分数)

See Also:

另见:

Convergence Packet Loss, Connectivity Packet Loss

聚合数据包丢失、连接数据包丢失

3.8. Miscellaneous Terms
3.8. 杂项条款
3.8.1. Impaired Packet
3.8.1. 受损数据包

Definition:

定义:

A packet that experienced at least one of the following impairments: loss, excessive Forwarding Delay, corruption, duplication, reordering.

一种数据包,它至少有以下一种损坏:丢失、过度转发延迟、损坏、重复、重新排序。

Discussion:

讨论:

A lost packet, a packet with a Forwarding Delay exceeding the Forwarding Delay Threshold, a corrupted packet, a Duplicate Packet [Po06], and an Out-of-Order Packet [Po06] are Impaired Packets.

丢失的分组、转发延迟超过转发延迟阈值的分组、损坏的分组、重复分组[Po06]和无序分组[Po06]都是受损分组。

Packet ordering is observed for each individual flow (see [Th00], Section 3) of the Offered Load.

对所提供负载的每个单独流(参见[Th00],第3节)观察数据包顺序。

Measurement Units:

计量单位:

N/A

不适用

See Also:

另见:

Forwarding Delay Threshold

转发延迟阈值

4. Security Considerations
4. 安全考虑

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/SUT.

此外,基准测试是在“黑盒”的基础上进行的,仅依赖于DUT/SUT外部可观察到的测量。

Special capabilities SHOULD NOT exist in the DUT/SUT specifically for benchmarking purposes. Any implications for network security arising from the DUT/SUT SHOULD be identical in the lab and in production networks.

DUT/SUT中不应存在专门用于基准测试的特殊能力。DUT/SUT对网络安全的任何影响应在实验室和生产网络中相同。

5. Acknowledgements
5. 致谢

Thanks to Sue Hares, Al Morton, Kevin Dubray, Ron Bonica, David Ward, Peter De Vriendt, Anuj Dewagan, Adrian Farrel, Stewart Bryant, Francis Dupont, and the Benchmarking Methodology Working Group for their contributions to this work.

感谢Sue Hares、Al Morton、Kevin Dubrey、Ron Bonica、David Ward、Peter De Vriendt、Anuj Dewagan、Adrian Farrel、Stewart Bryant、Francis Dupont和基准方法工作组对本工作的贡献。

6. Normative References
6. 规范性引用文件

[Br91] Bradner, S., "Benchmarking terminology for network interconnection devices", RFC 1242, July 1991.

[Br91]Bradner,S.,“网络互连设备的基准术语”,RFC 1242,1991年7月。

[Br97] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[Br97]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,1997年3月。

[Br99] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, March 1999.

[Br99]Bradner,S.和J.McQuaid,“网络互连设备的基准测试方法”,RFC 2544,1999年3月。

[Ca90] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and dual environments", RFC 1195, December 1990.

[Ca90]Callon,R.,“OSI IS-IS在TCP/IP和双环境中路由的使用”,RFC 1195,1990年12月。

[Co08] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, July 2008.

[Co08]Coltun,R.,Ferguson,D.,Moy,J.,和A.Lindem,“IPv6的OSPF”,RFC 53402008年7月。

[De02] Demichelis, C. and P. Chimento, "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)", RFC 3393, November 2002.

[De02]Demichelis,C.和P.Chimento,“IP性能度量的IP数据包延迟变化度量(IPPM)”,RFC 3393,2002年11月。

[Ho08] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October 2008.

[Ho08]Hopps,C.,“使用IS-IS路由IPv6”,RFC 5308,2008年10月。

[Ko02] Koodli, R. and R. Ravikanth, "One-way Loss Pattern Sample Metrics", RFC 3357, August 2002.

[Ko02]Koodli,R.和R.Ravikanth,“单向损失模式样本度量”,RFC 3357,2002年8月。

[Ma98] Mandeville, R., "Benchmarking Terminology for LAN Switching Devices", RFC 2285, February 1998.

[Ma98]Mandeville,R.,“局域网交换设备的基准术语”,RFC 2285,1998年2月。

[Mo98] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.

[Mo98]Moy,J.,“OSPF版本2”,STD 54,RFC 23281998年4月。

[Po06] Poretsky, S., Perser, J., Erramilli, S., and S. Khurana, "Terminology for Benchmarking Network-layer Traffic Control Mechanisms", RFC 4689, October 2006.

[Po06]Poretsky,S.,Perser,J.,Erramilli,S.,和S.Khurana,“基准网络层流量控制机制的术语”,RFC 4689,2006年10月。

[Po11m] Poretsky, S., Imhoff, B., and K. Michielsen, "Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence", RFC 6413, November 2011.

[Po11m]Poretsky,S.,Imhoff,B.,和K.Michielsen,“链路状态IGP数据平面路由收敛的基准测试方法”,RFC 6413,2011年11月。

[Th00] Thaler, D. and C. Hopps, "Multipath Issues in Unicast and Multicast Next-Hop Selection", RFC 2991, November 2000.

[Th00]Thaler,D.和C.Hopps,“单播和多播下一跳选择中的多路径问题”,RFC 2991,2000年11月。

Authors' Addresses

作者地址

Scott Poretsky Allot Communications 300 TradeCenter Woburn, MA 01801 USA

Scott Poretsky Allot Communications 300美国马萨诸塞州沃本贸易中心01801

   Phone: + 1 508 309 2179
   EMail: sporetsky@allot.com
        
   Phone: + 1 508 309 2179
   EMail: sporetsky@allot.com
        

Brent Imhoff F5 Networks 401 Elliott Avenue West Seattle, WA 98119 USA

布伦特·伊姆霍夫F5网络美国华盛顿州西雅图市埃利奥特大道西401号,邮编98119

   Phone: + 1 314 378 2571
   EMail: bimhoff@planetspork.com
        
   Phone: + 1 314 378 2571
   EMail: bimhoff@planetspork.com
        

Kris Michielsen Cisco Systems 6A De Kleetlaan Diegem, BRABANT 1831 Belgium

Kris Michielsen Cisco Systems 6A De Kleetlaan Diegem,比利时布拉班特1831

   EMail: kmichiel@cisco.com
        
   EMail: kmichiel@cisco.com