draft-ietf-snmpv3-update-proto-05.txt   draft-ietf-snmpv3-update-proto-06.txt 
INTERNET-DRAFT Editor of this version: INTERNET-DRAFT Editor of this version:
Request for Comments: -PROTO R. Presuhn Request for Comments: -PRO R. Presuhn
STD: XXX BMC Software, Inc. STD: XXX BMC Software, Inc.
Obsoletes: 1905 Authors of previous version: Obsoletes: 1905 Authors of previous version:
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
9 August 2000
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-05.txt> <draft-ietf-snmpv3-update-proto-06.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 41 skipping to change at page 1, line 40
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
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
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract Abstract
This document defines version 2 of the protocol operations for the This document defines version 2 of the protocol operations for the
Simple Network Management Protocol (SNMP). This document obsoletes Simple Network Management Protocol (SNMP). This document obsoletes
RFC 1905. It defines the syntax and elements of procedure for RFC 1905. It defines the syntax and elements of procedure for
sending, receiving, and processing SNMP PDUs. sending, receiving, and processing SNMP PDUs.
Table of Contents Table of Contents
skipping to change at page 3, line 10 skipping to change at page 3, line 10
9. Editor's Address ............................................ 30 9. Editor's Address ............................................ 30
10. Changes from RFC 1905 ...................................... 30 10. Changes from RFC 1905 ...................................... 30
11. Issues ..................................................... 32 11. Issues ..................................................... 32
12. Full Copyright Statement ................................... 34 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 -ARC [RFC-ARC].
- 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
Structure of Management Information (SMI) is called SMIv1 Structure of Management Information (SMI) is called SMIv1
and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC
1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version,
called SMIv2, is described in STD 58, RFC 2578 [RFC2578], called SMIv2, is described in STD 58, RFC 2578 [RFC2578],
STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management information. - Message protocols for transferring management information.
The first version of the SNMP message protocol is called The first version of the SNMP message protocol is called
SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A
second version of the SNMP message protocol, which is not second version of the SNMP message protocol, which is not
an Internet standards track protocol, is called SNMPv2c and an Internet standards track protocol, is called SNMPv2c and
described in RFC 1901 [RFC1901] and RFC -TM [RFC-TM]. The described in RFC 1901 [RFC1901] and RFC -TMM [RFC-TMM].
third version of the message protocol is called SNMPv3 and The third version of the message protocol is called SNMPv3
described in RFC -TM [RFC-TM], RFC 2572 [RFC2572] and RFC and described in RFC -TMM [RFC-TMM], RFC -MPD [RFC-MPD] and
2574 [RFC2574]. RFC -USM [RFC-USM].
- 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 -APL
[RFC2573] and the view-based access control mechanism [RFC-APL] and the view-based access control mechanism
described in RFC 2575 [RFC2575]. described in RFC -ACM [RFC-ACM].
A more detailed introduction to the SNMP Management Framework at the A more detailed introduction to the SNMP Management Framework at 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, 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 document, Version 2 of the Protocol Operations for the Simple This document, Version 2 of the Protocol Operations for the Simple
Network Management Protocol, defines the operations of the protocol Network Management Protocol, defines the operations of the protocol
skipping to change at page 5, line 43 skipping to change at page 5, line 43
accordingly, so as to reduce the risk of fragmentation. In accordingly, so as to reduce the risk of fragmentation. In
particular, under conditions of network stress, only small values particular, under conditions of network stress, only small values
should be used for max-repetitions. should be used for max-repetitions.
2.4. Transport Mappings 2.4. Transport Mappings
It is important to note that the exchange of SNMP messages requires It is important to note that the exchange of SNMP messages requires
only an unreliable datagram service, with every message being only an unreliable datagram service, with every message being
entirely and independently contained in a single transport datagram. entirely and independently contained in a single transport datagram.
Specific transport mappings and encoding rules are specified Specific transport mappings and encoding rules are specified
elsewhere [RFC-TM]. However, the preferred mapping is the use of the elsewhere [RFC-TMM]. However, the preferred mapping is the use of
User Datagram Protocol [RFC768]. the User Datagram Protocol [RFC768].
2.5. SMIv2 Data Type Mappings 2.5. SMIv2 Data Type Mappings
The SMIv2 [RFC2578] defines 11 base types (INTEGER, OCTET STRING, The SMIv2 [RFC2578] defines 11 base types (INTEGER, OCTET STRING,
OBJECT IDENTIFIER, Integer32, IpAddress, Counter32, Gauge32, OBJECT IDENTIFIER, Integer32, IpAddress, Counter32, Gauge32,
Unsigned32, TimeTicks, Opaque, Counter64) and the BITS construct. The Unsigned32, TimeTicks, Opaque, Counter64) and the BITS construct. The
SMIv2 base types are mapped to the corresponding selection type in SMIv2 base types are mapped to the corresponding selection type in
the SimpleSyntax and ApplicationSyntax choices of the ASN.1 SNMP the SimpleSyntax and ApplicationSyntax choices of the ASN.1 SNMP
protocol definition. Note that the INTEGER and Integer32 SMIv2 base protocol definition. Note that the INTEGER and Integer32 SMIv2 base
types are mapped to the integer-value selection type of the types are mapped to the integer-value selection type of the
skipping to change at page 6, line 24 skipping to change at page 6, line 24
bit, are placed in bits 8 (high order bit) to 1 (low order bit) of bit, are placed in bits 8 (high order bit) to 1 (low order bit) of
the first octet, followed by bits 8 to 1 of each subsequent octet in the first octet, followed by bits 8 to 1 of each subsequent octet in
turn, followed by as many bits as are needed of the final subsequent turn, followed by as many bits as are needed of the final subsequent
octet, commencing with bit 8. Remaining bits, if any, of the final octet, commencing with bit 8. Remaining bits, if any, of the final
octet are set to zero on generation and ignored on receipt. octet are set to zero on generation and ignored on receipt.
3. Definitions 3. Definitions
SNMPv2-PDU DEFINITIONS ::= BEGIN SNMPv2-PDU DEFINITIONS ::= BEGIN
ObjectName ::= OBJECT IDENTIFIER ObjectName ::= OBJECT IDENTIFIER !
ObjectSyntax ::= ObjectSyntax ::= !
CHOICE { CHOICE { !
simple simple !
SimpleSyntax, SimpleSyntax, !
application-wide application-wide !
ApplicationSyntax ApplicationSyntax !
} } !
SimpleSyntax ::= SimpleSyntax ::= !
CHOICE { CHOICE { !
integer-value integer-value !
INTEGER (-2147483648..2147483647), INTEGER (-2147483648..2147483647), !
string-value string-value !
OCTET STRING (SIZE (0..65535)), OCTET STRING (SIZE (0..65535)), !
objectID-value objectID-value !
OBJECT IDENTIFIER OBJECT IDENTIFIER !
} } !
ApplicationSyntax ::= ApplicationSyntax ::=
CHOICE { CHOICE {
ipAddress-value ipAddress-value
IpAddress, IpAddress,
counter-value counter-value
Counter32, Counter32,
timeticks-value timeticks-value
TimeTicks, TimeTicks,
skipping to change at page 7, line 25 skipping to change at page 7, line 25
arbitrary-value arbitrary-value
Opaque, Opaque,
big-counter-value big-counter-value
Counter64, Counter64,
unsigned-integer-value unsigned-integer-value
Unsigned32 Unsigned32
} }
IpAddress ::= [APPLICATION 0] IMPLICIT OCTET STRING (SIZE (4)) IpAddress ::= [APPLICATION 0] IMPLICIT OCTET STRING (SIZE (4)) !
Counter32 ::= [APPLICATION 1] IMPLICIT INTEGER (0..4294967295) Counter32 ::= [APPLICATION 1] IMPLICIT INTEGER (0..4294967295) !
Unsigned32 ::= [APPLICATION 2] IMPLICIT INTEGER (0..4294967295) Unsigned32 ::= [APPLICATION 2] IMPLICIT INTEGER (0..4294967295) !
Gauge32 ::= Unsigned32 Gauge32 ::= Unsigned32 !
TimeTicks ::= [APPLICATION 3] IMPLICIT INTEGER (0..4294967295) TimeTicks ::= [APPLICATION 3] IMPLICIT INTEGER (0..4294967295) !
Opaque ::= [APPLICATION 4] IMPLICIT OCTET STRING Opaque ::= [APPLICATION 4] IMPLICIT OCTET STRING !
Counter64 ::= [APPLICATION 6] Counter64 ::= [APPLICATION 6] !
IMPLICIT INTEGER (0..18446744073709551615) IMPLICIT INTEGER (0..18446744073709551615) !
-- protocol data units -- protocol data units
PDUs ::= PDUs ::=
CHOICE { CHOICE {
get-request get-request
GetRequest-PDU, GetRequest-PDU,
get-next-request get-next-request
GetNextRequest-PDU, GetNextRequest-PDU,
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 9, line 21 skipping to change at page 9, line 21
Report-PDU ::= Report-PDU ::=
[8] [8]
IMPLICIT PDU IMPLICIT PDU
max-bindings max-bindings
INTEGER ::= 2147483647 INTEGER ::= 2147483647
PDU ::= PDU ::=
SEQUENCE { SEQUENCE {
request-id request-id
INTEGER (-214783648..214783647), INTEGER (-214783648..214783647), !
error-status -- sometimes ignored error-status -- sometimes ignored
INTEGER { INTEGER {
noError(0), noError(0),
tooBig(1), tooBig(1),
noSuchName(2), -- for proxy compatibility noSuchName(2), -- for proxy compatibility
badValue(3), -- for proxy compatibility badValue(3), -- for proxy compatibility
readOnly(4), -- for proxy compatibility readOnly(4), -- for proxy compatibility
genErr(5), genErr(5),
noAccess(6), noAccess(6),
skipping to change at page 10, line 7 skipping to change at page 10, line 7
error-index -- sometimes ignored error-index -- sometimes ignored
INTEGER (0..max-bindings), INTEGER (0..max-bindings),
variable-bindings -- values are sometimes ignored variable-bindings -- values are sometimes ignored
VarBindList VarBindList
} }
BulkPDU ::= -- must be identical in BulkPDU ::= -- must be identical in
SEQUENCE { -- structure to PDU SEQUENCE { -- structure to PDU
request-id request-id
INTEGER (-214783648..214783647), INTEGER (-214783648..214783647), !
non-repeaters non-repeaters
INTEGER (0..max-bindings), INTEGER (0..max-bindings),
max-repetitions max-repetitions
INTEGER (0..max-bindings), INTEGER (0..max-bindings),
variable-bindings -- values are ignored variable-bindings -- values are ignored
VarBindList VarBindList
} }
skipping to change at page 20, line 45 skipping to change at page 20, line 45
If both the error-status field and the error-index field of the If both the error-status field and the error-index field of the
Response-PDU are non-zero, then the value of the error-index field is Response-PDU are non-zero, then the value of the error-index field is
the index of the variable binding (in the variable-binding list of the index of the variable binding (in the variable-binding list of
the corresponding request) for which the request failed. The first the corresponding request) for which the request failed. The first
variable binding in a request's variable-binding list is index one, variable binding in a request's variable-binding list is index one,
the second is index two, etc. the second is index two, etc.
A compliant SNMP entity supporting a command generator application A compliant SNMP entity supporting a command generator application
must be able to properly receive and handle a Response-PDU with an must be able to properly receive and handle a Response-PDU with an
error-status field equal to "noSuchName", "badValue", or "readOnly". error-status field equal to "noSuchName", "badValue", or "readOnly".
(See sections 1.3 and 4.3 of [RFC2576].) (See sections 1.3 and 4.3 of [RFC-COEX].)
Upon receipt of a Response-PDU, the receiving SNMP entity presents Upon receipt of a Response-PDU, the receiving SNMP entity presents
its contents to the application which generated the request with the its contents to the application which generated the request with the
same request-id value. For more details, see [RFC2572]. same request-id value. For more details, see [RFC-MPD].
4.2.5. The SetRequest-PDU 4.2.5. The SetRequest-PDU
A SetRequest-PDU is generated and transmitted at the request of an A SetRequest-PDU is generated and transmitted at the request of an
application. application.
Upon receipt of a SetRequest-PDU, the receiving SNMP entity Upon receipt of a SetRequest-PDU, the receiving SNMP entity
determines the size of a message encapsulating a Response-PDU having determines the size of a message encapsulating a Response-PDU having
the same values in its request-id and variable-bindings fields as the the same values in its request-id and variable-bindings fields as the
received SetRequest-PDU, and the largest possible sizes of the received SetRequest-PDU, and the largest possible sizes of the
skipping to change at page 25, line 9 skipping to change at page 25, line 9
present. This is a confirmed notification delivery mechanism, present. This is a confirmed notification delivery mechanism,
although there is, of course, no guarantee of delivery. although there is, of course, no guarantee of delivery.
The destination(s) to which an InformRequest-PDU is sent is specified The destination(s) to which an InformRequest-PDU is sent is specified
by the notification originator application. The first two variable by the notification originator application. The first two variable
bindings in the variable binding list of an InformRequest-PDU are bindings in the variable binding list of an InformRequest-PDU are
sysUpTime.0 [RFC-MIB] and snmpTrapOID.0 [RFC-MIB] respectively. If sysUpTime.0 [RFC-MIB] and snmpTrapOID.0 [RFC-MIB] respectively. If
the OBJECTS clause is present in the invocation of the corresponding the OBJECTS clause is present in the invocation of the corresponding
NOTIFICATION-TYPE macro, then each corresponding variable, as NOTIFICATION-TYPE macro, then each corresponding variable, as
instantiated by this notification, is copied, in order, to the instantiated by this notification, is copied, in order, to the
variable-bindings field. variable-bindings field. If any additional variables are being
included (at the option of the generating SNMP entity), then each is
copied to the variable-bindings field.
Upon receipt of an InformRequest-PDU, the receiving SNMP entity Upon receipt of an InformRequest-PDU, the receiving SNMP entity
determines the size of a message encapsulating a Response-PDU with determines the size of a message encapsulating a Response-PDU with
the same values in its request-id, error-status, error-index and the same values in its request-id, error-status, error-index and
variable-bindings fields as the received InformRequest-PDU. If the variable-bindings fields as the received InformRequest-PDU. If the
determined message size is greater than either a local constraint or determined message size is greater than either a local constraint or
the maximum message size of the originator, then an alternate the maximum message size of the originator, then an alternate
Response-PDU is generated, transmitted to the originator of the Response-PDU is generated, transmitted to the originator of the
InformRequest-PDU, and processing of the InformRequest-PDU terminates InformRequest-PDU, and processing of the InformRequest-PDU terminates
immediately thereafter. This alternate Response-PDU is formatted immediately thereafter. This alternate Response-PDU is formatted
skipping to change at page 25, line 37 skipping to change at page 25, line 39
InformRequest-PDU. Otherwise, the snmpSilentDrops [RFC-MIB] counter InformRequest-PDU. Otherwise, the snmpSilentDrops [RFC-MIB] counter
is incremented and the resultant message is discarded. Regardless, is incremented and the resultant message is discarded. Regardless,
processing of the InformRequest-PDU terminates. processing of the InformRequest-PDU terminates.
Otherwise, the receiving SNMP entity: Otherwise, the receiving SNMP entity:
(1) presents its contents to the appropriate application; (1) presents its contents to the appropriate application;
(2) generates a Response-PDU with the same values in its request-id (2) generates a Response-PDU with the same values in its request-id
and variable-bindings fields as the received InformRequest-PDU, and variable-bindings fields as the received InformRequest-PDU,
with the value of its error-status field is set to "noError" and with the value of its error-status field set to "noError" and
the value of its error-index field is zero; and the value of its error-index field set to zero; and
(3) transmits the generated Response-PDU to the originator of the (3) transmits the generated Response-PDU to the originator of the
InformRequest-PDU. InformRequest-PDU.
5. Notice on Intellectual Property 5. Notice on 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
skipping to change at page 27, line 39 skipping to change at page 27, line 41
Shawn Routhier Shawn Routhier
Jon Saperia Jon Saperia
Juergen Schoenwaelder Juergen Schoenwaelder
Bob Stewart Bob Stewart
Kaj Tesink Kaj Tesink
Glenn Waters Glenn Waters
Bert Wijnen Bert Wijnen
7. Security Considerations 7. Security Considerations
The protocol defined in this document by itself does not provide a The protocol defined in this document by itself does not provide a !
secure environment. Even if the network itself is secure (for secure environment. Even if the network itself is secure (for !
example by using IPSec), there is no control as to who on the secure example by using IPSec), there is no control as to who on the secure !
network is allowed to access and GET/SET (read/change) MIB network is allowed access to management information.
information.
It is recommended that the implementors consider the security It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2574 [RFC2574] and the of the User-based Security Model RFC -USM [RFC-USM] and the
View-based Access Control Model RFC 2575 [RFC2575] is recommended. View-based Access Control Model RFC -ACM [RFC-ACM] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity is properly configured so that: entity is properly configured so that:
- only those principals (users) having legitimate rights can - only those principals (users) having legitimate rights can
access or modify the values of any MIB objects supported by access or modify the values of any MIB objects supported by
that entity; that entity;
- the occurrence of particular events on the entity will be - the occurrence of particular events on the entity will be
communicated appropriately; communicated appropriately;
- the entity responds appropriately and with due credence to - the entity responds appropriately and with due credence to
events and information that have been communicated to it. events and information that have been communicated to it.
8. References 8. References
[ASN1] Information processing systems - Open Systems [ASN1] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax Interconnection - Specification of Abstract Syntax Notation
Notation One (ASN.1), International Organization for One (ASN.1), International Organization for
Standardization. International Standard 8824, December Standardization. International Standard 8824, December
1987. 1987.
[FRAG] Kent, C., and J. Mogul, Fragmentation Considered Harmful, [FRAG] Kent, C., and J. Mogul, "Fragmentation Considered Harmful,"
Proceedings, ACM SIGCOMM '87, Stowe, VT, August 1987. Proceedings, ACM SIGCOMM '87, Stowe, VT, August 1987.
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
USC/Information Sciences Institute, August 1980. USC/Information Sciences Institute, August 1980.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
"Simple Network Management Protocol", STD 15, RFC 1157, of Management Information for TCP/IP-based Internets", STD
May 1990. 16, RFC 1155, May 1990.
[RFC1213] McCloghrie, K., and M. Rose, Editors, "Management [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Information Base for Network Management of TCP/IP-based Network Management Protocol", STD 15, RFC 1157, May 1990.
internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
Identification of Management Information for TCP/IP-based 16, RFC 1212, March 1991.
Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1215] Rose, M., "A Convention for Defining Traps for use with the
STD 16, RFC 1212, March 1991. SNMP", RFC 1215, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with [RFC1213] McCloghrie, K., and M. Rose, Editors, "Management
the SNMP", RFC 1215, March 1991. Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, "Introduction to Community-based SNMPv2", RFC 1901, January
January 1996. 1996.
[RFC2233] McCloghrie, K., and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2233, November 1997.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard Network
Network Management Framework", RFC 2570, April 1999. Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC-ARC] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
Architecture for Describing SNMP Management Frameworks", for describing SNMP Management Frameworks",
RFC 2571, April 1999. <draft-ietf-snmpv3-arch-v2-01.txt>, July 2001.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC-MPD] Case, J., Harrington, D., Presuhn, R. and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple Network
Network Management Protocol (SNMP)", RFC 2572, April Management Protocol (SNMP)",
1999. <draft-ietf-snmpv3-mpd-v2-01.txt>, July 2001.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC-APL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications",
Applications", RFC 2573, April 1999. <draft-ietf-snmpv3-appl-v3-01.txt>, July 2001.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC-USM] Blumenthal, U. and B. Wijnen, "The User-Based Security
(USM) for version 3 of the Simple Network Management Model for Version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999. Protocol (SNMPv3)",
<draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt>, July 2001.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC-ACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model for the Simple Network Management
Management Protocol (SNMP)", RFC 2575, April 1999. Protocol (SNMP)", <draft-ietf-snmpv3-vacm-04.txt>, February
1999. <draft-ietf-snmpv3-vacm-v2-01.txt>, July 2001.
[RFC2576] Frye, R., Levi, D., Routhier, S., and B. Wijnen, [RFC-COEX]Frye, R., Levi, D., Routhier, S., and B. Wijnen,
"Coexistence between Version 1, Version 2, and Version 3 "Coexistence between Version 1, Version 2, and Version 3 of
of the Internet-standard Network Management Framework", the Internet-standard Network Management Framework",
RFC 2576, March, 2000. <draft-ietf-snmpv3-coex-v2-01.txt>, March, 2000.
[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
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
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-TMM] 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-05.txt>, August 2000. <draft-ietf-snmpv3-update-transmap-06.txt>, July 2001.
[RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 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-05.txt>, August 2000. <draft-ietf-snmpv3-update-mib-06.txt>, July 2001.
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 30, line 42 skipping to change at page 30, line 45
- Cosmetic fixes to layout and typography; - Cosmetic fixes to layout and typography;
- Added table of contents; - Added table of contents;
- Title changed; - Title changed;
- Updated document headers and footers; - Updated document headers and footers;
- Deleted the old clause 2.3, entitled "Access to Management - Deleted the old clause 2.3, entitled "Access to Management
Information". Information";
- Changed the way in which request-id was defined, though - Changed the way in which request-id was defined, though
with the same ultimate syntax and semantics, to avoid with the same ultimate syntax and semantics, to avoid
coupling with SMI. This does not affect the protocol in coupling with SMI. This does not affect the protocol in
any way. any way;
- Replaced the word "exception" with the word "error" in the - Replaced the word "exception" with the word "error" in the
old clause 4.1. This does not affect the protocol in any old clause 4.1. This does not affect the protocol in any
way. way;
- Deleted the first two paragraphs of the old clause 4.2. - Deleted the first two paragraphs of the old clause 4.2;
- Clarified the maximum number of variable bindings that an - Clarified the maximum number of variable bindings that an
implementation must support in a PDU. This does not affect implementation must support in a PDU. This does not affect
the protocol in any way. the protocol in any way;
- Replaced occurrences of "SNMPv2 application" with - Replaced occurrences of "SNMPv2 application" with
"application". "application";
- Deleted three sentences in old clause 4.2.3 describing the - Deleted three sentences in old clause 4.2.3 describing the
handling of an impossible situation. This does not affect handling of an impossible situation. This does not affect
the protocol in any way. the protocol in any way;
- Clarified the use of the SNMPv2-Trap-Pdu in the old clause - Clarified the use of the SNMPv2-Trap-Pdu in the old clause
4.2.6. This does not affect the protocol in any way. 4.2.6. This does not affect the protocol in any way;
- Aligned description of the use of the InformRequest-Pdu in - Aligned description of the use of the InformRequest-Pdu in
old clause 4.2.7 with the architecture. This does not old clause 4.2.7 with the architecture. This does not
affect the protocol in any way. affect the protocol in any way;
- Updated references. - Updated references;
- Re-wrote introduction clause. - Re-wrote introduction clause;
- Replaced manager/agent/SNMPv2 entity terminology with - Replaced manager/agent/SNMPv2 entity terminology with
terminology from RFC 2571. This does not affect the terminology from RFC 2571. This does not affect the
protocol in any way. protocol in any way;
- Eliminated IMPORTS from the SMI, replaced with equivalent - Eliminated IMPORTS from the SMI, replaced with equivalent
in-line ASN.1. This does not affect the protocol in any in-line ASN.1. This does not affect the protocol in any
way. way;
- Added notes calling attention to two different - Added notes calling attention to two different
manifestations of reaching the end of a table in the table manifestations of reaching the end of a table in the table
walk examples. walk examples;
- 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;
Deleted spurious comma in ASN.1 definition of PDUs. Added abstract;
Added abstract. Made handling of additional variable bindings in informs
consistent with that for traps. This was a correction of
an editorial oversight, and reflects implementation
practice.
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.
skipping to change at page 34, line 5 skipping to change at page 34, line 11
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-38 Done; added abstract.
1905-39 Done; clarified text on maximum PDU size. 1905-39 Done; clarified text on maximum PDU size.
1905-40 Open; should trap and inform procedures match for
added varbinds?
12. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2000). 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 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
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. 71 change blocks. 
121 lines changed or deleted 129 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/