draft-ietf-eos-snmpxproto-mib-01.txt   draft-ietf-eos-snmpxproto-mib-02.txt 
EOS Working Group S. Chisholm EOS Working Group S. Chisholm
Internet Draft Nortel Networks Internet Draft Nortel Networks
Document: draft-ietf-eos-snmpxproto-mib-01.txt Document: draft-ietf-eos-snmpxproto-mib-02.txt
Category: Standards Track Category: Standards Track
Expiration Date: January 2002 July 16 2001 Expiration Date: August 2002 February 2002
SNMP Extended Protocol MIB SNMP Extended Protocol 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 38 skipping to change at page 1, line 38
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes SNMP protocol extensions supported by In particular, it describes SNMP protocol operations supported by
an SNMP entity. an SNMP entity.
Table of Contents Table of Contents
1. The SNMP Management Framework 1. The SNMP Management Framework
2. Introduction 2. Introduction
3. Extended Protocol Management 3. Extended Protocol Management
3.1. SNMP Extensions 3.1. SNMP Extensions
3.2. Interoperability 3.2. Interoperability
3.3. Relation to Agent Capabilities 3.3. Relation to MAX-ACCESS clause
3.4. Relation to Agent Capabilities
4. MIB Overview 4. MIB Overview
5. Definitions 5. IANA Considerations
6. IANA Considerations 6. Definitions
7. Security Considerations 7. Security Considerations
8. Author's Address 8. Author's Address
9. Acknowledgements 9. Acknowledgements
10. References 10. References
11. Full Copyright Statement 11. Full Copyright Statement
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
skipping to change at page 3, line 46 skipping to change at page 3, line 46
[RFC2573] and the view-based access control mechanism described [RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575]. in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570]. can be found in RFC 2570 [RFC2570].
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. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is ;'ant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Introduction 2. Introduction
skipping to change at page 4, line 17 skipping to change at page 4, line 17
Traditionally, features have been added to SNMP by developing a new Traditionally, features have been added to SNMP by developing a new
version of the protocol that supports these new features. Currently, version of the protocol that supports these new features. Currently,
SNMP entities that conform to [RFC 2571] are expected to implement SNMP entities that conform to [RFC 2571] are expected to implement
all the protocol functionality defined by the standards. all the protocol functionality defined by the standards.
The idea, moving forward, is to add features to SNMP in a more The idea, moving forward, is to add features to SNMP in a more
modular fashion and without necessarily increasing the version modular fashion and without necessarily increasing the version
number. Since the protocol version number is no longer sufficient number. Since the protocol version number is no longer sufficient
information to determine which protocol features an SNMP entity information to determine which protocol features an SNMP entity
supports, another method is required. This memo defines a MIB to be supports, another method is required. This memo defines a MIB to be
used to determine the SNMP capabilities of an SNMP entity, above and used to determine the SNMP capabilities of an SNMP entity,
beyond the base features of its protocol version. independent of its protocol version.
Requirements of this feature are:
o It must be easy to determine the features that an SNMP entity
supports;
This feature is not required to:
o List base features of the SNMPv3 protocol.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
3. Extended Protocol Management 3. Extended Protocol Management
3.1 SNMP Extensions 3.1 SNMP Extensions
SNMP extensions are those standard protocol extensions that are SNMP extensions are those standard protocol extensions that are
skipping to change at page 5, line 31 skipping to change at page 5, line 31
| |Command | | | |Command | |
| |Generator +--------+ | |Generator +--------+
+------------+Protocol | +------------+Protocol |
|Operations | |Operations |
|v2 | |v2 |
+------------+ +------------+
An SNMP entity that supports version 2 of the protocol operations An SNMP entity that supports version 2 of the protocol operations
[RFC1905] MUST be able to communicate with an SNMP entity supporting [RFC1905] MUST be able to communicate with an SNMP entity supporting
extended protocol operations. This communication MUST be in a manner extended protocol operations. This communication MUST be in a manner
consistent with communicating with an SNMP entity which supports consistent with communicating with an SNMP entity that supports
version 2 of the protocol operations. Similarly, an SNMP entity that version 2 of the protocol operations. Similarly, an SNMP entity that
supports extended protocol operations MUST be able to communicate supports extended protocol operations MUST be able to communicate
with SNMP entities which support version 2 of the protocol with SNMP entities which support version 2 of the protocol
operations. operations.
An SNMP entity that supports the extended protocol operations MUST An SNMP entity that supports the extended protocol operations SHOULD
support protocol operations as defined in version 2 of the protocol support protocol operations as defined in version 2 of the protocol
operations [RFC1905]. Traditional sets may be an exception to this. operations [RFC1905]. The get-request operation MUST be supported.
Details to be determined.
A command generator SHOULD query a command responder before issuing A command generator SHOULD query a command responder before issuing
an extended protocol operation to determine if the command responder an extended protocol operation to determine if the command responder
supports the operation. supports the operation.
An SNMP entity MUST only issue a response using an extended protocol An SNMP entity MUST only issue a response using an extended protocol
feature if it received the request using the extended protocol feature if it received the request using the extended protocol
feature. feature.
If an SNMP entity receives an extended protocol feature it does not If an SNMP entity receives an extended protocol feature it does not
understand, it MUST follow the unknown PDU response mechanism as understand, it MUST follow the unknown PDU response mechanism as
defined in [RFC2262] section 4.2.2.1 defined in [RFC2262] section 4.2.2.1
3.3 Relation to Agent Capabilities 3.3 Relation to MAX-ACCESS Clause
MAX-ACCESS, as defined in [RFC1902], indicates whether it makes
"protocol sense" to read, write and/or create an instance of the
object, or to include its value in a notification. It is useful for
this discussion to term read, write, create and accessible for
notify as different classes of access to MIB objects. In the case of
the protocol operations defined in [RFC1905], the get-request,
get-next-request, get-bulk-request would all belong to the read
class. The set-request would belong to the write class and the
create class. The inform-request and the snmpV2-trap would both
belong to the accessible for notify class. The protocol capabilities
identified using this memo indicate which specific protocol
operations are supported on the object if the appropriate class of
access is allowed.
If a protocol operation is not supported on a given object, it only
affects the protocol capabilities statement, if its access class is
supported for that object. For example, if an object is read-only
and therefore does not support the write class, the system can still
claim support of the set-request operation so long as all objects
that do support the write class support the set-request. However, if
the object does not support the get-bulk-request, the system cannot
claim support of this protocol operation as this object supports the
read class.
3.4 Relation to Agent Capabilities
Agent capability statements are used when describing capabilities of Agent capability statements are used when describing capabilities of
agents with respect to object definitions. The extended protocol agents with respect to object definitions. The extended protocol
MIB is used when describing the capabilities of agents with respect MIB is used when describing the capabilities of agents with respect
to protocol operations. to protocol operations.
4. MIB Overview 4. MIB Overview
The snmpXProtoSystem object indicates which protocol extensions are The snmpXProtoSystem object indicates which protocol operations are
supported by the entire SNMP entity. snmpXProtoSubTreeTable supported by the entire SNMP entity. snmpXProtoSubTreeTable
indicates additional protocol extensions supported on particular MIB indicates additional protocol operations supported on particular MIB
sub trees. sub trees.
5. Definitions 5. IANA Considerations
IANASnmpProtocol is a bitmap that indicates which standard SNMP
operations an SNMP entity supports. New values for this bitmap may
be given out for SNMP protocol extensions published as standards
track RFCs.
The following shall be used as the initial values, but the latest
values for these textual conventions should be obtained from IANA:
IANA-SNMP-PROTOCOL-TC DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ianaSnmpProtoNumbers MODULE-IDENTITY
LAST-UPDATED "200202200000Z"
ORGANIZATION "IANA"
CONTACT-INFO
"Postal: Internet Assigned Numbers Authority
Internet Corporation for Assigned Names
and Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292-6601
USA
Tel: +1 310-823-9358
E-Mail: iana@iana.org"
DESCRIPTION
"The MIB module defines textual conventions for use
in identifying SNMP protocol operations."
::= { mib-2 xx }
-- IANA IANASnmpProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Standard SNMP protocol operations."
SYNTAX BITS
{
getRequest (0),
getNextRequest (1),
getBulkRequest (2),
response (3),
setRequest (4),
informRequest (5),
snmpV2Trap (6),
report (7)
} END
6. Definitions
SNMP-EXTENDED-PROTOCOL-MIB DEFINITIONS ::= BEGIN SNMP-EXTENDED-PROTOCOL-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, mib-2 FROM SNMPv2-SMI Unsigned32, mib-2 FROM SNMPv2-SMI
IANASnmpExtendedProtocol FROM SNMP-X-PROTOCOL-TC IANASnmpProtocol FROM IANA-SNMP-PROTOCOL-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
snmpXProtoMIB MODULE-IDENTITY snmpXProtoMIB MODULE-IDENTITY
LAST-UPDATED "200107160000Z" LAST-UPDATED "200202200000Z"
ORGANIZATION "IETF Evolution of SNMP Working Group" ORGANIZATION "IETF Evolution of SNMP Working Group"
CONTACT-INFO CONTACT-INFO
" 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"
DESCRIPTION DESCRIPTION
"The MIB module describes the SNMP protocol "The MIB module describes the SNMP protocol
extensions supported by this SNMP entity." operations supported by this SNMP entity."
REVISION "200107160000Z" REVISION "200202200000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
::= { mib-2 XX } ::= { mib-2 xx }
snmpXProtoObjects OBJECT IDENTIFIER ::= { snmpXProtoMIB 1 } snmpXProtoObjects OBJECT IDENTIFIER ::= { snmpXProtoMIB 1 }
snmpXProtoConformance OBJECT IDENTIFIER ::= { snmpXProtoMIB 3 } snmpXProtoConformance OBJECT IDENTIFIER ::= { snmpXProtoMIB 3 }
snmpXProtoCompliances OBJECT IDENTIFIER snmpXProtoCompliances OBJECT IDENTIFIER
::= { snmpXProtoConformance 1 } ::= { snmpXProtoConformance 1 }
snmpXProtoSystem OBJECT-TYPE snmpXProtoSystem OBJECT-TYPE
SYNTAX IANASnmpExtendedProtocol SYNTAX IANASnmpProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The standard SNMP protocol operations supported "The standard SNMP protocol operations supported
by this system above and beyond basic protocol by this SNMP entity on all objects with appropriate
support." access permissions. For example, SNMP sets may be
included in this list, even if the MAX-ACCESS of
some objects is read-only."
::= { snmpXProtoObjects 1 } ::= { snmpXProtoObjects 1 }
-- Extra Protocol Support per SubTree -- Extra Protocol Support per SubTree
snmpXProtoSubTreeTable OBJECT-TYPE snmpXProtoSubTreeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpXProtoSubTreeEntry SYNTAX SEQUENCE OF SnmpXProtoSubTreeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A table of additional protocol extensions to SNMP DESCRIPTION "A table of additional SNMP protocol operations
supported by specific subTrees." supported on objects in the specific subTrees."
::= { snmpXProtoObjects 2 } ::= { snmpXProtoObjects 2 }
snmpXProtoSubTreeEntry OBJECT-TYPE snmpXProtoSubTreeEntry OBJECT-TYPE
SYNTAX SnmpXProtoSubTreeEntry SYNTAX SnmpXProtoSubTreeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An additional protocol extension to SNMP DESCRIPTION "A MIB subtree that supports additional
supported by part of the MIB of this SNMP entity." protocol operations above that specified
in snmpXProtoSystem."
INDEX { snmpXProtoSubTreeIndex } INDEX { snmpXProtoSubTreeIndex }
::= { snmpXProtoSubTreeTable 1 } ::= { snmpXProtoSubTreeTable 1 }
SnmpXProtoSubTreeEntry ::= SEQUENCE { SnmpXProtoSubTreeEntry ::= SEQUENCE {
snmpXProtoSubTreeIndex Unsigned32, snmpXProtoSubTreeIndex Unsigned32,
snmpXProtoSubTreeBranch OBJECT IDENTIFIER, snmpXProtoSubTreeBranch OBJECT IDENTIFIER,
snmpXProtoSubTreeFeature IANASnmpExtendedProtocol snmpXProtoSubTreeFeature IANASnmpProtocol
} }
snmpXProtoSubTreeIndex OBJECT-TYPE snmpXProtoSubTreeIndex OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295) SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An arbitrary index into this table." DESCRIPTION "An arbitrary index into this table."
::= { snmpXProtoSubTreeEntry 1 } ::= { snmpXProtoSubTreeEntry 1 }
snmpXProtoSubTreeBranch OBJECT-TYPE snmpXProtoSubTreeBranch OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OID which identifies this SubTree feature." "The OID that identifies this MIB SubTree."
::= { snmpXProtoSubTreeEntry 2 } ::= { snmpXProtoSubTreeEntry 2 }
snmpXProtoSubTreeFeature OBJECT-TYPE snmpXProtoSubTreeFeature OBJECT-TYPE
SYNTAX IANASnmpExtendedProtocol SYNTAX IANASnmpProtocol
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The standard SNMP protocol operations supported "The standard SNMP protocol operations supported
by this subTree above and beyond protocol by this subTree above and beyond protocol
support as indicated by snmpXProtoSystem." support as indicated by snmpXProtoSystem."
::= { snmpXProtoSubTreeEntry 3 } ::= { snmpXProtoSubTreeEntry 3 }
snmpXProtoCompliance MODULE-COMPLIANCE snmpXProtoCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 8, line 47 skipping to change at page 10, line 23
snmpXProtoSubTreeFeature, snmpXProtoSubTreeFeature,
snmpXProtoSubTreeBranch snmpXProtoSubTreeBranch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"SubTree specific snmpXProto group." "SubTree specific snmpXProto group."
::= { snmpXProtoGroups 2} ::= { snmpXProtoGroups 2}
END END
6 IANA Considerations
IANASnmpExtendedProtocol is a bitmap which indicates which standard
extensions to SNMP an SNMP entity supports. It may be given out for
SNMP protocol extensions published as standards track RFCs.
7. Security Considerations 7. Security Considerations
There are no management objects defined in this MIB that have a There are no management objects defined in this MIB that have a
MAX-ACCESS clause of read-write and/or read-create. So, if this MIB MAX-ACCESS clause of read-write and/or read-create. So, if this MIB
is implemented correctly, then there is no risk that an intruder can is implemented correctly, then there is no risk that an intruder can
alter or create any management objects of this MIB via direct SNMP alter or create any management objects of this MIB via direct SNMP
SET operations. SET operations.
8. Author's Address 8. Author's Address
skipping to change at page 10, line 55 skipping to change at page 12, line 24
Model (USM) for version 3 of the Simple Network Management Model (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2274, January 1998. Protocol (SNMPv3)", RFC 2274, January 1998.
[RFC2275] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC2275] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2275, January 1998. Management Protocol (SNMP)", RFC 2275, January 1998.
[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.
[RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
RFC 3014, November 2000 "Protocol Operations for SNMPv2", RFC 1905, January 1996
[RFC2262] Case, J., Harrington, D, Presuhn, R., Wijnen, B.,
"Message Processing and Dispatching for the
Simple Network Management Protocol (SNMP)", RFC 2262,
January 1998
11. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). 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
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 29 change blocks. 
49 lines changed or deleted 119 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/