draft-ietf-snmpv3-update-proto-07.txt   draft-ietf-snmpv3-update-proto-08.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
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
3 October 2001 16 October 2001
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-07.txt> <draft-ietf-snmpv3-update-proto-08.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 4, line 41 skipping to change at page 4, line 41
2.2. Retransmission of Requests 2.2. Retransmission of Requests
For all types of request in this protocol, the receiver is required For all types of request in this protocol, the receiver is required
under normal circumstances, to generate and transmit a response to under normal circumstances, to generate and transmit a response to
the originator of the request. Whether or not a request should be the originator of the request. Whether or not a request should be
retransmitted if no corresponding response is received in an retransmitted if no corresponding response is received in an
appropriate time interval, is at the discretion of the application appropriate time interval, is at the discretion of the application
originating the request. This will normally depend on the urgency of originating the request. This will normally depend on the urgency of
the request. However, such an application needs to act responsibly the request. However, such an application needs to act responsibly
in respect to the frequency and duration of re-transmissions. in respect to the frequency and duration of re-transmissions. See
BCP 41 [RFC2914] for discussion of relevant congestion control
principles.
2.3. Message Sizes 2.3. Message Sizes
The maximum size of an SNMP message is limited to the minimum of: The maximum size of an SNMP message is limited to the minimum of:
(1) the maximum message size which the destination SNMP entity can (1) the maximum message size which the destination SNMP entity can
accept; and, accept; and,
(2) the maximum message size which the source SNMP entity can (2) the maximum message size which the source SNMP entity can
generate. generate.
skipping to change at page 6, line 24 skipping to change at page 6, line 26
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 27, line 41 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 access to management information. network is allowed access to management 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 -USM [RFC-USM] and the of the User-based Security Model RFC -USM [RFC-USM] and the
View-based Access Control Model RFC -ACM [RFC-ACM] 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:
skipping to change at page 29, line 23 skipping to change at page 29, line 23
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-TMM] 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-07.txt>, October 2001. <draft-ietf-snmpv3-update-transmap-08.txt>, October 2001.
[RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, RFC
2914, September 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-07.txt>, October 2001. <draft-ietf-snmpv3-update-mib-07.txt>, October 2001.
[RFC-ARC] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture [RFC-ARC] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
for describing SNMP Management Frameworks", for describing SNMP Management Frameworks",
<draft-ietf-snmpv3-arch-v2-01.txt>, October 2001. <draft-ietf-snmpv3-arch-v2-02.txt>, October 2001.
[RFC-MPD] 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 Network "Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)", Management Protocol (SNMP)",
<draft-ietf-snmpv3-mpd-v2-01.txt>, October 2001. <draft-ietf-snmpv3-mpd-v2-02.txt>, October 2001.
[RFC-APL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", [RFC-APL] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications",
<draft-ietf-snmpv3-appl-v3-01.txt>, October 2001. <draft-ietf-snmpv3-appl-v3-01.txt>, October 2001.
[RFC-USM] Blumenthal, U. and B. Wijnen, "The User-Based Security [RFC-USM] Blumenthal, U. and B. Wijnen, "The User-Based Security
Model for Version 3 of the Simple Network Management Model for Version 3 of the Simple Network Management
Protocol (SNMPv3)", Protocol (SNMPv3)",
<draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt>, October 2001. <draft-ietf-snmpv3-usm-v2-rfc2574bis-01.txt>, October 2001.
[RFC-ACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based [RFC-ACM] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
skipping to change at page 32, line 11 skipping to change at page 32, line 11
- 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 Made handling of additional variable bindings in informs
consistent with that for traps. This was a correction of consistent with that for traps. This was a correction of
an editorial oversight, and reflects implementation an editorial oversight, and reflects implementation
practice. practice;
Added reference to RFC 2914.
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.
 End of changes. 25 change blocks. 
38 lines changed or deleted 45 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/