RFC 8096 on The IPv6-Specific MIB Modules Are Obsolete
rfc-editor@rfc-editor.org Mon, 17 April 2017 20:27 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634A3129454; Mon, 17 Apr 2017 13:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qdt44Si5_zft; Mon, 17 Apr 2017 13:27:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D087F128C82; Mon, 17 Apr 2017 13:27:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DFC7EB80CFC; Mon, 17 Apr 2017 13:27:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8096 on The IPv6-Specific MIB Modules Are Obsolete
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipv6@ietf.org
Message-Id: <20170417202736.DFC7EB80CFC@rfc-editor.org>
Date: Mon, 17 Apr 2017 13:27:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/iXGqBLWmT51j0d9Lfeji87BKMuk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 20:27:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8096
Title: The IPv6-Specific MIB Modules Are Obsolete
Author: B. Fenner
Status: Informational
Stream: IETF
Date: April 2017
Mailbox: fenner@fenron.com
Pages: 65
Characters: 117298
Obsoletes: RFC 2452, RFC 2454, RFC 2465, RFC 2466
I-D Tag: draft-ietf-6man-ipv6-mibs-obsolete-02.txt
URL: https://www.rfc-editor.org/info/rfc8096
DOI: 10.17487/RFC8096
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.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC