metasystema.org
CurrentINFORMATIONALIETF stream

RFC 8096: The IPv6-Specific MIB Modules Are Obsolete

In plain English — editorial summary, not part of the RFC

In 2005-2006, the IPv6 MIB update group published updated versions of the IP-MIB, UDP-MIB, TCP-MIB, and IP-FORWARD-MIB modules, which use the InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the same table. This document contains versions of the obsoleted IPV6-MIB, IPV6-TC, IPV6-ICMP-MIB, IPV6-TCP-MIB, and IPV6-UDP-MIB modules for the purpose of updating MIB module repositories. This document obsoletes RFCs 2452, 2454, 2465, and 2466 (i.e., the RFCs containing these MIBs) and reclassifies them as Historic.

Document record

Document ID
RFC8096
Published
April 2017
Authors
B. Fenner
Status
INFORMATIONAL
Stream
IETF
Area
int
Pages
65
Also known as
—
Obsoletes:
RFC 2452, RFC 2454, RFC 2465, RFC 2466

Standards lineage

This document is one revision in a chain of 11 RFCs, each formally replacing the one before it.

  1. RFC 2011 (1996)
  2. RFC 2012 (1996)
  3. RFC 2013 (1996)
  4. RFC 2452 (1998)
  5. RFC 2454 (1998)
  6. RFC 2465 (1998)
  7. RFC 2466 (1998)
  8. RFC 4022 (2005)
  9. RFC 4113 (2005)
  10. RFC 4293 (2006)
  11. RFC 8096 (2017)

Read the full history of The IPv6-Specific MIB Modules Are Obsolete →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8096-the-ipv6-specific-mib-modules-are-obsolete