draft-ietf-snmpv3-update-proto-02.txt   draft-ietf-snmpv3-update-proto-03.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-02.txt> <draft-ietf-snmpv3-update-proto-03.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 6, line 14 skipping to change at page 6, line 14
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
SimpleSyntax choice. Similarly, the Gauge32 and Unsigned32 SMIv2 base SimpleSyntax choice. Similarly, the Gauge32 and Unsigned32 SMIv2 base
types are mapped to the unsigned-integer-value selection type of the types are mapped to the unsigned-integer-value selection type of the
ApplicationSyntax choice. ApplicationSyntax choice.
The SMIv2 BITS construct is mapped to the string-value selection type The SMIv2 BITS construct is mapped to the string-value selection type
of the SimpleSyntax choice. A BITS value is encoded as an OCTET of the SimpleSyntax choice. A BITS value is encoded as an OCTET
STRING, in which all the named bits in (the definition of) the STRING, in which all the named bits in (the definition of) the
bitstring, commencing with the first bit and proceeding to the last bitstring, commencing with the first bit and proceeding to the last
bit, are placed in bits 8 to 1 of the first octet, followed by bits 8 bit, are placed in bits 8 (high order bit) to 1 (low order bit) of
to 1 of each subsequent octet in turn, followed by as many bits as the first octet, followed by bits 8 to 1 of each subsequent octet in
are needed of the final subsequent octet, commencing with bit 8. turn, followed by as many bits as are needed of the final subsequent
Remaining bits, if any, of the final octet are set to zero on octet, commencing with bit 8. Remaining bits, if any, of the final
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
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 Section ???3.1.2??? of [RFC2576].) (See sections 1.3 and 4.3 of [RFC2576].)
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 [RFC2572].
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.
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-02.txt>, April 2000. <draft-ietf-snmpv3-update-transmap-03.txt>, 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-02.txt>, April 2000. <draft-ietf-snmpv3-update-mib-03.txt>, June 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 46 skipping to change at page 31, line 48
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.
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.
1905-3 Done; new introduction clause put in. 1905-3 Done; new introduction clause put in.
1905-4 Done; handled as part of 1905-3. 1905-4 Done; handled as part of 1905-3.
1905-5 Done; clause deleted. 1905-5 Done; clause deleted.
 End of changes. 8 change blocks. 
10 lines changed or deleted 12 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/