[rfc-dist] RFC 4293 on Management Information Base for the Internet Protocol (IP)
rfc-editor at rfc-editor.org
Tue Apr 11 16:22:54 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Management Information Base for the
Internet Protocol (IP)
Author: S. Routhier, Ed.
Status: Standards Track
Date: April 2006
Mailbox: sar at iwl.com
Obsoletes: RFC2011, RFC2465, RFC2466
I-D Tag: draft-ietf-ipv6-rfc2011-update-10.txt
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In
particular, it describes managed objects used for implementations of the
Internet Protocol (IP) in an IP version independent manner. This memo
obsoletes RFCs 2011, 2465, and 2466. [STANDARDS TRACK]
This document is a product of the IP Version 6 Working Group
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist