Network Working Group Y. Snir
Request for Comments: 3644 Y. Ramberg
Category: Standards Track Cisco Systems
J. Strassner
Intelliden
R. Cohen
Ntear LLC
B. Moore
IBM
November 2003
Network Working Group Y. Snir
Request for Comments: 3644 Y. Ramberg
Category: Standards Track Cisco Systems
J. Strassner
Intelliden
R. Cohen
Ntear LLC
B. Moore
IBM
November 2003
Policy Quality of Service (QoS) Information Model
策略服务质量（QoS）信息模型
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This document presents an object-oriented information model for representing Quality of Service (QoS) network management policies. This document is based on the IETF Policy Core Information Model and its extensions. It defines an information model for QoS enforcement for differentiated and integrated services using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol.
本文档提供了一个面向对象的信息模型，用于表示服务质量（QoS）网络管理策略。本文档基于IETF策略核心信息模型及其扩展。它定义了一个信息模型，用于使用策略实现区分服务和集成服务的QoS实施。需要注意的是，本文档定义了一个信息模型，根据定义，该模型独立于任何特定的数据存储机制和访问协议。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. The Process of QoS Policy Definition. . . . . . . . . . 5
1.2. Design Goals and Their Ramifications. . . . . . . . . . 8
1.2.1. Policy-Definition Oriented. . . . . . . . . . . 8
1.2.1.1. Rule-based Modeling . . . . . . . . . 9
1.2.1.2. Organize Information Hierarchically . 9
1.2.1.3. Goal-Oriented Policy Definition . . . 10
1.2.2. Policy Domain Model. . . . . . . . . . . . . . . 11
1.2.2.1. Model QoS Policy in a Device- and
Vendor-Independent Manner . . . . . . 11
1.2.2.2. Use Roles for Mapping Policy to
Network Devices . . . . . . . . . . . 11
1.2.2.3. Reusability . . . . . . . . . . . . . 12
1.2.3. Enforceable Policy. . . . . . . . . . . . . . . 12
1.2.4. QPIM Covers Both Signaled And Provisioned QoS . 14
1.2.5. Interoperability for PDPs and Management
Applications. . . . . . . . . . . . . . . . . . 14
1.3. Modeling Abstract QoS Policies. . . . . . . . . . . . . 15
1.4. Rule Hierarchy. . . . . . . . . . . . . . . . . . . . . 17
1.4.1. Use of Hierarchy Within Bandwidth Allocation
Policies. . . . . . . . . . . . . . . . . . . . 17
1.4.2. Use of Rule Hierarchy to Describe Drop
Threshold Policies. . . . . . . . . . . . . . . 21
1.4.3. Restrictions of the Use of Hierarchy Within
QPIM. . . . . . . . . . . . . . . . . . . . . . 22
1.5. Intended Audiences. . . . . . . . . . . . . . . . . . . 23
2. Class Hierarchies . . . . . . . . . . . . . . . . . . . . . . 23
2.1. Inheritance Hierarchy . . . . . . . . . . . . . . . . . 23
2.2. Relationship Hierarchy. . . . . . . . . . . . . . . . . 26
3. QoS Actions . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1. Overview. . . . . . . . . . . . . . . . . . . . . . . . 26
3.2. RSVP Policy Actions . . . . . . . . . . . . . . . . . . 27
3.2.1. Example: Controlling COPS Stateless Decision. . 28
3.2.2. Example: Controlling the COPS Replace Decision. 29
3.3. Provisioning Policy Actions . . . . . . . . . . . . . . 29
3.3.1. Admission Actions: Controlling Policers and
Shapers . . . . . . . . . . . . . . . . . . . . 29
3.3.2. Controlling Markers . . . . . . . . . . . . . . 32
3.3.3. Controlling Edge Policies - Examples. . . . . . 33
3.4. Per-Hop Behavior Actions. . . . . . . . . . . . . . . . 34
3.4.1. Controlling Bandwidth and Delay . . . . . . . . 35
3.4.2. Congestion Control Actions. . . . . . . . . . . 35
3.4.3. Using Hierarchical Policies: Examples for PHB
Actions . . . . . . . . . . . . . . . . . . . . 36
4. Traffic Profiles. . . . . . . . . . . . . . . . . . . . . . . 38
4.1. Provisioning Traffic Profiles . . . . . . . . . . . . . 38
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. The Process of QoS Policy Definition. . . . . . . . . . 5
1.2. Design Goals and Their Ramifications. . . . . . . . . . 8
1.2.1. Policy-Definition Oriented. . . . . . . . . . . 8
1.2.1.1. Rule-based Modeling . . . . . . . . . 9
1.2.1.2. Organize Information Hierarchically . 9
1.2.1.3. Goal-Oriented Policy Definition . . . 10
1.2.2. Policy Domain Model. . . . . . . . . . . . . . . 11
1.2.2.1. Model QoS Policy in a Device- and
Vendor-Independent Manner . . . . . . 11
1.2.2.2. Use Roles for Mapping Policy to
Network Devices . . . . . . . . . . . 11
1.2.2.3. Reusability . . . . . . . . . . . . . 12
1.2.3. Enforceable Policy. . . . . . . . . . . . . . . 12
1.2.4. QPIM Covers Both Signaled And Provisioned QoS . 14
1.2.5. Interoperability for PDPs and Management
Applications. . . . . . . . . . . . . . . . . . 14
1.3. Modeling Abstract QoS Policies. . . . . . . . . . . . . 15
1.4. Rule Hierarchy. . . . . . . . . . . . . . . . . . . . . 17
1.4.1. Use of Hierarchy Within Bandwidth Allocation
Policies. . . . . . . . . . . . . . . . . . . . 17
1.4.2. Use of Rule Hierarchy to Describe Drop
Threshold Policies. . . . . . . . . . . . . . . 21
1.4.3. Restrictions of the Use of Hierarchy Within
QPIM. . . . . . . . . . . . . . . . . . . . . . 22
1.5. Intended Audiences. . . . . . . . . . . . . . . . . . . 23
2. Class Hierarchies . . . . . . . . . . . . . . . . . . . . . . 23
2.1. Inheritance Hierarchy . . . . . . . . . . . . . . . . . 23
2.2. Relationship Hierarchy. . . . . . . . . . . . . . . . . 26
3. QoS Actions . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1. Overview. . . . . . . . . . . . . . . . . . . . . . . . 26
3.2. RSVP Policy Actions . . . . . . . . . . . . . . . . . . 27
3.2.1. Example: Controlling COPS Stateless Decision. . 28
3.2.2. Example: Controlling the COPS Replace Decision. 29
3.3. Provisioning Policy Actions . . . . . . . . . . . . . . 29
3.3.1. Admission Actions: Controlling Policers and
Shapers . . . . . . . . . . . . . . . . . . . . 29
3.3.2. Controlling Markers . . . . . . . . . . . . . . 32
3.3.3. Controlling Edge Policies - Examples. . . . . . 33
3.4. Per-Hop Behavior Actions. . . . . . . . . . . . . . . . 34
3.4.1. Controlling Bandwidth and Delay . . . . . . . . 35
3.4.2. Congestion Control Actions. . . . . . . . . . . 35
3.4.3. Using Hierarchical Policies: Examples for PHB
Actions . . . . . . . . . . . . . . . . . . . . 36
4. Traffic Profiles. . . . . . . . . . . . . . . . . . . . . . . 38
4.1. Provisioning Traffic Profiles . . . . . . . . . . . . . 38
4.2. RSVP Traffic Profiles . . . . . . . . . . . . . . . . . 39
5. Pre-Defined QoS-Related Variables . . . . . . . . . . . . . . 40
6. QoS Related Values. . . . . . . . . . . . . . . . . . . . . . 42
7. Class Definitions: Association Hierarchy. . . . . . . . . . . 44
7.1. The Association "QoSPolicyTrfcProfInAdmissionAction". . 44
7.1.1. The Reference "Antecedent". . . . . . . . . . . 44
7.1.2. The Reference "Dependent" . . . . . . . . . . . 44
7.2. The Association "PolicyConformAction" . . . . . . . . . 44
7.2.1. The Reference "Antecedent". . . . . . . . . . . 45
7.2.2. The Reference "Dependent" . . . . . . . . . . . 45
7.3. The Association "QoSPolicyExceedAction" . . . . . . . . 45
7.3.1. The Reference "Antecedent". . . . . . . . . . . 46
7.3.2. The Reference "Dependent" . . . . . . . . . . . 46
7.4. The Association "PolicyViolateAction" . . . . . . . . . 46
7.4.1. The Reference "Antecedent". . . . . . . . . . . 46
7.4.2. The Reference "Dependent" . . . . . . . . . . . 47
7.5 The Aggregation
"QoSPolicyRSVPVariableInRSVPSimplePolicyAction" . . . . 47
7.5.1. The Reference "GroupComponent". . . . . . . . . 47
7.5.2. The Reference "PartComponent" . . . . . . . . . 47
8. Class Definitions: Inheritance Hierarchy. . . . . . . . . . . 48
8.1. The Class QoSPolicyDiscardAction. . . . . . . . . . . . 48
8.2. The Class QoSPolicyAdmissionAction. . . . . . . . . . . 48
8.2.1. The Property qpAdmissionScope . . . . . . . . . 48
8.3. The Class QoSPolicyPoliceAction . . . . . . . . . . . . 49
8.4. The Class QoSPolicyShapeAction. . . . . . . . . . . . . 49
8.5. The Class QoSPolicyRSVPAdmissionAction. . . . . . . . . 50
8.5.1. The Property qpRSVPWarnOnly . . . . . . . . . . 50
8.5.2. The Property qpRSVPMaxSessions. . . . . . . . . 51
8.6. The Class QoSPolicyPHBAction. . . . . . . . . . . . . . 51
8.6.1. The Property qpMaxPacketSize. . . . . . . . . . 51
8.7. The Class QoSPolicyBandwidthAction. . . . . . . . . . . 52
8.7.1. The Property qpForwardingPriority . . . . . . . 52
8.7.2. The Property qpBandwidthUnits . . . . . . . . . 52
8.7.3. The Property qpMinBandwidth . . . . . . . . . . 53
8.7.4. The Property qpMaxBandwidth . . . . . . . . . . 53
8.7.5. The Property qpMaxDelay . . . . . . . . . . . . 53
8.7.6. The Property qpMaxJitter. . . . . . . . . . . . 53
8.7.7. The Property qpFairness . . . . . . . . . . . . 54
8.8. The Class QoSPolicyCongestionControlAction. . . . . . . 54
8.8.1. The Property qpQueueSizeUnits . . . . . . . . . 54
8.8.2. The Property qpQueueSize. . . . . . . . . . . . 55
8.8.3. The Property qpDropMethod . . . . . . . . . . . 55
8.8.4. The Property qpDropThresholdUnits . . . . . . . 55
8.8.5. The Property qpDropMinThresholdValue. . . . . . 55
8.8.6. The Property qpDropMaxThresholdValue. . . . . . 56
8.9. The Class QoSPolicyTrfcProf . . . . . . . . . . . . . . 56
8.10. The Class QoSPolicyTokenBucketTrfcProf. . . . . . . . . 57
4.2. RSVP Traffic Profiles . . . . . . . . . . . . . . . . . 39
5. Pre-Defined QoS-Related Variables . . . . . . . . . . . . . . 40
6. QoS Related Values. . . . . . . . . . . . . . . . . . . . . . 42
7. Class Definitions: Association Hierarchy. . . . . . . . . . . 44
7.1. The Association "QoSPolicyTrfcProfInAdmissionAction". . 44
7.1.1. The Reference "Antecedent". . . . . . . . . . . 44
7.1.2. The Reference "Dependent" . . . . . . . . . . . 44
7.2. The Association "PolicyConformAction" . . . . . . . . . 44
7.2.1. The Reference "Antecedent". . . . . . . . . . . 45
7.2.2. The Reference "Dependent" . . . . . . . . . . . 45
7.3. The Association "QoSPolicyExceedAction" . . . . . . . . 45
7.3.1. The Reference "Antecedent". . . . . . . . . . . 46
7.3.2. The Reference "Dependent" . . . . . . . . . . . 46
7.4. The Association "PolicyViolateAction" . . . . . . . . . 46
7.4.1. The Reference "Antecedent". . . . . . . . . . . 46
7.4.2. The Reference "Dependent" . . . . . . . . . . . 47
7.5 The Aggregation
"QoSPolicyRSVPVariableInRSVPSimplePolicyAction" . . . . 47
7.5.1. The Reference "GroupComponent". . . . . . . . . 47
7.5.2. The Reference "PartComponent" . . . . . . . . . 47
8. Class Definitions: Inheritance Hierarchy. . . . . . . . . . . 48
8.1. The Class QoSPolicyDiscardAction. . . . . . . . . . . . 48
8.2. The Class QoSPolicyAdmissionAction. . . . . . . . . . . 48
8.2.1. The Property qpAdmissionScope . . . . . . . . . 48
8.3. The Class QoSPolicyPoliceAction . . . . . . . . . . . . 49
8.4. The Class QoSPolicyShapeAction. . . . . . . . . . . . . 49
8.5. The Class QoSPolicyRSVPAdmissionAction. . . . . . . . . 50
8.5.1. The Property qpRSVPWarnOnly . . . . . . . . . . 50
8.5.2. The Property qpRSVPMaxSessions. . . . . . . . . 51
8.6. The Class QoSPolicyPHBAction. . . . . . . . . . . . . . 51
8.6.1. The Property qpMaxPacketSize. . . . . . . . . . 51
8.7. The Class QoSPolicyBandwidthAction. . . . . . . . . . . 52
8.7.1. The Property qpForwardingPriority . . . . . . . 52
8.7.2. The Property qpBandwidthUnits . . . . . . . . . 52
8.7.3. The Property qpMinBandwidth . . . . . . . . . . 53
8.7.4. The Property qpMaxBandwidth . . . . . . . . . . 53
8.7.5. The Property qpMaxDelay . . . . . . . . . . . . 53
8.7.6. The Property qpMaxJitter. . . . . . . . . . . . 53
8.7.7. The Property qpFairness . . . . . . . . . . . . 54
8.8. The Class QoSPolicyCongestionControlAction. . . . . . . 54
8.8.1. The Property qpQueueSizeUnits . . . . . . . . . 54
8.8.2. The Property qpQueueSize. . . . . . . . . . . . 55
8.8.3. The Property qpDropMethod . . . . . . . . . . . 55
8.8.4. The Property qpDropThresholdUnits . . . . . . . 55
8.8.5. The Property qpDropMinThresholdValue. . . . . . 55
8.8.6. The Property qpDropMaxThresholdValue. . . . . . 56
8.9. The Class QoSPolicyTrfcProf . . . . . . . . . . . . . . 56
8.10. The Class QoSPolicyTokenBucketTrfcProf. . . . . . . . . 57
8.10.1. The Property qpTBRate . . . . . . . . . . . . . 57
8.10.2. The Property qpTBNormalBurst. . . . . . . . . . 57
8.10.3. The Property qpTBExcessBurst. . . . . . . . . . 57
8.11. The Class QoSPolicyIntServTrfcProf. . . . . . . . . . . 57
8.11.1. The Property qpISTokenRate. . . . . . . . . . . 58
8.11.2. The Property qpISPeakRate . . . . . . . . . . . 58
8.11.3. The Property qpISBucketSize . . . . . . . . . . 58
8.11.4. The Property qpISResvRate . . . . . . . . . . . 58
8.11.5. The Property qpISResvSlack. . . . . . . . . . . 59
8.11.6. The Property qpISMinPolicedUnit . . . . . . . . 59
8.11.7. The Property qpISMaxPktSize . . . . . . . . . . 59
8.12. The Class QoSPolicyAttributeValue . . . . . . . . . . . 59
8.12.1. The Property qpAttributeName. . . . . . . . . . 60
8.12.2. The Property qpAttributeValueList . . . . . . . 60
8.13. The Class QoSPolicyRSVPVariable . . . . . . . . . . . . 60
8.14. The Class QoSPolicyRSVPSourceIPv4Variable . . . . . . . 61
8.15. The Class QoSPolicyRSVPDestinationIPv4Variable. . . . . 61
8.16. The Class QoSPolicyRSVPSourceIPv6Variable . . . . . . . 62
8.17. The Class QoSPolicyRSVPDestinationIPv6Variable. . . . . 62
8.18. The Class QoSPolicyRSVPSourcePortVariable . . . . . . . 62
8.19. The Class QoSPolicyRSVPDestinationPortVariable. . . . . 63
8.20. The Class QoSPolicyRSVPIPProtocolVariable . . . . . . . 63
8.21. The Class QoSPolicyRSVPIPVersionVariable. . . . . . . . 63
8.22. The Class QoSPolicyRSVPDCLASSVariable . . . . . . . . . 64
8.23. The Class QoSPolicyRSVPStyleVariable. . . . . . . . . . 64
8.24. The Class QoSPolicyRSVPIntServVariable. . . . . . . . . 65
8.25. The Class QoSPolicyRSVPMessageTypeVariable. . . . . . . 65
8.26. The Class QoSPolicyRSVPPreemptionPriorityVariable . . . 65
8.27. The Class QoSPolicyRSVPPreemptionDefPriorityVariable. . 66
8.28. The Class QoSPolicyRSVPUserVariable . . . . . . . . . . 66
8.29. The Class QoSPolicyRSVPApplicationVariable. . . . . . . 66
8.30. The Class QoSPolicyRSVPAuthMethodVariable . . . . . . . 67
8.31. The Class QosPolicyDNValue. . . . . . . . . . . . . . . 67
8.31.1. The Property qpDNList . . . . . . . . . . . . . 68
8.32. The Class QoSPolicyRSVPSimpleAction . . . . . . . . . . 68
8.32.1. The Property qpRSVPActionType . . . . . . . . . 68
9. Intellectual Property Rights Statement. . . . . . . . . . . . 69
10. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 69
11. Security Considerations . . . . . . . . . . . . . . . . . . . 69
12. References. . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.1. Normative References . . . . . . . . . . . . . . . . . 70
12.2. Informative References . . . . . . . . . . . . . . . . 70
13. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . 72
14. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 73
8.10.1. The Property qpTBRate . . . . . . . . . . . . . 57
8.10.2. The Property qpTBNormalBurst. . . . . . . . . . 57
8.10.3. The Property qpTBExcessBurst. . . . . . . . . . 57
8.11. The Class QoSPolicyIntServTrfcProf. . . . . . . . . . . 57
8.11.1. The Property qpISTokenRate. . . . . . . . . . . 58
8.11.2. The Property qpISPeakRate . . . . . . . . . . . 58
8.11.3. The Property qpISBucketSize . . . . . . . . . . 58
8.11.4. The Property qpISResvRate . . . . . . . . . . . 58
8.11.5. The Property qpISResvSlack. . . . . . . . . . . 59
8.11.6. The Property qpISMinPolicedUnit . . . . . . . . 59
8.11.7. The Property qpISMaxPktSize . . . . . . . . . . 59
8.12. The Class QoSPolicyAttributeValue . . . . . . . . . . . 59
8.12.1. The Property qpAttributeName. . . . . . . . . . 60
8.12.2. The Property qpAttributeValueList . . . . . . . 60
8.13. The Class QoSPolicyRSVPVariable . . . . . . . . . . . . 60
8.14. The Class QoSPolicyRSVPSourceIPv4Variable . . . . . . . 61
8.15. The Class QoSPolicyRSVPDestinationIPv4Variable. . . . . 61
8.16. The Class QoSPolicyRSVPSourceIPv6Variable . . . . . . . 62
8.17. The Class QoSPolicyRSVPDestinationIPv6Variable. . . . . 62
8.18. The Class QoSPolicyRSVPSourcePortVariable . . . . . . . 62
8.19. The Class QoSPolicyRSVPDestinationPortVariable. . . . . 63
8.20. The Class QoSPolicyRSVPIPProtocolVariable . . . . . . . 63
8.21. The Class QoSPolicyRSVPIPVersionVariable. . . . . . . . 63
8.22. The Class QoSPolicyRSVPDCLASSVariable . . . . . . . . . 64
8.23. The Class QoSPolicyRSVPStyleVariable. . . . . . . . . . 64
8.24. The Class QoSPolicyRSVPIntServVariable. . . . . . . . . 65
8.25. The Class QoSPolicyRSVPMessageTypeVariable. . . . . . . 65
8.26. The Class QoSPolicyRSVPPreemptionPriorityVariable . . . 65
8.27. The Class QoSPolicyRSVPPreemptionDefPriorityVariable. . 66
8.28. The Class QoSPolicyRSVPUserVariable . . . . . . . . . . 66
8.29. The Class QoSPolicyRSVPApplicationVariable. . . . . . . 66
8.30. The Class QoSPolicyRSVPAuthMethodVariable . . . . . . . 67
8.31. The Class QosPolicyDNValue. . . . . . . . . . . . . . . 67
8.31.1. The Property qpDNList . . . . . . . . . . . . . 68
8.32. The Class QoSPolicyRSVPSimpleAction . . . . . . . . . . 68
8.32.1. The Property qpRSVPActionType . . . . . . . . . 68
9. Intellectual Property Rights Statement. . . . . . . . . . . . 69
10. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 69
11. Security Considerations . . . . . . . . . . . . . . . . . . . 69
12. References. . . . . . . . . . . . . . . . . . . . . . . . . . 70
12.1. Normative References . . . . . . . . . . . . . . . . . 70
12.2. Informative References . . . . . . . . . . . . . . . . 70
13. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . 72
14. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 73
The QoS Policy Information Model (QPIM) establishes a standard framework and constructs for specifying and representing policies that administer, manage, and control access to network QoS resources. Such policies will be referred to as "QoS policies" in this document. The framework consists of a set of classes and relationships that are organized in an object-oriented information model. It is agnostic of any specific Policy Decision Point (PDP) or Policy Enforcement Point (PEP) (see [TERMS] for definitions) implementation, and independent of any particular QoS implementation mechanism.
QoS策略信息模型（QPIM）建立了一个标准框架和结构，用于指定和表示管理、管理和控制对网络QoS资源访问的策略。此类策略在本文件中称为“QoS策略”。该框架由一组以面向对象的信息模型组织的类和关系组成。它与任何特定的策略决策点（PDP）或策略实施点（PEP）（请参见[术语]中的定义）实现无关，并且与任何特定的QoS实现机制无关。
QPIM is designed to represent QoS policy information for large-scale policy domains (the term "policy domain" is defined in [TERMS]). A primary goal of this information model is to assist human administrators in their definition of policies to control QoS resources (as opposed to individual network element configuration). The process of creating QPIM data instances is fed by business rules, network topology and QoS methodology (e.g., Differentiated Services).
QPIM旨在表示大规模策略域的QoS策略信息（术语“策略域”在[术语]中定义）。此信息模型的主要目标是帮助管理员定义控制QoS资源的策略（与单个网元配置相反）。创建QPIM数据实例的过程由业务规则、网络拓扑和QoS方法（例如，区分服务）提供。
This document is based on the IETF Policy Core Information Model and its extensions as specified by [PCIM] and [PCIMe]. QPIM builds upon these two documents to define an information model for QoS enforcement for differentiated and integrated services ([DIFFSERV] and [INTSERV], respectively) using policy. It is important to note that this document defines an information model, which by definition is independent of any particular data storage mechanism and access protocol. This enables various data models (e.g., directory schemata, relational database schemata, and SNMP MIBs) to be designed and implemented according to a single uniform model.
本文件基于[PCIM]和[PCIMe]指定的IETF策略核心信息模型及其扩展。QPIM以这两个文档为基础，使用策略为区分服务和集成服务（分别为[DIFFSERV]和[INTSERV]）定义QoS实施的信息模型。需要注意的是，本文档定义了一个信息模型，根据定义，该模型独立于任何特定的数据存储机制和访问协议。这使得各种数据模型（例如，目录模式、关系数据库模式和SNMP MIB）能够根据单个统一模型进行设计和实现。
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 BCP 14, RFC 2119 [KEYWORDS].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[关键词]中的描述进行解释。
This section describes the process of using QPIM for the definition QoS policy for a policy domain. Figure 1 illustrates information flow and not the actual procedure, which has several loops and feedback not depicted.
本节描述使用QPIM定义策略域的QoS策略的过程。图1说明了信息流，而不是实际的过程，其中有几个循环和反馈没有描述。
---------- ---------- -----------
| Business | | Topology | | QoS |
| Policy | | | |Methodology|
---------- ---------- -----------
| | |
| | |
------------------------------------
|
V
---------------
| QPIM/PCIM(e) |
| modeling |
---------------
|
| --------------
|<----------| Device info, |
| | capabilities |
| --------------
V
(---------------)
( device )---)
( configuration ) )---)
(---------------) ) )
(--------------) )
(-------------)
---------- ---------- -----------
| Business | | Topology | | QoS |
| Policy | | | |Methodology|
---------- ---------- -----------
| | |
| | |
------------------------------------
|
V
---------------
| QPIM/PCIM(e) |
| modeling |
---------------
|
| --------------
|<----------| Device info, |
| | capabilities |
| --------------
V
(---------------)
( device )---)
( configuration ) )---)
(---------------) ) )
(--------------) )
(-------------)
Figure 1: The QoS definition information flow
图1:QoS定义信息流
The process of QoS policy definition is dependent on three types of information: the topology of the network devices under management, the particular type of QoS methodology used (e.g., DiffServ) and the business rules and requirements for specifying service(s) [TERMS] delivered by the network. Both topology and business rules are outside the scope of QPIM. However, important facets of both must be known and understood for correctly specifying the QoS policy.
QoS策略定义的过程取决于三种类型的信息：被管理的网络设备的拓扑结构、使用的特定类型的QoS方法（例如，DiffServ）以及用于指定网络提供的服务[条款]的业务规则和要求。拓扑和业务规则都不在QPIM的范围内。然而，为了正确地指定QoS策略，必须了解和理解两者的重要方面。
Typically, the process of QoS policy definition relies on a methodology based on one or more QoS methodologies. For example, the DiffServ methodology may be employed in the QoS policy definition process.
通常，QoS策略定义的过程依赖于基于一个或多个QoS方法的方法。例如，可以在QoS策略定义过程中采用区分服务方法。
The topology of the network consists of an inventory of the network elements that make up the network and the set of paths that traffic may take through the network. For example, a network administrator may decide to use the DiffServ architectural model [DIFFSERV] and classify network devices using the roles "boundary" and "core" (see [TERMS] for a definition of role, and [PCIM] for an explanation of
网络拓扑由构成网络的网络元件清单和流量可能通过网络的路径集组成。例如，网络管理员可能决定使用DiffServ架构模型[DiffServ]，并使用角色“边界”和“核心”对网络设备进行分类（角色定义见[TERMS]，角色解释见[PCIM]
how they are used in the policy framework). While this is not a complete topological view of the network, many times it may suffice for the purpose of QoS policy definition.
如何在政策框架中使用它们）。虽然这不是一个完整的网络拓扑视图，但在很多情况下，它可能足以用于QoS策略定义。
Business rules are informal sets of requirements for specifying the behavior of various types of traffic that may traverse the network. For example, the administrator may be instructed to implement policy such that VoIP traffic manifests behavior that is similar to legacy voice traffic over telephone networks. Note that this business rule (indirectly) prescribes specific behavior for this traffic type (VoIP), for example in terms of minimal delay, jitter and loss. Other traffic types, such as WEB buying transactions, system backup traffic, video streaming, etc., will express their traffic conditioning requirements in different terms. Again, this information is required not by QPIM itself, but by the overall policy management system that uses QPIM. QPIM is used to help map the business rules into a form that defines the requirements for conditioning different types of traffic in the network.
业务规则是一组非正式的需求，用于指定可能穿越网络的各种类型流量的行为。例如，可以指示管理员实施策略，使得VoIP业务表现出类似于电话网络上的传统语音业务的行为。请注意，此业务规则（间接）规定了此流量类型（VoIP）的特定行为，例如最小延迟、抖动和丢失。其他流量类型，如网络购买交易、系统备份流量、视频流等，将以不同的术语表达其流量调节要求。同样，这些信息不是QPIM本身所需要的，而是使用QPIM的整个策略管理系统所需要的。QPIM用于帮助将业务规则映射到一个表单中，该表单定义了调节网络中不同类型流量的要求。
The topology, QoS methodology, and business rules are necessary prerequisites for defining traffic conditioning. QPIM enables a set of tools for specifying traffic conditioning policy in a standard manner. Using a standard QoS policy information model such as QPIM is needed also because different devices can have markedly different capabilities. Even the same model of equipment can have different functionality if the network operating system and software running in those devices is different. Therefore, a means is required to specify functionality in a standard way that is independent of the capabilities of different vendors' devices. This is the role of QPIM.
拓扑、QoS方法和业务规则是定义流量调节的必要先决条件。QPIM支持一组用于以标准方式指定流量调节策略的工具。还需要使用标准QoS策略信息模型（如QPIM），因为不同的设备可能具有明显不同的功能。如果在这些设备中运行的网络操作系统和软件不同，那么即使是同一型号的设备也可能具有不同的功能。因此，需要一种方法以独立于不同供应商设备功能的标准方式指定功能。这就是QPIM的角色。
In a typical scenario, the administrator would first determine the role(s) that each interface of each network element plays in the overall network topology. These roles define the functions supplied by a given network element independent of vendor and device type. The [PCIM] and [PCIMe] documents define the concept of a role. Roles can be used to identify what parts of the network need which type of traffic conditioning. For example, network interface cards that are categorized as "core" interfaces can be assigned the role name "core-interface". This enables the administrator to design policies to configure all interfaces having the role "core-interface" independent of the actual physical devices themselves. QPIM uses roles to help the administrator map a given set of devices or interfaces to a given set of policy constructs.
在典型场景中，管理员首先确定每个网元的每个接口在整个网络拓扑中扮演的角色。这些角色定义了给定网元提供的功能，这些功能与供应商和设备类型无关。[PCIM]和[PCIMe]文档定义了角色的概念。角色可用于确定网络的哪些部分需要哪种类型的流量调节。例如，可以为归类为“核心”接口的网络接口卡分配角色名称“核心接口”。这使管理员能够设计策略来配置具有“核心接口”角色的所有接口，而不依赖于实际物理设备本身。QPIM使用角色帮助管理员将一组给定的设备或接口映射到一组给定的策略构造。
The policy constructs define the functionality required to perform the desired traffic conditioning for particular traffic type(s). The functions themselves depend on the particular type of networking technologies chosen. For example, the DiffServ methodology encourages us to aggregate similar types of traffic by assigning to each traffic class a particular per-hop forwarding behavior on each node. RSVP enables bandwidth to be reserved. These two methodologies can be used separately or in conjunction, as defined by the appropriate business policy. QPIM provides specific classes to enable DiffServ and RSVP conditioning to be modeled.
策略构造定义了为特定流量类型执行所需流量调节所需的功能。功能本身取决于所选择的特定类型的网络技术。例如，DiffServ方法鼓励我们通过在每个节点上为每个流量类别分配特定的每跳转发行为来聚合类似类型的流量。RSVP允许保留带宽。根据适当的业务策略的定义，这两种方法可以单独使用，也可以结合使用。QPIM提供了特定的类来支持对DiffServ和RSVP条件进行建模。
The QPIM class definitions are used to create instances of various policy constructs such as QoS actions and conditions that may be hierarchically organized in rules and groups (PolicyGroup and PolicyRule as defined in [PCIM] and [PCIMe]). Examples of policy actions are rate limiting, jitter control and bandwidth allocation. Policy conditions are constructs that can select traffic according to a complex Boolean expression.
QPIM类定义用于创建各种策略构造（如QoS操作和条件）的实例，这些策略构造可以在规则和组中分层组织（PolicyGroup和PolicyRule如[PCIM]和[PCIMe]中定义）。策略操作的示例包括速率限制、抖动控制和带宽分配。策略条件是可以根据复杂布尔表达式选择流量的结构。
A hierarchical organization was chosen for two reasons. First, it best reflects the way humans tend to think about complex policy. Second, it enables policy to be easily mapped onto administrative organizations, as the hierarchical organization of policy mirrors most administrative organizations. It is important to note that the policy definition process described here is done independent of any specific device capabilities and configuration options. The policy definition is completely independent from the details of the implementation and the configuration interface of individual network elements, as well as of the mechanisms that a network element can use to condition traffic.
选择分级组织有两个原因。首先，它最好地反映了人类对复杂政策的思考方式。其次，它使策略能够轻松映射到管理组织，因为策略的分层组织反映了大多数管理组织。需要注意的是，此处描述的策略定义过程独立于任何特定的设备功能和配置选项。策略定义完全独立于各个网元的实现细节和配置接口，以及网元可用于调节流量的机制。
This section explains the QPIM design goals and how these goals are addressed in this document. This section also describes the ramifications of the design goals and the design decisions made in developing QPIM.
本节介绍QPIM设计目标以及本文档中如何实现这些目标。本节还描述了开发QPIM过程中设计目标和设计决策的影响。
The primary design goal of QPIM is to model policies controlling QoS behavior in a way that as closely as possible reflects the way humans tend to think about policy. Therefore, QPIM is designed to address the needs of policy definition and management, and not device/network configuration.
QPIM的主要设计目标是对控制QoS行为的策略进行建模，以尽可能地反映人类对策略的思考方式。因此，QPIM旨在满足策略定义和管理的需要，而不是设备/网络配置的需要。
There are several ramifications of this design goal. First, QPIM uses rules to define policies, based on [PCIM] and [PCIMe]. Second, QPIM uses hierarchical organizations of policies and policy information extensively. Third, QPIM does not force the policy writer to specify all implementation details; rather, it assumes that configuration agents (PDPs) interpret the policies and match them to suit the needs of device-specific configurations.
这个设计目标有几个分支。首先，QPIM使用规则定义基于[PCIM]和[PCIMe]的策略。其次，QPIM广泛使用策略和策略信息的分层组织。第三，QPIM不强制策略编写器指定所有实现细节；相反，它假设配置代理（PDP）解释策略并匹配它们以满足特定于设备的配置的需要。
Policy is best described using rule-based modeling as explained and described in [PCIM] and [PCIMe]. A QoS policy rule is structured as a condition clause and an action clause. The semantics are simple: if the condition clause evaluates to TRUE, then a set of QoS actions (specified in the action clause) can be executed. For example, the rule:
策略最好使用基于规则的建模进行描述，如[PCIM]和[PCIMe]中所述。QoS策略规则的结构是一个条件子句和一个动作子句。语义很简单：如果condition子句的计算结果为TRUE，则可以执行一组QoS操作（在action子句中指定）。例如，规则：
"WEB traffic should receive at least 50% of the available bandwidth resources or more, when more is available"
当有更多可用带宽资源时，WEB流量应至少接收可用带宽资源的50%或更多
can be formalized as:
可形式化为：
"<If protocol == HTTP> then <minimum BW = 50%>"
"<If protocol == HTTP> then <minimum BW = 50%>"
where the first angle bracketed clause is a traffic condition and the second angle bracketed clause is a QoS action.
其中，括号内的第一个角度子句是交通状况，括号内的第二个角度子句是QoS动作。
This approach differs from data path modeling that describes the mechanisms that operates on the packet flows to achieve the desired effect.
这种方法不同于数据路径建模，数据路径建模描述了对数据包流进行操作以达到预期效果的机制。
Note that the approach taken in QPIM specifically did NOT subclass the PolicyRule class. Rather, it uses the SimplePolicyCondition, CompoundPolicyCondition, SimplePolicyAction, and CompoundPolicyAction classes defined in [PCIMe], as well as defining subclasses of the following classes: Policy, PolicyAction, SimplePolicyAction, PolicyImplicitVariable, and PolicyValue. Subclassing the PolicyRule class would have made it more difficult to combine actions and conditions defined within different functional domains [PCIMe] within the same rules.
请注意，QPIM中采用的方法并没有将PolicyRule类划分为子类。相反，它使用[PCIMe]中定义的SimplePolicyCondition、CompoundPolicyCondition、SimplePolicyAction和CompoundPolicyAction类，并定义以下类的子类：Policy、PolicyAction、SimplePolicyAction、PolicyImplicitVariable和PolicyValue。对PolicyRule类进行子类化会使在同一规则中组合不同功能域[PCIMe]中定义的操作和条件变得更加困难。
The organization of the information represented by QPIM is designed to be hierarchical. To do this, QPIM utilizes the PolicySetComponent aggregation [PCIMe] to provide an arbitrarily nested organization of policy information. A policy group functions as a container of
QPIM所表示的信息的组织设计为分层的。为此，QPIM利用PolicySetComponent聚合[PCIMe]提供策略信息的任意嵌套组织。策略组用作
policy rules and/or policy groups. A policy rule can also contain policy rules and/or groups, enabling a rule/sub-rule relationship to be realized.
策略规则和/或策略组。策略规则还可以包含策略规则和/或组，以实现规则/子规则关系。
The hierarchical design decision is based on the realization that it is natural for humans to organize policy rules in groups. Breaking down a complex policy into a set of simple rules is a process that follows the way people tend to think and analyze systems. The complexity of the abstract, business-oriented policy is simplified and made into a hierarchy of simple rules and grouping of simple rules.
分层设计决策基于这样一种认识，即人类自然会分组组织策略规则。将复杂的政策分解为一组简单的规则是一个遵循人们倾向于思考和分析系统的方式的过程。简化了抽象的、面向业务的策略的复杂性，并将其划分为简单规则的层次结构和简单规则的分组。
The hierarchical information organization helps to simplify the definition and readability of data instances based on QPIM. Hierarchies can also serve to carry additional semantics for QoS actions in a given context. An example, detailed in section 2.3, demonstrates how hierarchical bandwidth allocation policies can be specified in an intuitive form, without the need to specify complex scheduler structures.
分层信息组织有助于简化基于QPIM的数据实例的定义和可读性。层次结构还可以为给定上下文中的QoS操作提供附加语义。第2.3节中详细介绍的示例演示了如何以直观的形式指定分层带宽分配策略，而无需指定复杂的调度程序结构。
QPIM facilitates goal-oriented QoS policy definition. This means that the process of defining QoS policy is focused on the desired effect of policies, as opposed to the means of implementing the policy on network elements.
QPIM促进了面向目标的QoS策略定义。这意味着定义QoS策略的过程集中于策略的预期效果，而不是在网络元素上实现策略的方法。
QPIM is intended to define a minimal specification of desired network behavior. It is the role of device-specific configuration agents to interpret policy expressed in a standard way and fill in the necessary configuration details that are required for their particular application. The benefit of using QPIM is that it provides a common lingua franca that each of the device- and/or vendor-specific configuration agents can use. This helps ensure a common interpretation of the general policy as well as aid the administrator in specifying a common policy to be implemented across different devices. This is analogous to the fundamental object-oriented paradigm of separating specification from implementation. Using QPIM, traffic conditioning can be specified in a general manner that can help different implementations satisfy a common goal.
QPIM旨在定义所需网络行为的最低规范。特定于设备的配置代理的角色是解释以标准方式表示的策略，并填写其特定应用程序所需的必要配置详细信息。使用QPIM的好处在于，它提供了每个设备和/或特定于供应商的配置代理都可以使用的通用语言。这有助于确保通用策略的通用解释，并帮助管理员指定要在不同设备上实施的通用策略。这类似于将规范与实现分离的基本面向对象范例。使用QPIM，可以以一种通用的方式指定流量调节，以帮助不同的实现满足一个共同的目标。
For example, a valid policy may include only a single rule that specifies that bandwidth should be reserved for a given set of traffic flows. The rule does not need to include any of the various other details that may be needed for implementing a scheduler that supports this bandwidth allocation (e.g., the queue length required). It is assumed that a PDP or the PEPs would fill in these details using (for example) their default queue length settings. The policy
例如，有效的策略可能只包含一条规则，该规则指定应为给定的一组流量保留带宽。该规则不需要包括实现支持该带宽分配的调度器所需的任何其他细节（例如，所需的队列长度）。假设PDP或PEP将使用（例如）其默认队列长度设置填写这些详细信息。政策
writer need only specify the main goal of the policy, making sure that the preferred application receives enough bandwidth to operate adequately.
编写者只需指定策略的主要目标，确保首选应用程序获得足够的带宽以充分运行。
An important design goal of QPIM is to provide a means for defining policies that span numerous devices. This goal differentiates QPIM from device-level information models, which are designed for modeling policy that controls a single device, its mechanisms and capabilities.
QPIM的一个重要设计目标是提供一种方法来定义跨多个设备的策略。该目标将QPIM与设备级信息模型区分开来，设备级信息模型是为控制单个设备及其机制和功能的策略建模而设计的。
This design goal has several ramifications. First, roles [PCIM] are used to define policies across multiple devices. Second, the use of abstract policies frees the policy definition process from having to deal with individual device peculiarities, and leaves interpretation and configuration to be modeled by PDPs or other configuration agents. Third, QPIM allows extensive reuse of all policy building blocks in multiple rules used within different devices.
这个设计目标有几个分支。首先，角色[PCIM]用于跨多个设备定义策略。其次，抽象策略的使用使策略定义过程不必处理单个设备的特性，并将解释和配置留给PDP或其他配置代理建模。第三，QPIM允许在不同设备中使用的多个规则中广泛重用所有策略构建块。
QPIM models QoS policy in a way designed to be independent of any particular device or vendor. This enables networks made up of different devices that have different capabilities to be managed and controlled using a single standard set of policies. Using such a single set of policies is important because otherwise, the policy will itself reflect the differences between different device implementations.
QPIM以独立于任何特定设备或供应商的方式对QoS策略进行建模。这使得由具有不同功能的不同设备组成的网络能够使用单个标准策略集进行管理和控制。使用这样一组策略非常重要，因为否则，策略本身将反映不同设备实现之间的差异。
The use of roles enables a policy definition to be targeted to the network function of a network element, rather than to the element's type and capabilities. The use of roles for mapping policy to network elements provides an efficient and simple method for compact and abstract policy definition. A given abstract policy may be mapped to a group of network elements without the need to specify configuration for each of those elements based on the capabilities of any one individual element.
角色的使用使策略定义能够针对网络元素的网络功能，而不是元素的类型和功能。使用角色将策略映射到网络元素为紧凑和抽象的策略定义提供了一种高效而简单的方法。给定的抽象策略可以映射到一组网络元素，而无需基于任何一个单独元素的能力为这些元素中的每一个指定配置。
The policy definition is designed to allow aggregating multiple devices within the same role, if desired. For example, if two core network interfaces operate at different rates, one does not have to define two separate policy rules to express the very same abstract policy (e.g., allocating 30% of the interface bandwidth to a given
如果需要，策略定义旨在允许聚合同一角色中的多个设备。例如，如果两个核心网络接口以不同的速率运行，则不必定义两个单独的策略规则来表示完全相同的抽象策略（例如，将30%的接口带宽分配给给定的
preferred set of flows). The use of hierarchical context and relative QoS actions in QPIM addresses this and other related problems.
首选流集）。在QPIM中使用分层上下文和相对QoS操作解决了这个问题和其他相关问题。
Reusable objects, as defined by [PCIM] and [PCIMe], are the means for sharing policy building blocks, thus allowing central management of global concepts. QPIM provides the ability to reuse all policy building blocks: variables and values, conditions and actions, traffic profiles, and policy groups and policy rules. This provides the required flexibility to manage large sets of policy rules over large policy domains.
[PCIM]和[PCIMe]定义的可重用对象是共享策略构建块的手段，因此允许对全局概念进行集中管理。QPIM提供了重用所有策略构建块的能力：变量和值、条件和操作、流量配置文件以及策略组和策略规则。这提供了在大型策略域上管理大型策略规则集所需的灵活性。
For example, the following rule makes use of centrally defined objects being reused (referenced):
例如，以下规则使用正在重用（引用）的中心定义对象：
If <DestinationAddress == FinanceSubNet> then <DSCP =
MissionCritical>
If <DestinationAddress == FinanceSubNet> then <DSCP =
MissionCritical>
In this rule, the condition refers to an object named FinanceSubNet, which is a value (or possibly a set of values) defined and maintained in a reusable objects container. The QoS action makes use of a value named MissionCritical, which is also a reusable object. The advantage of specifying a policy in this way is its inherent flexibility. Given the above policy, whenever business needs require a change in the subnet definition for the organization, all that's required is to change the reusable value FinanceSubNet centrally. All referencing rules are immediately affected, without the need to modify them individually. Without this capability, the repository that is used to store the rules would have to be searched for all rules that refer to the finance subnet, and then each matching rule's condition would have to be individually updated. This is not only much less efficient, but also is more prone to error.
在此规则中，条件引用名为FinanceSubNet的对象，该对象是在可重用对象容器中定义和维护的值（或可能是一组值）。QoS操作使用名为MissionCritical的值，它也是一个可重用对象。以这种方式指定策略的优点是其固有的灵活性。根据上述策略，每当业务需要更改组织的子网定义时，只需集中更改可重用值FinanceSubNet即可。所有引用规则都会立即受到影响，无需单独修改。如果没有此功能，则必须在用于存储规则的存储库中搜索引用财务子网的所有规则，然后必须单独更新每个匹配规则的条件。这不仅效率低得多，而且更容易出错。
For a complete description of reusable objects, refer to [PCIM] and [PCIMe].
有关可重用对象的完整描述，请参阅[PCIM]和[PCIMe]。
Policy defined by QPIM should be enforceable. This means that a PDP can use QPIM's policy definition in order to make the necessary decisions and enforce the required policy rules. For example, RSVP admission decisions should be made based on the policy definitions specified by QPIM. A PDP should be able to map QPIM policy definitions into PEP configurations, using either standard or proprietary protocols.
QPIM定义的政策应具有可执行性。这意味着PDP可以使用QPIM的策略定义，以便做出必要的决策并实施所需的策略规则。例如，应根据QPIM指定的策略定义做出RSVP准入决定。PDP应该能够使用标准或专有协议将QPIM策略定义映射到PEP配置中。
QPIM is designed to be agnostic of any particular, vendor-dependent technology. However, QPIM's constructs SHOULD always be interpreted so that policy-compliant behavior can be enforced on the network under management. Therefore, there are three fundamental requirements that QPIM must satisfy:
QPIM被设计为不知道任何特定的、依赖于供应商的技术。但是，应始终解释QPIM的构造，以便在管理的网络上实施符合策略的行为。因此，QPIM必须满足三个基本要求：
1. Policy specified by QPIM must be able to be mapped to actual network elements.
1. QPIM指定的策略必须能够映射到实际的网络元素。
2. Policy specified by QPIM must be able to control QoS network functions without making reference to a specific type of device or vendor.
2. QPIM指定的策略必须能够控制QoS网络功能，而无需参考特定类型的设备或供应商。
3. Policy specified by QPIM must be able to be translated into network element configuration.
3. QPIM指定的策略必须能够转换为网元配置。
QPIM satisfies requirements #1 and #2 above by using the concept of roles (specifically, the PolicyRoles property, defined in PCIM). By matching roles assigned to policy groups and to network elements, a PDP (or other enforcement agent) can determine what policy should be applied to a given device or devices.
QPIM通过使用角色的概念（特别是PCIM中定义的PolicyRoles属性）满足上述第1和第2项要求。通过匹配分配给策略组和网络元素的角色，PDP（或其他实施代理）可以确定应将什么策略应用于给定的一个或多个设备。
The use of roles in mapping policy to network elements supports model scalability. QPIM policy can be mapped to large-scale policy domains by assigning a single role to a group of network elements. This can be done even when the policy domain contains heterogeneous devices. So, a small set of policies can be deployed to large networks without having to re-specify the policy for each device separately. This QPIM property is important for QoS policy management applications that strive to ease the task of policy definition for large policy domains.
在将策略映射到网络元素时使用角色支持模型可伸缩性。通过将单个角色分配给一组网络元素，QPIM策略可以映射到大规模策略域。即使策略域包含异构设备，也可以这样做。因此，可以将一小部分策略部署到大型网络，而无需分别为每个设备重新指定策略。此QPIM属性对于努力简化大型策略域的策略定义任务的QoS策略管理应用程序非常重要。
Requirement #2 is also satisfied by making QPIM domain-oriented (see [TERMS] for a definition of "domain"). In other words, the target of the policy is a domain, as opposed to a specific device or interface.
通过使QPIM面向域（参见[术语]了解“域”的定义），也满足了需求#2。换句话说，策略的目标是域，而不是特定的设备或接口。
Requirement #3 is satisfied by modeling QoS conditions and actions that are commonly configured on various devices. However, QPIM is extensible to allow modeling of actions that are not included in QPIM.
需求#3通过对各种设备上通常配置的QoS条件和操作进行建模来满足。但是，QPIM是可扩展的，允许对QPIM中未包含的操作进行建模。
It is important to note that different PEPs will have different capabilities and functions, which necessitate different individual configurations even if the different PEPs are controlled by the same policy.
需要注意的是，不同的政治公众人物将具有不同的能力和功能，即使不同的政治公众人物受同一政策控制，也需要不同的单独配置。
The two predominant standards-based QoS methodologies developed so far are Differentiated Services (DiffServ) and Integrated Services (IntServ). The DiffServ provides a way to enforce policies that apply to a large number of devices in a scalable manner. QPIM provides actions and conditions that control the classification, policing and shaping done within the differentiated service domain boundaries, as well as actions that control the per-hop behavior within the core of the DiffServ network. QPIM does not mandate the use of DiffServ as a policy methodology.
目前开发的两种主要的基于标准的QoS方法是区分服务（DiffServ）和集成服务（IntServ）。DiffServ提供了一种以可扩展的方式强制执行应用于大量设备的策略的方法。QPIM提供控制在区分服务域边界内完成的分类、管理和成形的操作和条件，以及控制DiffServ网络核心内每跳行为的操作。QPIM不强制使用DiffServ作为策略方法。
Integrated services, together with its signaling protocol (RSVP), provides a way for end nodes (and edge nodes) to request QoS from the network. QPIM provides actions that control the reservation of such requests within the network.
综合服务及其信令协议（RSVP）为终端节点（和边缘节点）从网络请求QoS提供了一种方式。QPIM提供控制在网络中保留此类请求的操作。
As both methodologies continue to evolve, QPIM does not attempt to provide full coverage of all possible scenarios. Instead, QPIM aims to provide policy control modeling for all major scenarios. QPIM is designed to be extensible to allow for incorporation of control over newly developed QoS mechanisms.
随着这两种方法的不断发展，QPIM并不试图提供所有可能场景的全面覆盖。相反，QPIM旨在为所有主要场景提供策略控制建模。QPIM的设计是可扩展的，允许对新开发的QoS机制进行控制。
Another design goal of QPIM is to facilitate interoperability among policy systems such as PDPs and policy management applications. QPIM accomplishes this interoperability goal by standardizing the representation of policy. Producers and consumers of QoS policy need only rely on QPIM-based schemata (and resulting data models) to ensure mutual understanding and agreement on the semantics of QoS policy.
QPIM的另一个设计目标是促进策略系统（如PDP和策略管理应用程序）之间的互操作性。QPIM通过标准化策略的表示来实现这一互操作性目标。QoS策略的生产者和消费者只需要依赖基于QPIM的模式（以及由此产生的数据模型），以确保对QoS策略语义的相互理解和一致。
For example, suppose that a QoS policy management application, built by vendor A writes its policies based on the LDAP schema that maps from QPIM to a directory implementation using LDAP. Now assume that a separately built PDP from vendor B also relies on this same LDAP schema derived from QPIM. Even though these are two vendors with two different PDPs, each may read the schema of the other and "understand" it. This is because both the management application and the PDP were architected to comply with the QPIM specification. The same is true with two policy management applications. For example, vendor B's policy application may run a validation tool that computes whether there are conflicts within rules specified by the other vendor's policy management application.
例如，假设由供应商a构建的QoS策略管理应用程序基于LDAP模式写入其策略，该模式使用LDAP从QPIM映射到目录实现。现在假设供应商B单独构建的PDP也依赖于从QPIM派生的相同LDAP模式。尽管这两个供应商有两个不同的PDP，但每个供应商都可以阅读另一个的模式并“理解”它。这是因为管理应用程序和PDP的架构都符合QPIM规范。两个策略管理应用程序也是如此。例如，供应商B的策略应用程序可以运行一个验证工具，该工具可以计算其他供应商的策略管理应用程序指定的规则内是否存在冲突。
Interoperability of QPIM producers/consumers is by definition at a high level, and does not guarantee that the same policy will result in the same PEP configuration. First, different PEPs will have different capabilities and functions, which necessitate different individual configurations even if the different PEPs are controlled by the same policy. Second, different PDPs will also have different capabilities and functions, and may choose to translate the high-level QPIM policy differently depending on the functionality of the PDP, as well as on the capabilities of the PEPs that are being controlled by the PDP. However, the different configurations should still result in the same network behavior as that specified by the policy rules.
根据定义，QPIM生产者/消费者的互操作性处于较高水平，并不保证相同的策略将导致相同的PEP配置。首先，不同的政治公众人物将具有不同的能力和功能，这需要不同的个人配置，即使不同的政治公众人物由相同的策略控制。第二，不同的PDP也将具有不同的能力和功能，并且可以根据PDP的功能以及由PDP控制的pep的能力，选择不同地转换高级QPIM策略。但是，不同的配置仍然会导致与策略规则指定的网络行为相同的网络行为。
This section provides a discussion of QoS policy abstraction and the way QPIM addresses this issue.
本节讨论QoS策略抽象以及QPIM解决此问题的方式。
As described above, the main goal of the QPIM is to create an information model that can be used to help bridge part of the conceptual gap between a human policy maker and a network element that is configured to enforce the policy. Clearly this wide gap implies several translation levels, from the abstract to the concrete. At the abstract end are the business QoS policy rules. Once the business rules are known, a network administrator must interpret them as network QoS policy and represent this QoS policy by using QPIM constructs. QPIM facilitates a formal representation of QoS rules, thus providing the first concretization level: formally representing humanly expressed QoS policy.
如上所述，QPIM的主要目标是创建一个信息模型，该模型可用于帮助弥合人类决策者和配置为实施策略的网络元素之间的部分概念差距。显然，这一巨大差距意味着从抽象到具体的几个翻译层次。抽象端是业务QoS策略规则。一旦知道了业务规则，网络管理员必须将其解释为网络QoS策略，并使用QPIM构造表示此QoS策略。QPIM促进了QoS规则的形式化表示，从而提供了第一个具体化级别：形式化表示人的QoS策略。
When a human business executive defines network policy, it is usually done using informal business terms and language. For example, a human may utter a policy statement that reads:
当人力业务主管定义网络策略时，通常使用非正式的业务术语和语言来完成。例如，一个人可能会说出一条政策声明，内容如下：
"human resources applications should have better QoS than simple web applications"
“人力资源应用程序应该比简单的web应用程序具有更好的QoS”
This might be translated to a slightly more sophisticated form, such as:
这可以转化为稍微复杂一点的形式，例如：
"traffic generated by our human resources applications should have a higher probability of communicating with its destinations than traffic generated by people browsing the WEB using non-mission-critical applications"
“人力资源应用程序产生的流量与目的地通信的概率应高于使用非关键任务应用程序浏览网页产生的流量”
While this statement clearly defines QoS policy at the business level, it isn't specific enough to be enforceable by network elements. Translation to "network terms and language" is required.
虽然此声明在业务级别明确定义了QoS策略，但它不够具体，无法由网络元素强制执行。需要翻译成“网络术语和语言”。
On the other end of the scale, a network element functioning as a PEP, such as a router, can be configured with specific commands that determine the operational parameters of its inner working QoS mechanisms. For example, the (imaginary) command "output-queue-depth = 100" may be an instruction to a network interface card of a router to allow up to 100 packets to be stored before subsequent packets are discarded (not forwarded). On a different device within the same network, the same instruction may take another form, because a different vendor built that device or it has a different set of functions, and hence implementation, even though it is from the same vendor. In addition, a particular PEP may not have the ability to create queues that are longer than, say, 50 packets, which may result in a different instruction implementing the same QoS policy.
在规模的另一端，作为PEP的网元（如路由器）可以配置特定的命令，以确定其内部工作QoS机制的操作参数。例如，（假想的）命令“输出队列深度＝100”可以是对路由器的网络接口卡的指令，以允许在丢弃（不转发）后续分组之前存储多达100个分组。在同一网络中的不同设备上，同一指令可能采用另一种形式，因为不同的供应商构建了该设备或具有不同的功能集，因此实现也不同，即使它来自同一供应商。此外，特定PEP可能没有能力创建长于（例如）50个分组的队列，这可能导致实现相同QoS策略的不同指令。
The first example illustrates 'abstract policy', while the second illustrates 'concrete configuration'. Furthermore, the first example illustrates end-to-end policy, which covers the conditioning of application traffic throughout the network. The second example illustrates configuration for a particular PEP or a set thereof. While an end-to-end policy statement can only be enforced by configuration of PEPs in various parts of the network, the information model of policy and that of the mechanisms that a PEP uses to implement that policy are vastly different.
第一个示例说明了“抽象策略”，而第二个示例说明了“具体配置”。此外，第一个示例说明了端到端策略，该策略涵盖了整个网络中应用程序流量的调节。第二示例说明特定PEP或其集合的配置。虽然端到端策略声明只能通过在网络的各个部分配置PEP来实施，但策略的信息模型和PEP用于实施该策略的机制的信息模型有很大的不同。
The translation process from abstract business policy to concrete PEP configuration is roughly expressed as follows:
从抽象业务策略到具体政治公众人物配置的转换过程大致如下：
1. Informal business QoS policy is expressed by a human policy maker (e.g., "All executives' WEB requests should be prioritized ahead of other employees' WEB requests")
1. 非正式的业务QoS策略由人力决策者表示（例如，“所有高管的WEB请求应优先于其他员工的WEB请求”）
2. A network administrator analyzes the policy domain's topology and determines the roles of particular device interfaces. A role may be assigned to a large group of elements, which will result in mapping a particular policy to a large group of device interfaces.
2. 网络管理员分析策略域的拓扑并确定特定设备接口的角色。角色可以分配给一大组元素，这将导致将特定策略映射到一大组设备接口。
3. The network administrator models the informal policy using QPIM constructs, thus creating a formal representation of the abstract policy. For example, "If a packet's protocol is HTTP and its destination is in the 'EXECUTIVES' user group, then assign IPP 7 to the packet header".
3. 网络管理员使用QPIM构造对非正式策略进行建模，从而创建抽象策略的正式表示。例如，“如果数据包的协议是HTTP，并且其目的地在‘Executive’用户组中，则将IPP 7分配给数据包头”。
4. The network administrator assigns roles to the policy groups created in the previous step matching the network elements' roles assigned in step #2 above.
4. 网络管理员将角色分配给在上一步中创建的策略组，该策略组与在上述第2步中分配的网络元素角色相匹配。
5. A PDP translates the abstract policy constructs created in step #3 into device-specific configuration commands for all devices effected by the new policy (i.e., devices that have interfaces that are assigned a role matching the new policy constructs' roles). In this process, the PDP consults the particular devices' capabilities to determine the appropriate configuration commands implementing the policy.
5. PDP将在步骤#3中创建的抽象策略构造转换为设备特定的配置命令，用于受新策略影响的所有设备（即，具有分配了与新策略构造的角色匹配的角色的接口的设备）。在此过程中，PDP参考特定设备的能力，以确定实现策略的适当配置命令。
6. For each PEP in the network, the PDP (or an agent of the PDP) issues the appropriate device-specific instructions necessary to enforce the policy.
6. 对于网络中的每个PEP，PDP（或PDP的代理）发出执行策略所需的适当设备特定指令。
QPIM, PCIM and PCIMe are used in step #3 above.
QPIM、PCIM和PCIMe在上述步骤#3中使用。
Policy is described by a set of policy rules that may be grouped into subsets [PCIMe]. Policy rules and policy groups can be nested within other policy rules, providing a hierarchical policy definition. Nested rules are also called sub-rules, and we use both terms in this document interchangeably. The aggregation PolicySetComponent (defined in [PCIMe] is used to represent the nesting of a policy rule or group in another policy rule.
策略由一组策略规则描述，这些规则可以分组为子集[PCIMe]。策略规则和策略组可以嵌套在其他策略规则中，从而提供分层策略定义。嵌套规则也称为子规则，我们在本文档中交替使用这两个术语。聚合PolicySetComponent（在[PCIMe]中定义）用于表示策略规则或组在另一个策略规则中的嵌套。
The hierarchical policy rule definition enhances policy readability and reusability. Within the QoS policy information model, hierarchy is used to model context or scope for the sub-rule actions. Within QPIM, bandwidth allocation policy actions and drop threshold actions use this hierarchal context. First we provide a detailed example of the use of hierarchy in bandwidth allocation policies. The differences between flat and hierarchical policy representation are discussed. The use of hierarchy in drop threshold policies is described in a following subsection. Last but not least, the restrictions on the use of rule hierarchies within QPIM are described.
分层策略规则定义增强了策略的可读性和可重用性。在QoS策略信息模型中，层次结构用于为子规则操作的上下文或范围建模。在QPIM中，带宽分配策略操作和丢弃阈值操作使用此层次上下文。首先，我们提供了在带宽分配策略中使用层次结构的详细示例。讨论了平面策略表示和层次策略表示的区别。下一小节将描述丢弃阈值策略中层次结构的使用。最后但并非最不重要的是，描述了QPIM中规则层次结构的使用限制。
Consider the following example where the informal policy reads:
考虑以下非正式政策的例子：
On any interface on which these rules apply, guarantee at least 30% of the interface bandwidth to UDP flows, and at least 40% of the interface bandwidth to TCP flows.
在这些规则适用的任何接口上，保证UDP流的接口带宽至少为30%，TCP流的接口带宽至少为40%。
The QoS Policy information model follows the Policy Core information model by using roles as a way to specify the set of interfaces on which this policy applies. The policy does not assume that all interfaces are run at the same speed, or have any other property in
QoS策略信息模型遵循策略核心信息模型，通过使用角色来指定应用此策略的接口集。该策略不假定所有接口都以相同的速度运行，也不假定所有接口中都有任何其他属性
common apart from being able to forward packets. Bandwidth is allocated between UDP and TCP flows using percentages of the available interface bandwidth. Assume that we have an available interface bandwidth of 1 Mbits/sec. Then this rule will guarantee 300Kbits/sec to UDP flows. However, if the interface bandwidth was instead only 64kbits/sec, then this rule would correspondingly guarantee 19.2kb/sec.
除了能够转发数据包之外，它还很常见。使用可用接口带宽的百分比在UDP和TCP流之间分配带宽。假设我们的可用接口带宽为1 Mbits/sec。然后此规则将保证300Kbits/sec到UDP流。但是，如果接口带宽仅为64kbits/sec，则此规则将相应地保证19.2kb/sec。
This policy is modeled within QPIM using two policy rules of the form:
此策略在QPIM中使用以下形式的两个策略规则建模：
If (IP protocol is UDP) THEN (guarantee 30% of available BW) (1) If (IP protocol is TCP) THEN (guarantee 40% of available BW) (2)
如果（IP协议为UDP），则（保证30%的可用BW）（1）如果（IP协议为TCP），则（保证40%的可用BW）（2）
Assume that these two rules are grouped within a PolicySet [PCIMe] carrying the appropriate role combination. A possible implementation of these rules within a PEP would be to use a Weighted-Round-Robin scheduler with 3 queues. The first queue would be used for UDP traffic, the second queue for TCP traffic and the third queue for the rest of the traffic. The weights of the Weighted-Round-Robin scheduler would be 30% for the first queue, 40% for the second queue and 30% for the last queue.
假设这两个规则分组在带有适当角色组合的策略集[PCIMe]中。这些规则在PEP中的一个可能实现是使用带3个队列的加权循环调度程序。第一个队列用于UDP流量，第二个队列用于TCP流量，第三个队列用于其余流量。加权循环调度程序的权重对于第一个队列为30%，第二个队列为40%，最后一个队列为30%。
The actions specifying the bandwidth guarantee implicitly assume that the bandwidth resource being guaranteed is the bandwidth available at the interface level. A PolicyRoleCollection is a class defined in [PCIMe] whose purpose is to identify the set of resources (in this example, interfaces) that are assigned to a particular role. Thus, the type of managed elements aggregated within the PolicyRoleCollection defines the bandwidth resource being controlled. In our example, interfaces are aggregated within the PolicyRoleCollection. Therefore, the rules specify bandwidth allocation to all interfaces that match a given role. Other behavior could be similarly defined by changing what was aggregated within the PolicyRoleCollection.
指定带宽保证的操作隐式地假定所保证的带宽资源是接口级别的可用带宽。PolicyRoleCollection是在[PCIMe]中定义的类，其目的是标识分配给特定角色的资源集（在本例中为接口）。因此，在PolicyRoleCollection中聚合的托管元素的类型定义了被控制的带宽资源。在我们的示例中，接口在PolicyRoleCollection中聚合。因此，这些规则为与给定角色匹配的所有接口指定带宽分配。通过更改PolicyRoleCollection中聚合的内容，可以类似地定义其他行为。
Normally, a full specification of the rules would require indicating the direction of the traffic for which bandwidth allocation is being made. Using the direction variable defined in [PCIMe], the rules can be specified in the following form:
通常，规则的完整规范需要指示正在进行带宽分配的通信量的方向。使用[PCIMe]中定义的方向变量，可以按以下形式指定规则：
If (direction is out) If (IP protocol is UDP) THEN (guarantee 30% of available BW) If (IP protocol is TCP) THEN (guarantee 40% of available BW)
如果（方向为out）如果（IP协议为UDP）则（保证30%的可用BW）如果（IP协议为TCP）则（保证40%的可用BW）
where indentation is used to indicate rule nesting. To save space, we omit the direction condition from further discussion.
其中缩进用于指示规则嵌套。为了节省空间，我们在进一步讨论中省略了方向条件。
Rule nesting provides the ability to further refine the scope of bandwidth allocation within a given traffic class forwarded via these interfaces. The example below adds two nested rules to refine bandwidth allocation for UDP and TCP applications.
规则嵌套提供了进一步细化通过这些接口转发的给定流量类内带宽分配范围的能力。下面的示例添加了两个嵌套规则，以优化UDP和TCP应用程序的带宽分配。
If (IP protocol is UDP) THEN (guarantee 30% of available BW) (1) If (protocol is TFTP) THEN (guarantee 10% of available BW) (1a) If (protocol is NFS) THEN (guarantee 40% of available BW) (1b) If (IP protocol is TCP) THEN (guarantee 40% of available BW) (2) If (protocol is HTTP) THEN guarantee 20% of available BW) (2a) If (protocol is FTP) THEN (guarantee 30% of available BW) (2b)
如果（IP协议是UDP）那么（保证30%的可用BW）（1）如果（协议是TFTP）那么（保证10%的可用BW）（1a）如果（协议是NFS）那么（保证40%的可用BW）（1b）如果（IP协议是TCP）那么（保证40%的可用BW）（2）如果（协议是HTTP）那么保证20%的可用BW）（2a）如果（协议是FTP）那么（保证30%的可用BW）（2b）
Subrules 1a and 1b specify bandwidth allocation for UDP applications. The total bandwidth resource being partitioned among UDP applications is the bandwidth available for the UDP traffic class (i.e., 30%), not the total bandwidth available at the interface level. Furthermore, TFTP and NFS are guaranteed to get at least 10% and 40% of the total available bandwidth for UDP, while other UDP applications aren't guaranteed to receive anything. Thus, TFTP and NFS are guaranteed to get at least 3% and 12% of the total bandwidth. Similar logic applies to the TCP applications.
子规则1a和1b指定UDP应用程序的带宽分配。在UDP应用程序之间划分的总带宽资源是UDP通信类的可用带宽（即30%），而不是接口级别的可用总带宽。此外，TFTP和NFS保证至少获得UDP总可用带宽的10%和40%，而其他UDP应用程序不保证接收任何内容。因此，TFTP和NFS保证获得至少3%和12%的总带宽。类似的逻辑也适用于TCP应用程序。
The point of this section will be to show that a hierarchical policy representation enables a finer level of granularity for bandwidth allocation to be specified than is otherwise available using a non-hierarchical policy representation. To see this, let's compare this set of rules with a non-hierarchical (flat) rule representation. In the non-hierarchical representation, the guaranteed bandwidth for TFTP flows is calculated by taking 10% of the bandwidth guaranteed to UDP flows, resulting in 3% of the total interface bandwidth guarantee.
本节的重点在于说明，与使用非分层策略表示的情况相比，分层策略表示可以实现更精细的带宽分配粒度。为了了解这一点，让我们将这组规则与非层次（平面）规则表示进行比较。在非分层表示中，TFTP流的保证带宽是通过取UDP流保证带宽的10%来计算的，从而得到总接口带宽保证的3%。
If (UDP AND TFTP) THEN (guarantee 3% of available BW) (1a) If (UDP AND NFS) THEN (guarantee 12% of available BW) (1b) If (other UDP APPs) THEN (guarantee 15% of available BW) (1c) If (TCP AND HTTP) THEN guarantee 8% of available BW) (2a) If (TCP AND FTP) THEN (guarantee 12% of available BW) (2b) If (other TCP APPs) THEN (guarantee 20% of available BW) (2c)
如果（UDP和TFTP）然后（保证3%的可用BW）（1a）如果（UDP和NFS）然后（保证12%的可用BW）（1b）如果（其他UDP应用）然后（保证15%的可用BW）（1c）如果（TCP和HTTP）然后保证8%的可用BW）（2a）如果（TCP和FTP）然后（保证12%的可用BW）（2b）如果（其他TCP应用）然后（保证20%的可用BW）（2c）
Are these two representations identical? No, bandwidth allocation is not the same. For example, within the hierarchical representation, UDP applications are guaranteed 30% of the bandwidth. Suppose a single UDP flow of an application different from NFS or TFTP is running. This application would be guaranteed 30% of the interface bandwidth in the hierarchical representation but only 15% of the interface bandwidth in the flat representation.
这两种表述相同吗？不，带宽分配不一样。例如，在分层表示中，UDP应用程序保证30%的带宽。假设正在运行与NFS或TFTP不同的应用程序的单个UDP流。该应用程序在分层表示中保证30%的接口带宽，但在平面表示中仅保证15%的接口带宽。
A two stage scheduler is best modeled by a hierarchical representation whereas a flat representation may be realized by a non-hierarchical scheduler.
两级调度器最好用分层表示法建模，而平面表示法可以用非分层调度器实现。
A schematic hierarchical Weighted-Round-Robin scheduler implementation that supports the hierarchical rule representation is described below.
下面描述支持分层规则表示的示意图分层加权循环调度程序实现。
--UDP AND TFTP queue--10%
--UDP AND NFS queue--40%-Scheduler-30%--+
--Other UDP queue--50% A1 |
|
--TCP AND HTTP queue--20% |
--TCP AND FTP queue--30%-Scheduler-40%--Scheduler--Interface
--Other TCP queue--50% A2 | B
|
------------Non UDP/TCP traffic-----30%--+
--UDP AND TFTP queue--10%
--UDP AND NFS queue--40%-Scheduler-30%--+
--Other UDP queue--50% A1 |
|
--TCP AND HTTP queue--20% |
--TCP AND FTP queue--30%-Scheduler-40%--Scheduler--Interface
--Other TCP queue--50% A2 | B
|
------------Non UDP/TCP traffic-----30%--+
Scheduler A1 extracts packets from the 3 UDP queues according to the weight specified by the UDP sub-rule policy. Scheduler A2 extracts packets from the 3 TCP queues specified by the TCP sub-rule policy. The second stage scheduler B schedules between UDP, TCP and all other traffic according to the policy specified in the top most rule level.
调度器A1根据UDP子规则策略指定的权重从3个UDP队列提取数据包。调度器A2从TCP子规则策略指定的3个TCP队列中提取数据包。第二阶段调度程序B根据最顶层规则级别中指定的策略在UDP、TCP和所有其他通信量之间进行调度。
Another difference between the flat and hierarchical rule representation is the actual division of bandwidth above the minimal bandwidth guarantee. Suppose two high rate streams are being forwarded via this interface: an HTTP stream and an NFS stream. Suppose that the rate of each flow is far beyond the capacity of the interface. In the flat scheduler implementation, the ratio between the weights is 8:12 (i.e., HTTP:NFS), and therefore HTTP stream would consume 40% of the bandwidth while NFS would consume 60% of the bandwidth. In the hierarchical scheduler implementation the only scheduler that has two queues filled is scheduler B, therefore the ratio between the HTTP (TCP) stream and the NFS (UDP) stream would be 30:40, and therefore the HTTP stream would consume approximately 42% of the interface bandwidth while NFS would consume 58% of the interface bandwidth. In both cases both HTTP and NFS streams got more than the minimal guaranteed bandwidth, but the actual rates forwarded via the interface differ.
平面规则表示和层次规则表示之间的另一个区别是带宽的实际划分高于最小带宽保证。假设两个高速流通过该接口转发：HTTP流和NFS流。假设每个流量的速率远远超过接口的容量。在平面调度器实现中，权重之间的比率为8:12（即HTTP:NFS），因此HTTP流将消耗40%的带宽，而NFS将消耗60%的带宽。在分层调度器实现中，唯一填充了两个队列的调度器是调度器B，因此HTTP（TCP）流和NFS（UDP）流之间的比率将为30:40，因此HTTP流将消耗大约42%的接口带宽，而NFS将消耗58%的接口带宽。在这两种情况下，HTTP和NFS流都获得了超过最小保证带宽的带宽，但通过接口转发的实际速率不同。
The conclusion is that hierarchical policy representation provides additional structure and context beyond the flat policy representation. Furthermore, policies specifying bandwidth allocation using rule hierarchies should be enforced using hierarchical schedulers where the rule hierarchy level is mapped to the hierarchical scheduler level.
结论是，分层策略表示提供了平面策略表示之外的附加结构和上下文。此外，使用规则层次结构指定带宽分配的策略应使用层次调度程序强制执行，其中规则层次结构级别映射到层次调度程序级别。
Two major resources govern the per hop behavior in each node. The bandwidth allocation resource governs the forwarding behavior of each traffic class. A scheduler priority and weights are controlled by the bandwidth allocation policies, as well as the (minimal) number of queues needed for traffic separation. A second resource, which is not controlled by bandwidth allocation policies, is the queuing length and drop behavior. For this purpose, queue length and threshold policies are used.
两个主要资源控制每个节点中的每跳行为。带宽分配资源控制每个流量类别的转发行为。调度器优先级和权重由带宽分配策略以及流量分离所需的（最小）队列数控制。第二个不受带宽分配策略控制的资源是队列长度和丢弃行为。为此，使用队列长度和阈值策略。
Rule hierarchy is used to describe the context on which thresholds act. The policy rule's condition describes the traffic class and the rule's actions describe the bandwidth allocation, the forwarding priority and the queue length. If the traffic class contains different drop precedence sub-classes that require different thresholds within the same queue, the sub-rules actions describe these thresholds.
规则层次结构用于描述阈值作用的上下文。策略规则的条件描述通信量类别，规则的操作描述带宽分配、转发优先级和队列长度。如果流量类包含在同一队列中需要不同阈值的不同丢弃优先级子类，则子规则操作将描述这些阈值。
Below is an example of the use of rule nesting for threshold control purposes. Let's look at the following rules:
下面是使用规则嵌套进行阈值控制的示例。让我们看看以下规则：
If (protocol is FTP) THEN (guarantee 10% of available BW) (queue length equals 40 packets) (drop technique is random)
如果（协议是FTP），则（保证10%的可用BW）（队列长度等于40个数据包）（丢弃技术是随机的）
if (src-ip is from net 2.x.x.x) THEN min threshold = 30% max threshold = 70%
如果（src ip来自网络2.x.x.x），则最小阈值=30%最大阈值=70%
if (src-ip is from net 3.x.x.x) THEN min threshold = 40% max threshold = 90%
如果（src ip来自网络3.x.x.x），则最小阈值=40%最大阈值=90%
if (all other) THEN min threshold = 20% max threshold = 60%
如果（所有其他），则最小阈值=20%，最大阈值=60%
The rule describes the bandwidth allocation, the queue length and the drop technique assigned to FTP flows. The sub-rules describe the drop threshold priorities within those FTP flows. FTP packets received from all networks apart from networks 2.x.x.x and 3.x.x.x are randomly dropped when the queue threshold for FTP flows accumulates to 20% of the queue length. Once the queue fills to 60%, all these packets are dropped before queuing. The two other sub rules provide other thresholds for FTP packets coming from the specified two subnets. The Assured Forwarding per hop behavior (AF) is another good example of the use of hierarchy to describe the different drop preferences within a traffic class. This example is provided in a later section.
该规则描述分配给FTP流的带宽分配、队列长度和丢弃技术。子规则描述这些FTP流中的丢弃阈值优先级。当FTP流的队列阈值累积到队列长度的20%时，从网络2.x.x.x和3.x.x.x以外的所有网络接收的FTP数据包将被随机丢弃。一旦队列填充到60%，所有这些数据包将在排队前丢弃。另外两个子规则为来自指定的两个子网的FTP数据包提供其他阈值。保证每跳转发行为（AF）是使用层次结构来描述流量类中不同的丢弃首选项的另一个好例子。本示例将在后面的部分中提供。
Rule nesting is used within QPIM for two important purposes:
规则嵌套在QPIM中用于两个重要目的：
1) Enhance clarity, readability and reusability.
1) 提高清晰度、可读性和可重用性。
2) Provide hierarchical context for actions.
2) 为操作提供分层上下文。
The second point captures the ability to specify context for bandwidth allocation, as well as providing context for drop threshold policies.
第二点捕获了为带宽分配指定上下文的能力，以及为丢弃阈值策略提供上下文的能力。
When is a hierarchy level supposed to specify the bandwidth allocation context, when is the hierarchy used for specifying the drop threshold context, and when is it used merely for clarity and reusability? The answer depends entirely on the actions. Bandwidth control actions within a sub-rule specify how the bandwidth allocated to the traffic class determined by the rule's condition clause should be further divided among the sub-rules. Drop threshold actions control the traffic class's queue drop behavior for each of the sub-rules. The bandwidth control actions have an implicit pointer saying: the bandwidth allocation is relative to the bandwidth resources defined by the higher level rule. Drop threshold actions have an implicit pointer saying: the thresholds are taken from the queue resources defined by the higher level rule. Other actions do not have such an implicit pointer, and for these actions hierarchy is used only for reusability and readability purposes.
什么时候层次结构级别应该指定带宽分配上下文，什么时候层次结构用于指定丢弃阈值上下文，什么时候它仅仅用于清晰性和可重用性？答案完全取决于行动。子规则中的带宽控制操作指定分配给由规则的条件子句确定的流量类的带宽应如何在子规则中进一步划分。丢弃阈值操作控制每个子规则的流量类的队列丢弃行为。带宽控制操作有一个隐式指针，表示：带宽分配与更高级别规则定义的带宽资源相关。Drop threshold操作有一个隐式指针，表示：阈值取自更高级别规则定义的队列资源。其他操作没有这样的隐式指针，对于这些操作，层次结构仅用于可重用性和可读性目的。
Each rule that includes a bandwidth allocation action implies that a queue should be allocated to the traffic class defined by the rule's condition clause. Therefore, once a bandwidth allocation action exists within the actions of a sub-rule, a threshold action within this sub-rule cannot refer to thresholds of the parent rule's queue. Instead, it must refer to the queue of the sub-rule itself. Therefore, in order to have a clear and unambiguous definition, refinement of thresholds and refinements of bandwidth allocations within sub-rules should be avoided. If both refinements are needed for the same rule, threshold refinements and bandwidth refinements rules should each be aggregated to a separate group, and these groups should be aggregated under the policy rule, using the PolicySetComponent aggregation.
包含带宽分配操作的每个规则都意味着应该将队列分配给由规则的条件子句定义的流量类。因此，一旦子规则的操作中存在带宽分配操作，该子规则中的阈值操作就不能引用父规则队列的阈值。相反，它必须引用子规则本身的队列。因此，为了有一个清晰明确的定义，应该避免在子规则中细化阈值和细化带宽分配。如果同一规则需要两种优化，则应将阈值优化和带宽优化规则分别聚合到一个单独的组中，并且应使用PolicySetComponent聚合将这些组聚合到策略规则下。
QPIM is intended for several audiences. The following lists some of the intended audiences and their respective uses:
QPIM面向多个受众。以下列出了一些预期受众及其各自的用途：
1. Developers of QoS policy management applications can use this model as an extensible framework for defining policies to control PEPs and PDPs in an interoperable manner.
1. QoS策略管理应用程序的开发人员可以将此模型用作可扩展的框架，用于定义策略，以互操作的方式控制PEP和PDP。
2. Developers of Policy Decision Point (PDP) systems built to control resource allocation signaled by RSVP requests.
2. 策略决策点（PDP）系统的开发人员，用于控制RSVP请求发出的资源分配信号。
3. Developers of Policy Decision Points (PDP) systems built to create QoS configuration for PEPs.
3. 政策决策点（PDP）系统的开发人员，用于为政治公众人物创建QoS配置。
4. Builders of large organization data and knowledge bases who decide to combine QoS policy information with other networking policy information, assuming all modeling is based on [PCIM] and [PCIMe].
4. 大型组织数据和知识库的构建者，他们决定将QoS策略信息与其他网络策略信息相结合，假设所有建模都基于[PCIM]和[PCIMe]。
5. Authors of various standards may use constructs introduced in this document to enhance their work. Authors of data models wishing to map a storage specific technology to QPIM must use this document as well.
5. 各种标准的作者可以使用本文中介绍的结构来增强他们的工作。希望将特定于存储的技术映射到QPIM的数据模型的作者也必须使用本文档。
QPIM's class and association inheritance hierarchies are rooted in
[PCIM] and [PCIMe]. Figures 2 and 3 depict these QPIM inheritance
hierarchies, while noting their relationships to [PCIM] and
[PCIMe]classes. Note that many other classes used to form QPIM
policies, such as SimplePolicyCondition, are defined in [PCIM] and
[PCIMe]. Thus, the following figures do NOT represent ALL necessary
classes and relationships for defining QPIM policies. Rather, the
designer using QPIM should use appropriate classes and relationships
from [PCIM] and [PCIMe] in conjunction with those defined below.
QPIM's class and association inheritance hierarchies are rooted in
[PCIM] and [PCIMe]. Figures 2 and 3 depict these QPIM inheritance
hierarchies, while noting their relationships to [PCIM] and
[PCIMe]classes. Note that many other classes used to form QPIM
policies, such as SimplePolicyCondition, are defined in [PCIM] and
[PCIMe]. Thus, the following figures do NOT represent ALL necessary
classes and relationships for defining QPIM policies. Rather, the
designer using QPIM should use appropriate classes and relationships
from [PCIM] and [PCIMe] in conjunction with those defined below.
[ManagedElement] (abstract, PCIM)
|
+--Policy (abstract, PCIM)
| |
| +---PolicyAction (abstract, PCIM)
| | |
| | +---SimplePolicyAction (PCIMe)
| | | |
| | | +---QoSPolicyRSVPSimpleAction (QPIM)
| | |
| | +---QoSPolicyDiscardAction (QPIM)
| | |
| | +---QoSPolicyAdmissionAction (abstract, QPIM)
| | | |
| | | +---QoSPolicyPoliceAction (QPIM)
| | | |
| | | +---QoSPolicyShapeAction (QPIM)
| | | |
| | | +---QoSPolicyRSVPAdmissionAction (QPIM)
| | |
| | +---QoSPolicyPHBAction (abstract, QPIM)
| | |
| | +---QoSPolicyBandwidthAction (QPIM)
| | |
| | +---QoSPolicyCongestionControlAction (QPIM)
| |
| +---QoSPolicyTrfcProf (abstract, QPIM)
| | |
| | +---QoSPolicyTokenBucketTrfcProf (QPIM)
| | |
| | +---QoSPolicyIntServTrfcProf (QPIM)
| |
| |
| +---PolicyVariable (abstract, PCIMe)
| | |
| | +---PolicyImplicitVariable (abstract, PCIMe)
| | |
| | +---QoSPolicyRSVPVariable (abstract, QPIM)
| | |
| | +---QoSPolicyRSVPSourceIPv4Variable (QPIM)
| | |
| | +---QoSPolicyRSVPDestinationIPv4Variable (QPIM)
| | |
| | +---QoSPolicyRSVPSourceIPv6Variable (QPIM)
| | |
[ManagedElement] (abstract, PCIM)
|
+--Policy (abstract, PCIM)
| |
| +---PolicyAction (abstract, PCIM)
| | |
| | +---SimplePolicyAction (PCIMe)
| | | |
| | | +---QoSPolicyRSVPSimpleAction (QPIM)
| | |
| | +---QoSPolicyDiscardAction (QPIM)
| | |
| | +---QoSPolicyAdmissionAction (abstract, QPIM)
| | | |
| | | +---QoSPolicyPoliceAction (QPIM)
| | | |
| | | +---QoSPolicyShapeAction (QPIM)
| | | |
| | | +---QoSPolicyRSVPAdmissionAction (QPIM)
| | |
| | +---QoSPolicyPHBAction (abstract, QPIM)
| | |
| | +---QoSPolicyBandwidthAction (QPIM)
| | |
| | +---QoSPolicyCongestionControlAction (QPIM)
| |
| +---QoSPolicyTrfcProf (abstract, QPIM)
| | |
| | +---QoSPolicyTokenBucketTrfcProf (QPIM)
| | |
| | +---QoSPolicyIntServTrfcProf (QPIM)
| |
| |
| +---PolicyVariable (abstract, PCIMe)
| | |
| | +---PolicyImplicitVariable (abstract, PCIMe)
| | |
| | +---QoSPolicyRSVPVariable (abstract, QPIM)
| | |
| | +---QoSPolicyRSVPSourceIPv4Variable (QPIM)
| | |
| | +---QoSPolicyRSVPDestinationIPv4Variable (QPIM)
| | |
| | +---QoSPolicyRSVPSourceIPv6Variable (QPIM)
| | |
(continued on the next page)
（下页续）
(continued from the previous page)
（上页续）
[ManagedElement] (abstract, PCIM, repeated for convenience)
|
+--Policy (abstract, PCIM, repeated for convenience)
| |
| +---PolicyVariable (abstract, PCIMe)
| | |
| | +---PolicyImplicitVariable (abstract, PCIMe)
| | |
| | +---QoSPolicyRSVPVariable (abstract, QPIM)
| | |
| | +---QoSPolicyRSVPDestinationIPv6Variable (QPIM)
| | |
| | +---QoSPolicyRSVPSourcePortVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDestinationPortVariable (QPIM)
| | |
| | +---QoSPolicyRSVPIPProtocolVariable (QPIM)
| | |
| | +---QoSPolicyRSVPIPVersionVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDCLASSVariable (QPIM)
| | |
| | +---QoSPolicyRSVPStyleVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDIntServVariable (QPIM)
| | |
| | +---QoSPolicyRSVPMessageTypeVariable (QPIM)
| | |
| | +---QoSPolicyRSVPPreemptionPriorityVariable (QPIM)
| | |
| | +---QoSPolicyRSVPPreemptionDefPriorityVariable (QPIM)
| | |
| | +---QoSPolicyRSVPUserVariable (QPIM)
| | |
| | +---QoSPolicyRSVPApplicationVariable (QPIM)
| | |
| | +---QoSPolicyRSVPAuthMethodVariable (QPIM)
| |
| +---PolicyValue (abstract, PCIMe)
| | |
| | +---QoSPolicyDNValue (QPIM)
| | |
| | +---QoSPolicyAttributeValue (QPIM)
[ManagedElement] (abstract, PCIM, repeated for convenience)
|
+--Policy (abstract, PCIM, repeated for convenience)
| |
| +---PolicyVariable (abstract, PCIMe)
| | |
| | +---PolicyImplicitVariable (abstract, PCIMe)
| | |
| | +---QoSPolicyRSVPVariable (abstract, QPIM)
| | |
| | +---QoSPolicyRSVPDestinationIPv6Variable (QPIM)
| | |
| | +---QoSPolicyRSVPSourcePortVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDestinationPortVariable (QPIM)
| | |
| | +---QoSPolicyRSVPIPProtocolVariable (QPIM)
| | |
| | +---QoSPolicyRSVPIPVersionVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDCLASSVariable (QPIM)
| | |
| | +---QoSPolicyRSVPStyleVariable (QPIM)
| | |
| | +---QoSPolicyRSVPDIntServVariable (QPIM)
| | |
| | +---QoSPolicyRSVPMessageTypeVariable (QPIM)
| | |
| | +---QoSPolicyRSVPPreemptionPriorityVariable (QPIM)
| | |
| | +---QoSPolicyRSVPPreemptionDefPriorityVariable (QPIM)
| | |
| | +---QoSPolicyRSVPUserVariable (QPIM)
| | |
| | +---QoSPolicyRSVPApplicationVariable (QPIM)
| | |
| | +---QoSPolicyRSVPAuthMethodVariable (QPIM)
| |
| +---PolicyValue (abstract, PCIMe)
| | |
| | +---QoSPolicyDNValue (QPIM)
| | |
| | +---QoSPolicyAttributeValue (QPIM)
Figure 2. The QPIM Class Inheritance Hierarchy
图2。QPIM类继承层次结构
Figure 3 shows the QPIM relationship hierarchy.
图3显示了QPIM关系层次结构。
[unrooted] (abstract, PCIM)
|
+---Dependency (abstract)
| |
| +--- QoSPolicyTrfcProfInAdmissionAction (QPIM)
| |
| +--- QoSPolicyConformAction (QPIM)
| |
| +--- QoSPolicyExceedAction (QPIM)
| |
| +--- QoSPolicyViolateAction (QPIM)
| |
| +--- PolicyVariableInSimplePolicyAction
| | |
| | + QoSPolicyRSVPVariableInRSVPSimplePolicyAction
[unrooted] (abstract, PCIM)
|
+---Dependency (abstract)
| |
| +--- QoSPolicyTrfcProfInAdmissionAction (QPIM)
| |
| +--- QoSPolicyConformAction (QPIM)
| |
| +--- QoSPolicyExceedAction (QPIM)
| |
| +--- QoSPolicyViolateAction (QPIM)
| |
| +--- PolicyVariableInSimplePolicyAction
| | |
| | + QoSPolicyRSVPVariableInRSVPSimplePolicyAction
Figure 3. The QPIM Association Class Inheritance Hierarchy
图3。QPIM关联类继承层次结构
This section describes the QoS actions that are modeled by QPIM. QoS actions are policy enforced network behaviors that are specified for traffic selected by QoS conditions. QoS actions are modeled using the classes PolicyAction (defined in [PCIM]), SimplePolicyAction (defined in [PCIMe]) and several QoS actions defined in this document that are derived from both of these classes, which are described below.
本节描述由QPIM建模的QoS操作。QoS操作是为QoS条件选择的流量指定的策略强制网络行为。QoS操作是使用类PolicyAction（在[PCIM]中定义）、SimplePolicyAction（在[PCIMe]中定义）和本文档中定义的几个QoS操作建模的，这些类派生自这两个类，如下所述。
Note that there is no discussion of PolicyRule, PolicyGroup, or different types of PolicyCondition classes in this document. This is because these classes are fully specified in [PCIM] and [PCIMe].
请注意，本文档中没有讨论PolicyRule、PolicyGroup或不同类型的PolicyCondition类。这是因为这些类是在[PCIM]和[PCIMe]中完全指定的。
QoS policy based systems allow the network administrator to specify a set of rules that control both the selection of the flows that need to be provided with a preferred forwarding treatment, as well as specifying the specific set of preferred forwarding behaviors. QPIM provides an information model for specifying such a set of rules.
基于QoS策略的系统允许网络管理员指定一组规则，用于控制需要提供首选转发处理的流的选择，以及指定特定的首选转发行为。QPIM提供了一个用于指定此类规则集的信息模型。
QoS policy rules enable controlling environments in which RSVP signaling is used to request different forwarding treatment for different traffic types from the network, as well as environments where no signaling is used, but preferred treatment is desired for
QoS策略规则能够控制使用RSVP信令为来自网络的不同通信量类型请求不同转发处理的环境，以及不使用信令但需要对其进行首选处理的环境
some (but not all) traffic types. QoS policy rules also allow controlling environments where strict QoS guarantees are provided to individual flows, as well as environments where QoS is provided to flow aggregates. QoS actions allow a PDP or a PEP to determine which RSVP requests should be admitted before network resources are allocated. QoS actions allow control of the RSVP signaling content itself, as well as differentiation between priorities of RSVP requests. QoS actions allow controlling the Differentiated Service edge enforcement including policing, shaping and marking, as well as the per-hop behaviors used in the network core. Finally, QoS actions can be used to control mapping of RSVP requests at the edge of a differentiated service cloud into per hop behaviors.
某些（但不是全部）流量类型。QoS策略规则还允许控制向单个流提供严格QoS保证的环境，以及向流聚合提供QoS的环境。QoS操作允许PDP或PEP在分配网络资源之前确定应允许哪些RSVP请求。QoS操作允许控制RSVP信令内容本身，以及区分RSVP请求的优先级。QoS操作允许控制区分服务边缘实施，包括策略、成形和标记，以及网络核心中使用的每跳行为。最后，QoS操作可用于控制区分服务云边缘的RSVP请求到每跳行为的映射。
Four groups of actions are derived from action classes defined in [PCIM] and [PCIMe]. The first QoS action group contains a single action, QoSPolicyRSVPSimpleAction. This action is used for both RSVP signal control and install actions. The second QoS action group determines whether a flow or class of flows should be admitted. This is done by specifying an appropriate traffic profile using the QoSPolicyTrfcProf class and its subclasses. This set of actions also includes QoS admission control actions, which use the QoSPolicyAdmissionAction class and its subclasses. The third group of actions control bandwidth allocation and congestion control differentiations, which together specify the per-hop behavior forwarding treatment. This group of actions includes the QoSPolicyPHBAction class and its subclasses. The fourth QoS action is an unconditional packet discard action, which uses the QoSPolicyDiscardAction class. This action is used either by itself or as a building block of the QoSPolicyPoliceAction.
从[PCIM]和[PCIMe]中定义的动作类派生出四组动作。第一个QoS操作组包含一个操作QoSPolicyRSVPSimpleAction。此操作用于RSVP信号控制和安装操作。第二个QoS操作组确定是否应允许一个流或一类流。这是通过使用QoSPolicyTrfcProf类及其子类指定适当的流量配置文件来实现的。这组操作还包括QoS许可控制操作，这些操作使用QosPolicyAdministrationAction类及其子类。第三组操作控制带宽分配和拥塞控制差异，它们共同指定每跳行为转发处理。这组操作包括QospolicyPbAction类及其子类。第四个QoS操作是无条件数据包丢弃操作，它使用QoSPolicyDiscardAction类。此操作本身或作为QospolicyPolicyAction的构建块使用。
Note that some QoS actions are not directly modeled. Instead, they are modeled by using the class SimplePolicyAction with the appropriate associations. For example, the three marking actions (DSCP, IPP and CoS) are modeled by using the SimplePolicyAction class, and associating that class with variables and values of the appropriate type defined in [PCIMe].
请注意，某些QoS操作不是直接建模的。相反，它们是通过使用具有适当关联的SimplePolicyAction类来建模的。例如，三个标记操作（DSCP、IPP和CoS）通过使用SimplePolicyAction类进行建模，并将该类与[PCIMe]中定义的适当类型的变量和值相关联。
There are three types of decisions a PDP (either remote or within a PEP) can make when it evaluates an RSVP request:
PDP（远程或PEP内）在评估RSVP请求时可以做出三种类型的决定：
1. Admit or reject the request 2. Add or modify the request admission parameters 3. Modify the RSVP signaling content
1. 接受或拒绝请求2。添加或修改请求准入参数3。修改RSVP信令内容
The COPS for RSVP [RFC2749] specification uses different Decision object types to model each of these decisions. QPIM follows the COPS for RSVP specification and models each decision using a different action class.
RSVP的COPS[RFC2749]规范使用不同的决策对象类型对每个决策进行建模。QPIM遵循针对RSVP的COPS规范，并使用不同的动作类对每个决策进行建模。
The QoSPolicyRSVPAdmissionAction controls the Decision Command and Decision Flags objects used within COPS for RSVP. The QoSPolicyRSVPAdmissionAction class, with its associated QoSPolicyIntServTrfcProf class, is used to determine whether to accept or reject a given RSVP request by comparing the RSVP request's TSPEC or RSPEC parameters against the traffic profile specified by the QoSPolicyIntServTrfcProf. For a full description of the comparison method, see section 4. Following the COPS for RSVP specification, the admission decision has an option to both accept the request and send a warning to the requester. The QoSPolicyRSVPAdmissionAction can be used to limit the number of admitted reservations as well.
QoSPolicyRSVPAdmissionAction控制COPS中用于RSVP的决策命令和决策标志对象。QOSPOLICYNTSERVTRFCPROF类及其关联的QOSPOLICYNTSERVTRFCPROF类用于通过将RSVP请求的TSPEC或RSPEC参数与QOSPOLICYNTSERVTRFCPROF指定的流量配置文件进行比较来确定是否接受或拒绝给定的RSVP请求。有关比较方法的完整说明，请参见第4节。按照COPS for RSVP规范，接纳决定可以选择接受请求和向请求者发送警告。QoSPolicyRSVPAdmissionAction也可用于限制允许的预订数量。
The class QoSPolicyRSVPSimpleAction, which is derived from the PolicySimpleAction class [PCIMe], can be used to control the two other COPS RSVP decision types. The property qpRSVPActionType designates the instance of the class to be either of type 'REPLACE', 'STATELESS', or both ('REPLACEANDSTATELESS'). For instances carrying a qpRSVPActionType property value of 'REPLACE', the action is interpreted as a COPS Replace Decision, controlling the contents of the RSVP message. For instances carrying a qpRSVPActionType property value of 'STATELESS', the action is interpreted as a COPS Stateless Decision, controlling the admission parameters. If both of these actions are required, this can be done by assigning the value REPLACEANDSTATELESS to the qpRSVPActionType property.
从PolicySimpleAction类[PCIMe]派生的类QosPolicyRSPSImpleAction可用于控制其他两种COPS RSVP决策类型。属性qpRSVPActionType将类的实例指定为“REPLACE”、“STATELESS”或“REPLACEANDSTATELESS”类型。对于带有qpRSVPActionType属性值“REPLACE”的实例，该操作被解释为COPS替换决策，控制RSVP消息的内容。对于携带qpRSVPActionType属性值“无状态”的实例，该操作被解释为COPS无状态决策，控制准入参数。如果这两个操作都是必需的，则可以通过将值REPLACEANDSTATELESS分配给qpRSVPActionType属性来完成。
This class is modeled to represent the COPS for RSVP Replace and Stateless decisions. This similarity allows future use of these COPS decisions to be directly controlled by a QoSPolicySimpleAction. The only required extension might be the definition of a new RSVP variable.
此类被建模以表示RSVP替换和无状态决策的COP。这种相似性允许这些COP决策的未来使用由QoSPolicySimpleAction直接控制。唯一需要的扩展可能是新RSVP变量的定义。
The QoSPolicyRSVPSimpleAction allows the specification of admission parameters. It allows specification of the preemption priority [RFC3181] of a given RSVP Reservation request. Using the preemption priority value, the PEP can determine the importance of a Reservation compared with already admitted reservations, and if necessary can preempt lower priority reservations to make room for the higher priority one. This class can also be used to control mapping of RSVP requests to a differentiated services domain by setting the
QoSPolicyRSVPSimpleAction允许指定接纳参数。它允许指定给定RSVP保留请求的抢占优先级[RFC3181]。通过使用优先权值，政治公众人物可以确定与已接受的预订相比的预订的重要性，并且如果需要，可以优先处理优先级较低的预订，为优先级较高的预订腾出空间。此类还可以通过设置
QoSPolicyRSVPDCLASSVariable to the required value. This instructs the PEP to mark traffic matching the Session and Sender specifications carried in an RSVP request to a given DSCP value.
QOSPOLICYRSVPCLASSVARIABLE设置为所需的值。这指示PEP将与RSVP请求中携带的会话和发送方规范相匹配的通信量标记为给定的DSCP值。
A Policy system should be able to control the information carried in the RSVP messages. The QoSPolicyRSVPSimpleAction allows control of the content of RSVP signaling messages. An RSVP message can carry a preemption policy object [RFC3181] specifying the priority of the reservation request in comparison to other requests. An RSVP message can also carry a policy object for authentication purposes. An RSVP message can carry a DCLASS [DCLASS] object that specifies to the receiver or sender the particular DSCP value that should be set on the data traffic. A COPS for RSVP Replacement Data Decision controls the content of the RSVP message by specifying a set of RSVP objects replacing or removing the existing ones.
策略系统应能够控制RSVP消息中包含的信息。QoSPolicyRSVPSimpleAction允许控制RSVP信令消息的内容。RSVP消息可以携带一个抢占策略对象[RFC3181]，该对象指定保留请求相对于其他请求的优先级。RSVP消息还可以携带用于身份验证的策略对象。RSVP消息可以携带DCLASS[DCLASS]对象，该对象向接收方或发送方指定应在数据通信量上设置的特定DSCP值。COPS for RSVP替换数据决策通过指定一组替换或删除现有RSVP对象来控制RSVP消息的内容。
The differentiated Service Architecture [DIFFSERV] was designed to provide a scalable QoS differentiation without requiring any signaling protocols running between the hosts and the network. The QoS actions modeled in QPIM can be used to control all of the building blocks of the Differentiated Service architecture, including per-hop behaviors, edge classification, and policing and shaping, without a need to specify the datapath mechanisms used by PEP implementations. This provides an abstraction level hiding the unnecessary details and allowing the network administrator to write rules that express the network requirements in a more natural form. In this architecture, as no signaling between the end host and the network occurs before the sender starts sending information, the QoS mechanisms should be set up in advance. This usually means that PEPs need to be provisioned with the set of policy rules in advance.
区分服务体系结构[DIFFSERV]旨在提供可扩展的QoS区分，而不需要在主机和网络之间运行任何信令协议。QPIM中建模的QoS操作可用于控制区分服务体系结构的所有构建块，包括每跳行为、边缘分类以及监管和成形，而无需指定PEP实现所使用的数据路径机制。这提供了一个抽象级别，隐藏了不必要的细节，并允许网络管理员编写以更自然的形式表达网络需求的规则。在这种架构中，由于在发送方开始发送信息之前，终端主机和网络之间没有信令发生，因此应该提前设置QoS机制。这通常意味着需要提前为政治公众人物提供一组策略规则。
Policing and Shaping actions are modeled as subclasses of the QoS admission action. DSCP and CoS marking are modeled by using the SimplePolicyAction ([PCIMe]) class associated with the appropriate variables and values. Bandwidth allocation and congestion control actions are modeled as subclasses of the QpQPolicyPHBAction, which is itself a subclass PolicyAction class ([PCIM])
策略和塑造动作被建模为QoS接纳动作的子类。DSCP和CoS标记通过使用与适当变量和值关联的SimplePolicyAction（[PCIMe]）类进行建模。带宽分配和拥塞控制操作被建模为QPOLICYPHBAction的子类，QPOLICYPHBAction本身就是一个子类PolicyAction类（[PCIM]）
Admission Actions (QoSPolicyAdmissionAction and its subclasses) are used to police and/or shape traffic.
准入行动（QospolicyAdministrationAction及其子类）用于管理和/或控制流量。
Each Admission Action is bound to a traffic profile (QoSPolicyTrfcProf) via the QoSPolicyTrfcProfInAdmissionAction association. The traffic profile is used to meter traffic for purposes of policing or shaping.
每个接纳操作都通过QoSPolicyTrfcProf接纳操作关联绑定到流量配置文件（QoSPolicyTrfcProf）。流量配置文件用于对流量进行计量，以便进行监控或调整。
An Admission Action carries a scope property (qpAdmissionScope) that is used to determine whether the action controls individual traffic flows or aggregate traffic classes. The concepts of "flow" and "traffic class" are explained in [DIFFSERV] using the terms 'microflow' and 'traffic stream'. Roughly speaking, a flow is a set of packets carrying an IP header that has the same values for source IP, destination IP, protocol and layer 4 source and destination ports. A traffic class is a set of flows. In QPIM, simple and compound conditions can identify flows and/or traffic classes by using Boolean terms over the values of IP header fields, including the value of the ToS byte.
准入操作带有一个作用域属性（qpAdmissionScope），用于确定该操作是控制单个流量还是控制聚合流量类。[DIFFSERV]使用术语“微流”和“流量流”解释了“流量”和“流量类别”的概念。粗略地说，流是一组包含IP报头的数据包，该报头的源IP、目标IP、协议以及第4层源端口和目标端口的值相同。流量类是一组流。在QPIM中，简单和复合条件可以通过在IP头字段的值（包括ToS字节的值）上使用布尔项来识别流和/或流量类。
Thus, the interpretation of the scope property is as follows: If the value of the scope property is 0 (per-flow), each (micro) flow that can be positively matched with the rule's condition is metered and policed individually. If the value of the scope property is 1 (per-class), all flows matched with the rule's condition are metered as a single aggregate and policed together.
因此，scope属性的解释如下：如果scope属性的值为0（每个流），则可以与规则的条件正匹配的每个（微）流将分别进行度量和策略。如果scope属性的值为1（每个类），则与规则条件匹配的所有流都将作为单个聚合进行计量并一起进行策略。
The following example illustrates the use of the scope property. Using two provisioned policing actions, the following policies can be enforced:
下面的示例演示了scope属性的使用。使用两个已设置的策略操作，可以强制执行以下策略：
- Make sure that each HTTP flow will not exceed 64kb/s
- 确保每个HTTP流不会超过64kb/s
- Make sure that the aggregate rate of all HTTP flows will not exceed 512Kb/s
- 确保所有HTTP流的聚合速率不超过512Kb/s
Both policies are modeled using the same class QoSPolicyPoliceAction (derived from QoSPolicyAdmissionAction). The first policy has its scope property set to 'flow', while the second policy has its scope property set to 'class'. The two policies are modeled using a rule with two police actions that, in a pseudo-formal definition, looks like the following:
这两个策略都使用同一类QospolicyPolicyAction（源自QospolicyAdministrationAction）建模。第一个策略的scope属性设置为“flow”，而第二个策略的scope属性设置为“class”。这两个策略使用带有两个警察行动的规则建模，在伪形式定义中，这两个警察行动如下所示：
If (HTTP) Action1=police, Traffic Profile1=64kb/s, Scope1=flow
Action2=police, Traffic Profile2=512kb/s, Scope2=class
If (HTTP) Action1=police, Traffic Profile1=64kb/s, Scope1=flow
Action2=police, Traffic Profile2=512kb/s, Scope2=class
The provisioned policing action QoSPolicyPoliceAction has three associations, QoSPolicyConformAction, QoSPolicyExceedAction and QoSPolicyViolateAction.
规定的警务行动QospolicyPolicyAction有三个关联，QoSPolicyConformAction、QoSPolicyExceedAction和QoSPolicyViolateAction。
To accomplish the desired result stated above, two possible modeling techniques may be used: The two actions can be part of a single policy rule using two PolicyActionInPolicyRule [PCIM] associations. In this case the ExecutionStrategy property of the PolicyRule class [PCIMe] SHOULD be set to "Do All" so that both individual flows and aggregate streams are policed.
为了实现上述预期结果，可以使用两种可能的建模技术：使用两个PolicyActionInPolicyRule[PCIM]关联，这两个操作可以是单个策略规则的一部分。在这种情况下，PolicyRule类[PCIMe]的ExecutionStrategy属性应设置为“Do All”，以便对单个流和聚合流都实施策略。
Alternatively, Action1 and Action2 could be aggregated in a CompundPolicyAction instance using the PolicyActionInPolicyAction aggregations [PCIMe]. In this case, in order for both individual flows and aggregate traffic classes to be policed, the ExecutionStrategy property of the CompoundPolicyAction class [PCIMe] SHOULD be set to "Do All".
或者，可以使用PolicyActionInPolicyAction聚合[PCIMe]在CompundPolicyAction实例中聚合Action1和Action2。在这种情况下，为了对单个流和聚合流量类进行策略管理，CompoundPolicyAction类[PCIMe]的ExecutionStrategy属性应设置为“全部执行”。
The policing action is associated with a three-level token bucket traffic profile carrying rate, burst and excess-burst parameters. Traffic measured by a meter can be classified as conforming traffic when the metered rate is below the rate defined by the traffic profile, as excess traffic when the metered traffic is above the normal burst and below the excess burst size, and violating traffic when rate is above the maximum excess burst.
警务行动与三级令牌桶流量配置文件携带率、突发和过量突发参数相关联。当计量速率低于流量剖面定义的速率时，计量器测量的流量可分类为合格流量；当计量流量高于正常突发且低于超额突发大小时，可分类为超额流量；当速率高于最大超额突发时，可分类为违规流量。
The [DIFF-MIB] defines a two-level meter, and provides a means to combine two-level meters into more complex meters. In this document, a three-level traffic profile is defined. This allows construction of both two-level meters as well as providing an easier definition for three-level meters needed for creating AF [AF] provisioning actions.
[DIFF-MIB]定义了两级仪表，并提供了将两级仪表组合成更复杂仪表的方法。在本文件中，定义了三级流量配置文件。这允许构建两级仪表，并为创建AF[AF]配置操作所需的三级仪表提供更简单的定义。
A policing action that models three-level policing MUST associate three separate actions with a three-level traffic profile. These actions are a conforming action, an exceeding action and a violating action. A policing action that models two-level policing uses a two-level traffic profile and associates only conforming and exceeding actions. A policing action with a three-level traffic profile that specifies an exceed action but does not specify a violate action implies that the action taken when the traffic is above the maximum excess burst is identical to the action taken when the traffic is above the normal burst. A policer determines whether the profile is being met, while the actions to be performed are determined by the associations QoSPolicyXXXAction.
模拟三级治安的治安行动必须将三个单独的行动与三级交通概况相关联。这些行为是符合行为、超越行为和违反行为。模拟两级警务的警务行动使用两级流量配置文件，并仅关联符合和超过要求的行动。具有三级流量配置文件（指定超出操作但未指定违反操作）的监控操作意味着当流量高于最大超出突发时采取的操作与当流量高于正常突发时采取的操作相同。policer确定是否满足配置文件，而要执行的操作由关联QospolicyxxAction确定。
Shapers are used to delay some or all of the packets in a traffic stream, in order to bring the stream into compliance with a traffic profile. A shaper usually has a finite-sized buffer, and packets may be discarded if there is not sufficient buffer space to hold the delayed packets. Shaping is controlled by the QoSPolicyShapeAction
整形器用于延迟业务流中的部分或全部分组，以便使该流符合业务概要。整形器通常有一个有限大小的缓冲区，如果没有足够的缓冲空间来容纳延迟的数据包，数据包可能会被丢弃。成形由QoSPolicyShapeAction控制
class. The only required association is a traffic profile that specifies the rate and burst parameters that the outgoing flows should conform with.
班唯一需要的关联是指定传出流应符合的速率和突发参数的流量配置文件。
Three types of marking control actions are modeled in QPIM: Differentiated Services Code Point (DSCP) assignment, IP Precedence (IPP) assignment and layer-2 Class of Service (CoS) assignment. These assignment actions themselves are modeled by using the SimplePolicyAction class associated with the appropriate variables and values.
QPIM中建模了三种类型的标记控制操作：区分服务代码点（DSCP）分配、IP优先级（IPP）分配和第二层服务类别（CoS）分配。通过使用与适当变量和值关联的SimplePolicyAction类对这些分配操作本身进行建模。
DSCP assignment sets ("marks" or "colors") the DS field of a packet header to a particular DS Code Point (DSCP), adding the marked packet to a particular DS behavior aggregate.
DSCP分配将数据包头的DS字段（“标记”或“颜色”）设置为特定DS代码点（DSCP），将标记的数据包添加到特定DS行为聚合中。
When used in the basic form, "If <condition> then 'DCSP = ds1'", the assignment action assigns a DSCP value (ds1) to all packets that result in the condition being evaluated to true.
在基本形式“If<condition>then'DCSP=ds1”中使用时，赋值操作会将一个DSCP值（ds1）分配给所有导致条件被求值为true的数据包。
When used in combination with a policing action, a different assignment action can be issued via each of the 'conform', 'exceed' and 'violate' action associations. This way, one may select a PHB in a PHB group according to the state of a meter.
当与警务行动结合使用时，可通过每个“符合”、“超过”和“违反”行动关联发布不同的分配行动。这样，可以根据仪表的状态在PHB组中选择PHB。
The semantics of the DSCP assignment is encapsulated in the pairing of a DSCP variable and a DSCP value within a single SimplePolicyAction instance via the appropriate associations.
DSCP赋值的语义通过适当的关联封装在单个SimplePolicyAction实例中的DSCP变量和DSCP值的配对中。
IPP assignment sets the IPP field of a packet header to a particular IPP value (0 through 7). The semantics of the IPP assignment is encapsulated in the pairing of a ToS variable (PolicyIPTosVariable) and a bit string value () (defined in [PCIMe]) within a single SimplePolicyAction instance via the appropriate associations. The bit string value is used in its masked bit string format. The mask indicates the relevant 3 bits of the IPP sub field within the ToS byte, while the bit string indicates the IPP value to be set.
IPP分配将数据包头的IPP字段设置为特定的IPP值（0到7）。IPP分配的语义通过适当的关联封装在单个SimplePolicyAction实例中的ToS变量（PolicyIPTosVariable）和位字符串值（）（在[PCIMe]中定义）的配对中。位字符串值以其屏蔽位字符串格式使用。掩码表示ToS字节内IPP子字段的相关3位，而位字符串表示要设置的IPP值。
CoS assignments control the mapping of a per-hop behavior to a layer-2 Class of Service. For example, mapping of a set of DSCP values into a 802.1p user priority value can be specified using a rule with a condition describing the set of DSCP values, and a CoS assignment action that specifies the required mapping to the given user priority value. The semantics of the CoS assignment is encapsulated in the pairing of a CoS variable and a CoS value (integer in the range of 0 through 7) within a single SimplePolicyAction instance via the appropriate associations.
CoS分配控制每跳行为到第2层服务类的映射。例如，可以使用具有描述DSCP值集的条件的规则和指定到给定用户优先级值的所需映射的CoS分配操作来指定将一组DSCP值映射到802.1p用户优先级值。CoS赋值的语义通过适当的关联封装在单个SimplePolicyAction实例中的CoS变量和CoS值（范围为0到7的整数）的配对中。
Assuming that the AF1 behavior aggregate is enforced within a DS domain, policy rules on the boundaries of the network should mark packets to one of the AF1x DSCPs, depending on the conformance of the traffic to a predetermined three-parameter traffic profile. QPIM models such AF1 policing action as defined in Figure 4.
假设在DS域内强制实施AF1行为聚合，则网络边界上的策略规则应将数据包标记为AF1x DSCP之一，这取决于流量是否符合预定的三参数流量配置文件。QPIM对图4中定义的AF1警务行动进行建模。
+-----------------------+ +------------------------------+
| QoSPolicyPoliceAction |====| QoSPolicyTokenBucketTrfcProf |
| scope = class | | rate = x, bc = y, be = z |
+-----------------------+ +------------------------------+
* @ #
* @ #
* @ +--------------------+ +--------------------------+
* @ | SimplePolicyAction |---| PolicyIntegerValue -AF13 |
* @ +--------------------+ +--------------------------+
* @
* +--------------------+ +---------------------------+
* | SimplePolicyAction |---| PolicyIntegerValue - AF12 |
* +--------------------+ +---------------------------+
*
+--------------------+ +---------------------------+
| SimplePolicyAction |---| PolicyIntegerValue - AF11 |
+--------------------+ +---------------------------+
+-----------------------+ +------------------------------+
| QoSPolicyPoliceAction |====| QoSPolicyTokenBucketTrfcProf |
| scope = class | | rate = x, bc = y, be = z |
+-----------------------+ +------------------------------+
* @ #
* @ #
* @ +--------------------+ +--------------------------+
* @ | SimplePolicyAction |---| PolicyIntegerValue -AF13 |
* @ +--------------------+ +--------------------------+
* @
* +--------------------+ +---------------------------+
* | SimplePolicyAction |---| PolicyIntegerValue - AF12 |
* +--------------------+ +---------------------------+
*
+--------------------+ +---------------------------+
| SimplePolicyAction |---| PolicyIntegerValue - AF11 |
+--------------------+ +---------------------------+
Association and Aggregation Legend:
关联和聚合图例：
**** QoSPolicyConformAction
@@@@ QoSPolicyExceedAction
#### QoSPolicyViolateAction
==== QoSTrfcProfInAdmissionAction
---- PolicyValueInSimplePolicyAction ([PCIMe])
&&&& PolicyVariableInSimplePolicyAction ([PCIMe], not shown)
**** QoSPolicyConformAction
@@@@ QoSPolicyExceedAction
#### QoSPolicyViolateAction
==== QoSTrfcProfInAdmissionAction
---- PolicyValueInSimplePolicyAction ([PCIMe])
&&&& PolicyVariableInSimplePolicyAction ([PCIMe], not shown)
Figure 4. AF Policing and Marking
图4。AF警务和标记
The AF policing action is composed of a police action, a token bucket traffic profile and three instances of the SimplePolicyAction class. Each of the simple policy action instances models a different marking action. Each SimplePolicyAction uses the aggregation PolicyVariableInSimplePolicyAction to specify that the associated PolicyDSCPVariable is set to the appropriate integer value. This is done using the PolicyValueInSimplePolicyAction aggregation. The three PolicyVariableInSimplePolicyAction aggregations which connect the appropriate SimplePolicyActions with the appropriate DSCP
AF策略操作由一个策略操作、一个令牌桶流量配置文件和三个SimplePolicyAction类实例组成。每个简单策略操作实例都为不同的标记操作建模。每个SimplePolicyAction都使用聚合PolicyVariableInSimplePolicyAction指定将关联的PolicyDSCPVariable设置为适当的整数值。这是使用PolicyValueInSimplePolicyAction聚合完成的。将适当的SimplePolicyActions与适当的DSCP连接起来的三个PolicyVariableInSimplePolicyAction聚合
Variables, are not shown in this figure for simplicity. AF11 is marked on detecting conforming traffic; AF12 is marked on detecting exceeding traffic, and AF13 on detecting violating traffic.
为简单起见，此图中未显示变量。AF11标记为检测合格流量；AF12标记为检测超过流量，AF13标记为检测违反流量。
The second example, shown in Figure 5, is the simplest policing action. Traffic below a two-parameter traffic profile is unmodified, while traffic exceeding the traffic profile is discarded.
第二个示例，如图5所示，是最简单的监管操作。低于双参数流量配置文件的流量将不被修改，而超过该流量配置文件的流量将被丢弃。
+-----------------------+ +------------------------------+
| QoSPolicyPoliceAction |====| QoSPolicyTokenBucketTrfcProf |
| scope = class | | rate = x, bc = y |
+-----------------------+ +------------------------------+
@
@
+-------------------------+
| QoSPolicyDiscardAction |
+-------------------------+
+-----------------------+ +------------------------------+
| QoSPolicyPoliceAction |====| QoSPolicyTokenBucketTrfcProf |
| scope = class | | rate = x, bc = y |
+-----------------------+ +------------------------------+
@
@
+-------------------------+
| QoSPolicyDiscardAction |
+-------------------------+
Association and Aggregation Legend:
**** QoSPolicyConformAction (not used)
@@@@ QoSPolicyExceedAction
#### QoSPolicyViolateAction (not used)
==== QoSTrfcProfInAdmissionAction
Association and Aggregation Legend:
**** QoSPolicyConformAction (not used)
@@@@ QoSPolicyExceedAction
#### QoSPolicyViolateAction (not used)
==== QoSTrfcProfInAdmissionAction
Figure 5. A Simple Policing Action
图5。简单的警务行动
A Per-Hop Behavior (PHB) is a description of the externally observable forwarding behavior of a DS node applied to a particular DS behavior aggregate [DIFFSERV]. The approach taken here is that a PHB action specifies both observable forwarding behavior (e.g., loss, delay, jitter) as well as specifying the buffer and bandwidth resources that need to be allocated to each of the behavior aggregates in order to achieve this behavior. That is, a rule with a set of PHB actions can specify that an EF packet must not be delayed more than 20 msec in each hop. The same rule may also specify that EF packets need to be treated with preemptive forwarding (e.g., with priority queuing), and specify the maximum bandwidth for this class, as well as the maximum buffer resources. PHB actions can therefore be used both to represent the final requirements from PHBs and to provide enough detail to be able to map the PHB actions into a set of configuration parameters to configure queues, schedulers, droppers and other mechanisms.
每跳行为（PHB）是对应用于特定DS行为聚合[DIFFSERV]的DS节点的外部可观察转发行为的描述。这里采用的方法是，PHB动作既指定了可观察的转发行为（例如，丢失、延迟、抖动），也指定了为了实现该行为而需要分配给每个行为集合的缓冲区和带宽资源。也就是说，具有一组PHB操作的规则可以指定EF数据包在每个跃点中的延迟不得超过20毫秒。同一规则还可以指定EF分组需要通过抢占式转发（例如，使用优先级队列）进行处理，并指定此类的最大带宽以及最大缓冲资源。因此，PHB操作既可用于表示PHB的最终需求，也可用于提供足够的细节，以便能够将PHB操作映射到一组配置参数中，以配置队列、调度器、拖放器和其他机制。
The QoSPolicyPHBAction abstract class has two subclasses. The
QoSPolicyBandwidthAction class is used to control bandwidth, delay
and forwarding behavior, while the QoSPolicyCongestionControlAction
The QoSPolicyPHBAction abstract class has two subclasses. The
QoSPolicyBandwidthAction class is used to control bandwidth, delay
and forwarding behavior, while the QoSPolicyCongestionControlAction
class is used to control queue size, thresholds and congestion algorithms. The qpMaxPacketSize property of the QoSPolicyPHBAction class specifies the packet size in bytes, and is needed when translating the bandwidth and congestion control actions into actual implementation configurations. For example, an implementation measuring queue length in bytes will need to use this property to map the qpQueueSize property into the desired queue length in bytes.
类用于控制队列大小、阈值和拥塞算法。QOSpolicyPbAction类的qpMaxPacketSize属性以字节为单位指定数据包大小，并且在将带宽和拥塞控制操作转换为实际实现配置时需要该属性。例如，测量队列长度（以字节为单位）的实现需要使用此属性将qpQueueSize属性映射到所需的队列长度（以字节为单位）。
QoSPolicyBandwidthAction allows specifying the minimal bandwidth that should be reserved for a class of traffic. The property qpMinBandwidth can be specified either in Kb/sec or as a percentage of the total available bandwidth. The property qpBandwidthUnits is used to determine whether percentages or fixed values are used.
QoSPolicyBandwidthAction允许指定应为一类流量保留的最小带宽。属性qpMinBandwidth可以以Kb/秒或总可用带宽的百分比指定。属性qpBandwidthUnits用于确定是使用百分比还是固定值。
The property qpForwardingPriority is used whenever preemptive forwarding is required. A policy rule that defines the EF PHB should indicate a non-zero forwarding priority. The qpForwardingPriority property holds an integer value to enable multiple levels of preemptive forwarding where higher values are used to specify higher priority.
只要需要抢占式转发，就会使用QpfrowardingPriority属性。定义EF PHB的策略规则应指示非零转发优先级。qpForwardingPriority属性保存一个整数值，以启用多级抢占式转发，其中使用更高的值指定更高的优先级。
The property qpMaxBandwidth specifies the maximum bandwidth that should be allocated to a class of traffic. This property may be specified in PHB actions with non-zero forwarding priority in order to guard against starvation of other PHBs.
属性qpMaxBandwidth指定应分配给一类流量的最大带宽。此属性可以在具有非零转发优先级的PHB操作中指定，以防止其他PHB的饥饿。
The properties qpMaxDelay and qpMaxJitter specify limits on the per-hop delay and jitter in milliseconds for any given packet within a traffic class. Enforcement of the maximum delay and jitter may require use of preemptive forwarding as well as minimum and maximum bandwidth controls. Enforcement of low max delay and jitter values may also require fragmentation and interleave mechanisms over low speed links.
属性qpMaxDelay和qpMaxJitter指定流量类中任何给定数据包的每跳延迟和抖动限制（以毫秒为单位）。实施最大延迟和抖动可能需要使用抢占转发以及最小和最大带宽控制。强制执行低最大延迟和抖动值也可能需要在低速链路上使用分段和交织机制。
The Boolean property qpFairness indicates whether flows should have a fair chance to be forwarded without drop or delay. A way to enforce a bandwidth action with qpFairness set to TRUE would be to build a queue per flow for the class of traffic specified in the rule's filter. In this way, interactive flows like terminal access will not be queued behind a bursty flow (like FTP) and therefore have a reasonable response time.
布尔属性QPFiratice表示流是否应该有公平的机会在不中断或延迟的情况下被转发。在QPFEARITY设置为TRUE的情况下强制执行带宽操作的一种方法是为规则的筛选器中指定的流量类别为每个流构建一个队列。这样，交互流（如终端访问）将不会在突发流（如FTP）后面排队，因此具有合理的响应时间。
The QoSPolicyCongestionControlAction class controls queue length, thresholds and congestion control algorithms.
QoSPolicyCongestionControlAction类控制队列长度、阈值和拥塞控制算法。
A PEP should be able to keep in its queues qpQueueSize packets matching the rule's condition. In order to provide a link-speed independent queue size, the qpQueueSize property can also be measured in milliseconds. The time interval specifies the time needed to transmit all packets within the queue if the link speed is dedicated entirely for transmission of packets within this queue. The property qpQueueSizeUnit determines whether queue size is measured in number of packets or in milliseconds. The property qpDropMethod selects either tail-drop, head-drop or random-drop algorithms. The set of maximum and minimum threshold values can be specified as well, using qpDropMinThresholdValue and qpDropMaxThresholdValue properties, either in packets or in percentage of the total available queue size as specified by the qpDropThresholdUnits property.
PEP应该能够在其队列中保留与规则条件匹配的QP大小的数据包。为了提供与链路速度无关的队列大小，qpQueueSize属性也可以以毫秒为单位进行测量。如果链路速度完全用于传输队列内的数据包，则时间间隔指定传输队列内所有数据包所需的时间。属性qpQueueSizeUnit确定队列大小是以数据包数还是以毫秒为单位测量的。属性qpDropMethod选择尾部下降、头部下降或随机下降算法。还可以使用qpDropMinThresholdValue和qpDropMaxThresholdValue属性，以数据包或qpDropThresholdUnits属性指定的总可用队列大小百分比来指定最大和最小阈值集。
Hierarchical policy definition is a primary tool in the QoS Policy information model. Rule nesting introduced in [PCIMe] allows specification of hierarchical policies controlling RSVP requests, hierarchical shaping, policing and marking actions, as well as hierarchical schedulers and definition of the differences in PHB groups.
分层策略定义是QoS策略信息模型中的主要工具。[PCIMe]中引入的规则嵌套允许指定控制RSVP请求、分层整形、策略和标记操作的分层策略，以及分层调度程序和定义PHB组中的差异。
This example provides a set of rules that specify PHBs enforced within a Differentiated Service domain. The network administrator chose to enforce the EF, AF11 and AF13 and Best Effort PHBs. For simplicity, AF12 is not differentiated. The set of rules takes the form:
此示例提供了一组规则，用于指定在差异化服务域中强制实施的PHB。网络管理员选择强制执行EF、AF11和AF13以及尽力而为PHB。为简单起见，AF12没有区别。这套规则的形式如下：
If (EF) then do EF actions If (AF1) then do AF1 actions If (AF11) then do AF11 actions If (AF12) then do AF12 actions If (AF13) then do AF13 actions If (default) then do Default actions.
如果（EF）则执行EF操作如果（AF1）则执行AF1操作如果（AF11）则执行AF11操作如果（AF12）则执行AF12操作如果（AF13）则执行AF13操作如果（默认）则执行默认操作。
EF, AF1, AF11, AF12 and AF13 are conditions that filter traffic according to DSCP values. The AF1 condition matches the entire AF1 PHB group including the AF11, AF12 and AF13 DSCP values. The default rule specifies the Best Effort rules. The nesting of the AF1x rules within the AF1 rule specifies that there are further refinements on how AF1x traffic should be treated relative to the entire AF1 PHB group. The set of rules reside in a PolicyGroup with a decision strategy property set to 'FirstMatching'.
EF、AF1、AF11、AF12和AF13是根据DSCP值过滤流量的条件。AF1条件匹配整个AF1 PHB组，包括AF11、AF12和AF13 DSCP值。默认规则指定最佳努力规则。AF1x规则在AF1规则中的嵌套说明，相对于整个AF1 PHB组，应如何处理AF1x流量有进一步的改进。规则集位于决策策略属性设置为“FirstMatching”的PolicyGroup中。
The class instances below specify the set of actions used to describe each of the PHBs. Queue sizes are not specified, but can easily be added to the example.
下面的类实例指定了用于描述每个PHB的一组操作。队列大小未指定，但可以轻松添加到示例中。
The actions used to describe the Best Effort PHB are simple. No bandwidth is allocated to Best Effort traffic. The first action specifies that Best Effort traffic class should have fairness.
用于描述尽力而为PHB的操作非常简单。没有为尽力而为的流量分配带宽。第一个操作指定尽力而为的流量类应该具有公平性。
QoSPolicyBandwidthAction BE-B: qpFairness: TRUE
QoSPolicyBandwidthAction BE-B:QP公平性：TRUE
The second action specifies that the congestion algorithm for the Best Effort traffic class should be random, and specifies the thresholds in percentage of the default queue size.
第二个操作指定“尽力而为”流量类别的拥塞算法应为随机的，并以默认队列大小的百分比指定阈值。
QoSPolicyCongestionControlAction BE-C: qpDropMethod: random qpDropThresholdUnits % qpDropMinThreshold: 10% qpDropMaxThreshold: 70%
QoSPolicyCongestionControlAction BE-C:qpDropMethod:random qpDropThresholdUnits%qpDropMinThreshold:10%qpDropMaxThreshold:70%
EF requires preemptive forwarding. The maximum bandwidth is also specified to make sure that the EF class does not starve the other classes. EF PHB uses tail drop as the applications using EF are supposed to be UDP-based and therefore would not benefit from a random dropper.
EF需要抢先转发。还指定了最大带宽，以确保EF类不会耗尽其他类。EFPHB使用尾部拖放，因为使用EF的应用程序应该是基于UDP的，因此不会从随机拖放中受益。
QoSPolicyBandwidthAction EF-B: qpForwardingPriority: 1 qpBandwidthUnits: % qpMaxBandwidth 50% qpFairness: FALSE
QoSPolicyBandwidthAction EF-B:qpForwardingPriority:1 qpBandwidthUnits:%QpMaxBandWidth50%QpFairity:FALSE
QoSPolicyCongestionControlAction EF-C: qpDropMethod: tail-drop qpDropThresholdUnits packet qpDropMaxThreshold: 3 packets
QOSpolicyCongestinoControlAction EF-C:qpDropMethod:tail-drop qpDropThresholdUnits数据包qpDropMaxThreshold:3数据包
The AF1 actions define the bandwidth allocations for the entire PHB group:
AF1操作定义了整个PHB组的带宽分配：
QoSPolicyBandwidthAction AF1-B: qpBandwidthUnits: % qpMinBandwidth: 30%
QoSPolicyBandwidthAction AF1-B:qpBandwidthUnits:%qpMinBandwidth:30%
The AF1i actions specifies the differentiating refinement for the AF1x PHBs within the AF1 PHB group. The different threshold values provide the difference in discard probability of the AF1x PHBs within the AF1 PHB group.
AF1i操作指定AF1 PHB组内AF1x PHB的差异化细化。不同的阈值提供了AF1 PHB组内AF1x PHB丢弃概率的差异。
QoSPolicyCongestionControlAction AF11-C: qpDropMethod: random qpDropThresholdUnits packet qpDropMinThreshold: 6 packets qpDropMaxThreshold: 16 packets
QospolicyCongestinoControlAction AF11-C:qpDropMethod:random qpDropThresholdUnits数据包qpDropMinThreshold:6数据包qpDropMaxThreshold:16数据包
QoSPolicyCongestionControlAction AF12-C: qpDropMethod: random qpDropThresholdUnits packet qpDropMinThreshold: 4 packets qpDropMaxThreshold: 13 packets
QospolicyCongestinoControlAction AF12-C:qpDropMethod:random qpDropThresholdUnits数据包qpDropMinThreshold:4数据包qpDropMaxThreshold:13数据包
QoSPolicyCongestionControlAction AF13-C: qpDropMethod: random qpDropThresholdUnits packet qpDropMinThreshold: 2 packets qpDropMaxThreshold: 10 packets
QospolicyCongestinoControlAction AF13-C:qpDropMethod:random qpDropThresholdUnits数据包qpDropMinThreshold:2数据包qpDropMaxThreshold:10数据包
Meters measure the temporal state of a flow or a set of flows against a traffic profile. In this document, traffic profiles are modeled by the QoSPolicyTrfcProf class. The association QoSPolicyTrfcProf InAdmissionAction binds the traffic profile to the admission action using it. Two traffic profiles are derived from the abstract class QoSPolicyTrfcProf. The first is a Token Bucket provisioning traffic profile carrying rate and burst parameters. The second is an RSVP traffic profile, which enables flows to be compared with RSVP TSPEC and FLOWSPEC parameters.
仪表根据流量剖面测量流量或一组流量的时间状态。在本文档中，流量配置文件由QoSPolicyTrfcProf类建模。关联QospolicyTRFCROF InAdmissionAction将流量配置文件绑定到使用它的接纳操作。两个流量配置文件是从抽象类QospolicyTRFCROF派生的。第一个是令牌桶，用于提供流量配置文件的承载率和突发参数。第二个是RSVP流量配置文件，它可以将流量与RSVP TSPEC和FLOWSPEC参数进行比较。
Provisioned Admission Actions, including shaping and policing, are specified using a two- or three-parameter token bucket traffic profile. The QoSPolicyTokenBucketTrfcProf class includes the following properties:
使用两个或三个参数的令牌桶流量配置文件指定已设置的接纳操作，包括整形和策略。QospolicyTokenBuckettrFCROF类包括以下属性：
1. Rate measured in kbits/sec 2. Normal burst measured in bytes 3. Excess burst measured in bytes
1. 以kbits/sec为单位测量的速率2。以字节3测量的正常突发。以字节为单位测量的过量突发
Rate determines the long-term average transmission rate. Traffic that falls under this rate is conforming, as long as the normal burst is not exceeded at any time. Traffic exceeding the normal burst but still below the excess burst is exceeding the traffic profile. Traffic beyond the excess burst is said to be violating the traffic profile.
速率决定长期平均传输速率。只要在任何时候都不超过正常突发，低于此速率的流量就是合格的。超过正常突发但仍低于过量突发的流量超过了流量剖面。超过过量突发的流量称为违反流量配置文件。
Excess burst size is measured in bytes in addition to the burst size. A zero excess burst size indicates that no excess burst is allowed.
除了突发大小之外，额外的突发大小以字节为单位进行测量。零过量突发大小表示不允许过量突发。
RSVP admission policy can condition the decision whether to accept or deny an RSVP request based on the traffic specification of the flow (TSPEC) or the amount of QoS resources requested (FLOWSPEC). The admission decision can be based on matching individual RSVP requests against a traffic profile or by matching the aggregated sum of all FLOWSPECs (TSPECs) currently admitted, as determined by the qpAdmissionScope property in an associated QoSPolicyRSVPAdmissionAction.
RSVP接纳策略可以根据流的流量规范（TSPEC）或请求的QoS资源量（FLOWSPEC）来决定是否接受或拒绝RSVP请求。接纳决定可以基于将单个RSVP请求与流量配置文件相匹配，或者通过匹配当前接纳的所有流规范（TSPEC）的聚合和，如相关QoSPolicyRSVPAdmissionAction中的QAppmissionScope属性所确定。
The QoSPolicyIntservTrfcProf class models both such traffic profiles. This class has the following properties:
QoSPolicyIntservTrfcProf类对这两种流量配置文件进行建模。此类具有以下属性：
1. Token Rate (r) measured in bits/sec 2. Peak Rate (p) measured in bits/sec 3. Bucket Size (b) measured in bytes 4. Min Policed unit (m) measured in bytes 5. Max packet size (M) measured in bytes 6. Resv Rate (R) measured in bits/sec 7. Slack term (s) measured in microseconds
1. 令牌速率（r），单位为比特/秒2。峰值速率（p），以比特/秒3为单位。存储桶大小（b）以字节4为单位。最小策略单位（m），以字节5为单位。以字节6为单位测量的最大数据包大小（M）。Resv速率（R），以位/秒7为单位测量。以微秒为单位测量的松弛项
The first five parameters are the traffic specification parameters used in the Integrated Service architecture ([INTSERV]). These parameters are used to define a sender TSPEC as well as a FLOWSPEC for the Controlled-Load service [CL]. For a definition and full explanation of their meanings, please refer to [RSVP-IS].
前五个参数是综合服务体系结构（[INTSERV]）中使用的流量规范参数。这些参数用于定义发送方TSPEC以及受控加载服务[CL]的流程规范。有关其含义的定义和完整解释，请参考[RSVP-IS]。
Parameters 6 and 7 are the additional parameters used for specification of the Guaranteed Service FLOWSPEC [GS].
参数6和7是用于保证服务流程规范[GS]的附加参数。
A partial order is defined between TSPECs (and FLOWSPECs). The TSPEC A is larger than the TSPEC B if and only if rA>rB, pA>pB, bA>bB, mA<mB and MA>MB. A TSPEC (FLOWSPEC) measured against a traffic profile uses the same ordering rule. An RSVP message is accepted only if its TSPEC (FLOWSPEC) is either smaller or equal to the traffic profile. Only parameters specified in the traffic profile are compared.
TSPEC（和流程规范）之间定义了部分顺序。当且仅当rA>rB、pA>pB、bA>bB、mA<mB和mA>mB时，TSPEC A大于TSPEC B。根据流量配置文件测量的TSPEC（FLOWSPEC）使用相同的排序规则。只有当RSVP消息的TSPEC（FLOWSPEC）小于或等于流量配置文件时，才会接受RSVP消息。仅比较流量配置文件中指定的参数。
The GS FLOWSPEC is compared against the rate R and the slack term s. The term R should not be larger than the traffic profile R parameter, while the FLOWSPEC slack term should not be smaller than that specified in the slack term.
将GS FLOWSPEC与速率R和松弛项s进行比较。术语R不应大于流量剖面R参数，而FLOWSPEC松弛术语不应小于松弛术语中指定的值。
TSPECs as well as FLOWSPECs can be added. The sum of two TSPECs is computed by summing the rate r, the peak rate p, the bucket size b, and by taking the minimum value of the minimum policed unit m and the maximum value of the maximum packet size M. GS FLOWSPECs are summed by adding the Resv rate and minimizing the slack term s. These rules are used to compute the temporal state of admitted RSVP states matching the traffic class defined by the rule condition. This state is compared with the traffic profile to arrive at an admission decision when the scope of the QoSPolicyRSVPAdmissionAction is set to 'class'.
可以添加TSPEC和流程规范。通过将速率r、峰值速率p、桶大小b相加，并取最小策略单元m的最小值和最大数据包大小m的最大值，计算两个tspec之和。通过添加Resv速率和最小化松弛项s，对GS流pec进行相加。这些规则用于计算与规则条件定义的流量类别相匹配的已接纳RSVP状态的时间状态。当QoSPolicyRSVPAdmissionAction的范围设置为“class”时，将此状态与流量配置文件进行比较，以得出接纳决策。
Pre-defined variables are necessary for ensuring interoperability among policy servers and policy management tools from different vendors. The purpose of this section is to define frequently used variables in QoS policy domains.
预定义变量对于确保不同供应商的策略服务器和策略管理工具之间的互操作性是必要的。本节的目的是定义QoS策略域中经常使用的变量。
Notice that this section only adds to the variable classes as defined in [PCIMe] and reuses the mechanism defined there.
请注意，本节仅添加到[PCIMe]中定义的变量类，并重用其中定义的机制。
The QoS policy information model specifies a set of pre-defined variable classes to support a set of fundamental QoS terms that are commonly used to form conditions and actions and are missing from the [PCIMe]. Examples of these include RSVP related variables. All variable classes defined in this document extend the QoSPolicyRSVPVariable class (defined in this document), which itself extends the PolicyImplictVariable class, defined in [PCIMe]. Subclasses specify the data type and semantics of the policy variables.
QoS策略信息模型指定一组预定义的变量类，以支持一组基本QoS术语，这些术语通常用于形成条件和操作，并且[PCIMe]中缺少这些术语。这些示例包括RSVP相关变量。本文档中定义的所有变量类都扩展了QoSPolicyRSVPVariable类（在本文档中定义），该类本身扩展了[PCIMe]中定义的PolicyImplictVariable类。子类指定策略变量的数据类型和语义。
This document defines the following RSVP variable classes; for details, see their class definitions:
本文件定义了以下RSVP变量类；有关详细信息，请参见其类定义：
RSVP related Variables:
RSVP相关变量：
1. QoSPolicyRSVPSourceIPv4Variable - The source IPv4 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
1. QoSPolicyRSVPSourceIPv4Variable—RSVP信号流的源IPv4地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
2. QoSPolicyRSVPDestinationIPv4Variable - The destination port of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects (for IPv4 traffic).
2. QOSPOLICYRSVPPDESTINATIONIPV4VARIABLE—RSVP信号流的目标端口，如RSVP路径和RESV会话[RSVP]对象（用于IPv4流量）中定义的。
3. QoSPolicyRSVPSourceIPv6Variable - The source IPv6 address of the RSVP signaled flow, as defied in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
3. QOSPOLICYRSVPSOURCEIPV6变量-RSVP信号流的源IPv6地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
4. QoSPolicyRSVPDestinationIPv6Variable - The destination port of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects (for IPv6 traffic).
4. QOSPOLICYRSVPPDESTIONIPV6变量-RSVP信号流的目标端口，如RSVP路径和RESV会话[RSVP]对象（用于IPv6流量）中定义的。
5. QoSPolicyRSVPSourcePortVariable - The source port of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
5. QoSPolicyRSVPSourcePortVariable—RSVP信号流的源端口，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
6. QoSPolicyRSVPDestinationPortVariable - The destination port of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
6. QOSPOLICYRSVPPDESTIONPortVariable—RSVP信号流的目标端口，如RSVP路径和RESV会话[RSVP]对象中所定义。
7. QoSPolicyRSVPIPProtocolVariable - The IP Protocol of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
7. QoSPolicyRSVPIPProtocolVariable—RSVP信号流的IP协议，如RSVP路径和RESV会话[RSVP]对象中所定义。
8. QoSPolicyRSVPIPVersionVariable - The version of the IP addresses carrying the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
8. QOSPOLICYRSVPIVIPVersionVariable—承载RSVP信号流的IP地址的版本，如RSVP路径和RESV会话[RSVP]对象中定义的。
9. QoSPolicyRSVPDCLASSVariable - The DSCP value as defined in the RSVP DCLASS [DCLASS] object.
9. QOSPOLICYRSVPCLASSVariable—RSVP DCLASS[DCLASS]对象中定义的DSCP值。
10. QoSPolicyRSVPStyleVariable - The reservation style (FF, SE, WF) as defined in the RSVP RESV message [RSVP].
10. QoSPolicyRSVPStyleVariable—RSVP RESV消息[RSVP]中定义的保留样式（FF、SE、WF）。
11. QoSPolicyRSVPIntServVariable - The type of Integrated Service (CL, GS, NULL) requested in the RSVP Reservation message, as defined in the FLOWSPEC RSVP Object [RSVP].
11. QOSPOLICYRSVPINTSERVARIABLE—RSVP保留消息中请求的集成服务类型（CL、GS、NULL），如FLOWSPEC RSVP对象[RSVP]中所定义。
12. QoSPolicyRSVPMessageTypeVariable - The RSVP message type, either PATH, PATHTEAR, RESV, RESVTEAR, RESVERR, CONF or PATHERR [RSVP].
12. QoSPolicyRSVPMessageTypeVariable—RSVP消息类型，路径、路径撕裂、RESV、RESVTEAR、RESVERR、CONF或路径错误[RSVP]。
13. QoSPolicyRSVPPreemptionPriorityVariable - The RSVP reservation priority as defined in [RFC3181].
13. QOSPOLICYRSVPREEMPTIONPRIORITYVARIABLE-在[RFC3181]中定义的RSVP保留优先级。
14. QoSPolicyRSVPPreemptionDefPriorityVariable - The RSVP preemption reservation defending priority as defined in [RFC3181].
14. QOSPOLICYRSVPRPREEMPTIONDEFPRIORITYVariable-RSVP抢占保留保护优先级，如[RFC3181]中所定义。
15. QoSPolicyRSVPUserVariable - The ID of the user that initiated the flow as defined in the User Locator string in the Identity Policy Object [RFC3182].
15. QoSPolicyRSVPUserVariable—启动流的用户的ID，如标识策略对象[RFC3182]中的用户定位器字符串中所定义。
16. QoSPolicyRSVPApplicationVariable - The ID of the application that generated the flow as defined in the application locator string in the Application policy object [RFC2872].
16. QoSPolicyRSVPApplicationVariable—生成流的应用程序的ID，如应用程序策略对象[RFC2872]中的应用程序定位器字符串中所定义。
17. QoSPolicyRSVPAuthMethodVariable - The RSVP Authentication type used in the Identity Policy Object [RFC3182].
17. QoSPolicyRSVPAuthMethodVariable—标识策略对象[RFC3182]中使用的RSVP身份验证类型。
Each class restricts the possible value types associated with a specific variable. For example, the QoSPolicyRSVPSourcePortVariable class is used to define the source port of the RSVP signaled flow. The value associated with this variable is of type PolicyIntegerValue.
每个类都限制与特定变量关联的可能值类型。例如，QoSPolicyRSVPSourcePortVariable类用于定义RSVP信号流的源端口。与此变量关联的值的类型为PolicyIntegerValue。
Values are used in the information model as building blocks for the policy conditions and policy actions, as described in [PCIM] and [PCIMe]. This section defines a set of auxiliary values that are used for QoS policies as well as other policy domains.
值在信息模型中用作策略条件和策略操作的构建块，如[PCIM]和[PCIMe]中所述。本节定义了一组用于QoS策略以及其他策略域的辅助值。
All value classes extend the PolicyValue class [PCIMe]. The subclasses specify specific data/value types that are not defined in [PCIMe].
所有值类都扩展了PolicyValue类[PCIMe]。子类指定[PCIMe]中未定义的特定数据/值类型。
This document defines the following two subclasses of the PolicyValue class:
本文档定义了PolicyValue类的以下两个子类：
QoSPolicyDNValue This class is used to represent a single or set of Distinguished Name [DNDEF] values, including wildcards. A Distinguished Name is a name that can be used as a key to retrieve an object from a directory service. This value can be used in comparison to reference values carried in RSVP policy objects, as specified in [RFC3182]. This class is defined in Section 8.31.
QoSPolicyDNValue此类用于表示单个或一组可分辨名称[DNDEF]值，包括通配符。可分辨名称是可以用作键的名称，用于从目录服务检索对象。此值可用于与[RFC3182]中指定的RSVP策略对象中携带的参考值进行比较。此类定义见第8.31节。
QoSPolicyAttributeValue A condition term uses the form "Variable matches Value", and an action term uses the form "set Variable to Value" ([PCIMe]). This class is used to represent a single or set of property values for the "Value" term in either a condition or an action. This value can be used in conjunction with reference values carried in RSVP objects, as specified in [RFC3182]. This class is defined in section 8.12.
QoSPolicyAttributeValue条件项使用“变量匹配值”形式，操作项使用“将变量设置为值”（[PCIMe]）形式。此类用于表示条件或操作中“值”项的单个或一组属性值。该值可与[RFC3182]中规定的RSVP对象中携带的参考值结合使用。此类定义见第8.12节。
The property name is used to specify which of the properties in the QoSPolicyAttributeValue class instance is being used in the condition or action term. The value of this property or properties will then
属性名称用于指定QoSPolicyAttributeValue类实例中的哪些属性正在条件或操作术语中使用。然后将显示此属性或多个属性的值
be retrieved. In the case of a condition, a match (which is dependent on the property name) will be used to see if the condition is satisfied or not. In the case of an action, the semantics are instead "set the variable to this value".
被找回。对于条件，将使用匹配项（取决于属性名称）查看是否满足条件。在操作的情况下，语义改为“将变量设置为此值”。
For example, suppose the "user" objects in the organization include several properties, among them:
例如，假设组织中的“用户”对象包括多个属性，其中包括：
- First Name - Last Name - Login Name - Department - Title
- 名-姓-登录名-部门-职务
A simple condition could be constructed to identify flows by their RSVP user carried policy object. The simple condition: Last Name = "Smith" to identify a user named Bill would be constructed in the following way:
可以构造一个简单的条件，通过RSVP用户携带的策略对象来识别流。简单的条件：Last Name=“Smith”识别一个名为Bill的用户，其构造方式如下：
A SimplePolicyCondition [PCIMe] would aggregate a QoSPolicyRSVPUserVariable [QPIM] object, via the PolicyVariableInSimplePolicyCondition [PCIMe] aggregation.
SimplePolicyCondition[PCIMe]将通过PolicyVariableInSimplePolicyCondition[PCIMe]聚合来聚合QoSPolicyRSVPUserVariable[QPIM]对象。
The implicit value associated with this condition is created in the following way:
通过以下方式创建与此条件关联的隐式值：
A QoSPolicyAttributeValue object would be aggregated to the simple condition object via a PolicyValueInSimplePolicyCondition [PCIMe]. The QoSPolicyAttributeValue attribute qpAttributeName would be set to "last name" and the qpAttributeValueList would be set to "Smith".
QoSPolicyAttributeValue对象将通过PolicyValueInSimplePolicyCondition[PCIMe]聚合到简单条件对象。QoSPolicyAttributeValue属性qpAttributeName将设置为“姓氏”，qpAttributeValueList将设置为“Smith”。
Another example is a condition that has to do with the user's organizational department. It can be constructed in the exact same way, by changing the QoSPolicyAttributeValue attribute qpAttributeName to "Department" and the qpAttributeValueList would be set to the particular value that is to be matched (e.g., "engineering" or "customer support"). The logical condition would than be evaluated to true if the user belong to either the engineering department or the customer support.
另一个例子是与用户的组织部门有关的条件。通过将QoSPolicyAttributeValue属性qpAttributeName更改为“Department”，qpAttributeValueList将被设置为要匹配的特定值（例如，“engineering”或“customer support”），可以以完全相同的方式构造它。如果用户属于工程部门或客户支持部门，则逻辑条件将被评估为true。
Notice that many multiple-attribute objects require the use of the QoSPolicyAttributeValue class to specify exactly which of its attributes should be used in the condition match operation.
请注意，许多多属性对象需要使用QoSPolicyAttributeValue类来精确指定在条件匹配操作中应使用其哪些属性。
The following sections define associations that are specified by QPIM.
以下部分定义了QPIM指定的关联。
This association links a QoSPolicyTrfcProf object (defined in section 8.9), modeling a specific traffic profile, to a QoSPolicyAdmissionAction object (defined in section 8.2). The class definition for this association is as follows:
该关联将QospolicyTRFCROF对象（定义见第8.9节）链接到QospolicyAdministrationAction对象（定义见第8.2节），该对象建模特定的流量配置文件。此关联的类定义如下所示：
NAME QoSPolicyTrfcProfInAdmissionAction DESCRIPTION A class representing the association between a QoS admission action and its traffic profile. DERIVED FROM Dependency (See [PCIM]) ABSTRACT FALSE PROPERTIES Antecedent[ref QoSPolicyAdmissionAction [0..n]] Dependent[ref QoSPolicyTrfcProf [1..1]]
名称QOSpolicyTRFCROFINAMISSIONAction描述表示QoS许可操作与其流量配置文件之间的关联的类。派生自依赖项（请参见[PCIM]）抽象假属性先行项[ref-QospolicyAdministrationAction[0..n]]依赖项[ref-QospolicyTRFCROF[1..1]]
This property is inherited from the Dependency association, defined in [PCIM]. Its type is overridden to become an object reference to a QoSPolicyAdmissionAction object. This represents the "independent" part of the association. The [0..n] cardinality indicates that any number of QoSPolicyAdmissionAction object(s) may use a given QoSPolicyTrfcProf.
此属性继承自[PCIM]中定义的依赖项关联。其类型被重写为QosPolicyAdministrationAction对象的对象引用。这代表了协会的“独立”部分。[0..n]基数表示任意数量的QospolicyAdministrationAction对象都可以使用给定的QospolicyTRFCROF。
This property is inherited from the Dependency association, and is overridden to become an object reference to a QoSPolicyTrfcProf object. This represents a specific traffic profile that is used by any number of QoSPolicyAdmissionAction objects. The [1..1] cardinality means that exactly one object of the QoSPolicyTrfcProf can be used by a given QoSPolicyAddmissionAction.
此属性从依赖项关联继承，并被重写为QospolicyTRFCROF对象的对象引用。这表示由任意数量的QosPolicyAdministrationAction对象使用的特定流量配置文件。[1..1]基数意味着给定的QoSPolicyAddmissionAction可以使用QospolicyTRFCROF的一个对象。
This association links a policing action with an object defining an action to be applied to conforming traffic relative to the associated traffic profile. The class definition for this association is as follows:
此关联将警务操作与一个对象链接起来，该对象定义了要应用于符合相关流量配置文件的一致性流量的操作。此关联的类定义如下所示：
NAME PolicyConformAction DESCRIPTION A class representing the association between a policing action and the action that should be applied to traffic conforming to an associated traffic profile. DERIVED FROM Dependency (see [PCIM]) ABSTRACT FALSE PROPERTIES Antecedent[ref QoSPolicyPoliceAction[0..n]] Dependent[ref PolicyAction [1..1]]
NAME PolicyConformation DESCRIPTION一个类，表示策略操作和应应用于符合关联流量配置文件的流量的操作之间的关联。派生自依赖项（请参见[PCIM]）抽象假属性先行项[ref QospolicyPolicyAction[0..n]]依赖项[ref PolicyAction[1..1]]
This property is inherited from the Dependency association. Its type is overridden to become an object reference to a QoSPolicyPoliceAction object. This represents the "independent" part of the association. The [0..n] cardinality indicates that any number of QoSPolicyPoliceAction objects may be given the same action to be executed as the conforming action.
此属性是从依赖项关联继承的。其类型被重写为QospolicyPolicyAction对象的对象引用。这代表了协会的“独立”部分。[0..n]基数表示，任何数量的QospolicyPolicyAction对象都可以被赋予与一致性操作相同的要执行的操作。
This property is inherited from the Dependency association, and is overridden to become an object reference to a PolicyAction object. This represents a specific policy action that is used by a given QoSPolicyPoliceAction. The [1..1] cardinality means that exactly one policy action can be used as the "conform" action for a QoSPolicyPoliceAction. To execute more than one conforming action, use the PolicyCompoundAction class to model the conforming action.
此属性从依赖项关联继承，并被重写为对PolicyAction对象的对象引用。这表示给定QospolicyPolicyAction使用的特定策略操作。[1..1]基数意味着只有一个策略操作可以用作QospolicyPolicyAction的“符合”操作。要执行多个一致性操作，请使用PolicyCompoundAction类对一致性操作建模。
This association links a policing action with an object defining an action to be applied to traffic exceeding the associated traffic profile. The class definition for this association is as follows:
此关联将警务操作与定义要应用于超出关联流量配置文件的流量的操作的对象相链接。此关联的类定义如下所示：
NAME QoSPolicyExceedAction DESCRIPTION A class representing the association between a policing action and the action that should be applied to traffic exceeding an associated traffic profile. DERIVED FROM Dependency (see [PCIM]) ABSTRACT FALSE PROPERTIES Antecedent[ref QoSPolicePoliceAction[0..n]] Dependent[ref PolicyAction [1..1]]
名称QoSPolicyExceedAction描述一个类，表示策略操作和应应用于超出关联流量配置文件的流量的操作之间的关联。派生自依赖项（请参见[PCIM]）抽象假属性先行项[ref QosPolicePolicyAction[0..n]]依赖项[ref PolicyAction[1..1]]
This property is inherited from the Dependency association. Its type is overridden to become an object reference to a QoSPolicyPoliceAction object. This represents the "independent" part of the association. The [0..n] cardinality indicates that any number of QoSPolicyPoliceAction objects may be given the same action to be executed as the exceeding action.
此属性是从依赖项关联继承的。其类型被重写为QospolicyPolicyAction对象的对象引用。这代表了协会的“独立”部分。[0..n]基数表示，任何数量的QospolicyPolicyAction对象都可能被赋予与超出操作相同的要执行的操作。
This property is inherited from the Dependency association, and is overridden to become an object reference to a PolicyAction object. This represents a specific policy action that is used by a given QoSPolicyPoliceAction. The [1..1] cardinality means that a exactly one policy action can be used as the "exceed" action by a QoSPolicyPoliceAction. To execute more than one conforming action, use the PolicyCompoundAction class to model the exceeding action.
此属性从依赖项关联继承，并被重写为对PolicyAction对象的对象引用。这表示给定QospolicyPolicyAction使用的特定策略操作。[1..1]基数意味着QospolicyPolicyAction可以将恰好一个策略操作用作“超出”操作。要执行多个一致性操作，请使用PolicyCompoundAction类对超出的操作建模。
This association links a policing action with an object defining an action to be applied to traffic violating the associated traffic profile. The class definition for this association is as follows:
此关联将策略操作与定义要应用于违反关联流量配置文件的流量的操作的对象相链接。此关联的类定义如下所示：
NAME PolicyViolateAction DESCRIPTION A class representing the association between a policing action and the action that should be applied to traffic violating an associated traffic profile. DERIVED FROM Dependency (see [PCIM]) ABSTRACT FALSE PROPERTIES Antecedent[ref QoSPolicePoliceAction[0..n]] Dependent[ref PolicyAction [1..1]]
NAME PolicyViolateAction DESCRIPTION一个类，表示策略操作和应应用于违反关联流量配置文件的流量的操作之间的关联。派生自依赖项（请参见[PCIM]）抽象假属性先行项[ref QosPolicePolicyAction[0..n]]依赖项[ref PolicyAction[1..1]]
This property is inherited from the Dependency association. Its type is overridden to become an object reference to a QoSPolicyPoliceAction object. This represents the "independent" part of the association. The [0..n] cardinality indicates that any number of QoSPolicyPoliceAction objects may be given the same action to be executed as the violating action.
此属性是从依赖项关联继承的。其类型被重写为QospolicyPolicyAction对象的对象引用。这代表了协会的“独立”部分。[0..n]基数表示任何数量的QospolicyPolicyAction对象都可能被赋予与违规操作相同的要执行的操作。
This property is inherited from the Dependency association, and is overridden to become an object reference to a PolicyAction object. This represents a specific policy action that is used by a given QoSPolicyPoliceAction. The [1..1] cardinality means that exactly one policy action can be used as the "violate" action by a QoSPolicyPoliceAction. To execute more than one violating action, use the PolicyCompoundAction class to model the conforming action.
此属性从依赖项关联继承，并被重写为对PolicyAction对象的对象引用。这表示给定QospolicyPolicyAction使用的特定策略操作。[1..1]基数意味着QospolicyPolicyAction只能将一个策略操作用作“违反”操作。要执行多个违反操作，请使用PolicyCompoundAction类对符合性操作建模。
A simple RSVP policy action is represented as a pair {variable, value}. This aggregation provides the linkage between a QoSPolicyRSVPSimpleAction instance and a single QoSPolicyRSVPVariable. The aggregation PolicyValueInSimplePolicyAction links the QoSPolicyRSVPSimpleAction to a single PolicyValue.
简单的RSVP策略操作表示为一对{变量，值}。此聚合提供QoSPolicyRSVPSimpleAction实例和单个QoSPolicyRSVPVariable之间的链接。聚合PolicyValueInSimplePolicyAction将QoSPolicyRSVPSimpleAction链接到单个PolicyValue。
The class definition for this aggregation is as follows:
此聚合的类定义如下所示：
NAME QoSPolicyRSVPVariableInRSVPSimplePolicyAction DERIVED FROM PolicyVariableInSimplePolicyAction ABSTRACT FALSE PROPERTIES GroupComponent[ref QoSPolicyRSVPSimpleAction [0..n]] PartComponent[ref QoSPolicyRSVPVariable [1..1] ]
从PolicyVariableInSimplePolicyAction抽象属性GroupComponent派生的名称QoSPolicyRSVPVariableInRSVPSimplePolicyAction[0..n]]PartComponent[ref QoSPolicyRSVPVariable[1..1]]
The reference property "GroupComponent" is inherited from PolicyComponent, and overridden to become an object reference to a QoSPolicyRSVPSimpleAction that contains exactly one QoSPolicyRSVPVariable. Note that for any single instance of the aggregation class QoSPolicyRSVPVariableInRSVPSimplePolicyAction, this property is single-valued. The [0..n] cardinality indicates that there may be 0, 1, or more QoSPolicyRSVPSimpleAction objects that contain any given RSVP variable object.
引用属性“GroupComponent”继承自PolicyComponent，并被重写为对仅包含一个QoSPolicyRSVPVariable的QoSPolicyRSVPSimpleAction的对象引用。请注意，对于聚合类QoSPolicyRSVPVariableInRSVPSimplePolicyAction的任何单个实例，此属性都是单值的。[0..n]基数表示可能有0个、1个或多个QoSPolicyRSVPSimpleAction对象包含任何给定的RSVP变量对象。
The reference property "PartComponent" is inherited from PolicyComponent, and overridden to become an object reference to a QoSPolicyRSVPVariable that is defined within the scope of a QoSPolicyRSVPSimpleAction. Note that for any single instance of the association class QoSPolicyRSVPVariableInRSVPSimplePolicyAction, this property (like all reference properties) is single-valued. The
引用属性“PartComponent”继承自PolicyComponent，并被重写为对QoSPolicyRSVPVariable的对象引用，该变量在QoSPolicyRSVPSimpleAction范围内定义。请注意，对于关联类QoSPolicyRSVPVariableInRSVPSimplePolicyAction的任何单个实例，此属性（与所有引用属性一样）都是单值的。这个
[1..1] cardinality indicates that a QoSPolicyRSVPVariableInRSVPSimplePolicyAction must have exactly one RSVP variable defined within its scope in order to be meaningful.
[1..1]基数表示QoSPolicyRSVPVariableInRSVPSimplePolicyAction必须在其范围内定义一个RSVP变量才能有意义。
The following sections define object classes that are specified by QPIM.
以下部分定义由QPIM指定的对象类。
This class is used to specify that packets should be discarded. This is the same as stating that packets should be denied forwarding. The class definition is as follows:
此类用于指定应丢弃的数据包。这与声明应拒绝数据包转发相同。类别定义如下：
NAME QoSPolicyDiscardAction DESCRIPTION This action specifies that packets should be discarded. DERIVED FROM PolicyAction (defined in [PCIM]) ABSTRACT FALSEFALSE PROPERTIES None
名称QoSPolicyDiscardAction描述此操作指定应丢弃数据包。派生自PolicyAction（在[PCIM]中定义）抽象FALSEFALSE属性无
This class is the base class for performing admission decisions based on a comparison of a meter measuring the temporal behavior of a flow or a set of flow with a traffic profile. The qpAdmissionScope property controls whether the comparison is done per flow or per class (of flows). Only packets that conform to the traffic profile are admitted for further processing; other packets are discarded. The class definition is as follows:
该类是基于测量流量或一组流量的时间行为的仪表与流量剖面的比较来执行接纳决策的基类。QpAdministrationScope属性控制是按流还是按类（流）进行比较。仅允许符合业务简档的分组进行进一步处理；其他数据包被丢弃。类别定义如下：
NAME QoSPolicyAdmissionAction DESCRIPTION This action controls admission decisions based on comparison of a meter to a traffic profile. DERIVED FROM PolicyAction (defined in [PCIM]) ABSTRACT FALSEFALSE PROPERTIES qpAdmissionScope
名称QOSpolicyAdministrationAction描述此操作基于仪表与流量配置文件的比较来控制接纳决策。源自PolicyAction（在[PCIM]中定义）抽象FALSEFALSE属性QPamissionScope
This attribute specifies whether the admission decision is done per flow or per the entire class of flows defined by the rule condition. If the scope is "flow", the actual or requested rate of each flow is compared against the traffic profile. If the scope is set to "class", the aggregate actual or requested rate of all flows matching the rule condition is measured against the traffic profile. The property is defined as follows:
此属性指定是按每个流还是按规则条件定义的整个流类执行接纳决策。如果范围为“流量”，则将每个流量的实际或请求速率与流量剖面进行比较。如果范围设置为“类”，则根据流量配置文件测量与规则条件匹配的所有流的聚合实际或请求速率。该属性的定义如下：
NAME qpAdmissionScope DESCRIPTION This property specifies whether the admission decision is done per flow or per the entire class of flows. SYNTAX Integer VALUE This is an enumerated integer. A value of 0 specifies that admission is done on a per-flow basis, and a value of 1 specifies that admission is done on a per-class basis.
NAME QPamissionScope DESCRIPTION此属性指定是针对每个流还是针对整个流类执行接纳决策。语法整数值这是一个枚举整数。值0指定在每个流的基础上进行准入，值1指定在每个类的基础上进行准入。
This is used for defining policing actions (i.e., those actions that restrict traffic based on a comparison with a traffic profile). Using the three associations QoSPolicyConformAction, QoSPolicyExceedAction and QoSPolicyViolateAction, it is possible to specify different actions to take based on whether the traffic is conforming, exceeding, or violating a traffic profile. The traffic profile is specified in a subclass of the QoSPolicyTrfcProf class. The class definition is as follows:
这用于定义策略操作（即，基于与流量配置文件的比较限制流量的操作）。使用QospolicyConformation、QoSPolicyExceedAction和QoSPolicyViolateAction三个关联，可以根据流量是否符合、超过或违反流量配置文件来指定要采取的不同行动。流量配置文件在QoSPolicyTrfcProf类的子类中指定。类别定义如下：
NAME QoSPolicyPoliceAction DESCRIPTION This action controls the operation of policers. The rate of flows is measured against a traffic profile. The actions that need to be performed on conforming, exceeding and violating traffic are indicated using the conform, exceed and violate action associations. DERIVED FROM QoSPolicyAdmissionAction (defined in this document) ABSTRACT FALSEFALSE PROPERTIES None
名称QOSpolicyPolicyAction描述此操作控制策略的操作。流量根据交通状况进行测量。需要对符合、超过和违反流量执行的操作使用符合、超过和违反操作关联指示。源自QospolicyAdministrationAction（在本文档中定义）抽象FALSEFALSE属性无
This class is used for defining shaping actions. Shapers are used to delay some or all of the packets in a traffic stream in order to bring a particular traffic stream into compliance with a given traffic profile. The traffic profile is specified in a subclass of the QoSPolicyTrfcProf class. The class definition is as follows:
此类用于定义造型动作。整形器用于延迟业务流中的部分或全部分组，以便使特定业务流符合给定的业务简档。流量配置文件在QoSPolicyTrfcProf类的子类中指定。类别定义如下：
NAME QoSPolicyShapeAction DESCRIPTION This action indicate that traffic should be shaped to be conforming with a traffic profile. DERIVED FROM QoSPolicyAdmissionAction (defined in this document) ABSTRACT FALSEFALSE PROPERTIES None
名称QoSPolicyShapeAction描述此操作表示应将流量塑造为符合流量配置文件。源自QospolicyAdministrationAction（在本文档中定义）抽象FALSEFALSE属性无
This class determines whether to accept or reject a given RSVP request by comparing the RSVP request's TSPEC or RSPEC parameters against the associated traffic profile and/or by enforcing the pre-set maximum sessions limit. The traffic profile is specified in the QoSPolicyIntServTrfcProf class. This class inherits the qpAdmissionScope property from its superclass. This property specifies whether admission should be done on a per-flow or per-class basis. If the traffic profile is not larger than or equal to the requested reservation, or to the sum of the admitted reservation merged with the requested reservation, the result is a deny decision. If no traffic profile is specified, the assumption is that all traffic can be admitted.
此类通过将RSVP请求的TSPEC或RSPEC参数与相关的流量配置文件进行比较和/或通过强制执行预设的最大会话限制来确定是否接受或拒绝给定的RSVP请求。流量配置文件在QoSPolicyIntServTrfcProf类中指定。此类从其超类继承QPamissionScope属性。此属性指定是基于每个流还是基于每个类进行准入。如果流量配置文件不大于或等于请求的预约，或不大于与请求的预约合并的已接纳预约的总和，则结果是拒绝决定。如果未指定流量配置文件，则假设所有流量都可以进入。
The class definition is as follows:
类别定义如下：
NAME QoSPolicyRSVPAdmissionAction DESCRIPTION This action controls the admission of RSVP requests. Depending on the scope, either a single RSVP request or the total admitted RSVP requests matching the conditions are compared against a traffic profile. DERIVED FROM QoSPolicyAdmissionAction (defined in this document) ABSTRACT FALSEFALSE PROPERTIES qpRSVPWarnOnly, qpRSVPMaxSessions
名称QoSPolicyRSVPAdmissionAction描述此操作控制RSVP请求的允许。根据作用域的不同，将单个RSVP请求或与条件匹配的总允许RSVP请求与流量配置文件进行比较。源自QOSpolicyAdministrationAction（在本文档中定义）抽象FalseFalseProperties qpRSVPWarnOnly、qpRSVPMaxSessions
This property is applicable when fulfilling ("admitting") an RSVP request would violate the policer (traffic profile) limits or when the maximum number session would be exceeded (or both).
当满足（“承认”）RSVP请求将违反POLICYR（流量配置文件）限制或超过最大会话数（或两者）时，此属性适用。
When this property is set to TRUE, the RSVP request is admitted in spite of the violation, but an RSVP error message carrying a warning is sent to the originator (sender or receiver). When set to FALSE, the request would be denied and an error message would be sent back to the originator. So the meaning of the qpWarnOnly flag is: Based on property's value (TRUE or FALSE), determine whether to admit but warn the originator that the request is in violation or to deny the request altogether (and send back an error).
当此属性设置为TRUE时，尽管存在冲突，RSVP请求仍会被接受，但会向发起人（发送方或接收方）发送一条带有警告的RSVP错误消息。当设置为FALSE时，请求将被拒绝，并将错误消息发送回发起人。因此，qpWarnOnly标志的含义是：根据属性的值（TRUE或FALSE），确定是承认但警告发端人请求违反了，还是完全拒绝请求（并发回错误）。
Specifically, a PATHERR (in response to a Path message) or a RESVERR (in response of a RESV message) will be sent. This follows the COPS for RSVP send error flag in the Decision Flags object. This property is defined as follows:
具体而言，将发送PATHERR（响应路径消息）或RESVERR（响应RESV消息）。这遵循Decision Flags对象中的COPS for RSVP send error标志。该属性定义如下：
NAME qpRSVPWarnOnly SYNTAX Boolean Default FALSE VALUE The value TRUE means that the request should be admitted AND an RSVP warning message should be sent to the originator. The value of FALSE means that the request should be not admitted and an appropriate error message should be sent back to the originator of the request.
名称QPRSVPWRNONLY语法布尔默认值FALSE值TRUE表示应允许请求，并应向发起人发送RSVP警告消息。FALSE的值表示不应接受请求，并应将适当的错误消息发送回请求的发起人。
This attribute is used to limit the total number of RSVP requests admitted for the specified class of traffic. For this property to be meaningful, the qpAdmissionScope property must be set to class. The definition of this property is as follows:
此属性用于限制指定流量类别允许的RSVP请求总数。要使此属性有意义，必须将QPamissionScope属性设置为class。该财产的定义如下：
NAME qpRSVPMaxSessions SYNTAX Integer VALUE Must be greater than 0.
名称qpRSVPMaxSessions语法整数值必须大于0。
This class is a base class that is used to define the per-hop behavior that is to be assigned to behavior aggregates. It defines a common property, qpMaxPacketSize, for use by its subclasses (QoSPolicyBandwidthAction and QoSPolicyCongestionControlAction). The class definition is as follows:
此类是一个基类，用于定义要分配给行为聚合的每跳行为。它定义了一个公共属性qpMaxPacketSize，供其子类（QoSPolicyBandwidthAction和QospolicyCongestOnControlAction）使用。类别定义如下：
NAME QoSPolicyPHBAction DESCRIPTION This action controls the Per-Hop-Behavior provided to behavior aggregates. DERIVED FROM PolicyAction (defined in [PCIM]) ABSTRACT TRUE PROPERTIES qpMaxPacketSize
名称QOSpolicyPbAction描述此操作控制提供给行为聚合的每跳行为。源自PolicyAction（在[PCIM]中定义）抽象真实属性qpMaxPacketSize
This property specifies the maximum packet size in bytes, of packets in the designated flow. This attribute is used in translation of QPIM attributes to QoS mechanisms used within a PEP. For example, queue length may be measured in bytes, while the minimum number of packets that should be kept in a PEP is defined within QPIM in number of packets. This property is defined as follows:
此属性指定指定流中数据包的最大数据包大小（以字节为单位）。此属性用于将QPIM属性转换为PEP中使用的QoS机制。例如，队列长度可以以字节为单位进行测量，而应保留在PEP中的最小分组数在QPIM中以分组数为单位进行定义。该属性定义如下：
NAME qpMaxPacketSize SYNTAX Integer Value Must be greater than 0
名称qpMaxPacketSize语法整数值必须大于0
This class is used to control the bandwidth, delay, and forwarding behavior of a PHB. Its class definition is as follows:
此类用于控制PHB的带宽、延迟和转发行为。其类别定义如下：
NAME QoSPolicyBandwidthAction DESCRIPTION This action controls the bandwidth, delay, and forwarding characteristics of the PHB. DERIVED FROM QoSPolicyPBHAction (defined in this document) ABSTRACT FALSE PROPERTIES qpForwardingPriority, qpBandwidthUnits, qpMinBandwdith, qpMaxBandwidth, qpMaxDelay, qpMaxJitter, qpFairness
名称QoSPolicyBandwidthAction描述此操作控制PHB的带宽、延迟和转发特性。源自QOSPolicyPbAction（在本文档中定义）抽象错误属性qpForwardingPriority、qpBandwidthUnits、qpMinBandwdith、qpMaxBandwidth、qpMaxDelay、qpMaxJitter、QpFairity
This property defines the forwarding priority for this set of flows. A non-zero value indicates that preemptive forwarding is required. Higher values represent higher forwarding priority. This property is defined as follows:
此属性定义此流集的转发优先级。非零值表示需要抢先转发。值越高表示转发优先级越高。该属性定义如下：
NAME qpForwardingPriority SYNTAX Integer VALUE Must be non-negative. The value 0 means that preemptive forwarding is not required. A positive value indicates the priority that is to be assigned for this (set of) flow(s). Larger values represent higher priorities.
NAME QForwardingPriority语法整数值必须为非负。值0表示不需要抢先转发。正值表示要为此（一组）流分配的优先级。值越大表示优先级越高。
This property defines the units that the properties qpMinBandwidth and qpMaxBandwidth have. Bandwidth can either be defined in bits/sec or as a percentage of the available bandwidth or scheduler resources. This property is defined as follows:
此属性定义属性qpMinBandwidth和qpMaxBandwidth具有的单位。带宽可以以位/秒或可用带宽或调度程序资源的百分比定义。该属性定义如下：
NAME qpBandwidthUnits SYNTAX Integer VALUE Two values are possible. The value of 0 is used to specify units of bits/sec, while the value of 1 is used to specify units as a percentage of the available bandwidth. If this property indicates that the bandwidth units are percentages, then each of the bandwidth properties expresses a whole-number percentage, and hence its maximum value is 100.
名称qpBandwidthUnits语法整数值两个值是可能的。值0用于指定位/秒的单位，而值1用于指定单位占可用带宽的百分比。如果此属性表示带宽单位为百分比，则每个带宽属性表示一个整数百分比，因此其最大值为100。
This property defines the minimum bandwidth that should be reserved for this class of traffic. Both relative (i.e., a percentage of the bandwidth) and absolute (i.e., bits/second) values can be specified according to the value of the qpBandwidthUnits property. This property is defined as follows:
此属性定义应为此类流量保留的最小带宽。可以根据qpBandwidthUnits属性的值来指定相对（即，带宽的百分比）和绝对（即，比特/秒）值。该属性定义如下：
NAME qpMinBandwidth SYNTAX Integer VALUE The value must be greater than 0. If the property qpMaxBandwidth is defined, then the value of qpMinBandwidth must be less than or equal to the value of qpMaxBandwidth.
NAME qpMinBandwidth语法整数值该值必须大于0。如果定义了属性qpMaxBandwidth，则qpMinBandwidth的值必须小于或等于qpMaxBandwidth的值。
This property defines the maximum bandwidth that should be allocated to this class of traffic. Both relative (i.e., a percentage of the bandwidth)and absolute (i.e., bits/second) values can be specified according to the value of the qpBandwidthUnits property. This property is defined as follows:
此属性定义应分配给此类流量的最大带宽。可以根据qpBandwidthUnits属性的值来指定相对（即，带宽的百分比）和绝对（即，比特/秒）值。该属性定义如下：
NAME qpMaxBandwidth SYNTAX Integer VALUE The value must be greater than 0. If the property qpMaxBandwidth is defined, then the value of qpMinBandwidth must be less than or equal to the value of qpMaxBandwidth.
名称qpMaxBandwidth语法整数值该值必须大于0。如果定义了属性qpMaxBandwidth，则qpMinBandwidth的值必须小于或等于qpMaxBandwidth的值。
This property defines the maximal per-hop delay that traffic of this class should experience while being forwarded through this hop. The maximum delay is measured in microseconds. This property is defined as follows:
此属性定义此类的流量在通过此跃点转发时应经历的最大每跃点延迟。最大延迟以微秒为单位测量。该属性定义如下：
NAME qpMaxDelay SYNTAX Integer (microseconds) VALUE The value must be greater than 0.
名称qpMaxDelay语法整数（微秒）值该值必须大于0。
This property defines the maximal per-hop delay variance that traffic of this class should experience while being forwarded through this hop. The maximum jitter is measured in microseconds. This property is defined as follows:
此属性定义此类流量在通过此跃点转发时应经历的最大每跃点延迟方差。最大抖动以微秒为单位测量。该属性定义如下：
NAME qpMaxJitter SYNTAX Integer (microseconds) VALUE The value must be greater than 0.
名称qpMaxJitter语法整数（微秒）值该值必须大于0。
This property defines whether fair queuing is required for this class of traffic. This property is defined as follows:
此属性定义此类流量是否需要公平排队。该属性定义如下：
NAME qpFairness SYNTAX Boolean VALUE The value of FALSE means that fair queuing is not required for this class of traffic, while the value of TRUE means that fair queuing is required for this class of traffic.
NAME QPFirity SYNTAX Boolean VALUE FALSE的值表示此类流量不需要公平排队，而TRUE的值表示此类流量需要公平排队。
This class is used to control the characteristics of the congestion control algorithm being used. The class definition is as follows:
此类用于控制正在使用的拥塞控制算法的特性。类别定义如下：
NAME QoSPolicyCongestionControlAction DESCRIPTION This action control congestion control characteristics of the PHB. DERIVED FROM QoSPolicyPBHAction (defined in this document) ABSTRACT FALSE PROPERTIES qpQueueSizeUnits, qpQueueSize, qpDropMethod, qpDropThresholdUnits, qpDropMinThresholdValue, qpDropMaxThresholdValue
名称QoSPolicyCongestionControlAction描述此操作控制PHB的拥塞控制特性。源自QoSpolicypbAction（在本文档中定义）抽象假属性qpQueueSizeUnits、qpQueueSize、qpDropMethod、qpDropThresholdUnits、qpDropMinThresholdValue、qpDropMaxThresholdValue
This property specifies the units in which the qpQueueSize attribute is measured. The queue size is measured either in number of packets or in units of time. The time interval specifies the time needed to transmit all packets within the queue if the link speed is dedicated entirely to transmission of packets within this queue. The property definition is:
此属性指定测量qpQueueSize属性的单位。队列大小以数据包的数量或时间单位来度量。如果链路速度完全用于传输队列内的数据包，则时间间隔指定传输队列内所有数据包所需的时间。属性定义为：
NAME qpQueueSizeUnits SYNTAX Integer VALUE This property can have two values. If the value is set to 0, then the unit of measurement is number of packets. If the value is set to 1, then the unit of measurement is milliseconds.
NAME qpQueueSizeUnits语法整数值此属性可以有两个值。如果该值设置为0，则测量单位为数据包数。如果该值设置为1，则测量单位为毫秒。
This property specifies the maximum queue size in packets or in milliseconds, depending on the value of the qpQueueSizeUnits (0 specifies packets, and 1 specifies milliseconds). This property is defined as follows:
此属性指定最大队列大小（以数据包为单位或以毫秒为单位），具体取决于qpQueueSizeUnits的值（0指定数据包，1指定毫秒）。该属性定义如下：
NAME qpQueueSize SYNTAX Integer VALUE This value must be greater than 0.
NAME qpQueueSize语法整数值此值必须大于0。
This property specifies the congestion control drop algorithm that should be used for this type of traffic. This property is defined as follows:
此属性指定应用于此类型流量的拥塞控制丢弃算法。该属性定义如下：
NAME qpDropMethod SYNTAX Integer VALUES Three values are currently defined. The value 0 specifies a random drop algorithm, the value 1 specifies a tail drop algorithm, and the value 2 specifies a head drop algorithm.
名称qpDropMethod语法整数值当前定义了三个值。值0指定随机下降算法，值1指定尾部下降算法，值2指定头部下降算法。
This property specifies the units in which the two properties qpDropMinThresholdValue and qpDropMaxThresholdValue are measured. Thresholds can be measured either in packets or as a percentage of the available queue sizes. This property is defined as follows:
此属性指定测量两个属性qpDropMinThresholdValue和qpDropMaxThresholdValue的单位。阈值可以以数据包或可用队列大小的百分比来度量。该属性定义如下：
NAME qpDropThresholdUnits SYNTAX Integer VALUES Three values are defined. The value 0 defines the units as number of packets, the value 1 defines the units as a percentage of the queue size and the value 2 defines the units in milliseconds. If this property indicates that the threshold units are percentages, then each of the threshold properties expresses a whole-number percentage, and hence its maximum value is 100.
名称qpDropThresholdUnits语法整数值定义了三个值。值0将单位定义为数据包数，值1将单位定义为队列大小的百分比，值2以毫秒为单位定义单位。如果此属性指示阈值单位为百分比，则每个阈值属性表示一个整数百分比，因此其最大值为100。
This property specifies the minimum number of queuing and buffer resources that should be reserved for this class of flows. The threshold can be specified as either relative (i.e., a percentage) or absolute (i.e., number of packets or millisecond) value according to the value of the qpDropThresholdUnits property. If this property
此属性指定为此类流保留的队列和缓冲区资源的最小数量。根据qpDropThresholdUnits属性的值，可以将阈值指定为相对（即百分比）或绝对（即分组数或毫秒）值。如果这个属性
specifies a value of 5 packets, then enough buffer and queuing resources should be reserved to hold 5 packets before running the specified congestion control drop algorithm. This property is defined as follows:
指定5个数据包的值，则在运行指定的拥塞控制丢弃算法之前，应保留足够的缓冲区和队列资源以容纳5个数据包。该属性定义如下：
NAME qpDropMinThresholdValue SYNTAX Integer VALUE This value must be greater than or equal to 0. If the property qpDropMaxThresholdValue is defined, then the value of the qpDropMinThresholdValue property must be less than or equal to the value of the qpDropMaxThresholdValue property.
名称qpDropMinThresholdValue语法整数值此值必须大于或等于0。如果定义了属性qpDropMaxThresholdValue，则qpDropMinThresholdValue属性的值必须小于或等于qpDropMaxThresholdValue属性的值。
This property specifies the maximum number of queuing and buffer resources that should be reserved for this class of flows. The threshold can be specified as either relative (i.e., a percentage) or absolute (i.e., number of packets or milliseconds) value according to the value of the qpDropThresholdUnits property. Congestion Control droppers should not keep more packets than the value specified in this property. Note, however, that some droppers may calculate queue occupancy averages, and therefore the actual maximum queue resources should be larger. This property is defined as follows:
此属性指定应为此类流保留的最大队列和缓冲区资源数。根据qpDropThresholdUnits属性的值，可以将阈值指定为相对值（即百分比）或绝对值（即包数或毫秒数）。拥塞控制拖放器保留的数据包不应超过此属性中指定的值。但是，请注意，一些滴管可能会计算队列占用率平均值，因此实际最大队列资源应该更大。该属性定义如下：
NAME qpDropMaxThresholdValue SYNTAX Integer VALUE This value must be greater than or equal to 0. If the property qpDropMinThresholdValue is defined, then the value of the qpDropMinThresholdValue property must be less than or equal to the value of the qpDropMaxThresholdValue property.
名称qpDropMaxThresholdValue语法整数值此值必须大于或等于0。如果定义了属性qpDropMinThresholdValue，则qpDropMinThresholdValue属性的值必须小于或等于qpDropMaxThresholdValue属性的值。
This is an abstract base class that models a traffic profile. Traffic profiles specify the maximum rate parameters used within admission decisions. The association QoSPolicyTrfcProfInAdmissionAction binds the admission decision to the traffic profile. The class definition is as follows:
这是一个抽象基类，用于建模流量配置文件。流量配置文件指定准入决策中使用的最大速率参数。关联QospolicyTRFCROFINAMISSIONAction将接纳决定绑定到流量配置文件。类别定义如下：
NAME QoSPolicyTrfcProf DERIVED FROM Policy (defined in [PCIM]) ABSTRACT TRUE PROPERTIES None
名称QOSPOLICYTRFCROF派生自策略（在[PCIM]中定义）抽象真实属性无
This class models a two- or three-level Token Bucket traffic profile. Additional profiles can be modeled by cascading multiple instances of this class (e.g., by connecting the output of one instance to the input of another instance). This traffic profile carries the policer or shaper rate values to be enforced on a flow or a set of flows. The class definition is as follows:
此类为两级或三级令牌桶流量配置文件建模。通过级联此类的多个实例（例如，通过将一个实例的输出连接到另一个实例的输入），可以对其他概要文件进行建模。此流量配置文件包含要在一个流或一组流上强制执行的策略器或整形器速率值。类别定义如下：
NAME QoSPolicyTokenBucketTrfcProf DERIVED FROM QoSPolicyTrfcProf (defined in this document) ABSTRACT FALSE PROPERTIES qpTBRate, qpTBNormalBurst, qpTBExcessBurst
名称QoSPolicyTokenBucketTrfcProf派生自QOSPOLICYTRFCROF（在本文档中定义）抽象错误属性qpTBRate、qpTBNormalBurst、QPTBEXExcessBurst
This is a non-negative integer that defines the token rate in kilobits per second. A rate of zero means that all packets will be out of profile. This property is defined as follows:
这是一个非负整数，定义令牌速率（以千比特每秒为单位）。速率为零意味着所有数据包都将超出配置文件。该属性定义如下：
NAME qpTBRate SYNTAX Integer VALUE This value must be greater than to 0
名称qpTBRate语法整数值此值必须大于0
This property is an integer that defines the normal size of a burst measured in bytes. This property is defined as follows:
此属性是一个整数，用于定义突发的正常大小（以字节为单位）。该属性定义如下：
NAME qpTBNormalBurst SYNTAX Integer VALUE This value must be greater than to 0
名称qpTBNormalBurst语法整数值此值必须大于0
This property is an integer that defines the excess burst size measured in bytes. This property is defined as follows:
此属性是一个整数，用于定义以字节为单位测量的多余突发大小。该属性定义如下：
NAME qpTBExcessBurst SYNTAX Integer VALUE This value must be greater than or equal to qpTBNormalBurst
名称QPTbexessBurst语法整数值此值必须大于或等于qpTBNormalBurst
This class represents an IntServ traffic profile. Values of IntServ traffic profiles are compared against Traffic specification (TSPEC) and QoS Reservation (FLOWSPEC) requests carried in RSVP requests.
此类表示IntServ流量配置文件。将IntServ流量配置文件的值与RSVP请求中承载的流量规范（TSPEC）和QoS保留（FLOWSPEC）请求进行比较。
The class definition is as follows:
类别定义如下：
NAME QoSPolicyIntServTrfcProf DERIVED FROM QoSPolicyTrfcProf (defined in this document) ABSTRACT FALSE PROPERTIES qpISTokenRate, qpISPeakRate, qpISBucketSize, qpISResvRate, qpISResvSlack, qpISMinPolicedUnit, qpISMaxPktSize
名称QoSPolicyIntServTrfcProf源自QospolicyTrfcRof（在本文档中定义）抽象错误属性qpISTokenRate、qpISPeakRate、qpISBucketSize、qpISResvRate、qpISResvSlack、QpisminPoliedUnit、qpISMaxPktSize
This property is a non-negative integer that defines the token rate parameter, measured in kilobits per second. This property is defined as follows:
此属性是定义令牌速率参数的非负整数，以千比特每秒为单位。该属性定义如下：
NAME qpISTokenRate SYNTAX Integer VALUE This value must be greater than or equal to 0
NAME qpISTokenRate语法整数值此值必须大于或等于0
This property is a non-negative integer that defines the peak rate parameter, measured in kilobits per second. This property is defined as follows:
此属性是定义峰值速率参数的非负整数，以千比特每秒为单位。该属性定义如下：
NAME qpISPeakRate SYNTAX Integer VALUE This value must be greater than or equal to 0
NAME qpISPeakRate语法整数值此值必须大于或等于0
This property is a non-negative integer that defines the token bucket size parameter, measured in bytes. This property is defined as follows:
此属性是一个非负整数，定义令牌桶大小参数，以字节为单位。该属性定义如下：
NAME qpISBucketSize SYNTAX Integer VALUE This value must be greater than or equal to 0
NAME qpISBucketSize语法整数值此值必须大于或等于0
This property is a non-negative integer that defines the reservation rate (R-Spec) in the RSVP guaranteed service reservation. It is measured in kilobits per second. This property is defined as follows:
此属性是一个非负整数，用于定义RSVP保证服务保留中的保留率（R-Spec）。它是以千比特每秒为单位测量的。该属性定义如下：
NAME qpISResvRate SYNTAX Integer VALUE This value must be greater than or equal to 0
名称qpISResvRate语法整数值此值必须大于或等于0
This property is a non-negative integer that defines the RSVP slack term in the RSVP guaranteed service reservation. It is measured in microseconds. This property is defined as follows:
此属性是一个非负整数，用于定义RSVP保证服务保留中的RSVP松弛项。它以微秒为单位。该属性定义如下：
NAME qpISResvSlack SYNTAX Integer VALUE This value must be greater than or equal to 0
名称qpISResvSlack语法整数值此值必须大于或等于0
This property is a non-negative integer that defines the minimum RSVP policed unit, measured in bytes. This property is defined as follows:
此属性是一个非负整数，用于定义最小RSVP策略单位（以字节为单位）。该属性定义如下：
NAME qpISMinPolicedUnit SYNTAX Integer VALUE This value must be greater than or equal to 0
名称qpISMinPolicedUnit语法整数值此值必须大于或等于0
This property is a positive integer that defines the maximum allowed packet size for RSVP messages, measured in bytes. This property is defined as follows:
此属性是一个正整数，用于定义RSVP消息允许的最大数据包大小（以字节为单位）。该属性定义如下：
NAME qpISMaxPktSize SYNTAX Integer VALUE This value must be a positive integer, denoting the number of bytes in the largest payload packet of an RSVP signaled flow or class.
NAME qpISMaxPktSize SYNTAX Integer VALUE此值必须为正整数，表示RSVP信号流或类的最大有效负载数据包中的字节数。
This class can be used for representing an indirection in variable
and value references either in a simple condition ("<x> match <y>")
or a simple action ("<x> = <y>"). In both cases, <x> and <y> are
known as the variable and the value of either the condition or
action. The value of the properties qpAttributeName and
qpAttributeValueList are used to substitute <x> and <y> in the
condition or action respectively.
This class can be used for representing an indirection in variable
and value references either in a simple condition ("<x> match <y>")
or a simple action ("<x> = <y>"). In both cases, <x> and <y> are
known as the variable and the value of either the condition or
action. The value of the properties qpAttributeName and
qpAttributeValueList are used to substitute <x> and <y> in the
condition or action respectively.
The substitution is done as follows: The value of the property qpAttributeName is used to substitute <x> and the value of the property qpAttributeValueList is used to substitute <y>.
替换操作如下：属性qpAttributeName的值用于替换<x>，属性qpAttributeValueList的值用于替换<y>。
Once the substitution is done, the condition can be evaluated and the action can be performed.
完成替换后，即可评估条件并执行操作。
For example, suppose we want to define a condition over a user name of the form "user == 'Smith'", using the QoSPolicyRSVPUserVariable class. The user information in the RSVP message provides a DN. The DN points to a user objects holding many attributes. If the relevant attribute is "last name", we would use the QoSPolicyAttributeValue class with qpAttributeName = "Last Name", qpAttributeValueList = {"Smith"}.
例如，假设我们希望使用QoSPolicyRSVPUserVariable类在用户名上定义一个条件，其形式为“user=='Smith'”。RSVP消息中的用户信息提供了一个DN。DN指向包含许多属性的用户对象。如果相关属性是“last name”，我们将使用qpspolicyattributevalue类和qpAttributeName=“last name”，qpAttributeValueList={“Smith”}。
The class definition is as follows:
类别定义如下：
NAME QoSPolicyAttributeValue DERIVED FROM PolicyValue (defined in [PCIMe]) ABSTRACT FALSE PROPERTIES qpAttributeName, qpAttributeValueList
名称QoSPolicyAttributeValue派生自PolicyValue（在[PCIMe]中定义）抽象假属性qpAttributeName、qpAttributeValueList
This property carries the name of the attribute that is to be used to
substitute <x> in a simple condition or simple condition of the forms
"<x> match <y>" or "<x> = <y>" respectively. This property is
defined as follows:
This property carries the name of the attribute that is to be used to
substitute <x> in a simple condition or simple condition of the forms
"<x> match <y>" or "<x> = <y>" respectively. This property is
defined as follows:
NAME qpAttributeName SYNTAX String
名称qpAttributeName语法字符串
This property carries a list of values that is to be used to
substitute <y> in a simple condition or simple action of the forms
"<x> match <y>" or "<x> = <y>" respectively.
This property carries a list of values that is to be used to
substitute <y> in a simple condition or simple action of the forms
"<x> match <y>" or "<x> = <y>" respectively.
This property is defined as follows:
该属性定义如下：
NAME qpAttributeValueList SYNTAX String
名称qpAttributeValueList语法字符串
This is an abstract class that serves as the base class for all implicit variables that have to do with RSVP conditioning. The class definition is as follows:
这是一个抽象类，用作与RSVP条件有关的所有隐式变量的基类。类别定义如下：
NAME QoSPolicyRSVPVariable DESCRIPTION An abstract base class used to build other classes that specify different attributes of an RSVP request DERIVED FROM PolicyImplicitVariable (defined in [PCIMe]) ABSTRACT TRUE PROPERTIES None
名称QoSPolicyRSVPVariable DESCRIPTION用于构建其他类的抽象基类，这些类指定从PolicyImplicitVariable（在[PCIMe]中定义）派生的RSVP请求的不同属性抽象真属性无
This is a concrete class that contains the source IPv4 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的源IPv4地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPSourceIPv4Variable DESCRIPTION The source IPv4 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
名称QOSPOLICYRSVPSOURCEIPV4变量描述RSVP信号流的源IPv4地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIPv4AddrValue
允许的值类型：PolicyIPv4AddrValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the destination IPv4 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的目标IPv4地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPDestinationIPv4Variable DESCRIPTION The destination IPv4 address of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
名称QOSPOLICYRSVDESTIONIPV4变量描述RSVP信号流的目标IPv4地址，如RSVP路径和RESV会话[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIPv4AddrValue
允许的值类型：PolicyIPv4AddrValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the source IPv6 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的源IPv6地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPSourceIPv6Variable DESCRIPTION The source IPv6 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
名称QOSPOLICYRSVPSOURCEIPV6变量描述RSVP信号流的源IPv6地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIPv6AddrValue
允许的值类型：PolicyIPv6AddrValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the destination IPv6 address of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的目标IPv6地址，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPDestinationIPv6Variable DESCRIPTION The destination IPv6 address of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
名称QOSPOLICYRSVPESTIONIPV6变量描述RSVP信号流的目标IPv6地址，如RSVP路径和RESV会话[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIPv6AddrValue
允许的值类型：PolicyIPv6AddrValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This class contains the source port of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
此类包含RSVP信号流的源端口，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPSourcePortVariable DESCRIPTION The source port of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects.
名称QoSPolicyRSVPSourcePortVariable描述RSVP信号流的源端口，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIntegerValue (0..65535)
允许的值类型：PolicyIntegerValue（0..65535）
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the destination port of the RSVP signaled flow, as defined in the RSVP PATH SENDER_TEMPLATE and RSVP RESV FILTER_SPEC [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的目标端口，如RSVP PATH SENDER_模板和RSVP RESV FILTER_SPEC[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPDestinationPortVariable DESCRIPTION The destination port of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
名称QOSPOLICYRSVP PDESTINATIONPortVariable描述RSVP信号流的目标端口，如RSVP路径和RESV会话[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIntegerValue (0..65535)
允许的值类型：PolicyIntegerValue（0..65535）
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the IP Protocol number of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects. The class definition is as follows:
这是一个具体的类，包含RSVP信号流的IP协议号，如RSVP路径和RESV会话[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPIPProtocolVariable DESCRIPTION The IP Protocol number of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
名称QOSPOLICYRSVPIPPROTOCOLVERATION描述RSVP信号流的IP协议号，如RSVP路径和RESV会话[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolicyIntegerValue
允许的值类型：PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the IP Protocol version number of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects. The well-known version numbers are 4 and 6. This variable allows a policy definition of the type:
This is a concrete class that contains the IP Protocol version number of the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects. The well-known version numbers are 4 and 6. This variable allows a policy definition of the type:translate error, please retry
"If IP version = IPv4 then ...".
“如果IP版本=IPv4，则…”。
The class definition is as follows:
类别定义如下：
NAME QoSPolicyRSVPIPVersionVariable DESCRIPTION The IP version number of the IP Addresses carried the RSVP signaled flow, as defined in the RSVP PATH and RESV SESSION [RSVP] objects.
名称QOSPOLICYRSVPVersionVariable描述承载RSVP信号流的IP地址的IP版本号，如RSVP路径和RESV会话[RSVP]对象中定义的。
ALLOWED VALUE TYPES: PolciIntegerValue
允许的值类型：PolciIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the DSCP value as defined in the RSVP DCLASS [DCLASS] object. The class definition is as follows:
这是一个具体的类，包含RSVP DCLASS[DCLASS]对象中定义的DSCP值。类别定义如下：
NAME QoSPolicyRSVPDCLASSVariable DESCRIPTION The DSCP value as defined in the RSVP DCLASS [DCLASS] object.
名称QoSPolicyRSVPDCLASSVariable DESCRIPTION RSVP DCLASS[DCLASS]对象中定义的DSCP值。
ALLOWED VALUE TYPES: PolicyIntegerValue, PolicyBitStringValue
允许的值类型：PolicyIntegerValue、PolicyBitStringValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the reservation style as defined in the RSVP STYLE object in the RESV message [RSVP]. The class definition is as follows:
这是一个具体的类，包含RESV message[RSVP]中RSVP style对象中定义的保留样式。类别定义如下：
NAME QoSPolicyRSVPStyleVariable DESCRIPTION The reservation style as defined in the RSVP STYLE object in the RESV message [RSVP].
名称QOSPOLICYRSVPTYLEVARIABLE描述RESV消息[RSVP]中RSVP样式对象中定义的保留样式。
ALLOWED VALUE TYPES: PolicyBitStringValue, PolicyIntegerValue (Integer has an enumeration of { Fixed-Filter=1, Shared-Explicit=2, Wildcard-Filter=3}
允许的值类型：PolicyBitStringValue，PolicyIntegerValue（Integer的枚举为{Fixed Filter=1，Shared Explicit=2，通配符Filter=3}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the Integrated Service requested in the RSVP Reservation message, as defined in the FLOWSPEC RSVP Object [RSVP]. The class definition is as follows:
这是一个具体的类，包含RSVP保留消息中请求的集成服务，如FLOWSPEC RSVP对象[RSVP]中定义的。类别定义如下：
NAME QoSPolicyRSVPIntServVariable DESCRIPTION The integrated Service requested in the RSVP Reservation message, as defined in the FLOWSPEC RSVP Object [RSVP].
名称QOSPOLICYRSPINTSERVERVARIABLE描述RSVP保留消息中请求的集成服务，如FLOWSPEC RSVP对象[RSVP]中定义的。
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumerated
value of { CL=1 , GS=2, NULL=3}
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumerated
value of { CL=1 , GS=2, NULL=3}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the RSVP message type, as defined in the RSVP message common header [RSVP] object. The class definition is as follows:
这是一个包含RSVP消息类型的具体类，如RSVP消息公共头[RSVP]对象中定义的。类别定义如下：
NAME QoSPolicyRSVPMessageTypeVariable DESCRIPTION The RSVP message type, as defined in the RSVP message common header [RSVP] object.
名称QOSPOLICYRSVPMSessageTypeVariable描述RSVP消息类型，如RSVP消息公共头[RSVP]对象中定义的。
ALLOWED VALUE TYPES: Integer (An enumerated value of
{PATH=1 , PATHTEAR=2, RESV=3,
RESVTEAR=4, RESVERR=5, CONF=6,
PATHERR=7}
ALLOWED VALUE TYPES: Integer (An enumerated value of
{PATH=1 , PATHTEAR=2, RESV=3,
RESVTEAR=4, RESVERR=5, CONF=6,
PATHERR=7}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the RSVP reservation priority, as defined in [RFC3181] object. The class definition is as follows:
这是一个具体的类，包含[RFC3181]对象中定义的RSVP保留优先级。类别定义如下：
NAME QoSPolicyRSVPPreemptionPriorityVariable DESCRIPTION The RSVP reservation priority as defined in [RFC3181].
名称QOSPOLICYRSVPREEMPTIONPRIORITYVARITY描述[RFC3181]中定义的RSVP保留优先级。
ALLOWED VALUE TYPES: PolicyIntegerValue
允许的值类型：PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the RSVP reservation defending priority, as defined in [RFC3181] object. The class definition is as follows:
这是一个包含RSVP保留保护优先级的具体类，如[RFC3181]对象中所定义。类别定义如下：
NAME QoSPolicyRSVPPreemptionDefPriorityVariable DESCRIPTION The RSVP preemption reservation defending priority as defined in [RFC3181].
名称QOSPOLICYRSVPRPREEMPTIONDEFPRIORITYVARITY描述[RFC3181]中定义的RSVP抢占保留保护优先级。
ALLOWED VALUE TYPES: PolicyIntegerValue
允许的值类型：PolicyIntegerValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the ID of the user that initiated the flow as defined in the User Locator string in the Identity Policy Object [RFC3182]. The class definition is as follows:
这是一个具体的类，包含发起流的用户的ID，如标识策略对象[RFC3182]中的用户定位器字符串中所定义。类别定义如下：
NAME QoSPolicyRSVPUserVariable DESCRIPTION The ID of the user that initiated the flow as defined in the User Locator string in the Identity Policy Object [RFC3182].
NAME QoSPolicyRSVPUserVariable DESCRIPTION启动流的用户的ID，如标识策略对象[RFC3182]中的用户定位器字符串中所定义。
ALLOWED VALUE TYPES: QoSPolicyDNValue, PolicyStringValue, QoSPolicyAttributeValue
允许的值类型：QoSPolicyDNValue、PolicyStringValue、QoSPolicyAttributeValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the ID of the application that generated the flow as defined in the application locator string in the Application policy object [RFC2872]. The class definition is as follows:
这是一个具体的类，包含生成流的应用程序的ID，该流在应用程序策略对象[RFC2872]的应用程序定位器字符串中定义。类别定义如下：
NAME QoSPolicyRSVPApplicationVariable DESCRIPTION The ID of the application that generated the flow as defined in the application locator string in the Application policy object [RFC2872].
名称QOSPOLICYRSVPAPPLICATION变量描述生成流的应用程序的ID，如应用程序策略对象[RFC2872]中的应用程序定位器字符串中定义的。
ALLOWED VALUE TYPES: QoSPolicyDNValue, PolicyStringValue, QoSPolicyAttributeValue
允许的值类型：QoSPolicyDNValue、PolicyStringValue、QoSPolicyAttributeValue
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This is a concrete class that contains the type of authentication used in the Identity Policy Object [RFC3182]. The class definition is as follows:
这是一个具体的类，包含身份策略对象[RFC3182]中使用的身份验证类型。类别定义如下：
NAME QoSPolicyRSVPAuthMethodVariable DESCRIPTION The RSVP Authentication type used in the Identity Policy Object [RFC3182].
名称QoSPolicyRSVPAuthMethodVariable DESCRIPTION标识策略对象[RFC3182]中使用的RSVP身份验证类型。
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumeration
of { NONE=0, PLAIN-TEXT=1,
DIGITAL-SIG = 2, KERBEROS_TKT=3,
X509_V3_CERT=4, PGP_CERT=5}
ALLOWED VALUE TYPES: PolicyIntegerValue (An enumeration
of { NONE=0, PLAIN-TEXT=1,
DIGITAL-SIG = 2, KERBEROS_TKT=3,
X509_V3_CERT=4, PGP_CERT=5}
DERIVED FROM QoSPolicyRSVPVariable (defined in this document) ABSTRACT FALSE PROPERTIES None
源自QospolicyrsvpvVariable（在本文档中定义）抽象假属性无
This class is used to represent a single or set of Distinguished Name [DNDEF] values, including wildcards. A Distinguished Name is a name that can be used as a key to retrieve an object from a directory service. This value can be used in comparison to reference values carried in RSVP policy objects, as specified in [RFC3182]. The class definition is as follows:
此类用于表示单个或一组可分辨名称[DNDEF]值，包括通配符。可分辨名称是可以用作键的名称，用于从目录服务检索对象。此值可用于与[RFC3182]中指定的RSVP策略对象中携带的参考值进行比较。类别定义如下：
NAME QoSPolicyDNValue DERIVED FROM PolicyValue ABSTRACT FALSE PROPERTIES qpDNList
从PolicyValue抽象属性qpDNList派生的名称QoSPolicyDNValue
This attribute provides an unordered list of strings, each representing a Distinguished Name (DN) with wildcards. The format of a DN is defined in [DNDEF]. The asterisk character ("*") is used as wildcard for either a single attribute value or a wildcard for an RDN. The order of RDNs is significant. For example: A qpDNList attribute carrying the following value:
此属性提供一个无序的字符串列表，每个字符串用通配符表示一个可分辨名称（DN）。DN的格式在[DNDEF]中定义。星号字符（“*”）用作单个属性值的通配符或RDN的通配符。RDNs的顺序是显著的。例如：带有以下值的qpDNList属性：
"CN=*, OU=Sales, O=Widget Inc., *, C=US" matches:
“CN=*，OU=Sales，O=Widget Inc.，*，C=US”匹配：
"CN=J. Smith, OU=Sales, O=Widget Inc, C=US"
"CN=J. Smith, OU=Sales, O=Widget Inc, C=US"
and also matches:
并且还匹配：
"CN=J. Smith, OU=Sales, O=Widget Inc, L=CA, C=US".
“CN=J.Smith，OU=Sales，O=Widget Inc，L=CA，C=US”。
The attribute is defined as follows:
该属性定义如下：
NAME qpDNList SYNTAX List of Distinguished Names implemented as strings, each of which serves as a reference to another object.
名称qpDNList语法以字符串形式实现的可分辨名称列表，每个字符串用作对另一个对象的引用。
This action controls the content of RSVP messages and the way RSVP requests are admitted. Depending on the value of its qpRSVPActionType property, this action directly translates into either a COPS Replace Decision or a COPS Stateless Decision, or both as defined in COPS for RSVP. Only variables that are subclasses of the QoSPolicyRSVPVariable are allowed to be associated with this action. The property definition is as follows:
此操作控制RSVP消息的内容以及允许RSVP请求的方式。根据其qpRSVPActionType属性的值，此操作直接转换为COPS替换决策或COPS无状态决策，或如COPS for RSVP中所定义的两者。只有属于QoSPolicyRSVPVariable的子类的变量才允许与此操作关联。物业定义如下：
NAME QoSPolicyRSVPSimpleAction DESCRIPTION This action controls the content of RSVP messages and the way RSVP requests are admitted. DERIVED FROM SimplePolicyAction (defined in [PCIMe]) ABSTRACT FALSE PROPERTIES qpRSVPActionType
名称QoSPolicyRSVPSimpleAction描述此操作控制RSVP消息的内容和RSVP请求的接收方式。派生自SimplePolicyAction（在[PCIMe]中定义）抽象假属性qpRSVPActionType
This property is an enumerated integer denoting the type(s) of RSVP action. The value 'REPLACE' denotes a COPS Replace Decision action. The value 'STATELESS' denotes a COPS Stateless Decision action. The value REPLACEANDSTATELESS denotes both decision actions. Refer to [RFC2749] for details.
此属性是一个枚举整数，表示RSVP操作的类型。值“REPLACE”表示COPS替换决策操作。值“无状态”表示COPS无状态决策操作。值REPLACEANDSTATELESS表示这两个决策操作。有关详细信息，请参阅[RFC2749]。
NAME qpRSVPActionType DESCRIPTION This property specifies whether the action type is for COPS Replace, Stateless, or both types of decisions. SYNTAX Integer VALUE This is an enumerated integer. A value of 0 specifies a COPS Replace decision. A value of 1 specifies a COPS Stateless Decision. A value of 2 specifies both COPS Replace and COPS Stateless decisions.
名称QPSVPActionType描述此属性指定操作类型是用于COPS替换、无状态还是同时用于这两种类型的决策。语法整数值这是一个枚举整数。值0指定COPS替换决策。值为1指定COPS无状态决策。值2指定COPS替换和COPS无状态决策。
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。
Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat.
可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
The authors wish to thank the input of the participants of the Policy Framework working group, and especially the combined group of the PCIMe coauthors, Lee Rafalow, Andrea Westerinen, Ritu Chadha and Marcus Brunner. In addition, we'd like to acknowledge the valuable contribution from Ed Ellesson, Joel Halpern and Mircea Pana. Thank you all for your comments, critique, ideas and general contribution.
作者希望感谢政策框架工作组参与者的投入，特别是PCIMe合著者Lee Rafalow、Andrea Westerinen、Ritu Chadha和Marcus Brunner的联合小组。此外，我们还要感谢Ed Ellsson、Joel Halpern和Mircea Pana的宝贵贡献。感谢大家的评论、批评、想法和总体贡献。
The Policy Core Information Model [PCIM] describes the general security considerations related to the general core policy model. The extensions defined in this document do not introduce any additional considerations related to security.
策略核心信息模型[PCIM]描述了与通用核心策略模型相关的一般安全注意事项。本文档中定义的扩展没有引入任何与安全性相关的附加注意事项。
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[关键词]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[PCIM] Moore, B., Ellesson, E., Strassner, J. and A. Westerinen, "Policy Core Information Model -- Version 1 Specification", RFC 3060, February 2001.
[PCIM]Moore，B.，Ellesson，E.，Strassner，J.和A.Westerinen，“政策核心信息模型——版本1规范”，RFC 3060，2001年2月。
[PCIMe] Moore, B., Ed., "Policy Core Information Model Extensions", RFC 3460, January 2003.
[PCIMe]Moore，B.，Ed.，“政策核心信息模型扩展”，RFC 3460，2003年1月。
[TERMS] Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M., Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J. and M. Waldbusser, "Terminology for Policy-based Management", RFC 3198, November 2001.
[术语]韦斯特林，A.，施尼兹林，J.，斯特拉斯纳，J.，舍林，M.，奎因，B.，赫尔佐格，S.，休恩，A.，卡尔森，M.，佩里，J.和M.瓦尔德布瑟，“基于政策的管理术语”，RFC 3198，2001年11月。
[DIFFSERV] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z. and W. Weiss, "An Architecture for Differentiated Services", RFC 2475, December 1998.
[DIFFSERV]Blake，S.，Black，D.，Carlson，M.，Davies，E.，Wang，Z.和W.Weiss，“区分服务的架构”，RFC 24751998年12月。
[INTSERV] Braden, R., Clark, D. and S. Shenker, "Integrated Services in the Internet Architecture: an Overview", RFC 1633, June 1994.
[INTSERV]Braden，R.，Clark，D.和S.Shenker，“互联网体系结构中的综合服务：概述”，RFC 16331994年6月。
[RSVP] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S. and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997.
[RSVP]Braden，R.，Ed.，Zhang，L.，Berson，S.，Herzog，S.和S.Jamin，“资源预留协议（RSVP）——第1版功能规范”，RFC 22052997年9月。
[RFC2749] Herzog, S., Ed., Boyle, J., Cohen, R., Durham, D., Rajan, R. and A. Sastry, "COPS usage for RSVP", RFC 2749, January 2000.
[RFC2749]Herzog，S.，Ed.，Boyle，J.，Cohen，R.，Durham，D.，Rajan，R.和A.Sastry，“警察对RSVP的使用”，RFC 2749，2000年1月。
[RFC3181] Herzog, S., "Signaled Preemption Priority Policy Element", RFC 3181, October 2001.
[RFC3181]Herzog，S.，“信号抢占优先权政策要素”，RFC 31812001年10月。
[DIFF-MIB] Baker, F., Chan, K. and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002.
[DIFF-MIB]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月。
[AF] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski, "Assured Forwarding PHB Group", RFC 2597, June 1999.
[AF]Heinanen，J.，Baker，F.，Weiss，W.和J.Wroclawski，“保证货运PHB集团”，RFC 25971999年6月。
[CL] Wroclawski, J., "Specification of the Controlled-Load Network Element Service", RFC 2211, September 1997.
[CL]Wroclawski，J.“受控负荷网元服务规范”，RFC 2211，1997年9月。
[RSVP-IS] Wroclawski, J., "The Use of RSVP with IETF Integrated Services", RFC 2210, September 1997.
[RSVP-IS]Wroclawski，J.，“RSVP与IETF集成服务的使用”，RFC 2210，1997年9月。
[GS] Shenker, S., Partridge, C. and R. Guerin, "Specification of the Guaranteed Quality of Service", RFC 2212, September 1997.
[GS]Shenker，S.，Partridge，C.和R.Guerin，“保证服务质量规范”，RFC 2212，1997年9月。
[DCLASS] Bernet, Y., "Format of the RSVP DCLASS Object", RFC 2996, November 2000.
[DCLASS]Bernet，Y.，“RSVP DCLASS对象的格式”，RFC 2996，2000年11月。
[RFC3182] Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T., Herzog, S. and R. Hess, "Identity Representation for RSVP", RFC 3182, October 2001.
[RFC3182]Yadav，S.，Yavatkar，R.，Pabbati，R.，Ford，P.，Moore，T.，Herzog，S.和R.Hess，“RSVP的身份表示”，RFC 31822001年10月。
[RFC2872] Bernet, Y. and R. Pabbati, "Application and Sub Application Identity Policy Element for Use with RSVP", RFC 2872, June 2000.
[RFC2872]Bernet，Y.和R.Pabbati，“与RSVP一起使用的应用程序和子应用程序标识策略元素”，RFC 2872，2000年6月。
[DNDEF] Wahl, M., Kille, S. and T. Howes, "Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names", RFC 2253, December 1997.
[DNDEF]Wahl，M.，Kille，S.和T.Howes，“轻量级目录访问协议（v3）：可分辨名称的UTF-8字符串表示”，RFC 2253，1997年12月。
Yoram Ramberg Cisco Systems 4 Maskit Street Herzliya Pituach, Israel 46766
约拉姆·兰伯格思科系统公司以色列赫兹利亚皮图奇马斯基街4号46766
Phone: +972-9-970-0081
Fax: +972-9-970-0219
EMail: yramberg@cisco.com
Phone: +972-9-970-0081
Fax: +972-9-970-0219
EMail: yramberg@cisco.com
Yoram Snir Cisco Systems 300 East Tasman Drive San Jose, CA 95134
加利福尼亚州圣何塞市东塔斯曼大道300号Yoram Snir Cisco Systems，邮编95134
Phone: +1 408-853-4053
Fax: +1 408 526-7864
EMail: ysnir@cisco.com
Phone: +1 408-853-4053
Fax: +1 408 526-7864
EMail: ysnir@cisco.com
John Strassner Intelliden Corporation 90 South Cascade Avenue Colorado Springs, Colorado 80903
约翰·斯特拉斯纳·Intelliden公司，科罗拉多州斯普林斯市南喀斯喀特大道90号，科罗拉多州80903
Phone: +1-719-785-0648
Fax: +1-719-785-0644
EMail: john.strassner@intelliden.com
Phone: +1-719-785-0648
Fax: +1-719-785-0644
EMail: john.strassner@intelliden.com
Ron Cohen Ntear LLC
罗恩科恩泰尔有限责任公司
Phone: +972-8-9402586
Fax: +972-9-9717798
EMail: ronc@lyciumnetworks.com
Phone: +972-8-9402586
Fax: +972-9-9717798
EMail: ronc@lyciumnetworks.com
Bob Moore IBM Corporation P. O. Box 12195, BRQA/501/G206 3039 Cornwallis Rd. Research Triangle Park, NC 27709-2195
Bob Moore IBM Corporation地址：北卡罗来纳州三角研究公园康沃利斯路3039号BRQA/501/G206 12195信箱，邮编：27709-2195
Phone: +1 919-254-4436
Fax: +1 919-254-6243
EMail: remoore@us.ibm.com
Phone: +1 919-254-4436
Fax: +1 919-254-6243
EMail: remoore@us.ibm.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 assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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编辑功能的资金目前由互联网协会提供。