Internet DRAFT - draft-ietf-snmpv3-update-proto
draft-ietf-snmpv3-update-proto
A new Request for Comments is now available in online RFC libraries.
STD 62
RFC 3416
Title: Version 2 of the Protocol Operations for the
Simple Network Management Protocol (SNMP)
Author(s): R. Presuhn, Ed.
Status: Standards Track
Date: December 2002
Mailbox: randy_presuhn@bmc.com
Pages: 31
Characters: 70043
Obsoletes: 1905
See Also: STD 62
I-D Tag: draft-ietf-snmpv3-update-proto-08.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3416.txt
This document defines version 2 of the protocol operations for the
Simple Network Management Protocol (SNMP). It defines the syntax and
elements of procedure for sending, receiving, and processing SNMP
PDUs. This document obsoletes RFC 1905.
This document is a product of the SNMPv3 Working Group of the IETF.
This is now a Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.