draft-ietf-6man-ipv6-mibs-obsolete-01.txt   draft-ietf-6man-ipv6-mibs-obsolete-02.txt 
IPv6 Maintenance B. Fenner IPv6 Maintenance B. Fenner
Internet-Draft Arista Networks, Inc. Internet-Draft Arista Networks, Inc.
Obsoletes: 2452, 2454, 2465, 2466 (if February 18, 2016 Obsoletes: 2452, 2454, 2465, 2466 (if November 14, 2016
approved) approved)
Intended status: Informational Intended status: Informational
Expires: August 21, 2016 Expires: May 18, 2017
Republishing the IPV6-specific MIB modules as obsolete Republishing the IPV6-specific MIB modules as obsolete
draft-ietf-6man-ipv6-mibs-obsolete-01 draft-ietf-6man-ipv6-mibs-obsolete-02
Abstract Abstract
In 2005, the IPv6 MIB update group published updated versions of the 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 IP-MIB, UDP-MIB, TCP-MIB and IP-FORWARD-MIB modules, which use the
InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the
same table. This document contains versions of the obsoleted same table. This document contains versions of the obsoleted
IPV6-MIB, IPV6-TC, IPV6-ICMP-MIB, IPV6-TCP-MIB and IPV6-UDP-MIB IPV6-MIB, IPV6-TC, IPV6-ICMP-MIB, IPV6-TCP-MIB and IPV6-UDP-MIB
modules, for the purpose of updating MIB module repositories. modules, for the purpose of updating MIB module repositories.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 21, 2016. This Internet-Draft will expire on May 18, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 24 skipping to change at page 2, line 24
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Historic IPV6-TC . . . . . . . . . . . . . . . . . . . . . . 3 2. Historic IPV6-TC . . . . . . . . . . . . . . . . . . . . . . 3
3. Historic IPV6-MIB . . . . . . . . . . . . . . . . . . . . . . 4 3. Historic IPV6-MIB . . . . . . . . . . . . . . . . . . . . . . 5
4. Historic IPV6-ICMP-MIB . . . . . . . . . . . . . . . . . . . 38 4. Historic IPV6-ICMP-MIB . . . . . . . . . . . . . . . . . . . 39
5. Historic IPV6-UDP-MIB . . . . . . . . . . . . . . . . . . . . 52 5. Historic IPV6-UDP-MIB . . . . . . . . . . . . . . . . . . . . 52
6. Historic IPV6-TCP-MIB . . . . . . . . . . . . . . . . . . . . 55 6. Historic IPV6-TCP-MIB . . . . . . . . . . . . . . . . . . . . 56
7. Reclassification . . . . . . . . . . . . . . . . . . . . . . 60 7. Reclassification . . . . . . . . . . . . . . . . . . . . . . 61
8. Security Considerations . . . . . . . . . . . . . . . . . . . 60 8. Security Considerations . . . . . . . . . . . . . . . . . . . 61
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.1. Normative References . . . . . . . . . . . . . . . . . . 61 10.1. Normative References . . . . . . . . . . . . . . . . . . 62
10.2. Informative References . . . . . . . . . . . . . . . . . 62 10.2. Informative References . . . . . . . . . . . . . . . . . 62
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 62 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Appendix A. Change history . . . . . . . . . . . . . . . . . . . 63 Appendix A. Change history . . . . . . . . . . . . . . . . . . . 63
A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01 . . . 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.2. Changes since draft-ietf-6man-ipv6-mibs-obsolete-00 . . . 63
A.3. Changes since draft-fenner-ipv6-mibs-obsolete-01 . . . . 63 A.3. Changes since draft-fenner-ipv6-mibs-obsolete-00 . . . . 63
A.4. Changes since draft-fenner-ipv6-mibs-obsolete-02 . . . . 63 A.4. Changes since draft-fenner-ipv6-mibs-obsolete-01 . . . . 64
A.5. Changes since draft-fenner-ipv6-mibs-obsolete-02 . . . . 64
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 64
1. Motivation 1. Motivation
In 2005, the IPv6 MIB update group published updated versions of the In 2005, the IPv6 MIB update group published updated versions of the
IP-MIB [RFC4293], UDP-MIB [RFC4113], TCP-MIB [RFC4022] and IP- IP-MIB [RFC4293], UDP-MIB [RFC4113], TCP-MIB [RFC4022] and IP-
FORWARD-MIB [RFC4292] modules, which use the InetAddressType/ FORWARD-MIB [RFC4292] modules, which use the InetAddressType/
InetAddress construct to handle IPv4 and IPv6 in the same table. InetAddress construct to handle IPv4 and IPv6 in the same table.
These documents were marked in the RFC Index as obsoleting the These documents were marked in the RFC Index as obsoleting the
corresponding IPV6-MIBs, but the extracted content of these MIBs corresponding IPV6-MIBs, but the extracted content of these MIBs
never changed in MIB repositories, and the original RFCs (as is never changed in MIB repositories, and the original RFCs (as is
normal IETF policy) never changed from being Proposed Standard. normal IETF policy) never changed from being Proposed Standard.
Note that the timeline of these MIB modules looks like shown below
(and it is the added support for IPv6 in the later revision of the
original modules that people often overlook).
IPv6-MIB--------X
\
IP-MIB-------------------IP-MIB--->
This causes an unclear situation when simply looking at MIB This causes an unclear situation when simply looking at MIB
repositories, so we are simply republishing these MIB modules with repositories, so we are simply republishing these MIB modules with
the SMI syntax changed to obsolete. the SMI syntax changed to obsolete. This is an unusual step, and is
not the intended path with every obsolete MIB module; the special
history of these modules lead to this special step.
2. Historic IPV6-TC 2. Historic IPV6-TC
IPV6-TC DEFINITIONS ::= BEGIN IPV6-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Integer32 FROM SNMPv2-SMI Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
-- definition of textual conventions -- definition of textual conventions
Ipv6Address ::= TEXTUAL-CONVENTION Ipv6Address ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:" DISPLAY-HINT "2x:"
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This data type is used to model IPv6 addresses. "This data type is used to model IPv6 addresses.
This is a binary string of 16 octets in network This is a binary string of 16 octets in network
byte-order." byte-order.
SYNTAX OCTET STRING (SIZE (16))
Ipv6AddressPrefix ::= TEXTUAL-CONVENTION This object is obsoleted by INET-ADDRESS-MIB::InetAddress."
DISPLAY-HINT "2x:" SYNTAX OCTET STRING (SIZE (16))
STATUS obsolete
DESCRIPTION
"This data type is used to model IPv6 address
prefixes. This is a binary string of up to 16
octets in network byte-order."
SYNTAX OCTET STRING (SIZE (0..16))
Ipv6AddressIfIdentifier ::= TEXTUAL-CONVENTION Ipv6AddressPrefix ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2x:" DISPLAY-HINT "2x:"
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This data type is used to model IPv6 address "This data type is used to model IPv6 address
interface identifiers. This is a binary string prefixes. This is a binary string of up to 16
of up to 8 octets in network byte-order." octets in network byte-order.
SYNTAX OCTET STRING (SIZE (0..8))
Ipv6IfIndex ::= TEXTUAL-CONVENTION This object is obsoleted by INET-ADDRESS-MIB::InetAddress."
DISPLAY-HINT "d" SYNTAX OCTET STRING (SIZE (0..16))
STATUS obsolete
DESCRIPTION
"A unique value, greater than zero for each
internetwork-layer interface in the managed
system. It is recommended that values are assigned
contiguously starting from 1. The value for each
internetwork-layer interface must remain constant
at least from one re-initialization of the entity's
network management system to the next
re-initialization."
SYNTAX Integer32 (1..2147483647)
Ipv6IfIndexOrZero ::= TEXTUAL-CONVENTION Ipv6AddressIfIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "2x:"
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the "This data type is used to model IPv6 address
Ipv6IfIndex convention. The latter defines interface identifiers. This is a binary string
a greater than zero value used to identify an IPv6 of up to 8 octets in network byte-order.
interface in the managed system. This extension
permits the additional value of zero. The value
zero is object-specific and must therefore be
defined as part of the description of any object
which uses this syntax. Examples of the usage of
zero might include situations where interface was
unknown, or when none or all interfaces need to be
referenced."
SYNTAX Integer32 (0..2147483647)
END This object is obsoleted by IP-MIB::Ipv6AddressIfIdentifierTC."
SYNTAX OCTET STRING (SIZE (0..8))
Ipv6IfIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS obsolete
DESCRIPTION
"A unique value, greater than zero for each
internetwork-layer interface in the managed
system. It is recommended that values are assigned
contiguously starting from 1. The value for each
internetwork-layer interface must remain constant
at least from one re-initialization of the entity's
network management system to the next
re-initialization.
This object is obsoleted by IF-MIB::InterfaceIndex."
SYNTAX Integer32 (1..2147483647)
Ipv6IfIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS obsolete
DESCRIPTION
"This textual convention is an extension of the
Ipv6IfIndex convention. The latter defines
a greater than zero value used to identify an IPv6
interface in the managed system. This extension
permits the additional value of zero. The value
zero is object-specific and must therefore be
defined as part of the description of any object
which uses this syntax. Examples of the usage of
zero might include situations where interface was
unknown, or when none or all interfaces need to be
referenced.
This object is obsoleted by IF-MIB::InterfaceIndexOrZero."
SYNTAX Integer32 (0..2147483647)
END
3. Historic IPV6-MIB 3. Historic IPV6-MIB
IPV6-MIB DEFINITIONS ::= BEGIN IPV6-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
mib-2, Counter32, Unsigned32, Integer32, mib-2, Counter32, Unsigned32, Integer32,
Gauge32 FROM SNMPv2-SMI Gauge32 FROM SNMPv2-SMI
DisplayString, PhysAddress, TruthValue, TimeStamp, DisplayString, PhysAddress, TruthValue, TimeStamp,
skipping to change at page 63, line 9 skipping to change at page 63, line 26
April 2006, <http://www.rfc-editor.org/info/rfc4293>. April 2006, <http://www.rfc-editor.org/info/rfc4293>.
10.3. URIs 10.3. URIs
[1] http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml [1] http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
Appendix A. Change history Appendix A. Change history
A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01 A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01
o Thanks to ops-dir comments by Dan Romascanu and Juergen
Schoenwaelder, updated the motiviation text to include Juergen's
ASCII art history and a specific mention that this is not the
intended disposition of all obsolete MIBs.
o Thanks to gen-art review by Jouni Korhonen, who pointed out that I
had neglected RFC2579's requirement to note the obsoleting object
for TEXTUAL-CONVENTIONs too.
A.2. Changes since draft-ietf-6man-ipv6-mibs-obsolete-00
Thanks to an excellent review by Mike Heard. Thanks to an excellent review by Mike Heard.
o Correct the REVISION clause for the original IPV6-MIB o Correct the REVISION clause for the original IPV6-MIB
o Remove the illegal sub-typing from SEQUENCE definitions in o Remove the illegal sub-typing from SEQUENCE definitions in
IPV6-MIB, IPV6-UDP-MIB and IPV6-TCP-MIB. IPV6-MIB, IPV6-UDP-MIB and IPV6-TCP-MIB.
A.2. Changes since draft-fenner-ipv6-mibs-obsolete-00 A.3. Changes since draft-fenner-ipv6-mibs-obsolete-00
o Realized that IPV6-ICMP-MIB was [RFC2466], so modified the added o Realized that IPV6-ICMP-MIB was [RFC2466], so modified the added
REVISION clause and the Reclassification section. REVISION clause and the Reclassification section.
o Added Security Considerations o Added Security Considerations
o Added IANA Considerations o Added IANA Considerations
o Added the 6.c.iii Legend to the copyright statement, since the o Added the 6.c.iii Legend to the copyright statement, since the
original RFCs were published before pre-5378. original RFCs were published before pre-5378.
o Used "MIB module" instead of "MIB" when referring to a module, and o Used "MIB module" instead of "MIB" when referring to a module, and
changed REVISION DESCRIPTION to "Obsoleting", not "Deprecating". changed REVISION DESCRIPTION to "Obsoleting", not "Deprecating".
o Added "Obsoletes:" header to document o Added "Obsoletes:" header to document
o Switched to pre-5378 IPR statement, since the original RFCs were o Switched to pre-5378 IPR statement, since the original RFCs were
pre-5378. pre-5378.
skipping to change at page 63, line 36 skipping to change at page 64, line 15
original RFCs were published before pre-5378. original RFCs were published before pre-5378.
o Used "MIB module" instead of "MIB" when referring to a module, and o Used "MIB module" instead of "MIB" when referring to a module, and
changed REVISION DESCRIPTION to "Obsoleting", not "Deprecating". changed REVISION DESCRIPTION to "Obsoleting", not "Deprecating".
o Added "Obsoletes:" header to document o Added "Obsoletes:" header to document
o Switched to pre-5378 IPR statement, since the original RFCs were o Switched to pre-5378 IPR statement, since the original RFCs were
pre-5378. pre-5378.
A.3. Changes since draft-fenner-ipv6-mibs-obsolete-01 A.4. Changes since draft-fenner-ipv6-mibs-obsolete-01
o Updated the DESCRIPTION of MODULE-IDENTITY to improve the "MIB o Updated the DESCRIPTION of MODULE-IDENTITY to improve the "MIB
index" problem. index" problem.
o Updated IANA considerations. o Updated IANA considerations.
A.4. Changes since draft-fenner-ipv6-mibs-obsolete-02 A.5. Changes since draft-fenner-ipv6-mibs-obsolete-02
o Fixed "IPV6-MIB" in title o Fixed "IPV6-MIB" in title
o Fixed some extra blank lines in the source MIBs, introduced by the o Fixed some extra blank lines in the source MIBs, introduced by the
process of extraction from RFCs. process of extraction from RFCs.
Author's Address Author's Address
Bill Fenner Bill Fenner
Arista Networks, Inc. Arista Networks, Inc.
 End of changes. 24 change blocks. 
79 lines changed or deleted 110 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/