Network Working Group K. McCloghrie
Request for Comments: 3159 M. Fine
Category: Standards Track Cisco Systems
J. Seligson
K. Chan
Nortel Networks
S. Hahn
R. Sahita
Intel
A. Smith
Allegro Networks
F. Reichmeyer
PFN
August 2001
Network Working Group K. McCloghrie
Request for Comments: 3159 M. Fine
Category: Standards Track Cisco Systems
J. Seligson
K. Chan
Nortel Networks
S. Hahn
R. Sahita
Intel
A. Smith
Allegro Networks
F. Reichmeyer
PFN
August 2001
Structure of Policy Provisioning Information (SPPI)
策略设置信息（SPPI）的结构
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 (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document, the Structure of Policy Provisioning Information (SPPI), defines the adapted subset of SNMP's Structure of Management Information (SMI) used to write Policy Information Base (PIB) modules.
本文档称为策略配置信息结构（SPPI），定义了用于编写策略信息库（PIB）模块的SNMP管理信息结构（SMI）的自适应子集。
RFC 2748 defines the COPS protocol, and RFC 2749 describes how the COPS protocol is used to provide for the outsourcing of policy decisions for RSVP. Another usage of the COPS protocol, for the provisioning of policy, is introduced in RFC 3084. In this provisioning model, the policy information is viewed as a collection of Provisioning Classes (PRCs) and Provisioning Instances (PRIs) residing in a virtual information store, termed the Policy Information Base (PIB). Collections of related Provisioning Classes are defined in a PIB module.
RFC 2748定义了COPS协议，RFC 2749描述了如何使用COPS协议为RSVP提供外包决策。RFC3084中介绍了COPS协议的另一种用法，用于提供策略。在此配置模型中，策略信息被视为驻留在虚拟信息存储中的配置类（PRC）和配置实例（PRI）的集合，称为策略信息库（PIB）。相关资源调配类的集合在PIB模块中定义。
Conventions used in this document
本文件中使用的公约
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Table of Contents
目录
1 Use of the SMI ................................................. 3
1.1 Terminology Translation ...................................... 3
1.2 Overview ..................................................... 3
2 Structure of this Specification ................................ 4
3 Definitions .................................................... 5
4 PIB Modules .................................................... 17
4.1 Importing Definitions ........................................ 17
4.2 Reserved Keywords ............................................ 18
5 Naming Hierarchy ............................................... 18
6 Mapping of the MODULE-IDENTITY macro ........................... 18
6.1 Mapping of the SUBJECT-CATEGORIES clause ..................... 18
7 Mapping of the OBJECT-TYPE macro ............................... 19
7.1 Mapping of the SYNTAX clause ................................. 19
7.1.1 Counter32 .................................................. 19
7.1.2 Gauge32 .................................................... 20
7.1.3 Opaque ..................................................... 20
7.1.4 IpAddress .................................................. 20
7.1.5 Counter64 .................................................. 20
7.1.6 Integer64 .................................................. 20
7.1.7 Unsigned64 ................................................. 20
7.1.8 Provisioning Classes ....................................... 21
7.2 Mapping of the MAX-ACCESS clause ............................. 21
7.3 Mapping of the PIB-ACCESS clause ............................. 22
7.4 Mapping of the INSTALL-ERRORS clause ......................... 22
7.5 Mapping of the PIB-INDEX clause .............................. 22
7.6 Mapping of the INDEX clause .................................. 23
7.7 Mapping of the AUGMENTS clause ............................... 23
7.8 Mapping of the EXTENDS clause ................................ 24
7.8.1 Relation between PIB-INDEX, AUGMENTS and EXTENDS clauses .. 24
7.9 Mapping of the UNIQUENESS clause ............................. 25
7.10 Mapping of the PIB-REFERENCES clause ........................ 25
7.11 Mapping of the PIB-TAG clause ............................... 25
8 Mapping of the OBJECT-IDENTITY macro ........................... 26
9 Mapping of the OBJECT-GROUP macro .............................. 26
9.1 Mapping of the OBJECTS clause ................................ 26
10 Mapping of the MODULE-COMPLIANCE macro ........................ 26
10.1 Mapping of the MODULE clause ................................ 26
10.1.1 Mapping of the MANDATORY-GROUPS clause .................... 27
10.1.2 Mapping of the GROUP clause ............................... 27
10.1.3 Mapping of the OBJECT clause .............................. 27
1 Use of the SMI ................................................. 3
1.1 Terminology Translation ...................................... 3
1.2 Overview ..................................................... 3
2 Structure of this Specification ................................ 4
3 Definitions .................................................... 5
4 PIB Modules .................................................... 17
4.1 Importing Definitions ........................................ 17
4.2 Reserved Keywords ............................................ 18
5 Naming Hierarchy ............................................... 18
6 Mapping of the MODULE-IDENTITY macro ........................... 18
6.1 Mapping of the SUBJECT-CATEGORIES clause ..................... 18
7 Mapping of the OBJECT-TYPE macro ............................... 19
7.1 Mapping of the SYNTAX clause ................................. 19
7.1.1 Counter32 .................................................. 19
7.1.2 Gauge32 .................................................... 20
7.1.3 Opaque ..................................................... 20
7.1.4 IpAddress .................................................. 20
7.1.5 Counter64 .................................................. 20
7.1.6 Integer64 .................................................. 20
7.1.7 Unsigned64 ................................................. 20
7.1.8 Provisioning Classes ....................................... 21
7.2 Mapping of the MAX-ACCESS clause ............................. 21
7.3 Mapping of the PIB-ACCESS clause ............................. 22
7.4 Mapping of the INSTALL-ERRORS clause ......................... 22
7.5 Mapping of the PIB-INDEX clause .............................. 22
7.6 Mapping of the INDEX clause .................................. 23
7.7 Mapping of the AUGMENTS clause ............................... 23
7.8 Mapping of the EXTENDS clause ................................ 24
7.8.1 Relation between PIB-INDEX, AUGMENTS and EXTENDS clauses .. 24
7.9 Mapping of the UNIQUENESS clause ............................. 25
7.10 Mapping of the PIB-REFERENCES clause ........................ 25
7.11 Mapping of the PIB-TAG clause ............................... 25
8 Mapping of the OBJECT-IDENTITY macro ........................... 26
9 Mapping of the OBJECT-GROUP macro .............................. 26
9.1 Mapping of the OBJECTS clause ................................ 26
10 Mapping of the MODULE-COMPLIANCE macro ........................ 26
10.1 Mapping of the MODULE clause ................................ 26
10.1.1 Mapping of the MANDATORY-GROUPS clause .................... 27
10.1.2 Mapping of the GROUP clause ............................... 27
10.1.3 Mapping of the OBJECT clause .............................. 27
10.1.3.1 Mapping of the SYNTAX clause ............................ 27
10.1.3.2 Mapping of the WRITE-SYNTAX clause ...................... 28
10.1.3.3 Mapping of the PIB-MIN-ACCESS clause .................... 28
11 Textual Conventions ........................................... 28
11.1 Mapping of the TEXTUAL-CONVENTION macro ..................... 28
11.1.1 Mapping of the DISPLAY-HINT clause ........................ 29
11.1.2 Mapping of the SYNTAX clause .............................. 29
11.1.2.1 Sub-typing of Textual Conventions ....................... 29
12 Extending a PIB Module ........................................ 29
12.1 PIB Modules ................................................. 29
12.2 Object Assignments .......................................... 30
12.3 Object Definitions .......................................... 30
Appendix A: Mapping a PIB to a MIB ............................... 32
Appendix B: Example usage of PIB-REFERENCES and PIB-TAG clauses .. 33
Security Considerations .......................................... 35
IANA Considerations .............................................. 35
Authors' Addresses ............................................... 37
References ....................................................... 38
Full Copyright Statement ......................................... 40
10.1.3.1 Mapping of the SYNTAX clause ............................ 27
10.1.3.2 Mapping of the WRITE-SYNTAX clause ...................... 28
10.1.3.3 Mapping of the PIB-MIN-ACCESS clause .................... 28
11 Textual Conventions ........................................... 28
11.1 Mapping of the TEXTUAL-CONVENTION macro ..................... 28
11.1.1 Mapping of the DISPLAY-HINT clause ........................ 29
11.1.2 Mapping of the SYNTAX clause .............................. 29
11.1.2.1 Sub-typing of Textual Conventions ....................... 29
12 Extending a PIB Module ........................................ 29
12.1 PIB Modules ................................................. 29
12.2 Object Assignments .......................................... 30
12.3 Object Definitions .......................................... 30
Appendix A: Mapping a PIB to a MIB ............................... 32
Appendix B: Example usage of PIB-REFERENCES and PIB-TAG clauses .. 33
Security Considerations .......................................... 35
IANA Considerations .............................................. 35
Authors' Addresses ............................................... 37
References ....................................................... 38
Full Copyright Statement ......................................... 40
The SPPI and PIB modules are based on SNMP's SMI and MIB modules, which use an adapted subset of the ASN.1 data definition language [ASN1]. The decision to base the definition of PIB modules on this format allows for the leveraging of the community's knowledge, experience and tools of the SMI and MIB modules.
SPPI和PIB模块基于SNMP的SMI和MIB模块，它们使用ASN.1数据定义语言[ASN1]的一个子集。基于此格式定义PIB模块的决定允许利用社区对SMI和MIB模块的知识、经验和工具。
The SMI uses the term "managed objects" to refer to object types, both tabular types with descriptors such as xxxTable and xxxEntry, as well as scalar and columnar object types. The SPPI does not use the term "object" so as to avoid confusion with COPS protocol objects. Instead, the SPPI uses the term Provisioning Class (PRC) for the table and row definitions (the xxxTable and xxxEntry objects, respectively), and Provisioning Instance (PRI) for an instantiation of a row definition. For a columnar object of a table definition, the SPPI uses the term "attribute" of a Provisioning Class. (The SPPI does not support the equivalent of the SMI's scalar objects.)
SMI使用术语“托管对象”来指代对象类型，包括带有诸如xxxTable和xxxEntry等描述符的表格类型，以及标量和柱状对象类型。SPPI不使用术语“对象”，以避免与COPS协议对象混淆。相反，SPPI使用术语Provisioning Class（PRC）表示表和行定义（分别是xxxTable和xxxEntry对象），使用术语Provisioning Instance（PRI）表示行定义的实例化。对于表定义的列对象，SPPI使用配置类的术语“属性”。（SPPI不支持SMI的标量对象的等效项。）
SNMP's SMI is divided into five parts: module definitions, object definitions, notification definitions [SMI], textual convention definitions [TC] and conformance definitions [CONF].
SNMP的SMI分为五个部分：模块定义、对象定义、通知定义[SMI]、文本约定定义[TC]和一致性定义[CONF]。
- The SMI's MODULE-IDENTITY macro is used to convey the semantics of a MIB module. The SPPI uses this macro to convey the semantics of a PIB module.
- SMI的MODULE-IDENTITY宏用于传递MIB模块的语义。SPPI使用此宏来传达PIB模块的语义。
- The SMI's OBJECT-TYPE macro is used to convey the syntax and semantics of managed objects. The SPPI uses this macro to convey the syntax and semantics of PRCs and their attributes.
- SMI的对象类型宏用于传递托管对象的语法和语义。SPPI使用此宏来传达PRC及其属性的语法和语义。
- The SMI's notification definitions are not used (at this time) by the SPPI. (Note that the use of the keyword 'notify' in the SPPI is not related to the SMI's notifications).
- SPPI（目前）未使用SMI的通知定义。（请注意，在SPPI中使用关键字“notify”与SMI的通知无关）。
- The SMI's TEXTUAL CONVENTION macro allows new data types to be defined. The SPPI uses this macro to define new data types having particular syntax and semantics which is common to several attributes of one of more PRCs.
- SMI的文本约定宏允许定义新的数据类型。SPPI使用此宏定义具有特定语法和语义的新数据类型，这些语法和语义对于一个或多个PRC的多个属性是通用的。
- The SMI's conformance definitions define several macros: the OBJECT-GROUP macro, the NOTIFICATION-GROUP macro, the MODULE-COMPLIANCE macro and the AGENT-CAPABILITIES macro. The SPPI uses the OBJECT-GROUP and MODULE-COMPLIANCE macros to specify acceptable lower-bounds of implementation of the attributes of PRCs, and thereby indirectly, acceptable lower-bounds of implementation of the PRCs themselves. The NOTIFICATION-GROUP macro is not used (at this time) by the SPPI. Potential usage by the SPPI of the AGENT- CAPABILITIES macro is for further study.
- SMI的一致性定义定义了几个宏：OBJECT-GROUP宏、NOTIFICATION-GROUP宏、MODULE-COMPLIANCE宏和AGENT-CAPABILITIES宏。SPPI使用对象组和模块符合性宏来指定PRC属性实现的可接受下限，从而间接指定PRC自身实现的可接受下限。SPPI（此时）未使用NOTIFICATION-GROUP宏。SPPI对AGENT-CAPABILITIES宏的潜在使用有待进一步研究。
The SMI is specified in terms of an ASN.1 definition together with descriptive text for each element introduced in that ASN.1 definition. This document specifies the SPPI also via a ASN.1 definition, which is a modified version of the SMI's definition, together with descriptive text for only those elements in the SPPI's ASN.1 definition which have differences from the SMI's. For elements in the ASN.1 definition which have no descriptive text in this specification, the reader is referred to the SMI's descriptive text for that element.
SMI是根据ASN.1定义以及该ASN.1定义中引入的每个元素的描述性文本来指定的。本文件还通过ASN.1定义指定了SPPI，该定义是SMI定义的修改版本，以及仅针对SPPI ASN.1定义中与SMI不同的元素的描述性文本。对于ASN.1定义中本规范中没有描述性文本的元素，读者可参考SMI对该元素的描述性文本。
COPS-PR-SPPI DEFINITIONS ::= BEGIN
COPS-PR-SPPI DEFINITIONS ::= BEGIN
IMPORTS ObjectName, SimpleSyntax, ExtUTCTime, mgmt FROM SNMPv2-SMI;
从SNMPv2 SMI导入ObjectName、SimpleSyntax、ExtUTCTime、mgmt；
-- the root for PIB definitions
--PIB定义的根
pib OBJECT IDENTIFIER ::= { mgmt 2 }
pib OBJECT IDENTIFIER ::= { mgmt 2 }
-- definitions for PIB modules
--PIB模块的定义
MODULE-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
SubjectPart -- new
"LAST-UPDATED" value(Update ExtUTCTime)
"ORGANIZATION" Text
"CONTACT-INFO" Text
"DESCRIPTION" Text
RevisionPart
MODULE-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
SubjectPart -- new
"LAST-UPDATED" value(Update ExtUTCTime)
"ORGANIZATION" Text
"CONTACT-INFO" Text
"DESCRIPTION" Text
RevisionPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
SubjectPart ::= -- new
"SUBJECT-CATEGORIES" "{" Categories "}"
-- see IANA Considerations section
Categories ::= -- new
CategoryIDs
| "all"
CategoryIDs ::= -- new
CategoryID
| CategoryIDs "," CategoryID
CategoryID ::= -- new
identifier "(" number ")" -- number is positive
SubjectPart ::= -- new
"SUBJECT-CATEGORIES" "{" Categories "}"
-- see IANA Considerations section
Categories ::= -- new
CategoryIDs
| "all"
CategoryIDs ::= -- new
CategoryID
| CategoryIDs "," CategoryID
CategoryID ::= -- new
identifier "(" number ")" -- number is positive
RevisionPart ::=
Revisions
| empty
Revisions ::=
Revision
| Revisions Revision
Revision ::=
"REVISION" value(Update ExtUTCTime)
"DESCRIPTION" Text
RevisionPart ::=
Revisions
| empty
Revisions ::=
Revision
| Revisions Revision
Revision ::=
"REVISION" value(Update ExtUTCTime)
"DESCRIPTION" Text
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
--
--
OBJECT-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
OBJECT-IDENTITY MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
Status ::=
"current"
| "deprecated"
| "obsolete"
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- syntax of attributes
--属性语法
-- the "base types" defined here are:
-- 3 built-in ASN.1 types: INTEGER, OCTET STRING, OBJECT IDENTIFIER
-- 7 application-defined types: Integer32, IpAddress, Unsigned32,
-- TimeTicks, Opaque, Integer64 and Unsigned64
-- the "base types" defined here are:
-- 3 built-in ASN.1 types: INTEGER, OCTET STRING, OBJECT IDENTIFIER
-- 7 application-defined types: Integer32, IpAddress, Unsigned32,
-- TimeTicks, Opaque, Integer64 and Unsigned64
ObjectSyntax ::=
CHOICE {
simple
SimpleSyntax,
ObjectSyntax ::=
CHOICE {
simple
SimpleSyntax,
-- note that SEQUENCEs for table and row definitions
-- are not mentioned here...
-- note that SEQUENCEs for table and row definitions
-- are not mentioned here...
application-wide ApplicationSyntax }
应用程序范围的ApplicationSyntax}
-- application-wide types
--应用程序范围的类型
ApplicationSyntax ::=
CHOICE {
ipAddress-value
IpAddress,
ApplicationSyntax ::=
CHOICE {
ipAddress-value
IpAddress,
timeticks-value TimeTicks,
timeticks值timeticks，
arbitrary-value Opaque,
任意值不透明，
unsigned-integer-value Unsigned32,
无符号整数值Unsigned32，
large-integer-value -- new Integer64,
大整数值--新整数64，
large-unsigned-integer-value -- new Unsigned64 }
大的无符号整数值--新的无符号64}
-- the following 5 types are copied from the SMI
--以下5种类型是从SMI复制的
-- indistinguishable from INTEGER, but never needs more than
-- 32-bits for a two's complement representation
Integer32 ::=
INTEGER (-2147483648..2147483647)
-- indistinguishable from INTEGER, but never needs more than
-- 32-bits for a two's complement representation
Integer32 ::=
INTEGER (-2147483648..2147483647)
-- (this is a tagged type for historical reasons)
IpAddress ::=
[APPLICATION 0]
IMPLICIT OCTET STRING (SIZE (4))
-- ******* THIS TYPE DEFINITION IS DEPRECATED *******
-- The IpAddress type represents a 32-bit internet
-- IPv4 address. It is represented as an OctetString
-- of length 4, in network byte-order.
-- Note that the IpAddress type is present for
-- historical reasons. IPv4 and IPv6 addresses should
-- be represented using the INET-ADDRESS-MIB
-- defined in [INETADDR].
-- (this is a tagged type for historical reasons)
IpAddress ::=
[APPLICATION 0]
IMPLICIT OCTET STRING (SIZE (4))
-- ******* THIS TYPE DEFINITION IS DEPRECATED *******
-- The IpAddress type represents a 32-bit internet
-- IPv4 address. It is represented as an OctetString
-- of length 4, in network byte-order.
-- Note that the IpAddress type is present for
-- historical reasons. IPv4 and IPv6 addresses should
-- be represented using the INET-ADDRESS-MIB
-- defined in [INETADDR].
-- an unsigned 32-bit quantity
Unsigned32 ::=
[APPLICATION 2]
IMPLICIT INTEGER (0..4294967295)
-- an unsigned 32-bit quantity
Unsigned32 ::=
[APPLICATION 2]
IMPLICIT INTEGER (0..4294967295)
-- hundredths of seconds since an epoch
TimeTicks ::=
[APPLICATION 3]
IMPLICIT INTEGER (0..4294967295)
-- hundredths of seconds since an epoch
TimeTicks ::=
[APPLICATION 3]
IMPLICIT INTEGER (0..4294967295)
--for backward compatibility only
Opaque ::=
[APPLICATION 4]
IMPLICIT OCTET STRING
--for backward compatibility only
Opaque ::=
[APPLICATION 4]
IMPLICIT OCTET STRING
-- the following 2 types are not present in the SMI
--以下两种类型在SMI中不存在
Integer64 ::=
[APPLICATION 10]
IMPLICIT INTEGER (-9223372036854775808..9223372036854775807)
Integer64 ::=
[APPLICATION 10]
IMPLICIT INTEGER (-9223372036854775808..9223372036854775807)
Unsigned64 ::=
[APPLICATION 11]
IMPLICIT INTEGER (0..18446744073709551615)
Unsigned64 ::=
[APPLICATION 11]
IMPLICIT INTEGER (0..18446744073709551615)
-- definition for Provisioning Classes and their attributes
-- (differences from the SMI are noted in the ASN.1 comments)
-- definition for Provisioning Classes and their attributes
-- (differences from the SMI are noted in the ASN.1 comments)
OBJECT-TYPE MACRO ::=
BEGIN
TYPE NOTATION ::=
"SYNTAX" Syntax
UnitsPart
"PIB-ACCESS" Access -- modified
PibReferencesPart -- new
PibTagPart -- new
"STATUS" Status
"DESCRIPTION" Text
ErrorsPart -- new
ReferPart
IndexPart -- modified
MibIndexPart -- modified
UniquePart -- new
DefValPart
OBJECT-TYPE MACRO ::=
BEGIN
TYPE NOTATION ::=
"SYNTAX" Syntax
UnitsPart
"PIB-ACCESS" Access -- modified
PibReferencesPart -- new
PibTagPart -- new
"STATUS" Status
"DESCRIPTION" Text
ErrorsPart -- new
ReferPart
IndexPart -- modified
MibIndexPart -- modified
UniquePart -- new
DefValPart
VALUE NOTATION ::=
value(VALUE ObjectName)
VALUE NOTATION ::=
value(VALUE ObjectName)
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type | "BITS" "{" NamedBits "}"
键入|“BITS”“{”NamedBits“}”
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
NamedBit ::= identifier "(" number ")" -- number is nonnegative
UnitsPart ::=
"UNITS" Text
| empty
UnitsPart ::=
"UNITS" Text
| empty
Access ::= -- modified
"install"
| "notify"
| "install-notify"
| "report-only"
Access ::= -- modified
"install"
| "notify"
| "install-notify"
| "report-only"
Status ::=
"current"
| "deprecated"
| "obsolete"
Status ::=
"current"
| "deprecated"
| "obsolete"
ErrorsPart ::= -- new
"INSTALL-ERRORS" "{" Errors "}"
| empty
ErrorsPart ::= -- new
"INSTALL-ERRORS" "{" Errors "}"
| empty
Errors ::= -- new
Error
| Errors "," Error
Error ::= -- new
identifier "(" number ")" -- number is positive
Errors ::= -- new
Error
| Errors "," Error
Error ::= -- new
identifier "(" number ")" -- number is positive
ReferPart ::=
"REFERENCE" Text
| empty
ReferPart ::=
"REFERENCE" Text
| empty
IndexPart ::=
"PIB-INDEX" "{" Index "}" -- new
| "AUGMENTS" "{" Entry "}"
| "EXTENDS" "{" Entry "}" -- new
| empty
Index ::=
-- the correspondent OBJECT-TYPE invocation
value(ObjectName)
Entry ::=
-- use the INDEX value of the
-- correspondent OBJECT-TYPE invocation
IndexPart ::=
"PIB-INDEX" "{" Index "}" -- new
| "AUGMENTS" "{" Entry "}"
| "EXTENDS" "{" Entry "}" -- new
| empty
Index ::=
-- the correspondent OBJECT-TYPE invocation
value(ObjectName)
Entry ::=
-- use the INDEX value of the
-- correspondent OBJECT-TYPE invocation
value(ObjectName)
MibIndexPart ::=
"INDEX" "{" IndexTypePart "}"
| empty
IndexTypePart ::=
IndexTypes
| IndexTypes "," ImpliedIndex
| ImpliedIndex
IndexTypes ::=
Index
| IndexTypes "," Index
ImpliedIndex ::=
"IMPLIED" Index
value(ObjectName)
MibIndexPart ::=
"INDEX" "{" IndexTypePart "}"
| empty
IndexTypePart ::=
IndexTypes
| IndexTypes "," ImpliedIndex
| ImpliedIndex
IndexTypes ::=
Index
| IndexTypes "," Index
ImpliedIndex ::=
"IMPLIED" Index
PibReferencesPart ::=
-- for use with ReferenceId TC
"PIB-REFERENCES" "{" Entry "}"
| empty
PibReferencesPart ::=
-- for use with ReferenceId TC
"PIB-REFERENCES" "{" Entry "}"
| empty
PibTagPart ::=
-- for use with TagReferenceId TC
"PIB-TAG" "{" Attr "}"
| empty
PibTagPart ::=
-- for use with TagReferenceId TC
"PIB-TAG" "{" Attr "}"
| empty
Attr ::= -- specifies an attribute
value(ObjectName)
Attr ::= -- specifies an attribute
value(ObjectName)
UniquePart ::= -- new
"UNIQUENESS" "{" UniqueTypes "}"
| "UNIQUENESS" "{" "}"
| empty
UniqueTypes ::=
UniqueType
| UniqueTypes "," UniqueType
UniqueType ::=
-- the correspondent OBJECT-TYPE invocation
value(ObjectName)
UniquePart ::= -- new
"UNIQUENESS" "{" UniqueTypes "}"
| "UNIQUENESS" "{" "}"
| empty
UniqueTypes ::=
UniqueType
| UniqueTypes "," UniqueType
UniqueType ::=
-- the correspondent OBJECT-TYPE invocation
value(ObjectName)
DefValPart ::= "DEFVAL" "{" Defvalue "}"
| empty
DefValPart ::= "DEFVAL" "{" Defvalue "}"
| empty
Defvalue ::= -- must be valid for the type specified in
-- SYNTAX clause of same OBJECT-TYPE macro
value(ObjectSyntax)
| "{" BitsValue "}"
Defvalue ::= -- must be valid for the type specified in
-- SYNTAX clause of same OBJECT-TYPE macro
value(ObjectSyntax)
| "{" BitsValue "}"
BitsValue ::= BitNames
BitsValue ::= BitNames
| empty
|空的
BitNames ::= BitName
| BitNames "," BitName
BitNames ::= BitName
| BitNames "," BitName
BitName ::= identifier
BitName ::= identifier
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- definitions for conformance groups
--一致性组的定义
OBJECT-GROUP MACRO ::=
BEGIN
TYPE NOTATION ::=
ObjectsPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
OBJECT-GROUP MACRO ::=
BEGIN
TYPE NOTATION ::=
ObjectsPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
ObjectsPart ::=
"OBJECTS" "{" Objects "}"
Objects ::=
Object
| Objects "," Object
Object ::=
value(ObjectName)
ObjectsPart ::=
"OBJECTS" "{" Objects "}"
Objects ::=
Object
| Objects "," Object
Object ::=
value(ObjectName)
Status ::=
"current"
| "deprecated"
| "obsolete"
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- definitions for compliance statements
--合规性声明的定义
MODULE-COMPLIANCE MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
ModulePart
MODULE-COMPLIANCE MACRO ::=
BEGIN
TYPE NOTATION ::=
"STATUS" Status
"DESCRIPTION" Text
ReferPart
ModulePart
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER)
Status ::=
"current"
| "deprecated"
| "obsolete"
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ReferPart ::=
"REFERENCE" Text
| empty
ModulePart ::=
Modules
Modules ::=
Module
| Modules Module
Module ::=
-- name of module --
"MODULE" ModuleName
MandatoryPart
CompliancePart
ModulePart ::=
Modules
Modules ::=
Module
| Modules Module
Module ::=
-- name of module --
"MODULE" ModuleName
MandatoryPart
CompliancePart
ModuleName ::=
-- identifier must start with uppercase letter
identifier ModuleIdentifier
-- must not be empty unless contained
-- in MIB Module
| empty
ModuleIdentifier ::=
value(OBJECT IDENTIFIER)
| empty
ModuleName ::=
-- identifier must start with uppercase letter
identifier ModuleIdentifier
-- must not be empty unless contained
-- in MIB Module
| empty
ModuleIdentifier ::=
value(OBJECT IDENTIFIER)
| empty
MandatoryPart ::=
"MANDATORY-GROUPS" "{" Groups "}"
| empty
MandatoryPart ::=
"MANDATORY-GROUPS" "{" Groups "}"
| empty
Groups ::=
Group
| Groups "," Group
Groups ::=
Group
| Groups "," Group
Group ::=
value(OBJECT IDENTIFIER)
Group ::=
value(OBJECT IDENTIFIER)
CompliancePart ::=
Compliances
| empty
CompliancePart ::=
Compliances
| empty
Compliances ::=
Compliance
| Compliances Compliance
Compliance ::=
ComplianceGroup
| Object
Compliances ::=
Compliance
| Compliances Compliance
Compliance ::=
ComplianceGroup
| Object
ComplianceGroup ::=
"GROUP" value(OBJECT IDENTIFIER)
"DESCRIPTION" Text
ComplianceGroup ::=
"GROUP" value(OBJECT IDENTIFIER)
"DESCRIPTION" Text
Object ::=
"OBJECT" value(ObjectName)
InstallSyntaxPart -- modified
AccessPart
"DESCRIPTION" Text
Object ::=
"OBJECT" value(ObjectName)
InstallSyntaxPart -- modified
AccessPart
"DESCRIPTION" Text
-- must be a refinement for object's SYNTAX clause
InstallSyntaxPart ::= "SYNTAX" Syntax
| empty
-- must be a refinement for object's SYNTAX clause
InstallSyntaxPart ::= "SYNTAX" Syntax
| empty
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement),
-- a textual convention (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
NamedBit ::= identifier "(" number ")" -- number is nonnegative
AccessPart ::=
"PIB-MIN-ACCESS" Access -- modified
| empty
Access ::= -- modified
"not-accessible"
| "install"
| "notify"
| "install-notify"
AccessPart ::=
"PIB-MIN-ACCESS" Access -- modified
| empty
Access ::= -- modified
"not-accessible"
| "install"
| "notify"
| "install-notify"
| "report-only"
|“仅报告”
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- a character string as defined in [SMI]
Text ::= value(IA5String)
END
-- definition of textual conventions
--文本约定的定义
TEXTUAL-CONVENTION MACRO ::=
BEGIN
TYPE NOTATION ::=
DisplayPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
"SYNTAX" Syntax
TEXTUAL-CONVENTION MACRO ::=
BEGIN
TYPE NOTATION ::=
DisplayPart
"STATUS" Status
"DESCRIPTION" Text
ReferPart
"SYNTAX" Syntax
VALUE NOTATION ::=
value(VALUE Syntax) -- adapted ASN.1
VALUE NOTATION ::=
value(VALUE Syntax) -- adapted ASN.1
DisplayPart ::=
"DISPLAY-HINT" Text
| empty
DisplayPart ::=
"DISPLAY-HINT" Text
| empty
Status ::=
"current"
| "deprecated"
| "obsolete"
Status ::=
"current"
| "deprecated"
| "obsolete"
ReferPart ::=
"REFERENCE" Text
| empty
ReferPart ::=
"REFERENCE" Text
| empty
-- a character string as defined in [SMI]
Text ::= value(IA5String)
-- a character string as defined in [SMI]
Text ::= value(IA5String)
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
Syntax ::= -- Must be one of the following:
-- a base type (or its refinement), or
-- a BITS pseudo-type
type
| "BITS" "{" NamedBits "}"
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBits ::= NamedBit
| NamedBits "," NamedBit
NamedBit ::= identifier "(" number ")" -- number is nonnegative
NamedBit ::= identifier "(" number ")" -- number is nonnegative
END
终止
END
终止
COPS-PR-SPPI-TC PIB-DEFINITIONS ::= BEGIN
COPS-PR-SPPI-TC PIB-DEFINITIONS ::= BEGIN
IMPORTS Unsigned32, MODULE-IDENTITY, TEXTUAL-CONVENTION, pib FROM COPS-PR-SPPI;
从COPS-PR-SPPI导入未签名32、模块标识、文本约定、pib；
copsPrSppiTc MODULE-IDENTITY SUBJECT-CATEGORIES { all } LAST-UPDATED "200108160000Z" ORGANIZATION "IETF RAP WG" CONTACT-INFO "Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive, San Jose, CA 95134-1706 USA Phone: +1 408 526 5260 Email: kzm@cisco.com
COPSPRPPITC模块身份主题类别{all}最近更新的“200108160000Z”组织“IETF RAP WG”联系方式“Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号邮编95134-1706电话：+1 408 526 5260电子邮件：kzm@cisco.com
Ravi Sahita
Intel
2111 NE 25th Avenue
Hillsboro, OR 97124 USA
Phone: +1 503 712 1554
Email: ravi.sahita@intel.com "
DESCRIPTION
"The PIB module containing a set of Textual Conventions
which have general applicability to all PIB modules."
REVISION "200108160000Z"
DESCRIPTION
"Initial version, published in RFC 3159."
::= { pib 1 }
Ravi Sahita
Intel
2111 NE 25th Avenue
Hillsboro, OR 97124 USA
Phone: +1 503 712 1554
Email: ravi.sahita@intel.com "
DESCRIPTION
"The PIB module containing a set of Textual Conventions
which have general applicability to all PIB modules."
REVISION "200108160000Z"
DESCRIPTION
"Initial version, published in RFC 3159."
::= { pib 1 }
InstanceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The textual convention for use by an attribute which is used
as the instance-identifying index of a PRC, i.e., an attribute
named in a PIB-INDEX clause. The value of an attribute with
this syntax is always greater than zero. PRIs of the same PRC
need not have contiguous values for their instance-identifying
attribute."
SYNTAX Unsigned32 (1..4294967295)
InstanceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The textual convention for use by an attribute which is used
as the instance-identifying index of a PRC, i.e., an attribute
named in a PIB-INDEX clause. The value of an attribute with
this syntax is always greater than zero. PRIs of the same PRC
need not have contiguous values for their instance-identifying
attribute."
SYNTAX Unsigned32 (1..4294967295)
ReferenceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A textual convention for use by an attribute which is used as
a pointer in order to reference an instance of a particular
ReferenceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A textual convention for use by an attribute which is used as
a pointer in order to reference an instance of a particular
PRC. An attribute with this syntax must not be used in a PIB-INDEX clause , and its description must specify the particular PRC to which the referenced PRI will belong. For an attribute of this type, the referenced PRI must exist. Furthermore, it is an error to try to delete a PRI that is referenced by another instance without first deleting/modifying the referencing instance. The definition of an attribute with this syntax can permit the attribute to have a value of zero to indicate that it is not currently pointing to a PRI." SYNTAX Unsigned32
中华人民共和国。具有此语法的属性不得在PIB-INDEX子句中使用，其描述必须指定引用PRI所属的特定PRC。对于此类型的属性，引用的PRI必须存在。此外，尝试删除另一个实例引用的PRI而不首先删除/修改引用实例是错误的。使用此语法的属性定义可以允许该属性的值为零，以表示它当前未指向PRI。“语法未签名32
Prid ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a pointer to a PRI, i.e,. to an instance of a
PRC. The value is the OID name of the PRC's row definition,
appended with one sub-identifier containing the value of the
InstanceId value for the referenced instance. The definition
of an attribute with this syntax can permit the attribute to
have a value of 0.0 to indicate that it is not currently
pointing to a PRI."
SYNTAX OBJECT IDENTIFIER
Prid ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a pointer to a PRI, i.e,. to an instance of a
PRC. The value is the OID name of the PRC's row definition,
appended with one sub-identifier containing the value of the
InstanceId value for the referenced instance. The definition
of an attribute with this syntax can permit the attribute to
have a value of 0.0 to indicate that it is not currently
pointing to a PRI."
SYNTAX OBJECT IDENTIFIER
TagId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a tag value, such that all instances of a
particular PRC having the same tag value form a tag list.
A tag list is identified by the tag value shared by all
instances in that tag list."
SYNTAX Unsigned32 (1..4294967295)
TagId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a tag value, such that all instances of a
particular PRC having the same tag value form a tag list.
A tag list is identified by the tag value shared by all
instances in that tag list."
SYNTAX Unsigned32 (1..4294967295)
TagReferenceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a reference to a tag list of instances of a
particular PRC. The particular PRC must have an attribute
with the syntax of TagId. The tag list consists of
all instances which have the same value of the TagId
attribute. Reference to the tag list is via the attribute
with the syntax of TagReferenceId containing the tag
value which identifies the tag list.
The definition of an attribute with this syntax can permit
the attribute to have a value of 0 to indicate that it is
not currently referencing a tag list."
SYNTAX Unsigned32
END
TagReferenceId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents a reference to a tag list of instances of a
particular PRC. The particular PRC must have an attribute
with the syntax of TagId. The tag list consists of
all instances which have the same value of the TagId
attribute. Reference to the tag list is via the attribute
with the syntax of TagReferenceId containing the tag
value which identifies the tag list.
The definition of an attribute with this syntax can permit
the attribute to have a value of 0 to indicate that it is
not currently referencing a tag list."
SYNTAX Unsigned32
END
The names of all standard PIB modules must be unique (but different versions of the same module should have the same name). Developers of enterprise PIB modules are encouraged to choose names for their modules that will have a low probability of colliding with standard or other enterprise modules.
所有标准PIB模块的名称必须唯一（但同一模块的不同版本应具有相同的名称）。鼓励企业PIB模块的开发人员为其模块选择与标准模块或其他企业模块发生冲突的可能性较低的名称。
The first line of a PIB module is:
PIB模块的第一行是：
PIB-MODULE-NAME PIB-DEFINITIONS ::= BEGIN
PIB-MODULE-NAME PIB-DEFINITIONS ::= BEGIN
where PIB-MODULE-NAME is the module name.
其中，PIB-MODULE-NAME是模块名称。
Like the SMI, additional ASN.1 macros must not be defined in PIB modules.
与SMI一样，不能在PIB模块中定义其他ASN.1宏。
Like the SMI, a PIB module which needs to reference an external definition, must use the IMPORTS statement to identify both the descriptor and the module in which the descriptor is defined, where a module is identified by its ASN.1 module name.
与SMI一样，需要引用外部定义的PIB模块必须使用IMPORTS语句来标识描述符和定义描述符的模块，其中模块由其ASN.1模块名称标识。
In particular, a PIB module imports each of the base data types that it uses from COPS-PR-SPPI (defined in this document), and may import as required from other PIB modules. A PIB module may import, from the SMI, (subtree) OIDs for the purpose of defining new OIDs. A PIB module may also import, from MIB modules, OID assignments as well as textual convention definitions providing that their underlying syntax is supported by the SPPI. However, the following must not be included in an IMPORTS statement:
具体而言，PIB模块从COPS-PR-SPPI（定义见本文件）导入其使用的每种基本数据类型，并可根据需要从其他PIB模块导入。PIB模块可以从SMI导入（子树）OID以定义新OID。PIB模块还可以从MIB模块导入OID分配以及文本约定定义，前提是SPPI支持它们的底层语法。但是，进口声明中不得包含以下内容：
- named types defined by ASN.1 itself, specifically: INTEGER, OCTET STRING, OBJECT IDENTIFIER, SEQUENCE, SEQUENCE OF type,
- ASN.1本身定义的命名类型，具体为：整数、八位字节字符串、对象标识符、序列、类型序列、，
- the BITS construct.
- 比特构造。
For each ASN.1 macro that a PIB uses, it must import that macro's definition from the COPS-PR-SPPI.
对于PIB使用的每个ASN.1宏，它必须从COPS-PR-SPPI导入该宏的定义。
In addition to the reserved keywords listed in the SMI, the following must not be used as descriptors or module names:
除SMI中列出的保留关键字外，以下内容不得用作描述符或模块名称：
EXTENDS INSTALL-ERRORS Integer64 PIB-MIN-ACCESS PIB-ACCESS PIB-INDEX PIB-REFERENCES PIB-TAG SUBJECT-CATEGORIES UNIQUENESS Unsigned64
扩展安装错误整数64 PIB-MIN-ACCESS PIB-ACCESS PIB-INDEX PIB-REFERENCES PIB-TAG主题类别唯一性未签名64
The SPPI uses the same OBJECT IDENTIFIER naming hierarchy as the SMI. That is, OIDs are typically assigned to PIB modules from the subtree administered by the Internet Assigned Numbers Authority (IANA). However, like the SMI, the SPPI does not prohibit the definition of PRCs in other portions of the OID tree.
SPPI使用与SMI相同的对象标识符命名层次结构。也就是说，OID通常从互联网分配号码管理局（IANA）管理的子树分配给PIB模块。然而，与SMI一样，SPPI并不禁止在OID树的其他部分中定义PRC。
The SUBJECT-CATEGORIES clause, which must be present, identifies one or more categories of provisioning data for which this PIB module defines provisioning information. For use with the COPS-PR protocol, the individual subject categories are mapped to COPS Client Types [COPS-PR]. IANA Considerations for SPPI SUBJECT-CATEGORIES follow the same requirements as specified in [COPS] IANA Considerations for COPS Client Types. The subject categories are identified either:
SUBJECT-CATEGORIES子句（必须存在）标识此PIB模块为其定义配置信息的一个或多个配置数据类别。为了与COPS-PR协议一起使用，各个主题类别映射到COPS客户端类型[COPS-PR]。SPPI主题类别的IANA注意事项遵循[COPS]IANA注意事项中针对COPS客户类型规定的相同要求。主题类别可确定为：
- via the keyword "all", indicating the PIB module defines provisioning information relevant for all subject categories (and thus, all COPS Client Types), or
- 通过关键字“all”，表示PIB模块定义了与所有主题类别（以及所有COPS客户端类型）相关的供应信息，或
- a list of named-number enumerations, where each number which must be greater than zero, identifies a subject category, and is mapped to the Client Type which is identified by that same number in the COPS protocol. The namespace for these named numbers is global and therefore the labels should be assigned consistently across PIB modules. At present time, no more than one named-number enumeration should be specified.
- 命名编号枚举列表，其中每个编号必须大于零，标识主题类别，并映射到COPS协议中由相同编号标识的客户端类型。这些命名编号的名称空间是全局的，因此应在PIB模块之间一致地分配标签。目前，不应指定多个命名编号枚举。
Note that the list of categories specified in a PIB module's SUBJECT-CATEGORIES clause is not exclusive. That is, some other specification might (e.g., at a future date) specify additional COPS Client Types to which the module is relevant.
请注意，PIB模块的SUBJECT-categories子句中指定的类别列表不是排他性的。也就是说，一些其他规范可能（例如，在将来的某个日期）指定与模块相关的其他COPS客户端类型。
When a PIB module applies to multiple subject categories, that PIB module exists in multiple virtual information stores, one for each Client-Type. A PIB module with SUBJECT-CATEGORIES "all" uses the named- number specified in the SUBJECT-CATEGORIES of the PIB it is associated with, as the COPS Client-Type when it is sent over COPS.
当PIB模块应用于多个主题类别时，该PIB模块存在于多个虚拟信息存储中，每个客户机类型对应一个虚拟信息存储。主题类别为“全部”的PIB模块在通过COPS发送时，使用与之关联的PIB主题类别中指定的命名编号作为COPS客户端类型。
The SPPI requires that all attribute definitions be contained within a PRC, i.e., within a table definition.
SPPI要求所有属性定义都包含在PRC中，即表定义中。
The SYNTAX clause, which must be present within the definition of an attribute, defines the abstract data structure of that attribute. The data structure must be one of the following: a base type, the BITS construct, or a textual convention.
SYNTAX子句必须出现在属性的定义中，它定义了该属性的抽象数据结构。数据结构必须是以下之一：基类型、位构造或文本约定。
The SYNTAX clause must also be present for the table and row definitions of a PRC, and in this case must be a SEQUENCE OF or SEQUENCE (see section 8.1.7 below).
PRC的表和行定义也必须包含SYNTAX子句，在这种情况下，必须是or序列（见下文第8.1.7节）。
The base types are an extended subset of the SMI's base types:
基本类型是SMI基本类型的扩展子集：
- built-in ASN.1 types: INTEGER, OCTET STRING, OBJECT IDENTIFIER,
- 内置ASN.1类型：整数、八位字符串、对象标识符、，
- application-defined types: Integer32, Unsigned32, TimeTicks, Integer64 and Unsigned64.
- 应用程序定义的类型：Integer32、Unsigned32、TimeTicks、Integer64和Unsigned64。
A textual convention is a newly-defined type defined as a sub-type of a base type [TC]. The value of an attribute whose syntax is defined using a textual convention is encoded "on-the-wire" according to the textual convention's underlying base type.
文本约定是新定义的类型，定义为基类型[TC]的子类型。使用文本约定定义语法的属性的值根据文本约定的基础基类型进行“在线”编码。
Note that the set of base types has been chosen so as to provide sufficient variety of on-the-wire encodings for attribute values; base types should contain a minimum of semantics. Semantics should, to the extent possible, be incorporated into a data type through the use of a textual convention.
请注意，已选择基本类型集，以便为属性值提供足够多的在线编码；基本类型应该包含最少的语义。语义应该尽可能通过使用文本约定合并到数据类型中。
The differences from the SMI in the semantics of ObjectSyntax are now described.
现在描述了ObjectSyntax在语义上与SMI的区别。
The Counter32 type is not supported by the SPPI.
SPPI不支持计数器32类型。
The Gauge32 type is not supported by the SPPI.
SPPI不支持Gauge32类型。
The Opaque type is provided solely for backward-compatibility, and shall not be used for newly-defined object types. The Opaque type supports the capability to pass arbitrary ASN.1 syntax. A value is encoded using the ASN.1 Basic Encoding Rules [ASN1] into a string of octets. This, in turn, is encoded as an OCTET STRING, in effect "double-wrapping" the original ASN.1 value. Note that a conforming implementation need only be able to accept and recognize opaquely-encoded data. It need not be able to unwrap the data and then interpret its contents. A requirement on "standard" PIB modules is that no object may have a SYNTAX clause value of Opaque.
不透明类型仅用于向后兼容，不得用于新定义的对象类型。不透明类型支持传递任意ASN.1语法的能力。使用ASN.1基本编码规则[ASN1]将值编码为八进制字符串。这又被编码为八位字节字符串，实际上是“双重包装”原始ASN.1值。注意，一致性实现只需要能够接受和识别不透明编码的数据。它不需要能够展开数据，然后解释其内容。“标准”PIB模块的一个要求是，任何对象的语法子句值都不能为不透明。
The IpAddress type is provided solely for backward-compatibility, and shall not be used for newly-defined object types. Instead, It is recommended to use the InetAddressType/InetAddress pair TCs as defined in RFC2851 [INETADDR].
IpAddress类型仅用于向后兼容，不得用于新定义的对象类型。相反，建议使用RFC2851[INETADDR]中定义的InetAddressType/InetAddress对TC。
The Counter64 type is not supported by the SPPI.
SPPI不支持计数器64类型。
The Integer64 type represents integer-valued information between -2^63 and 2^63-1 inclusive (-9223372036854775808 to 9223372036854775807 decimal). While Integer64 may be sub-typed to be more constrained, if the constraint results in all possible values being contained in the range (-2147483648..2147483647), then the Integer32 type must be used instead of Integer64.
Integer64类型表示介于-2^63和2^63-1（含）之间的整数值信息（-9223372036854775808到9223372036854775807十进制）。虽然Integer64可以是子类型，以便更受约束，但如果约束导致所有可能的值都包含在范围（-2147483648..2147483647）中，则必须使用Integer32类型而不是Integer64。
The Unsigned64 type represents integer-valued information between 0 and 2^64-1 inclusive (0 to 18446744073709551615 decimal). While Unsigned64 may be sub-typed to be more constrained, if the constraint results in all possible values being contained in the range (0..4294967295), then the Unsigned32 type must be used instead of Unsigned64.
Unsigned64类型表示0到2^64-1（包括0到18446744073709551615十进制）之间的整数值信息。虽然Unsigned64可能是子类型，以便受到更多约束，但如果约束导致所有可能的值都包含在范围（0..4294967295）中，则必须使用Unsigned32类型而不是Unsigned64。
The operations (on PIBs) supported by the SPPI apply exclusively to PRCs. Each PRC is modelled as a tabular structure, i.e., a table. Each instance of a particular PRC has the same set of attributes. The set of attributes which belong to every instance of a particular PRC is modelled as a row in the table. Note that a PRC must have no more than 127 attributes. The usage of subids (for PRC attributes) beyond 127 (that is 128 and above) is reserved for Mapping PIBs to MIBs (see Appendix A). PRCs that require more than 127 attributes must use the AUGMENTS clause to augment the PRC containing the initial 127 attributes to add additional attributes. Definition of Provisioning Classes is formalized by using the OBJECT-TYPE macro to define both:
SPPI支持的操作（在PIB上）仅适用于PRC。每个PRC建模为表格结构，即表格。特定PRC的每个实例都具有相同的属性集。属于特定PRC的每个实例的属性集被建模为表中的一行。请注意，PRC的属性不得超过127个。127（即128及以上）之外的子ID（PRC属性）的使用是为将PIB映射到MIB而保留的（见附录A）。需要127个以上属性的PRC必须使用AUGMENTS子句来扩充包含初始127个属性的PRC，以添加其他属性。配置类的定义通过使用对象类型宏来定义以下两个类来形式化：
- the PRC as a whole, called the table definition, and
- 中国作为一个整体，称为表定义，以及
- the characteristics of every instance of a particular PRC, called the row definition.
- 特定PRC的每个实例的特征，称为行定义。
In the table definition, the SYNTAX clause has the form:
在表定义中，SYNTAX子句的形式如下：
SEQUENCE OF <EntryType>
<EntryType>
where <EntryType> refers to the SEQUENCE type of its attribute definitions. In the row definition, the SYNTAX clause has the form:
其中，<EntryType>是指其属性定义的序列类型。在行定义中，SYNTAX子句的形式如下：
<EntryType>
<EntryType>
where <EntryType> is a SEQUENCE type defined as follows:
其中，<EntryType>是定义如下的序列类型：
<EntryType> ::= SEQUENCE { <type1>, ... , <typeN> }
<EntryType> ::= SEQUENCE { <type1>, ... , <typeN> }
where there is one <type> for each attribute, and each <type> is of the form:
其中每个属性有一个<type>，每个<type>的形式如下：
<descriptor> <syntax>
<descriptor> <syntax>
where <descriptor> is the descriptor naming an attribute, and <syntax> has the value of that attribute's SYNTAX clause, except that both sub- typing information and the named values for enumerated integers or the named bits for the BITS construct, are omitted from <syntax>.
其中，<descriptor>是命名属性的描述符，<syntax>具有该属性的syntax子句的值，除了子类型信息和枚举整数的命名值或位构造的命名位在<syntax>中被省略。
The MAX-ACCESS clause is not supported by the SPPI.
SPPI不支持MAX-ACCESS子句。
The PIB-ACCESS clause must be present for a PRC's table definition, and must not be present for any other OBJECT-TYPE definition. The PIB-ACCESS clause defines what kind of access is appropriate for the PRC.
PRC的表定义必须有PIB-ACCESS子句，而任何其他对象类型定义都不能有PIB-ACCESS子句。PIB-ACCESS条款定义了适用于中国的访问类型。
- the value "install" is used to indicate a PRC which a PDP can install in the PEP as provisioning information.
- 值“install”用于指示PDP可以在PEP中安装的PRC作为供应信息。
- the value "notify" is used to indicate a PRC for which the PEP must notify the PDP of all its instances and attribute values of that PRC.
- 值“notify”用于表示政治公众人物必须将其所有实例和该PRC的属性值通知PDP的PRC。
- the value "install-notify" is used to indicate the uncommon type of PRC which has both characteristics: "install" and "notify".
- 值“install notify”用于表示PRC的不常见类型，它具有“install”和“notify”两个特征。
- the value "report-only" is used to indicate a PRC which has neither the "install" characteristic nor the "notify" characteristic. However, instances of such a PRC may be included in synchronous/asynchronous reports generated by the PEP. (Note: PRCs having the "install" and/or "notify" characteristics may also be included in reports generated by the PEP.)
- 值“仅报告”用于表示既没有“安装”特性也没有“通知”特性的PRC。然而，此类PRC的实例可包括在政治公众人物生成的同步/异步报告中。（注：具有“安装”和/或“通知”特征的PRC也可包含在政治公众人物生成的报告中。）
The INSTALL-ERRORS clause, which may optionally be present for a PRC's table definition, and must be absent otherwise, lists one or more potential reasons for rejecting an install or a removal of an instance of the PRC. Each reason consists of a named-number enumeration, where the number represents a PRC-specific error-code to be used in a COPS protocol message, as the Error Sub-code, with the Error-Code set to priSpecificError (see [COPS-PR]). The semantics of each named-number enumeration should be described in the PRC's DESCRIPTION clause.
INSTALL-ERRORS子句（PRC的表定义中可能会有）列出了拒绝安装或删除PRC实例的一个或多个潜在原因，该子句在PRC的表定义中可能存在，在其他情况下必须不存在。每个原因都包含一个命名的数字枚举，其中数字表示将在COPS协议消息中使用的PRC特定错误代码，作为错误子代码，错误代码设置为PRISSpecificError（请参见[COPS-PR]）。PRC的描述条款中应描述每个命名数字枚举的语义。
The numbers listed in an INSTALL-ERRORS must be greater than zero and less than 65536. If this clause is not present, an install/remove can still fail, but no PRC-specific error is available to be reported.
安装错误中列出的数字必须大于零且小于65536。如果此条款不存在，安装/删除仍可能失败，但没有可报告的PRC特定错误。
The PIB-INDEX clause, which must be present for a row definition (unless an AUGMENTS or an EXTENDS clause is present instead), and must be absent otherwise, defines identification information for instances of the PRC.
PIB-INDEX子句定义PRC实例的标识信息。PIB-INDEX子句必须出现在行定义中（除非出现了增广或扩展子句），否则必须不存在。
The PIB-INDEX clause includes exactly one descriptor. This descriptor specifies an attribute (typically, but not necessarily of the same PRC) which is used to identify an instance of that PRC. The syntax of this attribute is REQUIRED to be InstanceId (a textual convention with an underlying syntax of Unsigned32), and it has no semantics other than its use in identifying the PRC instance. The OBJECT IDENTIFIER which identifies an instance of a PRC is formed by appending one sub- identifier to the OID which identifies that PRC's row definition. The value of the additional sub-identifier is that instance's value of the attribute specified in the INDEX clause.
PIB-INDEX子句只包含一个描述符。此描述符指定用于标识该PRC实例的属性（通常，但不一定是同一PRC）。该属性的语法必须是InstanceId（一种文本约定，其基本语法为Unsigned32），并且除了用于标识PRC实例之外，它没有其他语义。标识PRC实例的对象标识符是通过向标识PRC行定义的OID附加一个子标识符形成的。附加子标识符的值是该实例在INDEX子句中指定的属性的值。
Note that SPPI does not permit use of the IMPLIED keyword in a PIB-INDEX clause.
请注意，SPPI不允许在PIB-INDEX子句中使用隐含关键字。
The INDEX clause is optionally present if a PIB-INDEX clause is present, and must be absent otherwise. If present, the INDEX clause can contain any number of attributes, and is used only by the algorithmic conversion of a PIB to a MIB (see Appendix A).
如果存在PIB-INDEX子句，则INDEX子句可以选择存在，否则必须不存在。如果存在，INDEX子句可以包含任意数量的属性，并且仅用于PIB到MIB的算法转换（参见附录a）。
An IMPLIED keyword can be present in an INDEX clause if so desired.
如果需要，可以在索引子句中显示隐含关键字。
The AUGMENTS clause, which must not be present except in row definitions, is an alternative to the PIB-INDEX clause and the EXTENDS clause. Every row definition has exactly one of: a PIB-INDEX clause, an AUGMENTS clause, or an EXTENDS clause.
AUGMENTS子句是PIB-INDEX子句和EXTENDS子句的替代品，除了行定义中，它不能出现。每一行定义都只有一个：PIB-INDEX子句、AUGMENTS子句或EXTENDS子句。
A row definition which has a PIB-INDEX clause is called a base row definition. A row definition which has an AUGMENTS clause is called a row augmentation, where the AUGMENTS clause names the base row definition which is augmented by this row augmentation. (Thus, a row augmentation cannot itself be augmented.)
具有PIB-INDEX子句的行定义称为基行定义。具有AUGMENTS子句的行定义称为行扩充，其中AUGMENTS子句命名由该行扩充扩充的基行定义。（因此，行扩充本身无法扩充。）
A PRC whose row definition is a row augmentation is called an augmenting PRC. Instances of an augmenting PRC are identified according to the PIB-INDEX clause of the base row definition named in the AUGMENTS clause. Further, instances of an augmenting PRC exist according to the same semantics as instances of the PRC which it augments. As such, when an instance of a PRC is installed or removed, an instance of every PRC which augments it is also installed or removed. (for more details, see [COPS-PR]).
行定义为行扩充的PRC称为扩充PRC。根据在AUGMENTS子句中命名的基本行定义的PIB-INDEX子句来标识扩充PRC的实例。此外，扩充PRC的实例根据与其扩充的PRC实例相同的语义存在。因此，当安装或删除PRC的实例时，也会安装或删除每个PRC的实例，以增强其功能。（有关更多详细信息，请参见[COPS-PR]）。
The EXTENDS clause, which must not be present except in row definitions, is an alternative to the PIB-INDEX clause and the AUGMENTS clause. Every row definition has exactly one of: a PIB-INDEX clause, an AUGMENTS clause, or an EXTENDS clause.
EXTENDS子句是PIB-INDEX子句和AUGMENTS子句的替代品，只能在行定义中出现。每一行定义都只有一个：PIB-INDEX子句、AUGMENTS子句或EXTENDS子句。
A row definition which has an EXTENDS clause is called a sparse row augmentation, where the EXTENDS clause names the row definition which is sparsely-augmented by this sparse row augmentation. The sparsely-augmented row can be a base row definition, or another sparse row augmentation.
具有EXTENDS子句的行定义称为稀疏行扩充，其中EXTENDS子句命名由该稀疏行扩充稀疏扩充的行定义。稀疏扩充行可以是基行定义，也可以是另一个稀疏扩充行。
A PRC whose row definition is a sparse row augmentation is called a sparsely augmenting PRC. Instances of a sparsely augmenting PRC are identified according to the PIB-INDEX clause of the row definition named in the sparsely augmenting PRC's EXTENDS clause.
行定义为稀疏行扩充的PRC称为稀疏扩充PRC。稀疏增强PRC的实例根据稀疏增强PRC的EXTENDS子句中指定的行定义的PIB-INDEX子句进行标识。
An instance of a sparsely augmenting PRC can not exist unless a corresponding instance of the PRC which it sparsely augments exists. As such, when an instance of a PRC is removed, an instance of any PRC which sparsely augments it is also removed. However, an instance of a sparsely augmenting PRC need not exist when the corresponding instance of the PRC that it sparsely augments exists. Thus, an instance of a sparsely augmenting PRC can be installed at the same time as or subsequent to the installation of, and can be removed prior to the removal of, the corresponding instance of the PRC that it sparsely augments. So, instances of a sparsely augmenting PRC must be installed explicitly, but are removed either implicitly (via removal of the augmented PRI) or explicitly. When a sparsely augmented PRC is installed, both instances, the instance of the sparsely augmented PRC and the instance of the sparsely augmenting PRC must be sent in one COPS message.
稀疏扩充PRC的实例不可能存在，除非其稀疏扩充的PRC的相应实例存在。因此，当删除某个PRC实例时，任何稀疏增加该实例的PRC实例也将被删除。然而，当其稀疏扩充的PRC的相应实例存在时，稀疏扩充PRC的实例不需要存在。因此，稀疏增强PRC的实例可以在安装PRC的同时或之后安装，并且可以在移除其稀疏增强的PRC的相应实例之前移除。因此，稀疏增强PRC的实例必须显式安装，但可以隐式（通过删除增强PRI）或显式删除。当安装稀疏增强的PRC时，两个实例、稀疏增强的PRC实例和稀疏增强的PRC实例必须在一条COPS消息中发送。
When defining instance identification information for a PRC:
定义PRC的实例标识信息时：
- If there is a one-to-one correspondence between instances of this PRC and instances of an existing PRC, then the AUGMENTS clause should be used.
- 如果本PRC实例与现有PRC实例之间存在一一对应关系，则应使用增广条款。
- Otherwise, if there is a sparse relationship between instances of this PRC and instances of an existing PRC (that is, there is a one to zero or one correspondence between instances of a sparsely augmented PRC and the instances of the PRC that sparsely augments it.), then an EXTENDS clause should be used.
- 否则，如果该PRC实例与现有PRC实例之间存在稀疏关系（即，稀疏扩充PRC实例与稀疏扩充PRC实例之间存在一对零或一对应关系），则应使用扩展条款。
- Otherwise, a PIB-INDEX clause should be used which names its own InstanceId attribute.
- 否则，应该使用PIB-INDEX子句来命名自己的InstanceId属性。
The UNIQUENESS clause, which is optionally present for any row definition, lists a set of zero or more of the PRC's attributes, for which no two instances of the PRC can have the same set of values. The specified set of attributes provide a necessary and sufficient set of values by which to identify an instance of this PRC. The attribute contained in the PIB-INDEX clause may not be present in the UNIQUENESS clause. By definition, an attribute may not appear more than once in a UNIQUENESS clause. A UNIQUENESS clause containing zero attributes indicates that it's possible for two instances of the PRC to have identical values for all attributes except, of course, for the one named in the PIB-INDEX clause.
唯一性子句（可选地用于任何行定义）列出了一组零个或多个PRC属性，PRC的任何两个实例都不能具有相同的值集。指定的属性集提供了一组必要且充分的值，用于标识此PRC的实例。PIB-INDEX子句中包含的属性可能不存在于UNIQUISITY子句中。根据定义，属性在唯一性子句中不能出现多次。包含零属性的唯一性子句表示PRC的两个实例可能对所有属性具有相同的值，当然PIB-INDEX子句中指定的属性除外。
If a PRC and its sparsely augmenting PRC both have UNIQUENESS clauses, then the UNIQUENESS constraint for instances of each PRC MUST be applied according to the UNIQUENESS clause in the corresponding PRC definition. Note that a sparsely augmenting PRC thus can override the UNIQUENESS clause of the PRC it sparsely augments.
如果一个PRC及其稀疏扩展的PRC都有唯一性条款，则必须根据相应PRC定义中的唯一性条款应用每个PRC实例的唯一性约束。请注意，稀疏扩展的PRC因此可以覆盖其稀疏扩展的PRC的唯一性条款。
Even though the UNIQUENESS clause is optional, its inclusion is recommended wherever it provides useful information.
尽管university子句是可选的，但只要它提供有用的信息，就建议将其包含在内。
The PIB-REFERENCES clause, which must be present for any attribute which has the SYNTAX of ReferenceId, and must be absent otherwise, names the PRC, an instance of which is referenced by the ReferenceId attribute. For example usages of the PIB-REFERENCES clause, see Appendix B.
PIB-REFERENCES子句指定PRC，PRC的实例由ReferenceId属性引用。PIB-REFERENCES子句必须出现在具有ReferenceId语法的任何属性中，否则必须不存在。例如，PIB-REFERENCES条款的用法见附录B。
The PIB-TAG clause, which must be present for an attribute which has the SYNTAX TagReferenceId, and must be absent otherwise, is used to indicate that this attribute references a "tag list" of instances of another PRC. Such a tag list (similar in concept to the usage of the same term in [APPL]) is formed by all instances of the other PRC which have the same (tag) value of a particular attribute of that other PRC. The particular attribute of the other PRC, which must have the SYNTAX TagId, is named in the PIB-TAG clause. For an example usage of the PIB-TAG clause, see Appendix B.
PIB-TAG子句必须存在于语法为TagReferenceId的属性中，否则必须不存在，用于指示该属性引用另一PRC实例的“标记列表”。此类标记列表（在概念上类似于[APPL]中相同术语的用法）由其他PRC的所有实例形成，这些实例具有该其他PRC的特定属性的相同（标记）值。另一个PRC的特定属性必须具有语法TagId，在PIB-TAG子句中命名。有关PIB-TAG子句的示例用法，请参见附录B。
The OBJECT-IDENTITY macro is used in PIB modules to define information about an OBJECT IDENTIFIER assignment.
在PIB模块中，OBJECT-IDENTITY宏用于定义有关对象标识符分配的信息。
For conformance purposes, it is useful to define a conformance group as a collection of related PRCs and their attributes. The OBJECT-GROUP macro (directly) defines the collection of attributes which belong to a conformance group. Since each attribute included in the collection belongs to a PRC, the collection of related PRCs which belong to a conformance group is also specified (indirectly) as the set of PRCs to which the included attributes belong.
出于一致性目的，将一致性组定义为相关PRC及其属性的集合非常有用。OBJECT-GROUP宏（直接）定义了属于一致性组的属性集合。由于集合中包含的每个属性都属于PRC，因此属于一致性组的相关PRC集合也被（间接地）指定为所包含属性所属的PRC集合。
The OBJECTS clause, which must be present, is used to specify each attribute contained in the conformance group. Each of the specified attributes must be defined in the same PIB module as the OBJECT-GROUP macro appears.
OBJECTS子句必须存在，用于指定一致性组中包含的每个属性。必须在对象组宏出现时在同一PIB模块中定义每个指定属性。
It is required that every attribute defined in a PIB module be contained in at least one conformance group. This avoids the common error of adding a new attribute to a module and forgetting to add the new attribute to a group.
要求PIB模块中定义的每个属性至少包含在一个一致性组中。这避免了向模块添加新属性而忘记向组添加新属性的常见错误。
The MODULE-COMPLIANCE macro is used to convey a minimum set of requirements with respect to implementation of one or more PIB modules.
MODULE-COMPLIANCE宏用于传达与一个或多个PIB模块实施相关的最低要求集。
A requirement on all "standard" PIB modules is that a corresponding MODULE-COMPLIANCE specification is also defined, either in the same module or in a companion module.
所有“标准”PIB模块的要求是，在同一模块或配套模块中也定义了相应的模块合规性规范。
The MODULE clause, which must be present, is repeatedly used to name each PIB module for which compliance requirements are being specified. Each PIB module is named by its module name, and optionally, by its associated OBJECT IDENTIFIER as well. The module name can be omitted when the MODULE-COMPLIANCE invocation occurs inside a PIB module, to refer to the encompassing PIB module.
模块条款（必须存在）被反复用于命名每个指定合规性要求的PIB模块。每个PIB模块通过其模块名称命名，也可以通过其关联的对象标识符命名。当模块符合性调用发生在PIB模块内部时，可以省略模块名称，以引用包含的PIB模块。
The MANDATORY-GROUPS clause, which need not be present, names the one or more conformance groups within the correspondent PIB module which are unconditionally mandatory for implementation. If an agent claims compliance to the PIB module, then it must implement each and every attribute (and therefore the PRCs to which they belong) within each conformance group listed.
不需要出现的MANDATORY-GROUPS子句指定了相应PIB模块中的一个或多个一致性组，这些一致性组对于实现是无条件强制的。如果代理声称符合PIB模块，那么它必须在列出的每个一致性组中实现每个属性（以及它们所属的PRC）。
The GROUP clause, which need not be present, is repeatedly used to name each conformance group which is conditionally mandatory for compliance to the PIB module. The GROUP clause can also be used to name unconditionally optional groups. A group named in a GROUP clause must be absent from the correspondent MANDATORY-GROUPS clause.
GROUP子句（不需要出现）被反复用于命名每个符合性组，这对于符合PIB模块是有条件的强制性的。GROUP子句还可用于无条件命名可选组。在group子句中命名的组必须不在相应的强制-GROUPS子句中。
Conditionally mandatory groups include those which are mandatory only if a particular protocol is implemented, or only if another group is implemented. A GROUP clause's DESCRIPTION specifies the conditions under which the group is conditionally mandatory.
条件强制组包括仅在实现特定协议或仅在实现另一个组时才强制的组。GROUP子句的说明指定了在哪些条件下该组是有条件强制的。
A group which is named in neither a MANDATORY-GROUPS clause nor a GROUP clause, is unconditionally optional for compliance to the PIB module.
无论是在强制-GROUPS子句还是group子句中都没有命名的组都是符合PIB模块的无条件可选组。
The OBJECT clause, which need not be present, is repeatedly used to specify each attribute for which compliance has a refined requirement with respect to the PIB module definition. The attribute must be present in one of the conformance groups named in the correspondent MANDATORY-GROUPS clause or GROUP clauses.
OBJECT子句（不需要出现）被反复用于指定每个属性，对于这些属性，合规性对PIB模块定义有一个细化的要求。该属性必须存在于相应的MANDATORY-groups子句或GROUP子句中指定的一个一致性组中。
By definition, each attribute specified in an OBJECT clause follows a MODULE clause which names the PIB module in which that attribute is defined. Therefore, the use of an IMPORTS statement, to specify from where such attributes are imported, is redundant and is not required in a PIB module.
根据定义，OBJECT子句中指定的每个属性都跟在MODULE子句之后，MODULE子句命名定义该属性的PIB模块。因此，使用IMPORTS语句来指定这些属性从何处导入是多余的，在PIB模块中不需要。
The SYNTAX clause, which need not be present, is used to provide a refined SYNTAX for the attribute named in the correspondent OBJECT clause. The refined syntax is the minimum level of support needed for this attribute in order to be compliant.
SYNTAX子句（不需要出现）用于为相应的OBJECT子句中命名的属性提供精确的语法。优化的语法是该属性所需的最低支持级别，以符合要求。
The WRITE-SYNTAX clause is not supported by the SPPI.
SPPI不支持WRITE-SYNTAX子句。
The PIB-MIN-ACCESS clause, which need not be present, is used to define the minimal level of access for the attribute named in the correspondent OBJECT clause. If this clause is absent, the minimal level of access is the same as the maximal level specified in the PIB-ACCESS clause of the correspondent invocation of the OBJECT-TYPE macro. If present, this clause must specify a subset of the access specified in the correspondent PIB-ACCESS clause, where: "install" is a subset of "install-notify", "notify" is a subset of "install-notify", and "not- accessible" is a subset of all other values.
PIB-MIN-ACCESS子句（不需要存在）用于定义对应对象子句中命名的属性的最低访问级别。如果缺少此子句，则最小访问级别与对象类型宏的相应调用的PIB-access子句中指定的最大级别相同。如果存在，该条款必须指定相应PIB-access条款中指定的访问子集，其中：“安装”是“安装通知”的子集，“通知”是“安装通知”的子集，“不可访问”是所有其他值的子集。
An implementation is compliant if the level of access it provides is the same or a superset of the minimal level in the MODULE-COMPLIANCE macro and the same or a subset of the maximal level in the PIB-ACCESS clause.
如果实现提供的访问级别与MODULE-COMPLIANCE宏中的最低级别相同或超集，与PIB-access子句中的最高级别相同或是其子集，则实现是符合的。
When designing a PIB module, it is often useful to define new data types similar to those defined in the SPPI. In comparison to a type defined in the SPPI, each of these new types has a different name, a similar syntax, and specific semantics. These newly defined types are termed textual conventions, and are used for the convenience of humans reading the PIB module.
在设计PIB模块时，定义与SPPI中定义的数据类型类似的新数据类型通常很有用。与SPPI中定义的类型相比，每个新类型都有不同的名称、相似的语法和特定的语义。这些新定义的类型称为文本约定，用于方便人们阅读PIB模块。
Attributes defined using a textual convention are always encoded by means of the rules that define their underlying type.
使用文本约定定义的属性总是通过定义其底层类型的规则进行编码。
The TEXTUAL-CONVENTION macro is used to convey the syntax and semantics associated with a textual convention. It should be noted that the expansion of the TEXTUAL-CONVENTION macro is something which conceptually happens during implementation and not during run-time.
text-CONVENTION宏用于传递与文本约定相关的语法和语义。应该注意，文本约定宏的扩展在概念上是在实现过程中发生的，而不是在运行时发生的。
The name of a textual convention must consist of one or more letters or digits, with the initial character being an upper case letter. The name must not conflict with any of the reserved words listed in section 5.2, should not consist of all upper case letters, and shall not exceed 64 characters in length. (However, names longer than 32 characters are not recommended.) The hyphen is not allowed in the name of a textual convention (except for use in information modules
文本约定的名称必须由一个或多个字母或数字组成，首字母为大写字母。名称不得与第5.2节中列出的任何保留字冲突，不得包含所有大写字母，且长度不得超过64个字符。（但是，不建议名称长度超过32个字符。）文本约定的名称中不允许使用连字符（信息模块中使用除外）
converted from SMIv1 which allowed hyphens in ASN.1 type assignments). Further, all names used for the textual conventions defined in all "standard" PIB modules shall be unique.
从SMIv1转换而来，SMIv1允许在ASN.1类型分配中使用连字符）。此外，所有“标准”PIB模块中定义的文本约定使用的所有名称都应是唯一的。
The DISPLAY-HINT clause, which need not be present, gives a hint as to how the value of an instance of an object with the syntax defined using this textual convention might be displayed. The DISPLAY-HINT clause must not be present if the Textual Convention is defined with a syntax of: OBJECT IDENTIFIER, or any enumerated syntax (BITS or INTEGER). The determination of whether it makes sense for other syntax types is dependent on the specific definition of the Textual Convention.
DISPLAY-HINT子句不需要出现，它给出了一个关于如何显示使用此文本约定定义的语法的对象实例的值的提示。如果使用语法：OBJECT IDENTIFIER或任何枚举语法（位或整数）定义文本约定，则DISPLAY-HINT子句不得存在。确定它对其他语法类型是否有意义取决于文本约定的特定定义。
The rules for the format specification of the hint are the same as specified in Section 3.1 of [TC].
提示的格式规范规则与[TC]第3.1节中的规定相同。
The SYNTAX clause, which must be present, defines abstract data structure corresponding to the textual convention. The data structure must be one of the following: a base type (see the SYNTAX clause of an OBJECT-TYPE macro), or the BITS construct. Note that this means that the SYNTAX clause of a Textual Convention can not refer to a previously defined Textual Convention.
必须存在的SYNTAX子句定义了与文本约定相对应的抽象数据结构。数据结构必须是以下之一：基本类型（请参阅对象类型宏的语法子句）或BITS结构。注意，这意味着文本约定的语法子句不能引用以前定义的文本约定。
The SYNTAX clause of a TEXTUAL CONVENTION macro may be sub-typed in the same way as the SYNTAX clause of an OBJECT-TYPE macro.
文本约定宏的语法子句可以采用与对象类型宏的语法子句相同的方式进行子类型化。
PIBs may be revised as implementation experience is gained. However, changes with potential to cause disruption to interoperability between the previous PIB and the revised PIB are not allowed.
随着实施经验的积累，PIB可能会进行修订。但是，不允许有可能导致先前PIB和修订PIB之间互操作性中断的变更。
For any change, the invocation of the MODULE-IDENTITY macro must be updated to include information about the revision: specifically, updating the LAST-UPDATED clause, adding a pair of REVISION and DESCRIPTION clauses, and making any necessary changes to existing clauses, including the ORGANIZATION and CONTACT-INFO clauses.
对于任何更改，必须更新MODULE-IDENTITY宏的调用，以包含有关修订的信息：具体而言，更新LAST-Update子句，添加一对修订和说明子句，并对现有子句（包括组织和联系信息子句）进行任何必要的更改。
Note that any definition contained in an existing PIB is available to be IMPORT-ed by any other PIB, and is referenced in an IMPORTS clause via the PIB module name. Thus, a PIB module name should not be changed. Definitions should not be moved from one PIB to another.
请注意，现有PIB中包含的任何定义都可由任何其他PIB导入，并通过PIB模块名称在IMPORTS子句中引用。因此，不应更改PIB模块名称。不应将定义从一个PIB移动到另一个PIB。
Also note that obsolete definitions must not be removed from PIB modules since their descriptors may still be referenced by other PIB modules, and the OBJECT IDENTIFIERs used to name them must never be re-assigned. The EXTENDS/AUGMENTS clause should be used to extend previous definitions depending on the information to be represented.
还请注意，不能从PIB模块中删除过时的定义，因为其他PIB模块仍可能引用它们的描述符，并且用于命名它们的对象标识符不得重新分配。EXTENDS/AUGMENTS子句应用于根据要表示的信息扩展以前的定义。
Changes to an existing PIB can be made in several ways:
可以通过以下几种方式对现有PIB进行更改：
- Additional PRCs can be added to a PIB or an existing one deprecated.
- 可以将其他PRC添加到PIB或已弃用的现有PRC。
- Attributes can be added to, or deprecated from, an existing PRC. Note that an ASN.1 value of the correct type or an ASN.1 NULL value must be sent even for deprecated attributes to maintain interoperability. New attributes must be added in sequence after the existing ones.
- 属性可以添加到现有PRC中，也可以从现有PRC中弃用。请注意，即使对于不推荐使用的属性，也必须发送正确类型的ASN.1值或ASN.1空值，以保持互操作性。必须在现有属性之后依次添加新属性。
- An existing PRC can be extended or augmented with a new PRC defined in another (perhaps enterprise specific) PIB.
- 现有PRC可以通过另一个（可能是特定于企业的）PIB中定义的新PRC进行扩展或扩充。
Additional named-number enumerations may be added to a SUBJECT-CATEGORIES clause.
可以将其他命名数字枚举添加到SUBJECT-CATEGORIES子句中。
If any non-editorial change is made to any clause of a object assignment, then the OBJECT IDENTIFIER value associated with that object assignment must also be changed, along with its associated descriptor. Note that the max subid for PRC attributes is 127 (See Section 7.1.8)
如果对对象赋值的任何子句进行了任何非编辑性更改，则与该对象赋值关联的对象标识符值及其关联的描述符也必须更改。请注意，PRC属性的最大子ID为127（见第7.1.8节）
An object definition may be revised in any of the following ways:
对象定义可通过以下任一方式进行修改：
- A SYNTAX clause containing an enumerated INTEGER may have new enumerations added or existing labels changed. Similarly, named bits may be added or existing labels changed for the BITS construct.
- 包含枚举整数的语法子句可能会添加新枚举或更改现有标签。类似地，可以为bits构造添加命名位或更改现有标签。
- The value of a SYNTAX clause may be replaced by a textual convention, providing the textual convention is defined to use the same primitive ASN.1 type, has the same set of values, and has identical semantics.
- 语法子句的值可以由文本约定替换，前提是文本约定被定义为使用相同的原语ASN.1类型，具有相同的值集，并且具有相同的语义。
- A UNITS clause may be added.
- 可添加单位条款。
- A STATUS clause value of "current" may be revised as "deprecated" or "obsolete". Similarly, a STATUS clause value of "deprecated" may be revised as "obsolete". When making such a change, the DESCRIPTION clause should be updated to explain the rationale.
- 状态子句值“current”可以修改为“deprecated”或“过时”。同样，状态子句值“不推荐”也可以修改为“过时”。进行此类更改时，应更新描述条款，以解释基本原理。
- Clarifications and additional information may be included in the DESCRIPTION clause.
- 说明条款中可能包含澄清和附加信息。
- An INSTALL-ERRORS clause may be added or an existing INSTALL-ERRORS clause have additional errors defined.
- 可以添加INSTALL-ERRORS子句，或者现有INSTALL-ERRORS子句定义了其他错误。
- A REFERENCE clause may be added or updated.
- 可以添加或更新引用子句。
- A DEFVAL clause may be added or updated.
- 可以添加或更新DEFVAL子句。
- A PRC may be augmented by adding new objects at the end of the row, and making the corresponding update to the SEQUENCE definition.
- PRC可以通过在行的末尾添加新对象并对序列定义进行相应的更新来扩充。
- Entirely new objects may be defined, named with previously unassigned OBJECT IDENTIFIER values.
- 可以定义全新的对象，使用以前未分配的对象标识符值命名。
Otherwise, if the semantics of any previously defined object are changed (i.e., if a non-editorial change is made to any clause other than those specifically allowed above), then the OBJECT IDENTIFIER value associated with that object must also be changed. Note that changing the descriptor associated with an existing object is considered a semantic change, as these strings may be used in an IMPORTS statement.
否则，如果任何先前定义的对象的语义发生了更改（即，如果对任何子句进行了非编辑性更改，而不是上述明确允许的更改），则与该对象关联的对象标识符值也必须更改。请注意，更改与现有对象关联的描述符被视为语义更改，因为这些字符串可能会在IMPORTS语句中使用。
Appendix A: Mapping a PIB to a MIB
附录A：将PIB映射到MIB
Since the SPPI is modelled on the SMI, a PIB can be potentially algorithmically mapped into a MIB. This mapping is achieved by means of the following rules:
由于SPPI是基于SMI建模的，因此PIB可以潜在地通过算法映射到MIB中。此映射通过以下规则实现：
- Modify the module's module name by appending "-MIB" to the name.
- 通过在名称后面附加“-MIB”来修改模块的模块名称。
- Change the OID assigned to the MODULE-IDENTITY to be different value.
- 将分配给模块标识的OID更改为不同的值。
- Replace the keyword PIB-DEFINITIONS with the keyword DEFINITIONS.
- 将关键字PIB-DEFINITIONS替换为关键字定义。
- Modify the module names of all external references to PIB modules by appending "-MIB" to each such module name.
- 通过将“-MIB”附加到每个PIB模块名称，修改所有外部引用的模块名称。
- For each PRC definition, if an INDEX clause is absent, change the "PIB-INDEX" keyword to "INDEX"; otherwise, delete the PIB-INDEX clause.
- 对于每个PRC定义，如果缺少索引子句，则将“PIB-INDEX”关键字更改为“INDEX”；否则，删除PIB-INDEX子句。
- Delete all of the following clauses: PIB-ACCESS, PIB-REFERENCES, PIB-TAG, UNIQUENESS, INSTALL-ERRORS, and SUBJECT-CATEGORIES.
- 删除以下所有子句：PIB-ACCESS、PIB-REFERENCES、PIB-TAG、唯一性、安装错误和主题类别。
- Change all PIB-MIN-ACCESS clauses to MIN-ACCESS clauses, modifying "install" and "install-notify" to "read-create", and "notify" to "read-only".
- 将所有PIB-MIN-ACCESS子句更改为MIN-ACCESS子句，将“安装”和“安装通知”修改为“读取创建”，将“通知”修改为“只读”。
- Add a MAX-ACCESS clause for each OBJECT-TYPE. For each table definition and row definition, the MAX-ACCESS is "not-accessible". For each attribute that is in the INDEX clause, the MAX-ACCESS is "not-accessible". For the remaining attributes, the MAX-ACCESS is "read-create".
- 为每个对象类型添加MAX-ACCESS子句。对于每个表定义和行定义，MAX-ACCESS为“不可访问”。对于INDEX子句中的每个属性，MAX-ACCESS都是“不可访问的”。对于其余属性，MAX-ACCESS为“read-create”。
- Add a columnar attribute of type RowStatus with a descriptor and appropriate DESCRIPTION. The descriptor can be formed by appending the nine characters "RowStatus" to the end of the PRC's descriptor (truncated if necessary to avoid the resulting descriptor being too long). A Subid beyond 127 (i.e., 128 and above) can be used as the OID for this columnar attribute.
- 添加RowStatus类型的列属性，该属性带有描述符和适当的描述。描述符可以通过将九个字符“RowStatus”附加到PRC描述符的末尾来形成（必要时进行截断，以避免生成的描述符过长）。超过127的子ID（即128及以上）可以用作此列属性的OID。
- Modify any SYNTAX clause which has a base data type which is not allowed in the SMI, either to be a valid SMI data type or to omit the OBJECT-TYPE or TEXTUAL-CONVENTION definition and all references to it. Since it is not clear (at this time) which is the best SMI data type to use, the conversion SHOULD provide a configurable option allowing a choice from at least the following:
- 修改任何包含SMI中不允许的基本数据类型的语法子句，使其成为有效的SMI数据类型，或省略对象类型或文本约定定义及其所有引用。由于（目前）尚不清楚哪种SMI数据类型是最佳的SMI数据类型，因此转换应提供一个可配置选项，允许至少从以下选项中进行选择：
- convert to an OCTET STRING of the relevant size. Specifically, this option would map both Integer64 and Unsigned64 to OCTET STRING (SIZE(8)), or
- 转换为相关大小的八位字节字符串。具体来说，此选项将整数64和无符号64映射为八位字节字符串（大小（8）），或
- omit them from the conversion, or
- 将其从转换中忽略，或
- map Integer64 and Unsigned64 to Counter64 (even though this has problems representing negative numbers, and unwanted counter semantics.)
- 将Integer64和Unsigned64映射到Counter64（即使这在表示负数和不需要的计数器语义方面存在问题。）
Appendix B: Example usage of PIB-REFERENCES and PIB-TAG clauses
附录B：PIB-REFERENCES和PIB-TAG条款的示例用法
The following example demonstrates the use of the PIB-REFERENCES and PIB-TAG clauses.
下面的示例演示了PIB-REFERENCES和PIB-TAG子句的使用。
In this example, the PIB-REFERENCES clause is used by the qosIfDscpMapQueue attribute to indicate the PRC of which it references an instance, and similarly, by the qosIfDscpMapThresh attribute.
在本例中，qosIfDscpMapQueue属性使用PIB-REFERENCES子句来指示引用实例的PRC，类似地，qosIfDscpMapThresh属性也使用PIB-REFERENCES子句。
The qosIfDscpMapTable PRC has an instance for each DSCP of a particular "map", but there is no PRC defined for a map itself; rather, a map consists of all instances of qosIfDscpMapTable which have the same value of qosIfDscpMapMapId. That is, a tag list is formed by all instances of qosIfDscpMapTable which have the same value of qosIfDscpMapMapId. This tag list is referenced by the attribute qosIfDscpAssignDscpMap, and its use of the PIB-TAG clause indicates this.
qosIfDscpMapTable PRC对于特定“地图”的每个DSCP都有一个实例，但没有为地图本身定义PRC；相反，映射由QosifdsCmpapTable的所有实例组成，这些实例具有相同的QosifdsCmpapMapId值。也就是说，标记列表由具有相同QOSIFDSCPMAPID值的qosIfDscpMapTable的所有实例组成。该标记列表由属性qosIfDscpAssignDscpMap引用，它对PIB-tag子句的使用表明了这一点。
qosIfDscpAssignTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfDscpAssignEntry
PIB-ACCESS install
STATUS current
DESCRIPTION " "
::= { qosIfParameters 9 }
qosIfDscpAssignTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfDscpAssignEntry
PIB-ACCESS install
STATUS current
DESCRIPTION " "
::= { qosIfParameters 9 }
qosIfDscpAssignEntry OBJECT-TYPE
SYNTAX QosIfDscpAssignEntry
STATUS current
DESCRIPTION
"An instance of the qosIfDscpAssign class."
PIB-INDEX { qosIfDscpAssignPrid }
UNIQUENESS { qosIfDscpAssignName, qosIfDscpAssignRoles }
::= { qosIfDscpAssignTable 1 }
qosIfDscpAssignEntry OBJECT-TYPE
SYNTAX QosIfDscpAssignEntry
STATUS current
DESCRIPTION
"An instance of the qosIfDscpAssign class."
PIB-INDEX { qosIfDscpAssignPrid }
UNIQUENESS { qosIfDscpAssignName, qosIfDscpAssignRoles }
::= { qosIfDscpAssignTable 1 }
QosIfDscpAssignEntry ::= SEQUENCE {
qosIfDscpAssignPrid InstanceId,
qosIfDscpAssignName SnmpAdminString,
QosIfDscpAssignEntry ::= SEQUENCE {
qosIfDscpAssignPrid InstanceId,
qosIfDscpAssignName SnmpAdminString,
qosIfDscpAssignRoles RoleCombination, qosIfDscpAssignDscpMap TagReferenceId }
qosIfDscpAssignRoles角色组合，qosIfDscpAssignDscpMap TagReferenceId}
qosIfDscpAssignDscpMap OBJECT-TYPE
SYNTAX TagReferenceId
PIB-TAG { qosIfDscpMapMapId } -- attribute defined below
STATUS current
DESCRIPTION
"The DSCP map which is applied to interfaces of type
qosIfDscpAssignName which have a role combination of
qosIfDscpAssignRoles."
::= { qosIfDscpAssignEntry 3 }
qosIfDscpAssignDscpMap OBJECT-TYPE
SYNTAX TagReferenceId
PIB-TAG { qosIfDscpMapMapId } -- attribute defined below
STATUS current
DESCRIPTION
"The DSCP map which is applied to interfaces of type
qosIfDscpAssignName which have a role combination of
qosIfDscpAssignRoles."
::= { qosIfDscpAssignEntry 3 }
-- -- DSCP to Queue and Threshold Mapping Table --
----DSCP到队列和阈值映射表--
qosIfDscpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfDscpMapEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"Assigns DSCP values to queues and thresholds for an arbitrary
DSCP map. This map can then be assigned to various interface
and role combination pairs."
::= { qosIfParameters 10 }
qosIfDscpMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF QosIfDscpMapEntry
PIB-ACCESS install
STATUS current
DESCRIPTION
"Assigns DSCP values to queues and thresholds for an arbitrary
DSCP map. This map can then be assigned to various interface
and role combination pairs."
::= { qosIfParameters 10 }
qosIfDscpMapEntry OBJECT-TYPE
SYNTAX QosIfDscpMapEntry
STATUS current
DESCRIPTION
"An instance of the qosIfDscpMap class."
PIB-INDEX { qosIfDscpMapPrid }
UNIQUENESS { qosIfDscpMapMapId, qosIfDscpMapDscp }
::= { qosIfDscpMapTable 1 }
qosIfDscpMapEntry OBJECT-TYPE
SYNTAX QosIfDscpMapEntry
STATUS current
DESCRIPTION
"An instance of the qosIfDscpMap class."
PIB-INDEX { qosIfDscpMapPrid }
UNIQUENESS { qosIfDscpMapMapId, qosIfDscpMapDscp }
::= { qosIfDscpMapTable 1 }
QosIfDscpMapEntry ::= SEQUENCE {
qosIfDscpMapPrid InstanceId,
qosIfDscpMapMapId TagId,
qosIfDscpMapDscp Dscp,
qosIfDscpMapQueue ReferenceId,
qosIfDscpMapThresh ReferenceId
}
QosIfDscpMapEntry ::= SEQUENCE {
qosIfDscpMapPrid InstanceId,
qosIfDscpMapMapId TagId,
qosIfDscpMapDscp Dscp,
qosIfDscpMapQueue ReferenceId,
qosIfDscpMapThresh ReferenceId
}
qosIfDscpMapMapId OBJECT-TYPE SYNTAX TagId STATUS current
QOSIFDSCPMAPID对象类型语法标记ID状态当前
DESCRIPTION
"An integer that identifies the DSCP map to which this PRI
belongs."
::= { qosIfDscpMapEntry 2 }
DESCRIPTION
"An integer that identifies the DSCP map to which this PRI
belongs."
::= { qosIfDscpMapEntry 2 }
qosIfDscpMapQueue OBJECT-TYPE
SYNTAX ReferenceId
PIB-REFERENCES { qosIfQueueEntry }
STATUS current
DESCRIPTION
"This attribute maps the DSCP specified by qosIfDscpMapDscp to
the queue identified by qosIfQueuePrid in qosIfQueueTable.
For a given DSCP map, all the queues must belong to a single
queue set."
::= { qosIfDscpMapEntry 4 }
qosIfDscpMapQueue OBJECT-TYPE
SYNTAX ReferenceId
PIB-REFERENCES { qosIfQueueEntry }
STATUS current
DESCRIPTION
"This attribute maps the DSCP specified by qosIfDscpMapDscp to
the queue identified by qosIfQueuePrid in qosIfQueueTable.
For a given DSCP map, all the queues must belong to a single
queue set."
::= { qosIfDscpMapEntry 4 }
qosIfDscpMapThresh OBJECT-TYPE
SYNTAX ReferenceId
PIB-REFERENCES { qosIfThresholdEntry }
STATUS current
DESCRIPTION
"This attribute maps the DSCP specified by qosIfDscpMapDscp to
the threshold identified by qosIfThresholdId in
qosIfThresholdTable. The threshold set to which this
threshold belongs must be assigned to the queue specified by
qosIfDscpMapQueue."
::= { qosIfDscpMapEntry 5 }
qosIfDscpMapThresh OBJECT-TYPE
SYNTAX ReferenceId
PIB-REFERENCES { qosIfThresholdEntry }
STATUS current
DESCRIPTION
"This attribute maps the DSCP specified by qosIfDscpMapDscp to
the threshold identified by qosIfThresholdId in
qosIfThresholdTable. The threshold set to which this
threshold belongs must be assigned to the queue specified by
qosIfDscpMapQueue."
::= { qosIfDscpMapEntry 5 }
Security Considerations
安全考虑
This document defines a language with which to define provisioning information. The language itself has no security impact on the Internet.
本文档定义了一种用于定义配置信息的语言。这种语言本身对互联网没有安全影响。
IANA Considerations
IANA考虑
The root of the subtree administered by the Internet Assigned Numbers Authority (IANA) for the Internet is:
互联网分配号码管理局（IANA）为互联网管理的子树根为：
internet OBJECT IDENTIFIER ::= { iso 3 6 1 }
internet OBJECT IDENTIFIER ::= { iso 3 6 1 }
That is, the Internet subtree of OBJECT IDENTIFIERs starts with the prefix:
也就是说，对象标识符的Internet子树以前缀开头：
1.3.6.1.
1.3.6.1.
Several branches underneath this subtree are used for network management:
此子树下的几个分支用于网络管理：
mgmt OBJECT IDENTIFIER ::= { internet 2 }
experimental OBJECT IDENTIFIER ::= { internet 3 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
mgmt OBJECT IDENTIFIER ::= { internet 2 }
experimental OBJECT IDENTIFIER ::= { internet 3 }
private OBJECT IDENTIFIER ::= { internet 4 }
enterprises OBJECT IDENTIFIER ::= { private 1 }
The mgmt(2) subtree is used to identify "standard" objects.
mgmt（2）子树用于识别“标准”对象。
This document defines
本文件定义了
pib OBJECT IDENTIFIER ::= { mgmt 2 }
pib OBJECT IDENTIFIER ::= { mgmt 2 }
as the root for PIBs defined to be carried over [COPS-PR]. This Object Identifier is a high level assignment that needs to be registered with [IANA]. Root Object Identifiers for future "standards track" PIBs will also need to be registered and MUST use Object Identifiers below this oid. A standards track PIB can only be assigned an OID by IANA if the PIB is approved by the IESG as a "standards track" document. Experimental and enterprise PIBs MUST be defined under the "experimental" and "enterprises" Object Identifiers respectively.
作为定义为结转的PIB的根[COPS-PR]。此对象标识符是需要向[IANA]注册的高级分配。未来“标准跟踪”PIB的根对象标识符也需要注册，并且必须使用此oid下的对象标识符。如果PIB被IESG批准为“标准跟踪”文件，IANA只能为标准跟踪PIB分配OID。实验和企业PIB必须分别在“实验”和“企业”对象标识符下定义。
The PIB module "copsPrSppiTc" is defined in this document as a standard module and hence, needs a subid assignment under the "pib" oid from IANA.
PIB模块“COPSPRPPITC”在本文件中定义为标准模块，因此需要在IANA的“PIB”oid下分配子ID。
SPPI SUBJECT-CATEGORIES are mapped to COPS Client Types. IANA Considerations for SUBJECT-CATEGORIES follow the same requirements as specified in [COPS] IANA Considerations for COPS Client Types. Thus, a new PIB can define a new COPS Client Type in the "standards", "experimental" or "enterprise" space, and when approved that would mean that a new COPS Client Type gets assigned. IANA must update the registry for COPS Client Types (where applicable as described in [COPS] IANA Considerations) as a result.
SPPI主题类别映射到COPS客户端类型。主题类别的IANA注意事项遵循[COPS]IANA注意事项中针对COPS客户端类型规定的相同要求。因此，一个新的PIB可以在“标准”、“实验”或“企业”空间中定义一个新的COPS客户机类型，当获得批准时，这意味着将分配一个新的COPS客户机类型。因此，IANA必须更新COPS客户端类型的注册表（如适用，如[COPS]IANA注意事项中所述）。
Authors' Addresses
作者地址
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA
Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134-1706
Phone: +1 408 526 5260
Email: kzm@cisco.com
Phone: +1 408 526 5260
Email: kzm@cisco.com
Michael Fine Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA
美国加利福尼亚州圣何塞西塔斯曼大道170号，思科系统有限公司，邮编95134-1706
Phone: +1 408 527 8218
EMail: mfine@cisco.com
Phone: +1 408 527 8218
EMail: mfine@cisco.com
John Seligson Nortel Networks, Inc. 4401 Great America Parkway Santa Clara, CA 95054 USA
John Seligson Nortel Networks，Inc.美国加利福尼亚州圣克拉拉大美洲大道4401号，邮编95054
Phone: +1 408 495 2992
EMail: jseligso@nortelnetworks.com
Phone: +1 408 495 2992
EMail: jseligso@nortelnetworks.com
Kwok Ho Chan Nortel Networks, Inc. 600 Technology Park Drive Billerica, MA 01821 USA
郭浩灿北电网络有限公司，美国马萨诸塞州比尔里卡科技园大道600号，邮编01821
Phone: +1 978 288 8175
EMail: khchan@nortelnetworks.com
Phone: +1 978 288 8175
EMail: khchan@nortelnetworks.com
Scott Hahn Intel 2111 NE 25th Avenue Hillsboro, OR 97124 USA
斯科特哈恩英特尔2111东北25大道希尔斯伯勒，或97124美国
Phone: +1 503 264 8231
EMail: scott.hahn@intel.com
Phone: +1 503 264 8231
EMail: scott.hahn@intel.com
Ravi Sahita Intel 2111 NE 25th Avenue Hillsboro, OR 97124 USA
拉维萨希塔英特尔2111东北25大道希尔斯伯勒，或97124美国
Phone: +1 503 712 1554
EMail: ravi.sahita@intel.com
Phone: +1 503 712 1554
EMail: ravi.sahita@intel.com
Andrew Smith Allegro Networks 6399 San Ignacio Ave. San Jose, CA 95119 USA
安德鲁·史密斯快板网络美国加利福尼亚州圣何塞圣伊格纳西奥大道6399号，邮编95119
Fax: +1 415 345 1827
EMail: andrew@allegronetworks.com
Fax: +1 415 345 1827
EMail: andrew@allegronetworks.com
Francis Reichmeyer PFN Inc. University Park at MIT 26 Landsdowne Street Cambridge, MA 02139 USA
Francis Reichmeyer PFN Inc.美国马萨诸塞州剑桥兰德斯敦街26号麻省理工学院大学公园，邮编：02139
Phone: +1 617 494 9980
EMail: franr@pfn.com
Phone: +1 617 494 9980
EMail: franr@pfn.com
References
工具书类
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and A. Sastry, "The COPS (Common Open Policy Service) Protocol", RFC 2748, January 2000.
[COPS]Boyle，J.，Cohen，R.，Durham，D.，Herzog，S.，Rajan，R.和A.Sastry，“COPS（公共开放政策服务）协议”，RFC 2748，2000年1月。
[COPS-RSVP] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R. and A. Sastry, " COPS usage for RSVP", RFC 2749, January 2000.
[COPS-RSVP]Boyle，J.，Cohen，R.，Durham，D.，Herzog，S.，Rajan，R.和A.Sastry，“RSVP的COPS用法”，RFC 2749，2000年1月。
[COPS-PR] Reichmeyer, F., Herzog, S., Chan, K., Durham, D., Yavatkar, R., Gai, S., McCloghrie, K. and A. Smith, "COPS Usage for Policy Provisioning", RFC 3084, March 2001.
[COPS-PR]Reichmeyer，F.，Herzog，S.，Chan，K.，Durham，D.，Yavatkar，R.，Gai，S.，McCloghrie，K.和A.Smith，“政策制定的COPS使用”，RFC 3084，2001年3月。
[SMI] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[SMI]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[TC] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[TC]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[CONF] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[CONF]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[APPL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[APPL]Levi，D.，Meyer，P.和B.Stewart，“SNMP应用”，RFC 25731999年4月。
[ASN1] Information processing systems -- Open Systems Interconnection -- Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, December 1987.
[ASN1]信息处理系统——开放系统互连——抽象语法符号1规范（ASN.1），国际标准化组织。国际标准88241987年12月。
[INETADDR] Daniele, M., Haberman, B., Routhier, S. and J. Schoenwaelder "Textual Conventions for Internet Network Addresses", RFC 2851, June 2000.
[INETADDR]Daniele，M.，Haberman，B.，Routhier，S.和J.Schoenwaeld“互联网网络地址的文本约定”，RFC 28512000年6月。
[IANA] http://www.isi.edu/in-notes/iana/assignments/smi-numbers
[IANA] http://www.isi.edu/in-notes/iana/assignments/smi-numbers
[IANA-CONSIDERATIONS] Alvestrand, H. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[IANA注意事项]Alvestrand，H.和T.Narten，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。