Network Working Group K. Chan
Request for Comments: 3317 Nortel Networks
Category: Informational R. Sahita
S. Hahn
Intel
K. McCloghrie
Cisco Systems
March 2003
Network Working Group K. Chan
Request for Comments: 3317 Nortel Networks
Category: Informational R. Sahita
S. Hahn
Intel
K. McCloghrie
Cisco Systems
March 2003
Differentiated Services Quality of Service Policy Information Base
差异化服务服务质量政策信息库
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This document describes a Policy Information Base (PIB) for a device implementing the Differentiated Services Architecture. The provisioning classes defined here provide policy control over resources implementing the Differentiated Services Architecture. These provisioning classes can be used with other none Differentiated Services provisioning classes (defined in other PIBs) to provide for a comprehensive policy controlled mapping of service requirement to device resource capability and usage.
本文档描述了用于实现区分服务体系结构的设备的策略信息库（PIB）。这里定义的供应类为实现区分服务体系结构的资源提供策略控制。这些资源调配类可与其他无差别服务调配类（在其他PIB中定义）一起使用，以提供服务需求到设备资源能力和使用的全面策略控制映射。
Table of Contents
目录
Conventions used in this document...................................3
1. Glossary.........................................................3
2. Introduction.....................................................3
3. Relationship to the DiffServ Informal Management Model...........3
3.1. PIB Overview.................................................4
4. Structure of the PIB.............................................6
4.1. General Conventions..........................................6
4.2. DiffServ Data Paths..........................................7
4.2.1. Data Path PRC............................................7
4.3. Classifiers..................................................8
4.3.1. Classifier PRC...........................................9
4.3.2. Classifier Element PRC...................................9
4.4. Meters.......................................................9
4.4.1. Meter PRC...............................................10
4.4.2. Token-Bucket Parameter PRC..............................10
4.5. Actions.....................................................10
4.5.1. DSCP Mark Action PRC....................................11
4.6. Queueing Elements...........................................11
4.6.1. Algorithmic Dropper PRC.................................11
4.6.2. Random Dropper PRC......................................12
4.6.3. Queues and Schedulers...................................14
4.7. Specifying Device Capabilities..............................16
5. PIB Usage Example...............................................17
5.1. Data Path Example...........................................17
5.2. Classifier and Classifier Element Example...................18
5.3. Meter Example...............................................21
5.4. Action Example..............................................21
5.5. Dropper Examples............................................22
5.5.1. Tail Dropper Example....................................22
5.5.2. Single Queue Random Dropper Example.....................23
5.5.3. Multiple Queue Random Dropper Example...................23
5.6. Queue and Scheduler Example...............................26
6. Summary of the DiffServ PIB.....................................27
7. PIB Operational Overview........................................28
8. PIB Definition..................................................29
9. Acknowledgments.................................................90
10. Security Considerations........................................90
11. Intellectual Property Considerations...........................91
12. IANA Considerations............................................91
13. Normative References...........................................92
14. Authors' Addresses.............................................95
15. Full Copyright Statement.......................................96
Conventions used in this document...................................3
1. Glossary.........................................................3
2. Introduction.....................................................3
3. Relationship to the DiffServ Informal Management Model...........3
3.1. PIB Overview.................................................4
4. Structure of the PIB.............................................6
4.1. General Conventions..........................................6
4.2. DiffServ Data Paths..........................................7
4.2.1. Data Path PRC............................................7
4.3. Classifiers..................................................8
4.3.1. Classifier PRC...........................................9
4.3.2. Classifier Element PRC...................................9
4.4. Meters.......................................................9
4.4.1. Meter PRC...............................................10
4.4.2. Token-Bucket Parameter PRC..............................10
4.5. Actions.....................................................10
4.5.1. DSCP Mark Action PRC....................................11
4.6. Queueing Elements...........................................11
4.6.1. Algorithmic Dropper PRC.................................11
4.6.2. Random Dropper PRC......................................12
4.6.3. Queues and Schedulers...................................14
4.7. Specifying Device Capabilities..............................16
5. PIB Usage Example...............................................17
5.1. Data Path Example...........................................17
5.2. Classifier and Classifier Element Example...................18
5.3. Meter Example...............................................21
5.4. Action Example..............................................21
5.5. Dropper Examples............................................22
5.5.1. Tail Dropper Example....................................22
5.5.2. Single Queue Random Dropper Example.....................23
5.5.3. Multiple Queue Random Dropper Example...................23
5.6. Queue and Scheduler Example...............................26
6. Summary of the DiffServ PIB.....................................27
7. PIB Operational Overview........................................28
8. PIB Definition..................................................29
9. Acknowledgments.................................................90
10. Security Considerations........................................90
11. Intellectual Property Considerations...........................91
12. IANA Considerations............................................91
13. Normative References...........................................92
14. Authors' Addresses.............................................95
15. Full Copyright Statement.......................................96
Conventions used in this document
本文件中使用的公约
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
PRC Provisioning Class. A type of policy data. See [POLTERM]. PRI Provisioning Instance. An instance of a PRC. See [POLTERM]. PIB Policy Information Base. The database of policy information. See [POLTERM]. PDP Policy Decision Point. See [RAP-FRAMEWORK]. PEP Policy Enforcement Point. See [RAP-FRAMEWORK]. PRID Provisioning Instance Identifier. Uniquely identifies an instance of a PRC.
PRC供应类。策略数据的一种类型。见[POLTERM]。PRI配置实例。中国的一个例子。见[POLTERM]。PIB政策信息库。政策信息数据库。见[POLTERM]。PDP政策决策点。请参阅[RAP-FRAMEWORK]。政治公众人物政策执行点。请参阅[RAP-FRAMEWORK]。PRID配置实例标识符。唯一标识PRC的实例。
[SPPI] describes a structure for specifying policy information that can then be transmitted to a network device for the purpose of configuring policy at that device. The model underlying this structure is one of well-defined provisioning classes and instances of these classes residing in a virtual information store called the Policy Information Base (PIB).
[SPPI]描述了一种用于指定策略信息的结构，该策略信息随后可以传输到网络设备，以便在该设备上配置策略。此结构的基础模型是一个定义良好的供应类和这些类的实例，它们驻留在称为策略信息库（policyinformationbase，PIB）的虚拟信息存储中。
This document specifies a set of provisioning classes specifically for configuring QoS Policy for Differentiated Services [DSARCH].
本文档指定了一组专门用于配置区分服务的QoS策略的设置类[DSARCH]。
One way to provision policy is by means of the COPS protocol [COPS], with the extensions for provisioning [COPS-PR]. This protocol supports multiple clients, each of which may provision policy for a specific policy domain such as QoS. The PRCs defined in this DiffServ QoS PIB are intended for use by the COPS-PR diffServ client type. Furthermore, these PRCs are in addition to any other PIBs that may be defined for the diffServ client type in the future, as well as the PRCs defined in the Framework PIB [FR-PIB].
提供策略的一种方法是通过COPS协议[COPS]，以及提供[COPS-PR]的扩展。该协议支持多个客户端，每个客户端可以为特定的策略域（如QoS）提供策略。此DiffServ QoS PIB中定义的PRC旨在供COPS-PR DiffServ客户端类型使用。此外，这些PRC是未来可能为diffServ客户端类型定义的任何其他PIB以及框架PIB[FR-PIB]中定义的PRC的补充。
This PIB is designed according to the Differentiated Services Informal Management Model documented in [MODEL]. The model describes the way that ingress and egress interfaces of a 'n'-port router are modeled. It describes the configuration and management of a DiffServ interface in terms of a Traffic Conditioning Block (TCB) which contains, by definition, zero or more classifiers, meters, actions, algorithmic droppers, queues and schedulers. These elements are
本PIB是根据[模型]中记录的差异化服务非正式管理模型设计的。该模型描述了n端口路由器入口和出口接口的建模方式。它根据流量调节块（TCB）描述了DiffServ接口的配置和管理，根据定义，TCB包含零个或多个分类器、仪表、动作、算法拖放器、队列和调度程序。这些元素是
arranged according to the QoS policy being expressed, and are always in that order. Traffic may be classified; classified traffic may be metered; each stream of traffic identified by a combination of classifiers and meters may have some set of actions performed on it; it may have dropping algorithms applied and it may ultimately be stored into a queue before being scheduled out to its next destination, either onto a link or to another TCB. When the treatment for a given packet must have any of those elements repeated in a way that breaks the permitted sequence {classifier, meter, action, algorithmic dropper, queue, scheduler}, this must be modeled by cascading multiple TCBs.
根据所表示的QoS策略进行安排，并且始终按该顺序排列。交通可分类；可对分类交通进行计量；由分类器和仪表组合识别的每个流量流可能具有对其执行的一些动作集；它可能应用了丢弃算法，并且在被调度到下一个目的地（链路或另一个TCB）之前，它可能最终被存储到队列中。当对给定数据包的处理必须以中断允许序列{分类器、仪表、动作、算法滴管、队列、调度程序}的方式重复这些元素中的任何一个时，必须通过级联多个TCB来建模。
The PIB represents this cascade by following the "Next" attributes of the various elements. They indicate what the next step in DiffServ processing will be, whether it be a classifier, meter, action, algorithmic dropper, queue, scheduler or a decision to now forward a packet.
PIB通过遵循各种元素的“下一个”属性来表示这个级联。它们指出了区分服务处理的下一步是什么，是分类器、计量器、操作、算法滴管、队列、调度程序还是现在转发数据包的决定。
The PIB models the individual elements that make up the TCBs. The higher level concept of a TCB is not required in the parameterization or in the linking together of the individual elements, hence it is not used in the PIB itself and is only mentioned in the text for relating the PIB with the [MODEL]. The actual distinguishing of which TCB a specific element is a part of is not needed for the instrumentation of a device to support the functionalities of DiffServ, but it is useful for conceptual reasons. By not using the TCB concept, this PIB allows any grouping of elements to construct TCBs, using rules indicated by the [MODEL]. This will minimize changes to this PIB if rules in [MODEL] change.
PIB对构成TCB的各个元素进行建模。TCB的更高级别概念在参数化或单个元素的连接中不需要，因此它不用于PIB本身，仅在文本中提及，用于将PIB与[模型]关联。具体元件所属TCB的实际区分对于支持区分服务功能的设备的检测来说不是必需的，但出于概念上的原因，它是有用的。通过不使用TCB概念，该PIB允许任何元素分组使用[MODEL]指示的规则来构造TCB。如果[MODEL]中的规则发生更改，这将最小化对此PIB的更改。
The notion of a Data Path is used in this PIB to indicate the DiffServ processing a packet may experience. This Data Path is distinguished based on the Role Combination, Capability Set, and the Direction of the flow the packet is part of. A Data Path Table Entry indicates the first of possibly multiple elements that will apply DiffServ treatment to the packet.
该PIB中使用了数据路径的概念，以指示数据包可能经历的区分服务处理。此数据路径根据角色组合、功能集和数据包所属的流方向进行区分。数据路径表条目指示将对数据包应用区分服务处理的可能多个元素中的第一个元素。
This PIB is structured based on the need to configure the sequential DiffServ treatments being applied to a packet, and the parameterization of these treatments. These two aspects of the configuration are kept separate throughout the design of the PIB, and are fulfilled using separate tables and data definitions.
此PIB的结构基于需要配置应用于数据包的顺序区分服务处理，以及这些处理的参数化。在PIB的整个设计过程中，配置的这两个方面是分开的，并使用单独的表和数据定义来实现。
In addition, the PIB includes tables describing the capabilities and limitations of the device using a general extensible framework.
此外，PIB还包括使用通用可扩展框架描述设备功能和限制的表格。
These tables are reported to the PDP and assist the PDP with the configuration of functional elements that can be realized by the device.
这些表格向PDP报告，并协助PDP配置可由设备实现的功能元件。
This capabilities and limitations exchange allows a single or multiple devices to support many different variations of a functional datapath element. Allowing diverse methods of providing a general functional datapath element.
此功能和限制交换允许单个或多个设备支持功能数据路径元素的多种不同变体。允许提供通用功能数据路径元素的多种方法。
In this PIB, the ingress and egress portions of a router are configured independently but in the same manner. The difference is distinguished by an attribute in a table describing the start of the data path. Each interface performs some or all of the following high-level functions:
在该PIB中，路由器的入口和出口部分以相同的方式独立地配置。区别在于表中描述数据路径起点的属性。每个接口执行以下部分或全部高级功能：
- Classify each packet according to some set of rules.
- 根据一组规则对每个数据包进行分类。
- Determine whether the data stream the packet is part of is within or outside its metering parameters.
- 确定数据包所属的数据流是否在其计量参数之内或之外。
- Perform a set of resulting actions such as counting and marking of the traffic with a Differentiated Services Code Point (DSCP) as defined in [DSFIELD].
- 执行一组结果操作，如使用[DSFIELD]中定义的差异化服务代码点（DSCP）对流量进行计数和标记。
- Apply the appropriate drop policy, either simple or complex algorithmic drop functionality.
- 应用适当的删除策略，简单或复杂的算法删除功能。
- Enqueue the traffic for output in the appropriate queue, whose scheduler may shape the traffic or simply forward it with some minimum rate or maximum latency.
- 将流量排队以在适当的队列中进行输出，其调度器可以调整流量，或者简单地以某种最小速率或最大延迟转发流量。
The PIB therefore contains the following elements:
因此，PIB包含以下要素：
Data Path Table This describes the starting point of DiffServ data paths within a single DiffServ device. This class describes interface role combination and interface direction specific data paths.
数据路径表描述了单个DiffServ设备中DiffServ数据路径的起点。此类描述接口角色组合和接口方向特定的数据路径。
Classifier Tables A general extensible framework for specifying a group of filters.
分类器表是用于指定一组过滤器的通用可扩展框架。
Meter Tables A general extensible framework and one example of a parameterization table - TBParam table, applicable for Simple Token Bucket Meter, Average Rate Meter, Single Rate Three Color Meter, Two Rate Three Color Meter, and Sliding Window Three Color Meter.
Meter Tables是一个通用的可扩展框架和参数化表的一个示例—TBParam table，适用于简单令牌桶表、平均速率表、单速率三色表、双速率三色表和滑动窗口三色表。
Action Tables A general extensible framework and example of parameterization tables for Mark action. The "multiplexer" and "null" actions described in [MODEL] are accomplished implicitly by means of the Prid structures of the other elements.
Action Tables是一个通用的可扩展框架，是用于标记操作的参数化表的示例。[MODEL]中描述的“多路复用器”和“空”操作通过其他元素的Prid结构隐式完成。
Algorithmic Dropper Tables A general extensible framework for describing the dropper functional datapath element. This includes the absolute dropper and other queue measurement dependent algorithmic droppers.
算法滴管表描述滴管功能数据路径元素的通用可扩展框架。这包括绝对滴管和其他依赖于队列测量的算法滴管。
Queue and Scheduler Tables A general extensible framework for parameterizing queuing and scheduler systems. Notice Shaper is considered as a type of scheduler and is included here.
队列和调度器表是一个通用的可扩展框架，用于参数化队列和调度器系统。注意：Shaper被认为是一种调度器，包含在这里。
Capabilities Tables A general extensible framework for defining the capabilities and limitations of the elements listed above. The capability tables allow intelligent configuration of the elements by a PDP.
功能表是一个通用的可扩展框架，用于定义上述元素的功能和限制。能力表允许PDP对元件进行智能配置。
The PIB consists of PRCs that represent functional elements in the data path (e.g., classifiers, meters, actions), and classes that specify parameters that apply to a certain type of functional element (e.g., a Token Bucket meter or a Mark action). Parameters are typically specified in a separate PRC to enable the use of parameter classes by multiple policies.
PIB由表示数据路径中功能元素的PRC（例如，分类器、仪表、动作）和指定适用于特定类型功能元素的参数的类（例如，令牌桶仪表或标记动作）组成。参数通常在单独的PRC中指定，以允许多个策略使用参数类。
Functional element PRCs use the Prid TC (defined in [SPPI]) to indicate indirection. A Prid is an object identifier that is used to specify an instance of a PRC in another table. A Prid is used to point to parameter PRC that applies to a functional element, such as which filter should be used for a classifier element. A Prid is also used to specify an instance of a functional element PRC that describes what treatment should be applied next for a packet in the data path.
功能元件PRC使用Prid TC（在[SPPI]中定义）来指示间接性。Prid是用于在另一个表中指定PRC实例的对象标识符。Prid用于指向适用于功能元素的参数PRC，例如分类器元素应使用哪个过滤器。Prid还用于指定功能元素PRC的实例，该功能元素PRC描述了接下来应该对数据路径中的数据包应用什么处理。
Note that the use of Prids to specify parameter PRCs allows the same functional element PRC to be extended with a number of different types of parameter PRC's. In addition, using Prids to indicate the next functional datapath element allows the elements to be ordered in any way.
请注意，使用PRID指定参数PRCs允许使用许多不同类型的参数PRC扩展相同的功能元素PRC。此外，使用PRID指示下一个功能数据路径元素允许以任何方式对元素进行排序。
This part of the PIB provides instrumentation for connecting the DiffServ Functional Elements within a single DiffServ device. Please refer to [MODEL] for discussions on the valid sequencing and grouping of DiffServ Functional Elements. Given some basic information, e.g., the interface capability, role combination and direction, the first DiffServ Functional Element is determined. Subsequent DiffServ Functional Elements are provided by the "Next" pointer attribute of each entry of data path tables. A description of how this "Next" pointer is used in each table is provided in their respective DESCRIPTION clauses.
PIB的这一部分提供了在单个DiffServ设备内连接DiffServ功能元件的工具。有关DiffServ功能元素的有效排序和分组的讨论，请参考[模型]。给定一些基本信息，例如接口能力、角色组合和方向，确定第一个DiffServ功能元素。后续的DiffServ功能元素由数据路径表的每个条目的“Next”指针属性提供。每个表中如何使用该“下一个”指针的说明在各自的说明子句中提供。
The Data Path PRC provides the DiffServ treatment starting points for all packets of this DiffServ device. Each instance of this PRC specifies the interface capability, role combination and direction for the packet flow. There should be at most two entries for each instance (interface type, role combination, interface capability), one for ingress and one for egress. Each instance provides the first DiffServ Functional Element that each packet, at a specific interface (identified by the roles assigned to the interface) traveling in a specific relative direction, should experience. Notice this class is interface specific, with the use of interface type capability set and RoleCombination. To indicate explicitly that there are no DiffServ treatments for a particular interface type capability set, role combination and direction, an instance of the Data Path PRC can be created with zeroDotZero in the dsDataPathStart attribute. This situation can also be indicated implicitly by not supplying an instance of a Data Path PRC for that particular interface type capability set, role combination and direction. The explicit/implicit selection is up to the implementation. This means that the PEP should perform normal IP device processing when zeroDotZero is used in the dsDataPathStart attribute, or when the entry does not exist. Normal IP device processing will depend on the device; for example, this can be forwarding the packet.
数据路径PRC为该区分服务设备的所有数据包提供区分服务处理起点。此PRC的每个实例都指定了数据包流的接口能力、角色组合和方向。每个实例最多应有两个条目（接口类型、角色组合、接口功能），一个用于入口，一个用于出口。每个实例都提供了第一个DiffServ功能元素，在特定接口（由分配给接口的角色标识）上，在特定相对方向上移动的每个数据包都应该经历该元素。注意，这个类是特定于接口的，使用接口类型能力集和角色组合。为了明确指出特定接口类型功能集、角色组合和方向没有区分服务处理，可以在dsDataPathStart属性中使用zeroDotZero创建数据路径PRC的实例。这种情况也可以通过不为特定接口类型功能集、角色组合和方向提供数据路径PRC的实例来隐式指示。显式/隐式选择取决于实现。这意味着，当dsDataPathStart属性中使用zeroDotZero或条目不存在时，PEP应执行正常的IP设备处理。正常的IP设备处理将取决于设备；例如，这可以是转发数据包。
Based on implementation experience of network devices where data path functional elements are implemented in separate physical processors or application specific integrated circuits, separated by switch fabric, it seems that more complex notions of data path are required within the network device to correlate the different physically separate data path functional elements. For example, ingress processing may have determined a specific ingress flow that gets aggregated with other ingress flows at an egress data path functional element. Some of the information determined at the ingress data path functional element may need to be used by the egress data path
基于网络设备的实施经验，其中数据路径功能元件在单独的物理处理器或特定于应用的集成电路中实施，由交换机结构分离，似乎在网络设备内需要更复杂的数据路径概念来关联不同的物理上分离的数据路径功能元件。例如，入口处理可能已确定特定入口流，该特定入口流在出口数据路径功能元件处与其他入口流聚合。在入口数据路径功能元件处确定的一些信息可能需要由出口数据路径使用
functional element. In numerous implementations, such information has been carried by adding it to the frame/memory block used to carry the flow within the network device; some implementers have called such information a "preamble" or a "frame descriptor". Different implementations use different formats for such information. Initially, one may think such information has implementation details within the network device that does not need to be exposed outside of the network device. But from Policy Control point of view, such information will be very useful in determining network resource usage feedback from the network device to the policy server. This is accomplished by using the Internal Label Marker and Filter PRCs defined in [FR-PIB].
功能元素。在许多实现中，通过将此类信息添加到用于承载网络设备内的流的帧/存储器块来承载此类信息；一些实现者将此类信息称为“前导”或“帧描述符”。不同的实现对此类信息使用不同的格式。最初，人们可能认为这样的信息在网络设备内具有不需要在网络设备外公开的实现细节。但是从策略控制的角度来看，这些信息在确定从网络设备到策略服务器的网络资源使用反馈时非常有用。这是通过使用[FR-PIB]中定义的内部标签标记和过滤器PRC实现的。
The classifier and classifier element tables determine how traffic is sorted out. They identify separable classes of traffic, by reference to appropriate filters, which may select anything from an individual micro-flow to aggregates identified by DSCP.
分类器和分类器元素表确定如何对流量进行分类。它们通过参考适当的过滤器来识别可分离的流量类别，这些过滤器可以选择从单个微流到DSCP识别的聚合的任何内容。
The classification is used to send these separate streams to appropriate Meter, Action, Algorithmic Dropper, Queue and Scheduler elements. For example, to indicate a multi-stage meter, sub-classes of traffic may be sent to different meter stages: e.g., in an implementation of the Assured Forwarding (AF) PHB [AF-PHB], AF11 traffic might be sent to the first meter, AF12 traffic might be sent to the second and AF13 traffic sent to the second meter stage's out-of-profile action.
分类用于将这些单独的流发送到适当的仪表、动作、算法滴管、队列和调度程序元素。例如，为了指示多级计费器，可以将子类的业务发送到不同的计费器阶段：例如，在保证转发（AF）PHB[AF-PHB]的实现中，可以将AF11业务发送到第一个计费器，将AF12业务发送到第二个计费器阶段，将AF13业务发送到第二个计费器阶段的失配动作。
The concept of a classifier is the same as described in [MODEL]. The structure of the classifier and classifier element tables, is the same as the classifier described in [MODEL]. Classifier elements have an associated precedence order solely for the purpose of resolving ambiguity between overlapping filters. A filter with higher values of precedence are compared first; the order of tests for entries of the same precedence is unimportant.
分类器的概念与[模型]中描述的相同。分类器和分类器元素表的结构与[MODEL]中描述的分类器相同。分类器元素具有相关的优先顺序，仅用于解决重叠过滤器之间的歧义。首先比较优先级值较高的过滤器；相同优先级条目的测试顺序并不重要。
A datapath may consist of more than one classifier. There may be an overlap of filter specification between filters of different classifiers. The first classifier functional datapath element encountered, as determined by the sequencing of diffserv functional datapath elements, will be used first.
一个数据路径可以由多个分类器组成。不同分类器的过滤器之间可能存在过滤器规格的重叠。将首先使用遇到的第一个分类器功能数据路径元素（由diffserv功能数据路径元素的顺序确定）。
An important form of classifier is "everything else": the final stage of the classifier i.e., the one with the lowest precedence, must be "complete" since the result of an incomplete classifier is not necessarily deterministic - see [MODEL] section 4.1.2.
分类器的一种重要形式是“其他一切”：分类器的最后一个阶段，即优先级最低的阶段，必须是“完整”的，因为不完整分类器的结果不一定是确定性的-见[模型]第4.1.2节。
When a classifier PRC is instantiated at the PEP, it should always have at least one classifier element table entry, the "everything else" classifier element, with its filter matching all IP packets. This "everything else" classifier element should be created by the PDP as part of the classifier setup. The PDP has full control of all classifier PRIs instantiated at the PEP.
当在PEP实例化分类器PRC时，它应该始终至少有一个分类器元素表条目，“其他所有”分类器元素，其过滤器匹配所有IP数据包。此“其他一切”分类器元素应由PDP创建，作为分类器设置的一部分。PDP完全控制在PEP实例化的所有分类器PRI。
The definition of the actual filter to be used by the classifier is referenced via a Prid: this enables the use of any sort of filter table that one might wish to design, standard or proprietary. No filters are defined in this PIB. However, standard filters for IP packets are defined in the Framework PIB [FR-PIB].
分类器要使用的实际过滤器的定义通过Prid引用：这允许使用任何类型的过滤器表，人们可能希望设计，标准或专有。此PIB中未定义任何过滤器。然而，IP数据包的标准过滤器是在框架PIB[FR-PIB]中定义的。
Classifiers, used in various ingress and egress interfaces, are organized by the instances of the Classifier PRC. A data path entry points to a classifier entry. A classifier entry identifies a list of classifier elements. A classifier element effectively includes the filter entry, and points to a "next" classifier entry or some other data path functional element.
在各种入口和出口接口中使用的分类器由分类器PRC的实例组织。数据路径入口指向分类器入口。分类器条目标识分类器元素的列表。分类器元素有效地包括过滤器条目，并指向“下一个”分类器条目或某个其他数据路径功能元素。
Classifier elements point to the filters which identify various classes of traffic. The separation between the "classifier element" and the "filter" allows us to use many different kinds of filters with the same essential semantics of "an identified set of traffic". The traffic matching the filter corresponding to a classifier element is given to the "next" data path functional element identified in the classifier element.
分类器元素指向识别不同类别流量的过滤器。“分类器元素”和“过滤器”之间的分离允许我们使用许多不同类型的过滤器，它们具有“已识别的流量集”的相同基本语义。将与分类器元素对应的过滤器相匹配的通信量提供给分类器元素中标识的“下一个”数据路径功能元素。
An example of a filter that may be pointed to by a Classifier Element PRI is the frwkIpFilter PRC, defined in [FR-PIB].
分类器元素PRI可指向的过滤器示例为[FR-PIB]中定义的frwkIpFilter PRC。
A meter, according to [MODEL] section 5, measures the rate at which packets composing a stream of traffic pass it, compares this rate to some set of thresholds, and produces some number (two or more) of potential results. A given packet is said to "conform" to the meter if, at the time the packet is being looked at, the stream appears to be within the meter's profile. PIB syntax makes it easiest to define this as a sequence of one or more cascaded pass/fail tests, modeled here as if-then-else constructs. It is important to understand that this way of modeling does not imply anything about the implementation being "sequential": multi-rate/multi-profile meters, e.g., those designed to support [SRTCM], [TRTCM], or [TSWTCM] can still be
根据[模型]第5节，仪表测量组成流量流的数据包通过它的速率，将该速率与某一组阈值进行比较，并产生一定数量（两个或更多）的潜在结果。如果在查看数据包时，数据流似乎在仪表的配置文件内，则称给定数据包“符合”仪表。PIB语法使得将其定义为一个或多个级联通过/失败测试的序列变得最容易，在这里建模为if-then-else结构。重要的是要理解，这种建模方式并不意味着实现是“顺序的”：多速率/多剖面流量计，例如，设计用于支持[SRTCM]、[TRTCM]或[TSWTCM]的流量计仍然可以使用
modeled this way even if they, of necessity, share information between the stages: the stages are introduced merely as a notational convenience in order to simplify the PIB structure.
以这种方式建模，即使它们必须在阶段之间共享信息：为了简化PIB结构，阶段的引入仅仅是为了便于标记。
The generic meter PRC is used as a base for all more specific forms of meter. The definition of parameters specific to the type of meter used is referenced via a pointer to an instance of a PRC containing those specifics. This enables the use of any sort of specific meter table that one might wish to design, standard or proprietary. One specific meter table is defined in this PIB module. Other meter tables may be defined in other PIB modules.
通用仪表PRC用作所有更具体形式仪表的基础。特定于所用仪表类型的参数定义通过指向包含这些细节的PRC实例的指针引用。这使得可以使用任何一种特定的表，人们可能希望设计，标准或专有。本PIB模块中定义了一个特定的仪表表。其他仪表表可在其他PIB模块中定义。
This is included as an example of a common type of meter. Entries in this class are referenced from the dsMeterSpecific attributes of meter PRC instances. The parameters are represented by a rate dsTBParamRate, a burst size dsTBParamBurstSize, and an interval dsTBparamInterval. The type of meter being parameterized is indicated by the dsTBParamType attribute. This is used to determine how the rate, burst, and rate interval parameters are used. Additional meter parameterization classes can be defined in other PIBs when necessary.
这是一个常见类型仪表的示例。此类中的条目引用自仪表PRC实例的dsMeterSpecific属性。参数由速率dsTBParamRate、突发大小dsTBParamBurstSize和间隔dsTBparamInterval表示。参数化的仪表类型由dsTBParamType属性指示。这用于确定如何使用速率、突发和速率间隔参数。必要时，可在其他PIB中定义其他仪表参数化类别。
Actions include "no action", "mark the traffic with a DSCP" or "specific action". Other tasks such as "shape the traffic" or "drop based on some algorithm" are handled in other functional datapath elements rather than in actions. The "multiplexer", "replicator", and "null" actions described in [MODEL] are accomplished implicitly through various combinations of the other elements.
操作包括“无操作”、“使用DSCP标记流量”或“特定操作”。其他任务，如“塑造流量”或“基于某种算法的丢弃”在其他功能数据路径元素中处理，而不是在操作中处理。[MODEL]中描述的“多路复用器”、“复制器”和“空”操作通过其他元素的各种组合隐式完成。
This PIB uses the Action PRC dsActionTable to organize one Action's relationship with the element(s) before and after it. It allows Actions to be cascaded to enable that multiple Actions be applied to a single traffic stream by using each entry's dsActionNext attribute. The dsActionNext attribute of the last action entry in the chain points to the next element in the TCB, if any, e.g., a Queueing element. It may also point at a next TCB.
此PIB使用Action PRC dsActionTable来组织一个Action前后与元素的关系。它允许级联操作，以便通过使用每个条目的dsActionNext属性将多个操作应用于单个流量流。链中最后一个操作条目的dsActionNext属性指向TCB中的下一个元素（如果有），例如排队元素。它还可能指向下一个TCB。
The parameters needed for the Action element will depend on the type of Action to be taken. Hence the PIB allows for specific Action Tables for the different Action types. This flexibility allows additional Actions to be specified in other PIBs and also allows for the use of proprietary Actions without impact on those defined here.
动作元素所需的参数将取决于要采取的动作类型。因此，PIB允许为不同的动作类型提供特定的动作表。这种灵活性允许在其他PIB中指定其他操作，还允许使用专有操作，而不会影响此处定义的操作。
One may consider packet dropping as an Action element. Packet dropping is handled by the Algorithmic Dropper datapath functional element.
可以考虑分组丢弃作为动作元素。数据包丢弃由算法滴管数据路径功能元素处理。
This Action is applied to traffic in order to mark it with a DiffServ Codepoint (DSCP) value, specified in the dsDscpMarkActTable.
此操作应用于流量，以便使用DSCPmarkActTable中指定的DiffServ代码点（DSCP）值对其进行标记。
These include Algorithmic Droppers, Queues and Schedulers, which are all inter-related in their use of queueing techniques.
其中包括算法滴管、队列和调度程序，它们在使用排队技术时都是相互关联的。
Algorithmic Droppers are represented in this PIB by instances of the Algorithmic Dropper PRC. An Algorithmic Dropper is assumed to operate indiscriminately on all packets that are presented at its input; all traffic separation should be done by classifiers and meters preceding it.
算法滴管在本PIB中由算法滴管PRC的实例表示。假设算法滴管在其输入端呈现的所有数据包上不加区别地操作；所有交通隔离应通过其前面的分类器和仪表进行。
Algorithmic Dropper includes many types of droppers, from the simple always dropper to the more complex random dropper. This is indicated by the dsAlgDropType attribute.
算法滴管包括许多类型的滴管，从简单的始终滴管到更复杂的随机滴管。这由dsAlgDropType属性指示。
Algorithmic Droppers have a close relationship with queuing; each Algorithmic Dropper Table entry contains a dsAlgDropQMeasure attribute, indicating which queue's state affects the calculation of the Algorithmic Dropper. Each entry also contains a dsAlgDropNext attribute that indicates to which queue the Algorithmic Dropper sinks its traffic.
算法滴管与排队有着密切的关系；每个算法滴管表条目都包含一个dsAlgDropQMeasure属性，指示哪个队列的状态影响算法滴管的计算。每个条目还包含一个dsAlgDropNext属性，该属性指示算法滴管将其流量接收到哪个队列。
Algorithmic Droppers may also contain a pointer to a specific detail of the drop algorithm, dsAlgDropSpecific. This PIB defines the detail for three drop algorithms: Tail Drop, Head Drop, and Random Drop; other algorithms are outside the scope of this PIB module, but the general framework is intended to allow for their inclusion via other PIB modules.
算法滴管还可能包含指向滴管算法特定细节的指针dsAlgDropSpecific。该PIB定义了三种下降算法的细节：尾部下降、头部下降和随机下降；其他算法不在本PIB模块的范围内，但通用框架旨在允许通过其他PIB模块包含这些算法。
One generally-applicable parameter of a dropper is the specification of a queue-depth threshold at which some drop action is to start. This is represented in this PIB, as a base attribute, dsAlgDropQThreshold, of the Algorithmic Dropper entry. The attribute, dsAlgDropQMeasure, specifies which queue's depth dsAlgDropQThreshold is to be compared against.
滴管的一个普遍适用的参数是队列深度阈值的规格，在该阈值下，一些滴管操作将开始。这在这个PIB中表示为算法滴管条目的基本属性dsAlgDropQThreshold。属性dsAlgDropQMeasure指定要与哪个队列的深度dsAlgDropQThreshold进行比较。
o An Always Dropper drops every packet presented to it. This type of dropper does not require any other parameter.
o 一个总是滴管会滴落每一个包裹。这种类型的滴管不需要任何其他参数。
o A Tail Dropper requires the specification of a maximum queue depth threshold: when the queue pointed at by dsAlgDropQMeasure reaches that depth threshold, dsAlgDropQThreshold, any new traffic arriving at the dropper is discarded. This algorithm uses only parameters that are part of the dsAlgDropEntry.
o 尾部滴管需要指定最大队列深度阈值：当dsAlgDropQMeasure指向的队列达到该深度阈值dsAlgDropQThreshold时，到达滴管的任何新流量都将被丢弃。此算法仅使用属于dsAlgDropEntry的参数。
o A Head Dropper requires the specification of a maximum queue depth threshold: when the queue pointed at by dsAlgDropQMeasure reaches that depth threshold, dsAlgDropQThreshold, traffic currently at the head of the queue is discarded. This algorithm uses only parameters that are part of the dsAlgDropEntry.
o 头滴管需要指定最大队列深度阈值：当dsAlgDropQMeasure指向的队列达到深度阈值dsAlgDropQThreshold时，当前位于队列头的流量将被丢弃。此算法仅使用属于dsAlgDropEntry的参数。
o Random Droppers are recommended as a way to control congestion, in [QUEUEMGMT] and called for in the [AF-PHB]. Various implementations exist, that agree on marking or dropping just enough traffic to communicate with TCP-like protocols about congestion avoidance, but differ markedly on their specific parameters. This PIB attempts to offer a minimal set of controls for any random dropper, but expects that vendors will augment the PRC with additional controls and status in accordance with their implementation. This algorithm requires additional parameters on top of those in dsAlgDropEntry; these are discussed below.
o 在[QUEUEMGMT]和[AF-PHB]中，推荐使用随机滴管作为控制拥塞的方法。存在各种实现，它们同意标记或丢弃足够的通信量，以便与类似TCP的协议就拥塞避免进行通信，但在具体参数上存在显著差异。本PIB试图为任何随机滴管提供一组最小的控制，但期望供应商根据其实施情况，通过附加控制和状态来增加PRC。该算法需要在dsAlgDropEntry中的参数之上添加其他参数；下文将讨论这些问题。
A Dropper Type of other is provided for the implementation of dropper types not defined here. When the Dropper Type is other, its full specification will need to be provided by another PRC referenced by dsAlgDropSpecific. A Dropper Type of Multiple Queue Random Dropper is also provided; please reference section 5.5.3 of this document for more details.
为实现此处未定义的滴管类型，提供了other的滴管类型。当滴管类型为“其他”时，其完整规范将需要由DSALGDROPPECIT引用的另一个PRC提供。还提供了一种多队列随机滴管的滴管类型；更多详情请参考本文件第5.5.3节。
One example of a random dropper is a RED-like dropper. An example of the representation chosen in this PIB for this element is shown in Figure 1.
随机滴管的一个例子是红色的滴管。图1显示了在此PIB中为该元素选择的表示的示例。
Random droppers often have their drop probability function described as a plot of drop probability (P) against averaged queue length (Q). (Qmin, Pmin) then defines the start of the characteristic plot. Normally Pmin=0, meaning that with average queue length below Qmin, there will be no drops. (Qmax, Pmax) defines a "knee" on the plot, after which point the drop probability become more progressive (greater slope). (Qclip, 1) defines the queue length at which all
随机丢弃者的丢弃概率函数通常被描述为丢弃概率（P）与平均队列长度（Q）的关系图。（Qmin，Pmin）然后定义特征图的开始。通常，Pmin=0，这意味着平均队列长度低于Qmin时，将不会有丢弃。（Qmax，Pmax）在曲线图上定义了一个“拐点”，在此点之后，下降概率变得更加渐进（坡度更大）。（Qclip，1）定义所有
packets will be dropped. Notice this is different from Tail Drop because this uses an averaged queue length. Although it is possible for Qclip = Qmax.
数据包将被丢弃。请注意，这与尾部下降不同，因为它使用平均队列长度。虽然Qclip=Qmax是可能的。
In the PIB module, dsRandomDropMinThreshBytes and dsRandomDropMinThreshPkts represent Qmin. dsRandomDropMaxThreshBytes and dsRandomDropMaxThreshPkts represent Qmax. dsAlgDropQThreshold represents Qclip. dsRandomDropProbMax represents Pmax. This PIB does not represent Pmin (assumed to be zero unless otherwise represented).
在PIB模块中，dsRandomDropMinThreshBytes和dsRandomDropMinThreshPKT表示Qmin。dsRandomDropMaxThreshBytes和DSRandomDropMaxThreshPKT表示Qmax。dsAlgDropQThreshold表示Qclip。dsRandomDropProbMax表示Pmax。该PIB不代表Pmin（除非另有说明，否则假定为零）。
In addition, since message memory is finite, queues generally have some upper bound above which they are incapable of storing additional traffic. Normally this number is equal to Qclip, specified by dsAlgDropQThreshold.
此外，由于消息内存是有限的，队列通常有一些上限，超过这个上限，它们无法存储额外的流量。通常，该数字等于dsAlgDropQThreshold指定的Qclip。
Each random dropper specification is associated with a queue. This allows multiple drop processes (of same or different types) to be associated with the same queue, as different PHB implementations may require. This also allows for sequences of multiple droppers if necessary.
每个随机滴管规范都与一个队列相关联。这允许多个丢弃进程（相同或不同类型）与同一队列相关联，因为不同的PHB实现可能需要。如有必要，这也允许多个滴管的顺序。
+-----------------+ +-------+
|AlgDrop | |Queue |
--->| Next ---------+-+----------------->| Next -+-->
| QMeasure -------+-+ | ... |
| QThreshold | +-------+
| Type=randomDrop | +----------------+
| Specific -------+-->|RandomDrop |
+-----------------+ | MinThreshBytes |
| MaxThreshBytes |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
+-----------------+ +-------+
|AlgDrop | |Queue |
--->| Next ---------+-+----------------->| Next -+-->
| QMeasure -------+-+ | ... |
| QThreshold | +-------+
| Type=randomDrop | +----------------+
| Specific -------+-->|RandomDrop |
+-----------------+ | MinThreshBytes |
| MaxThreshBytes |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
Figure 1: Example Use of the RandomDropTable for Random Droppers
图1:RandomDropTable用于随机滴管的示例
The calculation of a smoothed queue length may also have an important bearing on the behavior of the dropper: parameters may include the sampling interval or rate, and the weight of each sample. The performance may be very sensitive to the values of these parameters and a wide range of possible values may be required due to a wide range of link speeds. Most algorithms include a sample weight, represented here by dsRandomDropWeight. The availability of dsRandomDropSamplingRate as readable is important; the information provided by the Sampling Rate is essential to the configuration of dsRandomDropWeight. Having the Sampling Rate be configurable is also
平滑队列长度的计算也可能对滴管的行为有重要影响：参数可能包括采样间隔或速率，以及每个样本的权重。性能可能对这些参数的值非常敏感，并且由于链路速度的范围很广，可能需要范围很广的可能值。大多数算法都包含一个样本权重，这里用dsRandomDropWeight表示。dsRandomDropSamplingRate的可读性非常重要；采样率提供的信息对于DSR随机落锤的配置至关重要。还可以配置采样率
helpful, because as line speed increases, the ability to have queue sampling be less frequent than packet arrival is needed. Note however that there is ongoing research on this topic, see e.g., [ACTQMGMT] and [AQMROUTER].
这很有帮助，因为随着线路速度的提高，需要队列采样的频率低于数据包到达的频率。然而，请注意，关于这一主题的研究仍在进行中，请参见[ACTQMGMT]和[AQMROUTER]。
Additional parameters may be added in an enterprise PIB module, e.g., by using AUGMENTS on this class, to handle aspects of random drop algorithms that are not standardized here.
可以在企业PIB模块中添加其他参数，例如，通过使用此类上的增强来处理此处未标准化的随机丢弃算法的各个方面。
NOTE: Deterministic Droppers can be viewed as a special case of Random Droppers with the drop probability restricted to 0 and 1. Hence Deterministic Droppers might be described by a Random Dropper with Pmin = 0, Pmax = 1, Qmin = Qmax = Qclip, the averaged queue length at which dropping occurs.
注：确定性滴管可视为随机滴管的特例，滴管概率限制为0和1。因此，确定性滴管可以用Pmin=0、Pmax=1、Qmin=Qmax=Qclip（发生滴管的平均队列长度）的随机滴管来描述。
The Queue PRC models simple FIFO queues, as described in [MODEL] section 7.1.1. The Scheduler PRC allows flexibility in constructing both simple and somewhat more complex queueing hierarchies from those queues. Of course, since TCBs can be cascaded multiple times on an interface, even more complex hierarchies can be constructed that way also.
队列PRC模拟简单的FIFO队列，如第7.1.1节[模型]所述。调度器PRC允许灵活地从这些队列构造简单的和稍微复杂一些的队列层次结构。当然，由于TCB可以在一个接口上级联多次，因此也可以通过这种方式构造更复杂的层次结构。
Queue PRC instances are pointed at by the "next" attributes of the upstream elements e.g., dsMeterSucceedNext. Note that multiple upstream elements may direct their traffic to the same Queue PRI. For example, the Assured Forwarding PHB suggests that all traffic marked AF11, AF12, or AF13 be placed in the same queue after metering, without reordering. This would be represented by having the dsMeterSucceedNext of each upstream meter point at the same Queue PRI.
队列PRC实例由上游元素的“下一个”属性指向，例如dsMeterSucceedNext。请注意，多个上游元素可以将其流量定向到同一队列PRI。例如，保证转发PHB建议所有标记为AF11、AF12或AF13的流量在计量后放置在同一队列中，而无需重新排序。这可以通过使每个上游计量点的dsMeterSucceedNext位于同一队列PRI来表示。
NOTE: Queue and Scheduler PRIs are for data path description; they both use Scheduler Parameterization Table entries for diffserv treatment parameterization.
注意：队列和调度程序PRI用于数据路径描述；它们都使用调度程序参数化表条目进行区分服务处理参数化。
A Queue Table entry specifies the scheduler it wants service from by use of its Next pointer.
队列表条目通过使用其下一个指针指定要从中获得服务的计划程序。
Each Scheduler Table entry represents the algorithm in use for servicing the one or more queues that feed it. [MODEL] section 7.1.2 describes a scheduler with multiple inputs: this is represented in the PIB by having the scheduling parameters be associated with each input. In this way, sets of Queues can be grouped together as inputs to the same Scheduler. This class serves to represent the example scheduler described in the [MODEL]: other more complex representations might be created outside of this PIB.
每个调度程序表项表示用于为其提供服务的一个或多个队列提供服务的算法。[模型]第7.1.2节描述了具有多个输入的调度器：这在PIB中通过将调度参数与每个输入关联来表示。通过这种方式，队列集可以组合在一起作为同一调度器的输入。此类用于表示[MODEL]中描述的示例调度器：其他更复杂的表示可能在该PIB之外创建。
Both the Queue PRC and the Scheduler PRC use instances of the Scheduler Parameterization PRC to specify diffserv treatment parameterization. Scheduler Parameter PRC instances are used to parameterize each input that feeds into a scheduler. The inputs can be a mixture of Queue PRI's and Scheduler PRI's. Scheduler Parameter PRI's can be used/reused by one or more Queue and/or Scheduler Table entries.
队列PRC和调度程序PRC都使用调度程序参数化PRC的实例来指定区分服务处理参数化。调度器参数PRC实例用于参数化馈送到调度器的每个输入。输入可以是队列优先级和调度程序优先级的混合。调度程序参数PRI可由一个或多个队列和/或调度程序表项使用/重用。
For representing a Strict Priority scheduler, each scheduler input is assigned a priority with respect to all the other inputs feeding the same scheduler, with default values for the other parameters. A higher-priority input which contains traffic that is not being delayed for shaping will be serviced before a lower-priority input.
为了表示严格优先级的调度器，每个调度器输入都被分配了一个优先级，相对于为同一个调度器提供数据的所有其他输入，其他参数都有默认值。包含未延迟成形的通信量的高优先级输入将在低优先级输入之前得到服务。
For Weighted Scheduling methods e.g., WFQ, WRR, the "weight" of a given scheduler input is represented with a Minimum Service Rate leaky-bucket profile that provides a guaranteed minimum bandwidth to that input, if required. This is represented by a rate dsMinRateAbsolute; the classical weight is the ratio between that rate and the interface speed, or perhaps the ratio between that rate and the sum of the configured rates for classes. Alternatively, the rate may be represented by a relative value, as a fraction of the interface's current line rate, dsMinRateRelative to assist in cases where line rates are variable or where a higher-level policy might be expressed in terms of fractions of network resources. The two rate parameters are inter-related and changes in one may be reflected in the other.
对于加权调度方法，例如WFQ、WRR，给定调度器输入的“权重”用最小服务速率泄漏桶配置文件表示，该配置文件为该输入提供保证的最小带宽（如果需要）。这是由dsMinRateAbsolute比率表示的；经典权重是该速率与接口速度之间的比率，或者可能是该速率与类的配置速率之和之间的比率。或者，速率可以用相对值表示，作为接口当前线路速率的一部分，DSMIN相对，以在线路速率可变或更高级别的策略可以用网络资源的一部分表示的情况下提供帮助。这两个速率参数相互关联，其中一个参数的变化可能反映在另一个参数中。
For weighted scheduling methods, one can say loosely, that WRR focuses on meeting bandwidth sharing, without concern for relative delay amongst the queues, where WFQ control both queue service order and amount of traffic serviced, providing meeting bandwidth sharing and relative delay ordering amongst the queues.
对于加权调度方法，可以粗略地说，WRR专注于满足带宽共享，而不考虑队列之间的相对延迟，其中WFQ控制队列服务顺序和服务的流量量，提供队列之间的会议带宽共享和相对延迟顺序。
A queue or scheduled set of queues (which is an input to a scheduler) may also be capable of acting as a non-work-conserving [MODEL] traffic shaper: this is done by defining a Maximum Service Rate leaky-bucket profile in order to limit the scheduler bandwidth available to that input. This is represented by a rate dsMaxRateAbsolute; the classical weight is the ratio between that rate and the interface speed, or perhaps the ratio between that rate and the sum of the configured rates for classes. Alternatively, the rate may, be represented by a relative value, as a fraction of the interface's current line rate, dsMaxRateRelative. There was discussion in the working group about alternative modeling approaches, such as defining a shaping action or a shaping element. We did not take this approach because shaping is in fact something a scheduler does to its inputs, (which we model as a queue with a
一个队列或一组调度队列（作为调度器的输入）也可以充当非工作节约[模型]流量整形器：这是通过定义最大服务速率泄漏桶配置文件来实现的，以限制该输入可用的调度器带宽。这由速率dsMaxRateAbsolute表示；经典权重是该速率与接口速度之间的比率，或者可能是该速率与类的配置速率之和之间的比率。或者，速率可以用相对值表示，作为接口当前线路速率DSMAXRATERVAL的一部分。工作组讨论了其他建模方法，例如定义塑造行动或塑造要素。我们没有采用这种方法，因为成形实际上是调度器对其输入所做的事情（我们将其建模为带有
maximum rate or a scheduler whose output has a maximum rate) and we felt it was simpler and more elegant to simply describe it in that context. Additionally, multi-rate shaper [SHAPER] can be represented by the use of multiple dsMaxRateTable entries.
最大速率或其输出具有最大速率的调度器），我们觉得在该上下文中简单地描述它更简单、更优雅。此外，多速率整形器[shaper]可以通过使用多个dsMaxRateTable条目来表示。
Other types of priority and weighted scheduling methods can be defined using existing parameters in dsMinRateEntry. NOTE: dsSchedulerMethod uses AutonomousType syntax, with the different types of scheduling methods defined as OBJECT-IDENTITY. Future scheduling methods may be defined in other PIBs. This requires an OBJECT-IDENTITY definition, a description of how the existing objects are reused, if they are, and any new objects they require.
其他类型的优先级和加权调度方法可以使用dsMinRateEntry中的现有参数来定义。注意：dsSchedulerMethod使用自治类型语法，不同类型的调度方法定义为对象标识。未来的调度方法可在其他PIB中定义。这需要一个对象标识定义，描述如何重用现有对象（如果是），以及它们需要的任何新对象。
NOTE: Hierarchical schedulers can be parameterized using this PIB by having Scheduler Table entries feeds into Scheduler Table entry.
注意：通过将调度程序表条目馈送到调度程序表条目中，可以使用此PIB参数化分层调度程序。
The DiffServ PIB uses the Base PRC classes frwkPrcSupportTable and frwkCompLimitsTable defined in [FR-PIB] to specify what PRC's are supported by a PEP and to specify any limitations on that support. The PIB also uses the capability PRC's frwkCapabilitySetTable and frwkIfRoleComboTable defined in [FR-PIB] to specify the device's capability sets, interface types, and role combinations. Each instance of the capability PRC frwkCapabilitySetTable contains an OID that points to an instance of a PRC that describes some capability of that interface type. The DiffServ PIB defines several of these capability PRCs, that assist the PDP with the configuration of DiffServ functional elements that can be implemented by the device. Each of these capability PRCs contains a direction attribute that specifies the direction for which the capability applies. This attribute is defined in a base capability PRC, which is extended by each specific capability PRC.
DiffServ PIB使用[FR-PIB]中定义的基本PRC类frwkPrcSupportTable和frwkCompLimitsTable来指定PEP支持哪些PRC，并指定该支持的任何限制。PIB还使用[FR-PIB]中定义的功能PRC的frwkCapabilitySetTable和frwkIfRoleComboTable来指定设备的功能集、接口类型和角色组合。功能PRC frwkCapabilitySetTable的每个实例都包含一个OID，该OID指向描述该接口类型的某些功能的PRC实例。DiffServ PIB定义了其中几个功能PRC，用于帮助PDP配置可由设备实现的DiffServ功能元件。每个功能PRC都包含一个方向属性，该属性指定应用该功能的方向。此属性在基本能力PRC中定义，由每个特定能力PRC扩展。
Classification capabilities, which specify the information elements the device can use to classify traffic, are reported using the dsIfClassificationCaps PRC. Metering capabilities, which indicate what the device can do with out-of-profile packets, are specified using the dsIfMeteringCaps PRC. Scheduling capabilities, such as the number of inputs supported, are reported using the dsIfSchedulingCaps PRC. Algorithmic drop capabilities, such as the types of algorithms supported, are reported using the dsIfAlgDropCaps PRC. Queue capabilities, such as the maximum number of queues, are reported using the dsIfQueueCaps PRC. Maximum Rate capabilities, such as the maximum number of max rate Levels, are reported using the dsIfMaxRateCaps PRC.
使用dsIfClassificationCaps PRC报告分类功能，该功能指定设备可用于分类流量的信息元素。使用dsIfMeteringCaps PRC指定指示设备可以对配置文件外数据包执行哪些操作的计量功能。使用dsIfSchedulingCaps PRC报告调度功能，如支持的输入数量。使用dsIfAlgDropCaps PRC报告算法丢弃功能，如支持的算法类型。使用dsIfQueueCaps PRC报告队列功能，如最大队列数。使用dsIfMaxRateCaps PRC报告最大速率能力，例如最大速率级别的最大数量。
Two PRC's are defined to allow specification of the element linkage capabilities of the PEP. The dsIfElmDepthCaps PRC indicates the maximum number of functional datapath elements that can be linked consecutively in a datapath. The dsIfElmLinkCaps PRC indicates what functional datapath elements may follow a specific type of element in a datapath.
定义了两个PRC，以规范PEP的元件连接能力。dsIfElmDepthCaps PRC表示可在数据路径中连续链接的功能数据路径元素的最大数量。dsIfElmLinkCaps PRC指示在数据路径中特定类型的元素后面可能有哪些功能数据路径元素。
The capability reporting classes in the DiffServ and Framework PIB are meant to allow the PEP to indicate some general guidelines about what the device can do. They are intended to be an aid to the PDP when it constructs policy for the PEP. These classes do not necessarily allow the PEP to indicate every possible configuration that it can or cannot support. If a PEP receives a policy that it cannot implement, it must notify the PDP with a failure report. Currently [COPS-PR] error handling mechanism as specified in [COPS-PR] sections 4.4, 4.5, and 4.6 completely handles all known error cases of this PIB; hence no additional methods or PRCs need to be specified here.
DiffServ和框架PIB中的功能报告类旨在允许PEP指示有关设备功能的一些一般准则。当PDP为政治公众人物制定政策时，它们旨在帮助PDP。这些类不一定允许PEP指出它可以或不能支持的所有可能的配置。如果政治公众人物收到无法实施的政策，则必须向PDP发送故障报告。目前，[COPS-PR]第4.4、4.5和4.6节规定的[COPS-PR]错误处理机制完全处理本PIB的所有已知错误案例；因此，此处无需指定其他方法或PRC。
This section provides some examples on how the different table entries of this PIB may be used together for a DiffServ Device. The usage of each individual attribute is defined within the PIB module itself. For the figures, all the PIB table entry and attribute names are assumed to have "ds" as their first common initial part of the name, with the table entry name assumed to be their second common initial part of the name. "0.0" is being used to mean zeroDotZero. And for Scheduler Method "= X" means "using the OID of diffServSchedulerX".
本节提供了一些示例，说明如何将此PIB的不同表项一起用于DiffServ设备。每个单独属性的用法在PIB模块本身中定义。对于这些图，假设所有PIB表条目和属性名称都有“ds”作为其名称的第一个公共首字母部分，而表条目名称则假定为其名称的第二个公共首字母部分。“0.0”被用来表示zeroDotZero。对于调度器方法“=X”意味着“使用diffServSchedulerX的OID”。
Notice Each entry of the DataPath table is used for a specific interface type handling a flow in a specific direction for a specific functional role-combination. For our example, we just define one such entry.
请注意，DataPath表的每个条目都用于处理特定功能角色组合的特定方向的流的特定接口类型。对于我们的示例，我们只定义一个这样的条目。
+---------------------+
|DataPath |
| CapSetName ="IfCap1"|
| Roles = "A+B" |
| IfDirection=Ingress | +---------+
| Start --------------+--->|Clfr |
+---------------------+ | Id=Dept |
+---------+
+---------------------+
|DataPath |
| CapSetName ="IfCap1"|
| Roles = "A+B" |
| IfDirection=Ingress | +---------+
| Start --------------+--->|Clfr |
+---------------------+ | Id=Dept |
+---------+
Figure 2: DataPath Usage Example
图2：数据路径使用示例
In Figure 2, we are using IfCap1 to indicate interface type with capability set 1 handling ingress flow for functional roles of "A+B". We are using classifier for departments to lead us into the Classifier Example below.
在图2中，我们使用IfCap1指示接口类型，其中功能集1处理“A+B”功能角色的入口流。我们使用部门分类器引导我们进入下面的分类器示例。
We want to show how a multilevel classifier can be built using the classifier tables provided by this PIB. Notice we didn't go into details on the filters because they are not defined by this PIB. Continuing in the Data Path example from the previous section, lets say we want to perform the following classification functionality to do flow separation based on department and application type:
我们想展示如何使用此PIB提供的分类器表构建多级分类器。请注意，我们没有详细介绍过滤器，因为它们不是由PIB定义的。继续上一节的数据路径示例，假设我们希望执行以下分类功能，以根据部门和应用程序类型进行流分离：
if (Dept1) then take Dept1-action { if (Appl1) then take Dept1-Appl1-action. if (Appl2) then take Dept1-Appl2-action. if (Appl3) then take Dept1-Appl3-action.
if（Dept1）然后执行Dept1操作{if（Appl1）然后执行Dept1-Appl1-action。if（Appl2）然后执行Dept1-Appl2-action。if（Appl3）然后执行Dept1-Appl3-action。
}
if (Dept2) then take Dept2-action
{
if (Appl1) then take Dept2-Appl1-action.
if (Appl2) then take Dept2-Appl2-action.
if (Appl3) then take Dept2-Appl3-action.
}
if (Dept3) then take Dept3-action
{
if (Appl1) then take Dept3-Appl1-action.
if (Appl2) then take Dept3-Appl2-action.
if (Appl3) then take Dept3-Appl3-action.
}
}
if (Dept2) then take Dept2-action
{
if (Appl1) then take Dept2-Appl1-action.
if (Appl2) then take Dept2-Appl2-action.
if (Appl3) then take Dept2-Appl3-action.
}
if (Dept3) then take Dept3-action
{
if (Appl1) then take Dept3-Appl1-action.
if (Appl2) then take Dept3-Appl2-action.
if (Appl3) then take Dept3-Appl3-action.
}
The above classification logic is translated into the following PIB table entries, with two levels of classifications.
上述分类逻辑转换为以下PIB表条目，具有两个级别的分类。
First for department:
第一个部门：
+---------+
|Clfr |
| Id=Dept |
+---------+
+---------+
|Clfr |
| Id=Dept |
+---------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept1 | | | Id=D1Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept1|
+-------------+ +------------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept1 | | | Id=D1Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept1|
+-------------+ +------------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept2 | | | Id=D2Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept2|
+-------------+ +------------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept2 | | | Id=D2Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept2|
+-------------+ +------------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept3 | | | Id=D3Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept3|
+-------------+ +------------+
+-------------+ +-----------+
|ClfrElement | +-->|Clfr |
| Id=Dept3 | | | Id=D3Appl |
| ClfrId=Dept | | +-----------+
| Preced=NA | |
| Next -------+--+ +------------+
| Specific ---+----->|Filter Dept3|
+-------------+ +------------+
Second for application:
第二项申请：
+-----------+
|Clfr |
| Id=D1Appl |
+-----------+
+-----------+
|Clfr |
| Id=D1Appl |
+-----------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl1 | | | Id=D1A1Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl1| +--------------+
+---------------+ +------------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl1 | | | Id=D1A1Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl1| +--------------+
+---------------+ +------------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl2 | | | Id=D1A2Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl2| +--------------+
+---------------+ +------------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl2 | | | Id=D1A2Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl2| +--------------+
+---------------+ +------------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl3 | | | Id=D1A3Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl3| +--------------+
+---------------+ +------------+
+---------------+ +--------------+
|ClfrElement | +----------------->|Meter |
| Id=D1Appl3 | | | Id=D1A3Rate1 |
| ClfrId=D1Appl | | | SucceedNext -+--->...
| Preced=NA | | | FailNext ----+--->...
| Next ---------+--+ +------------+ | Specific ----+--->...
| Specific -----+---->|Filter Appl3| +--------------+
+---------------+ +------------+
Figure 3: Classifier Usage Example
图3：分类器使用示例
The application classifiers for department 2 and 3 will be very much like the application classifier for department 1 shown above. Notice in this example, Filters for Appl1, Appl2, and Appl3 are reusable across the application classifiers.
部门2和部门3的应用程序分类器与上面显示的部门1的应用程序分类器非常相似。注意，在本例中，Appl1、Appl2和Appl3的过滤器可以跨应用程序分类器重用。
This classifier and classifier element example assume the next differentiated services functional datapath element is Meter and leads us into the Meter Example section.
这个分类器和分类器元素示例假定下一个区分服务功能数据路径元素是Meter，并将我们引入Meter示例部分。
A single rate simple Meter may be easy to envision, hence we will do a Two Rate Three Color [TRTCM] example, using two Meter table entries and two TBParam table entries.
单速率简单仪表可能很容易想象，因此我们将使用两个仪表表条目和两个TBParam表条目来制作一个双速率三色[TRTCM]示例。
+--------------+ +---------+ +--------------+ +----------+
|Meter | +->|Action | +->| Meter | +->|Action |
| Id=D1A1Rate1 | | | Id=Green| | | Id=D1A1Rate2 | | | Id=Yellow|
| SucceedNext -+-+ +---------+ | | SucceedNext -+-+ +----------+
| FailNext ----+-----------------+ | FailNext ----+--+ +-------+
| Specific -+ | | Specific -+ | +->|Action |
+-----------+--+ +-----------+--+ | Id=Red|
| | +-------+
| +------------+ | +------------+
+->|TBParam | +->|TBParam |
| Type=TRTCM | | Type=TRTCM |
| Rate | | Rate |
| BurstSize | | BurstSize |
| Interval | | Interval |
+------------+ +------------+
+--------------+ +---------+ +--------------+ +----------+
|Meter | +->|Action | +->| Meter | +->|Action |
| Id=D1A1Rate1 | | | Id=Green| | | Id=D1A1Rate2 | | | Id=Yellow|
| SucceedNext -+-+ +---------+ | | SucceedNext -+-+ +----------+
| FailNext ----+-----------------+ | FailNext ----+--+ +-------+
| Specific -+ | | Specific -+ | +->|Action |
+-----------+--+ +-----------+--+ | Id=Red|
| | +-------+
| +------------+ | +------------+
+->|TBParam | +->|TBParam |
| Type=TRTCM | | Type=TRTCM |
| Rate | | Rate |
| BurstSize | | BurstSize |
| Interval | | Interval |
+------------+ +------------+
Figure 4: Meter Usage Example
图4：仪表使用示例
For [TRTCM], the first level TBParam entry is used for Committed Information Rate and Committed Burst Size Token Bucket, and the second level TBParam entry is used for Peak Information Rate and Peak Burst Size Token Bucket.
对于[TRTCM]，第一级TBParam条目用于提交的信息速率和提交的突发大小令牌桶，第二级TBParam条目用于峰值信息速率和峰值突发大小令牌桶。
The other meters needed for this example will depend on the service class each classified flow uses. But their construction will be similar to the example given here. The TBParam table entries can be shared by multiple Meter table entries.
本示例所需的其他仪表将取决于每个分类流量使用的服务等级。但是它们的构造将类似于这里给出的示例。TBParam表项可由多个仪表表项共享。
In this example the differentiated services functional datapath element following Meter is Action, detailed in the following section.
在本例中，Meter后面的Differentied services functional datapath元素是Action，将在下一节中详细介绍。
Typically, Mark Action will be used; we will continue using the "Action, Id=Green" branch off the Meter example.
通常，将使用标记动作；我们将继续使用仪表示例的“Action，Id=Green”分支。
Recall this is the D1A1Rate1 SucceedNext branch, meaning the flow belongs to Department 1 Application 1, within the committed rate and burst size limits for this flow. We would like to Mark this flow with a specific DSCP and also with a device internal label.
回想一下，这是D1A1Rate1 SucceedNext分支，意味着该流属于部门1应用程序1，在该流的提交速率和突发大小限制内。我们希望使用特定的DSCP和设备内部标签来标记此流。
+-----------+ +-----------+ +--->AlgDropAF11
|Action | +----------------->|Action | |
| Next -----+--+ +------------+ | Next -----+--+ +-------------+
| Specific -+---->|DscpMarkAct | | Specific -+--->|ILabelMarker |
+-----------+ | Dscp=AF11 | +-----------+ | ILabel=D1A1 |
+------------+ +-------------+
+-----------+ +-----------+ +--->AlgDropAF11
|Action | +----------------->|Action | |
| Next -----+--+ +------------+ | Next -----+--+ +-------------+
| Specific -+---->|DscpMarkAct | | Specific -+--->|ILabelMarker |
+-----------+ | Dscp=AF11 | +-----------+ | ILabel=D1A1 |
+------------+ +-------------+
Figure 5: Action Usage Example
图5：操作使用示例
This example uses the frwkILabelMarker PRC defined in [FR-PIB], showing the device internal label being used to indicate the micro flow that feeds into the aggregated AF flow. This device internal label may be used for flow accounting purposes and/or other data path treatments.
此示例使用[FR-PIB]中定义的FRWKILABELLMAKER PRC，显示用于指示馈入聚合AF流的微流的设备内部标签。该设备内部标签可用于流量核算和/或其他数据路径处理。
The Dropper examples below will continue from the Action example above for AF11 flow. We will provide three different dropper setups, from simple to complex. The examples below may include some queuing structures; they are here only to show the relationship of the droppers to queuing and are not complete. Queuing examples are provided in later sections.
下面的滴管示例将从上面针对AF11 flow的操作示例继续。我们将提供三种不同的滴管设置，从简单到复杂。以下示例可能包括一些排队结构；它们在这里只是为了显示滴管与排队的关系，并不完整。后面的章节将提供排队示例。
The Tail Dropper is one of the simplest. For this example we just want to drop part of the flow that exceeds the queue's buffering capacity, 2 Mbytes.
尾部滴管是最简单的一种。对于本例，我们只想删除超过队列缓冲容量2MB的部分流。
+--------------------+ +------+
|AlgDrop | +->|Q AF1 |
| Id=AF11 | | +------+
| Type=tailDrop | |
| Next --------------+-+--+
| QMeasure ----------+-+
| QThreshold=2Mbytes |
| Specific=0.0 |
+--------------------+
+--------------------+ +------+
|AlgDrop | +->|Q AF1 |
| Id=AF11 | | +------+
| Type=tailDrop | |
| Next --------------+-+--+
| QMeasure ----------+-+
| QThreshold=2Mbytes |
| Specific=0.0 |
+--------------------+
Figure 6: Tail Dropper Usage Example
图6：尾部滴管使用示例
The use of Random Dropper will introduce the usage of dsRandomDropEntry as in the example below.
随机滴管的使用将引入dsRandomDropEntry的使用，如下例所示。
+-----------------+ +------+
|AlgDrop | +->|Q AF1 |
| Id=AF11 | | +------+
| Type=randomDrop | |
| Next -----------+-+--+
| QMeasure -------+-+
| QThreshold | +----------------+
| Specific -------+-->|RandomDrop |
+-----------------+ | MinThreshBytes |
| MinThreshPkts |
| MaxThreshBytes |
| MaxThreshPkts |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
+-----------------+ +------+
|AlgDrop | +->|Q AF1 |
| Id=AF11 | | +------+
| Type=randomDrop | |
| Next -----------+-+--+
| QMeasure -------+-+
| QThreshold | +----------------+
| Specific -------+-->|RandomDrop |
+-----------------+ | MinThreshBytes |
| MinThreshPkts |
| MaxThreshBytes |
| MaxThreshPkts |
| ProbMax |
| Weight |
| SamplingRate |
+----------------+
Figure 7: Single Queue Random Dropper Usage Example
图7：单队列随机滴管使用示例
Notice for Random Dropper, dsAlgDropQThreshold contains the maximum average queue length, Qclip, for the queue being measured as indicated by dsAlgDropQMeasure, the rest of the Random Dropper parameters are specified by dsRandomDropEntry as referenced by dsAlgDropSpecific. In this example, both dsAlgDropNext and dsAlgDropQMeasure references the same queue. This is the simple case but dsAlgDropQMeasure may reference another queue for PEP implementation supporting this feature.
注意：对于随机滴管，dsAlgDropQThreshold包含最大平均队列长度Qclip。对于由dsAlgDropQMeasure指示的正在测量的队列，其余的随机滴管参数由dsAlgDropSpecific引用的dsRandomDropEntry指定。在本例中，dsAlgDropNext和dsAlgDropQMeasure都引用相同的队列。这是一种简单的情况，但dsAlgDropQMeasure可能会引用另一个队列来实现支持此功能的PEP。
When network device implementation requires measuring multiple queues in determining the behavior of a drop algorithm, the existing PRCs defined in this PIB will be sufficient for the simple case, as indicated by this example.
当网络设备实现需要测量多个队列以确定丢弃算法的行为时，本PIB中定义的现有PRC将足以满足简单情况，如本示例所示。
+-------------+ +------+
|AlgDrop | +----------------+-------------------+->|Q_AF1 |
| Id=AF11 | | | | +------+
| Type=mQDrop | | | |
| Next -------+-+ +------------+ | +------------+ |
| QMeasure ---+-->|MQAlgDrop | | +->|MQAlgDrop | |
| QThreshold | | Id=AF11A | | | | Id=AF11B | |
| Specific | | Type | | | | Type | |
+-------------+ | Next ------+-+ | | Next ------+-+
| ExceedNext +---+ | ExceedNext | +------+
| QMeasure --+-+ | QMeasure --+-->|Q_AF2 |
| QThreshold | | | QThreshold | +------+
| Specific + | | | Specific + |
+----------+-+ | +----------+-+
| | +---+
+------+ | +------+ |
| +->|Q_AF1 | |
| +------+ |
| |
| +----------------+ | +----------------+
+->|RandomDrop | +->|RandomDrop |
| MinThreshBytes | | MinThreshBytes |
| MinThreshPkts | | MinThreshPkts |
| MaxThreshBytes | | MaxThreshBytes |
| MaxThreshPkts | | MaxThreshPkts |
| ProbMax | | ProbMax |
| Weight | | Weight |
| SamplingRate | | SamplingRate |
+----------------+ +----------------+
+-------------+ +------+
|AlgDrop | +----------------+-------------------+->|Q_AF1 |
| Id=AF11 | | | | +------+
| Type=mQDrop | | | |
| Next -------+-+ +------------+ | +------------+ |
| QMeasure ---+-->|MQAlgDrop | | +->|MQAlgDrop | |
| QThreshold | | Id=AF11A | | | | Id=AF11B | |
| Specific | | Type | | | | Type | |
+-------------+ | Next ------+-+ | | Next ------+-+
| ExceedNext +---+ | ExceedNext | +------+
| QMeasure --+-+ | QMeasure --+-->|Q_AF2 |
| QThreshold | | | QThreshold | +------+
| Specific + | | | Specific + |
+----------+-+ | +----------+-+
| | +---+
+------+ | +------+ |
| +->|Q_AF1 | |
| +------+ |
| |
| +----------------+ | +----------------+
+->|RandomDrop | +->|RandomDrop |
| MinThreshBytes | | MinThreshBytes |
| MinThreshPkts | | MinThreshPkts |
| MaxThreshBytes | | MaxThreshBytes |
| MaxThreshPkts | | MaxThreshPkts |
| ProbMax | | ProbMax |
| Weight | | Weight |
| SamplingRate | | SamplingRate |
+----------------+ +----------------+
Figure 8: Multiple Queue Random Dropper Usage Example
图8：多队列随机滴管使用示例
For this example, we have two queues, Q_AF1 and Q_AF2, sharing the same buffer resources. We want to make sure the common buffer resource is sufficient to service the AF11 traffic, and we want to measure the two queues for determining the drop algorithm for AF11 traffic feeding into Q_AF1. Notice mQDrop is used for dsAlgDropType of dsAlgDropEntry to indicate Multiple Queue Dropping Algorithm.
对于本例，我们有两个队列，Q_AF1和Q_AF2，它们共享相同的缓冲区资源。我们希望确保公共缓冲区资源足以为AF11流量提供服务，并且我们希望测量两个队列，以确定馈送到Q_AF1的AF11流量的丢弃算法。请注意，mQDrop用于dsAlgDropType的dsAlgDropEntry，以指示多队列丢弃算法。
The common shared buffer resource is indicated by the use of dsAlgDropEntry, with their attributes used as follows:
公共共享缓冲区资源由dsAlgDropEntry表示，其属性使用如下：
- dsAlgDropType indicates the algorithm used, mQDrop. - dsAlgDropNext is used to indicate the next functional data path element to handle the flow when no drop occurs. - dsAlgDropQMeasure is used as the anchor for the list of dsMQAlgDropEntry, one for each queue being measured.
- dsAlgDropType表示使用的算法mQDrop。-DSALGDROPEXT用于指示在未发生下降时处理流的下一个功能数据路径元素。-dsAlgDropQMeasure用作dsMQAlgDropEntry列表的锚，每个被测量的队列对应一个。
- dsAlgDropQThreshold is used to indicate the size of the shared buffer pool. - dsAlgDropSpecific can be used to reference instances of additional PRC (not defined in this PIB) if more parameters are required to describe the common shared buffer resource.
- dsAlgDropQThreshold用于指示共享缓冲池的大小。-如果需要更多参数来描述公共共享缓冲区资源，则DSALGDROPSPECIC可用于引用其他PRC（本PIB中未定义）的实例。
For this example, there are two subsequent dsMQAlgDropEntrys, one for each queue being measured, with its attributes used as follows:
对于本例，有两个后续DSMQALGDropentry，每个被测量的队列一个，其属性使用如下：
- dsMQAlgDropType indicates the algorithm used, for this example, both dsMQAlgDropType uses randomDrop. - dsMQAlgDropQMeasure indicates the queue being measured. - dsMQAlgDropNext indicates the next functional data path element to handle the flow when no drop occurs. - dsMQAlgDropExceedNext is used to indicate the next queue's dsMQAlgDropEntry. With the use of zeroDotZero to indicate the last queue. - dsMQAlgDropQMeasure is used to indicate the queue being measured. For this example, Q_AF1 and Q_AF2 are the two queues used. - dsAlgDropQThreshold is used as in single queue Random Dropper. - dsAlgDropSpecific is used to reference the PRID that describes the dropper parameters as in its normal usage. For this example both dsAlgDropSpecifics reference dsRandomDropEntrys.
- dsMQAlgDropType表示使用的算法，在本例中，dsMQAlgDropType和dsMQAlgDropType都使用randomDrop。-DSMQALGROPQMEASURE表示正在测量的队列。-dsMQAlgDropNext指示在不发生丢弃时处理流的下一个功能数据路径元素。-dsMQAlgDropExceedNext用于指示下一个队列的dsMQAlgDropEntry。使用zeroDotZero指示最后一个队列。-dsMQAlgDropQMeasure用于指示正在测量的队列。对于本例，使用的两个队列是Q_AF1和Q_AF2。-dsAlgDropQThreshold在单队列随机滴管中使用。-dsAlgDropSpecific用于引用PRID，该PRID在正常使用时描述滴管参数。对于本例，两个dsAlgDropSpecifics都引用dsrandomDropEntry。
Notice the anchoring dsAlgDropEntry and the two dsMQAlgDropEntrys all have their Next attribute pointing to Q_AF1. This indicates:
请注意，锚定dsAlgDropEntry和两个dsmqalgdropentry的下一个属性都指向Q_AF1。这表明：
- If the packet does not need to be checked with the individual queue's drop processing because of abundance of common shared buffer resources, then the packet is sent to Q_AF1. - If the packet is not dropped due to current Q_AF1 conditions, then it is sent to Q_AF1. - If the packet is not dropped due to current Q_AF2 conditions, then it is sent to Q_AF1.
- 如果由于公共共享缓冲区资源丰富，数据包不需要通过单个队列的丢弃处理进行检查，那么数据包将被发送到Q_AF1。-如果由于当前的Q_AF1条件，数据包没有被丢弃，那么它将被发送到Q_AF1。-如果由于当前的Q_AF2条件，数据包没有被丢弃，那么它将被发送到Q_AF1。
This example also uses two dsRandomDropEntrys for the two queues it measures. Their attribute usage is the same as if for single queue random dropper.
此示例还使用两个DSRandomDropEntry作为它测量的两个队列。它们的属性用法与单队列随机滴管的相同。
Other more complex result combinations can be achieved by specifying a new PRC and referencing this new PRC with the dsAlgDropSpecific of the anchoring dsAlgDropEntry. A more simple usage can also be achieved when a single set of drop parameters are used for all queues being measured. This, again, can be referenced by the anchoring of dsAlgDropSpecific. These are not defined in this PIB.
其他更复杂的结果组合可以通过指定一个新PRC并使用锚定dsAlgDropEntry的dsAlgDropSpecific引用该新PRC来实现。当对所有正在测量的队列使用一组drop参数时，还可以实现更简单的用法。这同样可以通过dsAlgDropSpecific的锚定来引用。这些未在本PIB中定义。
The queue and scheduler example will continue from the dropper example in the previous section, concentrating in the queue and scheduler DiffServ datapath functional elements. Notice a shaper is constructed using queue and scheduler with MaxRate parameters.
队列和调度器示例将继续上一节中的滴管示例，重点介绍队列和调度器DiffServ datapath功能元素。请注意，整形器是使用带有MaxRate参数的队列和调度器构造的。
+------------+ +-----------------+
---->|Q | +->|Scheduler |
| Id=EF | | | Id=DiffServ |
| Next ------+------------------------+ | Next=0.0 |
| MinRate ---+--+ | | Method=Priority |
| MaxRate -+ | | +----------+ | | MinRate=0.0 |
+----------+-+ +-->|MinRate | | | MaxRate=0.0 |
| | Priority | | +-----------------+
+----------+ | Absolute | |
| | Relative | |
| +-----------+ +----------+ |
+->|MaxRate | |
| Level | |
| Absolute | |
| Relative | |
| Threshold | |
+-----------+ +-------------+
|
+----------+ +------------+ |
---->|Q | +-->|Scheduler | |
| Id=AF1 | | | Id=AF | |
| Next ----+--------------------+ | Next ------+--+
| MinRate -+-+ | | Method=WRR |
| MaxRate | | +----------+ | | MinRate -+ |
+----------+ +->|MinRate | | | MaxRate | |
| Priority | | +----------+-+
| Absolute | | |
| Relative | | +----------+
+----------+ | |
+----------+ | | +------------+
---->|Q | | +->|MinRate |
| Id=AF2 | | | Priority |
| Next ----+--------------------+ | Absolute |
| MinRate -+-+ | | Relative |
| MaxRate | | +----------+ | +------------+
+----------+ +->|MinRate | |
| Priority | |
| Absolute | |
| Relative | |
+----------+ |
+------------+ +-----------------+
---->|Q | +->|Scheduler |
| Id=EF | | | Id=DiffServ |
| Next ------+------------------------+ | Next=0.0 |
| MinRate ---+--+ | | Method=Priority |
| MaxRate -+ | | +----------+ | | MinRate=0.0 |
+----------+-+ +-->|MinRate | | | MaxRate=0.0 |
| | Priority | | +-----------------+
+----------+ | Absolute | |
| | Relative | |
| +-----------+ +----------+ |
+->|MaxRate | |
| Level | |
| Absolute | |
| Relative | |
| Threshold | |
+-----------+ +-------------+
|
+----------+ +------------+ |
---->|Q | +-->|Scheduler | |
| Id=AF1 | | | Id=AF | |
| Next ----+--------------------+ | Next ------+--+
| MinRate -+-+ | | Method=WRR |
| MaxRate | | +----------+ | | MinRate -+ |
+----------+ +->|MinRate | | | MaxRate | |
| Priority | | +----------+-+
| Absolute | | |
| Relative | | +----------+
+----------+ | |
+----------+ | | +------------+
---->|Q | | +->|MinRate |
| Id=AF2 | | | Priority |
| Next ----+--------------------+ | Absolute |
| MinRate -+-+ | | Relative |
| MaxRate | | +----------+ | +------------+
+----------+ +->|MinRate | |
| Priority | |
| Absolute | |
| Relative | |
+----------+ |
+----------+ |
---->|Q | |
| Id=AF3 | |
| Next ----+--------------------+
| MinRate -+-+
| MaxRate | | +----------+
+----------+ +->|MinRate |
| Priority |
| Absolute |
| Relative |
+----------+
+----------+ |
---->|Q | |
| Id=AF3 | |
| Next ----+--------------------+
| MinRate -+-+
| MaxRate | | +----------+
+----------+ +->|MinRate |
| Priority |
| Absolute |
| Relative |
+----------+
Figure 9: Queue and Scheduler Usage Example
图9：队列和调度程序使用示例
This example shows the queuing system for handling EF, AF1, AF2, and AF3 traffic. It is assumed that AF11, AF12, and AF13 traffic feeds into Queue AF1. And likewise for AF2x and AF3x traffic.
此示例显示了处理EF、AF1、AF2和AF3流量的排队系统。假设AF11、AF12和AF13流量馈送到队列AF1。对于AF2x和AF3x流量也是如此。
The AF1, AF2, and AF3 Queues are serviced by the AF Scheduler using a Weighed Round Robin method. The AF Scheduler will service each of the queues feeding into it based on the minimum rate parameters of each queue.
AF1、AF2和AF3队列由AF调度器使用加权循环方法提供服务。AF调度器将根据每个队列的最小速率参数为每个队列提供服务。
The AF and EF traffic are serviced by the DiffServ Scheduler using a Strict Priority method. The DiffServ Scheduler will service each of its inputs based on their priority parameter.
AF和EF流量由DiffServ调度程序使用严格的优先级方法提供服务。DiffServ调度程序将根据每个输入的优先级参数为其提供服务。
Notice there is an upper bound to the servicing of EF traffic by the DiffServ Scheduler. This is accomplished with the use of maximum rate parameters. The DiffServ Scheduler uses both the maximum rate and priority parameters when servicing the EF Queue.
请注意，DiffServ调度程序对EF通信量的服务有一个上限。这是通过使用最大速率参数实现的。在为EF队列提供服务时，DiffServ调度程序同时使用最大速率和优先级参数。
The DiffServ Scheduler is the last DiffServ datapath functional element in this datapath. It uses zeroDotZero in its Next attribute.
DiffServ调度程序是此数据路径中的最后一个DiffServ数据路径功能元素。它在其下一个属性中使用zeroDotZero。
The DiffServ PIB consists of one module containing the base PRCs for setting DiffServ policy, queues, classifiers, meters, etc., and also contains capability PRC's that allow a PEP to specify its device characteristics to the PDP. This module contains two groups that are summarized in this section.
区分服务PIB由一个模块组成，其中包含用于设置区分服务策略、队列、分类器、仪表等的基本PRC，还包含允许PEP向PDP指定其设备特性的功能PRC。本模块包含两个组，在本节中进行了总结。
DiffServ Capabilities Group This group consists of PRCs to indicate to the PDP the types of interface supported on the PEP in terms of their DiffServ capabilities and PRCs that the PDP can install in order to configure these interfaces (queues, scheduling parameters, buffer
区分服务能力组该组由PRC组成，用于向PDP指示PEP上支持的接口类型（根据其区分服务能力），以及PDP可以安装的PRC，以配置这些接口（队列、调度参数、缓冲区）
sizes, etc.) to affect the desired policy. This group describes capabilities in terms of the types of interfaces and takes configuration in terms of interface types and role combinations [FR-PIB]; it does not deal with individual interfaces on the device.
大小等），以影响所需的策略。该组根据接口类型描述功能，并根据接口类型和角色组合进行配置[FR-PIB]；它不处理设备上的单个接口。
DiffServ Policy Group This group contains configurations of the functional elements that comprise the DiffServ policy that applies to an interface and the specific parameters that describe those elements. This group contains classifiers, meters, actions, droppers, queues and schedulers. This group also contains the PRC that associates the datapath elements with role combinations.
区分服务策略组此组包含功能元素的配置，这些功能元素包括应用于接口的区分服务策略以及描述这些元素的特定参数。此组包含分类器、仪表、动作、拖放器、队列和调度程序。此组还包含将datapath元素与角色组合关联的PRC。
This section provides an operational overview of configuring DiffServ QoS policy.
本节提供配置DiffServ QoS策略的操作概述。
After the initial PEP to PDP communication setup, using [COPS-PR] for example, the PEP will provide to the PDP the PIB Provisioning classes (PRCs), interface types, and interface type capabilities it supports.
初始PEP至PDP通信设置后，例如使用[COPS-PR]，PEP将向PDP提供其支持的PIB配置类（PRC）、接口类型和接口类型功能。
The PRCs supported by the PEP are reported to the PDP in the PRC Support Table, frwkPrcSupportTable, defined in the framework PIB [FR-PIB]. Each instance of the frwkPrcSupportTable indicates a PRC that the PEP understands and for which the PDP can send class instances as part of the policy information.
PEP支持的PRC在PRC支持表frwkPrcSupportTable中向PDP报告，frwkPrcSupportTable在框架PIB[FR-PIB]中定义。frwkPrcSupportTable的每个实例表示政治公众人物理解的PRC，PDP可以将其类实例作为策略信息的一部分发送给PRC。
The capabilities of interface types the PEP supports are described by rows in the capability set table, frwkCapabilitySetTable. Each row, or instance of this class contains a pointer to an instance of a PRC that describes the capabilities of the interface type. The capability objects may reside in the dsIfClassifierCapsTable, the dsIfMeteringCapsTable, the dsIfSchedulerCapsTable, the dsIfElmDepthCapsTable, the dsIfElmLinkCapsTable, or in a table defined in another PIB.
PEP支持的接口类型的功能由功能集表frwkCapabilitySetTable中的行描述。该类的每一行或实例都包含一个指向描述接口类型功能的PRC实例的指针。功能对象可以位于dsIfClassifierCapsTable、dsIfMeteringCapsTable、dsIfSchedulerCapsTable、dsIfElmDepthCapsTable、dsIfElmLinkCapsTable中，或者位于另一个PIB中定义的表中。
The PDP, with knowledge of the PEP's capabilities, then provides the PEP with administrative domain and interface-type-specific policy information.
PDP了解政治公众人物的能力，然后向政治公众人物提供特定于管理域和接口类型的策略信息。
Instances of the dsDataPathTable are used to specify the first element in the set of functional elements applied to an interface type. Each instance of the dsDataPathTable applies to an interface type defined by its roles and direction (ingress or egress).
dsDataPathTable的实例用于指定应用于接口类型的功能元素集中的第一个元素。dsDataPathTable的每个实例都应用于由其角色和方向（入口或出口）定义的接口类型。
DIFFSERV-PIB PIB-DEFINITIONS ::= BEGIN
DIFFSERV-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS Unsigned32, MODULE-IDENTITY, MODULE-COMPLIANCE, OBJECT-TYPE, OBJECT-GROUP, pib FROM COPS-PR-SPPI InstanceId, Prid, TagId, TagReferenceId FROM COPS-PR-SPPI-TC zeroDotZero FROM SNMPv2-SMI AutonomousType FROM SNMPv2-TC SnmpAdminString FROM SNMP-FRAMEWORK-MIB RoleCombination, PrcIdentifierOid, PrcIdentifierOidOrZero, AttrIdentifier FROM FRAMEWORK-TC-PIB Dscp FROM DIFFSERV-DSCP-TC IfDirection FROM DIFFSERV-MIB BurstSize FROM INTEGRATED-SERVICES-MIB;
从COPS-PR-SPPI实例ID、Prid、TagId、TagReferenceId从COPS-PR-SPPI-TC zeroDotZero从SNMPv2 SMI自治类型从SNMPv2 TC SNMPAdministring从SNMP-FRAMEWORK-MIB角色组合、PrcIdentifierOid、PrcIdentifierOidOrZero、，来自框架-TC-PIB Dscp的属性标识符来自DIFFSERV-Dscp-TC，来自DIFFSERV-MIB的方向来自INTEGRATED-SERVICES-MIB的BurstSize；
dsPolicyPib MODULE-IDENTITY SUBJECT-CATEGORIES { diffServ (2) } -- DiffServ QoS COPS Client Type LAST-UPDATED "200302180000Z" -- 18 Feb 2003 ORGANIZATION "IETF DIFFSERV WG" CONTACT-INFO " Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive, San Jose, CA 95134-1706 USA Phone: +1 408 526 5260 Email: kzm@cisco.com
dsPolicyPib模块标识主题类别{diffServ（2）}--diffServ QoS COPS客户端类型上次更新“200302180000Z”--2003年2月18日组织“IETF diffServ WG”联系方式“Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞市西塔斯曼大道170号95134-1706电话：+1408 526 5260电子邮件：kzm@cisco.com
John Seligson Nortel Networks, Inc. 4401 Great America Parkway Santa Clara, CA 95054 USA Phone: +1 408 495 2992 Email: jseligso@nortelnetworks.com
John Seligson Nortel Networks，Inc.美国加利福尼亚州圣克拉拉大美洲大道4401号95054电话：+1 408 495 2992电子邮件：jseligso@nortelnetworks.com
Kwok Ho Chan Nortel Networks, Inc.
郭浩灿北电网络有限公司。
600 Technology Park Drive Billerica, MA 01821 USA Phone: +1 978 288 8175 Email: khchan@nortelnetworks.com
美国马萨诸塞州比尔里卡科技园大道600号01821电话：+1 978 288 8175电子邮件：khchan@nortelnetworks.com
Differentiated Services Working Group: diffserv@ietf.org" DESCRIPTION "The PIB module containing a set of provisioning classes that describe quality of service (QoS) policies for DiffServ. It includes general classes that may be extended by other PIB specifications as well as a set of PIB classes related to IP processing.
差异化服务工作组：diffserv@ietf.org“描述”PIB模块，包含一组配置类，用于描述区分服务的服务质量（QoS）策略。它包括可由其他PIB规范扩展的通用类，以及一组与IP处理相关的PIB类。
Copyright (C) The Internet Society (2003). This version of this PIB module is part of RFC 3317; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2003年）。此版本的PIB模块是RFC 3317的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200302180000Z" -- 18 Feb 2003
DESCRIPTION
"Initial version, published as RFC 3317."
::= { pib 4 }
REVISION "200302180000Z" -- 18 Feb 2003
DESCRIPTION
"Initial version, published as RFC 3317."
::= { pib 4 }
dsCapabilityClasses OBJECT IDENTIFIER ::= { dsPolicyPib 1 }
dsPolicyClasses OBJECT IDENTIFIER ::= { dsPolicyPib 2 }
dsPolicyPibConformance OBJECT IDENTIFIER ::= { dsPolicyPib 3 }
dsCapabilityClasses OBJECT IDENTIFIER ::= { dsPolicyPib 1 }
dsPolicyClasses OBJECT IDENTIFIER ::= { dsPolicyPib 2 }
dsPolicyPibConformance OBJECT IDENTIFIER ::= { dsPolicyPib 3 }
-- -- Interface Type Capabilities Group --
----接口类型能力组--
--
-- Interface Type Capability Tables
--
-- The Interface type capability tables define capabilities that may
-- be associated with interfaces of a specific type.
-- This PIB defines capability tables for DiffServ Functionalities.
--
--
-- Interface Type Capability Tables
--
-- The Interface type capability tables define capabilities that may
-- be associated with interfaces of a specific type.
-- This PIB defines capability tables for DiffServ Functionalities.
--
-- -- The Base Capability Table --
----基本能力表--
dsBaseIfCapsTable OBJECT-TYPE SYNTAX SEQUENCE OF DsBaseIfCapsEntry PIB-ACCESS notify STATUS current DESCRIPTION
DsBaseIfCapsEntry PIB-ACCESS通知状态当前描述的dsBaseIfCapsTable对象类型语法序列
"The Base Interface Type Capability class. This class
represents a generic capability supported by a device in the
ingress, egress, or both directions."
::= { dsCapabilityClasses 1 }
"The Base Interface Type Capability class. This class
represents a generic capability supported by a device in the
ingress, egress, or both directions."
::= { dsCapabilityClasses 1 }
dsBaseIfCapsEntry OBJECT-TYPE SYNTAX DsBaseIfCapsEntry STATUS current DESCRIPTION "An instance of this class describes the dsBaseIfCaps class."
dsBaseIfCapsEntry对象类型语法dsBaseIfCapsEntry STATUS current DESCRIPTION“此类的一个实例描述了dsBaseIfCaps类。”
PIB-INDEX { dsBaseIfCapsPrid }
::= { dsBaseIfCapsTable 1 }
PIB-INDEX { dsBaseIfCapsPrid }
::= { dsBaseIfCapsTable 1 }
DsBaseIfCapsEntry ::= SEQUENCE {
dsBaseIfCapsPrid InstanceId,
dsBaseIfCapsDirection INTEGER
}
DsBaseIfCapsEntry ::= SEQUENCE {
dsBaseIfCapsPrid InstanceId,
dsBaseIfCapsDirection INTEGER
}
dsBaseIfCapsPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsBaseIfCapsEntry 1 }
dsBaseIfCapsPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsBaseIfCapsEntry 1 }
dsBaseIfCapsDirection OBJECT-TYPE
SYNTAX INTEGER {
inbound(1),
outbound(2),
inAndOut(3)
}
STATUS current
DESCRIPTION
"This object specifies the direction(s) for which the
capability applies. A value of 'inbound(1)' means the
capability applies only to the ingress direction. A value of
'outbound(2)' means the capability applies only to the egress
direction. A value of 'inAndOut(3)' means the capability
applies to both directions."
::= { dsBaseIfCapsEntry 2 }
dsBaseIfCapsDirection OBJECT-TYPE
SYNTAX INTEGER {
inbound(1),
outbound(2),
inAndOut(3)
}
STATUS current
DESCRIPTION
"This object specifies the direction(s) for which the
capability applies. A value of 'inbound(1)' means the
capability applies only to the ingress direction. A value of
'outbound(2)' means the capability applies only to the egress
direction. A value of 'inAndOut(3)' means the capability
applies to both directions."
::= { dsBaseIfCapsEntry 2 }
-- -- The Classification Capability Table --
--——分类能力表--
dsIfClassificationCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfClassificationCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the classification capabilities of
a Capability Set."
::= { dsCapabilityClasses 2 }
dsIfClassificationCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfClassificationCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the classification capabilities of
a Capability Set."
::= { dsCapabilityClasses 2 }
dsIfClassificationCapsEntry OBJECT-TYPE SYNTAX DsIfClassificationCapsEntry STATUS current DESCRIPTION "An instance of this class describes the classification capabilities of a Capability Set."
dsIfClassificationCapsEntry对象类型语法dsIfClassificationCapsEntry状态当前描述“此类的实例描述功能集的分类功能。”
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfClassificationCapsSpec }
::= { dsIfClassificationCapsTable 1 }
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfClassificationCapsSpec }
::= { dsIfClassificationCapsTable 1 }
DsIfClassificationCapsEntry ::= SEQUENCE {
dsIfClassificationCapsSpec BITS
}
DsIfClassificationCapsEntry ::= SEQUENCE {
dsIfClassificationCapsSpec BITS
}
dsIfClassificationCapsSpec OBJECT-TYPE
SYNTAX BITS {
ipSrcAddrClassification(0),
-- indicates the ability to classify based on
-- IP source addresses
ipDstAddrClassification(1),
-- indicates the ability to classify based on
-- IP destination addresses
ipProtoClassification(2),
-- indicates the ability to classify based on
-- IP protocol numbers
ipDscpClassification(3),
-- indicates the ability to classify based on
-- IP DSCP
ipL4Classification(4),
-- indicates the ability to classify based on
-- IP layer 4 port numbers for UDP and TCP
ipV6FlowID(5)
-- indicates the ability to classify based on
-- IPv6 FlowIDs.
}
dsIfClassificationCapsSpec OBJECT-TYPE
SYNTAX BITS {
ipSrcAddrClassification(0),
-- indicates the ability to classify based on
-- IP source addresses
ipDstAddrClassification(1),
-- indicates the ability to classify based on
-- IP destination addresses
ipProtoClassification(2),
-- indicates the ability to classify based on
-- IP protocol numbers
ipDscpClassification(3),
-- indicates the ability to classify based on
-- IP DSCP
ipL4Classification(4),
-- indicates the ability to classify based on
-- IP layer 4 port numbers for UDP and TCP
ipV6FlowID(5)
-- indicates the ability to classify based on
-- IPv6 FlowIDs.
}
STATUS current
DESCRIPTION
"Bit set of supported classification capabilities. In
addition to these capabilities, other PIBs may define other
capabilities that can then be specified in addition to the
ones specified here (or instead of the ones specified here if
none of these are specified)."
::= { dsIfClassificationCapsEntry 1 }
STATUS current
DESCRIPTION
"Bit set of supported classification capabilities. In
addition to these capabilities, other PIBs may define other
capabilities that can then be specified in addition to the
ones specified here (or instead of the ones specified here if
none of these are specified)."
::= { dsIfClassificationCapsEntry 1 }
-- -- Metering Capabilities --
----计量能力--
dsIfMeteringCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfMeteringCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the metering capabilities of a
Capability Set."
::= { dsCapabilityClasses 3 }
dsIfMeteringCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfMeteringCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the metering capabilities of a
Capability Set."
::= { dsCapabilityClasses 3 }
dsIfMeteringCapsEntry OBJECT-TYPE SYNTAX DsIfMeteringCapsEntry STATUS current DESCRIPTION "An instance of this class describes the metering capabilities of a Capability Set."
dsIfMeteringCapsEntry对象类型语法dsIfMeteringCapsEntry状态当前描述“此类的实例描述功能集的计量功能。”
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfMeteringCapsSpec }
::= { dsIfMeteringCapsTable 1 }
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfMeteringCapsSpec }
::= { dsIfMeteringCapsTable 1 }
DsIfMeteringCapsEntry ::= SEQUENCE {
dsIfMeteringCapsSpec BITS
}
DsIfMeteringCapsEntry ::= SEQUENCE {
dsIfMeteringCapsSpec BITS
}
dsIfMeteringCapsSpec OBJECT-TYPE SYNTAX BITS { zeroNotUsed(0), simpleTokenBucket(1), avgRate(2), srTCMBlind(3), srTCMAware(4), trTCMBlind(5), trTCMAware(6), tswTCM(7)
dsIfMeteringCapsSpec对象类型语法位{zeroNotUsed（0）、simpleTokenBucket（1）、avgRate（2）、srTCMBlind（3）、srTCMAware（4）、trTCMBlind（5）、trTCMAware（6）、tswTCM（7）
}
STATUS current
DESCRIPTION
"Bit set of supported metering capabilities. As with
classification capabilities, these metering capabilities may
be augmented by capabilities specified in other PRCs (in other
PIBs)."
::= { dsIfMeteringCapsEntry 1 }
}
STATUS current
DESCRIPTION
"Bit set of supported metering capabilities. As with
classification capabilities, these metering capabilities may
be augmented by capabilities specified in other PRCs (in other
PIBs)."
::= { dsIfMeteringCapsEntry 1 }
-- -- Algorithmic Dropper Capabilities --
----算法滴管功能--
dsIfAlgDropCapsTable OBJECT-TYPE SYNTAX SEQUENCE OF DsIfAlgDropCapsEntry PIB-ACCESS notify STATUS current DESCRIPTION "This class specifies the algorithmic dropper capabilities of a Capability Set.
DsIfAlgDropCapsEntry PIB-ACCESS notify STATUS current DESCRIPTION的dsIfAlgDropCapsTable对象类型语法序列“此类指定功能集的算法滴管功能。
This capability table indicates the types of algorithmic
drop supported by a Capability Set for a specific flow
direction.
Additional capabilities affecting the drop functionalities
are determined based on queue capabilities associated with
specific instance of a dropper, hence not specified by
this class."
::= { dsCapabilityClasses 4 }
This capability table indicates the types of algorithmic
drop supported by a Capability Set for a specific flow
direction.
Additional capabilities affecting the drop functionalities
are determined based on queue capabilities associated with
specific instance of a dropper, hence not specified by
this class."
::= { dsCapabilityClasses 4 }
dsIfAlgDropCapsEntry OBJECT-TYPE
SYNTAX DsIfAlgDropCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the algorithmic dropper
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfAlgDropCapsType,
dsIfAlgDropCapsMQCount }
::= { dsIfAlgDropCapsTable 1 }
dsIfAlgDropCapsEntry OBJECT-TYPE
SYNTAX DsIfAlgDropCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the algorithmic dropper
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfAlgDropCapsType,
dsIfAlgDropCapsMQCount }
::= { dsIfAlgDropCapsTable 1 }
DsIfAlgDropCapsEntry ::= SEQUENCE {
dsIfAlgDropCapsType BITS,
dsIfAlgDropCapsMQCount Unsigned32
}
DsIfAlgDropCapsEntry ::= SEQUENCE {
dsIfAlgDropCapsType BITS,
dsIfAlgDropCapsMQCount Unsigned32
}
dsIfAlgDropCapsType OBJECT-TYPE
dsIfAlgDropCapsType对象类型
SYNTAX BITS {
zeroNotUsed(0),
oneNotUsed(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5),
mQDrop(6) }
STATUS current
DESCRIPTION
"The type of algorithm that droppers associated with queues
may use.
SYNTAX BITS {
zeroNotUsed(0),
oneNotUsed(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5),
mQDrop(6) }
STATUS current
DESCRIPTION
"The type of algorithm that droppers associated with queues
may use.
The tailDrop(2) algorithm means that packets are dropped from
the tail of the queue when the associated queue's MaxQueueSize
is exceeded. The headDrop(3) algorithm means that packets are
dropped from the head of the queue when the associated queue's
MaxQueueSize is exceeded. The randomDrop(4) algorithm means
that an algorithm is executed which may randomly
drop the packet, or drop other packet(s) from the queue
in its place. The specifics of the algorithm may be
proprietary. However, parameters would be specified in the
dsRandomDropTable. The alwaysDrop(5) will drop every packet
presented to it. The mQDrop(6) algorithm will drop packets
based on measurement from multiple queues."
::= { dsIfAlgDropCapsEntry 1 }
The tailDrop(2) algorithm means that packets are dropped from
the tail of the queue when the associated queue's MaxQueueSize
is exceeded. The headDrop(3) algorithm means that packets are
dropped from the head of the queue when the associated queue's
MaxQueueSize is exceeded. The randomDrop(4) algorithm means
that an algorithm is executed which may randomly
drop the packet, or drop other packet(s) from the queue
in its place. The specifics of the algorithm may be
proprietary. However, parameters would be specified in the
dsRandomDropTable. The alwaysDrop(5) will drop every packet
presented to it. The mQDrop(6) algorithm will drop packets
based on measurement from multiple queues."
::= { dsIfAlgDropCapsEntry 1 }
dsIfAlgDropCapsMQCount OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"Indicates the number of queues measured for the drop
algorithm.
This attribute is ignored when alwaysDrop(5) algorithm is
used. This attribute contains the value of 1 for all drop
algorithm types except for mQDrop(6), where this attribute
is used to indicate the maximum number of dsMQAlgDropEntry
that can be chained together."
::= { dsIfAlgDropCapsEntry 2 }
dsIfAlgDropCapsMQCount OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"Indicates the number of queues measured for the drop
algorithm.
This attribute is ignored when alwaysDrop(5) algorithm is
used. This attribute contains the value of 1 for all drop
algorithm types except for mQDrop(6), where this attribute
is used to indicate the maximum number of dsMQAlgDropEntry
that can be chained together."
::= { dsIfAlgDropCapsEntry 2 }
-- -- Queue Capabilities --
----队列功能--
dsIfQueueCapsTable OBJECT-TYPE SYNTAX SEQUENCE OF DsIfQueueCapsEntry PIB-ACCESS notify STATUS current
DsIfQueueCapsEntry PIB-ACCESS通知状态当前的dsIfQueueCapsTable对象类型语法序列
DESCRIPTION
"This class specifies the queueing capabilities of a
Capability Set."
::= { dsCapabilityClasses 5 }
DESCRIPTION
"This class specifies the queueing capabilities of a
Capability Set."
::= { dsCapabilityClasses 5 }
dsIfQueueCapsEntry OBJECT-TYPE
SYNTAX DsIfQueueCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the queue
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfQueueCapsMinQueueSize,
dsIfQueueCapsMaxQueueSize,
dsIfQueueCapsTotalQueueSize }
::= { dsIfQueueCapsTable 1 }
dsIfQueueCapsEntry OBJECT-TYPE
SYNTAX DsIfQueueCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the queue
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfQueueCapsMinQueueSize,
dsIfQueueCapsMaxQueueSize,
dsIfQueueCapsTotalQueueSize }
::= { dsIfQueueCapsTable 1 }
DsIfQueueCapsEntry ::= SEQUENCE {
dsIfQueueCapsMinQueueSize Unsigned32,
dsIfQueueCapsMaxQueueSize Unsigned32,
dsIfQueueCapsTotalQueueSize Unsigned32
}
DsIfQueueCapsEntry ::= SEQUENCE {
dsIfQueueCapsMinQueueSize Unsigned32,
dsIfQueueCapsMaxQueueSize Unsigned32,
dsIfQueueCapsTotalQueueSize Unsigned32
}
dsIfQueueCapsMinQueueSize OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "Bytes"
STATUS current
DESCRIPTION
"Some interfaces may allow the size of a queue to be
configured. This attribute specifies the minimum size that
can be configured for a queue, specified in bytes.
dsIfQueueCapsMinQueueSize must be less than or equals to
dsIfQueueCapsMaxQueueSize when both are specified.
A zero value indicates not specified."
::= { dsIfQueueCapsEntry 1 }
dsIfQueueCapsMinQueueSize OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "Bytes"
STATUS current
DESCRIPTION
"Some interfaces may allow the size of a queue to be
configured. This attribute specifies the minimum size that
can be configured for a queue, specified in bytes.
dsIfQueueCapsMinQueueSize must be less than or equals to
dsIfQueueCapsMaxQueueSize when both are specified.
A zero value indicates not specified."
::= { dsIfQueueCapsEntry 1 }
dsIfQueueCapsMaxQueueSize OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Bytes" STATUS current DESCRIPTION "Some interfaces may allow the size of a queue to be configured. This attribute specifies the maximum size that can be configured for a queue, specified in bytes. dsIfQueueCapsMinQueueSize must be less than or equals to dsIfQueueCapsMaxQueueSize when both are specified. A zero value indicates not specified."
dsIfQueueCapsMaxQueueSize对象类型语法无符号32（0..4294967295）单位“字节”状态当前说明“某些接口可能允许配置队列的大小。此属性指定可以为队列配置的最大大小，以字节为单位。如果同时指定了DSIFQueueCapsInqueueSize和dsIfQueueCapsMaxQueueSize，则DSIFQueueCapsInqueueSize必须小于或等于。零值表示未指定。”
::= { dsIfQueueCapsEntry 2 }
::= { dsIfQueueCapsEntry 2 }
dsIfQueueCapsTotalQueueSize OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "Bytes"
STATUS current
DESCRIPTION
"Some interfaces may have a limited buffer space to be
shared amongst all queues of that interface while also
allowing the size of each queue to be configurable. To
prevent the situation where the PDP configures the sizes of
the queues in excess of the total buffer available to the
interface, the PEP can report the total buffer space in
bytes available with this capability.
A zero value indicates not specified."
::= { dsIfQueueCapsEntry 3 }
dsIfQueueCapsTotalQueueSize OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
UNITS "Bytes"
STATUS current
DESCRIPTION
"Some interfaces may have a limited buffer space to be
shared amongst all queues of that interface while also
allowing the size of each queue to be configurable. To
prevent the situation where the PDP configures the sizes of
the queues in excess of the total buffer available to the
interface, the PEP can report the total buffer space in
bytes available with this capability.
A zero value indicates not specified."
::= { dsIfQueueCapsEntry 3 }
-- -- Scheduler Capabilities --
----调度程序功能--
dsIfSchedulerCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfSchedulerCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the scheduler capabilities of a
Capability Set."
::= { dsCapabilityClasses 6 }
dsIfSchedulerCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfSchedulerCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the scheduler capabilities of a
Capability Set."
::= { dsCapabilityClasses 6 }
dsIfSchedulerCapsEntry OBJECT-TYPE
SYNTAX DsIfSchedulerCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the scheduler
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfSchedulerCapsServiceDisc,
dsIfSchedulerCapsMaxInputs }
::= { dsIfSchedulerCapsTable 1 }
dsIfSchedulerCapsEntry OBJECT-TYPE
SYNTAX DsIfSchedulerCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the scheduler
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfSchedulerCapsServiceDisc,
dsIfSchedulerCapsMaxInputs }
::= { dsIfSchedulerCapsTable 1 }
DsIfSchedulerCapsEntry ::= SEQUENCE {
dsIfSchedulerCapsServiceDisc AutonomousType,
dsIfSchedulerCapsMaxInputs Unsigned32,
dsIfSchedulerCapsMinMaxRate INTEGER
}
DsIfSchedulerCapsEntry ::= SEQUENCE {
dsIfSchedulerCapsServiceDisc AutonomousType,
dsIfSchedulerCapsMaxInputs Unsigned32,
dsIfSchedulerCapsMinMaxRate INTEGER
}
dsIfSchedulerCapsServiceDisc OBJECT-TYPE SYNTAX AutonomousType STATUS current DESCRIPTION "The scheduling discipline for which the set of capabilities specified in this object apply. Object identifiers for several general purpose and well-known scheduling disciplines are shared with and defined in the DiffServ MIB.
dsIfSchedulerCapsServiceDisc对象类型语法自主类型状态当前描述“此对象中指定的一组功能适用的调度规程。几个通用和知名调度规程的对象标识符与DiffServ MIB共享并在其中定义。
These include diffServSchedulerPriority,
diffServSchedulerWRR, diffServSchedulerWFQ."
::= { dsIfSchedulerCapsEntry 1 }
These include diffServSchedulerPriority,
diffServSchedulerWRR, diffServSchedulerWFQ."
::= { dsIfSchedulerCapsEntry 1 }
dsIfSchedulerCapsMaxInputs OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"The maximum number of queues and/or schedulers that can
feed into a scheduler indicated by this capability entry.
A value of zero means there is no maximum."
::= { dsIfSchedulerCapsEntry 2 }
dsIfSchedulerCapsMaxInputs OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"The maximum number of queues and/or schedulers that can
feed into a scheduler indicated by this capability entry.
A value of zero means there is no maximum."
::= { dsIfSchedulerCapsEntry 2 }
dsIfSchedulerCapsMinMaxRate OBJECT-TYPE
SYNTAX INTEGER {
minRate(1),
maxRate(2),
minAndMaxRates(3)
}
STATUS current
DESCRIPTION
"Scheduler capability indicating ability to handle inputs
with minimum rate, maximum rate, or both."
::= { dsIfSchedulerCapsEntry 3 }
dsIfSchedulerCapsMinMaxRate OBJECT-TYPE
SYNTAX INTEGER {
minRate(1),
maxRate(2),
minAndMaxRates(3)
}
STATUS current
DESCRIPTION
"Scheduler capability indicating ability to handle inputs
with minimum rate, maximum rate, or both."
::= { dsIfSchedulerCapsEntry 3 }
-- -- Maximum Rate Capabilities --
----最大速率能力--
dsIfMaxRateCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfMaxRateCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the maximum rate capabilities of a
Capability Set."
::= { dsCapabilityClasses 7 }
dsIfMaxRateCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfMaxRateCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the maximum rate capabilities of a
Capability Set."
::= { dsCapabilityClasses 7 }
dsIfMaxRateCapsEntry OBJECT-TYPE
dsIfMaxRateCapsEntry对象类型
SYNTAX DsIfMaxRateCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the maximum rate
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfMaxRateCapsMaxLevels }
::= { dsIfMaxRateCapsTable 1 }
SYNTAX DsIfMaxRateCapsEntry
STATUS current
DESCRIPTION
"An instance of this class describes the maximum rate
capabilities of a Capability Set."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfMaxRateCapsMaxLevels }
::= { dsIfMaxRateCapsTable 1 }
DsIfMaxRateCapsEntry ::= SEQUENCE {
dsIfMaxRateCapsMaxLevels Unsigned32
}
DsIfMaxRateCapsEntry ::= SEQUENCE {
dsIfMaxRateCapsMaxLevels Unsigned32
}
dsIfMaxRateCapsMaxLevels OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"The maximum number of levels a maximum rate specification
may have for this Capability Set and flow direction."
::= { dsIfMaxRateCapsEntry 1 }
dsIfMaxRateCapsMaxLevels OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"The maximum number of levels a maximum rate specification
may have for this Capability Set and flow direction."
::= { dsIfMaxRateCapsEntry 1 }
-- -- DataPath Element Linkage Capabilities --
----数据路径元素链接功能--
-- -- DataPath Element Cascade Depth --
----数据路径元素级联深度--
dsIfElmDepthCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfElmDepthCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the number of elements of the same
type that can be cascaded together in a datapath."
::= { dsCapabilityClasses 8 }
dsIfElmDepthCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfElmDepthCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies the number of elements of the same
type that can be cascaded together in a datapath."
::= { dsCapabilityClasses 8 }
dsIfElmDepthCapsEntry OBJECT-TYPE SYNTAX DsIfElmDepthCapsEntry STATUS current DESCRIPTION "An instance of this class describes the cascade depth for a particular functional datapath element PRC. A functional datapath element not represented in this class can be assumed to have no specific maximum depth."
dsIfElmDepthCapsEntry对象类型语法dsIfElmDepthCapsEntry STATUS current DESCRIPTION“此类的实例描述特定功能数据路径元素PRC的级联深度。可以假定此类中未表示的功能数据路径元素没有特定的最大深度。”
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfElmDepthCapsPrc }
::= { dsIfElmDepthCapsTable 1 }
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfElmDepthCapsPrc }
::= { dsIfElmDepthCapsTable 1 }
DsIfElmDepthCapsEntry ::= SEQUENCE {
dsIfElmDepthCapsPrc PrcIdentifierOid,
dsIfElmDepthCapsCascadeMax Unsigned32
}
DsIfElmDepthCapsEntry ::= SEQUENCE {
dsIfElmDepthCapsPrc PrcIdentifierOid,
dsIfElmDepthCapsCascadeMax Unsigned32
}
dsIfElmDepthCapsPrc OBJECT-TYPE
SYNTAX PrcIdentifierOid
STATUS current
DESCRIPTION
"The object identifier of a PRC that represents a functional
datapath element. This may be one of: dsClfrElementEntry,
dsMeterEntry, dsActionEntry, dsAlgDropEntry, dsQEntry, or
dsSchedulerEntry.
There may not be more than one instance of this class with
the same value of dsIfElmDepthCapsPrc and same value of
dsBaseIfCapsDirection. Must not contain the value of
zeroDotZero."
::= { dsIfElmDepthCapsEntry 1 }
dsIfElmDepthCapsPrc OBJECT-TYPE
SYNTAX PrcIdentifierOid
STATUS current
DESCRIPTION
"The object identifier of a PRC that represents a functional
datapath element. This may be one of: dsClfrElementEntry,
dsMeterEntry, dsActionEntry, dsAlgDropEntry, dsQEntry, or
dsSchedulerEntry.
There may not be more than one instance of this class with
the same value of dsIfElmDepthCapsPrc and same value of
dsBaseIfCapsDirection. Must not contain the value of
zeroDotZero."
::= { dsIfElmDepthCapsEntry 1 }
dsIfElmDepthCapsCascadeMax OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"The maximum number of elements of type dsIfElmDepthCapsPrc
that can be linked consecutively in a data path. A value of
zero indicates there is no specific maximum."
::= { dsIfElmDepthCapsEntry 2 }
dsIfElmDepthCapsCascadeMax OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"The maximum number of elements of type dsIfElmDepthCapsPrc
that can be linked consecutively in a data path. A value of
zero indicates there is no specific maximum."
::= { dsIfElmDepthCapsEntry 2 }
-- -- DataPath Element Linkage Types --
----数据路径元素链接类型--
dsIfElmLinkCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfElmLinkCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies what types of datapath functional
elements may be used as the next downstream element for
a specific type of functional element."
::= { dsCapabilityClasses 9 }
dsIfElmLinkCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsIfElmLinkCapsEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class specifies what types of datapath functional
elements may be used as the next downstream element for
a specific type of functional element."
::= { dsCapabilityClasses 9 }
dsIfElmLinkCapsEntry OBJECT-TYPE
dsIfElmLinkCapsEntry对象类型
SYNTAX DsIfElmLinkCapsEntry
STATUS current
DESCRIPTION
"An instance of this class specifies a PRC that may
be used as the next functional element after a specific
type of element in a data path."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfElmLinkCapsPrc,
dsIfElmLinkCapsAttr,
dsIfElmLinkCapsNextPrc }
::= { dsIfElmLinkCapsTable 1 }
SYNTAX DsIfElmLinkCapsEntry
STATUS current
DESCRIPTION
"An instance of this class specifies a PRC that may
be used as the next functional element after a specific
type of element in a data path."
EXTENDS { dsBaseIfCapsEntry }
UNIQUENESS { dsBaseIfCapsDirection,
dsIfElmLinkCapsPrc,
dsIfElmLinkCapsAttr,
dsIfElmLinkCapsNextPrc }
::= { dsIfElmLinkCapsTable 1 }
DsIfElmLinkCapsEntry ::= SEQUENCE {
dsIfElmLinkCapsPrc PrcIdentifierOid,
dsIfElmLinkCapsAttr AttrIdentifier,
dsIfElmLinkCapsNextPrc PrcIdentifierOidOrZero
}
DsIfElmLinkCapsEntry ::= SEQUENCE {
dsIfElmLinkCapsPrc PrcIdentifierOid,
dsIfElmLinkCapsAttr AttrIdentifier,
dsIfElmLinkCapsNextPrc PrcIdentifierOidOrZero
}
dsIfElmLinkCapsPrc OBJECT-TYPE
SYNTAX PrcIdentifierOid
STATUS current
DESCRIPTION
" The object identifier of a PRC that represents a functional
datapath element. This may be one of: dsClfrElementEntry,
dsMeterEntry, dsActionEntry, dsAlgDropEntry, dsQEntry, or
dsSchedulerEntry.
This must not have the value zeroDotZero."
::= { dsIfElmLinkCapsEntry 1 }
dsIfElmLinkCapsPrc OBJECT-TYPE
SYNTAX PrcIdentifierOid
STATUS current
DESCRIPTION
" The object identifier of a PRC that represents a functional
datapath element. This may be one of: dsClfrElementEntry,
dsMeterEntry, dsActionEntry, dsAlgDropEntry, dsQEntry, or
dsSchedulerEntry.
This must not have the value zeroDotZero."
::= { dsIfElmLinkCapsEntry 1 }
dsIfElmLinkCapsAttr OBJECT-TYPE
SYNTAX AttrIdentifier
STATUS current
DESCRIPTION
"The value represents the attribute in the PRC
indicated by dsIfElmLinkCapsPrc that is used to
specify the next functional element in the datapath."
::= { dsIfElmLinkCapsEntry 2 }
dsIfElmLinkCapsAttr OBJECT-TYPE
SYNTAX AttrIdentifier
STATUS current
DESCRIPTION
"The value represents the attribute in the PRC
indicated by dsIfElmLinkCapsPrc that is used to
specify the next functional element in the datapath."
::= { dsIfElmLinkCapsEntry 2 }
dsIfElmLinkCapsNextPrc OBJECT-TYPE SYNTAX PrcIdentifierOidOrZero STATUS current DESCRIPTION "The value is the OID of a PRC table entry from which instances can be referenced by the attribute indicated by dsIfElmLinkCapsPrc and dsIfElmLinkAttr.
dsIfElmLinkCapsNextPrc对象类型语法PrcIdentifierOidOrZero STATUS current DESCRIPTION“该值是PRC表项的OID，DSIFELMLinkCapsRC和DSIFELMLLinkAttr指示的属性可以从中引用实例。
For example, suppose a meter's success output can be an
例如，假设一个仪表的成功输出可以是
action or another meter, and the fail output can only be an action. This can be expressed as follows:
动作或另一个仪表，故障输出只能是一个动作。这可以表示为：
Prid Prc Attr NextPrc 1 dsMeterEntry dsMeterSucceedNext dsActionEntry 2 dsMeterEntry dsMeterSucceedNext dsMeterEntry 3 dsMeterEntry dsMeterFailNext dsActionEntry.
Prid Prc Attr NextPrc 1数据表条目数据表成功下一个数据表条目2数据表条目数据表成功下一个数据表条目3数据表条目数据表条目数据表失败下一个数据表条目。
zeroDotZero is a valid value for this attribute to
specify that the PRC specified in dsIfElmLinkCapsPrc
is the last functional data path element."
::= { dsIfElmLinkCapsEntry 3 }
zeroDotZero is a valid value for this attribute to
specify that the PRC specified in dsIfElmLinkCapsPrc
is the last functional data path element."
::= { dsIfElmLinkCapsEntry 3 }
-- -- Policy Classes --
----政策类--
-- -- Data Path Table --
----数据路径表--
dsDataPathTable OBJECT-TYPE SYNTAX SEQUENCE OF DsDataPathEntry PIB-ACCESS install STATUS current DESCRIPTION "The data path table indicates the start of functional data paths in this device.
dsDataPathTable对象类型DsDataPathEntry PIB-ACCESS的语法序列安装状态当前描述“数据路径表指示此设备中功能数据路径的开始。
The Data Path Table enumerates the Differentiated
Services Functional Data Paths within this device.
Each entry specifies the first functional datapath
element to process data flow for each specific datapath.
Each datapath is defined by the interface set's capability
set name, role combination, and direction. This class can
therefore have up to two entries for each interface set,
ingress and egress."
::= { dsPolicyClasses 1 }
The Data Path Table enumerates the Differentiated
Services Functional Data Paths within this device.
Each entry specifies the first functional datapath
element to process data flow for each specific datapath.
Each datapath is defined by the interface set's capability
set name, role combination, and direction. This class can
therefore have up to two entries for each interface set,
ingress and egress."
::= { dsPolicyClasses 1 }
dsDataPathEntry OBJECT-TYPE SYNTAX DsDataPathEntry STATUS current DESCRIPTION "Each entry in this class indicates the start of a single functional data path, defined by its capability set name, role combination and traffic direction. The first functional datapath element to handle traffic for each data path is defined by the dsDataPathStart attribute
dsDataPathEntry对象类型语法dsDataPathEntry状态当前说明“此类中的每个条目表示单个功能数据路径的开始，该路径由其功能集名称、角色组合和通信方向定义。处理每个数据路径流量的第一个功能性datapath元素由dsDataPathStart属性定义
of each table entry.
Notice for each entry:
1. dsDataPathCapSetName must reference an existing capability
set name in frwkCapabilitySetTable [FR-PIB].
2. dsDataPathRoles must reference existing Role Combination
in frwkIfRoleComboTable [FR-PIB].
3. dsDataPathStart must reference an existing entry in a
functional data path element table.
If any one or more of these three requirements is not
satisfied, the dsDataPathEntry will not be installed."
PIB-INDEX { dsDataPathPrid }
UNIQUENESS { dsDataPathCapSetName,
dsDataPathRoles,
dsDataPathIfDirection }
::= { dsDataPathTable 1 }
of each table entry.
Notice for each entry:
1. dsDataPathCapSetName must reference an existing capability
set name in frwkCapabilitySetTable [FR-PIB].
2. dsDataPathRoles must reference existing Role Combination
in frwkIfRoleComboTable [FR-PIB].
3. dsDataPathStart must reference an existing entry in a
functional data path element table.
If any one or more of these three requirements is not
satisfied, the dsDataPathEntry will not be installed."
PIB-INDEX { dsDataPathPrid }
UNIQUENESS { dsDataPathCapSetName,
dsDataPathRoles,
dsDataPathIfDirection }
::= { dsDataPathTable 1 }
DsDataPathEntry ::= SEQUENCE {
dsDataPathPrid InstanceId,
dsDataPathCapSetName SnmpAdminString,
dsDataPathRoles RoleCombination,
dsDataPathIfDirection IfDirection,
dsDataPathStart Prid
}
DsDataPathEntry ::= SEQUENCE {
dsDataPathPrid InstanceId,
dsDataPathCapSetName SnmpAdminString,
dsDataPathRoles RoleCombination,
dsDataPathIfDirection IfDirection,
dsDataPathStart Prid
}
dsDataPathPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsDataPathEntry 1 }
dsDataPathPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsDataPathEntry 1 }
dsDataPathCapSetName OBJECT-TYPE
SYNTAX SnmpAdminString
STATUS current
DESCRIPTION
"The capability set associated with this data path entry.
The capability set name specified by this attribute
must exist in the frwkCapabilitySetTable [FR-PIB]
prior to association with an instance of this class."
::= { dsDataPathEntry 2 }
dsDataPathCapSetName OBJECT-TYPE
SYNTAX SnmpAdminString
STATUS current
DESCRIPTION
"The capability set associated with this data path entry.
The capability set name specified by this attribute
must exist in the frwkCapabilitySetTable [FR-PIB]
prior to association with an instance of this class."
::= { dsDataPathEntry 2 }
dsDataPathRoles OBJECT-TYPE SYNTAX RoleCombination STATUS current DESCRIPTION "The interfaces to which this data path entry applies, specified in terms of roles. There must exist an entry
dsDataPathRoles对象类型语法RoleComposition STATUS current DESCRIPTION“此数据路径条目应用的接口，以角色的形式指定。必须存在一个条目
in the frwkIfRoleComboTable [FR-PIB] specifying
this role combination, together with the capability
set specified by dsDataPathCapSetName, prior to
association with an instance of this class."
::= { dsDataPathEntry 3 }
in the frwkIfRoleComboTable [FR-PIB] specifying
this role combination, together with the capability
set specified by dsDataPathCapSetName, prior to
association with an instance of this class."
::= { dsDataPathEntry 3 }
dsDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection
STATUS current
DESCRIPTION
"Specifies the direction for which this data path
entry applies."
::= { dsDataPathEntry 4 }
dsDataPathIfDirection OBJECT-TYPE
SYNTAX IfDirection
STATUS current
DESCRIPTION
"Specifies the direction for which this data path
entry applies."
::= { dsDataPathEntry 4 }
dsDataPathStart OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This selects the first functional datapath element to handle traffic for this data path. This Prid should point to an instance of one of: dsClfrEntry dsMeterEntry dsActionEntry dsAlgDropEntry dsQEntry
dsDataPathStart对象类型语法Prid STATUS current DESCRIPTION“这将选择第一个功能数据路径元素来处理此数据路径的流量。此Prid应指向以下之一的实例：dsClfrEntry dsMeterEntry dsActionEntry DSALGDROPERTY dsQEntry
The PRI pointed to must exist prior to the installation of
this datapath start element."
::= { dsDataPathEntry 5 }
The PRI pointed to must exist prior to the installation of
this datapath start element."
::= { dsDataPathEntry 5 }
--
-- Classifiers
--
-- Classifier allows multiple classifier elements, of same or
-- different types, to be used together.
-- A classifier must completely classify all packets presented to
-- it. This means all traffic handled by a classifier must match
-- at least one classifier element within the classifier,
-- with the classifier element parameters specified by a filter.
-- It is the PDP's responsibility to create a _catch all_ classifier
-- element and filter that matches all packet. This _catch all_
-- classifier element should have the lowest Precedence value.
--
-- If there is ambiguity between classifier elements of different
-- classifier, classifier linkage order indicates their precedence;
-- the first classifier in the link is applied to the traffic first.
--
--
-- Classifiers
--
-- Classifier allows multiple classifier elements, of same or
-- different types, to be used together.
-- A classifier must completely classify all packets presented to
-- it. This means all traffic handled by a classifier must match
-- at least one classifier element within the classifier,
-- with the classifier element parameters specified by a filter.
-- It is the PDP's responsibility to create a _catch all_ classifier
-- element and filter that matches all packet. This _catch all_
-- classifier element should have the lowest Precedence value.
--
-- If there is ambiguity between classifier elements of different
-- classifier, classifier linkage order indicates their precedence;
-- the first classifier in the link is applied to the traffic first.
--
-- Each entry in the classifier table represents a classifier, with
-- classifier element table handling the fan-out functionality of a
-- classifier, and filter table defining the classification
-- patterns.
--
-- Each entry in the classifier table represents a classifier, with
-- classifier element table handling the fan-out functionality of a
-- classifier, and filter table defining the classification
-- patterns.
--
-- -- Classifier Table --
----分类器表--
dsClfrTable OBJECT-TYPE SYNTAX SEQUENCE OF DsClfrEntry PIB-ACCESS install STATUS current DESCRIPTION "This table enumerates all the DiffServ classifier functional data path elements of this device. The actual classification definitions are detailed in dsClfrElementTable entries belonging to each classifier. Each classifier is referenced by its classifier elements using its classifier ID.
DsClfrEntry PIB-ACCESS的dsClfrTable对象类型语法序列安装状态当前说明“此表列举了此设备的所有DiffServ分类器功能数据路径元素。属于每个分类器的dsClfrElementTable条目详细说明了实际的分类定义。每个分类器由其分类器元素使用其分类器ID引用。
An entry in this table, referenced by an upstream functional data path element or a datapath table entry, is the entry point to the classifier functional data path element.
该表中由上游功能数据路径元素或数据路径表条目引用的条目是分类器功能数据路径元素的入口点。
The dsClfrId of each entry is used to organize all
classifier elements belonging to the same classifier."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 4.1"
::= { dsPolicyClasses 2 }
The dsClfrId of each entry is used to organize all
classifier elements belonging to the same classifier."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 4.1"
::= { dsPolicyClasses 2 }
dsClfrEntry OBJECT-TYPE
SYNTAX DsClfrEntry
STATUS current
DESCRIPTION
"An entry in the classifier table describes a single
classifier. Each classifier element belonging to this
classifier must have its dsClfrElementClfrId attribute equal
to dsClfrId."
PIB-INDEX { dsClfrPrid }
UNIQUENESS { dsClfrId }
::= { dsClfrTable 1 }
dsClfrEntry OBJECT-TYPE
SYNTAX DsClfrEntry
STATUS current
DESCRIPTION
"An entry in the classifier table describes a single
classifier. Each classifier element belonging to this
classifier must have its dsClfrElementClfrId attribute equal
to dsClfrId."
PIB-INDEX { dsClfrPrid }
UNIQUENESS { dsClfrId }
::= { dsClfrTable 1 }
DsClfrEntry ::= SEQUENCE {
dsClfrPrid InstanceId,
dsClfrId TagReferenceId
}
DsClfrEntry ::= SEQUENCE {
dsClfrPrid InstanceId,
dsClfrId TagReferenceId
}
dsClfrPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsClfrEntry 1 }
dsClfrPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsClfrEntry 1 }
dsClfrId OBJECT-TYPE
SYNTAX TagReferenceId
PIB-TAG { dsClfrElementClfrId }
STATUS current
DESCRIPTION
"Identifies a Classifier. A Classifier must be
complete, this means all traffic handled by a
Classifier must match at least one Classifier
Element within the Classifier."
::= { dsClfrEntry 2 }
dsClfrId OBJECT-TYPE
SYNTAX TagReferenceId
PIB-TAG { dsClfrElementClfrId }
STATUS current
DESCRIPTION
"Identifies a Classifier. A Classifier must be
complete, this means all traffic handled by a
Classifier must match at least one Classifier
Element within the Classifier."
::= { dsClfrEntry 2 }
-- -- Classifier Element Table --
----分类器元素表--
dsClfrElementTable OBJECT-TYPE SYNTAX SEQUENCE OF DsClfrElementEntry PIB-ACCESS install STATUS current DESCRIPTION "Entries in the classifier element table serves as the anchor for each classification pattern, defined in filter table entries. Each classifier element table entry also specifies the subsequent downstream diffserv functional datapath element when the classification pattern is satisfied. Hence the classifier element table enumerates the relationship between classification patterns and subsequent downstream diffserv functional data path elements, describing one branch of the fan-out characteristic of a classifier indicated in [Model].
dsClfrElementTable对象类型语法序列DsClfrElementEntry PIB-ACCESS安装状态当前说明“分类器元素表中的条目充当过滤器表条目中定义的每个分类模式的锚。当满足分类模式时，每个分类器元素表项还指定后续的下游diffserv functional datapath元素。因此，分类器元素表列举了分类模式和后续下游diffserv功能数据路径元素之间的关系，描述了[Model]中所示分类器扇出特性的一个分支。
Classification parameters are defined by entries of filter tables pointed to by dsClfrElementSpecific. There can be filter tables of different types, and they can be inter-mixed and used within a classifier. An example of a filter table is the frwkIpFilterTable [FR-PIB], for IP Multi-Field Classifiers (MFCs).
分类参数由dsClfrElementSpecific指向的筛选表条目定义。可以有不同类型的筛选表，它们可以相互混合并在分类器中使用。筛选器表的一个示例是用于IP多字段分类器（MFC）的frwkIpFilterTable[FR-PIB]。
If there is ambiguity between classifier elements of the same
classifier, then dsClfrElementPrecedence needs to be used."
::= { dsPolicyClasses 3 }
If there is ambiguity between classifier elements of the same
classifier, then dsClfrElementPrecedence needs to be used."
::= { dsPolicyClasses 3 }
dsClfrElementEntry OBJECT-TYPE
SYNTAX DsClfrElementEntry
STATUS current
DESCRIPTION
"An entry in the classifier element table describes a
single element of the classifier."
PIB-INDEX { dsClfrElementPrid }
UNIQUENESS { dsClfrElementClfrId,
dsClfrElementPrecedence,
dsClfrElementSpecific }
::= { dsClfrElementTable 1 }
dsClfrElementEntry OBJECT-TYPE
SYNTAX DsClfrElementEntry
STATUS current
DESCRIPTION
"An entry in the classifier element table describes a
single element of the classifier."
PIB-INDEX { dsClfrElementPrid }
UNIQUENESS { dsClfrElementClfrId,
dsClfrElementPrecedence,
dsClfrElementSpecific }
::= { dsClfrElementTable 1 }
DsClfrElementEntry ::= SEQUENCE {
dsClfrElementPrid InstanceId,
dsClfrElementClfrId TagId,
dsClfrElementPrecedence Unsigned32,
dsClfrElementNext Prid,
dsClfrElementSpecific Prid
}
DsClfrElementEntry ::= SEQUENCE {
dsClfrElementPrid InstanceId,
dsClfrElementClfrId TagId,
dsClfrElementPrecedence Unsigned32,
dsClfrElementNext Prid,
dsClfrElementSpecific Prid
}
dsClfrElementPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsClfrElementEntry 1 }
dsClfrElementPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsClfrElementEntry 1 }
dsClfrElementClfrId OBJECT-TYPE SYNTAX TagId STATUS current DESCRIPTION "A classifier is composed of one or more classifier elements. Each classifier element belonging to the same classifier uses the same classifier ID.
dsClfrElementClfrId对象类型语法TagId STATUS current DESCRIPTION“分类器由一个或多个分类器元素组成。属于同一分类器的每个分类器元素使用相同的分类器ID。
Hence, A classifier Id identifies which classifier
this classifier element is a part of. This must be
the value of dsClfrId attribute for an existing
instance of dsClfrEntry."
::= { dsClfrElementEntry 2 }
Hence, A classifier Id identifies which classifier
this classifier element is a part of. This must be
the value of dsClfrId attribute for an existing
instance of dsClfrEntry."
::= { dsClfrElementEntry 2 }
dsClfrElementPrecedence OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295)
DSCLFRelementPreference对象类型语法Unsigned32（1..4294967295）
STATUS current DESCRIPTION "The relative order in which classifier elements are applied: higher numbers represent classifier elements with higher precedence. Classifier elements with the same precedence must be unambiguous i.e., they must define non-overlapping patterns, and are considered to be applied simultaneously to the traffic stream. Classifier elements with different precedence may overlap in their filters: the classifier element with the highest precedence that matches is taken.
状态当前描述应用分类器元素的相对顺序：较高的数字表示具有较高优先级的分类器元素。具有相同优先级的分类器元素必须是明确的，即它们必须定义非重叠模式，并且被认为同时应用于业务流。具有不同优先级的分类器元素可能在其过滤器中重叠：采用匹配的具有最高优先级的分类器元素。
On a given interface, there must be a complete
classifier in place at all times in the ingress
direction. This means that there will always be one
or more filters that match every possible pattern
that could be presented in an incoming packet.
There is no such requirement in the egress direction."
::= { dsClfrElementEntry 3 }
On a given interface, there must be a complete
classifier in place at all times in the ingress
direction. This means that there will always be one
or more filters that match every possible pattern
that could be presented in an incoming packet.
There is no such requirement in the egress direction."
::= { dsClfrElementEntry 3 }
dsClfrElementNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This attribute provides one branch of the fan-out functionality of a classifier described in Diffserv Model section 4.1.
dsClfrElementNext对象类型语法Prid STATUS current DESCRIPTION“此属性提供Diffserv模型第4.1节中描述的分类器扇出功能的一个分支。
This selects the next diffserv functional datapath element to handle traffic for this data path.
这将选择下一个diffserv functional datapath元素来处理此数据路径的流量。
A value of zeroDotZero marks the end of DiffServ processing
for this data path. Any other value must point to a
valid (pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsClfrElementEntry 4 }
A value of zeroDotZero marks the end of DiffServ processing
for this data path. Any other value must point to a
valid (pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsClfrElementEntry 4 }
dsClfrElementSpecific OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "A pointer to a valid entry in another table that describes the applicable classification filter, e.g.,
dsClfrElementSpecific OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION“指向另一个表中描述适用分类筛选器的有效条目的指针，例如。，
an entry in frwkIpFilterTable (Framework PIB).
frwkIpFilterTable（框架PIB）中的条目。
The PRI pointed to must exist prior to the installation of this classifier element.
在安装此分类器元件之前，必须存在指向的PRI。
The value zeroDotZero is interpreted to match any-
thing not matched by another classifier element - only one
such entry may exist for each classifier."
::= { dsClfrElementEntry 5 }
The value zeroDotZero is interpreted to match any-
thing not matched by another classifier element - only one
such entry may exist for each classifier."
::= { dsClfrElementEntry 5 }
--
-- Meters
--
-- This PIB supports a variety of Meters. It includes a
-- specific definition for Meters whose parameter set can
-- be modeled using Token Bucket parameters.
-- Other metering parameter sets can be defined by other PIBs.
--
-- Multiple meter elements may be logically cascaded
-- using their dsMeterSucceedNext and dsMeterFailNext pointers if
-- required.
-- One example of this might be for an AF PHB implementation
-- that uses multiple level conformance meters.
--
-- Cascading of individual meter elements in the PIB is intended
-- to be functionally equivalent to multiple level conformance
-- determination of a packet. The sequential nature of the
-- representation is merely a notational convenience for this PIB.
--
-- srTCM meters (RFC 2697) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Information Rate and Committed Burst Size
-- token-bucket. Second set specifies the Excess Burst
-- Size token-bucket.
--
-- trTCM meters (RFC 2698) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Information Rate and Committed Burst Size
-- token-bucket. Second set specifies the Peak Information
-- Rate and Peak Burst Size token-bucket.
--
-- tswTCM meters (RFC 2859) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Target Rate token-bucket. Second set specifies the
-- Peak Target Rate token-bucket. dsTBParamInterval in each
-- token bucket reflects the Average Interval.
--
-- Meters
--
-- This PIB supports a variety of Meters. It includes a
-- specific definition for Meters whose parameter set can
-- be modeled using Token Bucket parameters.
-- Other metering parameter sets can be defined by other PIBs.
--
-- Multiple meter elements may be logically cascaded
-- using their dsMeterSucceedNext and dsMeterFailNext pointers if
-- required.
-- One example of this might be for an AF PHB implementation
-- that uses multiple level conformance meters.
--
-- Cascading of individual meter elements in the PIB is intended
-- to be functionally equivalent to multiple level conformance
-- determination of a packet. The sequential nature of the
-- representation is merely a notational convenience for this PIB.
--
-- srTCM meters (RFC 2697) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Information Rate and Committed Burst Size
-- token-bucket. Second set specifies the Excess Burst
-- Size token-bucket.
--
-- trTCM meters (RFC 2698) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Information Rate and Committed Burst Size
-- token-bucket. Second set specifies the Peak Information
-- Rate and Peak Burst Size token-bucket.
--
-- tswTCM meters (RFC 2859) can be specified using two sets of
-- dsMeterEntry and dsTBParamEntry. First set specifies the
-- Committed Target Rate token-bucket. Second set specifies the
-- Peak Target Rate token-bucket. dsTBParamInterval in each
-- token bucket reflects the Average Interval.
dsMeterTable OBJECT-TYPE
dsMeterTable对象类型
SYNTAX SEQUENCE OF DsMeterEntry PIB-ACCESS install STATUS current DESCRIPTION "This class enumerates specific meters that a system may use to police a stream of traffic. The traffic stream to be metered is determined by the element(s) upstream of the meter i.e., by the object(s) that point to each entry in this class. This may include all traffic on an interface.
DsMeterEntry PIB-ACCESS安装状态当前描述的语法顺序“此类列举了系统可用于监控交通流的特定仪表。要计量的交通流由仪表上游的元素（即对象）确定指向此类中的每个条目的点。这可能包括接口上的所有通信量。
Specific meter details are to be found in table entry
referenced by dsMeterSpecific."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5"
::= { dsPolicyClasses 4 }
Specific meter details are to be found in table entry
referenced by dsMeterSpecific."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5"
::= { dsPolicyClasses 4 }
dsMeterEntry OBJECT-TYPE
SYNTAX DsMeterEntry
STATUS current
DESCRIPTION
"An entry in the meter table describes a single
conformance level of a meter."
PIB-INDEX { dsMeterPrid }
UNIQUENESS { dsMeterSucceedNext,
dsMeterFailNext,
dsMeterSpecific }
::= { dsMeterTable 1 }
dsMeterEntry OBJECT-TYPE
SYNTAX DsMeterEntry
STATUS current
DESCRIPTION
"An entry in the meter table describes a single
conformance level of a meter."
PIB-INDEX { dsMeterPrid }
UNIQUENESS { dsMeterSucceedNext,
dsMeterFailNext,
dsMeterSpecific }
::= { dsMeterTable 1 }
DsMeterEntry ::= SEQUENCE {
dsMeterPrid InstanceId,
dsMeterSucceedNext Prid,
dsMeterFailNext Prid,
dsMeterSpecific Prid
}
DsMeterEntry ::= SEQUENCE {
dsMeterPrid InstanceId,
dsMeterSucceedNext Prid,
dsMeterFailNext Prid,
dsMeterSpecific Prid
}
dsMeterPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMeterEntry 1 }
dsMeterPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMeterEntry 1 }
dsMeterSucceedNext OBJECT-TYPE SYNTAX Prid STATUS current
dsMeterSucceedNext对象类型语法Prid状态当前
DESCRIPTION "If the traffic does conform, this selects the next diffserv functional datapath element to handle traffic for this data path.
DESCRIPTION“如果流量不符合要求，则选择下一个diffserv functional datapath元素来处理此数据路径的流量。
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsMeterEntry 2 }
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsMeterEntry 2 }
dsMeterFailNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "If the traffic does not conform, this selects the next diffserv functional datapath element to handle traffic for this data path.
dsMeterFailNext对象类型语法Prid STATUS current DESCRIPTION“如果流量不一致，则选择下一个diffserv functional datapath元素来处理此数据路径的流量。
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsMeterEntry 3 }
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsMeterEntry 3 }
dsMeterSpecific OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This indicates the behaviour of the meter by point-ing to an entry containing detailed parameters. Note that entries in that specific table must be managed explicitly.
dsMeterSpecific对象类型语法Prid STATUS current DESCRIPTION“通过指向包含详细参数的条目来指示仪表的行为。请注意，必须明确管理该特定表格中的条目。
For example, dsMeterSpecific may point to an entry in dsTBMeterTable, which contains an
例如，dsMeterSpecific可能指向dsTBMeterTable中的一个条目，其中包含
instance of a single set of Token Bucket parameters.
一组令牌桶参数的实例。
The PRI pointed to must exist prior to installing this
Meter datapath element."
::= { dsMeterEntry 4 }
The PRI pointed to must exist prior to installing this
Meter datapath element."
::= { dsMeterEntry 4 }
--
-- Token-Bucket Parameter Table
--
-- Each entry in the Token Bucket Parameter Table parameterizes
-- a single token bucket. Multiple token buckets can be
-- used together to parameterize multiple levels of
-- conformance.
--
-- Note that an entry in the Token Bucket Parameter Table can
-- be shared, pointed to, by multiple dsMeterTable entries.
--
--
-- Token-Bucket Parameter Table
--
-- Each entry in the Token Bucket Parameter Table parameterizes
-- a single token bucket. Multiple token buckets can be
-- used together to parameterize multiple levels of
-- conformance.
--
-- Note that an entry in the Token Bucket Parameter Table can
-- be shared, pointed to, by multiple dsMeterTable entries.
--
dsTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsTBParamEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"This table enumerates token-bucket meter parameter sets
that a system may use to police a stream of traffic.
Such parameter sets are modelled here as each having a single
rate and a single burst size. Multiple entries are used
when multiple rates/burst sizes are needed."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5.1"
::= { dsPolicyClasses 5 }
dsTBParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsTBParamEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"This table enumerates token-bucket meter parameter sets
that a system may use to police a stream of traffic.
Such parameter sets are modelled here as each having a single
rate and a single burst size. Multiple entries are used
when multiple rates/burst sizes are needed."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5.1"
::= { dsPolicyClasses 5 }
dsTBParamEntry OBJECT-TYPE
SYNTAX DsTBParamEntry
STATUS current
DESCRIPTION
"An entry that describes a single token-bucket
parameter set."
PIB-INDEX { dsTBParamPrid }
UNIQUENESS { dsTBParamType,
dsTBParamRate,
dsTBParamBurstSize,
dsTBParamInterval }
::= { dsTBParamTable 1 }
dsTBParamEntry OBJECT-TYPE
SYNTAX DsTBParamEntry
STATUS current
DESCRIPTION
"An entry that describes a single token-bucket
parameter set."
PIB-INDEX { dsTBParamPrid }
UNIQUENESS { dsTBParamType,
dsTBParamRate,
dsTBParamBurstSize,
dsTBParamInterval }
::= { dsTBParamTable 1 }
DsTBParamEntry ::= SEQUENCE {
dsTBParamPrid InstanceId,
DsTBParamEntry ::= SEQUENCE {
dsTBParamPrid InstanceId,
dsTBParamType AutonomousType, dsTBParamRate Unsigned32, dsTBParamBurstSize BurstSize, dsTBParamInterval Unsigned32 }
dsTBParamType自治类型，dsTBParamRate Unsigned32，dsTBParamBurstSize BurstSize，dsTBParamInterval Unsigned32}
dsTBParamPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsTBParamEntry 1 }
dsTBParamPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsTBParamEntry 1 }
dsTBParamType OBJECT-TYPE SYNTAX AutonomousType STATUS current DESCRIPTION "The Metering algorithm associated with the Token-Bucket parameters. zeroDotZero indicates this is unknown.
dsTBParamType对象类型语法AutonomousType状态当前描述“与令牌桶参数关联的计量算法。zeroDotZero表示这是未知的。
Standard values for generic algorithms are as follows:
通用算法的标准值如下：
diffServTBParamSimpleTokenBucket, diffServTBParamAvgRate, diffServTBParamSrTCMBlind, diffServTBParamSrTCMAware, diffServTBParamTrTCMBlind, diffServTBParamTrTCMAware, diffServTBParamTswTCM
diffServTBParamSimpleTokenBucket、diffServTBParamAvgRate、DiffServTbParamsRtcmBind、DiffServTbParamsRtcmWare、DiffServTbParamtRtcmBind、DiffServTbParamtRtcmWare、diffServTBParamTswTCM
These are specified in the DiffServ MIB."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5.1"
::= { dsTBParamEntry 2 }
These are specified in the DiffServ MIB."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 5.1"
::= { dsTBParamEntry 2 }
dsTBParamRate OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "kilobits per second"
STATUS current
DESCRIPTION
"The token-bucket rate, in kilobits per second
(kbps). This attribute is used for:
1. CIR in RFC 2697 for srTCM
2. CIR and PIR in RFC 2698 for trTCM
3. CTR and PTR in RFC 2859 for TSWTCM
4. AverageRate in RFC 3290, section 5.1.1"
::= { dsTBParamEntry 3 }
dsTBParamRate OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "kilobits per second"
STATUS current
DESCRIPTION
"The token-bucket rate, in kilobits per second
(kbps). This attribute is used for:
1. CIR in RFC 2697 for srTCM
2. CIR and PIR in RFC 2698 for trTCM
3. CTR and PTR in RFC 2859 for TSWTCM
4. AverageRate in RFC 3290, section 5.1.1"
::= { dsTBParamEntry 3 }
dsTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
STATUS current
DESCRIPTION
"The maximum number of bytes in a single transmission
burst. This attribute is used for:
1. CBS and EBS in RFC 2697 for srTCM
2. CBS and PBS in RFC 2698 for trTCM
3. Burst Size in RFC 3290, section 5."
::= { dsTBParamEntry 4 }
dsTBParamBurstSize OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
STATUS current
DESCRIPTION
"The maximum number of bytes in a single transmission
burst. This attribute is used for:
1. CBS and EBS in RFC 2697 for srTCM
2. CBS and PBS in RFC 2698 for trTCM
3. Burst Size in RFC 3290, section 5."
::= { dsTBParamEntry 4 }
dsTBParamInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "microseconds"
STATUS current
DESCRIPTION
"The time interval used with the token bucket. For:
1. Average Rate Meter, RFC 3290, section 5.1.1,
-Delta.
2. Simple Token Bucket Meter, RFC 3290, section
5.1.3, - time interval t.
3. RFC 2859 TSWTCM, - AVG_INTERVAL.
4. RFC 2697 srTCM, RFC 2698 trTCM, - token
bucket update time interval."
::= { dsTBParamEntry 5 }
dsTBParamInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "microseconds"
STATUS current
DESCRIPTION
"The time interval used with the token bucket. For:
1. Average Rate Meter, RFC 3290, section 5.1.1,
-Delta.
2. Simple Token Bucket Meter, RFC 3290, section
5.1.3, - time interval t.
3. RFC 2859 TSWTCM, - AVG_INTERVAL.
4. RFC 2697 srTCM, RFC 2698 trTCM, - token
bucket update time interval."
::= { dsTBParamEntry 5 }
-- -- Actions --
----行动--
--
-- The Action Table allows enumeration of the different
-- types of actions to be applied to a traffic flow.
--
--
-- The Action Table allows enumeration of the different
-- types of actions to be applied to a traffic flow.
--
dsActionTable OBJECT-TYPE SYNTAX SEQUENCE OF DsActionEntry PIB-ACCESS install STATUS current DESCRIPTION "The Action Table enumerates actions that can be per-formed to a stream of traffic. Multiple actions can be concatenated.
dsActionTable对象类型DsActionEntry PIB-ACCESS的语法序列安装状态当前描述“操作表枚举可以形成流量流的操作。可以连接多个操作。
Specific actions are indicated by dsAction-Specific which points to an entry of a specific action type parameterizing the action in detail."
特定操作由dsAction Specific表示，它指向一个特定操作类型的条目，该条目详细参数化了操作。”
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 6."
::= { dsPolicyClasses 6 }
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 6."
::= { dsPolicyClasses 6 }
dsActionEntry OBJECT-TYPE
SYNTAX DsActionEntry
STATUS current
DESCRIPTION
"Each entry in the action table allows description of
one specific action to be applied to traffic."
PIB-INDEX { dsActionPrid }
UNIQUENESS { dsActionNext,
dsActionSpecific }
::= { dsActionTable 1 }
dsActionEntry OBJECT-TYPE
SYNTAX DsActionEntry
STATUS current
DESCRIPTION
"Each entry in the action table allows description of
one specific action to be applied to traffic."
PIB-INDEX { dsActionPrid }
UNIQUENESS { dsActionNext,
dsActionSpecific }
::= { dsActionTable 1 }
DsActionEntry ::= SEQUENCE {
dsActionPrid InstanceId,
dsActionNext Prid,
dsActionSpecific Prid
}
DsActionEntry ::= SEQUENCE {
dsActionPrid InstanceId,
dsActionNext Prid,
dsActionSpecific Prid
}
dsActionPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsActionEntry 1 }
dsActionPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsActionEntry 1 }
dsActionNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This selects the next diffserv functional datapath element to handle traffic for this data path.
dsActionNext对象类型语法Prid STATUS current DESCRIPTION“此选项选择下一个diffserv functional datapath元素来处理此数据路径的流量。
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsActionEntry 2 }
The value zeroDotZero in this variable indicates no
further DiffServ treatment is performed on traffic of
this datapath. Any other value must point to a valid
(pre-existing) instance of one of:
dsClfrEntry
dsMeterEntry
dsActionEntry
dsAlgDropEntry
dsQEntry."
DEFVAL { zeroDotZero }
::= { dsActionEntry 2 }
dsActionSpecific OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "A pointer to an object instance providing additional information for the type of action indicated by this action table entry.
dsActionSpecific OBJECT-TYPE语法Prid STATUS current DESCRIPTION“指向对象实例的指针，该对象实例提供此操作表项指示的操作类型的附加信息。
For the standard actions defined by this PIB module, this should point to an instance of dsDscpMarkActEntry. For other actions, it may point to an instance of a PRC defined in some other PIB.
对于此PIB模块定义的标准操作，应指向DSCPMARKACTENTRY的实例。对于其他行动，它可能指向其他PIB中定义的PRC实例。
The PRI pointed to must exist prior to installing this
action datapath entry."
::= { dsActionEntry 3 }
The PRI pointed to must exist prior to installing this
action datapath entry."
::= { dsActionEntry 3 }
-- DSCP Mark Action Table
--
-- Rows of this class are pointed to by dsActionSpecific
-- to provide detailed parameters specific to the DSCP
-- Mark action.
-- This class should at most contain one entry for each supported
-- DSCP value. These entries should be reused by different
-- dsActionEntry in same or different data paths.
--
-- DSCP Mark Action Table
--
-- Rows of this class are pointed to by dsActionSpecific
-- to provide detailed parameters specific to the DSCP
-- Mark action.
-- This class should at most contain one entry for each supported
-- DSCP value. These entries should be reused by different
-- dsActionEntry in same or different data paths.
--
dsDscpMarkActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsDscpMarkActEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"This class enumerates specific DSCPs used for marking or
remarking the DSCP field of IP packets. The entries of this
table may be referenced by a dsActionSpecific attribute."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 6.1"
::= { dsPolicyClasses 7 }
dsDscpMarkActTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsDscpMarkActEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"This class enumerates specific DSCPs used for marking or
remarking the DSCP field of IP packets. The entries of this
table may be referenced by a dsActionSpecific attribute."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 6.1"
::= { dsPolicyClasses 7 }
dsDscpMarkActEntry OBJECT-TYPE SYNTAX DsDscpMarkActEntry STATUS current DESCRIPTION "An entry in the DSCP mark action table that describes a single DSCP used for marking." PIB-INDEX { dsDscpMarkActPrid }
DSCPMARKACTENTRY对象类型语法DSCPMARKACTENTRY STATUS current DESCRIPTION“DSCP标记操作表中描述用于标记的单个DSCP的条目。”PIB-INDEX{DSCPMARKACTPRID}
UNIQUENESS { dsDscpMarkActDscp }
::= { dsDscpMarkActTable 1 }
UNIQUENESS { dsDscpMarkActDscp }
::= { dsDscpMarkActTable 1 }
DsDscpMarkActEntry ::= SEQUENCE {
dsDscpMarkActPrid InstanceId,
dsDscpMarkActDscp Dscp
}
DsDscpMarkActEntry ::= SEQUENCE {
dsDscpMarkActPrid InstanceId,
dsDscpMarkActDscp Dscp
}
dsDscpMarkActPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsDscpMarkActEntry 1 }
dsDscpMarkActPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsDscpMarkActEntry 1 }
dsDscpMarkActDscp OBJECT-TYPE
SYNTAX Dscp
STATUS current
DESCRIPTION
"The DSCP that this Action uses for marking/remarking
traffic. Note that a DSCP value of -1 is not permit-
ted in this class. It is quite possible that the
only packets subject to this Action are already
marked with this DSCP. Note also that DiffServ may
result in packet remarking both on ingress to a net-
work and on egress from it and it is quite possible
that ingress and egress would occur in the same
router."
::= { dsDscpMarkActEntry 2 }
dsDscpMarkActDscp OBJECT-TYPE
SYNTAX Dscp
STATUS current
DESCRIPTION
"The DSCP that this Action uses for marking/remarking
traffic. Note that a DSCP value of -1 is not permit-
ted in this class. It is quite possible that the
only packets subject to this Action are already
marked with this DSCP. Note also that DiffServ may
result in packet remarking both on ingress to a net-
work and on egress from it and it is quite possible
that ingress and egress would occur in the same
router."
::= { dsDscpMarkActEntry 2 }
-- -- Algorithmic Drop Table --
----算法删除表--
-- Algorithmic Drop Table is the entry point for the Algorithmic
-- Dropper functional data path element.
-- Algorithmic Drop Table is the entry point for the Algorithmic
-- Dropper functional data path element.
-- For a simple algorithmic dropper, a single algorithmic drop entry
-- will be sufficient to parameterize the dropper.
-- For a simple algorithmic dropper, a single algorithmic drop entry
-- will be sufficient to parameterize the dropper.
-- For more complex algorithmic dropper, the dsAlgDropSpecific
-- attribute can be used to reference an entry in a parameter table,
-- e.g., dsRandomDropTable for random dropper.
-- For more complex algorithmic dropper, the dsAlgDropSpecific
-- attribute can be used to reference an entry in a parameter table,
-- e.g., dsRandomDropTable for random dropper.
-- For yet more complex dropper, for example, dropper that measures
-- multiple queues, each queue with its own algorithm, can use a
-- dsAlgDropTable entry as the entry point for Algorithmic Dropper
-- For yet more complex dropper, for example, dropper that measures
-- multiple queues, each queue with its own algorithm, can use a
-- dsAlgDropTable entry as the entry point for Algorithmic Dropper
-- functional data path element, leaving the dropper parameters
-- for each queue be specified by entries of dsMQAlgDropTable.
-- In such usage, the anchoring dsAlgDropEntry's dsAlgDropType
-- should be mQDrop, and its dsAlgDropQMeasure should reference
-- the subsequent dsMQAlgDropEntry's, its dsAlgDropSpecific
-- should be used to reference parameters applicable to all the
-- queues being measured.
-- The subsequent dsMQAlgDropEntry's will provide the parameters,
-- one for each queue being measured. The dsMQAlgDropEntry's are
-- chained using their dsMQAlgDropNext attributes.
--
-- functional data path element, leaving the dropper parameters
-- for each queue be specified by entries of dsMQAlgDropTable.
-- In such usage, the anchoring dsAlgDropEntry's dsAlgDropType
-- should be mQDrop, and its dsAlgDropQMeasure should reference
-- the subsequent dsMQAlgDropEntry's, its dsAlgDropSpecific
-- should be used to reference parameters applicable to all the
-- queues being measured.
-- The subsequent dsMQAlgDropEntry's will provide the parameters,
-- one for each queue being measured. The dsMQAlgDropEntry's are
-- chained using their dsMQAlgDropNext attributes.
--
dsAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsAlgDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The algorithmic drop table contains entries describ-
ing a functional data path element that drops
packets according to some algorithm."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.3"
::= { dsPolicyClasses 8 }
dsAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsAlgDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The algorithmic drop table contains entries describ-
ing a functional data path element that drops
packets according to some algorithm."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.3"
::= { dsPolicyClasses 8 }
dsAlgDropEntry OBJECT-TYPE
SYNTAX DsAlgDropEntry
STATUS current
DESCRIPTION
"An entry describes a process that drops packets
according to some algorithm. Further details of the
algorithm type are to be found in dsAlgDropType
and with more detail parameter entry pointed to by
dsAlgDropSpecific when necessary."
PIB-INDEX { dsAlgDropPrid }
UNIQUENESS { dsAlgDropType,
dsAlgDropNext,
dsAlgDropQMeasure,
dsAlgDropQThreshold,
dsAlgDropSpecific }
::= { dsAlgDropTable 1 }
dsAlgDropEntry OBJECT-TYPE
SYNTAX DsAlgDropEntry
STATUS current
DESCRIPTION
"An entry describes a process that drops packets
according to some algorithm. Further details of the
algorithm type are to be found in dsAlgDropType
and with more detail parameter entry pointed to by
dsAlgDropSpecific when necessary."
PIB-INDEX { dsAlgDropPrid }
UNIQUENESS { dsAlgDropType,
dsAlgDropNext,
dsAlgDropQMeasure,
dsAlgDropQThreshold,
dsAlgDropSpecific }
::= { dsAlgDropTable 1 }
DsAlgDropEntry ::= SEQUENCE {
dsAlgDropPrid InstanceId,
dsAlgDropType INTEGER,
dsAlgDropNext Prid,
dsAlgDropQMeasure Prid,
dsAlgDropQThreshold Unsigned32,
DsAlgDropEntry ::= SEQUENCE {
dsAlgDropPrid InstanceId,
dsAlgDropType INTEGER,
dsAlgDropNext Prid,
dsAlgDropQMeasure Prid,
dsAlgDropQThreshold Unsigned32,
dsAlgDropSpecific Prid }
dsAlgDropSpecific Prid}
dsAlgDropPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsAlgDropEntry 1 }
dsAlgDropPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsAlgDropEntry 1 }
dsAlgDropType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5),
mQDrop(6)
}
STATUS current
DESCRIPTION
"The type of algorithm used by this dropper. A value
of tailDrop(2), headDrop(3), or alwaysDrop(5) represents
an algorithm that is completely specified by this PIB.
dsAlgDropType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
tailDrop(2),
headDrop(3),
randomDrop(4),
alwaysDrop(5),
mQDrop(6)
}
STATUS current
DESCRIPTION
"The type of algorithm used by this dropper. A value
of tailDrop(2), headDrop(3), or alwaysDrop(5) represents
an algorithm that is completely specified by this PIB.
A value of other(1) indicates that the specifics of the drop algorithm are specified in some other PIB module, and that the dsAlgDropSpecific attribute points to an instance of a PRC in that PIB that specifies the information necessary to implement the algorithm.
值other（1）表示drop算法的细节在其他一些PIB模块中指定，并且dsAlgDropSpecific属性指向该PIB中PRC的实例，该实例指定实现算法所需的信息。
The tailDrop(2) algorithm is described as follows: dsAlgDropQThreshold represents the depth of the queue, pointed to by dsAlgDropQMeasure, at which all newly arriving packets will be dropped.
tailDrop（2）算法描述如下：dsAlgDropQThreshold表示由dsAlgDropQMeasure指向的队列深度，在该深度处，将丢弃所有新到达的数据包。
The headDrop(3) algorithm is described as follows: if a packet arrives when the current depth of the queue, pointed to by dsAlgDropQMeasure, is at dsAlgDropQThreshold, packets currently at the head of the queue are dropped to make room for the new packet to be enqueued at the tail of the queue.
headDrop（3）算法描述如下：如果当dsAlgDropQMeasure指向的队列的当前深度处于dsAlgDropQThreshold时，数据包到达，则丢弃当前位于队列头部的数据包，以便为在队列尾部排队的新数据包腾出空间。
The randomDrop(4) algorithm is described as follows: on packet arrival, an algorithm is executed which may randomly drop the packet, or drop other packet(s)
随机丢弃（4）算法描述如下：在数据包到达时，执行一个算法，该算法可以随机丢弃该数据包，或者丢弃其他数据包
from the queue in its place. The specifics of the algorithm may be proprietary. For this algorithm, dsAlgDropSpecific points to a dsRandomDropEntry that describes the algorithm. For this algorithm, dsAlgQThreshold is understood to be the absolute maximum size of the queue and additional parameters are described in dsRandomDropTable.
从队列中取出。算法的细节可能是专有的。对于此算法，dsAlgDropSpecific指向描述该算法的dsRandomDropEntry。对于该算法，dsAlgQThreshold被理解为队列的绝对最大大小，其他参数在dsRandomDropTable中描述。
The alwaysDrop(5) algorithm always drops packets. In this case, the other configuration values in this Entry are not meaningful; The queue is not used, therefore, dsAlgDropNext, dsAlgDropQMeasure, and dsAlgDropSpecific should be all set to zeroDotZero.
alwaysDrop（5）算法总是丢弃数据包。在这种情况下，该条目中的其他配置值没有意义；不使用队列，因此，dsAlgDropNext、dsAlgDropQMeasure和dsAlgDropSpecific都应设置为zeroDotZero。
The mQDrop(6) algorithm measures multiple queues for the drop algorithm. The queues measured are represented by having dsAlgDropQMeasure referencing a dsMQAlgDropEntry. Each of the chained dsMQAlgDropEntry is used to describe the drop algorithm for one of the measured queues."
mQDrop（6）算法为drop算法测量多个队列。测量的队列由dsAlgDropQMeasure引用DSMQALGDROPQMENTRY表示。每个链式dsMQAlgDropEntry用于描述一个测量队列的丢弃算法。”
::= { dsAlgDropEntry 2 }
::= { dsAlgDropEntry 2 }
dsAlgDropNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This selects the next diffserv functional datapath element to handle traffic for this data path.
dsAlgDropNext对象类型语法Prid STATUS current DESCRIPTION“这将选择下一个diffserv functional datapath元素来处理此数据路径的流量。
The value zeroDotZero in this attribute indicates no further DiffServ treatment is performed on traffic of this datapath. Any other value must point to a valid (pre-existing) instance of one of: dsClfrEntry dsMeterEntry dsActionEntry dsAlgDropEntry dsQEntry.
此属性中的值zeroDotZero表示不对此数据路径的流量执行进一步的区分服务处理。任何其他值都必须指向以下之一的有效（预先存在）实例：dsClfrEntry dsMeterEntry dsActionEntry dsalgdroperty dsQEntry。
When dsAlgDropType is alwaysDrop(5), this attribute is
Ignored."
DEFVAL { zeroDotZero }
::= { dsAlgDropEntry 3 }
When dsAlgDropType is alwaysDrop(5), this attribute is
Ignored."
DEFVAL { zeroDotZero }
::= { dsAlgDropEntry 3 }
dsAlgDropQMeasure OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION
dsAlgDropQMeasure对象类型语法Prid状态当前说明
"Points to a PRI to indicate the queues that a drop algorithm is to monitor when deciding whether to drop a packet.
指向PRI，以指示丢弃算法在决定是否丢弃数据包时要监视的队列。
For alwaysDrop(5), this attribute should be zeroDotZero. For tailDrop(2), headDrop(3), randomDrop(4), this should point to an entry in the dsQTable. For mQDrop(6), this should point to a dsMQAlgDropEntry that Describe one of the queues being measured for multiple queue dropper.
对于alwaysDrop（5），此属性应为zeroDotZero。对于尾降（2）、头降（3）、随机降（4），这应指向dsQTable中的一个条目。对于mQDrop（6），这应该指向一个dsMQAlgDropEntry，它描述了为多个队列拖放器测量的一个队列。
The PRI pointed to must exist prior to installing
this dropper element."
::= { dsAlgDropEntry 4 }
The PRI pointed to must exist prior to installing
this dropper element."
::= { dsAlgDropEntry 4 }
dsAlgDropQThreshold OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "Bytes" STATUS current DESCRIPTION "A threshold on the depth in bytes of the queue being measured at which a trigger is generated to the drop-ping algorithm, unless dsAlgDropType is alwaysDrop(5) where this attribute is ignored.
dsAlgDropQThreshold对象类型语法Unsigned32（1..4294967295）单位“Bytes”状态当前描述“在对drop ping算法生成触发器时测量的队列的字节深度阈值，除非dsAlgDropType始终是忽略此属性的drop（5）。
For the tailDrop(2) or headDrop(3) algorithms, this
represents the depth of the queue, pointed to by
dsAlgDropQMeasure, at which the drop action
will take place. Other algorithms will need to define
their own semantics for this threshold."
::= { dsAlgDropEntry 5 }
For the tailDrop(2) or headDrop(3) algorithms, this
represents the depth of the queue, pointed to by
dsAlgDropQMeasure, at which the drop action
will take place. Other algorithms will need to define
their own semantics for this threshold."
::= { dsAlgDropEntry 5 }
dsAlgDropSpecific OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "Points to a table entry that provides further detail regarding a drop algorithm. The PRI pointed to must exist prior to installing this dropper element.
dsAlgDropSpecific对象类型语法PRI STATUS current DESCRIPTION”指向一个表项，该表项提供有关drop算法的更多详细信息。在安装此DROPER元素之前，指向的PRI必须存在。
Entries with dsAlgDropType equal to other(1) must have this point to an instance of a PRC defined in another PIB module.
dsAlgDropType等于other（1）的条目必须具有指向另一PIB模块中定义的PRC实例的该点。
Entries with dsAlgDropType equal to random-Drop(4) must have this point to an entry in dsRandomDropTable.
dsAlgDropType等于random Drop（4）的条目必须具有指向dsRandomDropTable中某个条目的该点。
Entries with dsAlgDropType equal to mQDrop(6) can use this
dsAlgDropType等于mQDrop（6）的条目可以使用
attribute to reference parameters that is used by all the queues of the multiple queues being measured.
属性以引用被测量的多个队列的所有队列使用的参数。
For all other algorithms, this should take the value
zeroDotZero."
::= { dsAlgDropEntry 6 }
For all other algorithms, this should take the value
zeroDotZero."
::= { dsAlgDropEntry 6 }
--
-- Multiple Queue Algorithmic Drop Table
--
-- Entries of this table should be referenced by dsAlgDropQMeasure
-- when dsAlgDropType is mQDrop(6) for droppers measuring multiple
-- queues for its drop algorithm.
-- Each entry of the table is used to describe the drop algorithm
-- for a single queue within the multiple queues being measured.
--
-- Entries of this table, dsMQAlgDropEntry, is extended from
-- dsAlgDropEntry, with usage of corresponding parameters the same
-- except:
-- dsAlgDropNext is used to point to the next diffserv
-- functional data path element when the packet is not dropped.
-- dsMQAlgDropExceedNext is used to point to the next
-- dsMQAlgDropEntry for chaining together the multiple
-- dsMQAlgDropEntry's for the multiple queues being measured.
--
--
-- Multiple Queue Algorithmic Drop Table
--
-- Entries of this table should be referenced by dsAlgDropQMeasure
-- when dsAlgDropType is mQDrop(6) for droppers measuring multiple
-- queues for its drop algorithm.
-- Each entry of the table is used to describe the drop algorithm
-- for a single queue within the multiple queues being measured.
--
-- Entries of this table, dsMQAlgDropEntry, is extended from
-- dsAlgDropEntry, with usage of corresponding parameters the same
-- except:
-- dsAlgDropNext is used to point to the next diffserv
-- functional data path element when the packet is not dropped.
-- dsMQAlgDropExceedNext is used to point to the next
-- dsMQAlgDropEntry for chaining together the multiple
-- dsMQAlgDropEntry's for the multiple queues being measured.
--
dsMQAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsMQAlgDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The multiple queue algorithmic drop table contains entries
describing each queue being measured for the multiple queue
algorithmic dropper."
::= { dsPolicyClasses 9 }
dsMQAlgDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsMQAlgDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The multiple queue algorithmic drop table contains entries
describing each queue being measured for the multiple queue
algorithmic dropper."
::= { dsPolicyClasses 9 }
dsMQAlgDropEntry OBJECT-TYPE SYNTAX DsMQAlgDropEntry STATUS current DESCRIPTION "An entry describes a process that drops packets according to some algorithm. Each entry is used for each of the multiple queues being measured. Each entry extends the basic dsAlgDropEntry with adding of a dsMQAlgDropExceedNext attribute.
dsMQAlgDropEntry对象类型语法dsMQAlgDropEntry STATUS current DESCRIPTION“条目描述根据某种算法丢弃数据包的过程。每个条目用于所测量的多个队列中的每个队列。每个条目通过添加DSMQALGDropeExceedNext属性扩展基本dsAlgDropEntry。
Further details of the algorithm type are to be found in dsAlgDropType and with more detail parameter entry pointed
有关算法类型的更多详细信息，请参见dsAlgDropType，并指出更详细的参数输入
to by dsMQAlgDropSpecific when necessary."
EXTENDS { dsAlgDropEntry }
UNIQUENESS { dsMQAlgDropExceedNext }
::= { dsMQAlgDropTable 1 }
to by dsMQAlgDropSpecific when necessary."
EXTENDS { dsAlgDropEntry }
UNIQUENESS { dsMQAlgDropExceedNext }
::= { dsMQAlgDropTable 1 }
DsMQAlgDropEntry ::= SEQUENCE {
dsMQAlgDropExceedNext Prid
}
DsMQAlgDropEntry ::= SEQUENCE {
dsMQAlgDropExceedNext Prid
}
dsMQAlgDropExceedNext OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"Used for linking of multiple dsMQAlgDropEntry for mQDrop.
A value of zeroDotZero indicates this is the last of a
chain of dsMQAlgDropEntry."
DEFVAL { zeroDotZero }
::= { dsMQAlgDropEntry 1 }
dsMQAlgDropExceedNext OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"Used for linking of multiple dsMQAlgDropEntry for mQDrop.
A value of zeroDotZero indicates this is the last of a
chain of dsMQAlgDropEntry."
DEFVAL { zeroDotZero }
::= { dsMQAlgDropEntry 1 }
-- -- Random Drop Table --
----随机下降表--
dsRandomDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsRandomDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The random drop table contains entries describing a
process that drops packets randomly. Entries in this
table is intended to be pointed to by dsAlgDropSpecific
when dsAlgDropType is randomDrop(4)."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.3"
::= { dsPolicyClasses 10 }
dsRandomDropTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsRandomDropEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The random drop table contains entries describing a
process that drops packets randomly. Entries in this
table is intended to be pointed to by dsAlgDropSpecific
when dsAlgDropType is randomDrop(4)."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.3"
::= { dsPolicyClasses 10 }
dsRandomDropEntry OBJECT-TYPE SYNTAX DsRandomDropEntry STATUS current DESCRIPTION "An entry describes a process that drops packets according to a random algorithm." PIB-INDEX { dsRandomDropPrid } UNIQUENESS { dsRandomDropMinThreshBytes, dsRandomDropMinThreshPkts, dsRandomDropMaxThreshBytes, dsRandomDropMaxThreshPkts,
dsRandomDropEntry对象类型语法dsRandomDropEntry状态当前描述“条目描述根据随机算法丢弃数据包的过程。”PIB-INDEX{dsRandomDropPrid}唯一性{dsRandomDropMinThreshBytes，dsRandomDropMinThreshPkts，dsRandomDropMaxThreshBytes，dsRandomDropMaxThreshPkts，
dsRandomDropProbMax,
dsRandomDropWeight,
dsRandomDropSamplingRate
}
::= { dsRandomDropTable 1 }
dsRandomDropProbMax,
dsRandomDropWeight,
dsRandomDropSamplingRate
}
::= { dsRandomDropTable 1 }
DsRandomDropEntry ::= SEQUENCE {
dsRandomDropPrid InstanceId,
dsRandomDropMinThreshBytes Unsigned32,
dsRandomDropMinThreshPkts Unsigned32,
dsRandomDropMaxThreshBytes Unsigned32,
dsRandomDropMaxThreshPkts Unsigned32,
dsRandomDropProbMax Unsigned32,
dsRandomDropWeight Unsigned32,
dsRandomDropSamplingRate Unsigned32
}
DsRandomDropEntry ::= SEQUENCE {
dsRandomDropPrid InstanceId,
dsRandomDropMinThreshBytes Unsigned32,
dsRandomDropMinThreshPkts Unsigned32,
dsRandomDropMaxThreshBytes Unsigned32,
dsRandomDropMaxThreshPkts Unsigned32,
dsRandomDropProbMax Unsigned32,
dsRandomDropWeight Unsigned32,
dsRandomDropSamplingRate Unsigned32
}
dsRandomDropPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsRandomDropEntry 1 }
dsRandomDropPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsRandomDropEntry 1 }
dsRandomDropMinThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "bytes"
STATUS current
DESCRIPTION
"The average queue depth in bytes, beyond which traffic has a
non-zero probability of being dropped."
::= { dsRandomDropEntry 2 }
dsRandomDropMinThreshBytes OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "bytes"
STATUS current
DESCRIPTION
"The average queue depth in bytes, beyond which traffic has a
non-zero probability of being dropped."
::= { dsRandomDropEntry 2 }
dsRandomDropMinThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
STATUS current
DESCRIPTION
"The average queue depth in packets, beyond which traffic has
a non-zero probability of being dropped."
::= { dsRandomDropEntry 3 }
dsRandomDropMinThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
STATUS current
DESCRIPTION
"The average queue depth in packets, beyond which traffic has
a non-zero probability of being dropped."
::= { dsRandomDropEntry 3 }
dsRandomDropMaxThreshBytes OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "bytes" STATUS current DESCRIPTION
dsRandomDropMaxThreshBytes对象类型语法Unsigned32（1..4294967295）单位“字节”状态当前说明
"The average queue depth beyond which traffic has a
probability indicated by dsRandomDropProbMax of being dropped
or marked. Note that this differs from the physical queue
limit, which is stored in dsAlgDropQThreshold."
::= { dsRandomDropEntry 4 }
"The average queue depth beyond which traffic has a
probability indicated by dsRandomDropProbMax of being dropped
or marked. Note that this differs from the physical queue
limit, which is stored in dsAlgDropQThreshold."
::= { dsRandomDropEntry 4 }
dsRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a
probability indicated by dsRandomDropProbMax of being dropped
or marked. Note that this differs from the physical queue
limit, which is stored in dsAlgDropQThreshold."
::= { dsRandomDropEntry 5 }
dsRandomDropMaxThreshPkts OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
UNITS "packets"
STATUS current
DESCRIPTION
"The average queue depth beyond which traffic has a
probability indicated by dsRandomDropProbMax of being dropped
or marked. Note that this differs from the physical queue
limit, which is stored in dsAlgDropQThreshold."
::= { dsRandomDropEntry 5 }
dsRandomDropProbMax OBJECT-TYPE SYNTAX Unsigned32 (0..1000) STATUS current DESCRIPTION "The worst case random drop probability, expressed in drops per thousand packets.
dsRandomDropProbMax对象类型语法Unsigned32（0..1000）状态当前描述“最坏情况下的随机丢弃概率，以每千个数据包的丢弃数表示。
For example, if every packet may be dropped in the worst case
(100%), this has the value 1000. Alternatively, if in the
worst case one percent (1%) of traffic may be dropped, it has
the value 10."
::= { dsRandomDropEntry 6 }
For example, if every packet may be dropped in the worst case
(100%), this has the value 1000. Alternatively, if in the
worst case one percent (1%) of traffic may be dropped, it has
the value 10."
::= { dsRandomDropEntry 6 }
dsRandomDropWeight OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) STATUS current DESCRIPTION "The weighting of past history in affecting the Exponentially Weighted Moving Average function which calculates the current average queue depth. The equation uses dsRandomDropWeight/MaxValue as the coefficient for the new sample in the equation, and (MaxValue - dsRandomDropWeight)/MaxValue as the coefficient of the old value, where, MaxValue is determined via capability reported by the PEP.
dsRandomDropWeight对象类型语法Unsigned32（0..4294967295）STATUS current DESCRIPTION“影响指数加权移动平均函数（计算当前平均队列深度）的过去历史的权重。该方程使用dsRandomDropWeight/MaxValue作为方程中新样本的系数，以及（MaxValue-dsRandomDropWeight）/MaxValue作为旧值的系数，其中，MaxValue通过PEP报告的能力确定。
Implementations may further limit the values of
dsRandomDropWeight via the capability tables."
::= { dsRandomDropEntry 7 }
Implementations may further limit the values of
dsRandomDropWeight via the capability tables."
::= { dsRandomDropEntry 7 }
dsRandomDropSamplingRate OBJECT-TYPE
dsRandomDropSamplingRate对象类型
SYNTAX Unsigned32 (0..1000000)
STATUS current
DESCRIPTION
"The number of times per second the queue is sampled for queue
average calculation. A value of zero means the queue is
sampled approximately each time a packet is enqueued (or
dequeued)."
::= { dsRandomDropEntry 8 }
SYNTAX Unsigned32 (0..1000000)
STATUS current
DESCRIPTION
"The number of times per second the queue is sampled for queue
average calculation. A value of zero means the queue is
sampled approximately each time a packet is enqueued (or
dequeued)."
::= { dsRandomDropEntry 8 }
-- -- Queue Table --
----队列表--
--
-- An entry of dsQTable represents a FIFO queue diffserv
-- functional data path element as described in [MODEL] section
-- 7.1.1.
-- Notice the specification of scheduling parameters for a queue
-- as part of the input to a scheduler functional data path
-- element as described in [MODEL] section 7.1.2. This allows
-- building of hierarchical queuing/scheduling.
-- A queue therefore is parameterized by:
-- 1. Which scheduler will service this queue, dsQNext.
-- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service,
-- dsQMinRate and dsQMaxRate.
--
-- Notice one or more upstream diffserv functional data path element
-- may share, point to, a dsQTable entry as described in [MODEL]
-- section 7.1.1.
--
--
-- An entry of dsQTable represents a FIFO queue diffserv
-- functional data path element as described in [MODEL] section
-- 7.1.1.
-- Notice the specification of scheduling parameters for a queue
-- as part of the input to a scheduler functional data path
-- element as described in [MODEL] section 7.1.2. This allows
-- building of hierarchical queuing/scheduling.
-- A queue therefore is parameterized by:
-- 1. Which scheduler will service this queue, dsQNext.
-- 2. How the scheduler will service this queue, with respect
-- to all the other queues the same scheduler needs to service,
-- dsQMinRate and dsQMaxRate.
--
-- Notice one or more upstream diffserv functional data path element
-- may share, point to, a dsQTable entry as described in [MODEL]
-- section 7.1.1.
--
dsQTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsQEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The Queue Table enumerates the queues."
::= { dsPolicyClasses 11 }
dsQTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsQEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The Queue Table enumerates the queues."
::= { dsPolicyClasses 11 }
dsQEntry OBJECT-TYPE SYNTAX DsQEntry STATUS current DESCRIPTION "An entry in the Queue Table describes a single queue as a functional data path element." PIB-INDEX { dsQPrid } UNIQUENESS { dsQNext,
dsQEntry对象类型语法dsQEntry STATUS current DESCRIPTION“队列表中的一个条目将单个队列描述为功能数据路径元素。”PIB-INDEX{dsQPrid}唯一性{dsQNext，
dsQMinRate,
dsQMaxRate }
::= { dsQTable 1 }
dsQMinRate,
dsQMaxRate }
::= { dsQTable 1 }
DsQEntry ::= SEQUENCE {
dsQPrid InstanceId,
dsQNext Prid,
dsQMinRate Prid,
dsQMaxRate Prid
}
DsQEntry ::= SEQUENCE {
dsQPrid InstanceId,
dsQNext Prid,
dsQMinRate Prid,
dsQMaxRate Prid
}
dsQPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsQEntry 1 }
dsQPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsQEntry 1 }
dsQNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This selects the next diffserv scheduler. This must point to a dsSchedulerEntry.
dsQNext对象类型语法Prid STATUS current DESCRIPTION“这将选择下一个diffserv调度程序。它必须指向dsSchedulerEntry。
A value of zeroDotZero in this attribute indicates an
incomplete dsQEntry instance. In such a case, the entry
has no operational effect, since it has no parameters to
give it meaning."
::= { dsQEntry 2 }
A value of zeroDotZero in this attribute indicates an
incomplete dsQEntry instance. In such a case, the entry
has no operational effect, since it has no parameters to
give it meaning."
::= { dsQEntry 2 }
dsQMinRate OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"This Prid indicates the entry in dsMinRateTable
the scheduler, pointed to by dsQNext, should use to service
this queue.
If this value is zeroDotZero
then minimum rate and priority is unspecified.
If this value is not zeroDotZero then the instance pointed to
must exist prior to installing this entry."
::= { dsQEntry 3 }
dsQMinRate OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"This Prid indicates the entry in dsMinRateTable
the scheduler, pointed to by dsQNext, should use to service
this queue.
If this value is zeroDotZero
then minimum rate and priority is unspecified.
If this value is not zeroDotZero then the instance pointed to
must exist prior to installing this entry."
::= { dsQEntry 3 }
dsQMaxRate OBJECT-TYPE SYNTAX Prid STATUS current
dsQMaxRate对象类型语法Prid状态当前
DESCRIPTION
"This Prid indicates the entry in dsMaxRateTable
the scheduler, pointed to by dsQNext, should use to service
this queue.
If this value is zeroDotZero, then the maximum rate is the
line speed of the interface.
If this value is not zeroDotZero, then the instance pointed
to must exist prior to installing this entry."
::= { dsQEntry 4 }
DESCRIPTION
"This Prid indicates the entry in dsMaxRateTable
the scheduler, pointed to by dsQNext, should use to service
this queue.
If this value is zeroDotZero, then the maximum rate is the
line speed of the interface.
If this value is not zeroDotZero, then the instance pointed
to must exist prior to installing this entry."
::= { dsQEntry 4 }
--
-- Scheduler Table
--
--
-- The Scheduler Table is used for representing packet schedulers:
-- it provides flexibility for multiple scheduling algorithms, each
-- servicing multiple queues, to be used on the same
-- logical/physical interface of a data path.
--
-- Notice the servicing parameters the scheduler uses is
-- specified by each of its upstream functional data path elements,
-- queues or schedulers of this PIB.
-- The coordination and coherency between the servicing parameters
-- of the scheduler's upstream functional data path elements must
-- be maintained for the scheduler to function correctly.
--
-- The dsSchedulerMinRate and dsSchedulerMaxRate attributes are
-- used for specifying the servicing parameters for output of a
-- scheduler when its downstream functional data path element
-- is another scheduler.
-- This is used for building hierarchical queue/scheduler.
--
-- More discussion of the scheduler functional data path element
-- is in [MODEL] section 7.1.2.
--
--
-- Scheduler Table
--
--
-- The Scheduler Table is used for representing packet schedulers:
-- it provides flexibility for multiple scheduling algorithms, each
-- servicing multiple queues, to be used on the same
-- logical/physical interface of a data path.
--
-- Notice the servicing parameters the scheduler uses is
-- specified by each of its upstream functional data path elements,
-- queues or schedulers of this PIB.
-- The coordination and coherency between the servicing parameters
-- of the scheduler's upstream functional data path elements must
-- be maintained for the scheduler to function correctly.
--
-- The dsSchedulerMinRate and dsSchedulerMaxRate attributes are
-- used for specifying the servicing parameters for output of a
-- scheduler when its downstream functional data path element
-- is another scheduler.
-- This is used for building hierarchical queue/scheduler.
--
-- More discussion of the scheduler functional data path element
-- is in [MODEL] section 7.1.2.
--
dsSchedulerTable OBJECT-TYPE SYNTAX SEQUENCE OF DsSchedulerEntry PIB-ACCESS install STATUS current DESCRIPTION "The Scheduler Table enumerates packet schedulers. Multiple scheduling algorithms can be used on a given datapath, with each algorithm described by one dsSchedulerEntry." REFERENCE "An Informal Management Model for Diffserv Routers, RFC 3290, section 7.1.2"
dsSchedulerTable对象类型语法序列DsSchedulerEntry PIB-ACCESS安装状态当前描述“调度器表枚举数据包调度器。在给定数据路径上可以使用多个调度算法，每个算法由一个DsSchedulerEntry描述。”参考“区分服务路由器的非正式管理模型，RFC 3290，第7.1.2节”
::= { dsPolicyClasses 12 }
::= { dsPolicyClasses 12 }
dsSchedulerEntry OBJECT-TYPE
SYNTAX DsSchedulerEntry
STATUS current
DESCRIPTION
"An entry in the Scheduler Table describing a single
instance of a scheduling algorithm."
PIB-INDEX { dsSchedulerPrid }
UNIQUENESS { dsSchedulerNext,
dsSchedulerMethod,
dsSchedulerMinRate,
dsSchedulerMaxRate }
::= { dsSchedulerTable 1 }
dsSchedulerEntry OBJECT-TYPE
SYNTAX DsSchedulerEntry
STATUS current
DESCRIPTION
"An entry in the Scheduler Table describing a single
instance of a scheduling algorithm."
PIB-INDEX { dsSchedulerPrid }
UNIQUENESS { dsSchedulerNext,
dsSchedulerMethod,
dsSchedulerMinRate,
dsSchedulerMaxRate }
::= { dsSchedulerTable 1 }
DsSchedulerEntry ::= SEQUENCE {
dsSchedulerPrid InstanceId,
dsSchedulerNext Prid,
dsSchedulerMethod AutonomousType,
dsSchedulerMinRate Prid,
dsSchedulerMaxRate Prid
}
DsSchedulerEntry ::= SEQUENCE {
dsSchedulerPrid InstanceId,
dsSchedulerNext Prid,
dsSchedulerMethod AutonomousType,
dsSchedulerMinRate Prid,
dsSchedulerMaxRate Prid
}
dsSchedulerPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsSchedulerEntry 1 }
dsSchedulerPrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsSchedulerEntry 1 }
dsSchedulerNext OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This selects the next diffserv functional datapath element to handle traffic for this data path.
dsSchedulerNext对象类型语法Prid STATUS current DESCRIPTION“选择下一个diffserv functional datapath元素来处理此数据路径的流量。
This attribute normally have a value of zeroDotZero to indicate no further DiffServ treatment is performed on traffic of this datapath. The use of zeroDotZero is the normal usage for the last functional datapath element. Any value other than zeroDotZero must point to a valid (pre-existing) instance of one of: dsSchedulerEntry dsQEntry,
此属性的值通常为zeroDotZero，以指示不对此数据路径的通信量执行进一步的DiffServ处理。zeroDotZero是最后一个功能数据路径元素的正常用法。zeroDotZero以外的任何值都必须指向以下之一的有效（预先存在）实例：dsSchedulerEntry dsQEntry，
or:
或：
dsClfrEntry dsMeterEntry dsActionEntry dsAlgDropEntry
dsClfrEntry dsMeterEntry dsActionEntry DSALGDROPERTY
This points to another dsSchedulerEntry
for implementation of multiple scheduler methods for
the same data path, and for implementation of
hierarchical schedulers."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 2 }
This points to another dsSchedulerEntry
for implementation of multiple scheduler methods for
the same data path, and for implementation of
hierarchical schedulers."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 2 }
dsSchedulerMethod OBJECT-TYPE
SYNTAX AutonomousType
STATUS current
DESCRIPTION
"The scheduling algorithm used by this Scheduler.
Standard values for generic algorithms:
diffServSchedulerPriority,
diffServSchedulerWRR,
diffServSchedulerWFQ
are specified in the DiffServ MIB.
Additional values may be further specified in other PIBs.
A value of zeroDotZero indicates this is unknown."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.2"
::= { dsSchedulerEntry 3 }
dsSchedulerMethod OBJECT-TYPE
SYNTAX AutonomousType
STATUS current
DESCRIPTION
"The scheduling algorithm used by this Scheduler.
Standard values for generic algorithms:
diffServSchedulerPriority,
diffServSchedulerWRR,
diffServSchedulerWFQ
are specified in the DiffServ MIB.
Additional values may be further specified in other PIBs.
A value of zeroDotZero indicates this is unknown."
REFERENCE
"An Informal Management Model for Diffserv Routers,
RFC 3290, section 7.1.2"
::= { dsSchedulerEntry 3 }
dsSchedulerMinRate OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This Prid indicates the entry in dsMinRateTable which indicates the priority or minimum output rate from this scheduler. This attribute is used only when there is more than one level of scheduler.
DSSCHEDULERMIRATE对象类型语法Prid STATUS current DESCRIPTION“此Prid表示dsMinRateTable中的条目，该条目表示此计划程序的优先级或最小输出速率。仅当存在多个级别的计划程序时，才使用此属性。
When it has the value zeroDotZero, it indicates that no
Minimum rate or priority is imposed."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 4 }
When it has the value zeroDotZero, it indicates that no
Minimum rate or priority is imposed."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 4 }
dsSchedulerMaxRate OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "This Prid indicates the entry in dsMaxRateTable
dsSchedulerMaxRate对象类型语法Prid STATUS current DESCRIPTION“此Prid表示dsMaxRateTable中的条目
which indicates the maximum output rate from this scheduler. When more than one maximum rate applies (e.g., a multi-rate shaper is used), it points to the first of the rate entries. This attribute is only used when there is more than one level of scheduler.
指示此计划程序的最大输出速率。当应用多个最大速率时（例如，使用多速率整形器），它指向第一个速率条目。此属性仅在存在多个级别的计划程序时使用。
When it has the value zeroDotZero, it indicates that no
Maximum rate is imposed."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 5 }
When it has the value zeroDotZero, it indicates that no
Maximum rate is imposed."
DEFVAL { zeroDotZero }
::= { dsSchedulerEntry 5 }
--
-- Minimum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries
-- for reusability reasons and so that they may be used by both
-- queues and schedulers. This follows the approach for separation
-- of data path elements from parameterization that is used
-- throughout this PIB.
-- Use of these Minimum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling
-- systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a
-- second scheduler, might specify a minimum transfer rate by
-- pointing to a Minimum Rate Parameter Table entry.
--
-- The dsMinRatePriority/Absolute/Relative attributes are used as
-- parameters to the work-conserving portion of a scheduler:
-- "work-conserving" implies that the scheduler can continue to emit
-- data as long as there is data available at its input(s). This
-- has the effect of guaranteeing a certain priority relative to
-- other scheduler inputs and/or a certain minimum proportion of the
-- available output bandwidth. Properly configured, this means a
-- certain minimum rate, which may be exceeded should traffic be
-- available should there be spare bandwidth after all other classes
-- have had opportunities to consume their own minimum rates.
--
--
-- Minimum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries
-- for reusability reasons and so that they may be used by both
-- queues and schedulers. This follows the approach for separation
-- of data path elements from parameterization that is used
-- throughout this PIB.
-- Use of these Minimum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling
-- systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a
-- second scheduler, might specify a minimum transfer rate by
-- pointing to a Minimum Rate Parameter Table entry.
--
-- The dsMinRatePriority/Absolute/Relative attributes are used as
-- parameters to the work-conserving portion of a scheduler:
-- "work-conserving" implies that the scheduler can continue to emit
-- data as long as there is data available at its input(s). This
-- has the effect of guaranteeing a certain priority relative to
-- other scheduler inputs and/or a certain minimum proportion of the
-- available output bandwidth. Properly configured, this means a
-- certain minimum rate, which may be exceeded should traffic be
-- available should there be spare bandwidth after all other classes
-- have had opportunities to consume their own minimum rates.
--
dsMinRateTable OBJECT-TYPE SYNTAX SEQUENCE OF DsMinRateEntry PIB-ACCESS install STATUS current DESCRIPTION "The Minimum Rate Table enumerates individual sets of scheduling parameter that can be used/reused
DSMINRATABLE DSMINRATENTRY PIB-ACCESS安装状态当前描述的对象类型语法序列“最小速率表列举了可使用/重用的单独调度参数集
by Queues and Schedulers."
::= { dsPolicyClasses 13 }
by Queues and Schedulers."
::= { dsPolicyClasses 13 }
dsMinRateEntry OBJECT-TYPE
SYNTAX DsMinRateEntry
STATUS current
DESCRIPTION
"An entry in the Minimum Rate Table describes
a single set of scheduling parameter for use by
queues and schedulers."
PIB-INDEX { dsMinRatePrid }
UNIQUENESS { dsMinRatePriority,
dsMinRateAbsolute,
dsMinRateRelative }
::= { dsMinRateTable 1 }
dsMinRateEntry OBJECT-TYPE
SYNTAX DsMinRateEntry
STATUS current
DESCRIPTION
"An entry in the Minimum Rate Table describes
a single set of scheduling parameter for use by
queues and schedulers."
PIB-INDEX { dsMinRatePrid }
UNIQUENESS { dsMinRatePriority,
dsMinRateAbsolute,
dsMinRateRelative }
::= { dsMinRateTable 1 }
DsMinRateEntry ::= SEQUENCE {
dsMinRatePrid InstanceId,
dsMinRatePriority Unsigned32,
dsMinRateAbsolute Unsigned32,
dsMinRateRelative Unsigned32
}
DsMinRateEntry ::= SEQUENCE {
dsMinRatePrid InstanceId,
dsMinRatePriority Unsigned32,
dsMinRateAbsolute Unsigned32,
dsMinRateRelative Unsigned32
}
dsMinRatePrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMinRateEntry 1 }
dsMinRatePrid OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMinRateEntry 1 }
dsMinRatePriority OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"The priority of this input to the associated scheduler,
relative to the scheduler's other inputs. Higher Priority
value indicates the associated queue/scheduler will get
service first before others with lower Priority values."
::= { dsMinRateEntry 2 }
dsMinRatePriority OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
STATUS current
DESCRIPTION
"The priority of this input to the associated scheduler,
relative to the scheduler's other inputs. Higher Priority
value indicates the associated queue/scheduler will get
service first before others with lower Priority values."
::= { dsMinRateEntry 2 }
dsMinRateAbsolute OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "kilobits per second" STATUS current DESCRIPTION "The minimum absolute rate, in kilobits/sec, that a downstream scheduler element should allocate to this queue. If the value
dsMinRateAbsolute对象类型语法Unsigned32（1..4294967295）UNITS“kilobits per second”STATUS current DESCRIPTION“下游调度程序元素应分配给此队列的最小绝对速率（以千位/秒为单位）。如果
is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate.
如果为零，则实际上没有最低利率保证。如果该值不为零，调度程序将确保该队列的服务至少达到该速率。
Note that this attribute's value is coupled to that of dsMinRateRelative: changes to one will affect the value of the other.
请注意，此属性的值与DSMinrMaterialRelative的值耦合：对其中一个属性的更改将影响另一个属性的值。
[IFMIB] defines ifSpeed as Gauge32 in units of bits per second, and ifHighSpeed as Gauge32 in units of 1,000,000 bits per second. This yields the following equations:
[IFMIB]将ifSpeed定义为以每秒位为单位的Gauge32，将ifHighSpeed定义为以每秒1000000位为单位的Gauge32。这将产生以下方程式：
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
Where, 1000 is for converting kbps used by RateAbsolute to bps used by ifSpeed, 1,000 is for 'in units of 1/1,000 of 1' for RateRelative.
其中，1000表示将RateAbsolute使用的kbps转换为ifSpeed使用的bps，1000表示RateRelative的“单位为1/1000/1”。
or, if appropriate:
或在适当情况下：
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMinRateEntry 3 }
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMinRateEntry 3 }
dsMinRateRelative OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) STATUS current DESCRIPTION "The minimum rate that a downstream scheduler element should allocate to this queue, relative to the max-imum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1,000 of 1. If the value is zero, then there is effectively no minimum rate guarantee. If the value is non-zero, the scheduler will assure the servicing of this queue to at least this rate.
DSMINRaterrative对象类型语法Unsigned32（1..4294967295）状态当前说明“相对于ifSpeed或ifHighSpeed报告的接口最大最大速率，下游调度程序元素应分配给此队列的最小速率，单位为1/1000/1。如果该值为零，则实际上没有最低利率保证。如果该值不为零，调度程序将确保该队列的服务至少达到该速率。
Note that this attribute's value is coupled to that of dsMinRateAbsolute: changes to one will affect the value of the other.
请注意，此属性的值与dsMinRateAbsolute的值耦合：对其中一个属性的更改将影响另一个属性的值。
[IFMIB] defines ifSpeed as Gauge32 in units of bits per second, and ifHighSpeed as Gauge32 in units of 1,000,000 bits per second. This yields the following equations:
[IFMIB]将ifSpeed定义为以每秒位为单位的Gauge32，将ifHighSpeed定义为以每秒1000000位为单位的Gauge32。这将产生以下方程式：
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
Where, 1000 is for converting kbps used by RateAbsolute to bps used by ifSpeed, 1,000 is for 'in units of 1/1,000 of 1' for RateRelative.
其中，1000表示将RateAbsolute使用的kbps转换为ifSpeed使用的bps，1000表示RateRelative的“单位为1/1000/1”。
or, if appropriate:
或在适当情况下：
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMinRateEntry 4 }
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMinRateEntry 4 }
--
-- Maximum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries
-- for reusability reasons and so that they may be used by both
-- queues and schedulers. This follows the approach for separation
-- of data path elements from parameterization that is used
-- throughout this PIB.
--
-- Use of these Maximum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling
-- systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a
-- second scheduler, might specify a maximum transfer rate by
-- pointing to a Maximum Rate Parameter Table entry. Multi-rate
-- shapers, such as a Dual Leaky Bucket algorithm, specify their
-- rates using multiple Maximum Rate Parameter Entries with the same
-- dsMaxRateId but different dsMaxRateLevels.
--
-- The dsMaxRateLevel/Absolute/Relative attributes are used as
--
-- Maximum Rate Parameters Table
--
-- The parameters used by a scheduler for its inputs or outputs are
-- maintained separately from the Queue or Scheduler table entries
-- for reusability reasons and so that they may be used by both
-- queues and schedulers. This follows the approach for separation
-- of data path elements from parameterization that is used
-- throughout this PIB.
--
-- Use of these Maximum Rate Parameter Table entries by Queues and
-- Schedulers allows the modeling of hierarchical scheduling
-- systems.
--
-- Specifically, a Scheduler has one or more inputs and one output.
-- Any queue feeding a scheduler, or any scheduler which feeds a
-- second scheduler, might specify a maximum transfer rate by
-- pointing to a Maximum Rate Parameter Table entry. Multi-rate
-- shapers, such as a Dual Leaky Bucket algorithm, specify their
-- rates using multiple Maximum Rate Parameter Entries with the same
-- dsMaxRateId but different dsMaxRateLevels.
--
-- The dsMaxRateLevel/Absolute/Relative attributes are used as
-- parameters to the non-work-conserving portion of a scheduler:
-- non-work-conserving implies that the scheduler may sometimes not
-- emit a packet, even if there is data available at its input(s).
-- This has the effect of limiting the servicing of the
-- queue/scheduler input or output, in effect performing shaping of
-- the packet stream passing through the queue/scheduler, as
-- described in the Informal Differentiated Services Model
-- section 7.2.
--
-- parameters to the non-work-conserving portion of a scheduler:
-- non-work-conserving implies that the scheduler may sometimes not
-- emit a packet, even if there is data available at its input(s).
-- This has the effect of limiting the servicing of the
-- queue/scheduler input or output, in effect performing shaping of
-- the packet stream passing through the queue/scheduler, as
-- described in the Informal Differentiated Services Model
-- section 7.2.
--
dsMaxRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsMaxRateEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The Maximum Rate Table enumerates individual
sets of scheduling parameter that can be used/reused
by Queues and Schedulers."
::= { dsPolicyClasses 14 }
dsMaxRateTable OBJECT-TYPE
SYNTAX SEQUENCE OF DsMaxRateEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"The Maximum Rate Table enumerates individual
sets of scheduling parameter that can be used/reused
by Queues and Schedulers."
::= { dsPolicyClasses 14 }
dsMaxRateEntry OBJECT-TYPE
SYNTAX DsMaxRateEntry
STATUS current
DESCRIPTION
"An entry in the Maximum Rate Table describes
a single set of scheduling parameter for use by
queues and schedulers."
PIB-INDEX { dsMaxRatePrid }
UNIQUENESS { dsMaxRateId,
dsMaxRateLevel,
dsMaxRateAbsolute,
dsMaxRateRelative,
dsMaxRateThreshold }
::= { dsMaxRateTable 1 }
dsMaxRateEntry OBJECT-TYPE
SYNTAX DsMaxRateEntry
STATUS current
DESCRIPTION
"An entry in the Maximum Rate Table describes
a single set of scheduling parameter for use by
queues and schedulers."
PIB-INDEX { dsMaxRatePrid }
UNIQUENESS { dsMaxRateId,
dsMaxRateLevel,
dsMaxRateAbsolute,
dsMaxRateRelative,
dsMaxRateThreshold }
::= { dsMaxRateTable 1 }
DsMaxRateEntry ::= SEQUENCE {
dsMaxRatePrid InstanceId,
dsMaxRateId Unsigned32,
dsMaxRateLevel Unsigned32,
dsMaxRateAbsolute Unsigned32,
dsMaxRateRelative Unsigned32,
dsMaxRateThreshold BurstSize
}
DsMaxRateEntry ::= SEQUENCE {
dsMaxRatePrid InstanceId,
dsMaxRateId Unsigned32,
dsMaxRateLevel Unsigned32,
dsMaxRateAbsolute Unsigned32,
dsMaxRateRelative Unsigned32,
dsMaxRateThreshold BurstSize
}
dsMaxRatePrid OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION
dsMaxRatePrid对象类型语法InstanceId状态当前描述
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMaxRateEntry 1 }
"An arbitrary integer index that uniquely identifies an
instance of the class."
::= { dsMaxRateEntry 1 }
dsMaxRateId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"An identifier used together with dsMaxRateLevel for
representing a multi-rate shaper. This attribute is used for
associating all the rate attributes of a multi-rate shaper.
Each dsMaxRateEntry of a multi-rate shaper must have the same
value in this attribute. The different rates of a multi-rate
shaper is identified using dsMaxRateLevel.
This attribute uses the value of zero to indicate this
attribute is not used, for single rate shaper."
DEFVAL { 0 }
::= { dsMaxRateEntry 2 }
dsMaxRateId OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
STATUS current
DESCRIPTION
"An identifier used together with dsMaxRateLevel for
representing a multi-rate shaper. This attribute is used for
associating all the rate attributes of a multi-rate shaper.
Each dsMaxRateEntry of a multi-rate shaper must have the same
value in this attribute. The different rates of a multi-rate
shaper is identified using dsMaxRateLevel.
This attribute uses the value of zero to indicate this
attribute is not used, for single rate shaper."
DEFVAL { 0 }
::= { dsMaxRateEntry 2 }
dsMaxRateLevel OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
STATUS current
DESCRIPTION
"An index that indicates which level of a multi-rate shaper is
being given its parameters. A multi-rate shaper has some
number of rate levels. Frame Relay's dual rate specification
refers to a 'committed' and an 'excess' rate; ATM's dual rate
specification refers to a 'mean' and a 'peak' rate. This table
is generalized to support an arbitrary number of rates. The
committed or mean rate is level 1, the peak rate (if any) is
the highest level rate configured, and if there are other
rates they are distributed in monotonically increasing order
between them.
When the entry is used for a single rate shaper, this
attribute contains a value of one."
DEFVAL { 1 }
::= { dsMaxRateEntry 3 }
dsMaxRateLevel OBJECT-TYPE
SYNTAX Unsigned32 (1..32)
STATUS current
DESCRIPTION
"An index that indicates which level of a multi-rate shaper is
being given its parameters. A multi-rate shaper has some
number of rate levels. Frame Relay's dual rate specification
refers to a 'committed' and an 'excess' rate; ATM's dual rate
specification refers to a 'mean' and a 'peak' rate. This table
is generalized to support an arbitrary number of rates. The
committed or mean rate is level 1, the peak rate (if any) is
the highest level rate configured, and if there are other
rates they are distributed in monotonically increasing order
between them.
When the entry is used for a single rate shaper, this
attribute contains a value of one."
DEFVAL { 1 }
::= { dsMaxRateEntry 3 }
dsMaxRateAbsolute OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) UNITS "kilobits per second" STATUS current DESCRIPTION "The maximum rate in kilobits/sec that a downstream scheduler element should allocate to this queue. If the value is zero, then there is effectively no max-imum rate limit and that the scheduler should attempt to be work-conserving for this queue. If the value
dsMaxRateAbsolute对象类型语法无符号32（1..4294967295）单位“千比特每秒”状态当前说明“下游调度程序元素应分配到此队列的最大速率（以千比特/秒为单位）。如果该值为零，则实际上没有最大最小速率限制，并且调度程序应该尝试为该队列节省工作。如果值
is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner.
如果为非零，则调度程序将以非节省工时的方式将此队列的服务限制为最多此速率。
Note that this attribute's value is coupled to that of dsMaxRateRelative: changes to one will affect the value of the other.
请注意，此属性的值与dsMaxRateRelative的值耦合：对其中一个属性的更改将影响另一个属性的值。
[IFMIB] defines ifSpeed as Gauge32 in units of bits per second, and ifHighSpeed as Gauge32 in units of 1,000,000 bits per second. This yields the following equations:
[IFMIB]将ifSpeed定义为以每秒位为单位的Gauge32，将ifHighSpeed定义为以每秒1000000位为单位的Gauge32。这将产生以下方程式：
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
Where, 1000 is for converting kbps used by RateAbsolute to bps used by ifSpeed, 1,000 is for 'in units of 1/1,000 of 1' for RateRelative.
其中，1000表示将RateAbsolute使用的kbps转换为ifSpeed使用的bps，1000表示RateRelative的“单位为1/1000/1”。
or, if appropriate:
或在适当情况下：
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
::= { dsMaxRateEntry 4 }
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
::= { dsMaxRateEntry 4 }
dsMaxRateRelative OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) STATUS current DESCRIPTION "The maximum rate that a downstream scheduler element should allocate to this queue, relative to the max-imum rate of the interface as reported by ifSpeed or ifHighSpeed, in units of 1/1,000 of 1. If the value is zero, then there is effectively no maximum rate limit and the scheduler should attempt to be work-conserving for this queue. If the value is non-zero, the scheduler will limit the servicing of this queue to, at most, this rate in a non-work-conserving manner.
dsMaxRateRelative对象类型语法Unsigned32（1..4294967295）状态当前说明“相对于ifSpeed或ifHighSpeed报告的接口最大最大速率，下游调度程序元素应分配给此队列的最大速率，单位为1/1000/1。如果该值为零，则实际上没有最大速率限制，调度程序应尝试为该队列节省工作。如果该值不为零，调度程序将以非节省工时的方式将此队列的服务限制为最多此速率。
Note that this attribute's value is coupled to that of dsMaxRateAbsolute: changes to one will affect the value of the other.
请注意，此属性的值与dsMaxRateAbsolute的值耦合：对其中一个属性的更改将影响另一个属性的值。
[IFMIB] defines ifSpeed as Gauge32 in units of bits per second, and ifHighSpeed as Gauge32 in units of 1,000,000 bits per second. This yields the following equations:
[IFMIB]将ifSpeed定义为以每秒位为单位的Gauge32，将ifHighSpeed定义为以每秒1000000位为单位的Gauge32。这将产生以下方程式：
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
RateRelative = [ (RateAbsolute * 1000) / ifSpeed ] * 1,000
Where, 1000 is for converting kbps used by RateAbsolute to bps used by ifSpeed, 1,000 is for 'in units of 1/1,000 of 1' for RateRelative.
其中，1000表示将RateAbsolute使用的kbps转换为ifSpeed使用的bps，1000表示RateRelative的“单位为1/1000/1”。
or, if appropriate:
或在适当情况下：
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
RateRelative =
{ [ (RateAbsolute * 1000) / 1,000,000 ] / ifHIghSpeed } *
1,000
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMaxRateEntry 5 }
Where, 1000 and 1,000,000 is for converting kbps used by
RateAbsolute to 1 million bps used by ifHighSpeed, 1,000 is
for 'in units of 1/1,000 of 1' for RateRelative."
REFERENCE
"ifSpeed, ifHighSpeed from the IF-MIB, RFC 2863."
::= { dsMaxRateEntry 5 }
dsMaxRateThreshold OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
STATUS current
DESCRIPTION
"The number of bytes of queue depth at which the rate of a
multi-rate scheduler will increase to the next output rate. In
the last PRI for such a shaper, this threshold is
ignored and by convention is zero."
REFERENCE
"Adaptive Rate Shaper, RFC 2963"
::= { dsMaxRateEntry 6 }
dsMaxRateThreshold OBJECT-TYPE
SYNTAX BurstSize
UNITS "Bytes"
STATUS current
DESCRIPTION
"The number of bytes of queue depth at which the rate of a
multi-rate scheduler will increase to the next output rate. In
the last PRI for such a shaper, this threshold is
ignored and by convention is zero."
REFERENCE
"Adaptive Rate Shaper, RFC 2963"
::= { dsMaxRateEntry 6 }
-- -- Conformance Section --
----合规部分--
dsPolicyPibCompliances
OBJECT IDENTIFIER ::= { dsPolicyPibConformance 1 }
dsPolicyPibGroups
OBJECT IDENTIFIER ::= { dsPolicyPibConformance 2 }
dsPolicyPibCompliances
OBJECT IDENTIFIER ::= { dsPolicyPibConformance 1 }
dsPolicyPibGroups
OBJECT IDENTIFIER ::= { dsPolicyPibConformance 2 }
dsPolicyPibCompliance MODULE-COMPLIANCE
DSPolicyPIB合规性模块-合规性
STATUS current DESCRIPTION "Describes the requirements for conformance to the QoS Policy PIB."
“状态当前描述”描述符合QoS策略PIB的要求
MODULE FRAMEWORK-PIB
MANDATORY-GROUPS {
frwkPrcSupportGroup,
frwkPibIncarnationGroup,
frwkDeviceIdGroup,
frwkCompLimitsGroup,
frwkCapabilitySetGroup,
frwkRoleComboGroup,
frwkIfRoleComboGroup,
frwkBaseFilterGroup,
frwkIpFilterGroup }
MODULE FRAMEWORK-PIB
MANDATORY-GROUPS {
frwkPrcSupportGroup,
frwkPibIncarnationGroup,
frwkDeviceIdGroup,
frwkCompLimitsGroup,
frwkCapabilitySetGroup,
frwkRoleComboGroup,
frwkIfRoleComboGroup,
frwkBaseFilterGroup,
frwkIpFilterGroup }
OBJECT frwkPibIncarnationLongevity PIB-MIN-ACCESS notify DESCRIPTION "Install support is required if policy expiration is to be supported."
对象FRWKPIBINCARNATIONPIB-MIN-ACCESS通知说明“如果要支持策略过期，则需要安装支持。”
OBJECT frwkPibIncarnationTtl PIB-MIN-ACCESS notify DESCRIPTION "Install support is required if policy expiration is to be supported."
对象FRWKPIBINCARTONTTL PIB-MIN-ACCESS通知说明“如果要支持策略过期，则需要安装支持。”
MODULE DIFFSERV-PIB -- this module
MANDATORY-GROUPS {
dsPibBaseIfCapsGroup,
dsPibIfClassificationCapsGroup,
dsPibIfAlgDropCapsGroup,
dsPibIfQueueCapsGroup,
dsPibIfSchedulerCapsGroup,
dsPibIfMaxRateCapsGroup,
dsPibIfElmDepthCapsGroup,
dsPibIfElmLinkCapsGroup,
dsPibDataPathGroup,
dsPibClfrGroup,
dsPibClfrElementGroup,
dsPibActionGroup,
dsPibAlgDropGroup,
dsPibQGroup,
dsPibSchedulerGroup,
dsPibMinRateGroup,
dsPibMaxRateGroup }
MODULE DIFFSERV-PIB -- this module
MANDATORY-GROUPS {
dsPibBaseIfCapsGroup,
dsPibIfClassificationCapsGroup,
dsPibIfAlgDropCapsGroup,
dsPibIfQueueCapsGroup,
dsPibIfSchedulerCapsGroup,
dsPibIfMaxRateCapsGroup,
dsPibIfElmDepthCapsGroup,
dsPibIfElmLinkCapsGroup,
dsPibDataPathGroup,
dsPibClfrGroup,
dsPibClfrElementGroup,
dsPibActionGroup,
dsPibAlgDropGroup,
dsPibQGroup,
dsPibSchedulerGroup,
dsPibMinRateGroup,
dsPibMaxRateGroup }
GROUP dsPibIfMeteringCapsGroup DESCRIPTION "This group is mandatory for devices that implement metering functions."
组dsPibIfMeteringCapsGroup DESCRIPTION“此组对于实现计量功能的设备是必需的。”
GROUP dsPibMeterGroup DESCRIPTION "This group is mandatory for devices that implement metering functions."
GROUP dsPibMeterGroup DESCRIPTION“此组对于实现计量功能的设备是必需的。”
GROUP dsPibTBParamGroup DESCRIPTION "This group is mandatory for devices that implement token-bucket metering functions."
GROUP dsPibTBParamGroup DESCRIPTION“对于实现令牌桶计量功能的设备，此组是必需的。”
GROUP dsPibDscpMarkActGroup DESCRIPTION "This group is mandatory for devices that implement DSCP-Marking functions."
组DSPIBDSCMParkactGroup DESCRIPTION“此组对于实现DSCP标记功能的设备是必需的。”
GROUP dsPibMQAlgDropGroup DESCRIPTION "This group is mandatory for devices that implement Multiple Queue Measured Algorithmic Drop functions."
GROUP dsPibMQAlgDropGroup DESCRIPTION“对于实现多个队列测量算法丢弃功能的设备，此组是必需的。”
GROUP dsPibRandomDropGroup DESCRIPTION "This group is mandatory for devices that implement Random Drop functions."
GROUP dsPibRandomDropGroup DESCRIPTION“对于实现随机丢弃功能的设备，此组是必需的。”
OBJECT dsClfrId PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsClfrId PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsClfrElementClfrId PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsClfrElementClfrId PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsClfrElementPrecedence PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象DSCLFRelementPreference PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsClfrElementNext PIB-MIN-ACCESS not-accessible
对象dsClfrElementNext PIB-MIN-ACCESS不可访问
DESCRIPTION "Install support is not required."
说明“不需要安装支持。”
OBJECT dsClfrElementSpecific PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsClfrElementSpecific PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMeterSucceedNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMeterSucceedNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMeterFailNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMeterFailNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMeterSpecific PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMeterSpecific PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsTBParamType PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsTBParamType PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsTBParamRate PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsTBParamRate PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsTBParamBurstSize PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsTBParamBurstSize PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsTBParamInterval PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsTBParamInterval PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsActionNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsActionNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsActionSpecific PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsActionSpecific PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsAlgDropType PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsAlgDropType PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsAlgDropNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsAlgDropNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsAlgDropQMeasure PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsAlgDropQMeasure PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsAlgDropQThreshold PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsAlgDropQThreshold PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsAlgDropSpecific PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsAlgDropSpecific PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsRandomDropMinThreshBytes PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropMinThreshBytes PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsRandomDropMinThreshPkts PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropMinThreshPkts PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsRandomDropMaxThreshBytes PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropMaxThreshBytes PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsRandomDropMaxThreshPkts PIB-MIN-ACCESS not-accessible DESCRIPTION
对象dsRandomDropMaxThreshPkts PIB-MIN-ACCESS不可访问描述
"Install support is not required."
“不需要安装支持。”
OBJECT dsRandomDropProbMax PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropProbMax PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsRandomDropWeight PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropWeight PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsRandomDropSamplingRate PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsRandomDropSamplingRate PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsQNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsQNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsQMinRate PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsQMinRate PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsQMaxRate PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsQMaxRate PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsSchedulerNext PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsSchedulerNext PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsSchedulerMethod PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsSchedulerMethod PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsSchedulerMinRate PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象DSSchedulerMirate PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsSchedulerMaxRate
对象dsSchedulerMaxRate
PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
PIB-MIN-ACCESS不可访问说明“不需要安装支持。”
OBJECT dsMinRatePriority PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMinRatePriority PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMinRateAbsolute PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象DSMINRATE绝对PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMinRateRelative PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象DSMIN材料相关PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMaxRateId PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMaxRateId PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMaxRateLevel PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMaxRateLevel PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMaxRateAbsolute PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象DSMAXRATE绝对PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMaxRateRelative PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMaxRateRelative PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
OBJECT dsMaxRateThreshold PIB-MIN-ACCESS not-accessible DESCRIPTION "Install support is not required."
对象dsMaxRateThreshold PIB-MIN-ACCESS不可访问描述“不需要安装支持。”
::= { dsPolicyPibCompliances 1 }
::= { dsPolicyPibCompliances 1 }
dsPibBaseIfCapsGroup OBJECT-GROUP OBJECTS {
dsPibBaseIfCapsGroup对象组对象{
dsBaseIfCapsPrid, dsBaseIfCapsDirection
}
STATUS current
DESCRIPTION
"The Base Interface Capability Group defines the PIB
Objects that describe the base for interface capabilities."
::= { dsPolicyPibGroups 1 }
dsBaseIfCapsPrid, dsBaseIfCapsDirection
}
STATUS current
DESCRIPTION
"The Base Interface Capability Group defines the PIB
Objects that describe the base for interface capabilities."
::= { dsPolicyPibGroups 1 }
dsPibIfClassificationCapsGroup OBJECT-GROUP
OBJECTS {
dsIfClassificationCapsSpec
}
STATUS current
DESCRIPTION
"The Classification Capability Group defines the PIB
Objects that describe the classification capabilities."
::= { dsPolicyPibGroups 2 }
dsPibIfClassificationCapsGroup OBJECT-GROUP
OBJECTS {
dsIfClassificationCapsSpec
}
STATUS current
DESCRIPTION
"The Classification Capability Group defines the PIB
Objects that describe the classification capabilities."
::= { dsPolicyPibGroups 2 }
dsPibIfMeteringCapsGroup OBJECT-GROUP
OBJECTS {
dsIfMeteringCapsSpec
}
STATUS current
DESCRIPTION
"The Metering Capability Group defines the PIB
Objects that describe the metering capabilities."
::= { dsPolicyPibGroups 3 }
dsPibIfMeteringCapsGroup OBJECT-GROUP
OBJECTS {
dsIfMeteringCapsSpec
}
STATUS current
DESCRIPTION
"The Metering Capability Group defines the PIB
Objects that describe the metering capabilities."
::= { dsPolicyPibGroups 3 }
dsPibIfAlgDropCapsGroup OBJECT-GROUP
OBJECTS {
dsIfAlgDropCapsType, dsIfAlgDropCapsMQCount
}
STATUS current
DESCRIPTION
"The Algorithmic Dropper Capability Group defines the
PIB Objects that describe the algorithmic dropper
capabilities."
::= { dsPolicyPibGroups 4 }
dsPibIfAlgDropCapsGroup OBJECT-GROUP
OBJECTS {
dsIfAlgDropCapsType, dsIfAlgDropCapsMQCount
}
STATUS current
DESCRIPTION
"The Algorithmic Dropper Capability Group defines the
PIB Objects that describe the algorithmic dropper
capabilities."
::= { dsPolicyPibGroups 4 }
dsPibIfQueueCapsGroup OBJECT-GROUP
OBJECTS {
dsIfQueueCapsMinQueueSize, dsIfQueueCapsMaxQueueSize,
dsIfQueueCapsTotalQueueSize
}
STATUS current
DESCRIPTION
"The Queueing Capability Group defines the PIB
Objects that describe the queueing capabilities."
dsPibIfQueueCapsGroup OBJECT-GROUP
OBJECTS {
dsIfQueueCapsMinQueueSize, dsIfQueueCapsMaxQueueSize,
dsIfQueueCapsTotalQueueSize
}
STATUS current
DESCRIPTION
"The Queueing Capability Group defines the PIB
Objects that describe the queueing capabilities."
::= { dsPolicyPibGroups 5 }
::= { dsPolicyPibGroups 5 }
dsPibIfSchedulerCapsGroup OBJECT-GROUP
OBJECTS {
dsIfSchedulerCapsServiceDisc, dsIfSchedulerCapsMaxInputs,
dsIfSchedulerCapsMinMaxRate
}
STATUS current
DESCRIPTION
"The Scheduler Capability Group defines the PIB
Objects that describe the scheduler capabilities."
::= { dsPolicyPibGroups 6 }
dsPibIfSchedulerCapsGroup OBJECT-GROUP
OBJECTS {
dsIfSchedulerCapsServiceDisc, dsIfSchedulerCapsMaxInputs,
dsIfSchedulerCapsMinMaxRate
}
STATUS current
DESCRIPTION
"The Scheduler Capability Group defines the PIB
Objects that describe the scheduler capabilities."
::= { dsPolicyPibGroups 6 }
dsPibIfMaxRateCapsGroup OBJECT-GROUP
OBJECTS {
dsIfMaxRateCapsMaxLevels
}
STATUS current
DESCRIPTION
"The Max Rate Capability Group defines the PIB
Objects that describe the max rate capabilities."
::= { dsPolicyPibGroups 7 }
dsPibIfMaxRateCapsGroup OBJECT-GROUP
OBJECTS {
dsIfMaxRateCapsMaxLevels
}
STATUS current
DESCRIPTION
"The Max Rate Capability Group defines the PIB
Objects that describe the max rate capabilities."
::= { dsPolicyPibGroups 7 }
dsPibIfElmDepthCapsGroup OBJECT-GROUP
OBJECTS {
dsIfElmDepthCapsPrc, dsIfElmDepthCapsCascadeMax
}
STATUS current
DESCRIPTION
"The DataPath Element Depth Capability Group defines the PIB
Objects that describe the datapath element depth
capabilities."
::= { dsPolicyPibGroups 8 }
dsPibIfElmDepthCapsGroup OBJECT-GROUP
OBJECTS {
dsIfElmDepthCapsPrc, dsIfElmDepthCapsCascadeMax
}
STATUS current
DESCRIPTION
"The DataPath Element Depth Capability Group defines the PIB
Objects that describe the datapath element depth
capabilities."
::= { dsPolicyPibGroups 8 }
dsPibIfElmLinkCapsGroup OBJECT-GROUP
OBJECTS {
dsIfElmLinkCapsPrc, dsIfElmLinkCapsAttr,
dsIfElmLinkCapsNextPrc
}
STATUS current
DESCRIPTION
"The DataPath Element Linkage Capability Group defines the
PIB Objects that describe the datapath element linkage
capabilities."
::= { dsPolicyPibGroups 9 }
dsPibIfElmLinkCapsGroup OBJECT-GROUP
OBJECTS {
dsIfElmLinkCapsPrc, dsIfElmLinkCapsAttr,
dsIfElmLinkCapsNextPrc
}
STATUS current
DESCRIPTION
"The DataPath Element Linkage Capability Group defines the
PIB Objects that describe the datapath element linkage
capabilities."
::= { dsPolicyPibGroups 9 }
dsPibDataPathGroup OBJECT-GROUP OBJECTS {
dsPibDataPathGroup对象组对象{
dsDataPathPrid, dsDataPathCapSetName,
dsDataPathRoles, dsDataPathIfDirection,
dsDataPathStart
}
STATUS current
DESCRIPTION
"The Data Path Group defines the PIB Objects that
describe a data path."
::= { dsPolicyPibGroups 10 }
dsDataPathPrid, dsDataPathCapSetName,
dsDataPathRoles, dsDataPathIfDirection,
dsDataPathStart
}
STATUS current
DESCRIPTION
"The Data Path Group defines the PIB Objects that
describe a data path."
::= { dsPolicyPibGroups 10 }
dsPibClfrGroup OBJECT-GROUP
OBJECTS {
dsClfrPrid, dsClfrId
}
STATUS current
DESCRIPTION
"The Classifier Group defines the PIB Objects that
describe a generic classifier."
::= { dsPolicyPibGroups 11 }
dsPibClfrGroup OBJECT-GROUP
OBJECTS {
dsClfrPrid, dsClfrId
}
STATUS current
DESCRIPTION
"The Classifier Group defines the PIB Objects that
describe a generic classifier."
::= { dsPolicyPibGroups 11 }
dsPibClfrElementGroup OBJECT-GROUP
OBJECTS {
dsClfrElementPrid, dsClfrElementClfrId,
dsClfrElementPrecedence, dsClfrElementNext,
dsClfrElementSpecific
}
STATUS current
DESCRIPTION
"The Classifier Group defines the PIB Objects that
describe a generic classifier."
::= { dsPolicyPibGroups 12 }
dsPibClfrElementGroup OBJECT-GROUP
OBJECTS {
dsClfrElementPrid, dsClfrElementClfrId,
dsClfrElementPrecedence, dsClfrElementNext,
dsClfrElementSpecific
}
STATUS current
DESCRIPTION
"The Classifier Group defines the PIB Objects that
describe a generic classifier."
::= { dsPolicyPibGroups 12 }
dsPibMeterGroup OBJECT-GROUP
OBJECTS {
dsMeterPrid, dsMeterSucceedNext,
dsMeterFailNext, dsMeterSpecific
}
STATUS current
DESCRIPTION
"The Meter Group defines the objects used in describ-
ing a generic meter element."
::= { dsPolicyPibGroups 13 }
dsPibMeterGroup OBJECT-GROUP
OBJECTS {
dsMeterPrid, dsMeterSucceedNext,
dsMeterFailNext, dsMeterSpecific
}
STATUS current
DESCRIPTION
"The Meter Group defines the objects used in describ-
ing a generic meter element."
::= { dsPolicyPibGroups 13 }
dsPibTBParamGroup OBJECT-GROUP
OBJECTS {
dsTBParamPrid, dsTBParamType, dsTBParamRate,
dsTBParamBurstSize, dsTBParamInterval
}
dsPibTBParamGroup OBJECT-GROUP
OBJECTS {
dsTBParamPrid, dsTBParamType, dsTBParamRate,
dsTBParamBurstSize, dsTBParamInterval
}
STATUS current
DESCRIPTION
"The Token-Bucket Parameter Group defines the objects
used in describing a single-rate token bucket meter
element."
::= { dsPolicyPibGroups 14 }
STATUS current
DESCRIPTION
"The Token-Bucket Parameter Group defines the objects
used in describing a single-rate token bucket meter
element."
::= { dsPolicyPibGroups 14 }
dsPibActionGroup OBJECT-GROUP
OBJECTS {
dsActionPrid, dsActionNext, dsActionSpecific
}
STATUS current
DESCRIPTION
"The Action Group defines the objects used in
describing a generic action element."
::= { dsPolicyPibGroups 15 }
dsPibActionGroup OBJECT-GROUP
OBJECTS {
dsActionPrid, dsActionNext, dsActionSpecific
}
STATUS current
DESCRIPTION
"The Action Group defines the objects used in
describing a generic action element."
::= { dsPolicyPibGroups 15 }
dsPibDscpMarkActGroup OBJECT-GROUP
OBJECTS {
dsDscpMarkActPrid, dsDscpMarkActDscp
}
STATUS current
DESCRIPTION
"The DSCP Mark Action Group defines the objects used
in describing a DSCP Marking Action element."
::= { dsPolicyPibGroups 16 }
dsPibDscpMarkActGroup OBJECT-GROUP
OBJECTS {
dsDscpMarkActPrid, dsDscpMarkActDscp
}
STATUS current
DESCRIPTION
"The DSCP Mark Action Group defines the objects used
in describing a DSCP Marking Action element."
::= { dsPolicyPibGroups 16 }
dsPibAlgDropGroup OBJECT-GROUP
OBJECTS {
dsAlgDropPrid, dsAlgDropType, dsAlgDropNext,
dsAlgDropQMeasure, dsAlgDropQThreshold,
dsAlgDropSpecific
}
STATUS current
DESCRIPTION
"The Algorithmic Drop Group contains the objects that
describe algorithmic dropper operation and configura-
tion."
::= { dsPolicyPibGroups 17 }
dsPibAlgDropGroup OBJECT-GROUP
OBJECTS {
dsAlgDropPrid, dsAlgDropType, dsAlgDropNext,
dsAlgDropQMeasure, dsAlgDropQThreshold,
dsAlgDropSpecific
}
STATUS current
DESCRIPTION
"The Algorithmic Drop Group contains the objects that
describe algorithmic dropper operation and configura-
tion."
::= { dsPolicyPibGroups 17 }
dsPibMQAlgDropGroup OBJECT-GROUP
OBJECTS {
dsMQAlgDropExceedNext
}
STATUS current
DESCRIPTION
"The Multiple Queue Measured Algorithmic Drop Group
contains the objects that describe multiple queue
dsPibMQAlgDropGroup OBJECT-GROUP
OBJECTS {
dsMQAlgDropExceedNext
}
STATUS current
DESCRIPTION
"The Multiple Queue Measured Algorithmic Drop Group
contains the objects that describe multiple queue
measured algorithmic dropper operation and configuration."
::= { dsPolicyPibGroups 18 }
measured algorithmic dropper operation and configuration."
::= { dsPolicyPibGroups 18 }
dsPibRandomDropGroup OBJECT-GROUP
OBJECTS {
dsRandomDropPrid,
dsRandomDropMinThreshBytes,
dsRandomDropMinThreshPkts,
dsRandomDropMaxThreshBytes,
dsRandomDropMaxThreshPkts,
dsRandomDropProbMax,
dsRandomDropWeight,
dsRandomDropSamplingRate
}
STATUS current
DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group
for random dropper operation and configuration."
::= { dsPolicyPibGroups 19 }
dsPibRandomDropGroup OBJECT-GROUP
OBJECTS {
dsRandomDropPrid,
dsRandomDropMinThreshBytes,
dsRandomDropMinThreshPkts,
dsRandomDropMaxThreshBytes,
dsRandomDropMaxThreshPkts,
dsRandomDropProbMax,
dsRandomDropWeight,
dsRandomDropSamplingRate
}
STATUS current
DESCRIPTION
"The Random Drop Group augments the Algorithmic Drop Group
for random dropper operation and configuration."
::= { dsPolicyPibGroups 19 }
dsPibQGroup OBJECT-GROUP
OBJECTS {
dsQPrid, dsQNext, dsQMinRate, dsQMaxRate
}
STATUS current
DESCRIPTION
"The Queue Group contains the objects that describe
an interface type's queues."
::= { dsPolicyPibGroups 20 }
dsPibQGroup OBJECT-GROUP
OBJECTS {
dsQPrid, dsQNext, dsQMinRate, dsQMaxRate
}
STATUS current
DESCRIPTION
"The Queue Group contains the objects that describe
an interface type's queues."
::= { dsPolicyPibGroups 20 }
dsPibSchedulerGroup OBJECT-GROUP
OBJECTS {
dsSchedulerPrid, dsSchedulerNext, dsSchedulerMethod,
dsSchedulerMinRate, dsSchedulerMaxRate
}
STATUS current
DESCRIPTION
"The Scheduler Group contains the objects that
describe packet schedulers on interface types."
::= { dsPolicyPibGroups 21 }
dsPibSchedulerGroup OBJECT-GROUP
OBJECTS {
dsSchedulerPrid, dsSchedulerNext, dsSchedulerMethod,
dsSchedulerMinRate, dsSchedulerMaxRate
}
STATUS current
DESCRIPTION
"The Scheduler Group contains the objects that
describe packet schedulers on interface types."
::= { dsPolicyPibGroups 21 }
dsPibMinRateGroup OBJECT-GROUP
OBJECTS {
dsMinRatePrid, dsMinRatePriority,
dsMinRateAbsolute, dsMinRateRelative
}
STATUS current
DESCRIPTION
dsPibMinRateGroup OBJECT-GROUP
OBJECTS {
dsMinRatePrid, dsMinRatePriority,
dsMinRateAbsolute, dsMinRateRelative
}
STATUS current
DESCRIPTION
"The Minimum Rate Group contains the objects
that describe packet schedulers' parameters on interface
types."
::= { dsPolicyPibGroups 22 }
"The Minimum Rate Group contains the objects
that describe packet schedulers' parameters on interface
types."
::= { dsPolicyPibGroups 22 }
dsPibMaxRateGroup OBJECT-GROUP
OBJECTS {
dsMaxRatePrid, dsMaxRateId, dsMaxRateLevel,
dsMaxRateAbsolute, dsMaxRateRelative,
dsMaxRateThreshold
}
STATUS current
DESCRIPTION
"The Maximum Rate Group contains the objects
that describe packet schedulers' parameters on interface
types."
::= { dsPolicyPibGroups 23 }
dsPibMaxRateGroup OBJECT-GROUP
OBJECTS {
dsMaxRatePrid, dsMaxRateId, dsMaxRateLevel,
dsMaxRateAbsolute, dsMaxRateRelative,
dsMaxRateThreshold
}
STATUS current
DESCRIPTION
"The Maximum Rate Group contains the objects
that describe packet schedulers' parameters on interface
types."
::= { dsPolicyPibGroups 23 }
END
终止
Early versions of this specification were also co-authored by Michael Fine, John Seligson, Carol Bell, Andrew Smith, and Francis Reichmeyer.
该规范的早期版本也由Michael Fine、John Seligson、Carol Bell、Andrew Smith和Francis Reichmeyer共同编写。
This PIB builds on all the work that has gone into the Informal Management Model for DiffServ Routers and Management Information Base for the Differentiated Services Architecture.
该PIB建立在DiffServ路由器的非正式管理模型和区分服务体系结构的管理信息库的所有工作的基础上。
It has been developed with the active involvement of many people, but most notably Diana Rawlins, Martin Bokaemper, Walter Weiss, and Bert Wijnen.
它是在许多人的积极参与下发展起来的，但最著名的是戴安娜·罗林斯、马丁·博坎佩尔、沃尔特·韦斯和伯特·维恩。
The information contained in a PIB when transported by the COPS protocol [COPS-PR] may be sensitive, and its function of provisioning a PEP requires that only authorized communication take place.
当通过COPS协议[COPS-PR]传输时，PIB中包含的信息可能是敏感的，其提供政治公众人物的功能要求仅进行授权通信。
In this PIB, there are no PRCs which are sensitive in their own right, such as passwords or monetary amounts. But there are a number of PRCs in this PIB that may contain information that may be sensitive from a business perspective, in that they may represent a customer's service contract or the filters that the service provider chooses to apply to a customer's traffic. These PRCs have a PIB-ACCESS clause of install:
在此PIB中，不存在本身敏感的PRC，例如密码或货币金额。但该PIB中有许多PRC可能包含从业务角度来看可能敏感的信息，因为它们可能代表客户的服务合同或服务提供商选择应用于客户流量的过滤器。这些PRC有一个PIB-ACCESS安装条款：
dsDataPathTable, dsClfrTable, dsClfrElementTable, dsMeterTable, dsTBParamTable, dsActionTable, dsDscpMarkActTable, dsAlgDropTable, dsMQAlgDropTable, dsRandomDropTable, dsQTable, dsSchedulerTable, dsMinRateTable, dsMaxRateTable
dsDataPathTable、dsClfrTable、dsClfrElementTable、dsMeterTable、DSBPParamTable、dsActionTable、DSCPMarkActTable、dsAlgDropTable、DSQalDropTable、dsRandomDropTable、dsQTable、DSScheduleTable、dsMinRateTable、dsMaxRateTable
Malicious altering of the above PRCs may affect the DiffServ behavior of the device being provisioned.
恶意更改上述PRC可能会影响正在配置的设备的区分服务行为。
Malicious access of the above PRCs exposes policy information concerning how the device is provisioned.
恶意访问上述PRC会暴露有关如何配置设备的策略信息。
This PIB also contain PRCs with PIB-ACCESS clause of notify:
本PIB还包含PRC和PIB-ACCESS条款通知：
dsBaseIfCapsTAble, dsIfClassificationCapsTable, dsIfMeteringCapsTable, dsIfAlgDropCapsTable, dsIfQueueCapsTable, dsIfSchedulerCapsTable, dsIfMaxRateCapsTable, dsIfElmDepthCapsTable, dsIfElmLinkCapsTable
dsBaseIfCapsTAble、dsIfClassificationCapsTable、dsIfMeteringCapsTable、dsIfAlgDropCapsTable、dsIfQueueCapsTable、dsIfSchedulerCapsTable、dsIfMaxRateCapsTable、dsIfElmDepthCapsTable、dsIfElmLinkCapsTable
Malicious access of the above PRCs exposes information concerning the device being provisioned.
恶意访问上述PRC会暴露有关所配置设备的信息。
The use of IPSEC between PDP and PEP, as described in [COPS], provides the necessary protection.
如[COPS]所述，PDP和PEP之间使用IPSEC可提供必要的保护。
The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights.
IETF已收到关于本文件所含部分或全部规范的知识产权声明。有关更多信息，请查阅在线权利主张列表。
This document describes the dsPolicyPib Policy Information Base (PIB) modules for standardization under the "pib" branch registered with IANA. The IANA has assigned a PIB number (4) under the "pib" branch.
本文档描述了在IANA注册的“PIB”分支下用于标准化的dsPolicyPib政策信息库（PIB）模块。IANA已在“PIB”分支下分配了一个PIB编号（4）。
[SPPI] PIB SUBJECT-CATEGORIES are mapped to COPS Client Types. IANA Considerations for SUBJECT-CATEGORIES follow the same requirements as specified in [COPS] IANA Considerations for COPS Client Types. The DiffServ QoS PIB defines a new COPS Client Type in the Standards space. The IANA has assigned a COPS client type diffServ (2) as described in [COPS] IANA Considerations. IANA has updated the registry (http://www.iana.org/assignments/cops-parameters) for COPS Client Types as a result.
[SPPI]PIB主题类别映射到COPS客户端类型。主题类别的IANA注意事项遵循[COPS]IANA注意事项中针对COPS客户端类型规定的相同要求。DiffServ QoS PIB在标准空间中定义了一种新的COPS客户端类型。IANA已按照[COPS]IANA注意事项中所述，分配了一个COPS客户端类型diffServ（2）。IANA已经更新了注册表(http://www.iana.org/assignments/cops-parameters)因此，对于COPS客户端类型。
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and A. Sastry, "The COPS (Common Open Policy Service) Protocol", RFC 2748, January 2000.
[COPS]Boyle，J.，Cohen，R.，Durham，D.，Herzog，S.，Rajan，R.和A.Sastry，“COPS（公共开放政策服务）协议”，RFC 2748，2000年1月。
[COPS-PR] Chan, K., Durham, D., Gai, S., Herzog, S., McCloghrie, K., Reichmeyer, F., Seligson, J., Smith, A. and R. Yavatkar, "COPS Usage for Policy Provisioning", RFC 3084, March 2001.
[COPS-PR]Chan，K.，Durham，D.，Gai，S.，Herzog，S.，McCloghrie，K.，Reichmeyer，F.，Seligson，J.，Smith，A.和R.Yavatkar，“政策规定的COPS使用”，RFC 3084，2001年3月。
[SPPI] McCloghrie, K., Fine, M., Seligson, J., Chan, K., Hahn, S., Sahita, R., Smith, A. and F. Reichmeyer, "Structure of Policy Provisioning Information", RFC 3159, August 2001.
[SPPI]McCloghrie，K.，Fine，M.，Seligson，J.，Chan，K.，Hahn，S.，Sahita，R.，Smith，A.和F.Reichmeyer，“策略供应信息的结构”，RFC 3159，2001年8月。
[DSARCH] Carlson, M., Weiss, W., Blake, S., Wang, Z., Black, D. and E. Davies, "An Architecture for Differentiated Services", RFC 2475, December 1998.
[DSARCH]Carlson，M.，Weiss，W.，Blake，S.，Wang，Z.，Black，D.和E.Davies，“差异化服务架构”，RFC 24751998年12月。
[DSFIELD] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[DSFIELD]Nichols，K.，Blake，S.，Baker，F.和D.Black，“IPv4和IPv6报头中区分服务字段（DS字段）的定义”，RFC 24741998年12月。
[FR-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., Hahn, S., Sahita, R., Smith, A. and F. Reichmeyer, "Framework Policy Information Base", RFC 3318, March 2003.
[FR-PIB]Fine，M.，McCloghrie，K.，Seligson，J.，Chan，K.，Hahn，S.，Sahita，R.，Smith，A.和F.Reichmeyer，“框架政策信息库”，RFC 3318，2003年3月。
[RAP-FRAMEWORK] Yavatkar, R. and D. Pendarakis, "A Framework for Policy-based Admission Control", RFC 2753, January 2000.
[RAP-FRAMEWORK]Yavatkar，R.和D.Pendarakis，“基于政策的准入控制框架”，RFC 2753，2000年1月。
[SNMP-SMI] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[SNMP-SMI]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[MODEL] Bernet, Y., Blake, S., Grossman, D. and A. Smith "An Informal Management Model for Diffserv Routers", RFC 3290, May 2002.
[模型]Bernet，Y.，Blake，S.，Grossman，D.和A.Smith，“区分服务路由器的非正式管理模型”，RFC 32902002年5月。
[IFMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[IFMIB]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[DS-MIB] Baker, F., Chan, K. and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002.
[DS-MIB]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月。
[ACTQMGMT] Firoiu, V. and M. Borden, "A Study of Active Queue
Management for Congestion Control", March 2000, In
IEEE Infocom 2000, http://www.ieee-infocom.org/
2000/papers/405.pdf
[ACTQMGMT] Firoiu, V. and M. Borden, "A Study of Active Queue
Management for Congestion Control", March 2000, In
IEEE Infocom 2000, http://www.ieee-infocom.org/
2000/papers/405.pdf
[AQMROUTER] Misra, V., Gong, W. and D. Towsley, "Fluid-based
analysis of a network of AQM routers supporting TCP
flows with an application to RED", In SIGCOMM 2000,
http://www.acm.org/sigcomm/sigcomm2000/conf/paper/
sigcomm2000-4-3.ps.gz
[AQMROUTER] Misra, V., Gong, W. and D. Towsley, "Fluid-based
analysis of a network of AQM routers supporting TCP
flows with an application to RED", In SIGCOMM 2000,
http://www.acm.org/sigcomm/sigcomm2000/conf/paper/
sigcomm2000-4-3.ps.gz
[AF-PHB] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski, "Assured Forwarding PHB Group", RFC 2597, June 1999.
[AF-PHB]Heinanen，J.，Baker，F.，Weiss，W.和J.Wroclawski，“保付PHB集团”，RFC 25971999年6月。
[EF-PHB] Jacobson, V., Nichols, K. and K. Poduri, "An Expedited Forwarding PHB", RFC 2598, June 1999.
[EF-PHB]Jacobson，V.，Nichols，K.和K.Poduri，“快速转发PHB”，RFC 25981999年6月。
[INTSERVMIB] Baker, F., Krawczyk, J. and A. Sastry, "Integrated Services Management Information Base using SMIv2", RFC 2213, September 1997.
[INTSERVMIB]Baker，F.，Krawczyk，J.和A.Sastry，“使用SMIv2的集成服务管理信息库”，RFC 2213，1997年9月。
[QUEUEMGMT] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering, S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G., Partridge, C., Peterson, L., Ramakrishnan, K., Shenker, S., Wroclawski, J. and L. Zhang, "Recommendations on Queue Management and Congestion Avoidance in the Internet", RFC 2309, April 1998.
[QUEUEMGMT]Braden，B.，Clark，D.，Crowcroft，J.，Davie，B.，Deering，S.，Estrin，D.，Floyd，S.，Jacobson，V.，Minshall，G.，Partridge，C.，Peterson，L.，Ramakrishnan，K.，Shenker，S.，Wroclawski，J.和L.Zhang，“关于互联网中队列管理和拥塞避免的建议”，RFC 2309，1998年4月。
[SRTCM] Heinanen, J. and R. Guerin, "A Single Rate Three Color Marker", RFC 2697, September 1999.
[SRTCM]Heinanen，J.和R.Guerin，“单速率三色标记”，RFC 26971999年9月。
[TRTCM] Heinanen, J. and R. Guerin, "A Two Rate Three Color Marker", RFC 2698, September 1999.
[TRTCM]Heinanen，J.和R.Guerin，“双速率三色标记”，RFC 26981999年9月。
[TSWTCM] Fang, W., Seddigh, N. and B. Nandy, "A Time Sliding Window Three Colour Marker", RFC 2859, June 2000.
[TSWTCM]Fang，W.，Seddigh，N.和B.Nandy，“时间滑动窗口三色标记”，RFC 28592000年6月。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[SHAPER] Bonaventure, O. and S. De Cnodder, "A Rate Adaptive Shaper for Differentiated Services", RFC 2963, October 2000.
[SHAPER]Bonaventure，O.和S.De Cnodder，“差异化服务的速率自适应成形器”，RFC 2963，2000年10月。
[POLTERM] Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M., Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J. and S. Waldbusser, "Terminology for Policy-Based Management", RFC 3198, November 2001.
[POLTERM]Westerinen，A.，Schnizlein，J.，Strassner，J.，Scherling，M.，Quinn，B.，Herzog，S.，Huynh，A.，Carlson，M.，Perry，J.和S.Waldbusser，“基于政策的管理术语”，RFC 3198，2001年11月。
Kwok Ho Chan Nortel Networks, Inc. 600 Technology Park Drive Billerica, MA 01821 USA
郭浩灿北电网络有限公司，美国马萨诸塞州比尔里卡科技园大道600号，邮编01821
Phone: +1 978 288 8175
EMail: khchan@nortelnetworks.com
Phone: +1 978 288 8175
EMail: khchan@nortelnetworks.com
Ravi Sahita Intel Labs. 2111 NE 25th Avenue Hillsboro, OR 97124 USA
拉维萨希塔英特尔实验室。美国希尔斯伯勒东北25大道2111号，邮编：97124
Phone: +1 503 712 1554
EMail: ravi.sahita@intel.com
Phone: +1 503 712 1554
EMail: ravi.sahita@intel.com
Scott Hahn Intel 2111 NE 25th Avenue Hillsboro, OR 97124 USA
斯科特哈恩英特尔2111东北25大道希尔斯伯勒，或97124美国
Phone: +1 503 264 8231
EMail: scott.hahn@intel.com
Phone: +1 503 264 8231
EMail: scott.hahn@intel.com
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA
Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。