Network Working Group S. Chisholm
Request for Comments: 4268 Nortel Networks
Category: Standards Track D. Perkins
SNMPinfo
November 2005
Network Working Group S. Chisholm
Request for Comments: 4268 Nortel Networks
Category: Standards Track D. Perkins
SNMPinfo
November 2005
Entity State MIB
实体状态MIB
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 (2005).
版权所有（C）互联网协会（2005年）。
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 describes extensions to the Entity MIB to provide information about the state of physical entities.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了实体MIB的扩展，以提供有关物理实体状态的信息。
In addition, this memo defines a set of Textual Conventions to represent various states of an entity. The intent is that these Textual Conventions will be imported and used in MIB modules that would otherwise define their own representations.
此外，本备忘录定义了一组文本约定，以表示实体的各种状态。目的是导入这些文本约定，并在MIB模块中使用，否则这些模块将定义它们自己的表示。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................2
2. Entity State ....................................................2
2.1. Hierarchical State Management ..............................3
2.2. Entity Redundancy ..........................................3
2.3. Physical Entity Users ......................................3
2.4. Physical Class Behavior ....................................4
3. Relation to Other MIBs ..........................................4
3.1. Relation to the Interfaces MIB .............................4
3.2. Relation to Alarm MIB ......................................5
3.3. Relation to Bridge MIB .....................................5
3.4. Relation to the Host Resources MIB .........................5
4. Textual Conventions .............................................6
5. Definitions .................................................... 9
1. The Internet-Standard Management Framework ......................2
2. Entity State ....................................................2
2.1. Hierarchical State Management ..............................3
2.2. Entity Redundancy ..........................................3
2.3. Physical Entity Users ......................................3
2.4. Physical Class Behavior ....................................4
3. Relation to Other MIBs ..........................................4
3.1. Relation to the Interfaces MIB .............................4
3.2. Relation to Alarm MIB ......................................5
3.3. Relation to Bridge MIB .....................................5
3.4. Relation to the Host Resources MIB .........................5
4. Textual Conventions .............................................6
5. Definitions .................................................... 9
6. Security Considerations ........................................16
7. Acknowledgements ...............................................17
8. References .....................................................17
8.1. Normative References ......................................17
8.2. Informative References ....................................18
6. Security Considerations ........................................16
7. Acknowledgements ...............................................17
8. References .....................................................17
8.1. Normative References ......................................17
8.2. Informative References ....................................18
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The goal in adding state objects to the Entity MIB [RFC4133] is to define a useful subset of the possible state attributes that could be tracked for a given entity and that both fit into the state models such as those used in the Interfaces MIB [RFC2863] as well as leverage existing well-deployed models. The entStateTable contains state objects that are a subset of the popular ISO/OSI states that are also defined in ITU's X.731 specification [X.731]. Objects are defined to capture administrative, operational, and usage states. In addition, there are further state objects defined to provide more information for these three basic states.
将状态对象添加到实体MIB[RFC4133]的目的是定义可能的状态属性的有用子集，这些属性可以为给定实体跟踪，并且都适合于状态模型，如接口MIB[RFC2863]中使用的状态模型，并利用现有部署良好的模型。entStateTable包含的状态对象是流行的ISO/OSI状态的子集，这些状态也在ITU的X.731规范[X.731]中定义。对象被定义为捕获管理、操作和使用状态。此外，还定义了更多的状态对象，为这三种基本状态提供更多信息。
Administrative state indicates permission to use or prohibition against using the entity and is imposed through the management services.
行政状态表示允许使用或禁止使用实体，并通过管理服务实施。
Operational state indicates whether or not the entity is physically installed and working. Note that unlike the ifOperStatus [RFC2863], this operational state is independent of the administrative state.
操作状态指示实体是否已实际安装并正在工作。请注意，与ifOperStatus[RFC2863]不同，此操作状态独立于管理状态。
Usage state indicates whether or not the entity is in use at a specific instance, and if so, whether or not it currently has spare capacity to serve additional users. In the context of this MIB, the usage state refers to the ability of an entity to service other entities within its containment hierarchy.
使用状态表示实体是否在特定实例中使用，如果是，则表示实体当前是否具有为其他用户服务的备用容量。在这个MIB的上下文中，使用状态指的是实体为其包含层次结构中的其他实体提供服务的能力。
Alarm state indicates whether or not there are any alarms active against the entity. In addition to those alarm states defined in X.731 [X.731], warning and indeterminate status are also defined to provide a more complete mapping to the Alarm MIB [RFC3877].
报警状态指示是否存在针对实体的活动报警。除了X.731[X.731]中定义的报警状态外，还定义了警告和不确定状态，以提供到报警MIB[RFC3877]的更完整映射。
Standby state indicates whether the entity is currently running as hot standby or cold standby or is currently providing service.
Standby state表示实体当前是作为热备用还是冷备用运行，或者当前正在提供服务。
The terms "state" and "status" are used interchangeably in this memo.
“状态”和“状态”在本备忘录中互换使用。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
Physical entities exist within a containment hierarchy. Physical containment is defined by the entPhysicalContainedIn object[RFC4133]. This raises some interesting issues not addressed in existing work on state management.
物理实体存在于包含层次结构中。物理包含由entPhysicalContainedIn对象[RFC4133]定义。这就提出了一些在现有国家管理工作中没有解决的有趣问题。
There are two types of state for an entity:
实体有两种类型的状态：
1) The state of the entity independent of the states of its parents and children in its containment hierarchy. This is often referred to as raw state.
1) 实体的状态，独立于其包含层次结构中父级和子级的状态。这通常被称为原始状态。
2) The state of the entity, as it may be influenced by the state of its parents and children. This is often referred to as computed state.
2) 实体的状态，可能受其父母和子女的状态影响。这通常被称为计算状态。
All state objects in this memo are raw state.
此备忘录中的所有状态对象都是原始状态。
While this memo is not attempting to address the entire problem space around redundancy, the entStateStandby object provides an important piece of state information for entities, which helps identify which pieces of redundant equipment are currently providing service, and which are waiting in either hot or cold standby mode.
虽然此备忘录并未试图解决冗余的整个问题空间，但entStateStandby对象为实体提供了一条重要的状态信息，这有助于确定哪些冗余设备当前正在提供服务，哪些设备正在热备用或冷备用模式下等待。
There are three ways to define the 'user' of a physical entity
有三种方法可以定义物理实体的“用户”
1. Direct containment in physical hierarchy
1. 物理层次结构中的直接包容
2. Anywhere in physical hierarchy
2. 物理层次结构中的任意位置
3. As defined by a means outside the scope of this MIB. This could include logical interfaces that could run on a port, software that could run on a module, etc.
3. 通过本MIB范围之外的方式定义。这可能包括可在端口上运行的逻辑接口、可在模块上运行的软件等。
Administrative, operational, alarm, and standby state use all three definitions of 'user'. Usage state supports only the concept of direct containment to simplify implementations of this object.
管理、操作、报警和待机状态使用“用户”的所有三种定义。使用状态仅支持直接包含的概念，以简化此对象的实现。
This MIB makes no effort to standardize the behaviors and characteristics of the various physical classes [RFC4133], but rather how this information is reported. In looking at real-world products, items within the same physical class vary substantially. The MIB has therefore provided guidance on how to support objects where a particular instance of a physical class cannot support part or all of a particular state.
该MIB不致力于标准化各种物理类的行为和特征[RFC4133]，而是如何报告这些信息。在查看真实世界的产品时，同一物理类别中的项目差异很大。因此，MIB提供了如何支持物理类的特定实例无法支持特定状态的部分或全部的对象的指导。
The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which has states of up, down, and testing, and the ifOperStatus object, which has states of up, down, testing, unknown, dormant, notPresent, and lowerLayerDown.
接口MIB[RFC2863]定义了ifAdminStatus对象，其状态为up、down和testing，以及ifOperStatus对象，其状态为up、down、testing、unknown、Dorment、notPresent和lowerLayerDown。
An ifAdminStatus of 'up' is equivalent to setting the entStateAdmin object to 'unlocked'. An ifAdminStatus of 'down' is equivalent to setting the entStateAdmin object to either 'locked' or 'shuttingDown', depending on a system's interpretation of 'down'.
ifAdminStatus为“up”相当于将entStateAdmin对象设置为“unlocked”。ifAdminStatus为“down”相当于将entStateAdmin对象设置为“locked”或“shuttingDown”，具体取决于系统对“down”的解释。
An ifOperStatus of 'up' is equivalent to an entStateOper value of 'enabled'. An ifOperStatus of 'down' due to operational failure is equivalent to an entStateOper value of 'disabled'. An ifOperStatus of 'down' due to being administratively disabled is equivalent to an entStateAdmin value of 'locked' and an entStateOper value of either 'enabled' or 'disabled' depending on whether there are any known issues that would prevent the entity from becoming operational when its entStateAdmin is set to 'unlocked'. An ifOperStatus of 'unknown' is equivalent to an entStateOper value of 'unknown'. The ifOperStatus values of 'testing' and 'dormant' are not explicitly supported by this MIB, but the state objects will be able to reflect other aspects of the entities' administrative and operational state. The ifOperStatus values of 'notPresent' and 'lowerLayerDown' are in some ways computed states and so are therefore not supported in this
ifOperStatus为'up'相当于entStateOper值为'enabled'。由于操作故障而导致的IfOperaStatus为'down'相当于entStateOper值为'disabled'。由于被管理性禁用而导致的IfOperatStatus“down”相当于entStateAdmin值“locked”和entStateOper值“enabled”或“disabled”，具体取决于entStateAdmin设置为“unlocked”时是否存在任何会阻止实体运行的已知问题。ifOperStatus为“unknown”等同于entStateOper值为“unknown”。此MIB不明确支持“testing”和“dormant”的ifOperaStatus值，但状态对象将能够反映实体的管理和操作状态的其他方面。“notPresent”和“lowerLayerDown”的IfOperatStatus值在某些方面是计算状态，因此在本例中不受支持
MIB. They can, though, be computed by examining the states of entities within this object's containment hierarchy and other available related states.
MIB。但是，可以通过检查此对象的包含层次结构中实体的状态和其他可用的相关状态来计算它们。
The entStateAlarm object indicates whether or not there are any active alarms against this entity. If there are active alarms, then the alarmActiveTable in the Alarm MIB [RFC3877] should be searched for rows whose alarmActiveResourceId matches this entPhysicalIndex.
entStateAlarm对象指示是否存在针对此实体的任何活动报警。如果存在活动报警，则应在报警MIB[RFC3877]中的alarmActiveTable中搜索alarmActiveResourceId与此entPhysicalIndex匹配的行。
Alternatively, if the alarmActiveTable is queried first and an active alarm with a value of alarmActiveResourceId that matches this entPhysicalIndex is found, then entStateAlarm can be used to quickly determine if there are additional active alarms with a different severity against this physical entity.
或者，如果首先查询alarmActiveTable，并找到与此entPhysicalIndex匹配的alarmActiveResourceId值的活动报警，则可以使用entStateAlarm快速确定是否存在针对此物理实体的其他严重性不同的活动报警。
For entities of physical type of 'port' that support the dot1dStpPortEnable object in the Bridge MIB [RFC4188], a value of 'enabled' is equivalent to setting the entStateAdmin object to 'unlocked'. Setting dot1dStpPortEnable to 'disabled' is equivalent to setting the entStateAdmin object to 'locked'.
对于支持网桥MIB[RFC4188]中DOT1DSPTPORATABLE对象的物理类型为“port”的实体，值“enabled”相当于将entStateAdmin对象设置为“unlocked”。将dot1dstportenable设置为“disabled”相当于将entStateAdmin对象设置为“locked”。
The hrDeviceStatus object in the Host Resources MIB [RFC2790] provides an operational state for devices. For entities that logically correspond to the concept of a device, a value of 'unknown' for hrDeviceStatus corresponds to an entStateOper value of 'unknown'. A value of 'running' corresponds to an entStateOper value of 'enabled'. A value of 'warning' also corresponds to an entStateOper value of 'enabled', but with appropriate bits set in the entStateAlarm object to indicate the alarms corresponding to the unusual error condition detected. A value of 'testing' or 'down' is equivalent to an entStateOper value of 'disabled'.
主机资源MIB[RFC2790]中的hrDeviceStatus对象为设备提供操作状态。对于逻辑上与设备概念相对应的实体，hrDeviceStatus的“未知”值对应于entStateOper的“未知”值。值“running”对应于entStateOper值“enabled”。“警告”值也对应于“已启用”的entStateOper值，但在entStateAlarm对象中设置了适当的位，以指示与检测到的异常错误条件相对应的报警。值“testing”或“down”相当于entStateOper值“disabled”。
ENTITY-STATE-TC-MIB DEFINITIONS ::= BEGIN
ENTITY-STATE-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
从SNMPv2 TC导入模块标识、mib-2和SNMPv2 SMI文本约定；
entityStateTc MODULE-IDENTITY
LAST-UPDATED "200511220000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
"General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
entityStateTc MODULE-IDENTITY
LAST-UPDATED "200511220000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
"General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html
http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Nortel Networks PO Box 3511 Station C Ottawa, Ont. K1Y 4H7 Canada schishol@nortel.com
安大略省渥太华市C站3511号邮政信箱。K1Y 4H7加拿大schishol@nortel.com
David T. Perkins 548 Qualbrook Ct San Jose, CA 95110 USA Phone: 408 394-8702 dperkins@snmpinfo.com" DESCRIPTION "This MIB defines state textual conventions.
David T.Perkins 548加利福尼亚州圣何塞Qualbrook Ct 95110美国电话：408 394-8702dperkins@snmpinfo.com“说明”此MIB定义状态文本约定。
Copyright (C) The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200511220000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 130 }
Copyright (C) The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200511220000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 130 }
EntityAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
EntityAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use. A value of
'unknown' means that this resource is unable to
report administrative state."
SYNTAX INTEGER
{
unknown (1),
locked (2),
shuttingDown (3),
unlocked (4)
}
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use. A value of
'unknown' means that this resource is unable to
report administrative state."
SYNTAX INTEGER
{
unknown (1),
locked (2),
shuttingDown (3),
unlocked (4)
}
EntityOperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
EntityOperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable. A value of 'testing'
means the resource is currently being tested
and cannot therefore report whether it is operational
or not. A value of 'unknown' means that this
resource is unable to report operational state."
SYNTAX INTEGER
{
unknown (1),
disabled (2),
enabled (3),
testing (4)
}
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable. A value of 'testing'
means the resource is currently being tested
and cannot therefore report whether it is operational
or not. A value of 'unknown' means that this
resource is unable to report operational state."
SYNTAX INTEGER
{
unknown (1),
disabled (2),
enabled (3),
testing (4)
}
EntityUsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users. A value of 'unknown' means
that this resource is unable to report usage state."
SYNTAX INTEGER
EntityUsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users. A value of 'unknown' means
that this resource is unable to report usage state."
SYNTAX INTEGER
{
unknown (1),
idle (2),
active (3),
busy (4)
}
{
unknown (1),
idle (2),
active (3),
busy (4)
}
EntityAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of alarm status.
An Alarm [RFC3877] is a persistent indication
of an error or warning condition.
EntityAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of alarm status.
An Alarm [RFC3877] is a persistent indication
of an error or warning condition.
When no bits of this attribute are set, then no active alarms are known against this entity and it is not under repair.
如果未设置此属性的任何位，则不知道该实体的活动报警，并且该实体不在修复中。
When the 'value of underRepair' is set, the resource is currently being repaired, which, depending on the implementation, may make the other values in this bit string not meaningful.
设置“欠修复值”时，资源当前正在修复，这可能会使此位字符串中的其他值失去意义，具体取决于实现。
When the value of 'critical' is set, one or more critical alarms are active against the resource. When the value of 'major' is set, one or more major alarms are active against the resource. When the value of 'minor' is set, one or more minor alarms are active against the resource. When the value of 'warning' is set, one or more warning alarms are active against the resource. When the value of 'indeterminate' is set, one or more alarms of whose perceived severity cannot be determined are active against this resource.
设置“临界”值时，一个或多个针对资源的临界报警处于活动状态。设置“主要”值时，一个或多个针对资源的主要报警处于活动状态。设置“次要”值时，一个或多个针对资源的次要报警处于活动状态。设置“警告”值时，一个或多个针对资源的警告警报处于活动状态。设置“不确定”值时，无法确定其感知严重性的一个或多个警报将针对该资源激活。
A value of 'unknown' means that this resource is
unable to report alarm state."
SYNTAX BITS
{
unknown (0),
underRepair (1),
critical(2),
major(3),
minor(4),
-- The following are not defined in X.733
warning (5),
indeterminate (6)
}
A value of 'unknown' means that this resource is
unable to report alarm state."
SYNTAX BITS
{
unknown (0),
underRepair (1),
critical(2),
major(3),
minor(4),
-- The following are not defined in X.733
warning (5),
indeterminate (6)
}
EntityStandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
EntityStandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to
take over the role of the resource to be backed up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service. A value of
'unknown' means that this resource is unable to
report standby state."
SYNTAX INTEGER
{
unknown (1),
hotStandby (2),
coldStandby (3),
providingService (4)
}
A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to
take over the role of the resource to be backed up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service. A value of
'unknown' means that this resource is unable to
report standby state."
SYNTAX INTEGER
{
unknown (1),
hotStandby (2),
coldStandby (3),
providingService (4)
}
END
终止
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI DateAndTime FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF entPhysicalIndex FROM ENTITY-MIB EntityAdminState, EntityOperState, EntityUsageState, EntityAlarmStatus, EntityStandbyStatus FROM ENTITY-STATE-TC-MIB;
从ENTITY-mib EntityAdminState、EntityOpertState、EntityUsageState、EntityAlarmStatus、EntityStandbyStatus从SNMPv2 TC-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUP从SNMPv2 CONF entPhysicalIndex从ENTITY-mib EntityAdminState导入模块标识、对象类型、通知类型、mib-2，从SNMPv2 SMI日期和时间从ENTITY-STATE-TC-mib导入EntityStandbyStatus；
entityStateMIB MODULE-IDENTITY LAST-UPDATED "200511220000Z" ORGANIZATION "IETF Entity MIB Working Group"
entityStateMIB模块标识最后更新的“20051122000Z”组织“IETF实体MIB工作组”
CONTACT-INFO
" General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
CONTACT-INFO
" General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html
http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Nortel Networks PO Box 3511 Station C Ottawa, Ont. K1Y 4H7 Canada schishol@nortel.com
安大略省渥太华市C站3511号邮政信箱。K1Y 4H7加拿大schishol@nortel.com
David T. Perkins 548 Qualbrook Ct San Jose, CA 95110 USA Phone: 408 394-8702 dperkins@snmpinfo.com " DESCRIPTION "This MIB defines a state extension to the Entity MIB.
David T.Perkins 548加利福尼亚州圣何塞Qualbrook Ct 95110美国电话：408 394-8702dperkins@snmpinfo.com“说明”此MIB定义实体MIB的状态扩展。
Copyright (C) The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200511220000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 131 }
Copyright (C) The Internet Society 2005. This version
of this MIB module is part of RFC 4268; see the RFC
itself for full legal notices."
REVISION "200511220000Z"
DESCRIPTION
"Initial version, published as RFC 4268."
::= { mib-2 131 }
-- Entity State Objects
--实体状态对象
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
entStateTable OBJECT-TYPE SYNTAX SEQUENCE OF EntStateEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of information about state/status of entities. This is a sparse augment of the entPhysicalTable. Entries appear in this table for values of entPhysicalClass [RFC4133] that in this implementation are able to report any of the state or status stored in this table.
entStateTable对象类型EntStateEntry MAX-ACCESS的语法序列不可访问状态当前描述“有关实体状态/状态的信息表。这是entPhysicalTable的稀疏扩充。此表中显示的entPhysicalClass[RFC4133]值的条目在此实现中，可以报告存储在此表中的任何状态。
"
::= { entStateObjects 1 }
"
::= { entStateObjects 1 }
entStateEntry OBJECT-TYPE
SYNTAX EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"State information about this physical entity."
INDEX { entPhysicalIndex }
::= { entStateTable 1 }
entStateEntry OBJECT-TYPE
SYNTAX EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"State information about this physical entity."
INDEX { entPhysicalIndex }
::= { entStateTable 1 }
EntStateEntry ::= SEQUENCE {
entStateLastChanged DateAndTime,
entStateAdmin EntityAdminState,
entStateOper EntityOperState,
entStateUsage EntityUsageState,
entStateAlarm EntityAlarmStatus,
entStateStandby EntityStandbyStatus
}
EntStateEntry ::= SEQUENCE {
entStateLastChanged DateAndTime,
entStateAdmin EntityAdminState,
entStateOper EntityOperState,
entStateUsage EntityUsageState,
entStateAlarm EntityAlarmStatus,
entStateStandby EntityStandbyStatus
}
entStateLastChanged OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is the date and time when the value of any of entStateAdmin, entStateOper, entStateUsage, entStateAlarm, or entStateStandby changed for this entity.
entStateLastChanged对象类型语法DateAndTime MAX-ACCESS只读状态当前描述“此对象的值是更改此实体的entStateAdmin、entStateOper、entStateUsage、EntStateArm或entStateStandby中任何一个值的日期和时间。
If there has been no change since
the last re-initialization of the local system,
this object contains the date and time of
local system initialization. If there has been
no change since the entity was added to the
local system, this object contains the date and
time of the insertion."
::= { entStateEntry 1 }
If there has been no change since
the last re-initialization of the local system,
this object contains the date and time of
local system initialization. If there has been
no change since the entity was added to the
local system, this object contains the date and
time of the insertion."
::= { entStateEntry 1 }
entStateAdmin OBJECT-TYPE SYNTAX EntityAdminState MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative state for this entity.
entStateAdmin对象类型语法EntityAdminState MAX-ACCESS读写状态当前描述“此实体的管理状态。
This object refers to an entities administrative permission to service both other entities within its containment hierarchy as well other users of its services defined by means outside the scope of this MIB.
此对象是指一个实体管理权限，可以为其包含层次结构内的其他实体以及通过此MIB范围外的方式定义的其服务的其他用户提供服务。
Setting this object to 'notSupported' will result in an 'inconsistentValue' error. For entities that do not support administrative state, all set operations will result in an 'inconsistentValue' error.
将此对象设置为“不受支持”将导致“值不一致”错误。对于不支持管理状态的实体，所有设置操作都将导致“值不一致”错误。
Some physical entities exhibit only a subset of the
remaining administrative state values. Some entities
cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this object does not exhibit the
'shuttingDown' state. A value of 'inconsistentValue'
will be returned if attempts are made to set this
object to values not supported by its administrative
model."
::= { entStateEntry 2 }
Some physical entities exhibit only a subset of the
remaining administrative state values. Some entities
cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities cannot be shutdown
gracefully, and hence this object does not exhibit the
'shuttingDown' state. A value of 'inconsistentValue'
will be returned if attempts are made to set this
object to values not supported by its administrative
model."
::= { entStateEntry 2 }
entStateOper OBJECT-TYPE SYNTAX EntityOperState MAX-ACCESS read-only STATUS current DESCRIPTION "The operational state for this entity.
entStateOper对象类型语法EntityOperate MAX-ACCESS只读状态当前描述“此实体的操作状态。
Note that unlike the state model used within the Interfaces MIB [RFC2863], this object does not follow the administrative state. An administrative state of down does not predict an operational state of disabled.
请注意，与接口MIB[RFC2863]中使用的状态模型不同，此对象不遵循管理状态。停机的管理状态不能预测禁用的操作状态。
A value of 'testing' means that entity currently being tested and cannot therefore report whether it is operational or not.
“测试”值表示当前正在测试的实体，因此无法报告其是否可运行。
A value of 'disabled' means that an entity is totally inoperable and unable to provide service both to entities within its containment hierarchy, or to other receivers of its service as defined in ways outside the scope of this MIB.
“禁用”的值表示实体完全不可操作，无法向其包含层次结构内的实体或以本MIB范围外的方式定义的其他服务接收方提供服务。
A value of 'enabled' means that an entity is fully or partially operable and able to provide service both to
“已启用”的值表示实体完全或部分可操作，并且能够向双方提供服务
entities within its containment hierarchy, or to other receivers of its service as defined in ways outside the scope of this MIB.
其包含层次结构中的实体，或以超出此MIB范围的方式定义的其他服务接收方。
Note that some implementations may not be able to
accurately report entStateOper while the
entStateAdmin object has a value other than 'unlocked'.
In these cases, this object MUST have a value
of 'unknown'."
::= { entStateEntry 3 }
Note that some implementations may not be able to
accurately report entStateOper while the
entStateAdmin object has a value other than 'unlocked'.
In these cases, this object MUST have a value
of 'unknown'."
::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE SYNTAX EntityUsageState MAX-ACCESS read-only STATUS current DESCRIPTION "The usage state for this entity.
entStateUsage对象类型语法EntityUsageState MAX-ACCESS只读状态当前描述“此实体的使用状态。
This object refers to an entity's ability to service more physical entities in a containment hierarchy. A value of 'idle' means this entity is able to contain other entities but that no other entity is currently contained within this entity.
此对象指实体为包含层次结构中的更多物理实体提供服务的能力。值“idle”表示该实体可以包含其他实体，但该实体中当前不包含任何其他实体。
A value of 'active' means that at least one entity is contained within this entity, but that it could handle more. A value of 'busy' means that the entity is unable to handle any additional entities being contained in it.
值“active”表示此实体中至少包含一个实体，但它可以处理更多。值“busy”表示实体无法处理其中包含的任何其他实体。
Some entities will exhibit only a subset of the
usage state values. Entities that are unable to ever
service any entities within a containment hierarchy will
always have a usage state of 'busy'. Some entities will
only ever be able to support one entity within its
containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'."
::= { entStateEntry 4 }
Some entities will exhibit only a subset of the
usage state values. Entities that are unable to ever
service any entities within a containment hierarchy will
always have a usage state of 'busy'. Some entities will
only ever be able to support one entity within its
containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'."
::= { entStateEntry 4 }
entStateAlarm OBJECT-TYPE SYNTAX EntityAlarmStatus MAX-ACCESS read-only STATUS current DESCRIPTION "The alarm status for this entity. It does not include the alarms raised on child components within its containment hierarchy.
EntStateArm对象类型语法EntityAlarmStatus MAX-ACCESS只读状态当前描述“此实体的报警状态。它不包括在其包含层次结构中的子组件上引发的报警。
A value of 'unknown' means that this entity is
值“unknown”表示此实体为
unable to report alarm state. Note that this differs from 'indeterminate', which means that alarm state is supported and there are alarms against this entity, but the severity of some of the alarms is not known.
无法报告报警状态。请注意，这不同于“不确定”，这意味着支持报警状态，并且存在针对该实体的报警，但某些报警的严重性未知。
If no bits are set, then this entity supports reporting
of alarms, but there are currently no active alarms
against this entity."
::= { entStateEntry 5 }
If no bits are set, then this entity supports reporting
of alarms, but there are currently no active alarms
against this entity."
::= { entStateEntry 5 }
entStateStandby OBJECT-TYPE SYNTAX EntityStandbyStatus MAX-ACCESS read-only STATUS current DESCRIPTION "The standby status for this entity.
entStateStandby对象类型语法EntityStandbyStatus MAX-ACCESS只读状态当前描述“此实体的待机状态。
Some entities will exhibit only a subset of the
remaining standby state values. If this entity
cannot operate in a standby role, the value of this
object will always be 'providingService'."
::= { entStateEntry 6 }
Some entities will exhibit only a subset of the
remaining standby state values. If this entity
cannot operate in a standby role, the value of this
object will always be 'providingService'."
::= { entStateEntry 6 }
-- Notifications
entStateNotifications OBJECT IDENTIFIER ::= { entityStateMIB 0 }
-- Notifications
entStateNotifications OBJECT IDENTIFIER ::= { entityStateMIB 0 }
entStateOperEnabled NOTIFICATION-TYPE OBJECTS { entStateAdmin, entStateAlarm } STATUS current DESCRIPTION "An entStateOperEnabled notification signifies that the SNMP entity, acting in an agent role, has detected that the entStateOper object for one of its entities has transitioned into the 'enabled' state.
EntStateOperabled通知类型对象{entStateAdmin，entStateAlarm}状态当前描述“EntStateOperabled通知表示以代理角色运行的SNMP实体已检测到其一个实体的entStateOper对象已转换为“已启用”状态。
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled."
::= { entStateNotifications 1 }
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled."
::= { entStateNotifications 1 }
entStateOperDisabled NOTIFICATION-TYPE OBJECTS { entStateAdmin, entStateAlarm } STATUS current DESCRIPTION "An entStateOperDisabled notification signifies that the SNMP entity, acting in an agent role, has detected that the entStateOper object for one of its entities has transitioned into the 'disabled' state.
entStateOperDisabled通知类型对象{entStateAdmin，entStateAlarm}状态当前描述“entStateOperDisabled通知表示充当代理角色的SNMP实体已检测到其一个实体的entStateOper对象已转换为“disabled”状态。
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may affect the physical entity's
ability to stay operationally enabled."
::= { entStateNotifications 2 }
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well as to find out whether
there were any known alarms against the entity at that
time that may affect the physical entity's
ability to stay operationally enabled."
::= { entStateNotifications 2 }
-- Conformance and Compliance
--合规性和合规性
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 2 }
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 2 }
entStateCompliances OBJECT IDENTIFIER
::= { entStateConformance 1 }
entStateCompliances OBJECT IDENTIFIER
::= { entStateConformance 1 }
entStateCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Entity State MIB."
MODULE -- this module
MANDATORY-GROUPS {
entStateGroup
}
GROUP entStateNotificationsGroup
DESCRIPTION
"This group is optional."
OBJECT entStateAdmin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { entStateCompliances 1 }
entStateCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Entity State MIB."
MODULE -- this module
MANDATORY-GROUPS {
entStateGroup
}
GROUP entStateNotificationsGroup
DESCRIPTION
"This group is optional."
OBJECT entStateAdmin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { entStateCompliances 1 }
entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 }
entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 }
entStateGroup OBJECT-GROUP
OBJECTS {
entStateLastChanged,
entStateAdmin,
entStateOper,
entStateUsage,
entStateAlarm,
entStateStandby
}
STATUS current
DESCRIPTION
"Standard Entity State group."
::= { entStateGroups 1}
entStateGroup OBJECT-GROUP
OBJECTS {
entStateLastChanged,
entStateAdmin,
entStateOper,
entStateUsage,
entStateAlarm,
entStateStandby
}
STATUS current
DESCRIPTION
"Standard Entity State group."
::= { entStateGroups 1}
entStateNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
entStateOperEnabled,
entStateOperDisabled
}
STATUS current
DESCRIPTION
"Standard Entity State Notification group."
::= { entStateGroups 2}
entStateNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
entStateOperEnabled,
entStateOperDisabled
}
STATUS current
DESCRIPTION
"Standard Entity State Notification group."
::= { entStateGroups 2}
END
终止
The ENTITY-STATE-TC-MIB defined in section 4 does not define any management objects. Instead, it defines a set of textual conventions that may be used by other MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. The ENTITY-STATE-TC-MIB has therefore no impact on the security of the Internet.
第4节中定义的ENTITY-STATE-TC-MIB未定义任何管理对象。相反，它定义了一组文本约定，其他MIB模块可以使用这些文本约定来定义管理对象。有意义的安全注意事项只能写入定义管理对象的MIB模块中。因此，ENTITY-STATE-TC-MIB对Internet的安全性没有影响。
The ENTITY-STATE-MIB defined in section 5 defines one management object -- entStateAdmin -- that has a MAX-ACCESS clause of read-write. The object may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
第5节中定义的ENTITY-STATE-MIB定义了一个管理对象——entStateAdmin，它有一个读写的MAX-ACCESS子句。在某些网络环境中，该对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
Note that setting the entStateAdmin to 'locked' or 'shuttingDown' can cause disruption of services ranging from those running on a port to those on an entire device, depending on the type of entity. Access to this object should be properly protected.
请注意，根据实体的类型，将entStateAdmin设置为“锁定”或“关闭”可能会导致从端口上运行的服务到整个设备上运行的服务的中断。应适当保护对此对象的访问。
Access to the objects defined in this MIB allows one to figure out what the active and standby resources in a network are. This information can be used to optimize attacks on networks so even read-only access to this MIB should be properly protected.
通过访问此MIB中定义的对象，可以确定网络中的活动和备用资源是什么。此信息可用于优化网络攻击，因此即使对此MIB的只读访问也应得到适当保护。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (entities) that have legitimate rights to indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商有责任确保授予访问此MIB模块实例权限的SNMP实体正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（实体）访问对象。
This document is a product of the Entity MIB Working Group.
本文件是实体MIB工作组的产品。
[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月。
[RFC2578] 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.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.，和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC4133] Bierman, A. and K. McCloghrie, "Entity MIB (Version 3)", RFC 4133, August 2005.
[RFC4133]Bierman，A.和K.McCloghrie，“实体MIB（版本3）”，RFC 41332005年8月。
[RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC 2790, March 2000.
[RFC2790]Waldbusser，S.和P.Grillo，“主机资源MIB”，RFC 27902000年3月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“使用SMIv2的接口组MIB”，RFC 28632000年6月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3877] Chisholm, S. and D. Romascanu, "Alarm Management Information Base (MIB)", RFC 3877, September 2004.
[RFC3877]Chisholm，S.和D.Romascanu，“报警管理信息库（MIB）”，RFC 3877，2004年9月。
[RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects for Bridges", RFC 4188, September 2005.
[RFC4188]Norseth，K.和E.Bell，“网桥托管对象的定义”，RFC 4188，2005年9月。
[X.731] ITU Recommendation X.731, "Information Technology - Open Systems Interconnection - System Management: State Management Function", 1992.
[X.731]国际电联建议X.731，“信息技术-开放系统互连-系统管理：状态管理功能”，1992年。
Authors' Addresses
作者地址
Sharon Chisholm Nortel Networks PO Box 3511, Station C Ottawa, Ontario, K1Y 4H7 Canada
Sharon Chisholm Nortel Networks加拿大安大略省渥太华C站3511信箱，K1Y 4H7
EMail: schishol@nortel.com
EMail: schishol@nortel.com
David T. Perkins 548 Qualbrook Ct San Jose, CA 95110 USA
David T.Perkins 548 Qualbrook Ct圣何塞，加利福尼亚州95110美国
Phone: 408 394-8702 EMail: dperkins@snmpinfo.com
电话：408 394-8702电子邮件：dperkins@snmpinfo.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2005).
版权所有（C）互联网协会（2005年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat 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 on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。