draft-ietf-v6ops-ipv4survey-ops-02.txt   draft-ietf-v6ops-ipv4survey-ops-03.txt 
Network Working Group Philip J. Nesser II Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-ops-02.txt Nesser & Nesser Consulting draft-ietf-v6ops-ipv4survey-ops-03.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom Internet Draft Andreas Bergstrom
Ostfold University College Ostfold University College
August 2003 September 2003
Expires January 2004 Expires February 2004
Survey of IPv4 Addresses in Currently Deployed Survey of IPv4 Addresses in Currently Deployed
IETF Operations & Management Area Standards IETF Operations & Management Area Standards
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 67 skipping to change at line 67
8. Security Consideration 8. Security Consideration
9. Acknowledgements 9. Acknowledgements
10. References 10. References
11. Authors Address 11. Authors Address
12. Intellectual Property Statement 12. Intellectual Property Statement
13. Full Copyright Statement 13. Full Copyright Statement
1.0 Introduction 1.0 Introduction
This document is part of a document set aiming to document all usage of This document is part of a document set aiming to document all usage of
IPv4 addresses in IETF stanadards. In an effort to have the information IPv4 addresses in IETF standards. In an effort to have the information
in a manageable form, it has been broken into 7 documents conforming in a manageable form, it has been broken into 7 documents conforming
to the current IETF areas (Application, Internet, Manangement & to the current IETF areas (Application, Internet, Manangement &
Operations, Routing, Security, Sub-IP and Transport). Operations, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the intro[1] draft. For a full introduction, please see the intro[1] draft.
2.0 Document Organization 2.0 Document Organization
The document is organized as described below: The document is organized as described below:
Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft, Sections 3, 4, 5, and 6 each describe the raw analysis of Full, Draft,
and Proposed Standards, and Experimental RFCs. Each RFC is discussed in and Proposed Standards, and Experimental RFCs. Each RFC is discussed in
its turn starting with RFC 1 and ending with RFC 3247. The comments for its turn starting with RFC 1 and ending with RFC 3247. The comments for
each RFC is "raw" in nature. That is, each RFC is discussed in a each RFC are "raw" in nature. That is, each RFC is discussed in a
vacuum and problems or issues discussed do not "look ahead" to see if vacuum and problems or issues discussed do not "look ahead" to see if
the problems have already been fixed. the problems have already been fixed.
Section 7 is an analysis of the data presented in Sections 3, 4, 5, and Section 7 is an analysis of the data presented in Sections 3, 4, 5, and
6. It is here that all of the results are considered as a whole and the 6. It is here that all of the results are considered as a whole and the
problems that have been resolved in later RFCs are correlated. problems that have been resolved in later RFCs are correlated.
3.0 Full Standards 3.0 Full Standards
Full Internet Standards (most commonly simply referred to as Full Internet Standards (most commonly simply referred to as
"Standards") are fully mature protocol specification that are widely "Standards") are fully mature protocol specification that are widely
implemented and used throughout the Internet. implemented and used throughout the Internet.
3.1 RFC 1157 Simple Network Management Protocol 3.1 RFC 1155 Structure of Management Information
Beginning in Section 3.2.6.3.2 atTable Object Type Names thru the rest
of Section 3 there are numerous references to the use of IPv4 addresses
as part of OIDs.
Section 4. Protocol Specification specifies the format of an SNMP
packet which uses the overall format of:
RFC1157-SNMP DEFINITIONS ::= BEGIN
IMPORTS
ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks
FROM RFC1155-SMI;
Section 4.1.3.1. Example of Table Traversal has many uses of IPv4
addresses in its example of table transversal.
Section 5. Definitions reiterates the use of IPv4 addresses.
RFC1157-SNMP DEFINITIONS ::= BEGIN
IMPORTS
ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks
FROM RFC1155-SMI;
3.2 RFC 1155 Structure of Management Information
Section 3.2.3.2. IpAddress defines the following: Section 3.2.3.2. IpAddress defines the following:
This application-wide type represents a 32-bit internet address. It This application-wide type represents a 32-bit internet address. It
is represented as an OCTET STRING of length 4, in network byte-order. is represented as an OCTET STRING of length 4, in network byte-order.
There are several instances of the use of this definition in the rest of There are several instances of the use of this definition in the rest of
the document. the document.
3.3 RFC 1213 Management Information Base 3.2 RFC 1212 Concise MIB definitions
There are far too many instances of IPv4 addresses is this document In section 4.1.6 IpAddress is defined as:
to enumerate here. Clearly the entire IP OID sub tree is rife with
IPv4 dependencies. A new sub tree needs to be defined to deal with
IPv6 addresses leaving the current sub tree intact for IPv4 address
information.
3.4 RFC 1643 Definitions of Managed Objects for the Ethernet-like (6) IpAddress-valued: 4 sub-identifiers, in the familiar
Interface Types a.b.c.d notation.
There are no IPv4 dependencies in this specification. 3.1 RFC 1213 Management Information Base
3.5 RFC 2578 Structure of Management Information Version 2 (SMIv2) There are far too many instances of IPv4 addresses is this document
to enumerate here. The particular object groups that are affected
are the IP group, the ICMP group, the TCP group, the UDP group,
and the EGP group.
Section 7.1.5. IpAddress defines: 3.2 RFC 2578 Structure of Management Information Version 2 (SMIv2)
Section 7.1.5 defines the IpAddress data type:
The IpAddress type represents a 32-bit internet address. It is The IpAddress type represents a 32-bit internet address. It is
represented as an OCTET STRING of length 4, in network byte-order. represented as an OCTET STRING of length 4, in network byte-order.
Note that the IpAddress type is a tagged type for historical reasons. Note that the IpAddress type is a tagged type for historical reasons.
Network addresses should be represented using an invocation of the Network addresses should be represented using an invocation of the
TEXTUAL-CONVENTION macro. TEXTUAL-CONVENTION macro.
Note the deprecated status of this type; see RFC 3291 for details on Note the deprecated status of this type; see RFC 3291 for details on
TEXTUAL-CONVENTION macro. the replacement TEXTUAL-CONVENTION definitions.
3.6 RFC 2579 Textual Conventions for SMIv2 3.3 RFC 2579 Textual Conventions for SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.7 RFC 2819 Remote Network Monitoring Management Information Base 3.4 RFC 2580 Conformance Statements for SMIv2
(RMON-MIB)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.8 RFC 3416 Protocol Operations for Version 2 of the Simple Network 3.5 RFC 2819 Remote Network Monitoring Management Information Base
Management Protocol (SNMPv2) (OPS-MIB)
There are no IPv4 dependencies in this specification.
3.6 RFC 3411 An Architecture for Describing SNMP Management Frameworks
There are no IPv4 dependencies in this specification.
3.7 RFC 3412 Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP)
There are no IPv4 dependencies in this specification.
3.8 RFC 3413 SNMP Applications
There are no IPv4 dependencies in this specification.
3.9 RFC 3414 User-based Security Model (USM) for version 3 of the
Simple Network Management Protocol (SNMPv3)
There are no IPv4 dependencies in this specification.
3.10 RFC 3415 View-based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)
There are no IPv4 dependencies in this specification.
3.11 RFC 3416 Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMP)
Section 4.2.2.1. Example of Table Traversal and Section 4.2.3.1. Section 4.2.2.1. Example of Table Traversal and Section 4.2.3.1.
Another Example of Table Traversal both use OID's from MIB2 whose Another Example of Table Traversal both use objects from MIB2 whose
data contains IPv4 addresses. Other than their use in these example data contains IPv4 addresses. Other than their use in these example
sections there are no IPv4 dependencies in this specification. sections there are no IPv4 dependencies in this specification.
3.9 RFC 3417 Transport Mappings for Version 2 of the Simple Network 3.12 RFC 3417 Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2) (TRANS-MIB) Management Protocol (SNMP)
Section 2 Definitions contains the following OID definition: Section 2 Definitions contains the following definition:
SnmpUDPAddress ::= TEXTUAL-CONVENTION SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d" DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a UDP address: "Represents a UDP address:
octets contents encoding octets contents encoding
1-4 IP-address network-byte order 1-4 IP-address network-byte order
5-6 UDP-port network-byte order 5-6 UDP-port network-byte order
" "
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
Section 8.1. Usage Example also contains examples which use IPv4 Section 8.1, "Usage Example," also contains examples which uses IPv4
address, but it has no significance in the operation of the address, but it has no significance in the operation of the
specification. specification.
3.10 RFC 3418 Management Information Base for Version 2 of the Simple 3.13 RFC 3418 Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2) (SNMPv2-MIB) Network Management Protocol (SNMP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.0 Draft Standards 4.0 Draft Standards
Draft Standards represent the penultimate standard level in the IETF. Draft Standards represent the penultimate standard level in the IETF.
A protocol can only achieve draft standard when there are multiple, A protocol can only achieve draft standard when there are multiple,
independent, interoperable implementations. Draft Standards are usually independent, interoperable implementations. Draft Standards are usually
quite mature and widely used. quite mature and widely used.
4.01 RFC 1493 Definitions of Managed Objects for Bridges (BRIDGE-MIB) 4.01 RFC 1493 Definitions of Managed Objects for Bridges
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.02 RFC 1559 DECnet Phase IV MIB Extensions (DECNET-MIB) 4.02 RFC 1559 DECnet Phase IV MIB Extensions
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.03 RFC 1657 Definitions of Managed Objects for the Fourth 4.03 RFC 1657 Definitions of Managed Objects for the Fourth
Version of the Border Gateway Protocol (BGP-4) using SMIv2 (BGP-4-MIB) Version of the Border Gateway Protocol (BGP-4) using SMIv2
The MIB defined in this RFC deals with objects in a BGP4 based routing The MIB defined in this RFC deals with objects in a BGP4 based routing
system and therefore contain many objects that are limited by the system and therefore contain many objects that are limited by the
IpAddress 32-bit value defined in MIB2. Clearly the values of this MIB IpAddress 32-bit value defined in MIB2. Clearly the values of this MIB
are limited to IPv4 addresses. No update is needed, although a new MIB are limited to IPv4 addresses. No update is needed, although a new MIB
should be defined for BGP++ to allow management of IPv6 addresses and should be defined for BGP++ to allow management of IPv6 addresses and
routes. routes.
4.04 RFC 1658 Definitions of Managed Objects for Character Stream 4.04 RFC 1658 Definitions of Managed Objects for Character Stream
Devices using SMIv2 Devices using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.05 RFC 1659 Definitions of Managed Objects for RS-232-like Hardware 4.05 RFC 1659 Definitions of Managed Objects for RS-232-like Hardware
Devices using SMIv2 Devices using SMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.06 RFC 1660 Definitions of Managed Objects for Parallel-printer-like 4.06 RFC 1660 Definitions of Managed Objects for Parallel-printer-like
Hardware Devices using SMIv2 Hardware Devices using SMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
4.07 RFC 1694 Definitions of Managed Objects for SMDS Interfaces using 4.07 RFC 1694 Definitions of Managed Objects for SMDS Interfaces using
SMIv2 (SIP-MIB) SMIv2
This MIB definition defines the following subtree: This MIB module definition defines the following subtree:
ipOverSMDS OBJECT IDENTIFIER ::= { smdsApplications 1 } ipOverSMDS OBJECT IDENTIFIER ::= { smdsApplications 1 }
-- Although the objects in this group are read-only, at the -- Although the objects in this group are read-only, at the
-- agent's discretion they may be made read-write so that the -- agent's discretion they may be made read-write so that the
-- management station, when appropriately authorized, may -- management station, when appropriately authorized, may
-- change the addressing information related to the -- change the addressing information related to the
-- configuration of a logical IP subnetwork implemented on -- configuration of a logical IP subnetwork implemented on
-- top of SMDS. -- top of SMDS.
skipping to change at line 335 skipping to change at line 336
ipOverSMDSARPReq OBJECT-TYPE ipOverSMDSARPReq OBJECT-TYPE
SYNTAX SMDSAddress SYNTAX SMDSAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The SMDS address (individual or group) to which "The SMDS address (individual or group) to which
ARP Requests are to be sent." ARP Requests are to be sent."
::= { ipOverSMDSEntry 5 } ::= { ipOverSMDSEntry 5 }
Although these OIDs are intended for IPv4 addresses, a similar MIB Although these object definitions are intended for IPv4 addresses, a
can be defined for IPv6 addressing. similar MIB can be defined for IPv6 addressing.
4.08 RFC 1724 RIP Version 2 MIB Extension (RIP2-MIB) 4.08 RFC 1724 RIP Version 2 MIB Extension
As might be expected, this RFC is filled with IPv4 dependencies since As might be expected, this RFC is filled with IPv4 dependencies since
it defines a MIB for an IPv4 only routing protocol. A new MIB for RIPng it defines a MIB module for an IPv4-only routing protocol. A new MIB
is required. for RIPng is required.
4.09 RFC 1748 IEEE 802.5 MIB using SMIv2 (802.5-MIB) 4.09 RFC 1748 IEEE 802.5 MIB using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.10 RFC 1850 OSPF Version 2 Management Information Base (OSPF-MIB) 4.10 RFC 1850 OSPF Version 2 Management Information Base
This MIB defines managed objects for OSPFv2 which is a protocol used This MIB defines managed objects for OSPFv2 which is a protocol used
to exchange IPv4 routing information. Since OSPFv2 is limited to IPv4 to exchange IPv4 routing information. Since OSPFv2 is limited to IPv4
addresses a new MIB is required to support a new version of OSPF that addresses a new MIB is required to support a new version of OSPF that
is IPv6 aware. is IPv6 aware.
4.11 RFC 2115 Management Information Base for Frame Relay DTEs 4.11 RFC 2115 Management Information Base for Frame Relay DTEs
Using SMIv2 (FRAME-MIB) Using SMIv2
This MIB has several examples of mapping IPv4 addresses to multiple
Frame Relay DLCI's and monitoring their connections. A new set of OID's
needs to be defined to allow this functionality for IPv6.
4.12 RFC 2571 An Architecture for Describing SNMP Management Frameworks
(ARCH-SNMP)
There are no IPv4 dependencies in this specification. This specification has several examples of how IPv4 addresses might be
mapped to Frame Relay DLCIs. Other than those examples there are no
IPv4 dependencies in this specification.
4.13 RFC 2572 Message Processing and Dispatching for the Simple Network 4.12 RFC 2790 Host Resources MIB
Management Protocol (SNMP) (MPD-SNMP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.14 RFC 2573 SNMP Applications (SNMP-APP) 4.13 RFC 2863 The Interfaces Group MIB
There are no IPv4 dependencies in this protocol.
4.15 RFC 2574 User-based Security Model (USM) for version 3 of the
Simple Network Management Protocol (SNMPv3) (USM-SNMPV3)
There are no IPv4 dependencies in this protocol.
4.16 RFC 2575 View-based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP) (VACM-SNMP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification. There is some
discussion in one object definition about an interface performing a
self test, but the object itself is IP version independent.
4.17 RFC 2790 Host Resources MIB 4.14 RFC 3592 Definitions of Managed Objects for the Synchronous Optical
Network/Synchronous Digital Hierarchy (SONET/SDH)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.18 RFC 2863 The Interfaces Group MIB (INTERGRMIB) 4.15 RFC 3593 Textual Conventions for MIB Modules Using Performance History
Based on 15 Minute Intervals.
There are no IPv4 dependencies in this specification. There is some There are no IPv4 dependencies in this specification.
discussion in one OID about an interface performing a self test, but it
is IP version independent.
5.0 Proposed Standards 5.0 Proposed Standards
Proposed Standards are introductory level documents. There are no Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases Proposed requirements for even a single implementation. In many cases Proposed
are never implemented or advanced in the IETF standards process. They are never implemented or advanced in the IETF standards process. They
therefore are often just proposed ideas that are presented to the therefore are often just proposed ideas that are presented to the
Internet community. Sometimes flaws are exposed or they are one of Internet community. Sometimes flaws are exposed or they are one of
many competing solutions to problems. In these later cases, no many competing solutions to problems. In these later cases, no
discussion is presented as it would not serve the purpose of this discussion is presented as it would not serve the purpose of this
discussion. discussion.
5.001 RFC 1239 Reassignment of experimental MIBs to standard MIBs 5.001 RFC 1239 Reassignment of experimental MIBs to standard MIBs
(STD-MIBs)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.002 RFC 1269 Definitions of Managed Objects for the Border Gateway 5.002 RFC 1269 Definitions of Managed Objects for the Border Gateway
Protocol: Version 3 (BGP-MIB) Protocol: Version 3
The use of BGP3 has been deprecated and is not discussed. The use of BGP3 has been deprecated and is not discussed.
5.003 RFC 1285 FDDI Management Information Base (FDDI-MIB) 5.003 RFC 1285 FDDI Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.004 RFC 1381 SNMP MIB Extension for X.25 LAPB (SNMP-LAPB) 5.004 RFC 1381 SNMP MIB Extension for X.25 LAPB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.005 RFC 1382 SNMP MIB Extension for the X.25 Packet Layer (SNMP-X.25) 5.005 RFC 1382 SNMP MIB Extension for the X.25 Packet Layer
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.006 RFC 1414 Identification MIB (IDENT-MIB) 5.006 RFC 1414 Identification MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.007 RFC 1418 SNMP over OSI (SNMP-OSI) 5.007 RFC 1418 SNMP over OSI
There are no IPv4 dependencies in this protocol.
5.008 RFC 1419 SNMP over AppleTalk (SNMP-AT)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.009 RFC 1420 SNMP over IPX (SNMP-IPX) 5.008 RFC 1419 SNMP over AppleTalk
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.010 RFC 1441 Introduction to version 2 of the Internet-standard 5.009 RFC 1420 SNMP over IPX
Network Management Framework (SNMPv2)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.011 RFC 1461 SNMP MIB extension for Multiprotocol Interconnect 5.010 RFC 1461 SNMP MIB extension for Multiprotocol Interconnect
over X.25 (X25-MIB) over X.25
The following OIDs are defined in Section 4 "Definitions": The following objects are defined in Section 4 "Definitions":
mioxPleLastFailedEnAddr OBJECT-TYPE mioxPleLastFailedEnAddr OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2..128)) SYNTAX OCTET STRING (SIZE(2..128))
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"The last Encapsulated address that failed "The last Encapsulated address that failed
to find a corresponding X.121 address and to find a corresponding X.121 address and
caused mioxPleEnAddrToX121LkupFlrs to be caused mioxPleEnAddrToX121LkupFlrs to be
incremented. The first octet of this object incremented. The first octet of this object
skipping to change at line 528 skipping to change at line 509
mioxPeerIndex has a value of underCreation. mioxPeerIndex has a value of underCreation.
Setting this object to a value of 256 Setting this object to a value of 256
deletes the entry. When deleting an entry, deletes the entry. When deleting an entry,
all other entries in the mioxPeerEncTable all other entries in the mioxPeerEncTable
with the same mioxPeerIndex and with an with the same mioxPeerIndex and with an
mioxPeerEncIndex higher then the deleted mioxPeerEncIndex higher then the deleted
entry, will all have their mioxPeerEncIndex entry, will all have their mioxPeerEncIndex
values decremented by one." values decremented by one."
::= { mioxPeerEncEntry 2 } ::= { mioxPeerEncEntry 2 }
Updated values of the first byte of these OID's can be defined to Updated values of the first byte of these objects can be defined to
support IPv6 addresses. support IPv6 addresses.
5.012 RFC 1471 The Definitions of Managed Objects for the Link 5.011 RFC 1471 The Definitions of Managed Objects for the Link
Control Protocol of the Point-to-Point Protocol (PPP/LCPMIB) Control Protocol of the Point-to-Point Protocol
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.013 RFC 1472 The Definitions of Managed Objects for the Security 5.012 RFC 1472 The Definitions of Managed Objects for the Security
Protocols of the Point-to-Point Protocol (PPP/SECMIB) Protocols of the Point-to-Point Protocol
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.014 RFC 1473 The Definitions of Managed Objects for the IP Network 5.013 RFC 1473 The Definitions of Managed Objects for the IP Network
Control Protocol of the Point-to-Point Protocol (PPP/IPMIB) Control Protocol of the Point-to-Point Protocol
Every OID in the MIB contain IPv4 addresses. A new MIB must be defined This MIB module is targeted specifically at IPv4 over PPP. A new
for OIDs for similar IPv6 addresses. MIB moduld would need to be defined to support IPv6 over PPP.
5.015 RFC 1474 The Definitions of Managed Objects for the Bridge 5.014 RFC 1474 The Definitions of Managed Objects for the Bridge
Network Control Protocol of the Point-to-Point Protocol Network Control Protocol of the Point-to-Point Protocol
(PPP/Bridge)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.016 RFC 1512 FDDI Management Information Base (FDDI-MIB) 5.015 RFC 1512 FDDI Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.017 RFC 1513 Token Ring Extensions to the Remote Network 5.016 RFC 1513 Token Ring Extensions to the Remote Network
Monitoring MIB Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.018 RFC 1515 Definitions of Managed Objects for IEEE 802.3 5.017 RFC 1515 Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) Medium Attachment Units (MAUs)
There are no IPv4 dependencies in this protocol.
5.019 RFC 1525 Definitions of Managed Objects for Source Routing
Bridges (SRB-MIB)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.020 RFC 1611 DNS Server MIB Extensions (DNS-S-MIB) Note that this document has been Obsoleted.
The following OID is defined:
DnsServZoneEntry ::=
SEQUENCE {
dnsServZoneName
DnsNameAsIndex,
dnsServZoneClass
DnsClass,
dnsServZoneLastReloadSuccess
DnsTime,
dnsServZoneLastReloadAttempt
DnsTime,
dnsServZoneLastSourceAttempt
IpAddress,
dnsServZoneStatus
RowStatus,
dnsServZoneSerial
Counter32,
dnsServZoneCurrent
TruthValue,
dnsServZoneLastSourceSuccess
IpAddress
}
There are two instances of IPv4 assumptions. New OIDs can be
defined for IPv6 addressing.
Similarly:
-- DNS Zone Source Table
dnsServZoneSrcTable OBJECT-TYPE
SYNTAX SEQUENCE OF DnsServZoneSrcEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is a list of IP addresses from which the
server will attempt to load zone information using DNS
zone transfer operations. A reload may occur due to SNMP
operations that create a row in dnsServZoneTable or a
SET to object dnsServZoneReload. This table is only
used when the zone is loaded via zone transfer."
::= { dnsServZone 2 }
dnsServZoneSrcEntry OBJECT-TYPE
SYNTAX DnsServZoneSrcEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the name server zone source table."
INDEX { dnsServZoneSrcName,
dnsServZoneSrcClass,
dnsServZoneSrcAddr }
::= { dnsServZoneSrcTable 1 }
DnsServZoneSrcEntry ::=
SEQUENCE {
dnsServZoneSrcName
DnsNameAsIndex,
dnsServZoneSrcClass
DnsClass,
dnsServZoneSrcAddr
IpAddress,
dnsServZoneSrcStatus
RowStatus
}
dnsServZoneSrcName OBJECT-TYPE
SYNTAX DnsNameAsIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"DNS name of the zone to which this entry applies."
::= { dnsServZoneSrcEntry 1 }
dnsServZoneSrcClass OBJECT-TYPE
SYNTAX DnsClass
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"DNS class of zone to which this entry applies."
::= { dnsServZoneSrcEntry 2 }
dnsServZoneSrcAddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"IP address of name server host from which this zone
might be obtainable."
::= { dnsServZoneSrcEntry 3 }
5.021 RFC 1612 DNS Resolver MIB Extensions (DNS-R-MIB)
As in the previous section the following IPv4 dependent OIDs are
defined:
DnsResConfigSbeltEntry ::=
SEQUENCE {
dnsResConfigSbeltAddr
IpAddress,
dnsResConfigSbeltName
DnsName,
dnsResConfigSbeltRecursion
INTEGER,
dnsResConfigSbeltPref
INTEGER,
dnsResConfigSbeltSubTree
DnsNameAsIndex,
dnsResConfigSbeltClass
DnsClass,
dnsResConfigSbeltStatus
RowStatus
}
dnsResConfigSbeltAddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The IP address of the Sbelt name server identified by
this row of the table."
::= { dnsResConfigSbeltEntry 1 }
and
DnsResLameDelegationEntry ::=
SEQUENCE {
dnsResLameDelegationSource
IpAddress,
dnsResLameDelegationName
DnsNameAsIndex,
dnsResLameDelegationClass
DnsClass,
dnsResLameDelegationCounts
Counter32,
dnsResLameDelegationStatus
RowStatus
}
dnsResLameDelegationSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Source of lame delegation."
::= { dnsResLameDelegationEntry 1 }
and
DnsResCacheRREntry ::=
SEQUENCE {
dnsResCacheRRName
DnsNameAsIndex,
dnsResCacheRRClass
DnsClass,
dnsResCacheRRType
DnsType,
dnsResCacheRRTTL
DnsTime,
dnsResCacheRRElapsedTTL
DnsTime,
dnsResCacheRRSource
IpAddress,
dnsResCacheRRData
OCTET STRING,
dnsResCacheRRStatus
RowStatus,
dnsResCacheRRIndex
Integer32,
dnsResCacheRRPrettyName
DnsName
}
dnsResCacheRRSource OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Host from which RR was received, 0.0.0.0 if unknown."
::= { dnsResCacheRREntry 6 }
and
DnsResNCacheErrEntry ::= 5.018 RFC 1525 Definitions of Managed Objects for Source Routing
SEQUENCE { Bridges
dnsResNCacheErrQName
DnsNameAsIndex,
dnsResNCacheErrQClass
DnsQClass,
dnsResNCacheErrQType
DnsQType,
dnsResNCacheErrTTL
DnsTime,
dnsResNCacheErrElapsedTTL
DnsTime,
dnsResNCacheErrSource
IpAddress,
dnsResNCacheErrCode
INTEGER,
dnsResNCacheErrStatus
RowStatus,
dnsResNCacheErrIndex
Integer32,
dnsResNCacheErrPrettyName
DnsName
}
dnsResNCacheErrSource OBJECT-TYPE There are no IPv4 dependencies in this specification.
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Host which sent the authoritative error, 0.0.0.0 if
unknown."
::= { dnsResNCacheErrEntry 6 }
5.022 RFC 1628 UPS Management Information Base (UPS-MIB) 5.019 RFC 1628 UPS Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.023 RFC 1666 Definitions of Managed Objects for SNA NAUs 5.020 RFC 1666 Definitions of Managed Objects for SNA NAUs
using SMIv2 SNANAU-MIB using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.024 RFC 1696 Modem Management Information Base (MIB) using SMIv2 5.021 RFC 1696 Modem Management Information Base (MIB) using SMIv2
MODEM-MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.025 RFC 1697 Relational Database Management System (RDBMS) 5.022 RFC 1697 Relational Database Management System (RDBMS)
Management Information Base (MIB) using SMIv2 RDBMS-MIB Management Information Base (MIB) using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.026 RFC 1742 AppleTalk Management Information Base II (AT-MIB) 5.023 RFC 1742 AppleTalk Management Information Base II
The following OIDs are defined: The following OIDs are defined:
KipEntry ::= SEQUENCE { KipEntry ::= SEQUENCE {
kipNetStart ATNetworkNumber, kipNetStart ATNetworkNumber,
kipNetEnd ATNetworkNumber, kipNetEnd ATNetworkNumber,
kipNextHop IpAddress, kipNextHop IpAddress,
kipHopCount INTEGER, kipHopCount INTEGER,
kipBCastAddr IpAddress, kipBCastAddr IpAddress,
kipCore INTEGER, kipCore INTEGER,
skipping to change at line 856 skipping to change at line 618
SYNTAX IpAddress SYNTAX IpAddress
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"The IP address from which the routing entry was "The IP address from which the routing entry was
learned via the AA protocol. If this entry was not learned via the AA protocol. If this entry was not
created via the AA protocol, it should contain IP created via the AA protocol, it should contain IP
address 0.0.0.0." address 0.0.0.0."
::= { kipEntry 10 } ::= { kipEntry 10 }
5.027 RFC 1747 Definitions of Managed Objects for SNA Data Link 5.024 RFC 1747 Definitions of Managed Objects for SNA Data Link
Control (SDLC) using SMIv2 SDLCSMIv2 Control (SDLC) using SMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.028 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2 5.025 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2
802.5-SSR
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.029 RFC 1759 Printer MIB (Print-MIB) 5.026 RFC 1759 Printer MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.030 RFC 2006 The Definitions of Managed Objects for IP Mobility Note that this document is Obsoleted.
Support using SMIv2 (MOBILEIPMI)
5.027 RFC 2006 The Definitions of Managed Objects for IP Mobility
Support using SMIv2
This document defines a MIB for the Mobile IPv4 documents described This document defines a MIB for the Mobile IPv4 documents described
immediately above. Without enumeration, let it be stated that a new immediately above. Without enumeration, let it be stated that a new
MIB for IPv6 Mobility is required. MIB for IPv6 Mobility is required.
5.031 RFC 2011 SNMPv2 Management Information Base for the Internet 5.028 RFC 2011 SNMPv2 Management Information Base for the Internet
Protocol using SMIv2 (MIB-IP) Protocol using SMIv2
Approximately 1/3 of the OIDs defined in this document are clearly Approximately 1/3 of the objects defined in this document are
IPv4 dependent. A new MIB for IPv6 OIDs is required. IPv4-dependent. New objects need to be defined to support IPv6.
5.032 RFC 2012 SNMPv2 Management Information Base for the 5.029 RFC 2012 SNMPv2 Management Information Base for the
Transmission Control Protocol using SMIv2 (MIB-TCP) Transmission Control Protocol using SMIv2
A number of OIDs in this MIB assumes IPv4 addresses, as is noted in A number of object definitions in this MIB assumes IPv4 addresses, as
the note reproduced below: is noted in the note reproduced below:
IESG Note: IESG Note:
The IP, UDP, and TCP MIB modules currently support only IPv4. These The IP, UDP, and TCP MIB modules currently support only IPv4. These
three modules use the IpAddress type defined as an OCTET STRING of three modules use the IpAddress type defined as an OCTET STRING of
length 4 to represent the IPv4 32-bit internet addresses. (See RFC length 4 to represent the IPv4 32-bit internet addresses. (See RFC
1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6
internet addresses. internet addresses.
5.033 RFC 2013 SNMPv2 Management Information Base for the User 5.030 RFC 2013 SNMPv2 Management Information Base for the User
Datagram Protocol using SMIv2 (MIB-UDP) Datagram Protocol using SMIv2
A number of OIDs in this MIB assumes IPv4 addresses, as is noted in A number of OIDs in this MIB assumes IPv4 addresses, as is noted in
the note reproduced below: the note reproduced below:
IESG Note: IESG Note:
The IP, UDP, and TCP MIB modules currently support only IPv4. These The IP, UDP, and TCP MIB modules currently support only IPv4. These
three modules use the IpAddress type defined as an OCTET STRING of three modules use the IpAddress type defined as an OCTET STRING of
length 4 to represent the IPv4 32-bit internet addresses. (See RFC length 4 to represent the IPv4 32-bit internet addresses. (See RFC
1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6
internet addresses. internet addresses.
5.034 RFC 2020 IEEE 802.12 Interface MIB (802.12-MIB) 5.031 RFC 2020 EEE 802.12 Interface MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.035 RFC 2021 Remote Network Monitoring Management Information Base 5.032 RFC 2021 Remote Network Monitoring Management Information Base
Version 2 using SMIv2 (RMON-MIB) Version 2 using SMIv2
The following OIDs are defined: The following objects are defined:
addressMapNetworkAddress OBJECT-TYPE addressMapNetworkAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network address for this relation. "The network address for this relation.
This is represented as an octet string with This is represented as an octet string with
specific semantics and length as identified specific semantics and length as identified
skipping to change at line 1137 skipping to change at line 900
-- --
-- octets contents encoding -- octets contents encoding
-- 1-4 network-number network-byte order -- 1-4 network-number network-byte order
-- 5-10 physical-address network-byte order -- 5-10 physical-address network-byte order
-- 11-12 socket-number network-byte order -- 11-12 socket-number network-byte order
This object may not be modified if the associated This object may not be modified if the associated
trapDestStatus object is equal to active(1)." trapDestStatus object is equal to active(1)."
::= { trapDestEntry 4 } ::= { trapDestEntry 4 }
All of the OIDs above (except trapDestProtocol) imply IPv4 addresses All of the object definitions above (except trapDestProtocol) mention
but since they use a SYNTAX of OCTET STRING, they should work fine only IPv4 addresses but since they use a SYNTAX of OCTET STRING, they
for IPv6 addresses. A new legitimate value of trapDestProtocol (i.e. should work fine for IPv6 addresses. A new legitimate value of
SYNTAX addition of ipv6(3) should make this specification IPv6 trapDestProtocol (i.e. SYNTAX addition of ipv6(3) should make this
functional. specification functional for IPv6.
5.036 RFC 2024 Definitions of Managed Objects for Data Link Switching 5.033 RFC 2024 Definitions of Managed Objects for Data Link Switching
using SMIv2 (DLSW-MIB) using SMIv2
The following OIDs are defined: The following textual conventions are defined:
TAddress ::= TEXTUAL-CONVENTION TAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a transport service address. "Denotes a transport service address.
For dlswTCPDomain, a TAddress is 4 octets long, For dlswTCPDomain, a TAddress is 4 octets long,
containing the IP-address in network-byte order." containing the IP-address in network-byte order."
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
-- DLSw over TCP -- DLSw over TCP
skipping to change at line 1171 skipping to change at line 934
-- 1-4 IP-address network-byte order -- 1-4 IP-address network-byte order
-- --
DlswTCPAddress ::= TEXTUAL-CONVENTION DlswTCPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d" DISPLAY-HINT "1d.1d.1d.1d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the IP address of a DLSw which uses "Represents the IP address of a DLSw which uses
TCP as a transport protocol." TCP as a transport protocol."
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
Additionally there are many OIDs that use a SYNTAX of TAddress within Additionally there are many object definitions that use a SYNTAX of
the document. Interestingly the SYNTAX for TAddress is an OCTET TAddress within the document. Interestingly the SYNTAX for TAddress
string of up to 256 characters. It could easily accommodate a similar is an OCTET string of up to 256 characters. It could easily
hybrid format for IPv6 addresses. accommodate a similar hybrid format for IPv6 addresses.
A new OID to enhance functionality for DlswTCPAddress can be added A new OID to enhance functionality for DlswTCPAddress could be added
to support IPv6 addresses. to support IPv6 addresses.
5.037 RFC 2051 Definitions of Managed Objects for APPC using SMIv2 5.034 RFC 2051 Definitions of Managed Objects for APPC using SMIv2
(SNANAU-APP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.038 RFC 2096 IP Forwarding Table MIB (TABLE-MIB) 5.035 RFC 2096 IP Forwarding Table MIB
This MIB defines many OIDs that are IPv4 dependent. It is expected The MIB module's main conceptual table ipCidrRouteTable uses IPv4
that another MIB for similar IPv6 addresses will be developed. addresses as index objects and is therefore incapable of
representing an IPv6 forwarding information base. A new
conceptual table needs to be defined to support IPv6 addresses.
5.039 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater 5.036 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater
Devices using SMIv2 802 (3-MIB) Devices using SMIv2 802
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.040 RFC 2127 ISDN Management Information Base using SMIv2 5.037 RFC 2127 ISDN Management Information Base using SMIv2
(ISDN-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.041 RFC 2128 Dial Control Management Information Base using 5.038 RFC 2128 Dial Control Management Information Base using
SMIv2 (DC-MIB) SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.042 RFC 2206 RSVP Management Information Base using SMIv2 5.039 RFC 2206 RSVP Management Information Base using SMIv2
(RSVP-MIB)
All OIDs in this MIB have options for both IPv4 and IPv6. There All of the relevant object definitions in this MIB have options for
are no IPv4 dependencies in this specification. both IPv4 and IPv6. There are no IPv4 dependencies in this
specification.
5.043 RFC 2213 Integrated Services Management Information 5.040 RFC 2213 Integrated Services Management Information
Base using SMIv2 Base using SMIv2
This MIB is IPv6 aware and therefore there are no IPv4 This MIB is IPv6 aware and therefore there are no IPv4
dependencies in this specification. dependencies in this specification.
5.044 RFC 2214 Integrated Services Management Information 5.041 RFC 2214 Integrated Services Management Information
Base Guaranteed Service Extensions using SMIv2 Base Guaranteed Service Extensions using SMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.045 RFC 2232 Definitions of Managed Objects for DLUR using 5.042 RFC 2232 Definitions of Managed Objects for DLUR using
SMIv2 (DLUR-MIB) SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.046 RFC 2238 Definitions of Managed Objects for HPR using 5.043 RFC 2238 Definitions of Managed Objects for HPR using
SMIv2 (HPR-MIB) SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.047 RFC 2266 Definitions of Managed Objects for IEEE 802.12 5.044 RFC 2266 Definitions of Managed Objects for IEEE 802.12
Repeater Devices Repeater Devices
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.048 RFC 2287 Definitions of System-Level Managed Objects for 5.045 RFC 2287 Definitions of System-Level Managed Objects for
Applications (SLM-APP) Applications
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.049 RFC 2320 Definitions of Managed Objects for Classical IP 5.046 RFC 2320 Definitions of Managed Objects for Classical IP
and ARP Over ATM Using SMIv2 (IPOA-MIB) (IPOA-MIB) and ARP Over ATM Using SMIv2 (IPOA-MIB)
This MIB is wholly dependent of IPv4. A new MIB for IPv6 is This MIB is wholly dependent of IPv4. A new MIB for IPv6 is
required to provide the same functionality required to provide the same functionality
5.050 RFC 2417 Definitions of Managed Objects for Multicast 5.047 RFC 2417 Definitions of Managed Objects for Multicast
over UNI 3.0/3.1 based ATM Networks over UNI 3.0/3.1 based ATM Networks
There are many OIDs defined in this MIB which are IPv4 only. A This MIB is wholly dependent of IPv4. A new MIB for IPv6 is
similar MIB for IPv6 OIDs should be created. required to provide the same functionality
5.051 RFC 2452 IP Version 6 Management Information Base for the 5.048 RFC 2452 IP Version 6 Management Information Base for the
Transmission Control Protocol Transmission Control Protocol
This RFC documents an IPv6 MIB and is not considered in this This RFC documents a soon to be obsoleted IPv6 MIB and is not
discussion. considered in this discussion.
5.052 RFC 2454 IP Version 6 Management Information Base for 5.049 RFC 2454 IP Version 6 Management Information Base for
the User Datagram Protocol the User Datagram Protocol
This RFC documents an IPv6 MIB and is not considered in this This RFC documents a soon to be obsoleted IPv6 MIB and is not
discussion. considered in this discussion.
5.053 RFC 2455 Definitions of Managed Objects for APPN 5.050 RFC 2455 Definitions of Managed Objects for APPN
(APPN-MIB)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.054 RFC 2456 Definitions of Managed Objects for APPN TRAPS 5.051 RFC 2456 Definitions of Managed Objects for APPN TRAPS
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.055 RFC 2457 Definitions of Managed Objects for Extended Border 5.052 RFC 2457 Definitions of Managed Objects for Extended Border
Node (EBN-MIB) Node
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.056 RFC 2465 Management Information Base for IP Version 6: 5.053 RFC 2465 Management Information Base for IP Version 6:
Textual Conventions and General Group Textual Conventions and General Group
This RFC documents an IPv6 MIB and is not considered in this This RFC documents a soon to be obsolted IPv6 MIB and is not
discussion. considered in this discussion.
5.057 RFC 2466 Management Information Base for IP Version 6:
ICMPv6 Group (ICMPv6-MIB)
This RFC documents an IPv6 MIB and is not considered in this
discussion.
5.058 RFC 2493 Textual Conventions for MIB Modules Using 5.054 RFC 2466 Management Information Base for IP Version 6:
Performance History Based on 15 Minute Intervals ICMPv6 Group
There are no IPv4 dependencies in this specification. This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion.
5.059 RFC 2494 Definitions of Managed Objects for the DS0 5.055 RFC 2494 Definitions of Managed Objects for the DS0
and DS0 Bundle Interface Type and DS0 Bundle Interface Type
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.060 RFC 2495 Definitions of Managed Objects for the DS1 E1 5.056 RFC 2495 Definitions of Managed Objects for the DS1, E1,
DS2 and E2 Interface Types DS2 and E2 Interface Types
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.061 RFC 2496 Definitions of Managed Object for the DS3/E3 5.057 RFC 2496 Definitions of Managed Object for the DS3/E3
Interface Type (DS3-E3-MIB) Interface Type
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.062 RFC 2512 Accounting Information for ATM Networks 5.058 RFC 2512 Accounting Information for ATM Networks
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.063 RFC 2513 Managed Objects for Controlling the Collection 5.059 RFC 2513 Managed Objects for Controlling the Collection
and Storage of Accounting Information for Connection- and Storage of Accounting Information for Connection-
Oriented Networks Oriented Networks
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.064 RFC 2514 Definitions of Textual Conventions and 5.060 RFC 2514 Definitions of Textual Conventions and
OBJECT-IDENTITIES for ATM Management (ATM-TC-OID) OBJECT-IDENTITIES for ATM Management
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.065 RFC 2515 Definitions of Managed Objects for ATM 5.061 RFC 2515 Definitions of Managed Objects for ATM
Management (ATM-MIBMAN) Management
This MIB defines the following OIDs: This MIB defines the following objects:
AtmInterfaceConfEntry ::= SEQUENCE { AtmInterfaceConfEntry ::= SEQUENCE {
atmInterfaceMaxVpcs INTEGER, atmInterfaceMaxVpcs INTEGER,
atmInterfaceMaxVccs INTEGER, atmInterfaceMaxVccs INTEGER,
atmInterfaceConfVpcs INTEGER, atmInterfaceConfVpcs INTEGER,
atmInterfaceConfVccs INTEGER, atmInterfaceConfVccs INTEGER,
atmInterfaceMaxActiveVpiBits INTEGER, atmInterfaceMaxActiveVpiBits INTEGER,
atmInterfaceMaxActiveVciBits INTEGER, atmInterfaceMaxActiveVciBits INTEGER,
atmInterfaceIlmiVpi AtmVpIdentifier, atmInterfaceIlmiVpi AtmVpIdentifier,
atmInterfaceIlmiVci AtmVcIdentifier, atmInterfaceIlmiVci AtmVcIdentifier,
skipping to change at line 1384 skipping to change at line 1141
atmInterfaceMyNeighborIfName, atmInterfaceMyNeighborIfName,
atmInterfaceCurrentMaxVpiBits, atmInterfaceCurrentMaxVpiBits,
atmInterfaceCurrentMaxVciBits, atmInterfaceCurrentMaxVciBits,
atmInterfaceSubscrAddress } atmInterfaceSubscrAddress }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration "A collection of objects providing configuration
information about an ATM interface." information about an ATM interface."
::= { atmMIBGroups 10 } ::= { atmMIBGroups 10 }
Clearly a subsequent MIB must define equivalent IPv6 OIDs. Clearly a subsequent revision of this MIB module should define
equivalent IPv6 objects.
5.066 RFC 2558 Definitions of Managed Objects for the SONET/SDH
Interface Type
There are no IPv4 dependencies in this protocol.
5.067 RFC 2561 Base Definitions of Managed Objects for TN3270E 5.062 RFC 2561 Base Definitions of Managed Objects for TN3270E
Using SMIv2 Using SMIv2
The document states: The document states:
The MIB defined by this memo supports use of both IPv4 and IPv6 The MIB defined by this memo supports use of both IPv4 and IPv6
addressing. addressing.
This specification is both IPv4 and IPv6 aware. This specification is both IPv4 and IPv6 aware.
5.068 RFC 2562 Definitions of Protocol and Managed Objects for 5.063 RFC 2562 Definitions of Protocol and Managed Objects for
TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB) TN3270E Response Time Collection Using SMIv2 (TN3270E-RT-MIB)
(TN2370E-RT)
Several OIDs rely on imports from RFC 2561 and therefore the This MIB module inherits IP version-independence by virtue of
protocol is both IPv4 and IPv6 aware. importing the appropriate definitions from RFC 2561.
5.069 RFC 2564 Application Management MIB (APP-MIB)
The following OID is defined:
ApplTAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a transport service address.
For snmpUDPDomain, an ApplTAddress is 6 octets long,
the initial 4 octets containing the IP-address in
network-byte order and the last 2 containing the UDP
port in network-byte order. Consult 'Transport Mappings
for Version 2 of the Simple Network Management Protocol
(SNMPv2)' for further information on snmpUDPDomain."
SYNTAX OCTET STRING (SIZE (0..255))
A new OID should be defined to handle IPv6 addresses.
5.070 RFC 2576 Coexistence between Version 1 Version 2 and Version
3 of the Internet-standard Network Management Framework (SNMP)
This document states:
(11) For any object with a SYNTAX of NetworkAddress, the SYNTAX MUST
be changed to IpAddress. Note that the use of NetworkAddress in
new MIB documents is strongly discouraged (in fact, new MIB
documents should be written using SMIv2, which does not define
NetworkAddress).
and defines the OID:
snmpTrapAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The value of the agent-addr field of a Trap PDU which
is forwarded by a proxy forwarder application using
an SNMP version other than SNMPv1. The value of this
object SHOULD contain the value of the agent-addr field
from the original Trap PDU as generated by an SNMPv1
agent."
::= { snmpCommunityMIBObjects 3 }
This clearly points out a lack of IPv6 awareness in this specification.
5.071 RFC 2564 Application Management MIB (APP-MIB) 5.064 RFC 2564 Application Management MIB
The following OID is defined: The following textual convention is defined:
ApplTAddress ::= TEXTUAL-CONVENTION ApplTAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a transport service address. "Denotes a transport service address.
For snmpUDPDomain, an ApplTAddress is 6 octets long, For snmpUDPDomain, an ApplTAddress is 6 octets long,
the initial 4 octets containing the IP-address in the initial 4 octets containing the IP-address in
network-byte order and the last 2 containing the UDP network-byte order and the last 2 containing the UDP
port in network-byte order. Consult 'Transport Mappings port in network-byte order. Consult 'Transport Mappings
for Version 2 of the Simple Network Management Protocol for Version 2 of the Simple Network Management Protocol
(SNMPv2)' for further information on snmpUDPDomain." (SNMPv2)' for further information on snmpUDPDomain."
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
A new OID should be defined to handle IPv6 addresses. A new TC should be defined to handle IPv6 addresses.
5.072 RFC 2576 Coexistence between Version 1 Version 2 and Version
3 of the Internet-standard Network Management Framework (SNMP)
This document states:
(11) For any object with a SYNTAX of NetworkAddress, the SYNTAX MUST
be changed to IpAddress. Note that the use of NetworkAddress in
new MIB documents is strongly discouraged (in fact, new MIB
documents should be written using SMIv2, which does not define
NetworkAddress).
and defines the OID:
snmpTrapAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The value of the agent-addr field of a Trap PDU which
is forwarded by a proxy forwarder application using
an SNMP version other than SNMPv1. The value of this
object SHOULD contain the value of the agent-addr field
from the original Trap PDU as generated by an SNMPv1
agent."
::= { snmpCommunityMIBObjects 3 }
This clearly points out a lack of IPv6 awareness in this specification.
5.073 RFC 2584 Definitions of Managed Objects for APPN/HPR in 5.065 RFC 2584 Definitions of Managed Objects for APPN/HPR in
IP Networks IP Networks
Many of the OIDs described in this document assume the use of the Many of the object definitions described in this document assume the
IPv4 only TOS header bits. It is therefore IPv4 only in nature and use of the IPv4 only TOS header bits. It is therefore IPv4-only in
will not support IPv6 interfaces. An updated MIB should be created. nature and will not support IPv6 interfaces. An updated MIB should
be created.
5.074 RFC 2591 Definitions of Managed Objects for Scheduling
Management Operations
There are no IPv4 dependencies in this protocol.
5.075 RFC 2592 Definitions of Managed Objects for the Delegation
of Management Script
There are no IPv4 dependencies in this protocol.
5.076 RFC 2594 Definitions of Managed Objects for WWW Services 5.066 RFC 2594 Definitions of Managed Objects for WWW Services
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.077 RFC 2605 Directory Server Monitoring MIB 5.067 RFC 2605 Directory Server Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.078 RFC 2613 Remote Network Monitoring MIB Extensions for 5.068 RFC 2613 Remote Network Monitoring MIB Extensions for
Switched Networks Version 1.0 Switched Networks Version 1.0
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.079 RFC 2618 RADIUS Authentication Client MIB 5.069 RFC 2618 RADIUS Authentication Client MIB
This RFC defines the following OIDs: This RFC defines the following OIDs:
RadiusAuthServerEntry ::= SEQUENCE { RadiusAuthServerEntry ::= SEQUENCE {
radiusAuthServerIndex Integer32, radiusAuthServerIndex Integer32,
radiusAuthServerAddress IpAddress, radiusAuthServerAddress IpAddress,
radiusAuthClientServerPortNumber Integer32, radiusAuthClientServerPortNumber Integer32,
radiusAuthClientRoundTripTime TimeTicks, radiusAuthClientRoundTripTime TimeTicks,
radiusAuthClientAccessRequests Counter32, radiusAuthClientAccessRequests Counter32,
radiusAuthClientAccessRetransmissions Counter32, radiusAuthClientAccessRetransmissions Counter32,
skipping to change at line 1563 skipping to change at line 1231
radiusAuthServerAddress OBJECT-TYPE radiusAuthServerAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the RADIUS authentication server "The IP address of the RADIUS authentication server
referred to in this table entry." referred to in this table entry."
::= { radiusAuthServerEntry 2 } ::= { radiusAuthServerEntry 2 }
There needs to be an update to allow an IPv6 based OID for this There needs to be an update to allow an IPv6 based object for this
value. value.
5.080 RFC 2619 RADIUS Authentication Server MIB 5.070 RFC 2619 RADIUS Authentication Server MIB
This MIB defines the followings OIDs: This MIB defines the followings objects:
RadiusAuthClientEntry ::= SEQUENCE { RadiusAuthClientEntry ::= SEQUENCE {
radiusAuthClientIndex Integer32, radiusAuthClientIndex Integer32,
radiusAuthClientAddress IpAddress, radiusAuthClientAddress IpAddress,
radiusAuthClientID SnmpAdminString, radiusAuthClientID SnmpAdminString,
radiusAuthServAccessRequests Counter32, radiusAuthServAccessRequests Counter32,
radiusAuthServDupAccessRequests Counter32, radiusAuthServDupAccessRequests Counter32,
radiusAuthServAccessAccepts Counter32, radiusAuthServAccessAccepts Counter32,
radiusAuthServAccessRejects Counter32, radiusAuthServAccessRejects Counter32,
radiusAuthServAccessChallenges Counter32, radiusAuthServAccessChallenges Counter32,
skipping to change at line 1594 skipping to change at line 1262
radiusAuthClientAddress OBJECT-TYPE radiusAuthClientAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NAS-IP-Address of the RADIUS authentication client "The NAS-IP-Address of the RADIUS authentication client
referred to in this table entry." referred to in this table entry."
::= { radiusAuthClientEntry 2 } ::= { radiusAuthClientEntry 2 }
There needs to be an update to allow an IPv6 based OID for this This object needs to be deprecated and replaced by one that
value. supports both IPv4 and IPv6 addresses.
5.081 RFC 2622 Routing Policy Specification Language (RPSL) 5.071 RFC 2622 Routing Policy Specification Language (RPSL)
(RPSL)
The only objects in the version of RPSL that deal with IP addresses The only objects in the version of RPSL that deal with IP addresses
are defined as: are defined as:
<ipv4-address> An IPv4 address is represented as a sequence of four <ipv4-address> An IPv4 address is represented as a sequence of four
integers in the range from 0 to 255 separated by the character dot integers in the range from 0 to 255 separated by the character dot
".". For example, 128.9.128.5 represents a valid IPv4 address. ".". For example, 128.9.128.5 represents a valid IPv4 address.
In the rest of this document, we may refer to IPv4 addresses as IP In the rest of this document, we may refer to IPv4 addresses as IP
addresses. addresses.
skipping to change at line 1620 skipping to change at line 1287
followed by the character slash "/" followed by an integer in the followed by the character slash "/" followed by an integer in the
range from 0 to 32. The following are valid address prefixes: range from 0 to 32. The following are valid address prefixes:
128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address 128.9.128.5/32, 128.9.0.0/16, 0.0.0.0/0; and the following address
prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not
strings containing four integers. strings containing four integers.
There seems to be an awareness of IPv6 because of the terminology but There seems to be an awareness of IPv6 because of the terminology but
it is not specifically defined. Therefore additional objects for IPv6 it is not specifically defined. Therefore additional objects for IPv6
addresses and masks need to be defined. addresses and masks need to be defined.
5.082 RFC 2662 Definitions of Managed Objects for the ADSL 5.072 RFC 2662 Definitions of Managed Objects for the ADSL
Lines (MIB) Lines
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.083 RFC 2665 Definitions of Managed Objects for the 5.073 RFC 2665 Definitions of Managed Objects for the
Ethernet-like Interface Types (MIB) Ethernet-like Interface Types
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.084 RFC 2667 IP Tunnel MIB Note that this specification is Obsoleted.
5.074 RFC 2667 IP Tunnel MIB
The Abstract of this document says: The Abstract of this document says:
This memo defines a Management Information Base (MIB) for use with This memo defines a Management Information Base (MIB) for use with
network management protocols in the Internet community. In network management protocols in the Internet community. In
particular, it describes managed objects used for managing tunnels of particular, it describes managed objects used for managing tunnels of
any type over IPv4 networks. Extension MIBs may be designed for any type over IPv4 networks. Extension MIBs may be designed for
managing protocol-specific objects. Likewise, extension MIBs may be managing protocol-specific objects. Likewise, extension MIBs may be
designed for managing security-specific objects. This MIB does not designed for managing security-specific objects. This MIB does not
support tunnels over non-IPv4 networks (including IPv6 networks). support tunnels over non-IPv4 networks (including IPv6 networks).
Management of such tunnels may be supported by other MIBs. Management of such tunnels may be supported by other MIBs.
A similar MIB for tunneling over IPv6 should be defined. A similar MIB for tunneling over IPv6 should be defined.
5.085 RFC 2668 Definitions of Managed Objects for IEEE 802.3 Medium 5.075 RFC 2668 Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs) (MAU-MIB) Attachment Units (MAUs)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.086 RFC 2669 DOCSIS Cable Device MIB Cable Device Management 5.076 RFC 2669 DOCSIS Cable Device MIB Cable Device Management
Information Base for DOCSIS compliant Cable Modems and Information Base for DOCSIS compliant Cable Modems and
Cable Modem Termination Systems Cable Modem Termination Systems
This document states: This document states:
Please note that the DOCSIS 1.0 standard only requires Cable Please note that the DOCSIS 1.0 standard only requires Cable
Modems to implement SNMPv1 and to process IPv4 customer traffic. Modems to implement SNMPv1 and to process IPv4 customer traffic.
Design choices in this MIB reflect those requirements. Future Design choices in this MIB reflect those requirements. Future
versions of the DOCSIS standard are expected to require support versions of the DOCSIS standard are expected to require support
for SNMPv3 and IPv6 as well. for SNMPv3 and IPv6 as well.
5.087 RFC 2670 Radio Frequency (RF) Interface Management Information 5.077 RFC 2670 Radio Frequency (RF) Interface Management Information
Base for MCNS/DOCSIS compliant RF interfaces (MIB) Base for MCNS/DOCSIS compliant RF interfaces
This MIB defines the following OIDs: This MIB defines the following objects:
DocsIfCmtsCmStatusEntry ::= SEQUENCE { DocsIfCmtsCmStatusEntry ::= SEQUENCE {
docsIfCmtsCmStatusIndex Integer32, docsIfCmtsCmStatusIndex Integer32,
docsIfCmtsCmStatusMacAddress MacAddress, docsIfCmtsCmStatusMacAddress MacAddress,
docsIfCmtsCmStatusIpAddress IpAddress, docsIfCmtsCmStatusIpAddress IpAddress,
docsIfCmtsCmStatusDownChannelIfIndex InterfaceIndexOrZero, docsIfCmtsCmStatusDownChannelIfIndex InterfaceIndexOrZero,
docsIfCmtsCmStatusUpChannelIfIndex InterfaceIndexOrZero, docsIfCmtsCmStatusUpChannelIfIndex InterfaceIndexOrZero,
docsIfCmtsCmStatusRxPower TenthdBmV, docsIfCmtsCmStatusRxPower TenthdBmV,
docsIfCmtsCmStatusTimingOffset Unsigned32, docsIfCmtsCmStatusTimingOffset Unsigned32,
docsIfCmtsCmStatusEqualizationData OCTET STRING, docsIfCmtsCmStatusEqualizationData OCTET STRING,
skipping to change at line 1696 skipping to change at line 1365
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"IP address of this Cable Modem. If the Cable Modem has no "IP address of this Cable Modem. If the Cable Modem has no
IP address assigned, or the IP address is unknown, this IP address assigned, or the IP address is unknown, this
object returns a value of 0.0.0.0. If the Cable Modem has object returns a value of 0.0.0.0. If the Cable Modem has
multiple IP addresses, this object returns the IP address multiple IP addresses, this object returns the IP address
associated with the Cable interface." associated with the Cable interface."
::= { docsIfCmtsCmStatusEntry 3 } ::= { docsIfCmtsCmStatusEntry 3 }
IPv6 OIDs should be defined. This object needs to be deprecated and replaced by one that
supports both IPv4 and IPv6 addresses.
5.088 RFC 2674 Definitions of Managed Objects for Bridges with 5.078 RFC 2674 Definitions of Managed Objects for Bridges with
Traffic Classes, Multicast Filtering and Virtual LAN Traffic Classes, Multicast Filtering and Virtual LAN
Extensions (MIB) Extensions
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.089 RFC 2677 Definitions of Managed Objects for the NBMA Next 5.079 RFC 2677 Definitions of Managed Objects for the NBMA Next
Hop Resolution Protocol (NHRP) (NHRP-MIB) Hop Resolution Protocol (NHRP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.90 RFC 2720 Traffic Flow Measurement: Meter MIB 5.080 RFC 2720 Traffic Flow Measurement: Meter MIB
This protocol is both IPv4 and IPv6 aware and needs no changes.
5.091 RFC 2725 Routing Policy System Security
There are no IPv4 dependencies in this protocol. This specification is both IPv4 and IPv6 aware and needs no changes.
5.092 RFC 2726 PGP Authentication for RIPE Database Updates 5.081 RFC 2725 Routing Policy System Security
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.093 RFC 2737 Entity MIB (Version 2) 5.082 RFC 2726 PGP Authentication for RIPE Database Updates
The TAddress Syntax is used in this MIB which contains IPv4 There are no IPv4 dependencies in this specification.
assumptions and need to be updated.
entLogicalTAddress OBJECT-TYPE 5.083 RFC 2737 Entity MIB (Version 2)
SYNTAX TAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The transport service address by which the logical entity
receives network management traffic, formatted according to
the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial There are no IPv4 dependencies in this specification.
4 octets containing the IP-address in network-byte order and
the last 2 containing the UDP port in network-byte order.
Consult 'Transport Mappings for Version 2 of the Simple
Network Management Protocol' (RFC 1906 [RFC1906]) for
further information on snmpUDPDomain."
5.094 RFC 2741 Agent Extensibility (AgentX) Protocol Version 5.084 RFC 2741 Agent Extensibility (AgentX) Protocol Version 1
1 (SNMP)
This protocol contains definitions for IPv4 only objects, by reference Although the examples in the document are for IPv4 transport
and all examples use only IPv4 addressing. However, there does not only, there is no IPv4 dependency in the AgentX protocol itself.
seem to be any reason that it could not easily be modified to support
IPv6 addresses.
5.095 RFC 2742 Definitions of Managed Objects for Extensible SNMP 5.085 RFC 2742 Definitions of Managed Objects for Extensible SNMP
Agents Agents
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.096 RFC 2748 The COPS (Common Open Policy Service) Protocol 5.086 RFC 2748 The COPS (Common Open Policy Service) Protocol
(COPS)
This protocol is both IPv4 and IPv6 aware and needs no changes. This protocol is both IPv4 and IPv6 aware and needs no changes.
5.097 RFC 2749 COPS usage for RSVP 5.087 RFC 2749 COPS usage for RSVP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.098 RFC 2769 Routing Policy System Replication (RPSL) 5.088 RFC 2769 Routing Policy System Replication
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.099 RFC 2787 Definitions of Managed Objects for the Virtual 5.089 RFC 2787 Definitions of Managed Objects for the Virtual
Router Redundancy Protocol Router Redundancy Protocol
As stated in the Overview section: As stated in the Overview section:
Since the VRRP protocol is intended for use with IPv4 routers only, Since the VRRP protocol is intended for use with IPv4 routers only,
this MIB uses the SYNTAX for IP addresses which is specific to IPv4. this MIB uses the SYNTAX for IP addresses which is specific to IPv4.
Thus, changes will be required for this MIB to interoperate in an Thus, changes will be required for this MIB to interoperate in an
IPv6 environment. IPv6 environment.
5.100 RFC 2788 Network Services Monitoring MIB 5.090 RFC 2788 Network Services Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.101 RFC 2789 Mail Monitoring MIB 5.091 RFC 2789 Mail Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.102 RFC 2837 Definitions of Managed Objects for the Fabric Element 5.092 RFC 2837 Definitions of Managed Objects for the Fabric Element
in Fibre Channel Standard in Fibre Channel Standard
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.103 RFC 2851 Textual Conventions for Internet Network Addresses
This MIB defines a new set of OIDs for that allow new MIB's to
use multiple versions of IP. Currently IPv4 and IPv6 addressing
is defined. Update of the many MIBs previously identified as
having IPv4 dependencies could easily be updated using this new
set of IP address abstractions.
5.104 RFC 2856 Textual Conventions for Additional High Capacity 5.094 RFC 2856 Textual Conventions for Additional High Capacity
Data Types (SNMP) Data Types
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.105 RFC 2864 The Inverted Stack Table Extension to the Interfaces 5.095 RFC 2864 The Inverted Stack Table Extension to the Interfaces
Group MIB Group MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.106 RFC 2895 Remote Network Monitoring MIB Protocol Identifier 5.096 RFC 2895 Remote Network Monitoring MIB Protocol Identifier
Reference (RMON-MIB) Reference
This MIB is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
5.107 RFC 2925 Definitions of Managed Objects for Remote 5.097 RFC 2925 Definitions of Managed Objects for Remote
Ping, Traceroute, and Lookup Operations Ping, Traceroute, and Lookup Operations
This MIB mostly is IPv4 and IPv6 aware. There are a few This MIB mostly is IPv4 and IPv6 aware. There are a few
assumptions that are problems thought. In the following OIDs: assumptions that are problems, though. In the following object
definitions:
pingCtlDataSize OBJECT-TYPE pingCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507) SYNTAX Unsigned32 (0..65507)
UNITS "octets" UNITS "octets"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Specifies the size of the data portion to be "Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping transmitted in a ping operation in octets. A ping
request is usually an ICMP message encoded request is usually an ICMP message encoded
skipping to change at line 1852 skipping to change at line 1494
DESCRIPTION DESCRIPTION
"Specifies the size of the data portion of a traceroute "Specifies the size of the data portion of a traceroute
request in octets. A traceroute request is essentially request in octets. A traceroute request is essentially
transmitted by encoding a UDP datagram into a transmitted by encoding a UDP datagram into a
IP packet. So subtracting the size of a UDP header IP packet. So subtracting the size of a UDP header
(8 octets) and the size of a IP header (20 octets) (8 octets) and the size of a IP header (20 octets)
yields a maximum of 65507 octets." yields a maximum of 65507 octets."
DEFVAL { 0 } DEFVAL { 0 }
::= { traceRouteCtlEntry 6 } ::= { traceRouteCtlEntry 6 }
There is clearly an assumption of IPv4 header sizes. The DESCRIPTION clauses need to be updated to remove the
IPv4 dependencies.
5.108 RFC 2932 IPv4 Multicast Routing MIB 5.098 RFC 2932 IPv4 Multicast Routing MIB
This specification is only defined for IPv4 and a similar MIB This specification is only defined for IPv4 and a similar MIB
must be defined for IPv6. must be defined for IPv6.
5.109 RFC 2933 Internet Group Management Protocol MIB 5.099 RFC 2933 Internet Group Management Protocol MIB
As stated in this document: As stated in this document:
Since IGMP is specific to IPv4, this MIB does not support management Since IGMP is specific to IPv4, this MIB does not support management
of equivalent functionality for other address families, such as IPv6. of equivalent functionality for other address families, such as IPv6.
5.110 RFC 2940 Definitions of Managed Objects for Common 5.100 RFC 2940 Definitions of Managed Objects for Common
Open Policy Service (COPS) Protocol Clients Open Policy Service (COPS) Protocol Clients
This MIB is both IPv4 and IPv6 aware and needs no changes. This MIB is both IPv4 and IPv6 aware and needs no changes.
5.111 RFC 2954 Definitions of Managed Objects for Frame 5.101 RFC 2954 Definitions of Managed Objects for Frame
Relay Service (FR-MIB) Relay Service
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.112 RFC 2955 Definitions of Managed Objects for Monitoring 5.102 RFC 2955 Definitions of Managed Objects for Monitoring
and Controlling the Frame Relay/ATM PVC Service and Controlling the Frame Relay/ATM PVC Service
Interworking Function Interworking Function
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.113 RFC 2959 Real-Time Transport Protocol Management 5.103 RFC 2959 Real-Time Transport Protocol Management
Information Base Information Base
There are numerous uses of the included TAddress Syntax which is
IPv4 dependent as noted above.
For example:
rtpSessionRemAddr OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The address to which RTP packets are sent by the RTP system.
In an IP multicast RTP session, this is the single address used
by all senders and receivers of RTP session data. In a unicast
RTP session this is the unicast address of the remote RTP system.
'The destination address pair may be common for all participants,
as in the case of IP multicast, or may be different for each, as
in the case of individual unicast network address pairs.' See
RFC 1889, 'RTP: A Transport Protocol for Real-Time Applications,'
sec. 3. The transport service is identified by rtpSessionDomain.
For snmpUDPDomain, this is an IP address and even-numbered UDP
Port with the RTCP being sent on the next higher odd-numbered
port, see RFC 1889, sec. 5."
::= { rtpSessionEntry 3 }
There are a total of 8 instances of this.
5.114 RFC 2981 Event MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.115 RFC 2982 Distributed Management Expression MIB 5.104 RFC 2981 Event MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.116 RFC 3014 Notification Log MIB 5.105 RFC 2982 Distributed Management Expression MIB
This document contains OIDs that are IPv4 specific:
nlmLogVariableIpAddressVal OBJECT-TYPE There are no IPv4 dependencies in this specification.
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value when nlmLogVariableType is 'ipAddress'.
Although this seems to be unfriendly for IPv6, we
have to recognize that there are a number of older
MIBs that do contain an IPv4 format address, known
as IpAddress.
IPv6 addresses are represented using TAddress or 5.106 RFC 3014 Notification Log MIB
InetAddress, and so the underlying datatype is
OCTET STRING, and their value would be stored in
the nlmLogVariableOctetStringVal column."
::= { nlmLogVariableEntry 9 }
Not withstanding the note in the DESCRIPTION. There are no IPv4 dependencies in this specification.
5.117 RFC 3019 IP Version 6 Management Information Base for 5.107 RFC 3019 IP Version 6 Management Information Base for
The Multicast Listener Discovery Protocol The Multicast Listener Discovery Protocol
This is an IPv6 related document and is not discussed in this This is an IPv6 related document and is not discussed in this
document. document.
5.118 RFC 3020 Definitions of Managed Objects for Monitoring 5.108 RFC 3020 Definitions of Managed Objects for Monitoring
and Controlling the UNI/NNI Multilink Frame Relay Function and Controlling the UNI/NNI Multilink Frame Relay Function
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.119 RFC 3055 Management Information Base for the PINT Services 5.109 RFC 3055 Management Information Base for the PINT Services
Architecture Architecture
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.120 RFC 3060 Policy Core Information Model -- Version 1 5.110 RFC 3060 Policy Core Information Model -- Version 1
Specification (CIM) Specification (CIM)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.121 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR) 5.111 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR)
(COPS-PR)
This is an IPv4 only protocol. A version for IPv6 must be defined. This is an IPv4 only protocol. A version for IPv6 may need to be
defined.
5.112 RFC 3165 Definitions of Managed Objects for the Delegation of
Management Scripts.
There are no IPv4 dependencies in this specification.
5.112 RFC 3231 Definitions of Managed Objects for Scheduling Management
Operations.
There are no IPv4 dependecies in this specification.
5.113 RFC 3291 Textual Conventions for Internet Network Addresses
There are no IPv4 dependencies in this specification.
6.0 Experimental RFCs 6.0 Experimental RFCs
Experimental RFCs typically define protocols that do not have widescale Experimental RFCs typically define protocols that do not have widescale
implementation or usage on the Internet. They are often propriety in implementation or usage on the Internet. They are often propriety in
nature or used in limited arenas. They are documented to the Internet nature or used in limited arenas. They are documented to the Internet
community in order to allow potential interoperability or some other community in order to allow potential interoperability or some other
potential useful scenario. In a few cases they are presented as potential useful scenario. In a few cases they are presented as
alternatives to the mainstream solution to an acknowledged problem. alternatives to the mainstream solution to an acknowledged problem.
6.01 RFC 1187 Bulk Table Retrieval with the SNMP (SNMP-BULK) 6.01 RFC 1187 Bulk Table Retrieval with the SNMP
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.02 RFC 1224 Techniques for managing asynchronously generated 6.02 RFC 1224 Techniques for managing asynchronously generated
alerts (ALERTS) alerts
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.03 RFC 1238 CLNS MIB for use with Connectionless Network Protocol 6.03 RFC 1238 CLNS MIB for use with Connectionless Network Protocol
(ISO 8473) and End System to Intermediate System (ISO 9542) (ISO 8473) and End System to Intermediate System (ISO 9542)
(CLNS-MIB)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.04 RFC 1592 Simple Network Management Protocol Distributed Protocol 6.04 RFC 1592 Simple Network Management Protocol Distributed Protocol
Interface Version 2.0 (SNMP-DPI) Interface Version 2.0
There are no IPv4 dependencies in this protocol.
6.05 RFC 1792 TCP/IPX Connection Mib Specification (TCP/IPXMIB)
There are no IPv4 dependencies in this specification.
6.06 RFC 1901 Introduction to Community-based SNMPv2 (SNMPV2CB)
There are no IPv4 dependencies in this protocol.
6.07 RFC 1909 An Administrative Infrastructure for SNMPv2
(SNMPV2AI)
There are no IPv4 dependencies in this protocol.
6.08 RFC 1910 User-based Security Model for SNMPv2 (SNMPV2SM)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.09 RFC 2593 Script MIB Extensibility Protocol Version 1.0 6.05 RFC 1792 TCP/IPX Connection Mib Specification
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.10 RFC 2724 RTFM: New Attributes for Traffic Flow Measurement 6.07 RFC 2724 RTFM: New Attributes for Traffic Flow Measurement
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.11 RFC 2758 Definitions of Managed Objects for Service Level 6.08 RFC 2758 Definitions of Managed Objects for Service Level
Agreements Performance Monitoring Agreements Performance Monitoring
This protocol is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
6.12 RFC 2786 Diffie-Helman USM Key Management Information Base and 6.13 RFC 2786 Diffie-Helman USM Key Management Information Base and
Textual Convention Textual Convention
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.13 RFC 2903 Generic AAA Architecture 6.14 RFC 2903 Generic AAA Architecture
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.14 RFC 2934 Protocol Independent Multicast MIB for IPv4 6.15 RFC 2934 Protocol Independent Multicast MIB for IPv4
This document is specific to IPv4. This document is specific to IPv4.
6.16 RFC 3179 Script MIB Extensibility Protocol Version 1.1
There are no IPv4 dependencies in this specification.
7.0 Summary of Results 7.0 Summary of Results
In the initial survey of RFCs 41 positives were identified out of a In the initial survey of RFCs 41 positives were identified out of a
total of 163, broken down as follows: total of 163, broken down as follows:
Standards 6 of 10 or 60.00% Standards 6 of 10 or 60.00%
Draft Standards 3 of 18 or 16.67% Draft Standards 3 of 18 or 16.67%
Proposed Standards 31 of 121 or 25.62% Proposed Standards 31 of 121 or 25.62%
Experimental RFCs 1 of 14 or 7.14% Experimental RFCs 1 of 14 or 7.14%
Of those identified many require no action because they document Of those identified many require no action because they document
outdated and unused protocols, while others are document protocols outdated and unused protocols, while others are document protocols
that are actively being updated by the appropriate working groups. that are actively being updated by the appropriate working groups.
Additionally there are many instances of standards that should be Additionally there are many instances of standards that should be
updated but do not cause any operational impact if they are not updated but do not cause any operational impact if they are not
updated. The remaining instances are documented below. updated. The remaining instances are documented below.
7.1 Standards 7.1 Standards
7.1.1 STD 15 Simple Network Management Protocol (RFCs 1157, 1155, 1213) 7.1.1 STD 16, Structure of Management Information (RFCs 1155 and 1212)
The limitations identified have been addressed; RFC 1157 is HISTORIC, RFCs 1155 and RFCs 1212 (along with the informational document RFC
RFC1155 is obsoleted by RFC 2578-2580, and RFC1213 has been split to 1215) define SMIv1. These documents have been superseded by RFCs
multiple modules which have been seen to. 2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer
being used as the basis for new IETF MIB modules, the limitations
identified in this Internet Standard do not require any action.
7.1.2 STD 17 Simple Network Management Protocol (RFC 1213)
The limitations identified have been addressed, RFC1213 has been
split into multiple modules which have been seen to.
7.2 Draft Standards 7.2 Draft Standards
7.2.1 BGP4 MIB (RFC 1657) 7.2.1 BGP4 MIB (RFC 1657)
This problem is currently being addressed by the Inter Domain Routing This problem is currently being addressed by the Inter Domain Routing
(IDR) WG and an ID exists (draft-ietf-idr-bgp4-mib-09.txt). (IDR) WG and an ID exists (draft-ietf-idr-bgp4-mib-11.txt).
7.2.2 SMDS MIB (RFC 1694) 7.2.2 SMDS MIB (RFC 1694)
See Section 7.1.22. Once a specification for IPv6 over SMDS is See Internet Area standards. Once a specification for IPv6 over SMDS
created a new MIB must be defined. is created a new MIB must be defined.
7.2.3 RIPv2 MIB (RFC 1724) 7.2.3 RIPv2 MIB (RFC 1724)
See Section 7.1.24. This problem is currently being addressed by the See Routing standards. This problem is currently being addressed by
RIP WG and an ID exists (draft-ietf-rip-mib-01.txt). the RIP WG and an ID exists (draft-ietf-rip-mib-01.txt).
7.2.4 OSPFv2 MIB (RFC 1850) 7.2.4 OSPFv2 MIB (RFC 1850)
This problem is currently being addressed by the OSPF WG and an ID This problem is currently being addressed by the OSPF WG and an ID
exists (draft-ietf-ospf-ospfv3-mib-04.txt). exists (draft-ietf-ospf-ospfv3-mib-07.txt).
7.2.5 Transport MIB (RFC 1906) 7.2.5 Transport MIB (RFC 1906)
The problem has been fixed in RFC 2454, IPv6 Management Information RFC 1906 has been obsoleted by RFC 3417, Transport Mappings for
Base for the User Datagram Protocol. SNMP, and the limitations of this specification have been addressed by
that RFC, which defines TCs that can be used to specify transport
7.2.6 Frame Relay MIB (RFC 2115) domains in an IP version-independent way. RFC 3419 recommends that
those TCs be used in place of SnmpUDPAddress when IPv6 support is
The problem has been fixed in RFC 2954, Definitions of Managed Objects required and for all new applications that are not SNMP-specific.
for Frame Relay Service.
7.3 Proposed Standards 7.3 Proposed Standards
7.3.01 MIB for Multiprotocol Interconnect over X.25 (RFC 1461) 7.3.01 MIB for Multiprotocol Interconnect over X.25 (RFC 1461)
This problem has not been addressed. A new specification should This problem has not been addressed. If a user requirement for
be created. IPv6 over X.25 develops (which is thought to be unlikely) then
this MIB module will need to be updated in order to accomodate it.
7.3.02 PPP IPCP MIB (RFC 1473) 7.3.02 PPP IPCP MIB (RFC 1473)
There is no updated MIB to cover the problems outlined. A new MIB There is no updated MIB to cover the problems outlined. A new MIB
must be defined. should be defined.
7.3.03 DNS Server MIB (RFC 1611)
This document is HISTORIC and no action is required.
7.3.04 DNS Resolver MIB (RFC 1612)
This document is HISTORIC and no action is required.
7.3.05 Appletalk MIB (RFC 1742) 7.3.03 Appletalk MIB (RFC 1742)
The problems have not been addressed and a new MIB should be defined. This problem has not been addressed. If a user requirement for
IPv6 over Appletalk develops (which is thought to be unlikely)
then this MIB module will need to be updated (or a new MIB module
will need to be created) in order to accomodate it.
7.3.06 The Definitions of Managed Objects for IP Mobility 7.3.04 The Definitions of Managed Objects for IP Mobility
Support using SMIv2 (RFC 2006) Support using SMIv2 (RFC 2006)
The problems are being resolved by the Mobile IP WG and there is The problems are being resolved by the Mobile IP WG and there is
an ID (draft-ietf-mobileip-rfc2006bis-00.txt) an ID (draft-ietf-mobileip-rfc2006bis-02.txt)
7.3.07 SMIv2 MIB IP (RFC 2011) 7.3.05 SMIv2 IP MIB (RFC 2011)
The problems have been addressed in RFC 2851, Textual Conventions This issue is being resolved by the IPv6 WG and there is an
for Internet Network Addresses, and RFC 2465, Management Information ID (draft-ietf-ipv6-rfc2011-update-03.txt).
Base for IP Version 6: Textual Conventions and General Group.
7.3.08 SNMPv2 MIB TCP (RFC 2012) 7.3.06 SNMPv2 TCP MIB (RFC 2012)
The problems have been addressed in RFC 2452, IPv6 Management This issue is being resolved by the IPv6 WG and there is an
Information Base for the Transmission Control Protocol. ID (draft-ietf-ipv6-rfc2012-update-03.txt).
7.3.09 SNMPv2 MIB UDP (RFC 2013) 7.3.07 SNMPv2 UDP MIB (RFC 2013)
The problems have been addressed in RFC 2454, IPv6 Management This issue is being resolved by the IPv6 WG.
Information Base for the User Datagram Protocol.
7.3.10 RMON MIB (RFC 2021) 7.3.08 RMON-II MIB (RFC 2021)
The problems have been addressed in RFC 2819, Remote Network This issue has been brought to the attention of the RMONMIB WG.
Monitoring Management Information Base. Currently there is an ID (draft-ietf-rmonmib-rmon2-v2-00.txt)
to update RFC 2021, but it does not address the problems that
have been identified; it is expected that there will be a
resolution in a future version of that ID.
7.3.11 DataLink Switching using SMIv2 MIB (RFC 2022) 7.3.09 DataLink Switching using SMIv2 MIB (RFC 2024)
The problems have not been addressed and a new MIB should be The problems have not been addressed and an updated MIB should be
defined. defined.
7.3.12 IP Forwarding Table MIB (RFC 2096) 7.3.10 IP Forwarding Table MIB (RFC 2096)
This issue is being worked on by the IPv6 WG and an ID exists to This issue is being worked on by the IPv6 WG and an ID exists to
address this (draft-ietf-ipngwg-rfc2096-update-00.txt) address this (draft-ietf-ipngwg-rfc2096-update-05.txt)
7.3.13 Classical IP & ARP over ATM MIB (RFC 2320)
The problems identified are not addressed and a new MIB must be
defined.
7.3.14 Multicast over UNI 3.0/3.1 ATM MIB (RFC 2417) 7.3.11 Classical IP & ARP over ATM MIB (RFC 2320)
The problems identified are not addressed and a new MIB must be The current version of Classical IP and ARP over ATM (RFC 2225)
defined. does not support IPv6. If and when that protocol specification
is updated to add IPv6 support, then new MIB objects to represent
IPv6 addresses will need to be added to this MIB module
7.3.15 ATM MIB (RFC 2515) 7.3.12 Multicast over UNI 3.0/3.1 ATM MIB (RFC 2417)
The problems identified are not addressed and a new MIB must be The current version of Multicast over UNI 3.0/3.1 ATM (RFC
defined. 2022) does not support IPv6. If and when that protocol
specification is updated to add IPv6 support, then new MIB
objects to represent IPv6 addresses will need to be added to
this MIB module.
7.3.16 TN3270 MIB (RFC 2562) 7.3.13 ATM MIB (RFC 2515)
The problems identified are not addressed and a new MIB may be The AToM MIB WG is currently collecting implementation reports for RFC
defined. 2515 and is considering whether to advance, revise, or retire this
specification. The problems identified have been brought to the
attention of the WG.
7.3.17 Application MIB (RFC 2564) 7.3.14 TN3270 MIB (RFC 2562)
The problems identified are not addressed and a new MIB may be The problems identified are not being addressed and a new MIB
defined. module may need to be defined.
One possible solution is to use RFC 3419 TCs.
7.3.18 Coexistence of SNMP v1, v2, & v3 (RFC 2576) 7.3.15 Application MIB (RFC 2564)
There are no real issues that can be resolved. The problems identified are not being addressed and a new MIB
module may need to be defined. One possible solution might be
to use the RFC 3419 TCs.
7.3.19 Definitions of Managed Objects for APPN/HPR in IP Networks 7.3.16 Definitions of Managed Objects for APPN/HPR in IP Networks
(RFC 2584) (RFC 2584)
The problems identified are not addressed and a new MIB may be The problems identified are not addressed and a new MIB may be
defined. defined.
7.3.20 RADIUS MIB (RFC 2618) 7.3.17 RADIUS MIB (RFC 2618)
The problems have not been addressed and a new MIB should be defined. The problems have not been addressed and a new MIB should be defined.
7.3.21 RADIUS Authentication Server MIB (RFC 2619) 7.3.18 RADIUS Authentication Server MIB (RFC 2619)
The problems have not been addressed and a new MIB should be defined. The problems have not been addressed and a new MIB should be defined.
7.3.22 IPv4 Tunnel MIB (RFC 2667) 7.3.19 IPv4 Tunnel MIB (RFC 2667)
The problems have not been addressed and a new MIB should be defined. The problems have not been addressed and a new MIB should be defined.
7.3.23 DOCSIS MIB (RFC 2669) 7.3.20 DOCSIS MIB (RFC 2669)
This problem is currently being addressed by the IPCDN WG and an ID This problem is currently being addressed by the IPCDN WG and an ID
is available (draft-ietf-ipcdn-device-mibv2-01.txt). is available (draft-ietf-ipcdn-device-mibv2-05.txt).
7.3.24 RF MIB For DOCSIS (RFC 2670) 7.3.21 RF MIB For DOCSIS (RFC 2670)
This problem is currently being addressed by the IPCDN WG and an ID This problem is currently being addressed by the IPCDN WG and an ID
is available (draft-ietf-ipcdn-docs-rfmibv2-01.txt). is available (draft-ietf-ipcdn-docs-rfmibv2-06.txt).
7.3.25 Entity MIB Version 2 (RFC 2737)
The problems have not been addressed and a new MIB should be defined.
7.3.26 AgentX Protocol V1 (RFC 2741) 7.3.22 VRRP MIB (RFC 2787)
The problems have not been addressed and a new protocol may be The problems have not been addressed and a new MIB may need to be
defined. defined.
7.3.27 VRRP MIB (RFC 2787) 7.3.23 MIB For Traceroute, Pings and Lookups (RFC 2925)
The problems have not been addressed and a new MIB should be defined.
7.3.28 MIB For Traceroute, Pings and Lookups (RFC 2925)
The problems have not been addressed and a new MIB may be defined. The problems have not been addressed and a new MIB may need to be
defined.
7.3.29 IPv4 Multicast Routing MIB (RFC 2932) 7.3.24 IPv4 Multicast Routing MIB (RFC 2932)
This problem is currently being addressed by the IDR WG and several This problem is currently being addressed by the IDR WG and several
IDs exist. IDs exist.
7.3.30 IGMP MIB (RFC 2933) 7.3.25 IGMP MIB (RFC 2933)
This problem is currently being addressed by the IDR WG. This problem is currently being addressed by the IDR WG.
7.3.31 RPSL (RFC 2622) 7.3.26 RPSL (RFC 2622)
Additional objects must be defined for IPv6 addresses and prefixes. Additional objects must be defined for IPv6 addresses and prefixes.
draft-blunk-rpslng-01.txt defines extensions to solve this issue, and
it is being considered for publication.
7.4 Experimental RFCs 7.4 Experimental RFCs
7.4.1 Protocol Independent Multicast MIB for IPv4 (RFC 2934) 7.4.1 Protocol Independent Multicast MIB for IPv4 (RFC 2934)
The problems have not been addressed and a new MIB should be defined. The problems have not been addressed and a new MIB may need to be
defined.
8.0 Security Consideration 8.0 Security Consideration
This memo examines the IPv6-readiness of specifications; this does not This memo examines the IPv6-readiness of specifications; this does not
have security considerations in itself. have security considerations in itself.
9.0 Acknowledgements 9.0 Acknowledgements
The authors would like to acknowledge the support of the Internet The authors would like to acknowledge the support of the Internet
Society in the research and production of this document. Society in the research and production of this document.
Additionally the author, Philip J. Nesser II, would like to thanks Additionally the author, Philip J. Nesser II, would like to thanks
his partner in all ways, Wendy M. Nesser. his partner in all ways, Wendy M. Nesser.
The editor, Andreas Bergstrom, would like to thank Pekka Savola The editor, Andreas Bergstrom, would like to thank Pekka Savola
for guidance and collection of comments for the editing of this for guidance and collection of comments for the editing of this
document. document.
He would further like to thank Juergen Schoenwaelder, Brian Carpenter He would further like to thank Juergen Schoenwaelder, Brian Carpenter,
and C. M. Heard for feedback on many points of this document. Bert Wijnen and especially C. M. Heard for feedback on many points of
this document.
10.0 References 10.0 References
10.1 Normative 10.1 Normative
[1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey [1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey
of IPv4 Addresses in Currently Deployed IETF Standards", of IPv4 Addresses in Currently Deployed IETF Standards",
draft-ietf-v6ops-ipv4survey-intro-02.txt IETF work in progress, draft-ietf-v6ops-ipv4survey-intro-04.txt IETF work in progress,
August 2003 September 2003
11.0 Authors Address 11.0 Authors Address
Please contact the author with any questions, comments or suggestions Please contact the author with any questions, comments or suggestions
at: at:
Philip J. Nesser II Philip J. Nesser II
Principal Principal
Nesser & Nesser Consulting Nesser & Nesser Consulting
13501 100th Ave NE, #5202 13501 100th Ave NE, #5202
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/