draft-ietf-v6ops-ipv4survey-ops-05.txt   rfc3796.txt 
Network Working Group Philip J. Nesser II
draft-ietf-v6ops-ipv4survey-ops-05.txt Nesser & Nesser Consulting
Internet Draft Andreas Bergstrom (Ed.)
Ostfold University College
December 2003
Expires May 2004
Survey of IPv4 Addresses in Currently Deployed Network Working Group P. Nesser, II
IETF Operations & Management Area Standards Request for Comments: 3796 Nesser & Nesser Consulting
Category: Informational A. Bergstrom, Ed.
Ostfold University College
June 2004
This document is an Internet-Draft and is in full conformance with Survey of IPv4 Addresses in Currently Deployed IETF
all provisions of Section 10 of RFC2026. Operations & Management Area Standards Track and Experimental Documents
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering This memo provides information for the Internet community. It does
Task Force (IETF), its areas, and its working groups. Note that other not specify an Internet standard of any kind. Distribution of this
groups may also distribute working documents as Internet-Drafts. memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents at
any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2004).
http://www.ietf.org/shadow.html.
Abstract Abstract
This document seeks to document all usage of IPv4 addresses in currently This document seeks to record all usage of IPv4 addresses in
deployed IETF Operations & Management Area documented standards. In currently deployed IETF Operations & Management Area accepted
order to successfully transition from an all IPv4 Internet to an all standards. In order to successfully transition from an all IPv4
IPv6 Internet, many interim steps will be taken. One of these steps is Internet to an all IPv6 Internet, many interim steps will be taken.
the evolution of current protocols that have IPv4 dependencies. It is One of these steps is the evolution of current protocols that have
hoped that these protocols (and their implementations) will be IPv4 dependencies. It is hoped that these protocols (and their
redesigned to be network address independent, but failing that will at implementations) will be redesigned to be network address
least dually support IPv4 and IPv6. To this end, all Standards (Full, independent, but failing that will at least dually support IPv4 and
Draft, and Proposed) as well as Experimental RFCs will be surveyed and IPv6. To this end, all Standards (Full, Draft, and Proposed), as
any dependencies will be documented. well as Experimental RFCs, will be surveyed and any dependencies will
be documented.
Table of Contents Table of Contents
1. Introduction 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Document Organisation 2. Document Organization. . . . . . . . . . . . . . . . . . . . . 2
3. Full Standards 3. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Draft Standards 4. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . 5
5. Proposed Standards 5. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . 9
6. Experimental RFCs 6. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 34
7. Summary of Results 7. Summary of Results . . . . . . . . . . . . . . . . . . . . . . 36
7.1 Standards 7.1. Standards. . . . . . . . . . . . . . . . . . . . . . . . 36
7.2 Draft Standards 7.2. Draft Standards. . . . . . . . . . . . . . . . . . . . . 36
7.3 Proposed Standards 7.4 Experimental RFCs 7.3. Proposed Standards . . . . . . . . . . . . . . . . . . . 37
8. Security Consideration 7.4. Experimental RFCs. . . . . . . . . . . . . . . . . . . . 40
9. Acknowledgements 8. Security Considerations. . . . . . . . . . . . . . . . . . . . 40
10. References 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 40
11. Authors' Addresses 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12. Intellectual Property Statement 10.1. Normative Reference. . . . . . . . . . . . . . . . . . . 40
13. Full Copyright Statement 10.2. Informative References . . . . . . . . . . . . . . . . . 41
11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 42
12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 43
1.0 Introduction 1. Introduction
This document is part of a document set aiming to document all usage of This document is part of a set aiming to record all usage of IPv4
IPv4 addresses in IETF standards. In an effort to have the information addresses in IETF standards. In an effort to have the information in
in a manageable form, it has been broken into 7 documents conforming a manageable form, it has been broken into 7 documents conforming to
to the current IETF areas (Application, Internet, Management & the current IETF areas (Application, Internet, Operations &
Operations, Routing, Security, Sub-IP and Transport). Management, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the introduction [1]. For a full introduction, please see the introduction [1].
2.0 Document Organization 2. 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,
and Proposed Standards, and Experimental RFCs. Each RFC is discussed in Draft, and Proposed Standards, and Experimental RFCs. Each RFC is
its turn starting with RFC 1 and ending with (around) RFC 3100. discussed in its turn starting with RFC 1 and ending with (around)
The comments for each RFC are "raw" in nature. That is, each RFC is RFC 3100. The comments for each RFC are "raw" in nature. That is,
discussed in a vacuum and problems or issues discussed do not each RFC is discussed in a vacuum and problems or issues discussed do
"look ahead" to see if the problems have already been fixed. not "look ahead" to see if 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,
6. It is here that all of the results are considered as a whole and the and 6. It is here that all of the results are considered as a whole
problems that have been resolved in later RFCs are correlated. and the problems that have been resolved in later RFCs are
correlated.
3.0 Full Standards 3. 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 1155 Structure of Management Information 3.1. 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.
is represented as an OCTET STRING of length 4, in network byte-order. It 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
the document. of the document.
3.2 RFC 1212 Concise MIB definitions 3.2. RFC 1212 Concise MIB definitions
In section 4.1.6 IpAddress is defined as: In section 4.1.6 IpAddress is defined as:
(6) IpAddress-valued: 4 sub-identifiers, in the familiar (6) IpAddress-valued: 4 sub-identifiers, in the familiar
a.b.c.d notation. a.b.c.d notation.
3.3 RFC 1213 Management Information Base 3.3. RFC 1213 Management Information Base
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. The particular object groups that are affected to enumerate here. The particular object groups that are affected
are the IP group, the ICMP group, the TCP group, the UDP group, are the IP group, the ICMP group, the TCP group, the UDP group, and
and the EGP group. the EGP group.
3.4 RFC 2578 Structure of Management Information Version 2 (SMIv2) 3.4. RFC 2578 Structure of Management Information Version 2 (SMIv2)
Section 7.1.5 defines the IpAddress data type: 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
Network addresses should be represented using an invocation of the reasons. Network addresses should be represented using an
TEXTUAL-CONVENTION macro. invocation of the 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
the replacement TEXTUAL-CONVENTION definitions. the replacement TEXTUAL-CONVENTION definitions.
3.5 RFC 2579 Textual Conventions for SMIv2 3.5. RFC 2579 Textual Conventions for SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.6 RFC 2580 Conformance Statements for SMIv2 3.6. RFC 2580 Conformance Statements 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.7. RFC 2819 Remote Network Monitoring Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.8 RFC 3411 An Architecture for Describing SNMP Management Frameworks 3.8. RFC 3411 An Architecture for Describing SNMP Management Frameworks
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.9 RFC 3412 Message Processing and Dispatching for the Simple Network 3.9. RFC 3412 Message Processing and Dispatching for the Simple Network
Management Protocol (SNMP) Management Protocol (SNMP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.10 RFC 3413 SNMP Applications 3.10. RFC 3413 SNMP Applications
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.11 RFC 3414 User-based Security Model (USM) for version 3 of the 3.11. RFC 3414 User-based Security Model (USM) for version 3 of the
Simple Network Management Protocol (SNMPv3) Simple Network Management Protocol (SNMPv3)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.12 RFC 3415 View-based Access Control Model (VACM) for the Simple 3.12. RFC 3415 View-based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP) Network Management Protocol (SNMP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
3.13 RFC 3416 Protocol Operations for Version 2 of the Simple Network 3.13. RFC 3416 Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMP) 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 objects 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.14 RFC 3417 Transport Mappings for Version 2 of the Simple Network 3.14. RFC 3417 Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMP) Management Protocol (SNMP)
Section 2 Definitions contains the following 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 uses 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.15 RFC 3418 Management Information Base for Version 2 of the Simple 3.15. RFC 3418 Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMP) 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. 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
quite mature and widely used. usually quite mature and widely used.
4.01 RFC 1493 Definitions of Managed Objects for Bridges 4.1. 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 4.2. 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.3. RFC 1657 Definitions of Managed Objects for the Fourth
Version of the Border Gateway Protocol (BGP-4) using SMIv2 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
system and therefore contain many objects that are limited by the routing system and therefore contain many objects that are limited by
IpAddress 32-bit value defined in MIB2. Clearly the values of this MIB the IpAddress 32-bit value defined in MIB2. Clearly the values of
are limited to IPv4 addresses. No update is needed, although a new MIB this MIB are limited to IPv4 addresses. No update is needed,
should be defined for BGP4+ to allow management of IPv6 addresses and although a new MIB should be defined for BGP4+ to allow management of
routes. IPv6 addresses and routes.
4.04 RFC 1658 Definitions of Managed Objects for Character Stream 4.4. 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.5. RFC 1659 Definitions of Managed Objects for RS-232-like Hardware
Devices using SMIv2 Devices using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.06 RFC 1660 Definitions of Managed Objects for Parallel-printer-like 4.6. 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 specification. There are no IPv4 dependencies in this specification.
4.07 RFC 1694 Definitions of Managed Objects for SMDS Interfaces using 4.7. RFC 1694 Definitions of Managed Objects for SMDS Interfaces using
SMIv2 SMIv2
This MIB module 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
skipping to change at line 339 skipping to change at page 8, line 31
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 object definitions are intended for IPv4 addresses, a Although these object definitions are intended for IPv4 addresses, a
similar MIB can be defined for IPv6 addressing. similar MIB can be defined for IPv6 addressing.
4.08 RFC 1724 RIP Version 2 MIB Extension 4.8. RFC 1724 RIP Version 2 MIB Extension
As might be expected, this RFC is filled with IPv4 dependencies since As expected, this RFC is filled with IPv4 dependencies since it
it defines a MIB module for an IPv4-only routing protocol. A new MIB defines a MIB module for an IPv4-only routing protocol. A new MIB
for RIPng is required. for RIPng is required.
4.09 RFC 1748 IEEE 802.5 MIB using SMIv2 4.9. 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 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
addresses a new MIB is required to support a new version of OSPF that IPv4 addresses, a new MIB is required to support a new version of
is IPv6 aware. OSPF that 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 Using SMIv2
This specification has several examples of how IPv4 addresses might be This specification has several examples of how IPv4 addresses might
mapped to Frame Relay DLCIs. Other than those examples there are no be mapped to Frame Relay DLCIs. Other than those examples there are
IPv4 dependencies in this specification. no IPv4 dependencies in this specification.
4.12 RFC 2790 Host Resources MIB 4.12. RFC 2790 Host Resources MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.13 RFC 2863 The Interfaces Group MIB 4.13. RFC 2863 The Interfaces Group MIB
There are no IPv4 dependencies in this specification. There is some There are no IPv4 dependencies in this specification. There is some
discussion in one object definition about an interface performing a discussion in one object definition about an interface performing a
self test, but the object itself is IP version independent. self test, but the object itself is IP version independent.
4.14 RFC 3592 Definitions of Managed Objects for the Synchronous Optical 4.14. RFC 3592 Definitions of Managed Objects for the Synchronous
Network/Synchronous Digital Hierarchy (SONET/SDH) Optical Network/Synchronous Digital Hierarchy (SONET/SDH)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
4.15 RFC 3593 Textual Conventions for MIB Modules Using Performance 4.15. RFC 3593 Textual Conventions for MIB Modules Using Performance
History Based on 15 Minute Intervals. History Based on 15 Minute Intervals
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.0 Proposed Standards 5. 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,
are never implemented or advanced in the IETF standards process. They Proposed are never implemented or advanced in the IETF standards
therefore are often just proposed ideas that are presented to the process. They therefore are often just proposed ideas that are
Internet community. Sometimes flaws are exposed or they are one of presented to the Internet community. Sometimes flaws are exposed or
many competing solutions to problems. In these later cases, no they are one of many competing solutions to problems. In these later
discussion is presented as it would not serve the purpose of this cases, no discussion is presented as it would not serve the purpose
discussion. of this discussion.
5.001 RFC 1239 Reassignment of experimental MIBs to standard MIBs 5.1. RFC 1239 Reassignment of experimental MIBs to standard 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.2. RFC 1269 Definitions of Managed Objects for the Border
Protocol: Version 3 Gateway 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 5.3. 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 5.4. 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 5.5. 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 5.6. 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 5.7. RFC 1418 SNMP over OSI
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.008 RFC 1419 SNMP over AppleTalk 5.8. RFC 1419 SNMP over AppleTalk
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.009 RFC 1420 SNMP over IPX 5.9. RFC 1420 SNMP over IPX
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.010 RFC 1461 SNMP MIB extension for Multiprotocol Interconnect 5.10. RFC 1461 SNMP MIB extension for Multiprotocol Interconnect
over X.25 over X.25
The following objects 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 512 skipping to change at page 12, line 17
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 objects can be defined to Updated values of the first byte of these objects can be defined to
support IPv6 addresses. support IPv6 addresses.
5.011 RFC 1471 The Definitions of Managed Objects for the Link 5.11. RFC 1471 The Definitions of Managed Objects for the Link
Control Protocol of the Point-to-Point Protocol 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.012 RFC 1472 The Definitions of Managed Objects for the Security 5.12. RFC 1472 The Definitions of Managed Objects for the Security
Protocols of the Point-to-Point Protocol Protocols 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 1473 The Definitions of Managed Objects for the IP Network 5.13. RFC 1473 The Definitions of Managed Objects for the IP Network
Control Protocol of the Point-to-Point Protocol Control Protocol of the Point-to-Point Protocol
This MIB module is targeted specifically at IPv4 over PPP. A new This MIB module is targeted specifically at IPv4 over PPP. A new MIB
MIB moduld would need to be defined to support IPv6 over PPP. module would need to be defined to support IPv6 over PPP.
5.014 RFC 1474 The Definitions of Managed Objects for the Bridge 5.14. 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
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.015 RFC 1512 FDDI Management Information Base 5.15. RFC 1512 FDDI Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.016 RFC 1513 Token Ring Extensions to the Remote Network 5.16. 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.017 RFC 1525 Definitions of Managed Objects for Source Routing 5.17. RFC 1525 Definitions of Managed Objects for Source Routing
Bridges Bridges
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.018 RFC 1628 UPS Management Information Base 5.18. RFC 1628 UPS Management Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.019 RFC 1666 Definitions of Managed Objects for SNA NAUs 5.19. RFC 1666 Definitions of Managed Objects for SNA NAUs using SMIv2
using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.020 RFC 1696 Modem Management Information Base (MIB) using SMIv2 5.20. RFC 1696 Modem Management Information Base (MIB) using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.021 RFC 1697 Relational Database Management System (RDBMS) 5.21. RFC 1697 Relational Database Management System (RDBMS)
Management Information Base (MIB) using SMIv2 Management Information Base (MIB) using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.022 RFC 1742 AppleTalk Management Information Base II 5.22. RFC 1742 AppleTalk Management Information Base II
The following OIDs are defined: The following objects 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,
kipType INTEGER, kipType INTEGER,
kipState INTEGER, kipState INTEGER,
skipping to change at line 611 skipping to change at page 14, line 19
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.023 RFC 1747 Definitions of Managed Objects for SNA Data Link 5.23. RFC 1747 Definitions of Managed Objects for SNA Data Link
Control (SDLC) using SMIv2 Control (SDLC) using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.024 RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2 5.24. RFC 1749 IEEE 802.5 Station Source Routing MIB using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.025 RFC 1759 Printer MIB 5.25. RFC 1759 Printer MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.026 RFC 2006 The Definitions of Managed Objects for IP Mobility 5.26. RFC 2006 The Definitions of Managed Objects for IP Mobility
Support using SMIv2 Support using SMIv2
This document defines a MIB for the Mobile IPv4. Without enumeration, This document defines a MIB for the Mobile IPv4. Without
let it be stated that a new MIB for IPv6 Mobility is required. enumeration, let it be stated that a new MIB for IPv6 Mobility is
required.
5.027 RFC 2011 SNMPv2 Management Information Base for the Internet 5.27. RFC 2011 SNMPv2 Management Information Base for the Internet
Protocol using SMIv2 Protocol using SMIv2
Approximately 1/3 of the objects defined in this document are Approximately 1/3 of the objects defined in this document are IPv4-
IPv4-dependent. New objects need to be defined to support IPv6. dependent. New objects need to be defined to support IPv6.
5.028 RFC 2012 SNMPv2 Management Information Base for the 5.28. RFC 2012 SNMPv2 Management Information Base for the
Transmission Control Protocol using SMIv2 Transmission Control Protocol using SMIv2
A number of object definitions in this MIB assumes IPv4 addresses, as A number of object definitions in this MIB assumes IPv4 addresses, as
is noted in 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.
three modules use the IpAddress type defined as an OCTET STRING of These three modules use the IpAddress type defined as an OCTET
length 4 to represent the IPv4 32-bit internet addresses. (See RFC STRING of length 4 to represent the IPv4 32-bit internet
1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 addresses. (See RFC 1902, SMI for SNMPv2.) They do not support
internet addresses. the new 128-bit IPv6 internet addresses.
5.029 RFC 2013 SNMPv2 Management Information Base for the User 5.29. RFC 2013 SNMPv2 Management Information Base for the User
Datagram Protocol using SMIv2 Datagram 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.
three modules use the IpAddress type defined as an OCTET STRING of These three modules use the IpAddress type defined as an OCTET
length 4 to represent the IPv4 32-bit internet addresses. (See RFC STRING of length 4 to represent the IPv4 32-bit internet
1902, SMI for SNMPv2.) They do not support the new 128-bit IPv6 addresses. (See RFC 1902, SMI for SNMPv2.) They do not support
internet addresses. the new 128-bit IPv6 internet addresses.
5.030 RFC 2020 IEEE 802.12 Interface MIB 5.30. RFC 2020 IEEE 802.12 Interface MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.031 RFC 2021 Remote Network Monitoring Management Information Base 5.31. RFC 2021 Remote Network Monitoring Management Information Base
Version 2 using SMIv2 Version 2 using SMIv2
The following objects 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.
skipping to change at line 810 skipping to change at page 18, line 33
DESCRIPTION DESCRIPTION
"The network layer address of the destination host in this "The network layer address of the destination host in this
conversation. conversation.
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
by the associated nlMatrixTopNProtocolDirLocalIndex. by the associated nlMatrixTopNProtocolDirLocalIndex.
For example, if the nlMatrixTopNProtocolDirLocalIndex For example, if the nlMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the ip
in network byte order." address, in network byte order."
::= { nlMatrixTopNEntry 4 } ::= { nlMatrixTopNEntry 4 }
alMatrixTopNSourceAddress OBJECT-TYPE alMatrixTopNSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the source host in this "The network layer address of the source host in this
conversation. conversation.
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
by the associated alMatrixTopNProtocolDirLocalIndex. by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the
in network byte order." ip address, in network byte order."
::= { alMatrixTopNEntry 3 } ::= { alMatrixTopNEntry 3 }
alMatrixTopNDestAddress OBJECT-TYPE alMatrixTopNDestAddress OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network layer address of the destination host in this "The network layer address of the destination host in this
conversation. conversation.
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
by the associated alMatrixTopNProtocolDirLocalIndex. by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip address, length octet of 4, followed by the 4 octets of the ip
in network byte order." address, in network byte order."
::= { alMatrixTopNEntry 4 } ::= { alMatrixTopNEntry 4 }
trapDestProtocol OBJECT-TYPE trapDestProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ip(1), ip(1),
ipx(2) ipx(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 891 skipping to change at page 20, line 18
-- 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 object definitions above (except trapDestProtocol) mention All of the object definitions above (except trapDestProtocol) mention
only IPv4 addresses but since they use a SYNTAX of OCTET STRING, they only IPv4 addresses. However, since they use a SYNTAX of OCTET
should work fine for IPv6 addresses. A new legitimate value of STRING, they should work fine for IPv6 addresses. A new legitimate
trapDestProtocol (i.e. SYNTAX addition of ipv6(3) should make this value of trapDestProtocol (i.e., SYNTAX addition of ipv6(3) should
specification functional for IPv6. make this specification functional for IPv6.
5.032 RFC 2024 Definitions of Managed Objects for Data Link Switching 5.32. RFC 2024 Definitions of Managed Objects for Data Link Switching
using SMIv2 using SMIv2
The following textual conventions 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."
skipping to change at line 923 skipping to change at page 21, line 4
-- octets contents encoding -- octets contents encoding
-- 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 object definitions that use a SYNTAX of Additionally there are many object definitions that use a SYNTAX of
TAddress within the document. Interestingly the SYNTAX for TAddress TAddress within the document. Interestingly the SYNTAX for TAddress
is an OCTET string of up to 256 characters. It could easily is an OCTET string of up to 256 characters. It could easily
accommodate a similar hybrid format for IPv6 addresses. accommodate a similar hybrid format for IPv6 addresses.
A new OID to enhance functionality for DlswTCPAddress could be added A new OID to enhance functionality for DlswTCPAddress could be added
to support IPv6 addresses. to support IPv6 addresses.
5.033 RFC 2051 Definitions of Managed Objects for APPC using SMIv2 5.33. RFC 2051 Definitions of Managed Objects for APPC using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.034 RFC 2096 IP Forwarding Table MIB 5.34. RFC 2096 IP Forwarding Table MIB
The MIB module's main conceptual table ipCidrRouteTable uses IPv4 The MIB module's main conceptual table ipCidrRouteTable uses IPv4
addresses as index objects and is therefore incapable of addresses as index objects and is therefore incapable of representing
representing an IPv6 forwarding information base. A new an IPv6 forwarding information base. A new conceptual table needs to
conceptual table needs to be defined to support IPv6 addresses. be defined to support IPv6 addresses.
5.035 RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater 5.35. RFC 2108 Definitions of Managed Objects for IEEE 802.3 Repeater
Devices using SMIv2 802 Devices using SMIv2 802
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.036 RFC 2127 ISDN Management Information Base using SMIv2 5.36. RFC 2127 ISDN Management Information Base using SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.037 RFC 2128 Dial Control Management Information Base using 5.37. RFC 2128 Dial Control Management Information Base using
SMIv2 SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.038 RFC 2206 RSVP Management Information Base using SMIv2 5.38. RFC 2206 RSVP Management Information Base using SMIv2
All of the relevant object definitions in this MIB have options for All of the relevant object definitions in this MIB have options for
both IPv4 and IPv6. There are no IPv4 dependencies in this both IPv4 and IPv6. There are no IPv4 dependencies in this
specification. specification.
5.039 RFC 2213 Integrated Services Management Information 5.39. 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
dependencies in this specification. in this specification.
5.040 RFC 2214 Integrated Services Management Information 5.40. 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 specification. There are no IPv4 dependencies in this specification.
5.041 RFC 2232 Definitions of Managed Objects for DLUR using 5.41. RFC 2232 Definitions of Managed Objects for DLUR using SMIv2
SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.042 RFC 2238 Definitions of Managed Objects for HPR using 5.42. RFC 2238 Definitions of Managed Objects for HPR using SMIv2
SMIv2
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.043 RFC 2266 Definitions of Managed Objects for IEEE 802.12 5.43. RFC 2266 Definitions of Managed Objects for IEEE 802.12
Repeater Devices Repeater Devices
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.044 RFC 2287 Definitions of System-Level Managed Objects for 5.44. RFC 2287 Definitions of System-Level Managed Objects for
Applications Applications
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.045 RFC 2320 Definitions of Managed Objects for Classical IP 5.45. RFC 2320 Definitions of Managed Objects for Classical IP
and ARP Over ATM Using SMIv2 (IPOA-MIB) and ARP Over ATM Using SMIv2 (IPOA-MIB)
This MIB is wholly dependent on IPv4. A new MIB for IPv6 is This MIB is wholly dependent on IPv4. A new MIB for IPv6 is required
required to provide the same functionality. to provide the same functionality.
5.046 RFC 2417 Definitions of Managed Objects for Multicast 5.46. 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
This MIB is wholly dependent on IPv4. A new MIB for IPv6 is This MIB is wholly dependent on IPv4. A new MIB for IPv6 is required
required to provide the same functionality. to provide the same functionality.
5.047 RFC 2452 IP Version 6 Management Information Base for the 5.47. RFC 2452 IP Version 6 Management Information Base for the
Transmission Control Protocol Transmission Control Protocol
This RFC documents a soon to be obsoleted IPv6 MIB and is not This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion. considered in this discussion.
5.048 RFC 2454 IP Version 6 Management Information Base for 5.48. RFC 2454 IP Version 6 Management Information Base for
the User Datagram Protocol the User Datagram Protocol
This RFC documents a soon to be obsoleted IPv6 MIB and is not This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion. considered in this discussion.
5.049 RFC 2455 Definitions of Managed Objects for APPN 5.49. RFC 2455 Definitions of Managed Objects for APPN
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.050 RFC 2456 Definitions of Managed Objects for APPN TRAPS 5.50. RFC 2456 Definitions of Managed Objects for APPN TRAPS
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.051 RFC 2457 Definitions of Managed Objects for Extended Border 5.51. RFC 2457 Definitions of Managed Objects for Extended Border
Node Node
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.052 RFC 2465 Management Information Base for IP Version 6: 5.52. RFC 2465 Management Information Base for IP Version 6:
Textual Conventions and General Group Textual Conventions and General Group
This RFC documents a soon to be obsolted IPv6 MIB and is not This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion. considered in this discussion.
5.053 RFC 2466 Management Information Base for IP Version 6: 5.53. RFC 2466 Management Information Base for IP Version 6:
ICMPv6 Group ICMPv6 Group
This RFC documents a soon to be obsoleted IPv6 MIB and is not This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion. considered in this discussion.
5.054 RFC 2494 Definitions of Managed Objects for the DS0 5.54. 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 specification. There are no IPv4 dependencies in this specification.
5.055 RFC 2495 Definitions of Managed Objects for the DS1, E1, 5.55. 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 specification. There are no IPv4 dependencies in this specification.
5.056 RFC 2496 Definitions of Managed Object for the DS3/E3 5.56. RFC 2496 Definitions of Managed Object for the DS3/E3
Interface Type Interface Type
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.057 RFC 2512 Accounting Information for ATM Networks 5.57. RFC 2512 Accounting Information for ATM Networks
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.058 RFC 2513 Managed Objects for Controlling the Collection 5.58. RFC 2513 Managed Objects for Controlling the Collection
and Storage of Accounting Information for Connection- and Storage of Accounting Information for
Oriented Networks Connection-Oriented Networks
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.059 RFC 2514 Definitions of Textual Conventions and 5.59. RFC 2514 Definitions of Textual Conventions and
OBJECT-IDENTITIES for ATM Management OBJECT-IDENTITIES for ATM Management
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.060 RFC 2515 Definitions of Managed Objects for ATM 5.60. RFC 2515 Definitions of Managed Objects for ATM Management
Management
This MIB defines the following objects: 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,
skipping to change at line 1134 skipping to change at page 25, line 26
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 revision of this MIB module should define Clearly a subsequent revision of this MIB module should define
equivalent IPv6 objects. equivalent IPv6 objects.
5.061 RFC 2561 Base Definitions of Managed Objects for TN3270E 5.61. 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.062 RFC 2562 Definitions of Protocol and Managed Objects for 5.62. RFC 2562 Definitions of Protocol and Managed Objects for
TN3270E Response Time Collection Using SMIv2 TN3270E Response Time Collection Using SMIv2
This MIB module inherits IP version-independence by virtue of This MIB module inherits IP version-independence by virtue of
importing the appropriate definitions from RFC 2561. importing the appropriate definitions from RFC 2561.
5.063 RFC 2564 Application Management MIB 5.63. RFC 2564 Application Management MIB
The following textual convention 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 TC should be defined to handle IPv6 addresses. A new TC should be defined to handle IPv6 addresses.
5.064 RFC 2584 Definitions of Managed Objects for APPN/HPR in 5.64. RFC 2584 Definitions of Managed Objects for APPN/HPR in
IP Networks IP Networks
Many of the object definitions described in this document assume the Many of the object definitions described in this document assume the
use of the IPv4 only TOS header bits. It is therefore IPv4-only in use of the IPv4 only TOS header bits. It is therefore IPv4-only in
nature and will not support IPv6. nature and will not support IPv6.
5.065 RFC 2594 Definitions of Managed Objects for WWW Services 5.65. RFC 2594 Definitions of Managed Objects for WWW Services
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.066 RFC 2605 Directory Server Monitoring MIB 5.66. RFC 2605 Directory Server Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.067 RFC 2613 Remote Network Monitoring MIB Extensions for 5.67. 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.068 RFC 2618 RADIUS Authentication Client MIB 5.68. RFC 2618 RADIUS Authentication Client MIB
This RFC defines the following OIDs: This RFC defines the following objects:
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,
radiusAuthClientAccessAccepts Counter32, radiusAuthClientAccessAccepts Counter32,
radiusAuthClientAccessRejects Counter32, radiusAuthClientAccessRejects Counter32,
skipping to change at line 1223 skipping to change at page 27, line 19
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 object for this There needs to be an update to allow an IPv6 based object for this
value. value.
5.069 RFC 2619 RADIUS Authentication Server MIB 5.69. RFC 2619 RADIUS Authentication Server MIB
This MIB defines the followings objects: 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,
skipping to change at line 1251 skipping to change at page 27, line 47
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 }
This object needs to be deprecated and replaced by one that This object needs to be deprecated and replaced by one that supports
supports both IPv4 and IPv6 addresses. both IPv4 and IPv6 addresses.
5.070 RFC 2622 Routing Policy Specification Language (RPSL) 5.70. RFC 2622 Routing Policy Specification Language (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.
<address-prefix> An address prefix is represented as an IPv4 address <address-prefix> An address prefix is represented as an IPv4 address
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
addresses and prefixes need to be defined. IPv6 addresses and prefixes need to be defined.
5.071 RFC 2662 Definitions of Managed Objects for the ADSL 5.71. RFC 2662 Definitions of Managed Objects for the ADSL Lines
Lines
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.072 RFC 2667 IP Tunnel MIB 5.72. 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
any type over IPv4 networks. Extension MIBs may be designed for of any type over IPv4 networks. Extension MIBs may be designed
managing protocol-specific objects. Likewise, extension MIBs may be for managing protocol-specific objects. Likewise, extension MIBs
designed for managing security-specific objects. This MIB does not may be designed for managing security-specific objects. This MIB
support tunnels over non-IPv4 networks (including IPv6 networks). does not support tunnels over non-IPv4 networks (including IPv6
Management of such tunnels may be supported by other MIBs. networks). 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.073 RFC 2669 DOCSIS Cable Device MIB Cable Device Management 5.73. 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.074 RFC 2670 Radio Frequency (RF) Interface Management Information 5.74. RFC 2670 Radio Frequency (RF) Interface Management Information
Base for MCNS/DOCSIS compliant RF interfaces Base for MCNS/DOCSIS compliant RF interfaces
This MIB defines the following objects: 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,
skipping to change at line 1342 skipping to change at page 29, line 51
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 }
This object needs to be deprecated and replaced by one that This object needs to be deprecated and replaced by one that supports
supports both IPv4 and IPv6 addresses. both IPv4 and IPv6 addresses.
5.075 RFC 2674 Definitions of Managed Objects for Bridges with 5.75. RFC 2674 Definitions of Managed Objects for Bridges with
Traffic Classes, Multicast Filtering and Virtual LAN Traffic Classes, Multicast Filtering and Virtual LAN
Extensions Extensions
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.076 RFC 2677 Definitions of Managed Objects for the NBMA Next 5.76. RFC 2677 Definitions of Managed Objects for the NBMA Next
Hop Resolution Protocol (NHRP) Hop Resolution Protocol (NHRP)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.077 RFC 2720 Traffic Flow Measurement: Meter MIB 5.77. RFC 2720 Traffic Flow Measurement: Meter MIB
This specification is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
5.078 RFC 2725 Routing Policy System Security 5.78. RFC 2725 Routing Policy System Security
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.079 RFC 2726 PGP Authentication for RIPE Database Updates 5.79. RFC 2726 PGP Authentication for RIPE Database Updates
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.080 RFC 2737 Entity MIB (Version 2) 5.80. RFC 2737 Entity MIB (Version 2)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.081 RFC 2741 Agent Extensibility (AgentX) Protocol Version 1 5.81. RFC 2741 Agent Extensibility (AgentX) Protocol Version 1
Although the examples in the document are for IPv4 transport Although the examples in the document are for IPv4 transport only,
only, there is no IPv4 dependency in the AgentX protocol itself. there is no IPv4 dependency in the AgentX protocol itself.
5.082 RFC 2742 Definitions of Managed Objects for Extensible SNMP 5.82. RFC 2742 Definitions of Managed Objects for Extensible SNMP
Agents Agents
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.083 RFC 2748 The COPS (Common Open Policy Service) Protocol 5.83. RFC 2748 The COPS (Common Open Policy Service) Protocol
This specification is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
5.084 RFC 2749 COPS usage for RSVP 5.84. RFC 2749 COPS usage for RSVP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.085 RFC 2769 Routing Policy System Replication 5.85. RFC 2769 Routing Policy System Replication
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.086 RFC 2787 Definitions of Managed Objects for the Virtual 5.86. 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
this MIB uses the SYNTAX for IP addresses which is specific to IPv4. only, this MIB uses the SYNTAX for IP addresses which is specific
Thus, changes will be required for this MIB to interoperate in an to IPv4. Thus, changes will be required for this MIB to
IPv6 environment. interoperate in an IPv6 environment.
5.087 RFC 2788 Network Services Monitoring MIB 5.87. RFC 2788 Network Services Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.088 RFC 2789 Mail Monitoring MIB 5.88. RFC 2789 Mail Monitoring MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.089 RFC 2837 Definitions of Managed Objects for the Fabric Element 5.89. 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 specification. There are no IPv4 dependencies in this specification.
5.090 RFC 2856 Textual Conventions for Additional High Capacity 5.90. RFC 2856 Textual Conventions for Additional High Capacity
Data Types Data Types
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.091 RFC 2864 The Inverted Stack Table Extension to the Interfaces 5.91. 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.092 RFC 2895 Remote Network Monitoring MIB Protocol Identifier 5.92. RFC 2895 Remote Network Monitoring MIB Protocol Identifier
Reference Reference
This specification is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
5.093 RFC 2925 Definitions of Managed Objects for Remote 5.93. 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
assumptions that are problems, though. In the following object that are problems, though. In the following object definitions:
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 1471 skipping to change at page 32, line 32
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 }
The DESCRIPTION clauses need to be updated to remove the The DESCRIPTION clauses need to be updated to remove the IPv4
IPv4 dependencies. dependencies.
5.094 RFC 2932 IPv4 Multicast Routing MIB 5.94. 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
must be defined for IPv6. defined for IPv6.
5.095 RFC 2933 Internet Group Management Protocol MIB 5.95. 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
of equivalent functionality for other address families, such as IPv6. management of equivalent functionality for other address families,
such as IPv6.
5.096 RFC 2940 Definitions of Managed Objects for Common 5.96. 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.097 RFC 2954 Definitions of Managed Objects for Frame 5.97. RFC 2954 Definitions of Managed Objects for Frame
Relay Service Relay Service
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.098 RFC 2955 Definitions of Managed Objects for Monitoring 5.98. 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 specification. There are no IPv4 dependencies in this specification.
5.099 RFC 2959 Real-Time Transport Protocol Management 5.99. RFC 2959 Real-Time Transport Protocol Management Information Base
Information Base
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.100 RFC 2981 Event MIB 5.100. RFC 2981 Event MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.101 RFC 2982 Distributed Management Expression MIB 5.101. RFC 2982 Distributed Management Expression MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.102 RFC 3014 Notification Log MIB 5.102. RFC 3014 Notification Log MIB
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.103 RFC 3019 IP Version 6 Management Information Base for 5.103. 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.104 RFC 3020 Definitions of Managed Objects for Monitoring 5.104. 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 specification. There are no IPv4 dependencies in this specification.
5.105 RFC 3055 Management Information Base for the PINT Services 5.105. RFC 3055 Management Information Base for the PINT Services
Architecture Architecture
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.106 RFC 3060 Policy Core Information Model -- Version 1 5.106. RFC 3060 Policy Core Information Model -- Version 1
Specification (CIM) Specification (CIM)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.107 RFC 3084 COPS Usage for Policy Provisioning (COPS-PR) 5.107. RFC 3084 COPS Usage for Policy Provisioning (COPS-PR)
This specification builds on RFC 2748, and is both IPv4 This specification builds on RFC 2748, and is both IPv4 and IPv6
and IPv6 capable. The specification defines a sample filter in capable. The specification defines a sample filter in section 4.3,
section 4.3, which has "ipv4" in it; however, it's just an example, which has "ipv4" in it.
and available to IPv6 as well with a simple replacement of "ipv4"
with "ipv6".
5.108 RFC 3165 Definitions of Managed Objects for the Delegation of 5.108. RFC 3165 Definitions of Managed Objects for the Delegation of
Management Scripts. Management Scripts
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.109 RFC 3231 Definitions of Managed Objects for Scheduling Management 5.109. RFC 3231 Definitions of Managed Objects for Scheduling
Operations. Management Operations
There are no IPv4 dependecies in this specification. There are no IPv4 dependencies in this specification.
5.110 RFC 3291 Textual Conventions for Internet Network Addresses 5.110. RFC 3291 Textual Conventions for Internet Network Addresses
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.111 RFC 3635 Definitions of Managed Objects for the 5.111. RFC 3635 Definitions of Managed Objects for the
Ethernet-like Interface Types Ethernet-like Interface Types
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
5.112 RFC 3636 Definitions of Managed Objects for IEEE 802.3 Medium 5.112. RFC 3636 Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs) Attachment Units (MAUs)
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.0 Experimental RFCs 6. Experimental RFCs
Experimental RFCs typically define protocols that do not have widescale Experimental RFCs typically define protocols that do not have
implementation or usage on the Internet. They are often propriety in widescale implementation or usage on the Internet. They are often
nature or used in limited arenas. They are documented to the Internet propriety in nature or used in limited arenas. They are documented
community in order to allow potential interoperability or some other to the Internet community in order to allow potential
potential useful scenario. In a few cases they are presented as interoperability or some other potential useful scenario. In a few
alternatives to the mainstream solution to an acknowledged problem. cases, they are presented as alternatives to the mainstream solution
to an acknowledged problem.
6.01 RFC 1187 Bulk Table Retrieval with the SNMP 6.1. RFC 1187 Bulk Table Retrieval with the SNMP
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.02 RFC 1224 Techniques for managing asynchronously generated 6.2. RFC 1224 Techniques for managing asynchronously generated
alerts alerts
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.03 RFC 1238 CLNS MIB for use with Connectionless Network Protocol 6.3. 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)
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.4. RFC 1592 Simple Network Management Protocol Distributed Protocol
Interface Version 2.0 Interface Version 2.0
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.05 RFC 1792 TCP/IPX Connection Mib Specification 6.5. RFC 1792 TCP/IPX Connection Mib Specification
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.06 RFC 2724 RTFM: New Attributes for Traffic Flow Measurement 6.6. RFC 2724 RTFM: New Attributes for Traffic Flow Measurement
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.07 RFC 2758 Definitions of Managed Objects for Service Level 6.7. RFC 2758 Definitions of Managed Objects for Service Level
Agreements Performance Monitoring Agreements Performance Monitoring
This specification is both IPv4 and IPv6 aware and needs no changes. This specification is both IPv4 and IPv6 aware and needs no changes.
6.08 RFC 2786 Diffie-Helman USM Key Management Information Base and 6.8. RFC 2786 Diffie-Helman USM Key Management Information Base and
Textual Convention Textual Convention
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.09 RFC 2903 Generic AAA Architecture 6.9. RFC 2903 Generic AAA Architecture
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
6.10 RFC 2934 Protocol Independent Multicast MIB for IPv4 6.10. RFC 2934 Protocol Independent Multicast MIB for IPv4
This document is specific to IPv4. This document is specific to IPv4.
6.11 RFC 3179 Script MIB Extensibility Protocol Version 1.1 6.11. RFC 3179 Script MIB Extensibility Protocol Version 1.1
There are no IPv4 dependencies in this specification. There are no IPv4 dependencies in this specification.
7.0 Summary of Results 7. Summary of Results
In the initial survey of RFCs 36 positives were identified out of a In the initial survey of RFCs, 36 positives were identified out of a
total of 153, broken down as follows: total of 153, broken down as follows:
Standards 6 of 15 or 40.00% Standards: 6 out of 15 or 40.00%
Draft Standards 4 of 15 or 26.67% Draft Standards: 4 out of 15 or 26.67%
Proposed Standards 26 of 112 or 23.21% Proposed Standards: 26 out of 112 or 23.21%
Experimental RFCs 0 of 11 or 0.00% Experimental RFCs: 0 out of 11 or 0.00%
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 16, Structure of Management Information (RFCs 1155 and 1212) 7.1.1. STD 16, Structure of Management Information (RFCs 1155 and 1212)
RFCs 1155 and RFCs 1212 (along with the informational document RFC RFC 1155 and RFC 1212 (along with the informational document RFC
1215) define SMIv1. These documents have been superseded by RFCs 1215) define SMIv1. These documents have been superseded by RFCs
2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer 2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer
being used as the basis for new IETF MIB modules, the limitations being used as the basis for new IETF MIB modules, the limitations
identified in this Internet Standard do not require any action. identified in this Internet Standard do not require any action.
7.1.2 STD 17 Simple Network Management Protocol (RFC 1213) 7.1.2. STD 17 Simple Network Management Protocol (RFC 1213)
The limitations identified have been addressed, because RFC 1213 The limitations identified have been addressed, because RFC 1213 has
has been split into multiple modules which are all IPv6 capable. been split into multiple modules which are all IPv6 capable.
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-11.txt). (IDR) WG [2].
7.2.2 SMDS MIB (RFC 1694) 7.2.2. SMDS MIB (RFC 1694)
See Internet Area standards. Once a specification for IPv6 over SMDS See Internet Area standards. Once a specification for IPv6 over SMDS
is 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)
There is no updated MIB module to cover the problems outlined. A There is no updated MIB module to cover the problems outlined. A new
new MIB module should be defined. MIB module should be defined.
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 [3].
exists (draft-ietf-ospf-ospfv3-mib-07.txt).
7.2.5 Transport MIB (RFC 1906) 7.2.5. Transport MIB (RFC 1906)
RFC 1906 has been obsoleted by RFC 3417, Transport Mappings for RFC 1906 has been obsoleted by RFC 3417, Transport Mappings for SNMP,
SNMP, and the limitations of this specification have been addressed by and the limitations of this specification have been addressed by that
that RFC, which defines TCs that can be used to specify transport RFC, which defines TCs that can be used to specify transport domains
domains in an IP version-independent way. RFC 3419 recommends that in an IP version-independent way. RFC 3419 recommends that those TCs
those TCs be used in place of SnmpUDPAddress when IPv6 support is be used in place of SnmpUDPAddress when IPv6 support is required and
required and for all new applications that are not SNMP-specific. for all new applications that are not SNMP-specific.
7.3 Proposed Standards 7.3. Proposed Standards
7.3.01 MIB for Multiprotocol Interconnect over X.25 (RFC 1461) 7.3.1. MIB for Multiprotocol Interconnect over X.25 (RFC 1461)
This problem has not been addressed. If a user requirement for This problem has not been addressed. If a user requirement for IPv6
IPv6 over X.25 develops (which is thought to be unlikely) then over X.25 develops (which is thought to be unlikely) then this MIB
this MIB module will need to be updated in order to accomodate it. module will need to be updated in order to accommodate it.
7.3.02 PPP IPCP MIB (RFC 1473) 7.3.2. 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
should be defined. should be defined.
7.3.03 Appletalk MIB (RFC 1742) 7.3.3. Appletalk MIB (RFC 1742)
This problem has not been addressed. If a user requirement for This problem has not been addressed. If a user requirement for IPv6
IPv6 over Appletalk develops (which is thought to be unlikely) over Appletalk develops (which is thought to be unlikely) then this
then this MIB module will need to be updated (or a new MIB module MIB module will need to be updated (or a new MIB module will need to
will need to be created) in order to accomodate it. be created) in order to accommodate it.
7.3.04 The Definitions of Managed Objects for IP Mobility 7.3.4. 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 MIP6 WG and there is The problems are being resolved by the MIP6 WG [4].
an ID (draft-ietf-mip6-mipv6-mib-00.txt).
7.3.05 SMIv2 IP MIB (RFC 2011) 7.3.5. SMIv2 IP MIB (RFC 2011)
This issue is being resolved by the IPv6 WG and there is an This issue is being resolved by the IPv6 WG [5].
ID (draft-ietf-ipv6-rfc2011-update-04.txt).
7.3.06 SNMPv2 TCP MIB (RFC 2012) 7.3.6. SNMPv2 TCP MIB (RFC 2012)
This issue is being resolved by the IPv6 WG and there is an This issue is being resolved by the IPv6 WG [6].
ID (draft-ietf-ipv6-rfc2012-update-04.txt).
7.3.07 SNMPv2 UDP MIB (RFC 2013) 7.3.7. SNMPv2 UDP MIB (RFC 2013)
This issue is being resolved by the IPv6 WG and there is an This issue is being resolved by the IPv6 WG [7].
ID (draft-ietf-ipv6-rfc2013-update-01.txt).
7.3.08 RMON-II MIB (RFC 2021) 7.3.8. RMON-II MIB (RFC 2021)
This issue has been brought to the attention of the RMONMIB WG. This issue has been brought to the attention of the RMONMIB WG.
Currently there is an ID (draft-ietf-rmonmib-rmon2-v2-00.txt) Currently, there is a work in progress [8] to update RFC 2021, but it
to update RFC 2021, but it does not address the problems that does not address the problems that have been identified; it is
have been identified; it is expected that there will be a expected that there will be a resolution in a future version of that
resolution in a future version of that ID. document.
7.3.09 DataLink Switching using SMIv2 MIB (RFC 2024) 7.3.9. DataLink Switching using SMIv2 MIB (RFC 2024)
The problems have not been addressed and an updated MIB should be The problems have not been addressed and an updated MIB should be
defined. defined.
7.3.10 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 [9].
address this (draft-ietf-ipngwg-rfc2096-update-05.txt)
7.3.11 Classical IP & ARP over ATM MIB (RFC 2320) 7.3.11. Classical IP & ARP over ATM MIB (RFC 2320)
The current version of Classical IP and ARP over ATM (RFC 2225) The current version of Classical IP and ARP over ATM (RFC 2225) does
does not support IPv6. If and when that protocol specification not support IPv6. If and when that protocol specification is updated
is updated to add IPv6 support, then new MIB objects to represent to add IPv6 support, then new MIB objects to represent IPv6 addresses
IPv6 addresses will need to be added to this MIB module. will need to be added to this MIB module.
7.3.12 Multicast over UNI 3.0/3.1 ATM MIB (RFC 2417) 7.3.12. Multicast over UNI 3.0/3.1 ATM MIB (RFC 2417)
The current version of Multicast over UNI 3.0/3.1 ATM (RFC The current version of Multicast over UNI 3.0/3.1 ATM (RFC 2022) does
2022) does not support IPv6. If and when that protocol not support IPv6. If and when that protocol specification is updated
specification is updated to add IPv6 support, then new MIB to add IPv6 support, then new MIB objects to represent IPv6 addresses
objects to represent IPv6 addresses will need to be added to will need to be added to this MIB module.
this MIB module.
7.3.13 ATM MIB (RFC 2515) 7.3.13. ATM MIB (RFC 2515)
The AToM MIB WG is currently collecting implementation reports for RFC The AToM MIB WG is currently collecting implementation reports for
2515 and is considering whether to advance, revise, or retire this RFC 2515 and is considering whether to advance, revise, or retire
specification. The problems identified have been brought to the this specification. The problems identified have been brought to the
attention of the WG. attention of the WG.
7.3.14 TN3270 MIB (RFC 2562) 7.3.14. TN3270 MIB (RFC 2562)
The problems identified are not being addressed and a new MIB The problems identified are not being addressed and a new MIB module
module may need to be defined. may need to be defined.
7.3.15 Application MIB (RFC 2564) 7.3.15. Application MIB (RFC 2564)
The problems identified are not being addressed and a new MIB The problems identified are not being addressed and a new MIB module
module may need to be defined. One possible solution might be may need to be defined. One possible solution might be to use the
to use the RFC 3419 TCs. RFC 3419 TCs.
7.3.16 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.17 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.18 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.19 RPSL (RFC 2622) 7.3.19. 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 [10] defines extensions to solve this issue, and it is being
it is being considered for publication. considered for publication.
7.3.20 IPv4 Tunnel MIB (RFC 2667) 7.3.20. IPv4 Tunnel MIB (RFC 2667)
The issue is being resolved and and ID exists The issue is being resolved.
(draft-thaler-inet-tunnel-mib-00.txt).
7.3.21 DOCSIS MIB (RFC 2669) 7.3.21. 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.
is available (draft-ietf-ipcdn-device-mibv2-05.txt).
7.3.22 RF MIB For DOCSIS (RFC 2670) 7.3.22. 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 [11].
is available (draft-ietf-ipcdn-docs-rfmibv2-06.txt).
7.3.23 VRRP MIB (RFC 2787) 7.3.23. VRRP MIB (RFC 2787)
The problems have not been addressed and a new MIB may need to be The problems have not been addressed and a new MIB may need to be
defined. defined.
7.3.24 MIB For Traceroute, Pings and Lookups (RFC 2925) 7.3.24. MIB For Traceroute, Pings and Lookups (RFC 2925)
The problems have not been addressed and a new MIB may need to be The problems have not been addressed and a new MIB may need to be
defined. defined.
7.3.25 IPv4 Multicast Routing MIB (RFC 2932) 7.3.25. IPv4 Multicast Routing MIB (RFC 2932)
The problems have not been addressed a new MIB must be defined. The problems have not been addressed a new MIB must be defined.
7.3.26 IGMP MIB (RFC 2933) 7.3.26. IGMP MIB (RFC 2933)
This problem is currently being addressed by the MAGMA WG and an ID This problem is currently being addressed by the MAGMA WG [12].
exists (draft-ietf-magma-mgmd-mib-01.txt).
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 may need to be The problems have not been addressed and a new MIB may need to be
defined. defined.
8.0 Security Consideration 8. Security Considerations
This memo examines the IPv6-readiness of specifications; this does not This memo examines the IPv6-readiness of specifications; this does
have security considerations in itself. not have security considerations in itself.
9.0 Acknowledgements 9. 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 thank his
his partner in all ways, Wendy M. Nesser. 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
for guidance and collection of comments for the editing of this his guidance and collection of comments for the editing of this
document. document. He would further like to thank Juergen Schoenwaelder,
He would further like to thank Juergen Schoenwaelder, Brian Carpenter, Brian Carpenter, Bert Wijnen and especially C. M. Heard for feedback
Bert Wijnen and especially C. M. Heard for feedback on many points of on many points of this document.
this document.
10.0 References 10. References
10.1 Normative 10.1. Normative Reference
[1] Philip J. Nesser II, Andreas Bergstrom. "Introduction to the Survey [1] Nesser, II, P. and A. Bergstrom, Editor, "Introduction to the
of IPv4 Addresses in Currently Deployed IETF Standards", Survey of IPv4 Addresses in Currently Deployed IETF Standards",
draft-ietf-v6ops-ipv4survey-intro-05.txt IETF work in progress, RFC 3789, June 2004.
November 2003
11.0 Authors' Addresses 10.2. Informative References
Please contact the author with any questions, comments or suggestions [2] Haas, J. and S. Hares, Editors, "Definitions of Managed Objects
at: for the Fourth Version of Border Gateway Protocol (BGP-4)", Work
in Progress, April 2004.
[3] Joyal, D. and V. Manral, "Management Information Base for
OSPFv3", Work in Progress, April 2004.
[4] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, "The Mobile
IPv6 MIB", Work in Progress, February 2004.
[5] Routhier, S., Editor, "Management Information Base for the
Internet Protocol (IP)", Work in Progress, April 2004.
[6] Raghunarayan, R., Editor, "Management Information Base for the
Transmission Control Protocol (TCP)", Work in Progress, February
2004.
[7] Fenner, B. and J. Flick, "Management Information Base for the
User Datagram Protocol (UDP)", Work in Progress, April 2004.
[8] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 Using SMIv2", Work in Progress,
February 2004.
[9] Haberman, B., "IP Forwarding Table MIB", Work in Progress,
February 2004.
[10] Blunk, L., Damas, J., Parent, F. and A. Robachevsky, "Routing
Policy Specification Language next generation (RPSLng)", Work in
Progress, April 2004.
[11] Raftus, D. and E. Cardona, Editor, "Radio Frequency (RF)
Interface Management Information Base for DOCSIS 2.0 compliant
RF interfaces", Work in Progress, April 2004.
[12] Chesterfield, J., Editor, "Multicast Group Membership Discovery
MIB", Work in Progress, February 2004.
11. Authors' Addresses
Please contact the authors with any questions, comments or
suggestions 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
Kirkland, WA 98034 Kirkland, WA 98034
Email: phil@nesser.com
Phone: +1 425 481 4303 Phone: +1 425 481 4303
Fax: +1 425 48 Fax: +1 425 48
EMail: phil@nesser.com
Andreas Bergstrom (Editor) Andreas Bergstrom (Editor)
Ostfold University College Ostfold University College
Email: andreas.bergstrom@hiof.no Rute 503 Buer
Address: Rute 503 Buer
N-1766 Halden N-1766 Halden
Norway Norway
12.0 Intellectual Property Statement EMail: andreas.bergstrom@hiof.no
12. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
13.0 Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Acknowledgement
This document and translations of it may be copied and furnished to Funding for the RFC Editor function is currently provided by the
others, and derivative works that comment on or otherwise explain it Internet Society.
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu-
ment itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop-
ing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as
required to translate it into languages other than English. The lim-
ited permissions granted above are perpetual and will not be revoked
by the Internet Society or its successors or assigns. This document
and the information contained herein is provided on an "AS IS" basis
and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS-
CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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