Network Working Group B. Clouston, Ed.
Request for Comments: 2584 Cisco Systems
Category: Standards Track B. Moore, Ed.
IBM Corporation
May 1999
Network Working Group B. Clouston, Ed.
Request for Comments: 2584 Cisco Systems
Category: Standards Track B. Moore, Ed.
IBM Corporation
May 1999
Definitions of Managed Objects for APPN/HPR in IP Networks
IP网络中APPN/HPR的托管对象定义
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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling HPR (High Performance Routing) network devices which have the capability to communicate in IP (Internet Protocol) networks. This memo identifies managed objects for the HPR in IP network communications.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于监视和控制能够在IP（互联网协议）网络中通信的HPR（高性能路由）网络设备的对象。此备忘录标识IP网络通信中HPR的托管对象。
Table of Contents
目录
1. Introduction ........................................... 2
2. The SNMP Network Management Framework .................. 2
3. Overview ............................................... 3
3.1 HPR/IP Values for Objects in the APPN MIB ............. 3
3.2 APPN/HPR in IP Networks MIB structure ................. 4
3.2.1 hprIpMonitoringGroup ................................ 5
3.2.2 hprIpConfigurationGroup ............................. 5
4. Definitions ............................................ 6
5. Security Considerations ................................ 16
6. Intellectual Property .................................. 17
7. Acknowledgments ........................................ 18
8. References ............................................. 18
9. Authors' Addresses ..................................... 20
10. Full Copyright Statement ............................... 21
1. Introduction ........................................... 2
2. The SNMP Network Management Framework .................. 2
3. Overview ............................................... 3
3.1 HPR/IP Values for Objects in the APPN MIB ............. 3
3.2 APPN/HPR in IP Networks MIB structure ................. 4
3.2.1 hprIpMonitoringGroup ................................ 5
3.2.2 hprIpConfigurationGroup ............................. 5
4. Definitions ............................................ 6
5. Security Considerations ................................ 16
6. Intellectual Property .................................. 17
7. Acknowledgments ........................................ 18
8. References ............................................. 18
9. Authors' Addresses ..................................... 20
10. Full Copyright Statement ............................... 21
This document is a product of the SNA NAU Services MIB Working Group. It defines a MIB module for managing devices with HPR in IP networks capabilities.
本文件是SNA NAU服务MIB工作组的产品。它定义了一个MIB模块，用于管理具有HPR in IP网络功能的设备。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [17].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[17]中所述进行解释。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2271 [1].
o RFC 2271[1]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2478 [5], RFC 2579 [6] and RFC 2580 [7].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2478[5]、RFC 2579[6]和RFC 2580[7]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2272[11]和RFC 2274[12]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2273 [14] and the view-based access control mechanism described in RFC 2275 [15].
o RFC 2273[14]中描述的一组基本应用程序和RFC 2275[15]中描述的基于视图的访问控制机制。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
This document identifies a set of objects for monitoring the configuration and active characteristics of devices with HPR in IP network capabilities. HPR is an enhancement to the Advanced Peer-to-Peer Network (APPN) architecture that provides fast data routing and improved session reliability. APPN is the aspect of Systems Network Architecture (SNA) that supports peer-to-peer networking. APPN/HPR in IP Networks is a further enhancement to the APPN/HPR architecture, described in RFC 2353 [18]. It provides a method with which APPN/HPR nodes can communicate in IP networks.
本文档确定了一组对象，用于监控具有HPR in IP网络功能的设备的配置和活动特性。HPR是对高级对等网络（APPN）体系结构的增强，它提供了快速的数据路由和改进的会话可靠性。APPN是支持对等网络的系统网络体系结构（SNA）的一个方面。IP网络中的APPN/HPR是对APPN/HPR体系结构的进一步增强，如RFC 2353[18]所述。它提供了一种APPN/HPR节点在IP网络中通信的方法。
APPN management information is defined by the APPN MIB [19]. HPR management information is defined by the HPR MIB, RFC 2238 [20].
APPN管理信息由APPN MIB定义[19]。HPR管理信息由HPR MIB RFC 2238定义[20]。
Highlights of the management functions supported by the APPN/HPR in IP Networks MIB module include the following:
IP网络MIB模块中的APPN/HPR支持的管理功能要点包括：
o A count of UDP packets sent with each type of APPN traffic on HPR/IP links.
o 与HPR/IP链路上的每种类型的APPN通信一起发送的UDP数据包计数。
o Monitoring and setting configuration parameters for the mappings between APPN traffic types on Type of Service (TOS) Precedence settings in the IP header. Note that the TOS Precedence settings have been redefined in RFC 2474 [21] as the first three bits of the differentiated services code point (DSCP).
o 监视和设置IP标头中服务类型（TOS）优先级设置上的APPN流量类型之间的映射的配置参数。注意，在RFC 2474[21]中，TOS优先设置已被重新定义为区分服务代码点（DSCP）的前三位。
This MIB module does not support:
此MIB模块不支持：
o Configuration of IP addresses used for APPN ports or link stations.
o 用于APPN端口或链路站的IP地址配置。
Ports and link stations are the APPN device's interface to the data link control (DLC), which provides the physical transport, or to another protocol, such as IP. The APPN MIB identifies ports and link stations using IP as the transport with the following objects:
端口和链路站是APPN设备与提供物理传输的数据链路控制（DLC）或其他协议（如IP）的接口。APPN MIB识别使用IP作为传输的端口和链路站，并具有以下对象：
o appnPortDlcType
o appnPortDlcType
o appnLsDlcType
o appnLsDlcType
o appnLsStatusDlcType
o appnLsStatusDlcType
These objects all have the syntax IANAifType, and the value 126, defined as "IP (for APPN HPR in IP networks)" shall be returned when they identify an HPR/IP port or link station.
这些对象都具有语法IANAifType，当它们标识HPR/IP端口或链路站时，应返回定义为“IP（用于IP网络中的APPN HPR）”的值126。
The IP address used for the port or link station is returned in the following objects:
用于端口或链接站的IP地址在以下对象中返回：
o appnPortDlcLocalAddr
o appnPortDlcLocalAddr
o appnLsLocalAddr
o appnLsLocalAddr
o appnLsRemoteAddr
o appnLsRemoteAddr
o appnLsStatusLocalAddr
o appnLsStatusLocalAddr
o appnLsStatusRemoteAddr
o appnLsStatusRemoteAddr
These objects have the syntax DisplayableDlcAddress, defined in the APPN MIB as a textual convention to represent the address as an octet string of ASCII characters.
这些对象的语法为DisplayableDlcAddress，在APPN MIB中定义为文本约定，将地址表示为ASCII字符的八位字节字符串。
The following two objects return object identifiers that tie port and link table entries in the APPN MIB to lower-layer MIB entries:
以下两个对象返回将APPN MIB中的端口和链接表项与较低层MIB项联系起来的对象标识符：
o appnPortSpecific
o appnPortSpecific
o appnLsSpecific
o appnLsSpecific
Both objects should return a RowPointer to the ifEntry in the agent's ifTable for the physical interface associated with the local IP address for the port. If the agent implements the IP-MIB (RFC 2011), this association between the IP address and the physical interface will be represented in the ipNetToMediaTable.
这两个对象都应该为与端口的本地IP地址关联的物理接口返回一个指向代理ifTable中ifEntry的行指针。如果代理实现IP-MIB（RFC 2011），IP地址和物理接口之间的这种关联将在ipNetToMediaTable中表示。
The APPN/HPR in IP Networks MIB module contains two groups of objects:
IP网络MIB模块中的APPN/HPR包含两组对象：
o hprIpMonitoringGroup - an object for counting outgoing HPR/IP traffic for each APPN traffic type
o hprIpMonitoringGroup—用于计算每种APPN流量类型的传出HPR/IP流量的对象
o hprIpConfigurationGroup - objects to represent TOS Precedence to APPN traffic type mappings
o hprIpConfigurationGroup-表示TOS优先于APPN流量类型映射的对象
These groups are described below in more detail.
下面将更详细地描述这些组。
The hprIpMonitoringGroup group consists of the hprIpActiveLsTable. This table is indexed by the link station name and traffic type, and contains a counter for the number of UDP packets sent on a link station for that traffic type.
hprIpMonitoringGroup组由HPRIPActivelTable组成。此表按链路站名称和通信量类型编制索引，并包含一个计数器，用于该通信量类型在链路站上发送的UDP数据包数。
The hprIpMonitoringGroup group consists of the following objects and tables:
hprIpMonitoringGroup由以下对象和表组成：
1) hprIpAppnPortTable
1) hprIpAppnPortTable
This table supports reading and setting the default mapping between APPN traffic types and TOS Precedence settings for all link stations using a port. This mapping may be overridden for individual link stations or individual connection networks.
此表支持读取和设置使用端口的所有链路站的APPN通信量类型和TOS优先级设置之间的默认映射。对于单个链路站或单个连接网络，可以覆盖此映射。
2) hprIpLsTable
2) hprIpLsTable
This table supports reading and setting the mappings between APPN traffic types and TOS Precedence settings for an individual link station and APPN traffic type. If there is no entry in this table for a given link station and traffic type, then that link station inherits its mapping from its port.
此表支持读取和设置单个链路站和APPN流量类型的APPN流量类型和TOS优先级设置之间的映射。如果此表中没有给定链路站和通信量类型的条目，则该链路站将从其端口继承其映射。
3) hprIpCnTable
3) hprIpCnTable
This table supports reading and setting the mapping between APPN traffic types and TOS Precedence settings for an individual connection network and traffic type. If there is no entry in this table for a given connection network and traffic type, then that connection network inherits its mapping from its port.
此表支持读取和设置单个连接网络和流量类型的APPN流量类型和TOS优先级设置之间的映射。如果此表中没有给定连接网络和流量类型的条目，则该连接网络将从其端口继承其映射。
HPR-IP-MIB DEFINITIONS ::= BEGIN
HPR-IP-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY,OBJECT-TYPE, Counter32 FROM SNMPv2-SMI DisplayString, RowStatus, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnaControlPointName FROM APPN-MIB hprObjects, hprCompliances, hprGroups FROM HPR-MIB ;
从SNMPv2 SMI DisplayString导入模块标识、对象类型、计数器32、从SNMPv2导入行状态、从SNMPv2导入文本约定、从SNMPv2 CONF导入对象组、从APPN-MIB导入SnaControlPointName、从HPR-MIB导入HPR组；
hprIp MODULE-IDENTITY LAST-UPDATED "9809240000Z" -- September 24, 1998 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG" CONTACT-INFO " Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA Tel: 1 919 472 2333 E-mail: clouston@cisco.com
hprIp模块标识最后一次更新“980924000Z”-1998年9月24日组织“IETF SNA NAU MIB WG/AIW APPN MIBs SIG”联系信息“Bob Clouston Cisco Systems 7025 Kit Creek Road邮政信箱14987美国北卡罗来纳州三角研究园27709电话：1919 472 2333电子邮件：clouston@cisco.com
Bob Moore IBM Corporation 4205 S. Miami Boulevard BRQA/501 P.O. Box 12195 Research Triangle Park, NC 27709, USA Tel: 1 919 254 4436 E-mail: remoore@us.ibm.com " DESCRIPTION "The MIB module for HPR over IP. This module contains two groups:
Bob Moore IBM Corporation 4205 S.Miami Boulevard BRQA/501邮政信箱12195美国北卡罗来纳州三角研究公园27709电话：1919 254 4436电子邮件：remoore@us.ibm.com“描述”用于HPR over IP的MIB模块。本模块包含两个组：
- the HPR over IP Monitoring Group provides a count of the UDP packets sent by a link station for each APPN traffic type.
- HPR over IP监视组为每个APPN流量类型提供链路站发送的UDP数据包计数。
- the HPR over IP Configuration Group provides for reading and setting the mappings between APPN traffic types and TOS Precedence settings in the IP header. These mappings are
- HPR over IP配置组用于读取和设置IP标头中APPN流量类型和TOS优先级设置之间的映射。这些映射是
configured at the APPN port level, and are inherited by the APPN connection networks and link stations associated with an APPN port. A port-level mapping can, however, be overridden for a particular connection network or link station." REVISION "9809240000Z" -- September 24, 1998 DESCRIPTION "Initial version, Published as RFC 2584"
在APPN端口级别配置，并由与APPN端口关联的APPN连接网络和链接站继承。但是，可以为特定连接网络或链路站覆盖端口级映射。“修订版”980924000Z--1998年9月24日描述“初始版本，发布为RFC 2584”
::= { hprObjects 5 }
::= { hprObjects 5 }
-- *********************************************************************
-- Textual Conventions
-- *********************************************************************
AppnTrafficType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"APPN traffic type. The first four values correspond
to APPN transmission priorities (network, high, medium and
low), while the fifth is used for both LLC commands (XID,
TEST, DISC, and DM) and function-routed NLPs (XID_DONE_RQ
and XID_DONE_RSP)."
-- *********************************************************************
-- Textual Conventions
-- *********************************************************************
AppnTrafficType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"APPN traffic type. The first four values correspond
to APPN transmission priorities (network, high, medium and
low), while the fifth is used for both LLC commands (XID,
TEST, DISC, and DM) and function-routed NLPs (XID_DONE_RQ
and XID_DONE_RSP)."
SYNTAX INTEGER { low (1), medium (2), high (3), network (4), llcAndFnRoutedNlp (5) }
语法整数{low（1）、medium（2）、high（3）、network（4）、llcAndFnRoutedNlp（5）}
AppnTOSPrecedence ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A DisplayString representing the setting of the three TOS
Precedence bits in the IP Type of Service field for this APPN
traffic type. The HPR over IP architecture specifies the
following default mapping:
AppnTOSPrecedence ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A DisplayString representing the setting of the three TOS
Precedence bits in the IP Type of Service field for this APPN
traffic type. The HPR over IP architecture specifies the
following default mapping:
APPN traffic type IP TOS Precedence bits
------------------ ----------------------
Network 110
High 100
Medium 010
Low 001
LLC commands, etc. 110
"
APPN traffic type IP TOS Precedence bits
------------------ ----------------------
Network 110
High 100
Medium 010
Low 001
LLC commands, etc. 110
"
SYNTAX DisplayString (SIZE(3))
语法显示字符串（大小（3））
-- *******************************************************************
-- *******************************************************************
-- hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 }
-- *******************************************************************
-- hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 }
-- *******************************************************************
-- *******************************************************************
-- HPR over IP Monitoring Group
--
-- This group contains a single table, the hprIsActiveLsTable,
-- providing a count of UDP packets sent with each type of
-- APPN traffic on each active link supporting HPR over IP.
-- *******************************************************************
hprIpActiveLsTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpActiveLsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP active link station table. This table provides
counts of the number of UDP packets sent for each APPN
traffic type."
-- *******************************************************************
-- HPR over IP Monitoring Group
--
-- This group contains a single table, the hprIsActiveLsTable,
-- providing a count of UDP packets sent with each type of
-- APPN traffic on each active link supporting HPR over IP.
-- *******************************************************************
hprIpActiveLsTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpActiveLsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP active link station table. This table provides
counts of the number of UDP packets sent for each APPN
traffic type."
::= { hprIp 1 }
::= { hprIp 1 }
hprIpActiveLsEntry OBJECT-TYPE SYNTAX HprIpActiveLsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry of the HPR/IP link station table."
hprIpActiveLsEntry对象类型语法hprIpActiveLsEntry MAX-ACCESS不可访问状态当前描述“HPR/IP链路站表的条目”
INDEX { hprIpActiveLsLsName, hprIpActiveLsAppnTrafficType }
索引{hprIpActiveLsLsName，hprIpActiveLsAppnTrafficType}
::= { hprIpActiveLsTable 1 }
::= { hprIpActiveLsTable 1 }
HprIpActiveLsEntry ::= SEQUENCE {
hprIpActiveLsLsName DisplayString,
hprIpActiveLsAppnTrafficType AppnTrafficType,
hprIpActiveLsUdpPackets Counter32 }
HprIpActiveLsEntry ::= SEQUENCE {
hprIpActiveLsLsName DisplayString,
hprIpActiveLsAppnTrafficType AppnTrafficType,
hprIpActiveLsUdpPackets Counter32 }
hprIpActiveLsLsName OBJECT-TYPE SYNTAX DisplayString (SIZE (1..10)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Administratively assigned name for the link station. If this object has the same value as the appnLsName in the APPN MIB, then the two objects are referring to the same APPN link station."
hprIpActiveLsLsName对象类型语法DisplayString（大小（1..10））MAX-ACCESS不可访问状态当前描述“链接站的管理分配名称。如果此对象与APPN MIB中的appnLsName具有相同的值，则这两个对象引用的是同一APPN链接站。”
::= { hprIpActiveLsEntry 1 }
::= { hprIpActiveLsEntry 1 }
hprIpActiveLsAppnTrafficType OBJECT-TYPE SYNTAX AppnTrafficType MAX-ACCESS not-accessible STATUS current DESCRIPTION "APPN traffic type being sent through the link station."
hprIpActiveLsAppnTrafficType对象类型语法AppnTrafficType MAX-ACCESS不可访问状态当前描述“正在通过链接站发送的APPN流量类型。”
::= { hprIpActiveLsEntry 2 }
::= { hprIpActiveLsEntry 2 }
hprIpActiveLsUdpPackets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of outgoing UDP packets carrying this type of APPN traffic. A discontinuity in the counter is indicated by the appnLsCounterDisconTime object in the APPN MIB."
hprIpActiveLsUdpPackets对象类型语法计数器32 MAX-ACCESS只读状态当前描述“承载此类型APPN通信的传出UDP数据包的计数。计数器中的不连续由APPN MIB中的APPNLSOUnterDiscontraction对象指示。”
::= { hprIpActiveLsEntry 3 }
::= { hprIpActiveLsEntry 3 }
-- *******************************************************************
-- HPR over IP Configuration Group
--
-- This group contains three tables for reading and setting the
-- mapping between APPN traffic types and values for the TOS
-- Precedence bits in the IP header. hprIpAppnPortTOSPrecedence
-- represents the APPN port-level mapping. This mapping can be
-- overridden for an individual link station or an individual
-- connection network via, respectively, the hprIpLsTOSPrecedence
-- and the hprIpCnTOSPrecedence objects.
-- *******************************************************************
-- *******************************************************************
-- HPR over IP Configuration Group
--
-- This group contains three tables for reading and setting the
-- mapping between APPN traffic types and values for the TOS
-- Precedence bits in the IP header. hprIpAppnPortTOSPrecedence
-- represents the APPN port-level mapping. This mapping can be
-- overridden for an individual link station or an individual
-- connection network via, respectively, the hprIpLsTOSPrecedence
-- and the hprIpCnTOSPrecedence objects.
-- *******************************************************************
hprIpAppnPortTable OBJECT-TYPE SYNTAX SEQUENCE OF HprIpAppnPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The HPR/IP APPN port table. This table supports reading and setting the mapping between APPN traffic types and TOS Precedence settings for all the link stations at this APPN port. This mapping can be overridden for an individual link station or an individual connection network via, respectively, the hprIpLsTOSPrecedence and the hprIpCnTOSPrecedence objects."
hprIpAppnPortTable HprIpAppnPortEntry MAX-ACCESS的对象类型语法序列不可访问状态当前描述“HPR/IP APPN端口表。此表支持读取和设置此APPN端口上所有链路站的APPN流量类型和TOS优先级设置之间的映射。此映射可分别通过HPRIPStopRecessence和HPRIPCntospRecessence对象覆盖单个链路站或单个连接网络。”
::= { hprIp 2 }
::= { hprIp 2 }
hprIpAppnPortEntry OBJECT-TYPE SYNTAX HprIpAppnPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry of the HPR/IP APPN port table. Entries exist for every APPN port defined to support HPR over IP."
hprIpAppnPortEntry对象类型语法hprIpAppnPortEntry MAX-ACCESS不可访问状态当前描述“HPR/IP APPN端口表的条目。为支持IP上的HPR而定义的每个APPN端口都存在条目。”
INDEX { hprIpAppnPortName, hprIpAppnPortAppnTrafficType }
索引{hprIpAppnPortName，hprIpAppnPortAppnTrafficType}
::= { hprIpAppnPortTable 1 }
::= { hprIpAppnPortTable 1 }
HprIpAppnPortEntry ::= SEQUENCE {
hprIpAppnPortName DisplayString,
hprIpAppnPortAppnTrafficType AppnTrafficType,
hprIpAppnPortTOSPrecedence AppnTOSPrecedence }
HprIpAppnPortEntry ::= SEQUENCE {
hprIpAppnPortName DisplayString,
hprIpAppnPortAppnTrafficType AppnTrafficType,
hprIpAppnPortTOSPrecedence AppnTOSPrecedence }
hprIpAppnPortName OBJECT-TYPE SYNTAX DisplayString (SIZE (1..10)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Administratively assigned name for this APPN port. If this object has the same value as the appnPortName in the APPN MIB, then the two objects are referring to the same APPN port."
hprIpAppnPortName对象类型语法DisplayString（大小（1..10））MAX-ACCESS不可访问状态当前描述“此APPN端口的管理分配名称。如果此对象与APPN MIB中的APPPortName具有相同的值，则这两个对象引用的是同一APPN端口。”
::= { hprIpAppnPortEntry 1 }
::= { hprIpAppnPortEntry 1 }
hprIpAppnPortAppnTrafficType OBJECT-TYPE SYNTAX AppnTrafficType MAX-ACCESS not-accessible STATUS current DESCRIPTION "APPN traffic type sent through the port."
hprIpAppnPortAppnTrafficType对象类型语法AppnTrafficType MAX-ACCESS不可访问状态当前描述“通过端口发送的APPN流量类型。”
::= { hprIpAppnPortEntry 2 }
::= { hprIpAppnPortEntry 2 }
hprIpAppnPortTOSPrecedence OBJECT-TYPE SYNTAX AppnTOSPrecedence MAX-ACCESS read-write STATUS current DESCRIPTION "A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type.
HPRIPAppnPortTosPreference对象类型语法AppNtosRecessence MAX-ACCESS读写状态当前描述“此APPN流量类型的IP服务类型字段中三个TOS优先位的设置。
When this value is changed via a Set operation, the new setting for the TOS Precedence bits takes effect immediately, rather
当通过Set操作更改此值时，TOS优先位的新设置立即生效，而不是
than waiting for some event such as reinitialization of the port or of the APPN node itself."
而不是等待某些事件，例如重新初始化端口或APPN节点本身。“
::= { hprIpAppnPortEntry 3 }
::= { hprIpAppnPortEntry 3 }
-- *******************************************************************
hprIpLsTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpLsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP link station table. Values for TOS Precedence at
the link station level override those at the level of the
containing port. If there is no entry in this table for a
given link station, then that link station inherits its TOS
Precedence values from its port."
-- *******************************************************************
hprIpLsTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpLsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP link station table. Values for TOS Precedence at
the link station level override those at the level of the
containing port. If there is no entry in this table for a
given link station, then that link station inherits its TOS
Precedence values from its port."
::= { hprIp 3 }
::= { hprIp 3 }
hprIpLsEntry OBJECT-TYPE SYNTAX HprIpLsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry of the HPR/IP link station table."
HPRIPLENTRY对象类型语法HPRIPLENTRY MAX-ACCESS不可访问状态当前描述“HPR/IP链路站表的条目”
INDEX { hprIpLsLsName, hprIpLsAppnTrafficType }
索引{hprIpLsLsName，HPRIPLSAPPNTRAFFCTYPE}
::= { hprIpLsTable 1 }
::= { hprIpLsTable 1 }
HprIpLsEntry ::= SEQUENCE {
hprIpLsLsName DisplayString,
hprIpLsAppnTrafficType AppnTrafficType,
hprIpLsTOSPrecedence AppnTOSPrecedence,
hprIpLsRowStatus RowStatus }
HprIpLsEntry ::= SEQUENCE {
hprIpLsLsName DisplayString,
hprIpLsAppnTrafficType AppnTrafficType,
hprIpLsTOSPrecedence AppnTOSPrecedence,
hprIpLsRowStatus RowStatus }
hprIpLsLsName OBJECT-TYPE SYNTAX DisplayString (SIZE (1..10)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Administratively assigned name for the link station. If this object has the same value as the appnLsName in the APPN MIB, then the two objects are referring to the same APPN link station."
hprIpLsLsName对象类型语法DisplayString（大小（1..10））MAX-ACCESS not ACCESS STATUS current DESCRIPTION“链接站的管理分配名称。如果此对象与APPN MIB中的appnLsName具有相同的值，则这两个对象引用的是同一APPN链接站。”
::= { hprIpLsEntry 1 }
::= { hprIpLsEntry 1 }
hprIpLsAppnTrafficType OBJECT-TYPE SYNTAX AppnTrafficType MAX-ACCESS not-accessible STATUS current DESCRIPTION "APPN traffic type sent through the link station."
HPRIPLSAPPNTRAFFCTYPE对象类型语法APPPNTRAFFCTYPE MAX-ACCESS不可访问状态当前描述“通过链接站发送的APPN流量类型”
::= { hprIpLsEntry 2 }
::= { hprIpLsEntry 2 }
hprIpLsTOSPrecedence OBJECT-TYPE SYNTAX AppnTOSPrecedence MAX-ACCESS read-create STATUS current DESCRIPTION "A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type.
HPRIPLStopRecessence对象类型语法APPNTSRecessence MAX-ACCESS read create STATUS current DESCRIPTION“此APPN流量类型的IP服务类型字段中三个TOS优先级位的设置。
When this value is changed via a Set operation, the new setting for the TOS Precedence bits takes effect immediately, rather than waiting for some event such as reinitialization of the port or of the APPN node itself."
当通过Set操作更改此值时，TOS优先位的新设置立即生效，而不是等待端口或APPN节点本身的重新初始化等事件。”
::= { hprIpLsEntry 3 }
::= { hprIpLsEntry 3 }
hprIpLsRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the hprIpLsTable. As soon as an entry becomes active, the mapping between APPN traffic types and TOS Precedence settings that it specifies becomes effective.
hprIpLsRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在hprIpLsTable中创建和删除条目。一旦条目变为活动状态，它指定的APPN流量类型和TOS优先级设置之间的映射将生效。
The value of the other accessible object in this entry, hprIpLsTOSPrecedence, can be changed via a Set operation when this object's value is active(1).
当此对象的值处于活动状态（1）时，可以通过Set操作更改此条目中的另一个可访问对象HPRIPLSTOPSRECESS的值。
An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table causes the link station to revert to the default TOS Precedence mapping for its port."
通过将此对象设置为destroy（6），可以删除此表中的条目。删除此表中的条目会导致链路站还原到其端口的默认TOS优先级映射。”
::= { hprIpLsEntry 4 }
::= { hprIpLsEntry 4 }
-- *******************************************************************
hprIpCnTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpCnEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP connection network table. Values for TOS
Precedence at the connection network level override those at
the level of the containing port. If there is no entry in
this table for a given connection network, then that
connection network inherits its TOS Precedence values from
its port.
-- *******************************************************************
hprIpCnTable OBJECT-TYPE
SYNTAX SEQUENCE OF HprIpCnEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The HPR/IP connection network table. Values for TOS
Precedence at the connection network level override those at
the level of the containing port. If there is no entry in
this table for a given connection network, then that
connection network inherits its TOS Precedence values from
its port.
A node may have connections to a given connection network through multiple ports. There is no provision in the HPR-IP architecture for variations in TOS Precedence values for a single connection network based on the port through which traffic is flowing to the connection network. Thus an entry in this table overrides the port-level settings for all the ports through which the node can reach the connection network."
节点可以通过多个端口连接到给定的连接网络。HPR-IP体系结构中没有针对单个连接网络的TOS优先级值变化的规定，该值基于流量流向连接网络的端口。因此，此表中的条目将覆盖节点可通过其到达连接网络的所有端口的端口级别设置。”
::= { hprIp 4 }
::= { hprIp 4 }
hprIpCnEntry OBJECT-TYPE SYNTAX HprIpCnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry of the HPR/IP connection network table."
HPRIPCNERY对象类型语法HPRIPCNERY MAX-ACCESS不可访问状态当前描述“HPR/IP连接网络表的条目”
INDEX { hprIpCnVrnName, hprIpCnAppnTrafficType }
索引{hprIpCnVrnName，hprIpCnAppnTrafficType}
::= { hprIpCnTable 1 }
::= { hprIpCnTable 1 }
HprIpCnEntry ::= SEQUENCE {
hprIpCnVrnName SnaControlPointName,
hprIpCnAppnTrafficType AppnTrafficType,
hprIpCnTOSPrecedence AppnTOSPrecedence,
hprIpCnRowStatus RowStatus }
HprIpCnEntry ::= SEQUENCE {
hprIpCnVrnName SnaControlPointName,
hprIpCnAppnTrafficType AppnTrafficType,
hprIpCnTOSPrecedence AppnTOSPrecedence,
hprIpCnRowStatus RowStatus }
hprIpCnVrnName OBJECT-TYPE SYNTAX SnaControlPointName MAX-ACCESS not-accessible STATUS current DESCRIPTION "SNA control point name of the virtual routing node (VRN) that
HPRIPCNVRNAME对象类型语法SnaControlPointName MAX-ACCESS不可访问状态当前描述“要访问的虚拟路由节点（VRN）的SNA控制点名称”
identifies the connection network in the APPN topology database. If this object has the same value as the appnVrnName in the APPN MIB, then the two objects are referring to the same APPN VRN."
标识APPN拓扑数据库中的连接网络。如果此对象与APPN MIB中的appnVrnName具有相同的值，则这两个对象引用的是相同的APPN VRN。“
::= { hprIpCnEntry 1 }
::= { hprIpCnEntry 1 }
hprIpCnAppnTrafficType OBJECT-TYPE SYNTAX AppnTrafficType MAX-ACCESS not-accessible STATUS current DESCRIPTION "APPN traffic type sent to this connection network."
HPRIPCNAPPNTRAFFCTYPE对象类型语法APPPNTRAFFCTYPE MAX-ACCESS不可访问状态当前描述“发送到此连接网络的APPN流量类型。”
::= { hprIpCnEntry 2 }
::= { hprIpCnEntry 2 }
hprIpCnTOSPrecedence OBJECT-TYPE SYNTAX AppnTOSPrecedence MAX-ACCESS read-create STATUS current DESCRIPTION "A setting for the three TOS Precedence bits in the IP Type of Service field for this APPN traffic type. This setting applies to all traffic sent to this connection network by this node, regardless of the port through which the traffic is sent.
HPRIPCNTOSPRECENDESS对象类型语法APPNOSPRECENDESS MAX-ACCESS读取创建状态当前描述“此APPN流量类型的IP服务类型字段中三个TOS优先位的设置。此设置适用于此节点发送到此连接网络的所有流量，而不考虑通过哪个端口发送流量。
When this value is changed via a Set operation, the new setting
for the TOS Precedence bits takes effect immediately, rather
than waiting for some event such as reinitialization of a
port or of the APPN node itself."
::= { hprIpCnEntry 3 }
When this value is changed via a Set operation, the new setting
for the TOS Precedence bits takes effect immediately, rather
than waiting for some event such as reinitialization of a
port or of the APPN node itself."
::= { hprIpCnEntry 3 }
hprIpCnRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the hprIpCnTable. As soon as an entry becomes active, the mapping between APPN traffic types and TOS Precedence settings that it specifies becomes effective.
hprIpCnRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此对象允许在hprIpCnTable中创建和删除条目。一旦条目变为活动状态，它指定的APPN流量类型和TOS优先级设置之间的映射将生效。
The value of the other accessible object in this entry, hprIpCnTOSPrecedence, can be changed via a Set operation when this object's value is active(1).
当此对象的值处于活动状态（1）时，可以通过设置操作更改此条目中另一个可访问对象hprIpCnTOSPrecedence的值。
An entry in this table is deleted by setting this object to destroy(6). Deleting an entry in this table causes the
通过将此对象设置为destroy（6），可以删除此表中的条目。删除此表中的条目会导致
connection network to revert to the default TOS Precedence mapping for each port through which it is accessed."
连接网络，以恢复到访问它的每个端口的默认TOS优先级映射。”
::= { hprIpCnEntry 4 }
::= { hprIpCnEntry 4 }
-- *******************************************************************
-- Conformance Statement
-- *******************************************************************
-- Definitions imported from the HPR MIB:
-- hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 }
-- hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 }
-- hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 }
-- *******************************************************************
-- Conformance Statement
-- *******************************************************************
-- Definitions imported from the HPR MIB:
-- hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 }
-- hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 }
-- hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 }
-- Compliance statements hprIpCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for the HPR over IP MIB module." MODULE -- this module
--合规性声明HPRIP合规性模块—合规性状态当前描述“HPR over IP MIB模块的合规性声明”。模块—此模块
-- Conditionally mandatory groups GROUP hprIpMonitoringGroup DESCRIPTION "The hprIpMonitoringGroup is mandatory for APPN implementations supporting HPR over IP."
--条件强制组组hprIpMonitoringGroup DESCRIPTION“hprIpMonitoringGroup对于支持HPR over IP的APPN实现是强制的。”
GROUP hprIpConfigurationGroup DESCRIPTION "The hprIpConfigurationGroup is mandatory for APPN implementations supporting HPR over IP. It may, however, be implemented as a collection of read-only objects."
GROUP hprIpConfigurationGroup DESCRIPTION“hprIpConfigurationGroup对于支持HPR over IP的APPN实现是必需的。但是，它可以实现为只读对象的集合。”
OBJECT hprIpAppnPortTOSPrecedence MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象HPRIPAppnPortTosMin-ACCESS只读说明“不需要写访问。”
OBJECT hprIpLsTOSPrecedence MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象HPRIPLStopRecessence最小访问只读描述“不需要写访问。”
OBJECT hprIpLsRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象hprIpLsRowStatus MIN-ACCESS只读说明“不需要写访问权限。”
OBJECT hprIpCnTOSPrecedence MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象hprIpCnTOSPrecedence最小访问只读描述“不需要写访问。”
OBJECT hprIpCnRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象hprIpCnRowStatus MIN-ACCESS只读说明“不需要写访问权限。”
::= { hprCompliances 2 }
::= { hprCompliances 2 }
-- Group definitions
--组定义
hprIpMonitoringGroup OBJECT-GROUP OBJECTS { hprIpActiveLsUdpPackets } STATUS current DESCRIPTION "An object for counting outgoing HPR/IP traffic for each APPN traffic type."
hprIpMonitoringGroup对象组对象{hprIpActiveLsUdpPackets}状态当前描述“用于计算每种APPN流量类型的传出HPR/IP流量的对象。”
::= { hprGroups 5 }
::= { hprGroups 5 }
hprIpConfigurationGroup OBJECT-GROUP OBJECTS { hprIpAppnPortTOSPrecedence, hprIpLsTOSPrecedence, hprIpLsRowStatus, hprIpCnTOSPrecedence, hprIpCnRowStatus } STATUS current DESCRIPTION "A collection of HPR/IP objects representing the mappings between APPN traffic types and TOS Precedence bits at the APPN port, APPN link station, and APPN connection network levels."
hprIpConfigurationGroup对象组对象{HPRIPAppnPortToPreference，HPRIPLSOSPRecessence，HPRIPLSOSPROWSTATUS，HPRIPCNOSPRecessence，HPRIPCNOSPROWSTATUS}状态当前描述HPR/IP对象的集合，表示APPN端口、APPN链路站和APPN连接网络级别上的APPN通信量类型和TOS优先位之间的映射
::= { hprGroups 6 }
::= { hprGroups 6 }
END
终止
Certain management information defined in this MIB may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information SHOULD be employed in such environments. An authentication protocol is defined in [12]. A protocol for access control is defined in [15]. It is a customer responsibility to properly set up access control for MIB access.
在某些网络环境中，此MIB中定义的某些管理信息可能被视为敏感信息。因此，在这样的环境中，应该对接收到的SNMP请求进行身份验证，并控制对管理信息的访问。[12]中定义了认证协议。[15]中定义了访问控制协议。正确设置MIB访问的访问控制是客户的责任。
None of the read-only objects in this MIB reports a password, user data, or anything else that is particularly sensitive. Some enterprises view their network configuration itself, as well as information about network usage and performance, as corporate assets; such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
此MIB中的只读对象都不会报告密码、用户数据或任何其他特别敏感的内容。一些企业将其网络配置本身以及有关网络使用和性能的信息视为企业资产；此类企业可能希望限制对MIB中大多数对象的SNMP访问。
The one read-write and four read-create objects in the MIB can affect network operations; it is recommended that SNMP access to these objects be restricted. The five objects are:
MIB中的一个读写和四个读创建对象会影响网络操作；建议限制对这些对象的SNMP访问。这五个对象是：
o hprIpPortTOSPrecedence: Setting this object immediately changes the mapping for all link stations using this port which do not have an entry to override the port value. Improper mappings may cause delays or disruptions in the network. For example, if APPN traffic type 'High' is mapped to IP TOS Precedence bits ' 001', network control traffic will have the same TOS precedence as bulk data traffic. This may cause delays with session initializations, and timeouts on control sessions that could cause network outages.
o HPRIPPortTosPreference：设置此对象会立即更改使用此端口的所有链路站的映射，这些链路站没有覆盖端口值的条目。不正确的映射可能会导致网络延迟或中断。例如，如果APPN通信量类型“高”映射到IP TOS优先级位“001”，则网络控制通信量将具有与批量数据通信量相同的TOS优先级。这可能会导致会话初始化延迟，以及控制会话超时，从而导致网络中断。
o hprIpLsTOSPrecedence: Setting this object has the potential for delay or disruption for this link station as described above with hprIpPortTOSPrecedence.
o HPRIPPortToPreference：设置此对象可能会导致此链接站延迟或中断，如上面使用HPRIPPortToPreference所述。
o hprIpLsRowStatus: Setting this object to delete(6) causes this link station to revert to the default TOS Precedence mapping for its port. The customized mapping for this link station will no longer be in effect.
o hprIpLsRowStatus：将此对象设置为delete（6）会导致此链接站还原为其端口的默认TOS优先级映射。此链接站点的自定义映射将不再有效。
o hprIpCnTOSPrecedence: Setting this object has the potential for delay or disruption for this links created for this connection network as described above with hprIpPortTOSPrecedence.
o hprIpCnTOSPrecedence：设置此对象可能会延迟或中断使用HPRIPPortToPreference如上所述为此连接网络创建的链接。
o hprIpCnRowStatus: Setting this object to delete(6) causes links created for this connection network to revert to the default TOS Precedence mapping for its port. The customized mapping for this connection network will no longer be in effect.
o hprIpCnRowStatus：将此对象设置为delete（6）会导致为此连接网络创建的链接还原为其端口的默认TOS优先级映射。此连接网络的自定义映射将不再有效。
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
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。IETF关于标准跟踪和认证权利的程序信息
standards-related documentation can be found in BCP-11 [16]. 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.
与标准相关的文件可在BCP-11[16]中找到。可从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执行董事。
This MIB module is the product of the IETF SNA NAU MIB WG and the AIW APPN/HPR MIBs SIG. The editors would like to thank Katie Lee, IBM Corporation, for her work in creating the original version of this MIB.
该MIB模块是IETF SNA NAU MIB WG和AIW APPN/HPR MIBs SIG的产品。编辑们要感谢IBM公司的Katie Lee，感谢她在创建此MIB原始版本方面所做的工作。
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, January 1998
[1] Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2271，1998年1月
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[5] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[5] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[6] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998.
[11] Case，J.，Harrington D.，Presuhn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 22721998年1月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 22741998年1月。
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 22731998年1月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 22751998年1月。
[16] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[16] Hovey，R.和S.Bradner，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。
[17] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[17] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[18] Dudley, G, "APPN/HPR in IP Networks", RFC 2353, May 1998.
[18] Dudley，G，“IP网络中的APPN/HPR”，RFC 2353，1998年5月。
[19] Clouston, B. and B. Moore, "Definition of Managed Objects for APPN", RFC 2455, November 1998.
[19] Clouston，B.和B.Moore，“APPN管理对象的定义”，RFC 2455，1998年11月。
[20] Clouston, B. and B. Moore, "Definitions of Managed Objects for HPR", RFC 2238, May 1997.
[20] Clouston，B.和B.Moore，“HPR管理对象的定义”，RFC 2238，1997年5月。
[21] Nichols, K., Blake, S., Baker, F. and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998.
[21] Nichols，K.，Blake，S.，Baker，F.和D.Black，“IPv4和IPv6标头中区分服务字段（DS字段）的定义”，RFC 2474，1998年12月。
Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA
Bob Clouston Cisco Systems 7025 Kit Creek Road美国北卡罗来纳州三角研究公园14987号邮政信箱，邮编27709
Phone: +1 919 472 2333
EMail: clouston@cisco.com
Phone: +1 919 472 2333
EMail: clouston@cisco.com
Robert Moore Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
美国北卡罗来纳州康沃利斯研究三角公园12195 3039号IBM公司信箱501/G114号楼BRQA/BRQA部门
Phone: +1 919 254 4436
EMail: remoore@us.ibm.com
Phone: +1 919 254 4436
EMail: remoore@us.ibm.com
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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编辑功能的资金目前由互联网协会提供。