--- 1/draft-ietf-6man-ipv6-mibs-obsolete-00.txt 2016-02-18 12:15:04.140734233 -0800 +++ 2/draft-ietf-6man-ipv6-mibs-obsolete-01.txt 2016-02-18 12:15:04.248736972 -0800 @@ -1,20 +1,20 @@ IPv6 Maintenance B. Fenner Internet-Draft Arista Networks, Inc. -Obsoletes: 2452, 2454, 2465, 2466 (if August 25, 2015 +Obsoletes: 2452, 2454, 2465, 2466 (if February 18, 2016 approved) Intended status: Informational -Expires: February 26, 2016 +Expires: August 21, 2016 Republishing the IPV6-specific MIB modules as obsolete - draft-ietf-6man-ipv6-mibs-obsolete-00 + draft-ietf-6man-ipv6-mibs-obsolete-01 Abstract In 2005, 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. @@ -26,25 +26,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on February 26, 2016. + This Internet-Draft will expire on August 21, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -71,24 +71,25 @@ 5. Historic IPV6-UDP-MIB . . . . . . . . . . . . . . . . . . . . 52 6. Historic IPV6-TCP-MIB . . . . . . . . . . . . . . . . . . . . 55 7. Reclassification . . . . . . . . . . . . . . . . . . . . . . 60 8. Security Considerations . . . . . . . . . . . . . . . . . . . 60 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 10.1. Normative References . . . . . . . . . . . . . . . . . . 61 10.2. Informative References . . . . . . . . . . . . . . . . . 62 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Appendix A. Change history . . . . . . . . . . . . . . . . . . . 63 - A.1. Changes since draft-fenner-ipv6-mibs-obsolete-00 . . . . 63 - A.2. Changes since draft-fenner-ipv6-mibs-obsolete-01 . . . . 63 - A.3. Changes since draft-fenner-ipv6-mibs-obsolete-02 . . . . 63 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 63 + A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01 . . . 63 + A.2. Changes since draft-fenner-ipv6-mibs-obsolete-00 . . . . 63 + A.3. Changes since draft-fenner-ipv6-mibs-obsolete-01 . . . . 63 + A.4. Changes since draft-fenner-ipv6-mibs-obsolete-02 . . . . 63 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 64 1. Motivation In 2005, the IPv6 MIB update group published updated versions of the IP-MIB [RFC4293], UDP-MIB [RFC4113], TCP-MIB [RFC4022] and IP- FORWARD-MIB [RFC4292] modules, which use the InetAddressType/ InetAddress construct to handle IPv4 and IPv6 in the same table. These documents were marked in the RFC Index as obsoleting the corresponding IPV6-MIBs, but the extracted content of these MIBs never changed in MIB repositories, and the original RFCs (as is @@ -209,21 +210,21 @@ Tel: +1-978-916-3816 E-mail: sonishi@baynetworks.com" DESCRIPTION "The obsolete MIB module for entities implementing the IPv6 protocol. Use the IP-MIB or IP-FORWARD-MIB instead." REVISION "201505282112Z" DESCRIPTION "Obsoleting this MIB module; it has been replaced by the revised IP-MIB (RFC4293) and IP-FORWARD-MIB (RFC4292)." - REVISION "9801082155Z" + REVISION "9802052155Z" DESCRIPTION "First revision, published as RFC2465" ::= { mib-2 55 } -- the IPv6 general group ipv6MIBObjects OBJECT IDENTIFIER ::= { ipv6MIB 1 } ipv6Forwarding OBJECT-TYPE SYNTAX INTEGER { @@ -916,21 +917,21 @@ This entry is obsoleted by IP-MIB::ipAddressPrefixEntry." INDEX { ipv6IfIndex, ipv6AddrPrefix, ipv6AddrPrefixLength } ::= { ipv6AddrPrefixTable 1 } Ipv6AddrPrefixEntry ::= SEQUENCE { ipv6AddrPrefix Ipv6AddressPrefix, - ipv6AddrPrefixLength INTEGER (0..128), + ipv6AddrPrefixLength INTEGER, ipv6AddrPrefixOnLinkFlag TruthValue, ipv6AddrPrefixAutonomousFlag TruthValue, ipv6AddrPrefixAdvPreferredLifetime Unsigned32, ipv6AddrPrefixAdvValidLifetime Unsigned32 } ipv6AddrPrefix OBJECT-TYPE SYNTAX Ipv6AddressPrefix MAX-ACCESS not-accessible STATUS obsolete @@ -2534,21 +2535,21 @@ managed node. This entry is obsoleted by UDP-MIB::udpEndpointTable." INDEX { ipv6UdpLocalAddress, ipv6UdpLocalPort, ipv6UdpIfIndex } ::= { ipv6UdpTable 1 } Ipv6UdpEntry ::= SEQUENCE { ipv6UdpLocalAddress Ipv6Address, - ipv6UdpLocalPort INTEGER (0..65535), + ipv6UdpLocalPort INTEGER, ipv6UdpIfIndex Ipv6IfIndexOrZero } ipv6UdpLocalAddress OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "The local IPv6 address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IPv6 address @@ -2706,23 +2707,23 @@ This entry is obsoleted by TCP-MIB::tcpConnectionEntry." INDEX { ipv6TcpConnLocalAddress, ipv6TcpConnLocalPort, ipv6TcpConnRemAddress, ipv6TcpConnRemPort, ipv6TcpConnIfIndex } ::= { ipv6TcpConnTable 1 } Ipv6TcpConnEntry ::= SEQUENCE { ipv6TcpConnLocalAddress Ipv6Address, - ipv6TcpConnLocalPort INTEGER (0..65535), + ipv6TcpConnLocalPort INTEGER, ipv6TcpConnRemAddress Ipv6Address, - ipv6TcpConnRemPort INTEGER (0..65535), + ipv6TcpConnRemPort INTEGER, ipv6TcpConnIfIndex Ipv6IfIndexOrZero, ipv6TcpConnState INTEGER } ipv6TcpConnLocalAddress OBJECT-TYPE SYNTAX Ipv6Address MAX-ACCESS not-accessible STATUS obsolete DESCRIPTION "The local IPv6 address for this TCP connection. In the case of a connection in the listen state which @@ -2972,48 +2973,57 @@ [RFC4293] Routhier, S., Ed., "Management Information Base for the Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293, April 2006, . 10.3. URIs [1] http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml Appendix A. Change history -A.1. Changes since draft-fenner-ipv6-mibs-obsolete-00 +A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01 + + Thanks to an excellent review by Mike Heard. + + o Correct the REVISION clause for the original IPV6-MIB + + o Remove the illegal sub-typing from SEQUENCE definitions in + IPV6-MIB, IPV6-UDP-MIB and IPV6-TCP-MIB. + +A.2. Changes since draft-fenner-ipv6-mibs-obsolete-00 o Realized that IPV6-ICMP-MIB was [RFC2466], so modified the added REVISION clause and the Reclassification section. o Added Security Considerations o Added IANA Considerations o Added the 6.c.iii Legend to the copyright statement, since the original RFCs were published before pre-5378. o Used "MIB module" instead of "MIB" when referring to a module, and changed REVISION DESCRIPTION to "Obsoleting", not "Deprecating". o Added "Obsoletes:" header to document o Switched to pre-5378 IPR statement, since the original RFCs were pre-5378. -A.2. Changes since draft-fenner-ipv6-mibs-obsolete-01 +A.3. Changes since draft-fenner-ipv6-mibs-obsolete-01 o Updated the DESCRIPTION of MODULE-IDENTITY to improve the "MIB index" problem. o Updated IANA considerations. -A.3. Changes since draft-fenner-ipv6-mibs-obsolete-02 +A.4. Changes since draft-fenner-ipv6-mibs-obsolete-02 o Fixed "IPV6-MIB" in title o Fixed some extra blank lines in the source MIBs, introduced by the process of extraction from RFCs. Author's Address Bill Fenner Arista Networks, Inc.