draft-ietf-entmib-state-03.txt   draft-ietf-entmib-state-04.txt 
Entity MIB Working Group S. Chisholm Entity MIB Working Group S. Chisholm
Internet Draft Nortel Networks Internet Draft Nortel Networks
Document: draft-ietf-entmib-state-03.txt D. Perkins Document: draft-ietf-entmib-state-04.txt D. Perkins
Category: Standards Track SNMPinfo Category: Standards Track SNMPinfo
Expiration Date: August 2004 February 2004 Expiration Date: January 2005 July 2004
Entity State MIB Entity State MIB
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 46 skipping to change at page 1, line 47
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes extensions to the Entity MIB to In particular, it describes extensions to the Entity MIB to
provide information about the state of physical entities. provide information about the state of physical entities.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
2. Entity State 2. Entity State
2.1. Hierarchical State Management 2.1. Hierarchical State Management
2.2. Entity Redundancy 2.2. Entity Redundancy
2.3. Physical Entity Users
2.4. Physical Class Behaviour
3. Relationship to Other MIBs 3. Relationship to Other MIBs
3.1. Relation to Interfaces MIB 3.1. Relation to Interfaces MIB
3.2. Relation to Alarm MIB 3.2. Relation to Alarm MIB
3.3. Relation to Bridge MIB 3.3. Relation to Bridge MIB
3.4. Relation to Host Resource MIB 3.4. Relation to Host Resource MIB
4. Definitions 4. Textual Conventions
5. Security Considerations 5. Definitions
6. Intellectual Property 6. Security Considerations
7. Authors' Addresses 7. Intellectual Property
8. Acknowledgements 8. Authors' Addresses
9. References 9. Acknowledgements
10. Full Copyright Statement 10. References
11. Full Copyright Statement
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 38 skipping to change at page 4, line 38
All state objects in this memo are raw state. All state objects in this memo are raw state.
2.2 Entity Redundancy 2.2 Entity Redundancy
While this memo is not attempting to address the entire problem While this memo is not attempting to address the entire problem
space around redundancy, the entStateStandby object provides an space around redundancy, the entStateStandby object provides an
important piece of state information for entities, which helps important piece of state information for entities, which helps
identify which pieces of redundant equipment are currently providing identify which pieces of redundant equipment are currently providing
service, and which are waiting in either hot or cold standby mode. service, and which are waiting in either hot or cold standby mode.
2.3 Physical Entity Users
There are three ways to define the 'user' of a physical entity
1. Direct Containment in physical hierarchy
2. Anywhere in physical hierarchy
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.
Administrative, operational, alarm and standby state use all three
definitions of 'user'. Usage state only supports the concept of
direct containment to simplify implementations of this object.
2.4 Physical Class Behaviour
This MIB makes no effort to standardize on the behaviours and
characteristics of the various physical classes [RFC2737], 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 can not support part
or all of a particular state.
3 Relation to other MIBs 3 Relation to other MIBs
3.1 Relationship to the Interfaces MIB 3.1 Relationship to the Interfaces MIB
The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which
has states of up, down and testing and the ifOperStatus object, has states of up, down and testing and the ifOperStatus object,
which has states of up, down, testing, unknown, dormant, notPresent which has states of up, down, testing, unknown, dormant, notPresent
and lowerLayerDown. and lowerLayerDown.
An ifAdminStatus of 'up' is equivalent to setting the entStateAdmin An ifAdminStatus of 'up' is equivalent to setting the entStateAdmin
skipping to change at page 6, line 5 skipping to change at page 6, line 32
provides an operational state for devices. For entities that provides an operational state for devices. For entities that
logically correspond to the concept of a device, a value of logically correspond to the concept of a device, a value of
'unknown' for hrDeviceStatus corresponds to an entStateOper value of 'unknown' for hrDeviceStatus corresponds to an entStateOper value of
'unavailable'. A value of 'running' corresponds to an entStateOper 'unavailable'. A value of 'running' corresponds to an entStateOper
value of 'enabled'. A value of 'warning' also corresponds to an value of 'enabled'. A value of 'warning' also corresponds to an
entStateOper value of 'enabled', but with appropriate bits set in entStateOper value of 'enabled', but with appropriate bits set in
the entStateAlarm object to indicate the alarms corresponding to the the entStateAlarm object to indicate the alarms corresponding to the
unusual error condition detected. A value of 'testing' or 'down' is unusual error condition detected. A value of 'testing' or 'down' is
equivalent to an entStateOper value of 'disabled'. equivalent to an entStateOper value of 'disabled'.
4. Definitions 4. Textual Conventions
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN ENTITY-STATE-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
FROM SNMPv2-SMI TEXTUAL-CONVENTION FROM SNMPv2-TC;
TEXTUAL-CONVENTION, DateAndTime
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
entPhysicalIndex
FROM ENTITY-MIB;
entityStateMIB MODULE-IDENTITY entityStateTc MODULE-IDENTITY
LAST-UPDATED "200402150000Z" LAST-UPDATED "200407190000Z"
ORGANIZATION "IETF Entity MIB Working Group" ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO CONTACT-INFO
" General Discussion: entmib@ietf.org " General Discussion: entmib@ietf.org
To Subscribe: To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib 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 Sharon Chisholm
Nortel Networks Nortel Networks
skipping to change at page 6, line 35 skipping to change at page 7, line 4
http://www.ietf.org/mailman/listinfo/entmib 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 Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511 Station C PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7 Ottawa, Ont. K1Y 4H7
Canada Canada
schishol@nortelnetworks.com schishol@nortelnetworks.com
David T. Perkins David T. Perkins
548 Qualbrook Ct 548 Qualbrook Ct
San Jose, CA 95110 San Jose, CA 95110
USA USA
Phone: 408 394-8702 Phone: 408 394-8702
dperkins@snmpinfo.com dperkins@snmpinfo.com"
"
DESCRIPTION DESCRIPTION
"This MIB defines a state extension to the Entity MIB. "This MIB defines a state textual conventions.
Copyright (C) The Internet Society 2004. This version Copyright (C) The Internet Society 2004. This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove -- RFC Ed.: replace yyyy with actual RFC number & remove
-- this note -- this note
REVISION "200402150000Z" REVISION "200407190000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYYY." "Initial version, published as RFC yyyy."
-- RFC-Editor assigns yyyy -- RFC-Editor assigns yyyy
::= { mib-2 XX } -- to be assigned by IANA ::= { mib-2 XX } -- to be assigned by IANA
-- Textual conventions
AdminState ::= TEXTUAL-CONVENTION AdminState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the various possible administrative states. " Represents the various possible administrative states.
A value of 'locked' means the resource is administratively A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not use. A value of 'unlocked' means the resource is not
skipping to change at page 8, line 52 skipping to change at page 9, line 17
alarms are active against the resource. When the value alarms are active against the resource. When the value
of 'major' is set, one or more major alarms are active of 'major' is set, one or more major alarms are active
against the resource. When the value of 'minor' is set, against the resource. When the value of 'minor' is set,
one or more minor alarms are active against the resource. one or more minor alarms are active against the resource.
When the value of 'warning' is set, one or more warning When the value of 'warning' is set, one or more warning
alarms are active against the resource. When the value alarms are active against the resource. When the value
of 'indeterminate' is set, one or more alarms whose of of 'indeterminate' is set, one or more alarms whose of
perceived severity cannot be determined are active perceived severity cannot be determined are active
against this resource. against this resource.
When the value of 'alarmOutstanding' is set, one or more A value of 'unavailable' means that this resource is
alarms is active against the resource. The fault may unable to report alarm state."
or may not be disabling. This bit provides a high-level
summary that can be used to determine whether or not
to examine the rest of the values. A value of
'unavailable' means that this resource is unable to
report alarm state."
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX BITS SYNTAX BITS
{ {
unavailable (0), unavailable (0),
underRepair(1), underRepair(1),
critical(2), critical(2),
major(3), major(3),
minor(4), minor(4),
alarmOutstanding(5),
-- The following are not defined in X.733 -- The following are not defined in X.733
warning (6), warning (5),
indeterminate (7) indeterminate (6)
} }
StandbyStatus ::= TEXTUAL-CONVENTION StandbyStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the possible values of standby status. " Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to providing service, but it will be immediately able to
take over the role of the resource to be backed-up, take over the role of the resource to be backed-up,
skipping to change at page 10, line 4 skipping to change at page 10, line 13
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
unavailable (1), unavailable (1),
hotStandby(2), hotStandby(2),
coldStandby(3), coldStandby(3),
providingService(4) providingService(4)
} }
END
5. Definitions
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
entPhysicalIndex
FROM ENTITY-MIB
AdminState, OperState, UsageState, AlarmStatus, StandbyStatus
FROM ENTITY-STATE-TC;
entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200407190000Z"
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
Sharon Chisholm
Nortel Networks
PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7
Canada
schishol@nortelnetworks.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.
Copyright (C) The Internet Society 2004. This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove
-- this note
REVISION "200407190000Z"
DESCRIPTION
"Initial version, published as RFC YYYY."
-- RFC-Editor assigns yyyy
::= { mib-2 XX } -- to be assigned by IANA
-- Entity State Objects -- Entity State Objects
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 } entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
entStateTable OBJECT-TYPE entStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntStateEntry SYNTAX SEQUENCE OF EntStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of information about state/status of entities. "A table of information about state/status of entities.
skipping to change at page 11, line 13 skipping to change at page 12, line 28
no change since the entity was added to the no change since the entity was added to the
local system, this object contains the date and local system, this object contains the date and
time of the insertion" time of the insertion"
::= { entStateEntry 1 } ::= { entStateEntry 1 }
entStateAdmin OBJECT-TYPE entStateAdmin OBJECT-TYPE
SYNTAX AdminState SYNTAX AdminState
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative state for this entity. "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.
The administrative state for this entity.
Setting this object to 'notSupported' will result Setting this object to 'notSupported' will result
in an 'inconsistentValue' error. For entities that in an 'inconsistentValue' error. For entities that
do not support administrative state, all set do not support administrative state, all set
operations will result in an 'inconsistentValue' operations will result in an 'inconsistentValue'
error error
Some physical entities exhibit only a subset of the Some physical entities exhibit only a subset of the
remaining administrative state values. Some entities remaining administrative state values. Some entities
cannot be locked, and hence this object exhibits only cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities can not be shutdown the 'unlocked' state. Other entities can not be shutdown
skipping to change at page 12, line 19 skipping to change at page 13, line 40
of 'unavailable'." of 'unavailable'."
::= { entStateEntry 3 } ::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE entStateUsage OBJECT-TYPE
SYNTAX UsageState SYNTAX UsageState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The usage state for this entity. "The usage state for this entity.
Note that in the context of a physical entity, this This object refers to an entity's ability to service more
object refers to an entity's ability to service more
physical entities in a containment hierarchy. A value physical entities in a containment hierarchy. A value
of 'idle' means this entity is able to contain other of 'idle' means this entity is able to contain other
entities but that no other entity is currently entities but that no other entity is currently
contained within this entity. contained within this entity.
A value of 'active' means that at least one entity is A value of 'active' means that at least one entity is
contained within this entity, but that it could handle contained within this entity, but that it could handle
more. A value of 'busy' means that the entity is unable more. A value of 'busy' means that the entity is unable
to handle any additional entities being contained in it. to handle any additional entities being contained in it.
skipping to change at page 15, line 16 skipping to change at page 16, line 38
entStateOperEnabled, entStateOperEnabled,
entStateOperDisabled entStateOperDisabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Standard Entity State Notification group." "Standard Entity State Notification group."
::= { entStateGroups 2} ::= { entStateGroups 2}
END END
5. Security Considerations 6. Security Considerations
There is one management object defined in this MIB that has a There is one management object defined in this MIB that has a
MAX-ACCESS clause of read-write. The object may be considered MAX-ACCESS clause of read-write. The object may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
The following object is defined with a MAX-ACCESS clause of The following object is defined with a MAX-ACCESS clause of
read-write: entStateAdmin. read-write: entStateAdmin.
skipping to change at page 16, line 5 skipping to change at page 17, line 28
Note that setting the entStateAdmin to 'locked' or 'shuttingDown' Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
can cause disruption of services ranging from those running on a can cause disruption of services ranging from those running on a
port to those on an entire device, depending on the type of entity. port to those on an entire device, depending on the type of entity.
Access to this object should be properly protected. Access to this object should be properly protected.
Access to the objects defined in this MIB allows one to figure out Access to the objects defined in this MIB allows one to figure out
what the active and standby resources in a network are. This what the active and standby resources in a network are. This
information can be used to optimize attacks on networks so even information can be used to optimize attacks on networks so even
read-only access to this MIB should be properly protected. read-only access to this MIB should be properly protected.
6. Intellectual Property 7. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances
skipping to change at page 16, line 27 skipping to change at page 17, line 50
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
7. Authors' Addresses 8. Authors' Addresses
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511, Station C PO Box 3511, Station C
Ottawa, Ontario, K1Y 4H7 Ottawa, Ontario, K1Y 4H7
Canada Canada
Email: schishol@nortelnetworks.com Email: schishol@nortelnetworks.com
David T. Perkins David T. Perkins
548 Qualbrook Ct 548 Qualbrook Ct
San Jose, CA 95110 San Jose, CA 95110
USA USA
Phone: 408 394-8702 Phone: 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
8. Acknowledgments 9. Acknowledgments
This document is a product of the Entity MIB Working Group. This document is a product of the Entity MIB Working Group.
9. References 10. References
9.1 Normative 10.1 Normative
[ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB", [ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB",
draft-ietf-disman-alarm-mib-18.txt, February 2004 draft-ietf-disman-alarm-mib-18.txt, February 2004
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
skipping to change at page 17, line 26 skipping to change at page 18, line 48
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)", [RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)",
December 1999. December 1999.
[X.731] ITU Recommendation X.731, "Information Technology - Open [X.731] ITU Recommendation X.731, "Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function", 1992 Management Function", 1992
8.2 Informative References 10.2 Informative References
[RFC1493] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [RFC1493] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493, "Definitions of Managed Objects for Bridges", RFC 1493,
July 1993 July 1993
[RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB", [RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB",
RFC 2790, March 2000 RFC 2790, March 2000
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB using SMIv2", RFC2863, June 2000 MIB using SMIv2", RFC2863, June 2000
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
skipping to change at page 17, line 42 skipping to change at page 19, line 14
[RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB", [RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB",
RFC 2790, March 2000 RFC 2790, March 2000
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB using SMIv2", RFC2863, June 2000 MIB using SMIv2", RFC2863, June 2000
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
10. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/