draft-ietf-snmpv3-update-proto-03.txt   draft-ietf-snmpv3-update-proto-04.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Category: Standards Track J. Case Category: Standards Track J. Case
SNMP Research, Inc. SNMP Research, Inc.
K. McCloghrie K. McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
M. Rose M. Rose
Dover Beach Consulting, Inc. Dover Beach Consulting, Inc.
S. Waldbusser S. Waldbusser
International Network Services International Network Services
Version 2 of the Protocol Operations for Version 2 of the Protocol Operations for
the Simple Network Management Protocol the Simple Network Management Protocol
<draft-ietf-snmpv3-update-proto-03.txt> <draft-ietf-snmpv3-update-proto-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract Abstract
This document is intended to obsolete RFC 1905, Protocol Operations This document defines version 2 of the protocol operations for the
for Version 2 of the Simple Network Management Protocol (SNMPv2). It Simple Network Management Protocol (SNMP). This document obsoletes
defines the syntax and elements of procedure for sending, receiving, RFC 1905. It defines the syntax and elements of procedure for
and processing SNMP PDUs. sending, receiving, and processing SNMP PDUs.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 3
2. Overview .................................................... 4 2. Overview .................................................... 4
2.1. Management Information .................................... 4 2.1. Management Information .................................... 4
2.2. Retransmission of Requests ................................ 4 2.2. Retransmission of Requests ................................ 4
2.3. Message Sizes ............................................. 4 2.3. Message Sizes ............................................. 4
2.4. Transport Mappings ........................................ 5 2.4. Transport Mappings ........................................ 5
2.5. SMIv2 Data Type Mappings .................................. 5 2.5. SMIv2 Data Type Mappings .................................. 5
skipping to change at page 2, line 34 skipping to change at page 2, line 34
4.2.4. The Response-PDU ........................................ 20 4.2.4. The Response-PDU ........................................ 20
4.2.5. The SetRequest-PDU ...................................... 21 4.2.5. The SetRequest-PDU ...................................... 21
4.2.6. The SNMPv2-Trap-PDU ..................................... 24 4.2.6. The SNMPv2-Trap-PDU ..................................... 24
4.2.7. The InformRequest-PDU ................................... 24 4.2.7. The InformRequest-PDU ................................... 24
5. Notice on Intellectual Property ............................. 25 5. Notice on Intellectual Property ............................. 25
6. Acknowledgments ............................................. 26 6. Acknowledgments ............................................. 26
7. Security Considerations ..................................... 27 7. Security Considerations ..................................... 27
8. References .................................................. 28 8. References .................................................. 28
9. Editor's Address ............................................ 30 9. Editor's Address ............................................ 30
10. Changes from RFC 1905 ...................................... 30 10. Changes from RFC 1905 ...................................... 30
11. Issues ..................................................... 31 11. Issues ..................................................... 32
12. Full Copyright Statement ................................... 33 12. Full Copyright Statement ................................... 34
1. Introduction 1. Introduction
The SNMP Management Framework at the time of this writing consists of The SNMP Management Framework at the time of this writing consists of
five major components: five major components:
- An overall architecture, described in RFC 2571 [RFC2571]. - An overall architecture, described in RFC 2571 [RFC2571].
- Mechanisms for describing and naming objects and events for - Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this the purpose of management. The first version of this
skipping to change at page 3, line 40 skipping to change at page 3, line 40
- Protocol operations for accessing management information. - Protocol operations for accessing management information.
The first set of protocol operations and associated PDU The first set of protocol operations and associated PDU
formats is described in STD 15, RFC 1157 [RFC1157]. A formats is described in STD 15, RFC 1157 [RFC1157]. A
second set of protocol operations and associated PDU second set of protocol operations and associated PDU
formats is described in this document. formats is described in this document.
- A set of fundamental applications described in RFC 2573 - A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism [RFC2573] and the view-based access control mechanism
described in RFC 2575 [RFC2575]. described in RFC 2575 [RFC2575].
A more detailed introduction to the SNMP Management Framework at A more detailed introduction to the SNMP Management Framework at the
the time of this writing can be found in RFC 2570 [RFC2570]. time of this writing can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store, termed
termed the Management Information Base or MIB. Objects in the the Management Information Base or MIB. Objects in the MIB are
MIB are defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This document, Version 2 of the Protocol Operations for the This document, Version 2 of the Protocol Operations for the Simple
Simple Network Management Protocol, defines the operations of Network Management Protocol, defines the operations of the protocol
the protocol with respect to the sending and receiving of PDUs with respect to the sending and receiving of PDUs to be carried by
to be carried by the message protocol. the message protocol.
2. Overview 2. Overview
SNMP entities supporting command generator or notification receiver SNMP entities supporting command generator or notification receiver
applications (traditionally called "managers") communicate with SNMP applications (traditionally called "managers") communicate with SNMP
entities supporting command responder or notification originator entities supporting command responder or notification originator
applications (traditionally called "agents"). The purpose of this applications (traditionally called "agents"). The purpose of this
protocol is the transport of management information and operations. protocol is the transport of management information and operations.
2.1. Management Information 2.1. Management Information
skipping to change at page 8, line 20 skipping to change at page 8, line 20
set-request set-request
SetRequest-PDU, SetRequest-PDU,
inform-request inform-request
InformRequest-PDU, InformRequest-PDU,
snmpV2-trap snmpV2-trap
SNMPv2-Trap-PDU, SNMPv2-Trap-PDU,
report report
Report-PDU, Report-PDU
} }
-- PDUs -- PDUs
GetRequest-PDU ::= GetRequest-PDU ::=
[0] [0]
IMPLICIT PDU IMPLICIT PDU
GetNextRequest-PDU ::= GetNextRequest-PDU ::=
[1] [1]
skipping to change at page 12, line 11 skipping to change at page 12, line 11
entity. However, all components of a PDU, including those whose entity. However, all components of a PDU, including those whose
values are ignored by the receiving SNMP entity, must have valid values are ignored by the receiving SNMP entity, must have valid
ASN.1 syntax and encoding. For example, some PDUs (e.g., the ASN.1 syntax and encoding. For example, some PDUs (e.g., the
GetRequest-PDU) are concerned only with the name of a variable and GetRequest-PDU) are concerned only with the name of a variable and
not its value. In this case, the value portion of the variable not its value. In this case, the value portion of the variable
binding is ignored by the receiving SNMP entity. The unSpecified binding is ignored by the receiving SNMP entity. The unSpecified
value is defined for use as the value portion of such bindings. value is defined for use as the value portion of such bindings.
On generating a management communication, the message "wrapper" to On generating a management communication, the message "wrapper" to
encapsulate the PDU is generated according to the "Elements of encapsulate the PDU is generated according to the "Elements of
Procedure" of the administrative framework in use is followed. While Procedure" of the administrative framework in use. The definition of
the definition of "max-bindings" does impose an upper-bound on the "max-bindings" imposes an upper bound on the number of variable
number of variable bindings, in practice, the size of a message is bindings. In practice, the size of a message is also limited by
limited only by constraints on the maximum message size -- it is not constraints on the maximum message size. A compliant implementation
limited by the number of variable bindings. A compliant must support as many variable bindings in a PDU or BulkPDU as fit
implementation must support as many variable bindings in a PDU or into the overall maximum message size limit of the SNMP engine, but
BulkPDU as fit into the overall maximum message size limit of the no more than 2147483647 variable bindings.
SNMP engine, but no more than 2147483647.
On receiving a management communication, the "Elements of Procedure" On receiving a management communication, the "Elements of Procedure"
of the administrative framework in use is followed, and if those of the administrative framework in use is followed, and if those
procedures indicate that the operation contained within the message procedures indicate that the operation contained within the message
is to be performed locally, then those procedures also indicate the is to be performed locally, then those procedures also indicate the
MIB view which is visible to the operation. MIB view which is visible to the operation.
4.2.1. The GetRequest-PDU 4.2.1. The GetRequest-PDU
A GetRequest-PDU is generated and transmitted at the request of an A GetRequest-PDU is generated and transmitted at the request of an
skipping to change at page 14, line 30 skipping to change at page 14, line 29
Otherwise, an alternate Response-PDU is generated. This alternate Otherwise, an alternate Response-PDU is generated. This alternate
Response-PDU is formatted with the same values in its request-id Response-PDU is formatted with the same values in its request-id
field as the received GetNextRequest-PDU, with the value of its field as the received GetNextRequest-PDU, with the value of its
error-status field set to "tooBig", the value of its error-index error-status field set to "tooBig", the value of its error-index
field set to zero, and an empty variable-bindings field. This field set to zero, and an empty variable-bindings field. This
alternate Response-PDU is then encapsulated into a message. If the alternate Response-PDU is then encapsulated into a message. If the
size of the resultant message is less than or equal to both a local size of the resultant message is less than or equal to both a local
constraint and the maximum message size of the originator, it is constraint and the maximum message size of the originator, it is
transmitted to the originator of the GetNextRequest-PDU. Otherwise, transmitted to the originator of the GetNextRequest-PDU. Otherwise,
the snmpSilentDrops [RFC-MIB] message is discarded. the snmpSilentDrops [RFC-MIB] counter is incremented and the
resultant message is discarded.
4.2.2.1. Example of Table Traversal 4.2.2.1. Example of Table Traversal
An important use of the GetNextRequest-PDU is the traversal of An important use of the GetNextRequest-PDU is the traversal of
conceptual tables of information within a MIB. The semantics of this conceptual tables of information within a MIB. The semantics of this
type of request, together with the method of identifying individual type of request, together with the method of identifying individual
instances of objects in the MIB, provides access to related objects instances of objects in the MIB, provides access to related objects
in the MIB as if they enjoyed a tabular organization. in the MIB as if they enjoyed a tabular organization.
In the protocol exchange sketched below, an application retrieves the In the protocol exchange sketched below, an application retrieves the
skipping to change at page 16, line 21 skipping to change at page 16, line 21
As there are no further entries in the table, the SNMP entity As there are no further entries in the table, the SNMP entity
supporting the command responder application responds with the supporting the command responder application responds with the
variables that are next in the lexicographical ordering of the variables that are next in the lexicographical ordering of the
accessible object names, for example: accessible object names, for example:
Response (( sysUpTime.0 = "123471" ), Response (( sysUpTime.0 = "123471" ),
( ipNetToMediaNetAddress.1.9.2.3.4 = ( ipNetToMediaNetAddress.1.9.2.3.4 =
"9.2.3.4" ), "9.2.3.4" ),
( ipRoutingDiscards.0 = "2" )) ( ipRoutingDiscards.0 = "2" ))
Note now, having reached the end of the column for Note how, having reached the end of the column for
ipNetToMediaPhysAddress, the second variable binding in the command ipNetToMediaPhysAddress, the second variable binding from the command
responder application has "wrapped" to the first row in the next responder application has now "wrapped" to the first row in the next
column. Furthermore, note how, having reached the end of the column. Furthermore, note how, having reached the end of the
ipNetToMediaTable for the third variable binding, the command ipNetToMediaTable for the third variable binding, the command
responder application has responded with the next available object, responder application has responded with the next available object,
which is outside that table. This response signals the end of the which is outside that table. This response signals the end of the
table to the command generator application. table to the command generator application.
4.2.3. The GetBulkRequest-PDU 4.2.3. The GetBulkRequest-PDU
A GetBulkRequest-PDU is generated and transmitted at the request of A GetBulkRequest-PDU is generated and transmitted at the request of
an application. The purpose of the GetBulkRequest-PDU is to request an application. The purpose of the GetBulkRequest-PDU is to request
skipping to change at page 29, line 50 skipping to change at page 29, line 50
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
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.
[RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for the Simple Network Waldbusser, "Transport Mappings for the Simple Network
Management Protocol", Management Protocol",
<draft-ietf-snmpv3-update-transmap-03.txt>, June 2000. <draft-ietf-snmpv3-update-transmap-04.txt>, July 2000.
[RFC-MIB] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. [RFC-MIB] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Management Information Base for the Simple Waldbusser, "Management Information Base for the Simple
Network Management Protocol", Network Management Protocol",
<draft-ietf-snmpv3-update-mib-03.txt>, June 2000. <draft-ietf-snmpv3-update-mib-04.txt>, July 2000.
9. Editor's Address 9. Editor's Address
Randy Presuhn Randy Presuhn
BMC Software, Inc. BMC Software, Inc.
2141 North First Street 2141 North First Street
San Jose, CA 95131 San Jose, CA 95131
USA USA
Phone: +1 408 546 1006 Phone: +1 408 546 1006
skipping to change at page 31, line 50 skipping to change at page 31, line 50
- Added content to security considerations clause. - Added content to security considerations clause.
- Updated ASN.1 comment on use of Report-PDU. This does not - Updated ASN.1 comment on use of Report-PDU. This does not
affect the protocol in any way. affect the protocol in any way.
- Updated acknowledgements section. - Updated acknowledgements section.
Included information on handling of BITS. Included information on handling of BITS.
Deleted spurious comma in ASN.1 definition of PDUs.
Added abstract.
11. Issues 11. Issues
This clause will be deleted when this material is published as an This clause will be deleted when this material is published as an
RFC. The issue labels are the same as those used in the on-line RFC. The issue labels are the same as those used in the on-line
issues list at issues list at
ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1905/index.html ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1905/index.html
1905-1 Done; table of contents added. 1905-1 Done; table of contents added.
1905-2 Done; new title put in. 1905-2 Done; new title put in.
skipping to change at page 33, line 43 skipping to change at page 33, line 47
1905-34 Done; headers and footers updated appropriately. 1905-34 Done; headers and footers updated appropriately.
1905-35 Done; resolution was "no change". 1905-35 Done; resolution was "no change".
1905-36 Done; though original resolution was "no change", this 1905-36 Done; though original resolution was "no change", this
was effectively superseded by the resolution to was effectively superseded by the resolution to
1905-12. 1905-12.
1905-37 Done; resolution was "no change". 1905-37 Done; resolution was "no change".
1905-38 Done; added abstract.
1905-39 Done; clarified text on maximum PDU size.
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2000). 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 and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, 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
 End of changes. 14 change blocks. 
31 lines changed or deleted 39 lines changed or added

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