Skip to main content

9. Changes from RFC 1905

The following are the changes from RFC 1905:

  • Corrected typos in the copyright statement

  • Updated the copyright date

  • Updated the name and contact information of the new editor

  • Added the notice on intellectual property

  • Made cosmetic fixes to layout and typography

  • Added table of contents

  • Changed the title

  • Updated document headers and footers

  • Removed the old Section 2.3, titled "Access to Management Information"

  • Changed the way request-id is defined, although with the same end syntax and semantics, to avoid coupling with the SMI. This does not affect the protocol in any way

  • Replaced the word "exception" with the word "error" in the old Section 4.1. This does not affect the protocol in any way

  • Removed the first two paragraphs of the old Section 4.2

  • Clarified the maximum number of variable bindings that implementations must support in a PDU. This does not affect the protocol in any way

  • Replaced occurrences of "SNMPv2 application" with "application"

  • Removed three sentences describing processing of impossible situations in the old Section 4.2.3. This does not affect the protocol in any way

  • Clarified the usage of SNMPv2-Trap-Pdu in the old Section 4.2.6. This does not affect the protocol in any way

  • Aligned the description of usage of InformRequest-Pdu in the old Section 4.2.7 with the architecture. This does not affect the protocol in any way

  • Updated references

  • Rewrote the introduction clause

  • Replaced manager/agent/SNMPv2 entity terminology with that of RFC 2571. This does not affect the protocol in any way

  • Eliminated IMPORTS from the SMI, replacing with equivalent inline ASN.1. This does not affect the protocol in any way

  • Added a note in the table traversal examples to draw attention to the two different manifestations of reaching the end of a table

  • Added content to the security considerations clause

  • Updated the ASN.1 comment regarding use of Report-PDU. This does not affect the protocol in any way

  • Updated the acknowledgments section

  • Included information about handling BITS

  • Removed extraneous comma in the ASN.1 definition of PDU

  • Added the abstract

  • Made the handling of additional variable-bindings in informs consistent with that for traps. This is a correction to an editorial oversight and reflects implementation practice

  • Added a reference to RFC 2914

Note: Most of these changes are editorial in nature and do not affect the protocol specification itself. The substantive changes primarily involve clarifications and alignment with the SNMPv3 architecture defined in RFC 3411 and related documents.

Last updated on