draft-ietf-v6ops-ipv4survey-ops-01.txt   draft-ietf-v6ops-ipv4survey-ops-02.txt 
Network Working Group Philip J. Nesser II Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-ops-01.txt Nesser & Nesser Consulting draft-ietf-v6ops-ipv4survey-ops-02.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom Internet Draft Andreas Bergstrom
Ostfold University College Ostfold University College
June 2003 August 2003
Expires December 2003 Expires January 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 141 skipping to change at line 141
There are far too many instances of IPv4 addresses is this document There are far too many instances of IPv4 addresses is this document
to enumerate here. Clearly the entire IP OID sub tree is rife with 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 IPv4 dependencies. A new sub tree needs to be defined to deal with
IPv6 addresses leaving the current sub tree intact for IPv4 address IPv6 addresses leaving the current sub tree intact for IPv4 address
information. information.
3.4 RFC 1643 Definitions of Managed Objects for the Ethernet-like 3.4 RFC 1643 Definitions of Managed Objects for the Ethernet-like
Interface Types Interface Types
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
3.5 Structure of Management Information Version 2 (SMIv2. RFC2578,
RFC2579
3.5.1 RFC 2578 Structure of Management Information Version 2 (SMIv2) 3.5 RFC 2578 Structure of Management Information Version 2 (SMIv2)
Section 7.1.5. IpAddress defines: Section 7.1.5. IpAddress defines:
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 [3]. TEXTUAL-CONVENTION macro.
Note the depreciated status of this type. Note the deprecated status of this type; see RFC 3291 for details on
TEXTUAL-CONVENTION macro.
3.5.2 RFC 2579 Textual Conventions for SMIv2 3.6 RFC 2579 Textual Conventions for SMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
3.6 RFC 2819 Remote Network Monitoring Management Information Base 3.7 RFC 2819 Remote Network Monitoring Management Information Base
(RMON-MIB) (RMON-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
3.8 RFC 3416 Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2) (OPS-MIB)
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
data contains IPv4 addresses. Other than their use in these example
sections there are no IPv4 dependencies in this specification.
3.9 RFC 3417 Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2) (TRANS-MIB)
Section 2 Definitions contains the following OID definition:
SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current
DESCRIPTION
"Represents a UDP address:
octets contents encoding
1-4 IP-address network-byte order
5-6 UDP-port network-byte order
"
SYNTAX OCTET STRING (SIZE (6))
Section 8.1. Usage Example also contains examples which use IPv4
address, but it has no significance in the operation of the
specification.
3.10 RFC 3418 Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2) (SNMPv2-MIB)
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 (BRIDGE-MIB)
There are no IPv4 dependencies in this protocol. 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 (DECNET-MIB)
There are no IPv4 dependencies in this protocol. 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 (BGP-4-MIB)
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 protocol. 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 protocol.
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.
skipping to change at line 314 skipping to change at line 346
can be defined for IPv6 addressing. 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 (RIP2-MIB)
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 for an IPv4 only routing protocol. A new MIB for RIPng
is required. 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 (802.5-MIB)
There are no IPv4 dependencies in this protocol. 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 (OSPF-MIB)
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 1905 Protocol Operations for Version 2 of the Simple Network 4.11 RFC 2115 Management Information Base for Frame Relay DTEs
Management Protocol (SNMPv2) (OPS-MIB)
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
data contains IPv4 addresses. Other than their use in these example
sections there are no IPv4 dependencies in this protocol.
4.12 RFC 1906 Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2) (TRANS-MIB)
Section 2 Definitions contains the following OID definition:
SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current
DESCRIPTION
"Represents a UDP address:
octets contents encoding
1-4 IP-address network-byte order
5-6 UDP-port network-byte order
"
SYNTAX OCTET STRING (SIZE (6))
Section 8.1. Usage Example also contains examples which use IPv4
address, but it has no significance in the operation of the protocol.
4.13 RFC 1907 Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2) (SNMPv2-MIB)
There are no IPv4 dependencies in this protocol.
4.14 RFC 2115 Management Information Base for Frame Relay DTEs
Using SMIv2 (FRAME-MIB) Using SMIv2 (FRAME-MIB)
This MIB has several examples of mapping IPv4 addresses to multiple 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 Frame Relay DLCI's and monitoring their connections. A new set of OID's
needs to be defined to allow this functionality for IPv6. needs to be defined to allow this functionality for IPv6.
4.15 RFC 2571 An Architecture for Describing SNMP Management Frameworks 4.12 RFC 2571 An Architecture for Describing SNMP Management Frameworks
(ARCH-SNMP) (ARCH-SNMP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.16 RFC 2572 Message Processing and Dispatching for the Simple Network 4.13 RFC 2572 Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP) (MPD-SNMP) Management Protocol (SNMP) (MPD-SNMP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.17 RFC 2573 SNMP Applications (SNMP-APP) 4.14 RFC 2573 SNMP Applications (SNMP-APP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
4.18 RFC 2574 User-based Security Model (USM) for version 3 of the 4.15 RFC 2574 User-based Security Model (USM) for version 3 of the
Simple Network Management Protocol (SNMPv3) (USM-SNMPV3) Simple Network Management Protocol (SNMPv3) (USM-SNMPV3)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
4.19 RFC 2575 View-based Access Control Model (VACM) for the Simple 4.16 RFC 2575 View-based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP) (VACM-SNMP) Network Management Protocol (SNMP) (VACM-SNMP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
4.20 RFC 2790 Host Resources MIB 4.17 RFC 2790 Host Resources MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
4.21 RFC 2863 The Interfaces Group MIB (INTERGRMIB) 4.18 RFC 2863 The Interfaces Group MIB (INTERGRMIB)
There are no IPv4 dependencies in this protocol. There is some There are no IPv4 dependencies in this specification. There is some
discussion in one OID about an interface performing a self test, but it discussion in one OID about an interface performing a self test, but it
is IP version independent. 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) (STD-MIBs)
There are no IPv4 dependencies in this protocol. 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 (BGP-MIB)
The use of BGP3 has been depreciated 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 (FDDI-MIB)
There are no IPv4 dependencies in this protocol. 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 (SNMP-LAPB)
There are no IPv4 dependencies in this protocol. 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 (SNMP-X.25)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.006 RFC 1414 Identification MIB (IDENT-MIB) 5.006 RFC 1414 Identification MIB (IDENT-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.007 RFC 1418 SNMP over OSI (SNMP-OSI) 5.007 RFC 1418 SNMP over OSI (SNMP-OSI)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.008 RFC 1419 SNMP over AppleTalk (SNMP-AT) 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.009 RFC 1420 SNMP over IPX (SNMP-IPX)
skipping to change at line 535 skipping to change at line 534
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 OID's can be defined to
support IPv6 addresses. support IPv6 addresses.
5.012 RFC 1471 The Definitions of Managed Objects for the Link 5.012 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 (PPP/LCPMIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.013 RFC 1472 The Definitions of Managed Objects for the Security 5.013 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 (PPP/SECMIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.014 RFC 1473 The Definitions of Managed Objects for the IP Network 5.014 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 (PPP/IPMIB)
Every OID in the MIB contain IPv4 addresses. A new MIB must be defined Every OID in the MIB contain IPv4 addresses. A new MIB must be defined
for OIDs for similar IPv6 addresses. for OIDs for similar IPv6 addresses.
5.015 RFC 1474 The Definitions of Managed Objects for the Bridge 5.015 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) (PPP/Bridge)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.016 RFC 1512 FDDI Management Information Base (FDDI-MIB) 5.016 RFC 1512 FDDI Management Information Base (FDDI-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.017 RFC 1513 Token Ring Extensions to the Remote Network 5.017 RFC 1513 Token Ring Extensions to the Remote Network
Monitoring MIB Monitoring MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.018 RFC 1515 Definitions of Managed Objects for IEEE 802.3 5.018 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. There are no IPv4 dependencies in this protocol.
5.019 RFC 1525 Definitions of Managed Objects for Source Routing 5.019 RFC 1525 Definitions of Managed Objects for Source Routing
Bridges (SRB-MIB) Bridges (SRB-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.020 RFC 1611 DNS Server MIB Extensions (DNS-S-MIB) 5.020 RFC 1611 DNS Server MIB Extensions (DNS-S-MIB)
The following OID is defined: The following OID is defined:
DnsServZoneEntry ::= DnsServZoneEntry ::=
SEQUENCE { SEQUENCE {
dnsServZoneName dnsServZoneName
DnsNameAsIndex, DnsNameAsIndex,
dnsServZoneClass dnsServZoneClass
skipping to change at line 794 skipping to change at line 793
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Host which sent the authoritative error, 0.0.0.0 if "Host which sent the authoritative error, 0.0.0.0 if
unknown." unknown."
::= { dnsResNCacheErrEntry 6 } ::= { dnsResNCacheErrEntry 6 }
5.022 RFC 1628 UPS Management Information Base (UPS-MIB) 5.022 RFC 1628 UPS Management Information Base (UPS-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.023 RFC 1666 Definitions of Managed Objects for SNA NAUs 5.023 RFC 1666 Definitions of Managed Objects for SNA NAUs
using SMIv2 SNANAU-MIB using SMIv2 SNANAU-MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.024 RFC 1696 Modem Management Information Base (MIB) using SMIv2 5.024 RFC 1696 Modem Management Information Base (MIB) using SMIv2
MODEM-MIB MODEM-MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.025 RFC 1697 Relational Database Management System (RDBMS) 5.025 RFC 1697 Relational Database Management System (RDBMS)
Management Information Base (MIB) using SMIv2 RDBMS-MIB Management Information Base (MIB) using SMIv2 RDBMS-MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.026 RFC 1742 AppleTalk Management Information Base II (AT-MIB) 5.026 RFC 1742 AppleTalk Management Information Base II (AT-MIB)
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,
skipping to change at line 865 skipping to change at line 864
::= { kipEntry 10 } ::= { kipEntry 10 }
5.027 RFC 1747 Definitions of Managed Objects for SNA Data Link 5.027 RFC 1747 Definitions of Managed Objects for SNA Data Link
Control (SDLC) using SMIv2 SDLCSMIv2 Control (SDLC) using SMIv2 SDLCSMIv2
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.028 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2 5.028 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2
802.5-SSR 802.5-SSR
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.029 RFC 1759 Printer MIB (Print-MIB) 5.029 RFC 1759 Printer MIB (Print-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.030 RFC 2006 The Definitions of Managed Objects for IP Mobility 5.030 RFC 2006 The Definitions of Managed Objects for IP Mobility
Support using SMIv2 (MOBILEIPMI) Support using SMIv2 (MOBILEIPMI)
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.031 RFC 2011 SNMPv2 Management Information Base for the Internet
Protocol using SMIv2 (MIB-IP) Protocol using SMIv2 (MIB-IP)
skipping to change at line 914 skipping to change at line 913
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.034 RFC 2020 IEEE 802.12 Interface MIB (802.12-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.035 RFC 2021 Remote Network Monitoring Management Information Base 5.035 RFC 2021 Remote Network Monitoring Management Information Base
Version 2 using SMIv2 (RMON-MIB) Version 2 using SMIv2 (RMON-MIB)
The following OIDs are defined: The following OIDs 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
skipping to change at line 1141 skipping to change at line 1140
-- 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 OIDs above (except trapDestProtocol) imply IPv4 addresses
but since they use a SYNTAX of OCTET STRING, they should work fine but since they use a SYNTAX of OCTET STRING, they should work fine
for IPv6 addresses. A new legitimate value of trapDestProtocol (i.e. for IPv6 addresses. A new legitimate value of trapDestProtocol (i.e.
SYNTAX addition of ipv6(3) should make this protocol IPv6 functional. SYNTAX addition of ipv6(3) should make this specification IPv6
functional.
5.036 RFC 2024 Definitions of Managed Objects for Data Link Switching 5.036 RFC 2024 Definitions of Managed Objects for Data Link Switching
using SMIv2 (DLSW-MIB) using SMIv2 (DLSW-MIB)
The following OIDs are defined: The following OIDs are defined:
TAddress ::= TEXTUAL-CONVENTION TAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a transport service address. "Denotes a transport service address.
skipping to change at line 1192 skipping to change at line 1192
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.038 RFC 2096 IP Forwarding Table MIB (TABLE-MIB) 5.038 RFC 2096 IP Forwarding Table MIB (TABLE-MIB)
This MIB defines many OIDs that are IPv4 dependent. It is expected This MIB defines many OIDs that are IPv4 dependent. It is expected
that another MIB for similar IPv6 addresses will be developed. that another MIB for similar IPv6 addresses will be developed.
5.039 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater 5.039 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater
Devices using SMIv2 802 (3-MIB) Devices using SMIv2 802 (3-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.040 RFC 2127 ISDN Management Information Base using SMIv2 5.040 RFC 2127 ISDN Management Information Base using SMIv2
(ISDN-MIB) (ISDN-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.041 RFC 2128 Dial Control Management Information Base using 5.041 RFC 2128 Dial Control Management Information Base using
SMIv2 (DC-MIB) SMIv2 (DC-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.042 RFC 2206 RSVP Management Information Base using SMIv2 5.042 RFC 2206 RSVP Management Information Base using SMIv2
(RSVP-MIB) (RSVP-MIB)
All OIDs in this MIB have options for both IPv4 and IPv6. There All OIDs in this MIB have options for both IPv4 and IPv6. There
are no IPv4 dependencies in this protocol. are no IPv4 dependencies in this specification.
5.043 RFC 2213 Integrated Services Management Information 5.043 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 protocol. dependencies in this specification.
5.044 RFC 2214 Integrated Services Management Information 5.044 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 protocol.
5.045 RFC 2232 Definitions of Managed Objects for DLUR using 5.045 RFC 2232 Definitions of Managed Objects for DLUR using
SMIv2 (DLUR-MIB) SMIv2 (DLUR-MIB)
There are no IPv4 dependencies in this protocol.
There are no IPv4 dependencies in this specification.
5.046 RFC 2238 Definitions of Managed Objects for HPR using 5.046 RFC 2238 Definitions of Managed Objects for HPR using
SMIv2 (HPR-MIB) SMIv2 (HPR-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.047 RFC 2266 Definitions of Managed Objects for IEEE 802.12 5.047 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 protocol.
5.048 RFC 2287 Definitions of System-Level Managed Objects for 5.048 RFC 2287 Definitions of System-Level Managed Objects for
Applications (SLM-APP) Applications (SLM-APP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
skipping to change at line 1267 skipping to change at line 1268
5.052 RFC 2454 IP Version 6 Management Information Base for 5.052 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 an IPv6 MIB and is not considered in this
discussion. discussion.
5.053 RFC 2455 Definitions of Managed Objects for APPN 5.053 RFC 2455 Definitions of Managed Objects for APPN
(APPN-MIB) (APPN-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.054 RFC 2456 Definitions of Managed Objects for APPN TRAPS 5.054 RFC 2456 Definitions of Managed Objects for APPN TRAPS
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.055 RFC 2457 Definitions of Managed Objects for Extended Border 5.055 RFC 2457 Definitions of Managed Objects for Extended Border
Node (EBN-MIB) Node (EBN-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.056 RFC 2465 Management Information Base for IP Version 6: 5.056 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 an IPv6 MIB and is not considered in this
discussion. discussion.
5.057 RFC 2466 Management Information Base for IP Version 6: 5.057 RFC 2466 Management Information Base for IP Version 6:
ICMPv6 Group (ICMPv6-MIB) ICMPv6 Group (ICMPv6-MIB)
This RFC documents an IPv6 MIB and is not considered in this This RFC documents an IPv6 MIB and is not considered in this
discussion. discussion.
5.058 RFC 2493 Textual Conventions for MIB Modules Using 5.058 RFC 2493 Textual Conventions for MIB Modules Using
Performance History Based on 15 Minute Intervals Performance History Based on 15 Minute Intervals
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.059 RFC 2494 Definitions of Managed Objects for the DS0 5.059 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 protocol.
5.060 RFC 2495 Definitions of Managed Objects for the DS1 E1 5.060 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 protocol.
5.061 RFC 2496 Definitions of Managed Object for the DS3/E3 5.061 RFC 2496 Definitions of Managed Object for the DS3/E3
Interface Type (DS3-E3-MIB) Interface Type (DS3-E3-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.062 RFC 2512 Accounting Information for ATM Networks 5.062 RFC 2512 Accounting Information for ATM Networks
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.063 RFC 2513 Managed Objects for Controlling the Collection 5.063 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 protocol.
skipping to change at line 1398 skipping to change at line 1399
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.067 RFC 2561 Base Definitions of Managed Objects for TN3270E 5.067 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 protocol 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.068 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) (TN2370E-RT)
Several OIDs rely on imports from RFC 2561 and therefore the Several OIDs rely on imports from RFC 2561 and therefore the
protocol is both IPv4 and IPv6 aware. protocol is both IPv4 and IPv6 aware.
5.069 RFC 2564 Application Management MIB (APP-MIB) 5.069 RFC 2564 Application Management MIB (APP-MIB)
skipping to change at line 1452 skipping to change at line 1453
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the agent-addr field of a Trap PDU which "The value of the agent-addr field of a Trap PDU which
is forwarded by a proxy forwarder application using is forwarded by a proxy forwarder application using
an SNMP version other than SNMPv1. The value of this an SNMP version other than SNMPv1. The value of this
object SHOULD contain the value of the agent-addr field object SHOULD contain the value of the agent-addr field
from the original Trap PDU as generated by an SNMPv1 from the original Trap PDU as generated by an SNMPv1
agent." agent."
::= { snmpCommunityMIBObjects 3 } ::= { snmpCommunityMIBObjects 3 }
This clearly points out a lack of IPv6 awareness in this protocol. This clearly points out a lack of IPv6 awareness in this specification.
5.071 RFC 2564 Application Management MIB (APP-MIB) 5.071 RFC 2564 Application Management MIB (APP-MIB)
The following OID is defined: The following OID is defined:
ApplTAddress ::= TEXTUAL-CONVENTION ApplTAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a transport service address. "Denotes a transport service address.
skipping to change at line 1499 skipping to change at line 1500
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the agent-addr field of a Trap PDU which "The value of the agent-addr field of a Trap PDU which
is forwarded by a proxy forwarder application using is forwarded by a proxy forwarder application using
an SNMP version other than SNMPv1. The value of this an SNMP version other than SNMPv1. The value of this
object SHOULD contain the value of the agent-addr field object SHOULD contain the value of the agent-addr field
from the original Trap PDU as generated by an SNMPv1 from the original Trap PDU as generated by an SNMPv1
agent." agent."
::= { snmpCommunityMIBObjects 3 } ::= { snmpCommunityMIBObjects 3 }
This clearly points out a lack of IPv6 awareness in this protocol. 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.073 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 OIDs described in this document assume the use of the
IPv4 only TOS header bits. It is therefore IPv4 only in nature and IPv4 only TOS header bits. It is therefore IPv4 only in nature and
will not support IPv6 interfaces. An updated MIB should be created. will not support IPv6 interfaces. An updated MIB should be created.
5.074 RFC 2591 Definitions of Managed Objects for Scheduling 5.074 RFC 2591 Definitions of Managed Objects for Scheduling
Management Operations Management Operations
skipping to change at line 1524 skipping to change at line 1525
of Management Script of Management Script
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.076 RFC 2594 Definitions of Managed Objects for WWW Services 5.076 RFC 2594 Definitions of Managed Objects for WWW Services
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.077 RFC 2605 Directory Server Monitoring MIB 5.077 RFC 2605 Directory Server Monitoring MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.078 RFC 2613 Remote Network Monitoring MIB Extensions for 5.078 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 protocol. There are no IPv4 dependencies in this specification.
5.079 RFC 2618 RADIUS Authentication Client MIB 5.079 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,
skipping to change at line 1622 skipping to change at line 1623
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.082 RFC 2662 Definitions of Managed Objects for the ADSL
Lines (MIB) Lines (MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.083 RFC 2665 Definitions of Managed Objects for the 5.083 RFC 2665 Definitions of Managed Objects for the
Ethernet-like Interface Types (MIB) Ethernet-like Interface Types (MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.084 RFC 2667 IP Tunnel MIB 5.084 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.085 RFC 2668 Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs) (MAU-MIB) Attachment Units (MAUs) (MAU-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.086 RFC 2669 DOCSIS Cable Device MIB Cable Device Management 5.086 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
skipping to change at line 1701 skipping to change at line 1702
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. IPv6 OIDs should be defined.
5.088 RFC 2674 Definitions of Managed Objects for Bridges with 5.088 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 (MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.089 RFC 2677 Definitions of Managed Objects for the NBMA Next 5.089 RFC 2677 Definitions of Managed Objects for the NBMA Next
Hop Resolution Protocol (NHRP) (NHRP-MIB) Hop Resolution Protocol (NHRP) (NHRP-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.90 RFC 2720 Traffic Flow Measurement: Meter MIB 5.90 RFC 2720 Traffic Flow Measurement: Meter MIB
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.091 RFC 2725 Routing Policy System Security 5.091 RFC 2725 Routing Policy System Security
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.092 RFC 2726 PGP Authentication for RIPE Database Updates 5.092 RFC 2726 PGP Authentication for RIPE Database Updates
skipping to change at line 1779 skipping to change at line 1780
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.100 RFC 2788 Network Services Monitoring MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.101 RFC 2789 Mail Monitoring MIB 5.101 RFC 2789 Mail Monitoring MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.102 RFC 2837 Definitions of Managed Objects for the Fabric Element 5.102 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 protocol.
5.103 RFC 2851 Textual Conventions for Internet Network Addresses 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 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 use multiple versions of IP. Currently IPv4 and IPv6 addressing
skipping to change at line 1806 skipping to change at line 1807
set of IP address abstractions. set of IP address abstractions.
5.104 RFC 2856 Textual Conventions for Additional High Capacity 5.104 RFC 2856 Textual Conventions for Additional High Capacity
Data Types (SNMP) Data Types (SNMP)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
5.105 RFC 2864 The Inverted Stack Table Extension to the Interfaces 5.105 RFC 2864 The Inverted Stack Table Extension to the Interfaces
Group MIB Group MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.106 RFC 2895 Remote Network Monitoring MIB Protocol Identifier 5.106 RFC 2895 Remote Network Monitoring MIB Protocol Identifier
Reference (RMON-MIB) Reference (RMON-MIB)
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.107 RFC 2925 Definitions of Managed Objects for Remote 5.107 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
skipping to change at line 1855 skipping to change at line 1856
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. There is clearly an assumption of IPv4 header sizes.
5.108 RFC 2932 IPv4 Multicast Routing MIB 5.108 RFC 2932 IPv4 Multicast Routing MIB
This protocol 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.109 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.110 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.111 RFC 2954 Definitions of Managed Objects for Frame
Relay Service (FR-MIB) Relay Service (FR-MIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.112 RFC 2955 Definitions of Managed Objects for Monitoring 5.112 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 protocol.
5.113 RFC 2959 Real-Time Transport Protocol Management 5.113 RFC 2959 Real-Time Transport Protocol Management
Information Base Information Base
skipping to change at line 1912 skipping to change at line 1913
sec. 3. The transport service is identified by rtpSessionDomain. sec. 3. The transport service is identified by rtpSessionDomain.
For snmpUDPDomain, this is an IP address and even-numbered UDP For snmpUDPDomain, this is an IP address and even-numbered UDP
Port with the RTCP being sent on the next higher odd-numbered Port with the RTCP being sent on the next higher odd-numbered
port, see RFC 1889, sec. 5." port, see RFC 1889, sec. 5."
::= { rtpSessionEntry 3 } ::= { rtpSessionEntry 3 }
There are a total of 8 instances of this. There are a total of 8 instances of this.
5.114 RFC 2981 Event MIB 5.114 RFC 2981 Event MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.115 RFC 2982 Distributed Management Expression MIB 5.115 RFC 2982 Distributed Management Expression MIB
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
5.116 RFC 3014 Notification Log MIB 5.116 RFC 3014 Notification Log MIB
This document contains OIDs that are IPv4 specific: This document contains OIDs that are IPv4 specific:
nlmLogVariableIpAddressVal OBJECT-TYPE nlmLogVariableIpAddressVal OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 1989 skipping to change at line 1990
6.02 RFC 1224 Techniques for managing asynchronously generated 6.02 RFC 1224 Techniques for managing asynchronously generated
alerts (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) (CLNS-MIB)
There are no IPv4 dependencies in this protocol. 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 (SNMP-DPI)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.05 RFC 1792 TCP/IPX Connection Mib Specification (TCP/IPXMIB) 6.05 RFC 1792 TCP/IPX Connection Mib Specification (TCP/IPXMIB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.06 RFC 1901 Introduction to Community-based SNMPv2 (SNMPV2CB) 6.06 RFC 1901 Introduction to Community-based SNMPv2 (SNMPV2CB)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.07 RFC 1909 An Administrative Infrastructure for SNMPv2 6.07 RFC 1909 An Administrative Infrastructure for SNMPv2
(SNMPV2AI) (SNMPV2AI)
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this protocol.
6.08 RFC 1910 User-based Security Model for SNMPv2 (SNMPV2SM) 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.09 RFC 2593 Script MIB Extensibility Protocol Version 1.0
There are no IPv4 dependencies in this protocol. There are no IPv4 dependencies in this specification.
6.10 RFC 2724 RTFM: New Attributes for Traffic Flow Measurement 6.10 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.11 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 protocol is both IPv4 and IPv6 aware and needs no changes.
skipping to change at line 2044 skipping to change at line 2045
6.14 RFC 2934 Protocol Independent Multicast MIB for IPv4 6.14 RFC 2934 Protocol Independent Multicast MIB for IPv4
This document is specific to IPv4. This document is specific to IPv4.
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 3 of 7 or 42.86% Standards 6 of 10 or 60.00%
Draft Standards 6 of 21 or 28.57% 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 15 Simple Network Management Protocol (RFCs 1157, 1155, 1213)
The limitations identified have been addressed. The limitations identified have been addressed; RFC 1157 is HISTORIC,
RFC1155 is obsoleted by RFC 2578-2580, and RFC1213 has been split to
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-09.txt).
7.2.2 SMDS MIB (RFC 1694) 7.2.2 SMDS MIB (RFC 1694)
skipping to change at line 2108 skipping to change at line 2111
This problem has not been addressed. A new specification should This problem has not been addressed. A new specification should
be created. be created.
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. must be defined.
7.3.03 DNS Server MIB (RFC 1611) 7.3.03 DNS Server MIB (RFC 1611)
The problems have not been addressed and a new MIB must be defined. This document is HISTORIC and no action is required.
7.3.04 DNS Resolver MIB (RFC 1612) 7.3.04 DNS Resolver MIB (RFC 1612)
The problems have not been addressed and a new MIB must be defined. This document is HISTORIC and no action is required.
7.3.05 Appletalk MIB (RFC 1742) 7.3.05 Appletalk MIB (RFC 1742)
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.06 The Definitions of Managed Objects for IP Mobility 7.3.06 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-00.txt)
skipping to change at line 2179 skipping to change at line 2182
7.3.16 TN3270 MIB (RFC 2562) 7.3.16 TN3270 MIB (RFC 2562)
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.17 Application MIB (RFC 2564) 7.3.17 Application MIB (RFC 2564)
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.
One possible solution is to use RFC 3419 TCs.
7.3.18 Coexistence of SNMP v1, v2, & v3 (RFC 2576) 7.3.18 Coexistence of SNMP v1, v2, & v3 (RFC 2576)
There are no real issues that can be resolved. There are no real issues that can be resolved.
7.3.19 Definitions of Managed Objects for APPN/HPR in IP Networks 7.3.19 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.
skipping to change at line 2263 skipping to change at line 2267
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
and 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 of [1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey
IPv4 Addresses in Currently Deployed IETF Standards", of IPv4 Addresses in Currently Deployed IETF Standards",
draft-ietf-v6ops-ipv4survey-intro-01.txt IETF work in progress, draft-ietf-v6ops-ipv4survey-intro-02.txt IETF work in progress,
June 2003 August 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/