draft-ietf-6man-ipv6-mibs-obsolete-02.txt   rfc8096.txt 
IPv6 Maintenance B. Fenner Internet Engineering Task Force (IETF) B. Fenner
Internet-Draft Arista Networks, Inc. Request for Comments: 8096 Arista Networks, Inc.
Obsoletes: 2452, 2454, 2465, 2466 (if November 14, 2016 Obsoletes: 2452, 2454, 2465, 2466 April 2017
approved) Category: Informational
Intended status: Informational ISSN: 2070-1721
Expires: May 18, 2017
Republishing the IPV6-specific MIB modules as obsolete The IPv6-Specific MIB Modules Are Obsolete
draft-ietf-6man-ipv6-mibs-obsolete-02
Abstract Abstract
In 2005, the IPv6 MIB update group published updated versions of the In 2005-2006, the IPv6 MIB update group published updated versions of
IP-MIB, UDP-MIB, TCP-MIB and IP-FORWARD-MIB modules, which use the the IP-MIB, UDP-MIB, TCP-MIB, and IP-FORWARD-MIB modules, which use
InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the the InetAddressType/InetAddress construct to handle IPv4 and IPv6 in
same table. This document contains versions of the obsoleted the 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. This
document obsoletes RFCs 2452, 2454, 2465, and 2466 (i.e., the RFCs
containing these MIBs) and reclassifies them as Historic.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 7841.
This Internet-Draft will expire on May 18, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8096.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 22 skipping to change at page 2, line 34
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
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 ......................................................3
2. Historic IPV6-TC . . . . . . . . . . . . . . . . . . . . . . 3 2. Historic IPV6-TC ................................................4
3. Historic IPV6-MIB . . . . . . . . . . . . . . . . . . . . . . 5 3. Historic IPV6-MIB ...............................................6
4. Historic IPV6-ICMP-MIB . . . . . . . . . . . . . . . . . . . 39 4. Historic IPV6-ICMP-MIB .........................................40
5. Historic IPV6-UDP-MIB . . . . . . . . . . . . . . . . . . . . 52 5. Historic IPV6-UDP-MIB ..........................................54
6. Historic IPV6-TCP-MIB . . . . . . . . . . . . . . . . . . . . 56 6. Historic IPV6-TCP-MIB ..........................................58
7. Reclassification . . . . . . . . . . . . . . . . . . . . . . 61 7. Reclassification ...............................................63
8. Security Considerations . . . . . . . . . . . . . . . . . . . 61 8. Security Considerations ........................................63
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 9. IANA Considerations ............................................63
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 62 10. References ....................................................64
10.1. Normative References . . . . . . . . . . . . . . . . . . 62 10.1. Normative References .....................................64
10.2. Informative References . . . . . . . . . . . . . . . . . 62 10.2. Informative References ...................................64
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Author's Address ..................................................65
Appendix A. Change history . . . . . . . . . . . . . . . . . . . 63
A.1. Changes since draft-ietf-6man-ipv6-mibs-obsolete-01 . . . 63
A.2. Changes since draft-ietf-6man-ipv6-mibs-obsolete-00 . . . 63
A.3. Changes since draft-fenner-ipv6-mibs-obsolete-00 . . . . 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
1. Motivation 1. Motivation
In 2005, the IPv6 MIB update group published updated versions of the In 2005-2006, the IPv6 MIB update group published updated versions of
IP-MIB [RFC4293], UDP-MIB [RFC4113], TCP-MIB [RFC4022] and IP- the 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. The
These documents were marked in the RFC Index as obsoleting the RFC Editor marked these documents as obsoleting the corresponding
corresponding IPV6-MIBs, but the extracted content of these MIBs IPV6-MIBs, but the extracted content of these MIBs never changed in
never changed in MIB repositories, and the original RFCs (as is MIB repositories, and the original RFCs (as is normal IETF policy)
normal IETF policy) never changed from being Proposed Standard. never changed from being Proposed Standard.
Note that the timeline of these MIB modules looks like shown below Note that the timeline of these MIB modules is as shown below (and it
(and it is the added support for IPv6 in the later revision of the is the added support for IPv6 in the later revision of the original
original modules that people often overlook). modules that people often overlook).
IPv6-MIB--------X IPv6-MIB--------X
\ \
IP-MIB-------------------IP-MIB---> 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. This is an unusual step, and is the Structure of Management Information (SMI) status changed to
not the intended path with every obsolete MIB module; the special obsolete. This is an unusual step, and it is not the intended path
history of these modules lead to this special step. with every obsolete MIB module; the special history of these modules
led to this special step.
2. Historic IPV6-TC 2. Historic IPV6-TC
IPV6-TC DEFINITIONS ::= BEGIN IPV6-TC DEFINITIONS ::= BEGIN
IMPORTS -- Copyright (c) 2017 IETF Trust and the persons identified as
Integer32 FROM SNMPv2-SMI -- authors of the code. All rights reserved.
TEXTUAL-CONVENTION FROM SNMPv2-TC;
-- definition of textual conventions -- Redistribution and use in source and binary forms, with or without
Ipv6Address ::= TEXTUAL-CONVENTION -- modification, is permitted pursuant to, and subject to the license
DISPLAY-HINT "2x:" -- terms contained in, the Simplified BSD License set forth in Section
STATUS obsolete -- 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
DESCRIPTION -- (http://trustee.ietf.org/license-info).
"This data type is used to model IPv6 addresses.
This is a binary string of 16 octets in network
byte-order.
This object is obsoleted by INET-ADDRESS-MIB::InetAddress." IMPORTS
SYNTAX OCTET STRING (SIZE (16)) Integer32 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
Ipv6AddressPrefix ::= TEXTUAL-CONVENTION -- definition of textual conventions
DISPLAY-HINT "2x:" Ipv6Address ::= TEXTUAL-CONVENTION
STATUS obsolete DISPLAY-HINT "2x:"
DESCRIPTION STATUS obsolete
"This data type is used to model IPv6 address DESCRIPTION
prefixes. This is a binary string of up to 16 "This data type is used to model IPv6 addresses.
octets in network byte-order. This is a binary string of 16 octets in network
byte-order.
This object is obsoleted by INET-ADDRESS-MIB::InetAddress." This object is obsoleted by INET-ADDRESS-MIB::InetAddress."
SYNTAX OCTET STRING (SIZE (0..16)) SYNTAX OCTET STRING (SIZE (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.
This object is obsoleted by INET-ADDRESS-MIB::InetAddress."
SYNTAX OCTET STRING (SIZE (0..16))
This object is obsoleted by IP-MIB::Ipv6AddressIfIdentifierTC." Ipv6AddressIfIdentifier ::= TEXTUAL-CONVENTION
SYNTAX OCTET STRING (SIZE (0..8)) DISPLAY-HINT "2x:"
STATUS obsolete
DESCRIPTION
"This data type is used to model IPv6 address
interface identifiers. This is a binary string
of up to 8 octets in network byte-order.
Ipv6IfIndex ::= TEXTUAL-CONVENTION This object is obsoleted by IP-MIB::Ipv6AddressIfIdentifierTC."
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 OCTET STRING (SIZE (0..8))
SYNTAX Integer32 (1..2147483647)
Ipv6IfIndexOrZero ::= TEXTUAL-CONVENTION Ipv6IfIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the "A unique value, greater than zero for each
Ipv6IfIndex convention. The latter defines internetwork-layer interface in the managed
a greater than zero value used to identify an IPv6 system. It is recommended that values are assigned
interface in the managed system. This extension contiguously starting from 1. The value for each
permits the additional value of zero. The value internetwork-layer interface must remain constant
zero is object-specific and must therefore be at least from one re-initialization of the entity's
defined as part of the description of any object network management system to the next
which uses this syntax. Examples of the usage of re-initialization.
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." This object is obsoleted by IF-MIB::InterfaceIndex."
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (1..2147483647)
END 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,
VariablePointer, RowPointer FROM SNMPv2-TC VariablePointer, RowPointer FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
Ipv6IfIndex, Ipv6Address, Ipv6AddressPrefix, Ipv6IfIndex, Ipv6Address, Ipv6AddressPrefix,
Ipv6AddressIfIdentifier, Ipv6AddressIfIdentifier,
Ipv6IfIndexOrZero FROM IPV6-TC; Ipv6IfIndexOrZero FROM IPV6-TC;
ipv6MIB MODULE-IDENTITY ipv6MIB MODULE-IDENTITY
LAST-UPDATED "201505282112Z" LAST-UPDATED "201702220000Z"
ORGANIZATION "IETF IPv6 Working Group" ORGANIZATION "IETF IPv6 Working Group"
CONTACT-INFO CONTACT-INFO
" Dimitry Haskin " Dimitry Haskin
Postal: Bay Networks, Inc. Postal: Bay Networks, Inc.
660 Techology Park Drive. 660 Technology Park Drive.
Billerica, MA 01821 Billerica, MA 01821
US US
Tel: +1-978-916-8124 Tel: +1-978-916-8124
E-mail: dhaskin@baynetworks.com E-mail: dhaskin@baynetworks.com
Steve Onishi Steve Onishi
Postal: Bay Networks, Inc. Postal: Bay Networks, Inc.
3 Federal Street 3 Federal Street
Billerica, MA 01821 Billerica, MA 01821
US US
Tel: +1-978-916-3816 Tel: +1-978-916-3816
E-mail: sonishi@baynetworks.com" E-mail: sonishi@baynetworks.com"
DESCRIPTION DESCRIPTION
"The obsolete MIB module for entities implementing the IPv6 "The obsolete MIB module for entities implementing the IPv6
protocol. Use the IP-MIB or IP-FORWARD-MIB instead." protocol. Use the IP-MIB or IP-FORWARD-MIB instead.
REVISION "201505282112Z"
Copyright (c) 2017 IETF Trust and the persons identified
as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201702220000Z"
DESCRIPTION DESCRIPTION
"Obsoleting this MIB module; it has been replaced by "Obsoleting this MIB module; it has been replaced by
the revised IP-MIB (RFC4293) and IP-FORWARD-MIB the revised IP-MIB (RFC 4293) and IP-FORWARD-MIB
(RFC4292)." (RFC 4292)."
REVISION "9802052155Z" REVISION "9802052155Z"
DESCRIPTION DESCRIPTION
"First revision, published as RFC2465" "First revision, published as RFC 2465"
::= { mib-2 55 } ::= { mib-2 55 }
-- the IPv6 general group -- the IPv6 general group
ipv6MIBObjects OBJECT IDENTIFIER ::= { ipv6MIB 1 } ipv6MIBObjects OBJECT IDENTIFIER ::= { ipv6MIB 1 }
ipv6Forwarding OBJECT-TYPE ipv6Forwarding OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
forwarding(1), -- acting as a router forwarding(1), -- acting as a router
skipping to change at page 7, line 14 skipping to change at page 8, line 27
::= { ipv6MIBObjects 2 } ::= { ipv6MIBObjects 2 }
ipv6Interfaces OBJECT-TYPE ipv6Interfaces OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The number of IPv6 interfaces (regardless of "The number of IPv6 interfaces (regardless of
their current state) present on this system. their current state) present on this system.
This object is obsolete; there is no direct replacement This object is obsolete; there is no direct replacement,
but its value can be derived from the number of rows but its value can be derived from the number of rows
in the IP-MIB::ipv6InterfaceTable." in the IP-MIB::ipv6InterfaceTable."
::= { ipv6MIBObjects 3 } ::= { ipv6MIBObjects 3 }
ipv6IfTableLastChange OBJECT-TYPE ipv6IfTableLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time of the last "The value of sysUpTime at the time of the last
insertion or removal of an entry in the insertion or removal of an entry in the
ipv6IfTable. If the number of entries has been ipv6IfTable. If the number of entries has been
unchanged since the last re-initialization of unchanged since the last re-initialization of
the local network management subsystem, then this the local network management subsystem, then this
object contains a zero value. object contains a zero value.
This object is obsoleted by This object is obsoleted by
IP-MIB::ipv6InterfaceTableLastChange." IP-MIB::ipv6InterfaceTableLastChange."
::= { ipv6MIBObjects 4 } ::= { ipv6MIBObjects 4 }
-- the IPv6 Interfaces table -- the IPv6 Interfaces table
skipping to change at page 9, line 16 skipping to change at page 10, line 28
ipv6IfLowerLayer OBJECT-TYPE ipv6IfLowerLayer OBJECT-TYPE
SYNTAX VariablePointer SYNTAX VariablePointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This object identifies the protocol layer over "This object identifies the protocol layer over
which this network interface operates. If this which this network interface operates. If this
network interface operates over the data-link network interface operates over the data-link
layer, then the value of this object refers to an layer, then the value of this object refers to an
instance of ifIndex [6]. If this network interface instance of ifIndex [RFC1573]. If this network interface
operates over an IPv4 interface, the value of this operates over an IPv4 interface, the value of this
object refers to an instance of ipAdEntAddr [3]. object refers to an instance of ipAdEntAddr [RFC1213].
If this network interface operates over another If this network interface operates over another
IPv6 interface, the value of this object refers to IPv6 interface, the value of this object refers to
an instance of ipv6IfIndex. If this network an instance of ipv6IfIndex. If this network
interface is not currently operating over an active interface is not currently operating over an active
protocol layer, then the value of this object protocol layer, then the value of this object
should be set to the OBJECT ID { 0 0 }. should be set to the OBJECT ID { 0 0 }.
This object is obsolete. The IF-STACK-TABLE may This object is obsolete. The IF-STACK-TABLE may
be used to express relationships between interfaces." be used to express relationships between interfaces."
skipping to change at page 10, line 17 skipping to change at page 11, line 30
This object is obsoleted by IP-MIB::ipv6InterfaceReasmMaxSize." This object is obsoleted by IP-MIB::ipv6InterfaceReasmMaxSize."
::= { ipv6IfEntry 5 } ::= { ipv6IfEntry 5 }
ipv6IfIdentifier OBJECT-TYPE ipv6IfIdentifier OBJECT-TYPE
SYNTAX Ipv6AddressIfIdentifier SYNTAX Ipv6AddressIfIdentifier
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The Interface Identifier for this interface that "The Interface Identifier for this interface that
is (at least) unique on the link this interface is is (at least) unique on the link this interface is
attached to. The Interface Identifier is combined attached to. The Interface Identifier is combined
with an address prefix to form an interface address. with an address prefix to form an interface address.
By default, the Interface Identifier is autoconfigured By default, the Interface Identifier is autoconfigured
according to the rules of the link type this according to the rules of the link type this
interface is attached to. interface is attached to.
This object is obsoleted by IP-MIB::ipv6InterfaceIdentifier." This object is obsoleted by IP-MIB::ipv6InterfaceIdentifier."
::= { ipv6IfEntry 6 } ::= { ipv6IfEntry 6 }
ipv6IfIdentifierLength OBJECT-TYPE ipv6IfIdentifierLength OBJECT-TYPE
skipping to change at page 10, line 45 skipping to change at page 12, line 10
This object is obsolete. It can be derived from the length This object is obsolete. It can be derived from the length
of IP-MIB::ipv6InterfaceIdentifier; Interface Identifiers of IP-MIB::ipv6InterfaceIdentifier; Interface Identifiers
that are not an even number of octets are not supported." that are not an even number of octets are not supported."
::= { ipv6IfEntry 7 } ::= { ipv6IfEntry 7 }
ipv6IfPhysicalAddress OBJECT-TYPE ipv6IfPhysicalAddress OBJECT-TYPE
SYNTAX PhysAddress SYNTAX PhysAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The interface's physical address. For example, for "The interface's physical address. For example, for
an IPv6 interface attached to an 802.x link, this an IPv6 interface attached to an 802.x link, this
object normally contains a MAC address. Note that object normally contains a MAC address. Note that
in some cases this address may differ from the in some cases this address may differ from the
address of the interface's protocol sub-layer. The address of the interface's protocol sub-layer. The
interface's media-specific MIB must define the bit interface's media-specific MIB must define the bit
and byte ordering and the format of the value of and byte ordering and the format of the value of
this object. For interfaces which do not have such this object. For interfaces which do not have such
an address (e.g., a serial line), this object should an address (e.g., a serial line), this object should
contain an octet string of zero length. contain an octet string of zero length.
This object is obsoleted by IF-MIB::ifPhysAddress." This object is obsoleted by IF-MIB::ifPhysAddress."
::= { ipv6IfEntry 8 } ::= { ipv6IfEntry 8 }
ipv6IfAdminStatus OBJECT-TYPE ipv6IfAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- ready to pass packets up(1), -- ready to pass packets
down(2) down(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The desired state of the interface. When a managed "The desired state of the interface. When a managed
system initializes, all IPv6 interfaces start with system initializes, all IPv6 interfaces start with
ipv6IfAdminStatus in the down(2) state. As a result ipv6IfAdminStatus in the down(2) state. As a result
of either explicit management action or per of either explicit management action or per
configuration information retained by the managed configuration information retained by the managed
system, ipv6IfAdminStatus is then changed to system, ipv6IfAdminStatus is then changed to
the up(1) state (or remains in the down(2) state). the up(1) state (or remains in the down(2) state).
This object is obsolete. IPv6 does not have a This object is obsolete. IPv6 does not have a
separate admin status; the admin status of the separate admin status; the admin status of the
interface is represented by IF-MIB::ifAdminStatus." interface is represented by IF-MIB::ifAdminStatus."
::= { ipv6IfEntry 9 } ::= { ipv6IfEntry 9 }
ipv6IfOperStatus OBJECT-TYPE ipv6IfOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- ready to pass packets up(1), -- ready to pass packets
skipping to change at page 15, line 38 skipping to change at page 16, line 50
This object is obsoleted by IP-MIB::ipIfStatsInAddrErrors." This object is obsoleted by IP-MIB::ipIfStatsInAddrErrors."
::= { ipv6IfStatsEntry 5 } ::= { ipv6IfStatsEntry 5 }
ipv6IfStatsInUnknownProtos OBJECT-TYPE ipv6IfStatsInUnknownProtos OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The number of locally-addressed datagrams "The number of locally-addressed datagrams
received successfully but discarded because of an received successfully but discarded because of an
unknown or unsupported protocol. This counter is unknown or unsupported protocol. This counter is
incremented at the interface to which these incremented at the interface to which these
datagrams were addressed which might not be datagrams were addressed which might not be
necessarily the input interface for some of necessarily the input interface for some of
the datagrams. the datagrams.
This object is obsoleted by IP-MIB::ipIfStatsInUnknownProtos." This object is obsoleted by IP-MIB::ipIfStatsInUnknownProtos."
::= { ipv6IfStatsEntry 6 } ::= { ipv6IfStatsEntry 6 }
ipv6IfStatsInTruncatedPkts OBJECT-TYPE ipv6IfStatsInTruncatedPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 21, line 22 skipping to change at page 22, line 34
This object is obsoleted by IP-MIB::ipAddressPrefixLength." This object is obsoleted by IP-MIB::ipAddressPrefixLength."
::= { ipv6AddrPrefixEntry 2 } ::= { ipv6AddrPrefixEntry 2 }
ipv6AddrPrefixOnLinkFlag OBJECT-TYPE ipv6AddrPrefixOnLinkFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"This object has the value 'true(1)', if this "This object has the value 'true(1)', if this
prefix can be used for on-link determination prefix can be used for on-link determination
and the value 'false(2)' otherwise. and the value 'false(2)' otherwise.
This object is obsoleted by IP-MIB::ipAddressPrefixOnLinkFlag." This object is obsoleted by IP-MIB::ipAddressPrefixOnLinkFlag."
::= { ipv6AddrPrefixEntry 3 } ::= { ipv6AddrPrefixEntry 3 }
ipv6AddrPrefixAutonomousFlag OBJECT-TYPE ipv6AddrPrefixAutonomousFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"Autonomous address configuration flag. When "Autonomous address configuration flag. When
true(1), indicates that this prefix can be used true(1), indicates that this prefix can be used
for autonomous address configuration (i.e. can for autonomous address configuration (i.e. can
be used to form a local interface address). be used to form a local interface address).
If false(2), it is not used to autoconfigure If false(2), it is not used to autoconfigure
a local interface address. a local interface address.
This object is obsoleted by This object is obsoleted by
IP-MIB::ipAddressPrefixAutonomousFlag." IP-MIB::ipAddressPrefixAutonomousFlag."
::= { ipv6AddrPrefixEntry 4 } ::= { ipv6AddrPrefixEntry 4 }
skipping to change at page 24, line 18 skipping to change at page 25, line 29
-- by stateful means -- by stateful means
-- (e.g. DHCPv6, manual -- (e.g. DHCPv6, manual
stateful(2), -- configuration) stateful(2), -- configuration)
-- type can not be determined -- type can not be determined
unknown(3) -- for some reason. unknown(3) -- for some reason.
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The type of address. Note that 'stateless(1)' "The type of address. Note that 'stateless(1)'
refers to an address that was statelessly refers to an address that was statelessly
autoconfigured; 'stateful(2)' refers to a address autoconfigured; 'stateful(2)' refers to a address
which was acquired by via a stateful protocol which was acquired by via a stateful protocol
(e.g. DHCPv6, manual configuration). (e.g. DHCPv6, manual configuration).
This object is obsoleted by IP-MIB::ipAddressOrigin." This object is obsoleted by IP-MIB::ipAddressOrigin."
::= { ipv6AddrEntry 3 } ::= { ipv6AddrEntry 3 }
ipv6AddrAnycastFlag OBJECT-TYPE ipv6AddrAnycastFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
skipping to change at page 25, line 10 skipping to change at page 26, line 22
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"Address status. The preferred(1) state indicates "Address status. The preferred(1) state indicates
that this is a valid address that can appear as that this is a valid address that can appear as
the destination or source address of a packet. the destination or source address of a packet.
The deprecated(2) state indicates that this is The deprecated(2) state indicates that this is
a valid but deprecated address that should no longer a valid but deprecated address that should no longer
be used as a source address in new communications, be used as a source address in new communications,
but packets addressed to such an address are but packets addressed to such an address are
processed as expected. The invalid(3) state indicates processed as expected. The invalid(3) state indicates
that this is not valid address which should not that this is not valid address which should not
appear as the destination or source address of appear as the destination or source address of
a packet. The inaccessible(4) state indicates that a packet. The inaccessible(4) state indicates that
the address is not accessible because the interface the address is not accessible because the interface
to which this address is assigned is not operational. to which this address is assigned is not operational.
This object is obsoleted by IP-MIB::ipAddressStatus." This object is obsoleted by IP-MIB::ipAddressStatus."
::= { ipv6AddrEntry 5 } ::= { ipv6AddrEntry 5 }
-- IPv6 Routing objects -- IPv6 Routing objects
ipv6RouteNumber OBJECT-TYPE ipv6RouteNumber OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
skipping to change at page 26, line 8 skipping to change at page 27, line 20
IP-FORWARD-MIB::inetCidrRouteDiscards." IP-FORWARD-MIB::inetCidrRouteDiscards."
::= { ipv6MIBObjects 10 } ::= { ipv6MIBObjects 10 }
-- IPv6 Routing table -- IPv6 Routing table
ipv6RouteTable OBJECT-TYPE ipv6RouteTable OBJECT-TYPE
SYNTAX SEQUENCE OF Ipv6RouteEntry SYNTAX SEQUENCE OF Ipv6RouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"IPv6 Routing table. This table contains "IPv6 Routing table. This table contains
an entry for each valid IPv6 unicast route an entry for each valid IPv6 unicast route
that can be used for packet forwarding that can be used for packet forwarding
determination. determination.
This table is obsoleted by IP-FORWARD-MIB::inetCidrRouteTable." This table is obsoleted by IP-FORWARD-MIB::inetCidrRouteTable."
::= { ipv6MIBObjects 11 } ::= { ipv6MIBObjects 11 }
ipv6RouteEntry OBJECT-TYPE ipv6RouteEntry OBJECT-TYPE
SYNTAX Ipv6RouteEntry SYNTAX Ipv6RouteEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 28, line 41 skipping to change at page 30, line 5
local(3), -- connected (sub-)network local(3), -- connected (sub-)network
-- route to a remote -- route to a remote
remote(4) -- destination remote(4) -- destination
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The type of route. Note that 'local(3)' refers "The type of route. Note that 'local(3)' refers
to a route for which the next hop is the final to a route for which the next hop is the final
destination; 'remote(4)' refers to a route for destination; 'remote(4)' refers to a route for
which the next hop is not the final which the next hop is not the final
destination; 'discard(2)' refers to a route destination; 'discard(2)' refers to a route
indicating that packets to destinations matching indicating that packets to destinations matching
this route are to be discarded (sometimes called this route are to be discarded (sometimes called
black-hole route). black-hole route).
This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteType." This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteType."
::= { ipv6RouteEntry 6 } ::= { ipv6RouteEntry 6 }
ipv6RouteProtocol OBJECT-TYPE ipv6RouteProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 29, line 52 skipping to change at page 31, line 16
selection of one multipath route (set of next hops selection of one multipath route (set of next hops
for a given destination) is referred to as 'policy'. for a given destination) is referred to as 'policy'.
Unless the mechanism indicated by ipv6RouteProtocol Unless the mechanism indicated by ipv6RouteProtocol
specified otherwise, the policy specifier is the specified otherwise, the policy specifier is the
8-bit Traffic Class field of the IPv6 packet header 8-bit Traffic Class field of the IPv6 packet header
that is zero extended at the left to a 32-bit value. that is zero extended at the left to a 32-bit value.
Protocols defining 'policy' otherwise must either Protocols defining 'policy' otherwise must either
define a set of values which are valid for define a set of values which are valid for
this object or must implement an integer- this object or must implement an integer-
instanced policy table for which this object's instanced policy table for which this object's
value acts as an index. value acts as an index.
This object is obsoleted by IP-FORWARD-MIB::inetCidrRoutePolicy." This object is obsoleted by IP-FORWARD-MIB::inetCidrRoutePolicy."
::= { ipv6RouteEntry 8 } ::= { ipv6RouteEntry 8 }
ipv6RouteAge OBJECT-TYPE ipv6RouteAge OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
skipping to change at page 30, line 30 skipping to change at page 31, line 43
This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteAge." This object is obsoleted by IP-FORWARD-MIB::inetCidrRouteAge."
::= { ipv6RouteEntry 9 } ::= { ipv6RouteEntry 9 }
ipv6RouteNextHopRDI OBJECT-TYPE ipv6RouteNextHopRDI OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The Routing Domain ID of the Next Hop. "The Routing Domain ID of the Next Hop.
The semantics of this object are determined by The semantics of this object are determined by
the routing-protocol specified in the route's the routing-protocol specified in the route's
ipv6RouteProtocol value. When this object is ipv6RouteProtocol value. When this object is
unknown or not relevant its value should be set unknown or not relevant its value should be set
to zero. to zero.
This object is obsolete, and has no replacement. This object is obsolete, and it has no replacement.
The Routing Domain ID concept did not catch on." The Routing Domain ID concept did not catch on."
::= { ipv6RouteEntry 10 } ::= { ipv6RouteEntry 10 }
ipv6RouteMetric OBJECT-TYPE ipv6RouteMetric OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The routing metric for this route. The "The routing metric for this route. The
semantics of this metric are determined by the semantics of this metric are determined by the
routing protocol specified in the route's routing protocol specified in the route's
ipv6RouteProtocol value. When this is unknown ipv6RouteProtocol value. When this is unknown
or not relevant to the protocol indicated by or not relevant to the protocol indicated by
ipv6RouteProtocol, the object value should be ipv6RouteProtocol, the object value should be
set to its maximum value (4,294,967,295). set to its maximum value (4,294,967,295).
This object is obsoleted by This object is obsoleted by
IP-FORWARD-MIB::inetCidrRouteMetric1." IP-FORWARD-MIB::inetCidrRouteMetric1."
::= { ipv6RouteEntry 11 } ::= { ipv6RouteEntry 11 }
ipv6RouteWeight OBJECT-TYPE ipv6RouteWeight OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The system internal weight value for this route. "The system internal weight value for this route.
The semantics of this value are determined by The semantics of this value are determined by
the implementation specific rules. Generally, the implementation specific rules. Generally,
within routes with the same ipv6RoutePolicy value, within routes with the same ipv6RoutePolicy value,
the lower the weight value the more preferred is the lower the weight value the more preferred is
the route. the route.
This object is obsoleted, and has not been replaced." This object is obsoleted, and it has not been replaced."
::= { ipv6RouteEntry 12 } ::= { ipv6RouteEntry 12 }
ipv6RouteInfo OBJECT-TYPE ipv6RouteInfo OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"A reference to MIB definitions specific to the "A reference to MIB definitions specific to the
particular routing protocol which is responsible particular routing protocol which is responsible
for this route, as determined by the value for this route, as determined by the value
specified in the route's ipv6RouteProto value. specified in the route's ipv6RouteProto value.
If this information is not present, its value If this information is not present, its value
should be set to the OBJECT ID { 0 0 }, should be set to the OBJECT ID { 0 0 },
which is a syntactically valid object identifier, which is a syntactically valid object identifier,
and any implementation conforming to ASN.1 and any implementation conforming to ASN.1
and the Basic Encoding Rules must be able to and the Basic Encoding Rules must be able to
generate and recognize this value. generate and recognize this value.
This object is obsoleted, and has not been replaced." This object is obsoleted, and it has not been replaced."
::= { ipv6RouteEntry 13 } ::= { ipv6RouteEntry 13 }
ipv6RouteValid OBJECT-TYPE ipv6RouteValid OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"Setting this object to the value 'false(2)' has "Setting this object to the value 'false(2)' has
the effect of invalidating the corresponding entry the effect of invalidating the corresponding entry
in the ipv6RouteTable object. That is, it in the ipv6RouteTable object. That is, it
skipping to change at page 33, line 51 skipping to change at page 35, line 15
ipv6NetToMediaType OBJECT-TYPE ipv6NetToMediaType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- none of the following other(1), -- none of the following
dynamic(2), -- dynamically resolved dynamic(2), -- dynamically resolved
static(3), -- statically configured static(3), -- statically configured
local(4) -- local interface local(4) -- local interface
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The type of the mapping. The 'dynamic(2)' type "The type of the mapping. The 'dynamic(2)' type
indicates that the IPv6 address to physical indicates that the IPv6 address to physical
addresses mapping has been dynamically addresses mapping has been dynamically
resolved using the IPv6 Neighbor Discovery resolved using the IPv6 Neighbor Discovery
protocol. The static(3)' types indicates that protocol. The static(3)' types indicates that
the mapping has been statically configured. the mapping has been statically configured.
The local(4) indicates that the mapping is The local(4) indicates that the mapping is
provided for an entity's own interface address. provided for an entity's own interface address.
This object is obsoleted by IP-MIB::ipNetToPhysicalType." This object is obsoleted by IP-MIB::ipNetToPhysicalType."
::= { ipv6NetToMediaEntry 3 } ::= { ipv6NetToMediaEntry 3 }
ipv6IfNetToMediaState OBJECT-TYPE ipv6IfNetToMediaState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
reachable(1), -- confirmed reachability reachable(1), -- confirmed reachability
skipping to change at page 34, line 34 skipping to change at page 35, line 47
probe(4), -- actively probing probe(4), -- actively probing
invalid(5), -- an invalidated mapping invalid(5), -- an invalidated mapping
unknown(6) -- state can not be determined unknown(6) -- state can not be determined
-- for some reason. -- for some reason.
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The Neighbor Unreachability Detection [8] state "The Neighbor Unreachability Detection [RFC2461] state
for the interface when the address mapping in for the interface when the address mapping in
this entry is used. this entry is used.
This object is obsoleted by IP-MIB::ipNetToPhysicalState." This object is obsoleted by IP-MIB::ipNetToPhysicalState."
::= { ipv6NetToMediaEntry 4 } ::= { ipv6NetToMediaEntry 4 }
ipv6IfNetToMediaLastUpdated OBJECT-TYPE ipv6IfNetToMediaLastUpdated OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
skipping to change at page 35, line 34 skipping to change at page 36, line 45
entries requires examination of the relevant entries requires examination of the relevant
ipv6NetToMediaValid object. ipv6NetToMediaValid object.
This object is obsoleted by IP-MIB::ipNetToPhysicalRowStatus." This object is obsoleted by IP-MIB::ipNetToPhysicalRowStatus."
DEFVAL { true } DEFVAL { true }
::= { ipv6NetToMediaEntry 6 } ::= { ipv6NetToMediaEntry 6 }
-- definition of IPv6-related notifications. -- definition of IPv6-related notifications.
-- Note that we need ipv6NotificationPrefix with the 0 -- Note that we need ipv6NotificationPrefix with the 0
-- sub-identifier to make this MIB to translate to -- sub-identifier to make this MIB to translate to
-- an SNMPv1 format in a reversible way. For example
-- it is needed for proxies that convert SNMPv1 traps -- it is needed for proxies that convert SNMPv1 traps
-- to SNMPv2 notifications without MIB knowledge. -- to SNMPv2 notifications without MIB knowledge.
ipv6Notifications OBJECT IDENTIFIER ipv6Notifications OBJECT IDENTIFIER
::= { ipv6MIB 2 } ::= { ipv6MIB 2 }
ipv6NotificationPrefix OBJECT IDENTIFIER ipv6NotificationPrefix OBJECT IDENTIFIER
::= { ipv6Notifications 0 } ::= { ipv6Notifications 0 }
ipv6IfStateChange NOTIFICATION-TYPE ipv6IfStateChange NOTIFICATION-TYPE
OBJECTS { OBJECTS {
skipping to change at page 39, line 24 skipping to change at page 40, line 34
IPV6-ICMP-MIB DEFINITIONS ::= BEGIN IPV6-ICMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, mib-2 FROM SNMPv2-SMI Counter32, mib-2 FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
ipv6IfEntry FROM IPV6-MIB; ipv6IfEntry FROM IPV6-MIB;
ipv6IcmpMIB MODULE-IDENTITY ipv6IcmpMIB MODULE-IDENTITY
LAST-UPDATED "201505282112Z" LAST-UPDATED "201702220000Z"
ORGANIZATION "IETF IPv6 Working Group" ORGANIZATION "IETF IPv6 Working Group"
CONTACT-INFO CONTACT-INFO
" Dimitry Haskin " Dimitry Haskin
Postal: Bay Networks, Inc. Postal: Bay Networks, Inc.
660 Techology Park Drive. 660 Technology Park Drive.
Billerica, MA 01821 Billerica, MA 01821
US US
Tel: +1-978-916-8124 Tel: +1-978-916-8124
E-mail: dhaskin@baynetworks.com E-mail: dhaskin@baynetworks.com
Steve Onishi Steve Onishi
Postal: Bay Networks, Inc. Postal: Bay Networks, Inc.
3 Federal Street 3 Federal Street
Billerica, MA 01821 Billerica, MA 01821
US US
Tel: +1-978-916-3816 Tel: +1-978-916-3816
E-mail: sonishi@baynetworks.com" E-mail: sonishi@baynetworks.com"
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 48 skipping to change at page 41, line 15
Postal: Bay Networks, Inc. Postal: Bay Networks, Inc.
3 Federal Street 3 Federal Street
Billerica, MA 01821 Billerica, MA 01821
US US
Tel: +1-978-916-3816 Tel: +1-978-916-3816
E-mail: sonishi@baynetworks.com" E-mail: sonishi@baynetworks.com"
DESCRIPTION DESCRIPTION
"The obsolete MIB module for entities implementing "The obsolete MIB module for entities implementing
the ICMPv6. Use the IP-MIB instead." the ICMPv6. Use the IP-MIB instead.
REVISION "201505282112Z"
Copyright (c) 2017 IETF Trust and the persons
identified as authors of the code. All rights
reserved.
Redistribution and use in source and binary
forms, with or without modification, is permitted
pursuant to, and subject to the license terms contained
in, the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to
IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201702220000Z"
DESCRIPTION DESCRIPTION
"Obsoleting this MIB module; it has been replaced by "Obsoleting this MIB module; it has been replaced by
the revised IP-MIB (RFC4293)." the revised IP-MIB (RFC 4293)."
REVISION "9801082155Z" REVISION "9801082155Z"
DESCRIPTION DESCRIPTION
"First revision, published as RFC2466" "First revision, published as RFC 2466"
::= { mib-2 56 } ::= { mib-2 56 }
-- the ICMPv6 group -- the ICMPv6 group
ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 } ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 }
-- Per-interface ICMPv6 statistics table -- Per-interface ICMPv6 statistics table
ipv6IfIcmpTable OBJECT-TYPE ipv6IfIcmpTable OBJECT-TYPE
SYNTAX SEQUENCE OF Ipv6IfIcmpEntry SYNTAX SEQUENCE OF Ipv6IfIcmpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"IPv6 ICMP statistics. This table contains statistics "IPv6 ICMP statistics. This table contains statistics
of ICMPv6 messages that are received and sourced by of ICMPv6 messages that are received and sourced by
the entity. the entity.
This table is obsolete, because systems were found This table is obsolete because systems were found
not to maintain these statistics per-interface." not to maintain these statistics per-interface."
::= { ipv6IcmpMIBObjects 1 } ::= { ipv6IcmpMIBObjects 1 }
ipv6IfIcmpEntry OBJECT-TYPE ipv6IfIcmpEntry OBJECT-TYPE
SYNTAX Ipv6IfIcmpEntry SYNTAX Ipv6IfIcmpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"An ICMPv6 statistics entry containing "An ICMPv6 statistics entry containing
objects at a particular IPv6 interface. objects at a particular IPv6 interface.
Note that a receiving interface is Note that a receiving interface is
the interface to which a given ICMPv6 message the interface to which a given ICMPv6 message
is addressed which may not be necessarily is addressed which may not be necessarily
the input interface for the message. the input interface for the message.
Similarly, the sending interface is Similarly, the sending interface is
the interface that sources a given the interface that sources a given
ICMP message which is usually but not ICMP message which is usually but not
necessarily the output interface for the message. necessarily the output interface for the message.
This table is obsolete, because systems were found This table is obsolete because systems were found
not to maintain these statistics per-interface." not to maintain these statistics per-interface."
AUGMENTS { ipv6IfEntry } AUGMENTS { ipv6IfEntry }
::= { ipv6IfIcmpTable 1 } ::= { ipv6IfIcmpTable 1 }
Ipv6IfIcmpEntry ::= SEQUENCE { Ipv6IfIcmpEntry ::= SEQUENCE {
ipv6IfIcmpInMsgs ipv6IfIcmpInMsgs
Counter32 , Counter32 ,
ipv6IfIcmpInErrors ipv6IfIcmpInErrors
Counter32 , Counter32 ,
ipv6IfIcmpInDestUnreachs ipv6IfIcmpInDestUnreachs
skipping to change at page 42, line 25 skipping to change at page 44, line 4
ipv6IfIcmpOutNeighborAdvertisements ipv6IfIcmpOutNeighborAdvertisements
Counter32 , Counter32 ,
ipv6IfIcmpOutRedirects ipv6IfIcmpOutRedirects
Counter32 , Counter32 ,
ipv6IfIcmpOutGroupMembQueries ipv6IfIcmpOutGroupMembQueries
Counter32 , Counter32 ,
ipv6IfIcmpOutGroupMembResponses ipv6IfIcmpOutGroupMembResponses
Counter32 , Counter32 ,
ipv6IfIcmpOutGroupMembReductions ipv6IfIcmpOutGroupMembReductions
Counter32 Counter32
} }
ipv6IfIcmpInMsgs OBJECT-TYPE ipv6IfIcmpInMsgs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The total number of ICMP messages received "The total number of ICMP messages received
by the interface which includes all those by the interface which includes all those
counted by ipv6IfIcmpInErrors. Note that this counted by ipv6IfIcmpInErrors. Note that this
interface is the interface to which the interface is the interface to which the
ICMP messages were addressed which may not be ICMP messages were addressed which may not be
necessarily the input interface for the messages. necessarily the input interface for the messages.
This object has been obsoleted by IP-MIB::icmpStatsInMsgs." This object has been obsoleted by IP-MIB::icmpStatsInMsgs."
::= { ipv6IfIcmpEntry 1 } ::= { ipv6IfIcmpEntry 1 }
ipv6IfIcmpInErrors OBJECT-TYPE ipv6IfIcmpInErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 50, line 18 skipping to change at page 51, line 44
This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts
in the row corresponding to this message type." in the row corresponding to this message type."
::= { ipv6IfIcmpEntry 30 } ::= { ipv6IfIcmpEntry 30 }
ipv6IfIcmpOutRedirects OBJECT-TYPE ipv6IfIcmpOutRedirects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The number of Redirect messages sent. For "The number of Redirect messages sent. For
a host, this object will always be zero, a host, this object will always be zero,
since hosts do not send redirects. since hosts do not send redirects.
This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts This object has been obsoleted by IP-MIB::icmpMsgStatsOutPkts
in the row corresponding to this message type." in the row corresponding to this message type."
::= { ipv6IfIcmpEntry 31 } ::= { ipv6IfIcmpEntry 31 }
ipv6IfIcmpOutGroupMembQueries OBJECT-TYPE ipv6IfIcmpOutGroupMembQueries OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 52, line 47 skipping to change at page 54, line 26
IPV6-UDP-MIB DEFINITIONS ::= BEGIN IPV6-UDP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
mib-2, experimental FROM SNMPv2-SMI mib-2, experimental FROM SNMPv2-SMI
Ipv6Address, Ipv6IfIndexOrZero FROM IPV6-TC; Ipv6Address, Ipv6IfIndexOrZero FROM IPV6-TC;
ipv6UdpMIB MODULE-IDENTITY ipv6UdpMIB MODULE-IDENTITY
LAST-UPDATED "201505282112Z" LAST-UPDATED "201702220000Z"
ORGANIZATION "IETF IPv6 MIB Working Group" ORGANIZATION "IETF IPv6 MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Mike Daniele " Mike Daniele
Postal: Compaq Computer Corporation Postal: Compaq Computer Corporation
110 Spitbrook Rd 110 Spitbrook Rd
Nashua, NH 03062. Nashua, NH 03062.
US US
Phone: +1 603 884 1423 Phone: +1 603 884 1423
Email: daniele@zk3.dec.com" Email: daniele@zk3.dec.com"
DESCRIPTION DESCRIPTION
"The obsolete MIB module for entities implementing UDP "The obsolete MIB module for entities implementing UDP
over IPv6. Use the UDP-MIB instead." over IPv6. Use the UDP-MIB instead.
REVISION "201505282112Z"
Copyright (c) 2017 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms,
with or without modification, is permitted pursuant to,
and subject to the license terms contained in, the
Simplified BSD License set forth in Section 4.c of the IETF
Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201702220000Z"
DESCRIPTION DESCRIPTION
"Obsoleting this MIB module; it has been replaced by "Obsoleting this MIB module; it has been replaced by
the revised UDP-MIB (RFC4113)." the revised UDP-MIB (RFC 4113)."
REVISION "9801290000Z" REVISION "9801290000Z"
DESCRIPTION DESCRIPTION
"First revision, published as RFC2454" "First revision, published as RFC 2454"
::= { experimental 87 } ::= { experimental 87 }
-- objects specific to UDP for IPv6 -- objects specific to UDP for IPv6
udp OBJECT IDENTIFIER ::= { mib-2 7 } udp OBJECT IDENTIFIER ::= { mib-2 7 }
-- the UDP over IPv6 Listener table -- the UDP over IPv6 Listener table
-- This table contains information about this entity's -- This table contains information about this entity's
-- UDP/IPv6 endpoints. Only endpoints utilizing IPv6 addresses -- UDP/IPv6 endpoints. Only endpoints utilizing IPv6 addresses
skipping to change at page 56, line 13 skipping to change at page 58, line 7
"The group of objects providing management of "The group of objects providing management of
UDP over IPv6. UDP over IPv6.
This group is obsoleted by several groups in UDP-MIB." This group is obsoleted by several groups in UDP-MIB."
::= { ipv6UdpGroups 1 } ::= { ipv6UdpGroups 1 }
END END
6. Historic IPV6-TCP-MIB 6. Historic IPV6-TCP-MIB
IPV6-TCP-MIB DEFINITIONS ::= BEGIN IPV6-TCP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
mib-2, experimental FROM SNMPv2-SMI mib-2, experimental FROM SNMPv2-SMI
Ipv6Address, Ipv6IfIndexOrZero FROM IPV6-TC; Ipv6Address, Ipv6IfIndexOrZero FROM IPV6-TC;
ipv6TcpMIB MODULE-IDENTITY ipv6TcpMIB MODULE-IDENTITY
LAST-UPDATED "201505282112Z" LAST-UPDATED "201702220000Z"
ORGANIZATION "IETF IPv6 MIB Working Group" ORGANIZATION "IETF IPv6 MIB Working Group"
CONTACT-INFO CONTACT-INFO
" Mike Daniele " Mike Daniele
Postal: Compaq Computer Corporation Postal: Compaq Computer Corporation
110 Spitbrook Rd 110 Spitbrook Rd
Nashua, NH 03062. Nashua, NH 03062.
US US
Phone: +1 603 884 1423 Phone: +1 603 884 1423
Email: daniele@zk3.dec.com" Email: daniele@zk3.dec.com"
DESCRIPTION DESCRIPTION
"The obsolete MIB module for entities implementing TCP "The obsolete MIB module for entities implementing TCP
over IPv6. Use the TCP-MIB instead." over IPv6. Use the TCP-MIB instead.
REVISION "201505282112Z"
DESCRIPTION
"Obsoleting this MIB module; it has been replaced by
the revised TCP-MIB (RFC4022)."
REVISION "9801290000Z"
DESCRIPTION
"First revision, published as RFC2452"
::= { experimental 86 }
Copyright (c) 2017 IETF Trust and the persons identified
as authors of the code. All rights reserved.
tcp OBJECT IDENTIFIER ::= { mib-2 6 } Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
subject to the license terms contained in, the Simplified
BSD License set forth in Section 4.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201702220000Z"
DESCRIPTION
"Obsoleting this MIB module; it has been replaced by
the revised TCP-MIB (RFC 4022)."
REVISION "9801290000Z"
DESCRIPTION
"First revision, published as RFC 2452"
::= { experimental 86 }
-- objects specific to TCP for IPv6
ipv6TcpConnTable OBJECT-TYPE tcp OBJECT IDENTIFIER ::= { mib-2 6 }
SYNTAX SEQUENCE OF Ipv6TcpConnEntry -- the TCP over IPv6 Connection table
MAX-ACCESS not-accessible
STATUS obsolete
DESCRIPTION
"A table containing TCP connection-specific information,
for only those connections whose endpoints are IPv6 addresses.
This table is obsoleted by TCP-MIB::tcpConnectionTable." -- This connection table contains information about this
::= { tcp 16 } -- entity's existing TCP connections between IPv6 endpoints.
-- Only connections between IPv6 addresses are contained in
-- this table. This entity's connections between IPv4
-- endpoints are contained in tcpConnTable.
ipv6TcpConnEntry OBJECT-TYPE ipv6TcpConnTable OBJECT-TYPE
SYNTAX Ipv6TcpConnEntry SYNTAX SEQUENCE OF Ipv6TcpConnEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"A conceptual row of the ipv6TcpConnTable containing "A table containing TCP connection-specific information,
information about a particular current TCP connection. for only those connections whose endpoints are IPv6 addresses.
Each row of this table is transient, in that it ceases to
exist when (or soon after) the connection makes the transition
to the CLOSED state.
Note that conceptual rows in this table require an additional This table is obsoleted by TCP-MIB::tcpConnectionTable."
index object compared to tcpConnTable, since IPv6 addresses ::= { tcp 16 }
are not guaranteed to be unique on the managed node.
This entry is obsoleted by TCP-MIB::tcpConnectionEntry." ipv6TcpConnEntry OBJECT-TYPE
INDEX { ipv6TcpConnLocalAddress, SYNTAX Ipv6TcpConnEntry
ipv6TcpConnLocalPort, MAX-ACCESS not-accessible
ipv6TcpConnRemAddress, STATUS obsolete
ipv6TcpConnRemPort, DESCRIPTION
ipv6TcpConnIfIndex } "A conceptual row of the ipv6TcpConnTable containing
::= { ipv6TcpConnTable 1 } information about a particular current TCP connection.
Each row of this table is transient, in that it ceases to
exist when (or soon after) the connection makes the transition
to the CLOSED state.
Ipv6TcpConnEntry ::= Note that conceptual rows in this table require an additional
SEQUENCE { ipv6TcpConnLocalAddress Ipv6Address, index object compared to tcpConnTable, since IPv6 addresses
ipv6TcpConnLocalPort INTEGER, are not guaranteed to be unique on the managed node.
ipv6TcpConnRemAddress Ipv6Address,
ipv6TcpConnRemPort INTEGER,
ipv6TcpConnIfIndex Ipv6IfIndexOrZero,
ipv6TcpConnState INTEGER }
ipv6TcpConnLocalAddress OBJECT-TYPE This entry is obsoleted by TCP-MIB::tcpConnectionEntry."
SYNTAX Ipv6Address INDEX { ipv6TcpConnLocalAddress,
MAX-ACCESS not-accessible ipv6TcpConnLocalPort,
STATUS obsolete ipv6TcpConnRemAddress,
DESCRIPTION ipv6TcpConnRemPort,
"The local IPv6 address for this TCP connection. In ipv6TcpConnIfIndex }
the case of a connection in the listen state which ::= { ipv6TcpConnTable 1 }
is willing to accept connections for any IPv6
address associated with the managed node, the value
::0 is used.
This object is obsoleted by Ipv6TcpConnEntry ::=
TCP-MIB::tcpConnectionLocalAddressType." SEQUENCE { ipv6TcpConnLocalAddress Ipv6Address,
::= { ipv6TcpConnEntry 1 } ipv6TcpConnLocalPort INTEGER,
ipv6TcpConnRemAddress Ipv6Address,
ipv6TcpConnRemPort INTEGER,
ipv6TcpConnIfIndex Ipv6IfIndexOrZero,
ipv6TcpConnState INTEGER }
ipv6TcpConnLocalPort OBJECT-TYPE ipv6TcpConnLocalAddress OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX Ipv6Address
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The local port number for this TCP connection. "The local IPv6 address for this TCP connection. In
the case of a connection in the listen state which
is willing to accept connections for any IPv6
address associated with the managed node, the value
::0 is used.
This object is obsoleted by TCP-MIB::tcpConnectionLocalPort." This object is obsoleted by
::= { ipv6TcpConnEntry 2 } TCP-MIB::tcpConnectionLocalAddressType."
::= { ipv6TcpConnEntry 1 }
ipv6TcpConnRemAddress OBJECT-TYPE ipv6TcpConnLocalPort OBJECT-TYPE
SYNTAX Ipv6Address SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The remote IPv6 address for this TCP connection. "The local port number for this TCP connection.
This object is obsoleted by TCP-MIB::tcpConnectionRemAddress." This object is obsoleted by TCP-MIB::tcpConnectionLocalPort."
::= { ipv6TcpConnEntry 3 } ::= { ipv6TcpConnEntry 2 }
ipv6TcpConnRemPort OBJECT-TYPE ipv6TcpConnRemAddress OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX Ipv6Address
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The remote port number for this TCP connection. "The remote IPv6 address for this TCP connection.
This object is obsoleted by TCP-MIB::tcpConnectionRemPort." This object is obsoleted by TCP-MIB::tcpConnectionRemAddress."
::= { ipv6TcpConnEntry 4 } ::= { ipv6TcpConnEntry 3 }
ipv6TcpConnIfIndex OBJECT-TYPE ipv6TcpConnRemPort OBJECT-TYPE
SYNTAX Ipv6IfIndexOrZero SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"An index object used to disambiguate conceptual rows in "The remote port number for this TCP connection.
the table, since the connection 4-tuple may not be unique.
If the connection's remote address (ipv6TcpConnRemAddress) This object is obsoleted by TCP-MIB::tcpConnectionRemPort."
is a link-local address and the connection's local address ::= { ipv6TcpConnEntry 4 }
(ipv6TcpConnLocalAddress) is not a link-local address, this
object identifies a local interface on the same link as
the connection's remote link-local address.
Otherwise, this object identifies the local interface that ipv6TcpConnIfIndex OBJECT-TYPE
is associated with the ipv6TcpConnLocalAddress for this SYNTAX Ipv6IfIndexOrZero
TCP connection. If such a local interface cannot be determined, MAX-ACCESS not-accessible
this object should take on the value 0. (A possible example STATUS obsolete
of this would be if the value of ipv6TcpConnLocalAddress is ::0.) DESCRIPTION
"An index object used to disambiguate conceptual rows in
the table, since the connection 4-tuple may not be unique.
The interface identified by a particular non-0 value of this If the connection's remote address (ipv6TcpConnRemAddress)
index is the same interface as identified by the same value is a link-local address and the connection's local address
of ipv6IfIndex. (ipv6TcpConnLocalAddress) is not a link-local address, this
object identifies a local interface on the same link as
the connection's remote link-local address.
The value of this object must remain constant during the life Otherwise, this object identifies the local interface that
of the TCP connection. is associated with the ipv6TcpConnLocalAddress for this
TCP connection. If such a local interface cannot be
determined, this object should take on the value 0.
(A possible example of this would be if the value of
ipv6TcpConnLocalAddress is ::0.)
This object is obsoleted by the zone identifier in The interface identified by a particular non-0 value of this
an InetAddressIPv6z address in either index is the same interface as identified by the same value
TCP-MIB::tcpConnectionLocalAddress or of ipv6IfIndex.
TCP-MIB::tcpConnectionRemAddress."
::= { ipv6TcpConnEntry 5 }
ipv6TcpConnState OBJECT-TYPE The value of this object must remain constant during the life
SYNTAX INTEGER { of the TCP connection.
closed(1),
listen(2),
synSent(3),
synReceived(4),
established(5),
finWait1(6),
finWait2(7),
closeWait(8),
lastAck(9),
closing(10),
timeWait(11),
deleteTCB(12) }
MAX-ACCESS read-write
STATUS obsolete
DESCRIPTION
"The state of this TCP connection.
The only value which may be set by a management station is This object is obsoleted by the zone identifier in
deleteTCB(12). Accordingly, it is appropriate for an agent an InetAddressIPv6z address in either
to return an error response (`badValue' for SNMPv1, 'wrongValue' TCP-MIB::tcpConnectionLocalAddress or
for SNMPv2) if a management station attempts to set this TCP-MIB::tcpConnectionRemAddress."
object to any other value. ::= { ipv6TcpConnEntry 5 }
If a management station sets this object to the value ipv6TcpConnState OBJECT-TYPE
deleteTCB(12), then this has the effect of deleting the TCB SYNTAX INTEGER {
(as defined in RFC 793) of the corresponding connection on closed(1),
the managed node, resulting in immediate termination of the listen(2),
connection. synSent(3),
synReceived(4),
established(5),
finWait1(6),
finWait2(7),
closeWait(8),
lastAck(9),
closing(10),
timeWait(11),
deleteTCB(12) }
MAX-ACCESS read-write
STATUS obsolete
DESCRIPTION
"The state of this TCP connection.
As an implementation-specific option, a RST segment may be The only value which may be set by a management station is
sent from the managed node to the other TCP endpoint (note deleteTCB(12). Accordingly, it is appropriate for an agent
however that RST segments are not sent reliably). to return an error response ('badValue' for SNMPv1,
'wrongValue' for SNMPv2) if a management station attempts
to set this object to any other value.
This object is obsoleted by TCP-MIB::tcpConnectionState." If a management station sets this object to the value
::= { ipv6TcpConnEntry 6 } deleteTCB(12), then this has the effect of deleting the TCB
(as defined in RFC 793) of the corresponding connection on
the managed node, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note
however that RST segments are not sent reliably).
ipv6TcpConformance OBJECT IDENTIFIER ::= { ipv6TcpMIB 2 } This object is obsoleted by TCP-MIB::tcpConnectionState."
::= { ipv6TcpConnEntry 6 }
ipv6TcpCompliances OBJECT IDENTIFIER ::= { ipv6TcpConformance 1 } --
ipv6TcpGroups OBJECT IDENTIFIER ::= { ipv6TcpConformance 2 } -- conformance information
--
ipv6TcpConformance OBJECT IDENTIFIER ::= { ipv6TcpMIB 2 }
ipv6TcpCompliance MODULE-COMPLIANCE ipv6TcpCompliances OBJECT IDENTIFIER ::= { ipv6TcpConformance 1 }
STATUS obsolete ipv6TcpGroups OBJECT IDENTIFIER ::= { ipv6TcpConformance 2 }
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement TCP over IPv6.
This compliance statement is obsoleted by -- compliance statements
TCP-MIB::tcpMIBCompliance2."
MODULE -- this module
MANDATORY-GROUPS { ipv6TcpGroup }
::= { ipv6TcpCompliances 1 }
ipv6TcpGroup OBJECT-GROUP ipv6TcpCompliance MODULE-COMPLIANCE
OBJECTS { -- these are defined in this module STATUS obsolete
-- ipv6TcpConnLocalAddress (not-accessible) DESCRIPTION
-- ipv6TcpConnLocalPort (not-accessible) "The compliance statement for SNMPv2 entities which
-- ipv6TcpConnRemAddress (not-accessible) implement TCP over IPv6.
-- ipv6TcpConnRemPort (not-accessible)
-- ipv6TcpConnIfIndex (not-accessible)
ipv6TcpConnState }
STATUS obsolete
DESCRIPTION
"The group of objects providing management of
TCP over IPv6.
This group is obsoleted by several groups in TCP-MIB." This compliance statement is obsoleted by
::= { ipv6TcpGroups 1 } TCP-MIB::tcpMIBCompliance2."
MODULE -- this module
MANDATORY-GROUPS { ipv6TcpGroup }
::= { ipv6TcpCompliances 1 }
END ipv6TcpGroup OBJECT-GROUP
OBJECTS { -- these are defined in this module
-- ipv6TcpConnLocalAddress (not-accessible)
-- ipv6TcpConnLocalPort (not-accessible)
-- ipv6TcpConnRemAddress (not-accessible)
-- ipv6TcpConnRemPort (not-accessible)
-- ipv6TcpConnIfIndex (not-accessible)
ipv6TcpConnState }
STATUS obsolete
DESCRIPTION
"The group of objects providing management of
TCP over IPv6.
This group is obsoleted by several groups in TCP-MIB."
::= { ipv6TcpGroups 1 }
END
7. Reclassification 7. Reclassification
This document reclassifies [RFC2452], [RFC2454], [RFC2465], and This document reclassifies [RFC2452], [RFC2454], [RFC2465], and
[RFC2466] to Historic. [RFC2466] to Historic.
8. Security Considerations 8. Security Considerations
This document contains only obsolete objects, which [RFC2578] says This document contains only obsolete objects, which [RFC2578] says
"should not be implemented and/or can be removed if previously "should not be implemented and/or can be removed if previously
implemented". Since the contents of this document should not be implemented". Since the contents of this document should not be
implemented, it has no security implications. If there were any implemented, it has no security implications. If there were any
security implications based on these objects in an implementation, security implications based on these objects in an implementation,
removing these objects as [RFC2578] suggests would improve the removing these objects as [RFC2578] suggests would improve the
security of that implementation. security of that implementation.
9. IANA Considerations 9. IANA Considerations
In smi-numbers [1], the entries for RFC2452 and RFC2454, in the "SMI IANA has updated the SMI Numbers registry at
Experimental Codes" section, have an annotation "(Historic)" or <http://www.iana.org/assignments/smi-numbers/> as described below.
"(Historical)".
IANA is asked to make the following changes to the "SMI Network IANA has updated the "SMI Network Management MGMT Codes Internet-
Management MGMT Codes Internet-standard MIB" section: standard MIB" section as follows:
o Remove RFC1213 from the references for mib-2.5 "icmp". o Removed RFC 1213 as a reference for mib-2.5 ("icmp").
o Update the reference for mib-2.6 "tcp" to point to RFC4022. o Updated the reference for mib-2.6 ("tcp") to point to RFC 4022.
o Remove RFC1213 from the references for mib-2.7 "udp". o Removed RFC 1213 as a reference for mib-2.7 ("udp").
o Remove RFC2012 from the references for mib-2.49 "tcpMIB". o Removed RFC 2012 as a reference for mib-2.49 ("tcpMIB").
o Add the "(Historic)" annotation for the entries for mib-2.55 o Added the "(Historic)" annotation for the entries for mib-2.55
"ipv6MIB" and for mib-2.56 "ipv6IcmpMIB", and update the reference ("ipv6MIB") and mib-2.56 ("ipv6IcmpMIB") and updated the reference
to point to this document. of each to point to this document.
IANA is asked to make the following changes to the "SMI Experimental IANA has updated the "SMI Experimental Codes" section as follows:
Codes" section:
o Add the "(Historic)" annotation for experimental.74 "IPV6 MIB" o Added the "(Historic)" annotation for experimental.74 ("IPv6
MIB").
o Change the "(Historical)" annotation for experimental.87 o Changed the "(Historical)" annotation for experimental.87
"ipv6UdpMIB" to "(Historic)" ("ipv6UdpMIB") to "(Historic)".
o Update the reference for experimental.86 "ipv6TcpMIB" and o Updated the reference for experimental.86 ("ipv6TcpMIB") and
experimental.87 "ipv6UdpMIB" to point to this document. experimental.87 ("ipv6UdpMIB") to point to this document.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ Version 2 (SMIv2)", STD 58, RFC 2578,
RFC2578, April 1999, DOI 10.17487/RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>. <http://www.rfc-editor.org/info/rfc2578>.
10.2. Informative References 10.2. Informative References
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, DOI 10.17487/RFC1213, March 1991,
<http://www.rfc-editor.org/info/rfc1213>.
[RFC1573] McCloghrie, K. and F. Kastenholz, "Evolution of the
Interfaces Group of MIB-II", RFC 1573,
DOI 10.17487/RFC1573, January 1994,
<http://www.rfc-editor.org/info/rfc1573>.
[RFC2452] Daniele, M., "IP Version 6 Management Information Base for [RFC2452] Daniele, M., "IP Version 6 Management Information Base for
the Transmission Control Protocol", RFC 2452, DOI the Transmission Control Protocol", RFC 2452,
10.17487/RFC2452, December 1998, DOI 10.17487/RFC2452, December 1998,
<http://www.rfc-editor.org/info/rfc2452>. <http://www.rfc-editor.org/info/rfc2452>.
[RFC2454] Daniele, M., "IP Version 6 Management Information Base for [RFC2454] Daniele, M., "IP Version 6 Management Information Base for
the User Datagram Protocol", RFC 2454, DOI 10.17487/ the User Datagram Protocol", RFC 2454,
RFC2454, December 1998, DOI 10.17487/RFC2454, December 1998,
<http://www.rfc-editor.org/info/rfc2454>. <http://www.rfc-editor.org/info/rfc2454>.
[RFC2461] Narten, T., Nordmark, E., and W. Simpson, "Neighbor
Discovery for IP Version 6 (IPv6)", RFC 2461,
DOI 10.17487/RFC2461, December 1998,
<http://www.rfc-editor.org/info/rfc2461>.
[RFC2465] Haskin, D. and S. Onishi, "Management Information Base for [RFC2465] Haskin, D. and S. Onishi, "Management Information Base for
IP Version 6: Textual Conventions and General Group", RFC IP Version 6: Textual Conventions and General Group",
2465, DOI 10.17487/RFC2465, December 1998, RFC 2465, DOI 10.17487/RFC2465, December 1998,
<http://www.rfc-editor.org/info/rfc2465>. <http://www.rfc-editor.org/info/rfc2465>.
[RFC2466] Haskin, D. and S. Onishi, "Management Information Base for [RFC2466] Haskin, D. and S. Onishi, "Management Information Base for
IP Version 6: ICMPv6 Group", RFC 2466, DOI 10.17487/ IP Version 6: ICMPv6 Group", RFC 2466,
RFC2466, December 1998, DOI 10.17487/RFC2466, December 1998,
<http://www.rfc-editor.org/info/rfc2466>. <http://www.rfc-editor.org/info/rfc2466>.
[RFC4022] Raghunarayan, R., Ed., "Management Information Base for [RFC4022] Raghunarayan, R., Ed., "Management Information Base for
the Transmission Control Protocol (TCP)", RFC 4022, DOI the Transmission Control Protocol (TCP)", RFC 4022,
10.17487/RFC4022, March 2005, DOI 10.17487/RFC4022, March 2005,
<http://www.rfc-editor.org/info/rfc4022>. <http://www.rfc-editor.org/info/rfc4022>.
[RFC4113] Fenner, B. and J. Flick, "Management Information Base for [RFC4113] Fenner, B. and J. Flick, "Management Information Base for
the User Datagram Protocol (UDP)", RFC 4113, DOI 10.17487/ the User Datagram Protocol (UDP)", RFC 4113,
RFC4113, June 2005, DOI 10.17487/RFC4113, June 2005,
<http://www.rfc-editor.org/info/rfc4113>. <http://www.rfc-editor.org/info/rfc4113>.
[RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292, DOI [RFC4292] Haberman, B., "IP Forwarding Table MIB", RFC 4292,
10.17487/RFC4292, April 2006, DOI 10.17487/RFC4292, April 2006,
<http://www.rfc-editor.org/info/rfc4292>. <http://www.rfc-editor.org/info/rfc4292>.
[RFC4293] Routhier, S., Ed., "Management Information Base for the [RFC4293] Routhier, S., Ed., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293, Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293,
April 2006, <http://www.rfc-editor.org/info/rfc4293>. April 2006, <http://www.rfc-editor.org/info/rfc4293>.
10.3. URIs
[1] http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml
Appendix A. Change history
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.
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.3. 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.4. 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.5. 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 Author's Address
Bill Fenner Bill Fenner
Arista Networks, Inc. Arista Networks, Inc.
5453 Great America Parkway 5453 Great America Parkway
Santa Clara 95054 Santa Clara, CA 95054
USA United States of America
Phone: +1-408-547-5572 Phone: +1-408-547-5572
Email: fenner@fenron.com Email: fenner@fenron.com
 End of changes. 147 change blocks. 
472 lines changed or deleted 483 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/