draft-ietf-eos-snmpxproto-mib-00.txt   draft-ietf-eos-snmpxproto-mib-01.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-00.txt Document: draft-ietf-eos-snmpxproto-mib-01.txt
Category: Standards Track Category: Standards Track
Expiration Date: October 2001 April 18 2001 Expiration Date: January 2002 July 16 2001
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 44 skipping to change at page 1, line 46
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 extensions 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. Standard Extensions 3.1. SNMP Extensions
3.2. Vendor Extensions 3.2. Interoperability
3.3. Interoperability 3.3. Relation to Agent Capabilities
3.4. Relation to Agent Capabilities
4. MIB Overview 4. MIB Overview
5. Definitions 5. Definitions
6. IANA Considerations 6. IANA Considerations
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
skipping to change at page 4, line 23 skipping to change at page 4, line 23
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, above and
beyond the base features of its protocol version. beyond the base features of its protocol version.
Requirements of this feature are: Requirements of this feature are:
o It must be easy to determine the features that an SNMP entity o It must be easy to determine the features that an SNMP entity
supports; supports;
o It MUST be extensible so that vendor defined features may appear
in the capabilities list.
This feature is not required to: This feature is not required to:
o List base features of the SNMPv3 protocol. 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 Standard Extensions 3.1 SNMP Extensions
Standard protocol extensions are those extensions that are developed SNMP extensions are those standard protocol extensions that are
within the IETF and published in standards track RFCs. developed within the IETF and published in standards track RFCs.
3.2 Vendor Extensions 3.2 Interoperability
+------------+
|Command |
+--------+Generator |-----------+
| |Extended | |
| |Protocol | |
| +------------+ |
| |
| |
| +--------+------------+
+------+-----+ |Command Responder |
|Command | | |
|Responder | | Extended Protocol |
|Protocol | +--------+------------+
|Operations | |
|v2 | |
+-----+------+ |
| +------------+ |
| |Command | |
| |Generator +--------+
+------------+Protocol |
|Operations |
|v2 |
+------------+
Vendor Extensions are proprietary protocol extensions developed by a An SNMP entity that supports version 2 of the protocol operations
particular vendor. They are not part of standard SNMP, and should [RFC1905] MUST be able to communicate with an SNMP entity supporting
not be positioned as such. extended protocol operations. This communication MUST be in a manner
consistent with communicating with an SNMP entity which supports
version 2 of the protocol operations. Similarly, an SNMP entity that
supports extended protocol operations MUST be able to communicate
with SNMP entities which support version 2 of the protocol
operations.
3.3 Interoperability An SNMP entity that supports the extended protocol operations MUST
support protocol operations as defined in version 2 of the protocol
operations [RFC1905]. Traditional sets may be an exception to this.
Details to be determined.
A command generator SHOULD query a command responder before issuing
an extended protocol operation to determine if the command responder
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.4 Relation to Agent Capabilities 3.3 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 SNMP Extended Protocol MIB consists of snmpXProtoStandard to The snmpXProtoSystem object indicates which protocol extensions are
indicate which standard PDU extensions are supported and supported by the entire SNMP entity. snmpXProtoSubTreeTable
snmpXProtoVendorTable to indicate which vendor extensions are indicates additional protocol extensions supported on particular MIB
supported. sub trees.
5. Definitions 5. 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
DisplayString FROM SNMPv2-TC
IANASnmpExtendedProtocol FROM SNMP-X-PROTOCOL-TC IANASnmpExtendedProtocol FROM SNMP-X-PROTOCOL-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
snmpXProtoMIB MODULE-IDENTITY snmpXProtoMIB MODULE-IDENTITY
LAST-UPDATED "200104180000Z" LAST-UPDATED "200107160000Z"
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." extensions supported by this SNMP entity."
REVISION "200104180000Z" REVISION "200107160000Z"
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
snmpXProtoStandard OBJECT-TYPE
SYNTAX IANASnmpExtendedProtocol SYNTAX IANASnmpExtendedProtocol
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 system above and beyond basic protocol
support." support."
::= { snmpXProtoObjects 1 } ::= { snmpXProtoObjects 1 }
snmpXProtoVendorTable OBJECT-TYPE -- Extra Protocol Support per SubTree
SYNTAX SEQUENCE OF SnmpXProtoVendorEntry
snmpXProtoSubTreeTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpXProtoSubTreeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A table of vendor protocol extensions to SNMP DESCRIPTION "A table of additional protocol extensions to SNMP
supported by SNMP entity." supported by specific subTrees."
::= { snmpXProtoObjects 2 } ::= { snmpXProtoObjects 2 }
snmpXProtoVendorEntry OBJECT-TYPE snmpXProtoSubTreeEntry OBJECT-TYPE
SYNTAX SnmpXProtoVendorEntry SYNTAX SnmpXProtoSubTreeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A vendor protocol extensions to SNMP DESCRIPTION "An additional protocol extension to SNMP
supported by SNMP entity." supported by part of the MIB of this SNMP entity."
INDEX { snmpXProtoVendorIndex } INDEX { snmpXProtoSubTreeIndex }
::= { snmpXProtoVendorTable 1 } ::= { snmpXProtoSubTreeTable 1 }
SnmpXProtoVendorEntry ::= SEQUENCE { SnmpXProtoSubTreeEntry ::= SEQUENCE {
snmpXProtoVendorIndex Unsigned32, snmpXProtoSubTreeIndex Unsigned32,
snmpXProtoVendorFeature OBJECT IDENTIFIER, snmpXProtoSubTreeBranch OBJECT IDENTIFIER,
snmpXProtoVendorDocument DisplayString snmpXProtoSubTreeFeature IANASnmpExtendedProtocol
} }
snmpXProtoVendorIndex 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."
::= { snmpXProtoVendorEntry 1 } ::= { snmpXProtoSubTreeEntry 1 }
snmpXProtoVendorFeature OBJECT-TYPE snmpXProtoSubTreeBranch OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The OID of the object within the vendor tree DESCRIPTION
which identifies this vendor feature." "The OID which identifies this SubTree feature."
::= { snmpXProtoVendorEntry 2 } ::= { snmpXProtoSubTreeEntry 2 }
snmpXProtoVendorDocument OBJECT-TYPE snmpXProtoSubTreeFeature OBJECT-TYPE
SYNTAX DisplayString SYNTAX IANASnmpExtendedProtocol
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The vendor specific document identifier which DESCRIPTION
unambiguously points to the user documentation which defines "The standard SNMP protocol operations supported
this protocol feature." by this subTree above and beyond protocol
::= { snmpXProtoVendorEntry 3 } support as indicated by snmpXProtoSystem."
::= { snmpXProtoSubTreeEntry 3 }
snmpXProtoCompliance MODULE-COMPLIANCE snmpXProtoCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems supporting "The compliance statement for systems supporting
the snmpXProto MIB." the snmpXProto MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
snmpXProtoGroup snmpXProtoGroup
} }
::= { snmpXProtoCompliances 1 } ::= { snmpXProtoCompliances 1 }
snmpXProtoGroups OBJECT IDENTIFIER ::= { snmpXProtoConformance 2 } snmpXProtoGroups OBJECT IDENTIFIER ::= { snmpXProtoConformance 2 }
snmpXProtoGroup OBJECT-GROUP snmpXProtoGroup OBJECT-GROUP
OBJECTS { OBJECTS {
snmpXProtoStandard snmpXProtoSystem
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Standard snmpXProto group." "Standard snmpXProto group."
::= { snmpXProtoGroups 1} ::= { snmpXProtoGroups 1}
snmpXProtoVendorGroup OBJECT-GROUP snmpXProtoSubTreeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
snmpXProtoVendorIndex, snmpXProtoSubTreeFeature,
snmpXProtoVendorFeature, snmpXProtoSubTreeBranch
snmpXProtoVendorDocument
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vendor snmpXProto group." "SubTree specific snmpXProto group."
::= { snmpXProtoGroups 2} ::= { snmpXProtoGroups 2}
END END
6 IANA Considerations 6 IANA Considerations
IANASnmpExtendedProtocol is a bitmap which indicates which standard IANASnmpExtendedProtocol is a bitmap which indicates which standard
extensions to SNMP an SNMP entity supports. It may be given out for extensions to SNMP an SNMP entity supports. It may be given out for
SNMP protocol extensions published as standards track RFCs. SNMP protocol extensions published as standards track RFCs.
skipping to change at page 8, line 27 skipping to change at page 9, line 27
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
9. Acknowledgments 9. Acknowledgments
This document is a product of the Evolution of SNMP Working Group. This document is a product of the Evolution of SNMP Working Group.
... ...
11. References 10. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 41999. RFC 2571, April 41999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990. 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
skipping to change at page 10, line 6 skipping to change at page 11, line 6
[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, [RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB,
RFC 3014, November 2000 RFC 3014, November 2000
10. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). 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. 36 change blocks. 
63 lines changed or deleted 97 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/