Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework
draft-ietf-snmpv3-coex-v2-04
The information below is for an old version of the document that is already published as an RFC.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3584.
|
|
|---|---|---|---|
| Authors | Rob Frye , David B. Levi , Bert Wijnen , Shawn A. Routhier | ||
| Last updated | 2015-10-14 (Latest revision 2003-05-06) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 3584 (Best Current Practice) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Randy Bush | ||
| Send notices to | (None) |
draft-ietf-snmpv3-coex-v2-04
A new Request for Comments is now available in online RFC libraries.
BCP 74
RFC 3584
Title: Coexistence between Version 1, Version 2, and
Version 3 of the Internet-standard Network
Management Framework
Author(s): R. Frye, D. Levi, S. Routhier, B. Wijnen
Status: Best Current Practice
Date: August 2003
Mailbox: rfrye@vibrant-1.com, dlevi@nortelnetworks.com,
sar@epilogue.com, bwijnen@lucent.com
Pages: 51
Characters: 115222
Obsoletes: 2576
I-D Tag: draft-ietf-snmpv3-coex-v2-04.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3584.txt
The purpose of this document is to describe coexistence between
version 3 of the Internet-standard Network Management Framework,
(SNMPv3), version 2 of the Internet-standard Network Management
Framework (SNMPv2), and the original Internet-standard Network
Management Framework (SNMPv1). This document also describes how to
convert MIB modules from SMIv1 format to SMIv2 format. This document
obsoletes RFC 2576.
This document is a product of the SNMP Version 3 Working Group of the
IETF.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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.