3796
INFORMATIONAL
Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents
Authors: P. Nesser, II, A. Bergstrom
Date: June 2004
Area: ops
Working Group: v6ops
Stream: IETF
Abstract
This document seeks to record all usage of IPv4 addresses in currently deployed IETF Operations & Management Area accepted standards. In order to successfully transition from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies. It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at least dually support IPv4 and IPv6. To this end, all Standards (Full, Draft, and Proposed), as well as Experimental RFCs, will be surveyed and any dependencies will be documented. This memo provides information for the Internet community.
RFC 3796
INFORMATIONAL
Network Working Group P. Nesser, II
Request for Comments: 3796 Nesser & Nesser Consulting
Category: Informational A. Bergstrom, Ed.
Ostfold University College
June 2004
<span class="h1">Survey of IPv4 Addresses in Currently Deployed IETF</span>
Operations & Management Area Standards Track and Experimental Documents
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2004).
Abstract
This document seeks to record all usage of IPv4 addresses in
currently deployed IETF Operations & Management Area accepted
standards. In order to successfully transition from an all IPv4
Internet to an all IPv6 Internet, many interim steps will be taken.
One of these steps is the evolution of current protocols that have
IPv4 dependencies. It is hoped that these protocols (and their
implementations) will be redesigned to be network address
independent, but failing that will at least dually support IPv4 and
IPv6. To this end, all Standards (Full, Draft, and Proposed), as
well as Experimental RFCs, will be surveyed and any dependencies will
be documented.
<span class="grey">Nesser II & Bergstrom Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Document Organization. . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Full Standards . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Draft Standards. . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5">5</a>. Proposed Standards . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6">6</a>. Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a>
<a href="#section-7">7</a>. Summary of Results . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
<a href="#section-7.1">7.1</a>. Standards. . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
<a href="#section-7.2">7.2</a>. Draft Standards. . . . . . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
<a href="#section-7.3">7.3</a>. Proposed Standards . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
<a href="#section-7.4">7.4</a>. Experimental RFCs. . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-8">8</a>. Security Considerations. . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9">9</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-10">10</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-10.1">10.1</a>. Normative Reference. . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-10.2">10.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
<a href="#section-11">11</a>. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . <a href="#page-42">42</a>
<a href="#section-12">12</a>. Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document is part of a set aiming to record all usage of IPv4
addresses in IETF standards. In an effort to have the information in
a manageable form, it has been broken into 7 documents conforming to
the current IETF areas (Application, Internet, Operations &
Management, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the introduction [<a href="#ref-1" title=""Introduction to the Survey of IPv4 Addresses in Currently Deployed IETF Standards"">1</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Document Organization</span>
The document is organized as described below:
Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, <a href="#section-5">5</a>, and <a href="#section-6">6</a> each describe the raw analysis of Full,
Draft, and Proposed Standards, and Experimental RFCs. Each RFC is
discussed in its turn starting with <a href="./rfc1">RFC 1</a> and ending with (around)
<a href="./rfc3100">RFC 3100</a>. The comments for each RFC are "raw" in nature. That is,
each RFC is discussed in a vacuum and problems or issues discussed do
not "look ahead" to see if the problems have already been fixed.
<a href="#section-7">Section 7</a> is an analysis of the data presented in Sections <a href="#section-3">3</a>, <a href="#section-4">4</a>, <a href="#section-5">5</a>,
and 6. It is here that all of the results are considered as a whole
and the problems that have been resolved in later RFCs are
correlated.
<span class="grey">Nesser II & Bergstrom Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Full Standards</span>
Full Internet Standards (most commonly simply referred to as
"Standards") are fully mature protocol specification that are widely
implemented and used throughout the Internet.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. <a href="./rfc1155">RFC 1155</a> Structure of Management Information</span>
<a href="#section-3.2.3.2">Section 3.2.3.2</a>. IpAddress defines the following:
This application-wide type represents a 32-bit internet address.
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 the document.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. <a href="./rfc1212">RFC 1212</a> Concise MIB definitions</span>
In <a href="#section-4.1.6">section 4.1.6</a> IpAddress is defined as:
(6) IpAddress-valued: 4 sub-identifiers, in the familiar
a.b.c.d notation.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. <a href="./rfc1213">RFC 1213</a> Management Information Base</span>
There are far too many instances of IPv4 addresses is this document
to enumerate here. The particular object groups that are affected
are the IP group, the ICMP group, the TCP group, the UDP group, and
the EGP group.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. <a href="./rfc2578">RFC 2578</a> Structure of Management Information Version 2 (SMIv2)</span>
<a href="#section-7.1.5">Section 7.1.5</a> defines the IpAddress data type:
The IpAddress type represents a 32-bit internet address. It is
represented as an OCTET STRING of length 4, in network byte-order.
Note that the IpAddress type is a tagged type for historical
reasons. Network addresses should be represented using an
invocation of the TEXTUAL-CONVENTION macro.
Note the deprecated status of this type; see <a href="./rfc3291">RFC 3291</a> for details on
the replacement TEXTUAL-CONVENTION definitions.
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. <a href="./rfc2579">RFC 2579</a> Textual Conventions for SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. <a href="./rfc2580">RFC 2580</a> Conformance Statements for SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. <a href="./rfc2819">RFC 2819</a> Remote Network Monitoring Management Information Base</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. <a href="./rfc3411">RFC 3411</a> An Architecture for Describing SNMP Management Frameworks</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. <a href="./rfc3412">RFC 3412</a> Message Processing and Dispatching for the Simple Network</span>
<span class="h3"> Management Protocol (SNMP)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. <a href="./rfc3413">RFC 3413</a> SNMP Applications</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. <a href="./rfc3414">RFC 3414</a> User-based Security Model (USM) for version 3 of the</span>
<span class="h3"> Simple Network Management Protocol (SNMPv3)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.12" href="#section-3.12">3.12</a>. <a href="./rfc3415">RFC 3415</a> View-based Access Control Model (VACM) for the Simple</span>
<span class="h3"> Network Management Protocol (SNMP)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-3.13" href="#section-3.13">3.13</a>. <a href="./rfc3416">RFC 3416</a> Protocol Operations for Version 2 of the Simple Network</span>
<span class="h3"> Management Protocol (SNMP)</span>
<a href="#section-4.2.2.1">Section 4.2.2.1</a>., Example of Table Traversal, and <a href="#section-4.2.3.1">Section 4.2.3.1</a>.,
Another Example of Table Traversal, both use objects from MIB2 whose
data contains IPv4 addresses. Other than their use in these example
sections, there are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-3.14" href="#section-3.14">3.14</a>. <a href="./rfc3417">RFC 3417</a> Transport Mappings for Version 2 of the Simple Network</span>
<span class="h3"> Management Protocol (SNMP)</span>
<a href="#section-2">Section 2</a> Definitions contains the following definition:
SnmpUDPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d/2d"
STATUS current
DESCRIPTION
"Represents a UDP address:
octets contents encoding
1-4 IP-address network-byte order
5-6 UDP-port network-byte order
"
SYNTAX OCTET STRING (SIZE (6))
<a href="#section-8.1">Section 8.1</a>, Usage Example, also contains examples which uses IPv4
address, but it has no significance in the operation of the
specification.
<span class="h3"><a class="selflink" id="section-3.15" href="#section-3.15">3.15</a>. <a href="./rfc3418">RFC 3418</a> Management Information Base for Version 2 of the Simple</span>
<span class="h3"> Network Management Protocol (SNMP)</span>
There are no IPv4 dependencies in this specification.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Draft Standards</span>
Draft Standards represent the penultimate standard level in the IETF.
A protocol can only achieve draft standard when there are multiple,
independent, interoperable implementations. Draft Standards are
usually quite mature and widely used.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. <a href="./rfc1493">RFC 1493</a> Definitions of Managed Objects for Bridges</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. <a href="./rfc1559">RFC 1559</a> DECnet Phase IV MIB Extensions</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. <a href="./rfc1657">RFC 1657</a> Definitions of Managed Objects for the Fourth</span>
<span class="h3"> Version of the Border Gateway Protocol (BGP-4) using SMIv2</span>
The MIB defined in this RFC deals with objects in a BGP4 based
routing system and therefore contain many objects that are limited by
the IpAddress 32-bit value defined in MIB2. Clearly the values of
this MIB are limited to IPv4 addresses. No update is needed,
although a new MIB should be defined for BGP4+ to allow management of
IPv6 addresses and routes.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. <a href="./rfc1658">RFC 1658</a> Definitions of Managed Objects for Character Stream</span>
<span class="h3"> Devices using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. <a href="./rfc1659">RFC 1659</a> Definitions of Managed Objects for RS-232-like Hardware</span>
<span class="h3"> Devices using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. <a href="./rfc1660">RFC 1660</a> Definitions of Managed Objects for Parallel-printer-like</span>
<span class="h3"> Hardware Devices using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. <a href="./rfc1694">RFC 1694</a> Definitions of Managed Objects for SMDS Interfaces using</span>
<span class="h3"> SMIv2</span>
This MIB module definition defines the following subtree:
ipOverSMDS OBJECT IDENTIFIER ::= { smdsApplications 1 }
-- Although the objects in this group are read-only, at the
-- agent's discretion they may be made read-write so that the
-- management station, when appropriately authorized, may
-- change the addressing information related to the
-- configuration of a logical IP subnetwork implemented on
-- top of SMDS.
-- This table is necessary to support <a href="./rfc1209">RFC1209</a> (IP-over-SMDS)
-- and gives information on the Group Addresses and ARP
-- Addresses used in the Logical IP subnetwork.
-- One SMDS address may be associated with multiple IP
-- addresses. One SNI may be associated with multiple LISs.
ipOverSMDSTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpOverSMDSEntry
MAX-ACCESS not-accessible
<span class="grey">Nesser II & Bergstrom Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
STATUS current
DESCRIPTION
"The table of addressing information relevant to
this entity's IP addresses."
::= { ipOverSMDS 1 }
ipOverSMDSEntry OBJECT-TYPE
SYNTAX IpOverSMDSEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The addressing information for one of this
entity's IP addresses."
INDEX { ipOverSMDSIndex, ipOverSMDSAddress }
::= { ipOverSMDSTable 1 }
IpOverSMDSEntry ::=
SEQUENCE {
ipOverSMDSIndex IfIndex,
ipOverSMDSAddress IpAddress,
ipOverSMDSHA SMDSAddress,
ipOverSMDSLISGA SMDSAddress,
ipOverSMDSARPReq SMDSAddress
}
ipOverSMDSIndex OBJECT-TYPE
SYNTAX IfIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object identifies the
interface for which this entry contains management
information. "
::= { ipOverSMDSEntry 1 }
ipOverSMDSAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address to which this entry's addressing
information pertains."
::= { ipOverSMDSEntry 2 }
ipOverSMDSHA OBJECT-TYPE
SYNTAX SMDSAddress
MAX-ACCESS read-only
STATUS current
<span class="grey">Nesser II & Bergstrom Informational [Page 7]</span><span id="page-8" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
DESCRIPTION
"The SMDS Individual address of the IP station."
::= { ipOverSMDSEntry 3 }
ipOverSMDSLISGA OBJECT-TYPE
SYNTAX SMDSAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The SMDS Group Address that has been configured
to identify the SMDS Subscriber-Network Interfaces
(SNIs) of all members of the Logical IP Subnetwork
(LIS) connected to the network supporting SMDS."
::= { ipOverSMDSEntry 4 }
ipOverSMDSARPReq OBJECT-TYPE
SYNTAX SMDSAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The SMDS address (individual or group) to which
ARP Requests are to be sent."
::= { ipOverSMDSEntry 5 }
Although these object definitions are intended for IPv4 addresses, a
similar MIB can be defined for IPv6 addressing.
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. <a href="./rfc1724">RFC 1724</a> RIP Version 2 MIB Extension</span>
As expected, this RFC is filled with IPv4 dependencies since it
defines a MIB module for an IPv4-only routing protocol. A new MIB
for RIPng is required.
<span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>. <a href="./rfc1748">RFC 1748</a> IEEE 802.5 MIB using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.10" href="#section-4.10">4.10</a>. <a href="./rfc1850">RFC 1850</a> OSPF Version 2 Management Information Base</span>
This MIB defines managed objects for OSPFv2 which is a protocol used
to exchange IPv4 routing information. Since OSPFv2 is limited to
IPv4 addresses, a new MIB is required to support a new version of
OSPF that is IPv6 aware.
<span class="grey">Nesser II & Bergstrom Informational [Page 8]</span><span id="page-9" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-4.11" href="#section-4.11">4.11</a>. <a href="./rfc2115">RFC 2115</a> Management Information Base for Frame Relay DTEs</span>
<span class="h3"> Using SMIv2</span>
This specification has several examples of how IPv4 addresses might
be mapped to Frame Relay DLCIs. Other than those examples there are
no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.12" href="#section-4.12">4.12</a>. <a href="./rfc2790">RFC 2790</a> Host Resources MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.13" href="#section-4.13">4.13</a>. <a href="./rfc2863">RFC 2863</a> The Interfaces Group MIB</span>
There are no IPv4 dependencies in this specification. There is some
discussion in one object definition about an interface performing a
self test, but the object itself is IP version independent.
<span class="h3"><a class="selflink" id="section-4.14" href="#section-4.14">4.14</a>. <a href="./rfc3592">RFC 3592</a> Definitions of Managed Objects for the Synchronous</span>
<span class="h3"> Optical Network/Synchronous Digital Hierarchy (SONET/SDH)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-4.15" href="#section-4.15">4.15</a>. <a href="./rfc3593">RFC 3593</a> Textual Conventions for MIB Modules Using Performance</span>
<span class="h3"> History Based on 15 Minute Intervals</span>
There are no IPv4 dependencies in this specification.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Proposed Standards</span>
Proposed Standards are introductory level documents. There are no
requirements for even a single implementation. In many cases,
Proposed are never implemented or advanced in the IETF standards
process. They therefore are often just proposed ideas that are
presented to the Internet community. Sometimes flaws are exposed or
they are one of many competing solutions to problems. In these later
cases, no discussion is presented as it would not serve the purpose
of this discussion.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. <a href="./rfc1239">RFC 1239</a> Reassignment of experimental MIBs to standard MIBs</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. <a href="./rfc1269">RFC 1269</a> Definitions of Managed Objects for the Border</span>
<span class="h3"> Gateway Protocol: Version 3</span>
The use of BGP3 has been deprecated and is not discussed.
<span class="grey">Nesser II & Bergstrom Informational [Page 9]</span><span id="page-10" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. <a href="./rfc1285">RFC 1285</a> FDDI Management Information Base</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. <a href="./rfc1381">RFC 1381</a> SNMP MIB Extension for X.25 LAPB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. <a href="./rfc1382">RFC 1382</a> SNMP MIB Extension for the X.25 Packet Layer</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. <a href="./rfc1414">RFC 1414</a> Identification MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.7" href="#section-5.7">5.7</a>. <a href="./rfc1418">RFC 1418</a> SNMP over OSI</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.8" href="#section-5.8">5.8</a>. <a href="./rfc1419">RFC 1419</a> SNMP over AppleTalk</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.9" href="#section-5.9">5.9</a>. <a href="./rfc1420">RFC 1420</a> SNMP over IPX</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.10" href="#section-5.10">5.10</a>. <a href="./rfc1461">RFC 1461</a> SNMP MIB extension for Multiprotocol Interconnect</span>
<span class="h3"> over X.25</span>
The following objects are defined in <a href="#section-4">Section 4</a>, Definitions:
mioxPleLastFailedEnAddr OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(2..128))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The last Encapsulated address that failed
to find a corresponding X.121 address and
caused mioxPleEnAddrToX121LkupFlrs to be
incremented. The first octet of this object
contains the encapsulation type, the
remaining octets contain the address of that
type that failed. Thus for an IP address,
the length will be five octets, the first
octet will contain 204 (hex CC), and the
last four octets will contain the IP
<span class="grey">Nesser II & Bergstrom Informational [Page 10]</span><span id="page-11" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
address. For a snap encapsulation, the
first byte would be 128 (hex 80) and the
rest of the octet string would have the snap
header."
::= { mioxPleEntry 4 }
mioxPeerEnAddr OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..128))
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The Encapsulation address of the remote
host mapped by this table entry. A length
of zero indicates the remote IP address is
unknown or unspecified for use as a PLE
default.
The first octet of this object contains the
encapsulation type, the remaining octets
contain an address of that type. Thus for
an IP address, the length will be five
octets, the first octet will contain 204
(hex CC), and the last four octets will
contain the IP address. For a snap
encapsulation, the first byte would be 128
(hex 80) and the rest of the octet string
would have the snap header."
DEFVAL { ''h }
::= { mioxPeerEntry 7 }
mioxPeerEncType OBJECT-TYPE
SYNTAX INTEGER (0..256)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The value of the encapsulation type. For
IP encapsulation this will have a value of
204 (hex CC). For SNAP encapsulated
packets, this will have a value of 128 (hex
80). For CLNP, ISO 8473, this will have a
value of 129 (hex 81). For ES-ES, ISO 9542,
this will have a value of 130 (hex 82). A
value of 197 (hex C5) identifies the Blacker
X.25 encapsulation. A value of 0,
identifies the Null encapsulation.
This value can only be written when the
mioxPeerStatus object with the same
<span class="grey">Nesser II & Bergstrom Informational [Page 11]</span><span id="page-12" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
mioxPeerIndex has a value of underCreation.
Setting this object to a value of 256
deletes the entry. When deleting an entry,
all other entries in the mioxPeerEncTable
with the same mioxPeerIndex and with an
mioxPeerEncIndex higher then the deleted
entry, will all have their mioxPeerEncIndex
values decremented by one."
::= { mioxPeerEncEntry 2 }
Updated values of the first byte of these objects can be defined to
support IPv6 addresses.
<span class="h3"><a class="selflink" id="section-5.11" href="#section-5.11">5.11</a>. <a href="./rfc1471">RFC 1471</a> The Definitions of Managed Objects for the Link</span>
<span class="h3"> Control Protocol of the Point-to-Point Protocol</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.12" href="#section-5.12">5.12</a>. <a href="./rfc1472">RFC 1472</a> The Definitions of Managed Objects for the Security</span>
<span class="h3"> Protocols of the Point-to-Point Protocol</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.13" href="#section-5.13">5.13</a>. <a href="./rfc1473">RFC 1473</a> The Definitions of Managed Objects for the IP Network</span>
<span class="h3"> Control Protocol of the Point-to-Point Protocol</span>
This MIB module is targeted specifically at IPv4 over PPP. A new MIB
module would need to be defined to support IPv6 over PPP.
<span class="h3"><a class="selflink" id="section-5.14" href="#section-5.14">5.14</a>. <a href="./rfc1474">RFC 1474</a> The Definitions of Managed Objects for the Bridge</span>
<span class="h3"> Network Control Protocol of the Point-to-Point Protocol</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.15" href="#section-5.15">5.15</a>. <a href="./rfc1512">RFC 1512</a> FDDI Management Information Base</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.16" href="#section-5.16">5.16</a>. <a href="./rfc1513">RFC 1513</a> Token Ring Extensions to the Remote Network</span>
<span class="h3"> Monitoring MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.17" href="#section-5.17">5.17</a>. <a href="./rfc1525">RFC 1525</a> Definitions of Managed Objects for Source Routing</span>
<span class="h3"> Bridges</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 12]</span><span id="page-13" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.18" href="#section-5.18">5.18</a>. <a href="./rfc1628">RFC 1628</a> UPS Management Information Base</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.19" href="#section-5.19">5.19</a>. <a href="./rfc1666">RFC 1666</a> Definitions of Managed Objects for SNA NAUs using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.20" href="#section-5.20">5.20</a>. <a href="./rfc1696">RFC 1696</a> Modem Management Information Base (MIB) using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.21" href="#section-5.21">5.21</a>. <a href="./rfc1697">RFC 1697</a> Relational Database Management System (RDBMS)</span>
<span class="h3"> Management Information Base (MIB) using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.22" href="#section-5.22">5.22</a>. <a href="./rfc1742">RFC 1742</a> AppleTalk Management Information Base II</span>
The following objects are defined:
KipEntry ::= SEQUENCE {
kipNetStart ATNetworkNumber,
kipNetEnd ATNetworkNumber,
kipNextHop IpAddress,
kipHopCount INTEGER,
kipBCastAddr IpAddress,
kipCore INTEGER,
kipType INTEGER,
kipState INTEGER,
kipShare INTEGER,
kipFrom IpAddress
}
kipNextHop OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The IP address of the next hop in the route to this
entry's destination network."
::= { kipEntry 3 }
kipBCastAddr OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-write
STATUS mandatory
DESCRIPTION
<span class="grey">Nesser II & Bergstrom Informational [Page 13]</span><span id="page-14" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
"The form of the IP address used to broadcast on this
network."
::= { kipEntry 5 }
kipFrom OBJECT-TYPE
SYNTAX IpAddress
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The IP address from which the routing entry was
learned via the AA protocol. If this entry was not
created via the AA protocol, it should contain IP
address 0.0.0.0."
::= { kipEntry 10 }
<span class="h3"><a class="selflink" id="section-5.23" href="#section-5.23">5.23</a>. <a href="./rfc1747">RFC 1747</a> Definitions of Managed Objects for SNA Data Link</span>
<span class="h3"> Control (SDLC) using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.24" href="#section-5.24">5.24</a>. <a href="./rfc1749">RFC 1749</a> IEEE 802.5 Station Source Routing MIB using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.25" href="#section-5.25">5.25</a>. <a href="./rfc1759">RFC 1759</a> Printer MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.26" href="#section-5.26">5.26</a>. <a href="./rfc2006">RFC 2006</a> The Definitions of Managed Objects for IP Mobility</span>
<span class="h3"> Support using SMIv2</span>
This document defines a MIB for the Mobile IPv4. Without
enumeration, let it be stated that a new MIB for IPv6 Mobility is
required.
<span class="h3"><a class="selflink" id="section-5.27" href="#section-5.27">5.27</a>. <a href="./rfc2011">RFC 2011</a> SNMPv2 Management Information Base for the Internet</span>
<span class="h3"> Protocol using SMIv2</span>
Approximately 1/3 of the objects defined in this document are IPv4-
dependent. New objects need to be defined to support IPv6.
<span class="grey">Nesser II & Bergstrom Informational [Page 14]</span><span id="page-15" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.28" href="#section-5.28">5.28</a>. <a href="./rfc2012">RFC 2012</a> SNMPv2 Management Information Base for the</span>
<span class="h3"> Transmission Control Protocol using SMIv2</span>
A number of object definitions in this MIB assumes IPv4 addresses, as
is noted in the note reproduced below:
IESG Note:
The IP, UDP, and TCP MIB modules currently support only IPv4.
These three modules use the IpAddress type defined as an OCTET
STRING of length 4 to represent the IPv4 32-bit internet
addresses. (See <a href="./rfc1902">RFC 1902</a>, SMI for SNMPv2.) They do not support
the new 128-bit IPv6 internet addresses.
<span class="h3"><a class="selflink" id="section-5.29" href="#section-5.29">5.29</a>. <a href="./rfc2013">RFC 2013</a> SNMPv2 Management Information Base for the User</span>
<span class="h3"> Datagram Protocol using SMIv2</span>
A number of object definitions in this MIB assumes IPv4 addresses, as
is noted in the note reproduced below:
IESG Note:
The IP, UDP, and TCP MIB modules currently support only IPv4.
These three modules use the IpAddress type defined as an OCTET
STRING of length 4 to represent the IPv4 32-bit internet
addresses. (See <a href="./rfc1902">RFC 1902</a>, SMI for SNMPv2.) They do not support
the new 128-bit IPv6 internet addresses.
<span class="h3"><a class="selflink" id="section-5.30" href="#section-5.30">5.30</a>. <a href="./rfc2020">RFC 2020</a> IEEE 802.12 Interface MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.31" href="#section-5.31">5.31</a>. <a href="./rfc2021">RFC 2021</a> Remote Network Monitoring Management Information Base</span>
<span class="h3"> Version 2 using SMIv2</span>
The following objects are defined:
addressMapNetworkAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address for this relation.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the
index.
<span class="grey">Nesser II & Bergstrom Informational [Page 15]</span><span id="page-16" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { addressMapEntry 2 }
nlHostAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network address for this nlHostEntry.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlHostEntry 2 }
nlMatrixSDSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network source address for this nlMatrixSDEntry.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlMatrixSDEntry 2 }
nlMatrixSDDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network destination address for this
nlMatrixSDEntry.
<span class="grey">Nesser II & Bergstrom Informational [Page 16]</span><span id="page-17" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlMatrixSDEntry 3 }
nlMatrixDSSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network source address for this nlMatrixDSEntry.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlMatrixDSEntry 2 }
nlMatrixDSDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The network destination address for this
nlMatrixDSEntry.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlMatrixDSEntry 3 }
nlMatrixTopNSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
<span class="grey">Nesser II & Bergstrom Informational [Page 17]</span><span id="page-18" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
STATUS current
DESCRIPTION
"The network layer address of the source host in this
conversation.
This is represented as an octet string with
specific semantics and length as identified
by the associated nlMatrixTopNProtocolDirLocalIndex.
For example, if the protocolDirLocalIndex indicates an
encapsulation of ip, this object is encoded as a length
octet of 4, followed by the 4 octets of the ip address,
in network byte order."
::= { nlMatrixTopNEntry 3 }
nlMatrixTopNDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The network layer address of the destination host in this
conversation.
This is represented as an octet string with
specific semantics and length as identified
by the associated nlMatrixTopNProtocolDirLocalIndex.
For example, if the nlMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip
address, in network byte order."
::= { nlMatrixTopNEntry 4 }
alMatrixTopNSourceAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The network layer address of the source host in this
conversation.
This is represented as an octet string with
specific semantics and length as identified
by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the
ip address, in network byte order."
<span class="grey">Nesser II & Bergstrom Informational [Page 18]</span><span id="page-19" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
::= { alMatrixTopNEntry 3 }
alMatrixTopNDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The network layer address of the destination host in this
conversation.
This is represented as an octet string with
specific semantics and length as identified
by the associated alMatrixTopNProtocolDirLocalIndex.
For example, if the alMatrixTopNProtocolDirLocalIndex
indicates an encapsulation of ip, this object is encoded as a
length octet of 4, followed by the 4 octets of the ip
address, in network byte order."
::= { alMatrixTopNEntry 4 }
trapDestProtocol OBJECT-TYPE
SYNTAX INTEGER {
ip(1),
ipx(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The protocol with which to send this trap."
::= { trapDestEntry 3 }
trapDestAddress OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The address to send traps on behalf of this entry.
If the associated trapDestProtocol object is equal to ip(1),
the encoding of this object is the same as the snmpUDPAddress
textual convention in [<a href="./rfc1906">RFC1906</a>]:
-- for a SnmpUDPAddress of length 6:
--
-- octets contents encoding
-- 1-4 IP-address network-byte order
-- 5-6 UDP-port network-byte order
If the associated trapDestProtocol object is equal to ipx(2),
<span class="grey">Nesser II & Bergstrom Informational [Page 19]</span><span id="page-20" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
the encoding of this object is the same as the snmpIPXAddress
textual convention in [<a href="./rfc1906">RFC1906</a>]:
-- for a SnmpIPXAddress of length 12:
--
-- octets contents encoding
-- 1-4 network-number network-byte order
-- 5-10 physical-address network-byte order
-- 11-12 socket-number network-byte order
This object may not be modified if the associated
trapDestStatus object is equal to active(1)."
::= { trapDestEntry 4 }
All of the object definitions above (except trapDestProtocol) mention
only IPv4 addresses. However, since they use a SYNTAX of OCTET
STRING, they should work fine for IPv6 addresses. A new legitimate
value of trapDestProtocol (i.e., SYNTAX addition of ipv6(3) should
make this specification functional for IPv6.
<span class="h3"><a class="selflink" id="section-5.32" href="#section-5.32">5.32</a>. <a href="./rfc2024">RFC 2024</a> Definitions of Managed Objects for Data Link Switching</span>
<span class="h3"> using SMIv2</span>
The following textual conventions are defined:
TAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a transport service address.
For dlswTCPDomain, a TAddress is 4 octets long,
containing the IP-address in network-byte order."
SYNTAX OCTET STRING (SIZE (0..255))
-- DLSw over TCP
dlswTCPDomain OBJECT IDENTIFIER ::= { dlswDomains 1 }
-- for an IP address of length 4:
--
-- octets contents encoding
-- 1-4 IP-address network-byte order
--
DlswTCPAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d"
STATUS current
DESCRIPTION
"Represents the IP address of a DLSw which uses
TCP as a transport protocol."
SYNTAX OCTET STRING (SIZE (4))
<span class="grey">Nesser II & Bergstrom Informational [Page 20]</span><span id="page-21" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
Additionally there are many object definitions that use a SYNTAX of
TAddress within the document. Interestingly the SYNTAX for TAddress
is an OCTET string of up to 256 characters. It could easily
accommodate a similar hybrid format for IPv6 addresses.
A new OID to enhance functionality for DlswTCPAddress could be added
to support IPv6 addresses.
<span class="h3"><a class="selflink" id="section-5.33" href="#section-5.33">5.33</a>. <a href="./rfc2051">RFC 2051</a> Definitions of Managed Objects for APPC using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.34" href="#section-5.34">5.34</a>. <a href="./rfc2096">RFC 2096</a> IP Forwarding Table MIB</span>
The MIB module's main conceptual table ipCidrRouteTable uses IPv4
addresses as index objects and is therefore incapable of representing
an IPv6 forwarding information base. A new conceptual table needs to
be defined to support IPv6 addresses.
<span class="h3"><a class="selflink" id="section-5.35" href="#section-5.35">5.35</a>. <a href="./rfc2108">RFC 2108</a> Definitions of Managed Objects for IEEE 802.3 Repeater</span>
<span class="h3"> Devices using SMIv2 802</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.36" href="#section-5.36">5.36</a>. <a href="./rfc2127">RFC 2127</a> ISDN Management Information Base using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.37" href="#section-5.37">5.37</a>. <a href="./rfc2128">RFC 2128</a> Dial Control Management Information Base using</span>
<span class="h3"> SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.38" href="#section-5.38">5.38</a>. <a href="./rfc2206">RFC 2206</a> RSVP Management Information Base using SMIv2</span>
All of the relevant object definitions in this MIB have options for
both IPv4 and IPv6. There are no IPv4 dependencies in this
specification.
<span class="h3"><a class="selflink" id="section-5.39" href="#section-5.39">5.39</a>. <a href="./rfc2213">RFC 2213</a> Integrated Services Management Information</span>
<span class="h3"> Base using SMIv2</span>
This MIB is IPv6 aware and therefore there are no IPv4 dependencies
in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 21]</span><span id="page-22" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.40" href="#section-5.40">5.40</a>. <a href="./rfc2214">RFC 2214</a> Integrated Services Management Information</span>
<span class="h3"> Base Guaranteed Service Extensions using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.41" href="#section-5.41">5.41</a>. <a href="./rfc2232">RFC 2232</a> Definitions of Managed Objects for DLUR using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.42" href="#section-5.42">5.42</a>. <a href="./rfc2238">RFC 2238</a> Definitions of Managed Objects for HPR using SMIv2</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.43" href="#section-5.43">5.43</a>. <a href="./rfc2266">RFC 2266</a> Definitions of Managed Objects for IEEE 802.12</span>
<span class="h3"> Repeater Devices</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.44" href="#section-5.44">5.44</a>. <a href="./rfc2287">RFC 2287</a> Definitions of System-Level Managed Objects for</span>
<span class="h3"> Applications</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.45" href="#section-5.45">5.45</a>. <a href="./rfc2320">RFC 2320</a> Definitions of Managed Objects for Classical IP</span>
<span class="h3"> and ARP Over ATM Using SMIv2 (IPOA-MIB)</span>
This MIB is wholly dependent on IPv4. A new MIB for IPv6 is required
to provide the same functionality.
<span class="h3"><a class="selflink" id="section-5.46" href="#section-5.46">5.46</a>. <a href="./rfc2417">RFC 2417</a> Definitions of Managed Objects for Multicast</span>
<span class="h3"> over UNI 3.0/3.1 based ATM Networks</span>
This MIB is wholly dependent on IPv4. A new MIB for IPv6 is required
to provide the same functionality.
<span class="h3"><a class="selflink" id="section-5.47" href="#section-5.47">5.47</a>. <a href="./rfc2452">RFC 2452</a> IP Version 6 Management Information Base for the</span>
<span class="h3"> Transmission Control Protocol</span>
This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion.
<span class="h3"><a class="selflink" id="section-5.48" href="#section-5.48">5.48</a>. <a href="./rfc2454">RFC 2454</a> IP Version 6 Management Information Base for</span>
<span class="h3"> the User Datagram Protocol</span>
This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion.
<span class="grey">Nesser II & Bergstrom Informational [Page 22]</span><span id="page-23" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.49" href="#section-5.49">5.49</a>. <a href="./rfc2455">RFC 2455</a> Definitions of Managed Objects for APPN</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.50" href="#section-5.50">5.50</a>. <a href="./rfc2456">RFC 2456</a> Definitions of Managed Objects for APPN TRAPS</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.51" href="#section-5.51">5.51</a>. <a href="./rfc2457">RFC 2457</a> Definitions of Managed Objects for Extended Border</span>
<span class="h3"> Node</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.52" href="#section-5.52">5.52</a>. <a href="./rfc2465">RFC 2465</a> Management Information Base for IP Version 6:</span>
<span class="h3"> Textual Conventions and General Group</span>
This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion.
<span class="h3"><a class="selflink" id="section-5.53" href="#section-5.53">5.53</a>. <a href="./rfc2466">RFC 2466</a> Management Information Base for IP Version 6:</span>
<span class="h3"> ICMPv6 Group</span>
This RFC documents a soon to be obsoleted IPv6 MIB and is not
considered in this discussion.
<span class="h3"><a class="selflink" id="section-5.54" href="#section-5.54">5.54</a>. <a href="./rfc2494">RFC 2494</a> Definitions of Managed Objects for the DS0</span>
<span class="h3"> and DS0 Bundle Interface Type</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.55" href="#section-5.55">5.55</a>. <a href="./rfc2495">RFC 2495</a> Definitions of Managed Objects for the DS1, E1,</span>
<span class="h3"> DS2 and E2 Interface Types</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.56" href="#section-5.56">5.56</a>. <a href="./rfc2496">RFC 2496</a> Definitions of Managed Object for the DS3/E3</span>
<span class="h3"> Interface Type</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.57" href="#section-5.57">5.57</a>. <a href="./rfc2512">RFC 2512</a> Accounting Information for ATM Networks</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 23]</span><span id="page-24" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.58" href="#section-5.58">5.58</a>. <a href="./rfc2513">RFC 2513</a> Managed Objects for Controlling the Collection</span>
<span class="h3"> and Storage of Accounting Information for</span>
Connection-Oriented Networks
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.59" href="#section-5.59">5.59</a>. <a href="./rfc2514">RFC 2514</a> Definitions of Textual Conventions and</span>
<span class="h3"> OBJECT-IDENTITIES for ATM Management</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.60" href="#section-5.60">5.60</a>. <a href="./rfc2515">RFC 2515</a> Definitions of Managed Objects for ATM Management</span>
This MIB defines the following objects:
AtmInterfaceConfEntry ::= SEQUENCE {
atmInterfaceMaxVpcs INTEGER,
atmInterfaceMaxVccs INTEGER,
atmInterfaceConfVpcs INTEGER,
atmInterfaceConfVccs INTEGER,
atmInterfaceMaxActiveVpiBits INTEGER,
atmInterfaceMaxActiveVciBits INTEGER,
atmInterfaceIlmiVpi AtmVpIdentifier,
atmInterfaceIlmiVci AtmVcIdentifier,
atmInterfaceAddressType INTEGER,
atmInterfaceAdminAddress AtmAddr,
atmInterfaceMyNeighborIpAddress IpAddress,
atmInterfaceMyNeighborIfName DisplayString,
atmInterfaceCurrentMaxVpiBits INTEGER,
atmInterfaceCurrentMaxVciBits INTEGER,
atmInterfaceSubscrAddress AtmAddr
}
atmInterfaceMyNeighborIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The IP address of the neighbor system connected to
the far end of this interface, to which a Network
Management Station can send SNMP messages, as IP
datagrams sent to UDP port 161, in order to access
network management information concerning the
operation of that system. Note that the value
of this object may be obtained in different ways,
e.g., by manual configuration, or through ILMI
interaction with the neighbor system."
::= { atmInterfaceConfEntry 11 }
<span class="grey">Nesser II & Bergstrom Informational [Page 24]</span><span id="page-25" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
atmInterfaceConfGroup2 OBJECT-GROUP
OBJECTS {
atmInterfaceMaxVpcs, atmInterfaceMaxVccs,
atmInterfaceConfVpcs, atmInterfaceConfVccs,
atmInterfaceMaxActiveVpiBits,
atmInterfaceMaxActiveVciBits,
atmInterfaceIlmiVpi,
atmInterfaceIlmiVci,
atmInterfaceMyNeighborIpAddress,
atmInterfaceMyNeighborIfName,
atmInterfaceCurrentMaxVpiBits,
atmInterfaceCurrentMaxVciBits,
atmInterfaceSubscrAddress }
STATUS current
DESCRIPTION
"A collection of objects providing configuration
information about an ATM interface."
::= { atmMIBGroups 10 }
Clearly a subsequent revision of this MIB module should define
equivalent IPv6 objects.
<span class="h3"><a class="selflink" id="section-5.61" href="#section-5.61">5.61</a>. <a href="./rfc2561">RFC 2561</a> Base Definitions of Managed Objects for TN3270E</span>
<span class="h3"> Using SMIv2</span>
The document states:
The MIB defined by this memo supports use of both IPv4 and IPv6
addressing.
This specification is both IPv4 and IPv6 aware.
<span class="h3"><a class="selflink" id="section-5.62" href="#section-5.62">5.62</a>. <a href="./rfc2562">RFC 2562</a> Definitions of Protocol and Managed Objects for</span>
<span class="h3"> TN3270E Response Time Collection Using SMIv2</span>
This MIB module inherits IP version-independence by virtue of
importing the appropriate definitions from <a href="./rfc2561">RFC 2561</a>.
<span class="h3"><a class="selflink" id="section-5.63" href="#section-5.63">5.63</a>. <a href="./rfc2564">RFC 2564</a> Application Management MIB</span>
The following textual convention is defined:
ApplTAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a transport service address.
For snmpUDPDomain, an ApplTAddress is 6 octets long,
<span class="grey">Nesser II & Bergstrom Informational [Page 25]</span><span id="page-26" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
the initial 4 octets containing the IP-address in
network-byte order and the last 2 containing the UDP
port in network-byte order. Consult 'Transport Mappings
for Version 2 of the Simple Network Management Protocol
(SNMPv2)' for further information on snmpUDPDomain."
SYNTAX OCTET STRING (SIZE (0..255))
A new TC should be defined to handle IPv6 addresses.
<span class="h3"><a class="selflink" id="section-5.64" href="#section-5.64">5.64</a>. <a href="./rfc2584">RFC 2584</a> Definitions of Managed Objects for APPN/HPR in</span>
<span class="h3"> IP Networks</span>
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
nature and will not support IPv6.
<span class="h3"><a class="selflink" id="section-5.65" href="#section-5.65">5.65</a>. <a href="./rfc2594">RFC 2594</a> Definitions of Managed Objects for WWW Services</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.66" href="#section-5.66">5.66</a>. <a href="./rfc2605">RFC 2605</a> Directory Server Monitoring MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.67" href="#section-5.67">5.67</a>. <a href="./rfc2613">RFC 2613</a> Remote Network Monitoring MIB Extensions for</span>
<span class="h3"> Switched Networks Version 1.0</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.68" href="#section-5.68">5.68</a>. <a href="./rfc2618">RFC 2618</a> RADIUS Authentication Client MIB</span>
This RFC defines the following objects:
RadiusAuthServerEntry ::= SEQUENCE {
radiusAuthServerIndex Integer32,
radiusAuthServerAddress IpAddress,
radiusAuthClientServerPortNumber Integer32,
radiusAuthClientRoundTripTime TimeTicks,
radiusAuthClientAccessRequests Counter32,
radiusAuthClientAccessRetransmissions Counter32,
radiusAuthClientAccessAccepts Counter32,
radiusAuthClientAccessRejects Counter32,
radiusAuthClientAccessChallenges Counter32,
radiusAuthClientMalformedAccessResponses Counter32,
radiusAuthClientBadAuthenticators Counter32,
radiusAuthClientPendingRequests Gauge32,
radiusAuthClientTimeouts Counter32,
radiusAuthClientUnknownTypes Counter32,
<span class="grey">Nesser II & Bergstrom Informational [Page 26]</span><span id="page-27" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
radiusAuthClientPacketsDropped Counter32
}
radiusAuthServerAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the RADIUS authentication server
referred to in this table entry."
::= { radiusAuthServerEntry 2 }
There needs to be an update to allow an IPv6 based object for this
value.
<span class="h3"><a class="selflink" id="section-5.69" href="#section-5.69">5.69</a>. <a href="./rfc2619">RFC 2619</a> RADIUS Authentication Server MIB</span>
This MIB defines the followings objects:
RadiusAuthClientEntry ::= SEQUENCE {
radiusAuthClientIndex Integer32,
radiusAuthClientAddress IpAddress,
radiusAuthClientID SnmpAdminString,
radiusAuthServAccessRequests Counter32,
radiusAuthServDupAccessRequests Counter32,
radiusAuthServAccessAccepts Counter32,
radiusAuthServAccessRejects Counter32,
radiusAuthServAccessChallenges Counter32,
radiusAuthServMalformedAccessRequests Counter32,
radiusAuthServBadAuthenticators Counter32,
radiusAuthServPacketsDropped Counter32,
radiusAuthServUnknownTypes Counter32
}
radiusAuthClientAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-IP-Address of the RADIUS authentication client
referred to in this table entry."
::= { radiusAuthClientEntry 2 }
This object needs to be deprecated and replaced by one that supports
both IPv4 and IPv6 addresses.
<span class="grey">Nesser II & Bergstrom Informational [Page 27]</span><span id="page-28" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.70" href="#section-5.70">5.70</a>. <a href="./rfc2622">RFC 2622</a> Routing Policy Specification Language (RPSL)</span>
The only objects in the version of RPSL that deal with IP addresses
are defined as:
<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
".". 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
addresses.
<address-prefix> An address prefix is represented as an IPv4 address
followed by the character slash "/" followed by an integer in the
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
prefixes are invalid: 0/0, 128.9/16 since 0 or 128.9 are not
strings containing four integers.
There seems to be an awareness of IPv6 because of the terminology but
it is not specifically defined. Therefore additional objects for
IPv6 addresses and prefixes need to be defined.
<span class="h3"><a class="selflink" id="section-5.71" href="#section-5.71">5.71</a>. <a href="./rfc2662">RFC 2662</a> Definitions of Managed Objects for the ADSL Lines</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.72" href="#section-5.72">5.72</a>. <a href="./rfc2667">RFC 2667</a> IP Tunnel MIB</span>
The Abstract of this document says:
This memo defines a Management Information Base (MIB) for use with
network management protocols in the Internet community. In
particular, it describes managed objects used for managing tunnels
of any type over IPv4 networks. Extension MIBs may be designed
for managing protocol-specific objects. Likewise, extension MIBs
may be designed for managing security-specific objects. This MIB
does not support tunnels over non-IPv4 networks (including IPv6
networks). Management of such tunnels may be supported by other
MIBs.
A similar MIB for tunneling over IPv6 should be defined.
<span class="grey">Nesser II & Bergstrom Informational [Page 28]</span><span id="page-29" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.73" href="#section-5.73">5.73</a>. <a href="./rfc2669">RFC 2669</a> DOCSIS Cable Device MIB Cable Device Management</span>
<span class="h3"> Information Base for DOCSIS compliant Cable Modems and</span>
Cable Modem Termination Systems
This document states:
Please note that the DOCSIS 1.0 standard only requires Cable
Modems to implement SNMPv1 and to process IPv4 customer traffic.
Design choices in this MIB reflect those requirements. Future
versions of the DOCSIS standard are expected to require support
for SNMPv3 and IPv6 as well.
<span class="h3"><a class="selflink" id="section-5.74" href="#section-5.74">5.74</a>. <a href="./rfc2670">RFC 2670</a> Radio Frequency (RF) Interface Management Information</span>
<span class="h3"> Base for MCNS/DOCSIS compliant RF interfaces</span>
This MIB defines the following objects:
DocsIfCmtsCmStatusEntry ::= SEQUENCE {
docsIfCmtsCmStatusIndex Integer32,
docsIfCmtsCmStatusMacAddress MacAddress,
docsIfCmtsCmStatusIpAddress IpAddress,
docsIfCmtsCmStatusDownChannelIfIndex InterfaceIndexOrZero,
docsIfCmtsCmStatusUpChannelIfIndex InterfaceIndexOrZero,
docsIfCmtsCmStatusRxPower TenthdBmV,
docsIfCmtsCmStatusTimingOffset Unsigned32,
docsIfCmtsCmStatusEqualizationData OCTET STRING,
docsIfCmtsCmStatusValue INTEGER,
docsIfCmtsCmStatusUnerroreds Counter32,
docsIfCmtsCmStatusCorrecteds Counter32,
docsIfCmtsCmStatusUncorrectables Counter32,
docsIfCmtsCmStatusSignalNoise TenthdB,
docsIfCmtsCmStatusMicroreflections Integer32
}
docsIfCmtsCmStatusIpAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"IP address of this Cable Modem. If the Cable Modem has no
IP address assigned, or the IP address is unknown, this
object returns a value of 0.0.0.0. If the Cable Modem has
multiple IP addresses, this object returns the IP address
associated with the Cable interface."
::= { docsIfCmtsCmStatusEntry 3 }
This object needs to be deprecated and replaced by one that supports
both IPv4 and IPv6 addresses.
<span class="grey">Nesser II & Bergstrom Informational [Page 29]</span><span id="page-30" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.75" href="#section-5.75">5.75</a>. <a href="./rfc2674">RFC 2674</a> Definitions of Managed Objects for Bridges with</span>
<span class="h3"> Traffic Classes, Multicast Filtering and Virtual LAN</span>
Extensions
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.76" href="#section-5.76">5.76</a>. <a href="./rfc2677">RFC 2677</a> Definitions of Managed Objects for the NBMA Next</span>
<span class="h3"> Hop Resolution Protocol (NHRP)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.77" href="#section-5.77">5.77</a>. <a href="./rfc2720">RFC 2720</a> Traffic Flow Measurement: Meter MIB</span>
This specification is both IPv4 and IPv6 aware and needs no changes.
<span class="h3"><a class="selflink" id="section-5.78" href="#section-5.78">5.78</a>. <a href="./rfc2725">RFC 2725</a> Routing Policy System Security</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.79" href="#section-5.79">5.79</a>. <a href="./rfc2726">RFC 2726</a> PGP Authentication for RIPE Database Updates</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.80" href="#section-5.80">5.80</a>. <a href="./rfc2737">RFC 2737</a> Entity MIB (Version 2)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.81" href="#section-5.81">5.81</a>. <a href="./rfc2741">RFC 2741</a> Agent Extensibility (AgentX) Protocol Version 1</span>
Although the examples in the document are for IPv4 transport only,
there is no IPv4 dependency in the AgentX protocol itself.
<span class="h3"><a class="selflink" id="section-5.82" href="#section-5.82">5.82</a>. <a href="./rfc2742">RFC 2742</a> Definitions of Managed Objects for Extensible SNMP</span>
<span class="h3"> Agents</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.83" href="#section-5.83">5.83</a>. <a href="./rfc2748">RFC 2748</a> The COPS (Common Open Policy Service) Protocol</span>
This specification is both IPv4 and IPv6 aware and needs no changes.
<span class="h3"><a class="selflink" id="section-5.84" href="#section-5.84">5.84</a>. <a href="./rfc2749">RFC 2749</a> COPS usage for RSVP</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.85" href="#section-5.85">5.85</a>. <a href="./rfc2769">RFC 2769</a> Routing Policy System Replication</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 30]</span><span id="page-31" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.86" href="#section-5.86">5.86</a>. <a href="./rfc2787">RFC 2787</a> Definitions of Managed Objects for the Virtual</span>
<span class="h3"> Router Redundancy Protocol</span>
As stated in the Overview section:
Since the VRRP protocol is intended for use with IPv4 routers
only, this MIB uses the SYNTAX for IP addresses which is specific
to IPv4. Thus, changes will be required for this MIB to
interoperate in an IPv6 environment.
<span class="h3"><a class="selflink" id="section-5.87" href="#section-5.87">5.87</a>. <a href="./rfc2788">RFC 2788</a> Network Services Monitoring MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.88" href="#section-5.88">5.88</a>. <a href="./rfc2789">RFC 2789</a> Mail Monitoring MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.89" href="#section-5.89">5.89</a>. <a href="./rfc2837">RFC 2837</a> Definitions of Managed Objects for the Fabric Element</span>
<span class="h3"> in Fibre Channel Standard</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.90" href="#section-5.90">5.90</a>. <a href="./rfc2856">RFC 2856</a> Textual Conventions for Additional High Capacity</span>
<span class="h3"> Data Types</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.91" href="#section-5.91">5.91</a>. <a href="./rfc2864">RFC 2864</a> The Inverted Stack Table Extension to the Interfaces</span>
<span class="h3"> Group MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.92" href="#section-5.92">5.92</a>. <a href="./rfc2895">RFC 2895</a> Remote Network Monitoring MIB Protocol Identifier</span>
<span class="h3"> Reference</span>
This specification is both IPv4 and IPv6 aware and needs no changes.
<span class="h3"><a class="selflink" id="section-5.93" href="#section-5.93">5.93</a>. <a href="./rfc2925">RFC 2925</a> Definitions of Managed Objects for Remote</span>
<span class="h3"> Ping, Traceroute, and Lookup Operations</span>
This MIB mostly is IPv4 and IPv6 aware. There are a few assumptions
that are problems, though. In the following object definitions:
pingCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
<span class="grey">Nesser II & Bergstrom Informational [Page 31]</span><span id="page-32" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
STATUS current
DESCRIPTION
"Specifies the size of the data portion to be
transmitted in a ping operation in octets. A ping
request is usually an ICMP message encoded
into an IP packet. An IP packet has a maximum size
of 65535 octets. Subtracting the size of the ICMP
or UDP header (both 8 octets) and the size of the IP
header (20 octets) yields a maximum size of 65507
octets."
DEFVAL { 0 }
::= { pingCtlEntry 5 }
traceRouteCtlDataSize OBJECT-TYPE
SYNTAX Unsigned32 (0..65507)
UNITS "octets"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Specifies the size of the data portion of a traceroute
request in octets. A traceroute request is essentially
transmitted by encoding a UDP datagram into a
IP packet. So subtracting the size of a UDP header
(8 octets) and the size of a IP header (20 octets)
yields a maximum of 65507 octets."
DEFVAL { 0 }
::= { traceRouteCtlEntry 6 }
The DESCRIPTION clauses need to be updated to remove the IPv4
dependencies.
<span class="h3"><a class="selflink" id="section-5.94" href="#section-5.94">5.94</a>. <a href="./rfc2932">RFC 2932</a> IPv4 Multicast Routing MIB</span>
This specification is only defined for IPv4 and a similar MIB must be
defined for IPv6.
<span class="h3"><a class="selflink" id="section-5.95" href="#section-5.95">5.95</a>. <a href="./rfc2933">RFC 2933</a> Internet Group Management Protocol MIB</span>
As stated in this document:
Since IGMP is specific to IPv4, this MIB does not support
management of equivalent functionality for other address families,
such as IPv6.
<span class="grey">Nesser II & Bergstrom Informational [Page 32]</span><span id="page-33" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.96" href="#section-5.96">5.96</a>. <a href="./rfc2940">RFC 2940</a> Definitions of Managed Objects for Common</span>
<span class="h3"> Open Policy Service (COPS) Protocol Clients</span>
This MIB is both IPv4 and IPv6 aware and needs no changes.
<span class="h3"><a class="selflink" id="section-5.97" href="#section-5.97">5.97</a>. <a href="./rfc2954">RFC 2954</a> Definitions of Managed Objects for Frame</span>
<span class="h3"> Relay Service</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.98" href="#section-5.98">5.98</a>. <a href="./rfc2955">RFC 2955</a> Definitions of Managed Objects for Monitoring</span>
<span class="h3"> and Controlling the Frame Relay/ATM PVC Service</span>
Interworking Function
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.99" href="#section-5.99">5.99</a>. <a href="./rfc2959">RFC 2959</a> Real-Time Transport Protocol Management Information Base</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.100" href="#section-5.100">5.100</a>. <a href="./rfc2981">RFC 2981</a> Event MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.101" href="#section-5.101">5.101</a>. <a href="./rfc2982">RFC 2982</a> Distributed Management Expression MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.102" href="#section-5.102">5.102</a>. <a href="./rfc3014">RFC 3014</a> Notification Log MIB</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.103" href="#section-5.103">5.103</a>. <a href="./rfc3019">RFC 3019</a> IP Version 6 Management Information Base for</span>
<span class="h3"> The Multicast Listener Discovery Protocol</span>
This is an IPv6 related document and is not discussed in this
document.
<span class="h3"><a class="selflink" id="section-5.104" href="#section-5.104">5.104</a>. <a href="./rfc3020">RFC 3020</a> Definitions of Managed Objects for Monitoring</span>
<span class="h3"> and Controlling the UNI/NNI Multilink Frame Relay Function</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.105" href="#section-5.105">5.105</a>. <a href="./rfc3055">RFC 3055</a> Management Information Base for the PINT Services</span>
<span class="h3"> Architecture</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 33]</span><span id="page-34" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-5.106" href="#section-5.106">5.106</a>. <a href="./rfc3060">RFC 3060</a> Policy Core Information Model -- Version 1</span>
<span class="h3"> Specification (CIM)</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.107" href="#section-5.107">5.107</a>. <a href="./rfc3084">RFC 3084</a> COPS Usage for Policy Provisioning (COPS-PR)</span>
This specification builds on <a href="./rfc2748">RFC 2748</a>, and is both IPv4 and IPv6
capable. The specification defines a sample filter in <a href="#section-4.3">section 4.3</a>,
which has "ipv4" in it.
<span class="h3"><a class="selflink" id="section-5.108" href="#section-5.108">5.108</a>. <a href="./rfc3165">RFC 3165</a> Definitions of Managed Objects for the Delegation of</span>
<span class="h3"> Management Scripts</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.109" href="#section-5.109">5.109</a>. <a href="./rfc3231">RFC 3231</a> Definitions of Managed Objects for Scheduling</span>
<span class="h3"> Management Operations</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.110" href="#section-5.110">5.110</a>. <a href="./rfc3291">RFC 3291</a> Textual Conventions for Internet Network Addresses</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.111" href="#section-5.111">5.111</a>. <a href="./rfc3635">RFC 3635</a> Definitions of Managed Objects for the</span>
<span class="h3"> Ethernet-like Interface Types</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-5.112" href="#section-5.112">5.112</a>. <a href="./rfc3636">RFC 3636</a> Definitions of Managed Objects for IEEE 802.3 Medium</span>
<span class="h3"> Attachment Units (MAUs)</span>
There are no IPv4 dependencies in this specification.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Experimental RFCs</span>
Experimental RFCs typically define protocols that do not have
widescale implementation or usage on the Internet. They are often
propriety in nature or used in limited arenas. They are documented
to the Internet community in order to allow potential
interoperability or some other potential useful scenario. In a few
cases, they are presented as alternatives to the mainstream solution
to an acknowledged problem.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. <a href="./rfc1187">RFC 1187</a> Bulk Table Retrieval with the SNMP</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 34]</span><span id="page-35" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. <a href="./rfc1224">RFC 1224</a> Techniques for managing asynchronously generated</span>
<span class="h3"> alerts</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. <a href="./rfc1238">RFC 1238</a> CLNS MIB for use with Connectionless Network Protocol</span>
(ISO 8473) and End System to Intermediate System (ISO 9542)
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. <a href="./rfc1592">RFC 1592</a> Simple Network Management Protocol Distributed Protocol</span>
<span class="h3"> Interface Version 2.0</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. <a href="./rfc1792">RFC 1792</a> TCP/IPX Connection Mib Specification</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. <a href="./rfc2724">RFC 2724</a> RTFM: New Attributes for Traffic Flow Measurement</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.7" href="#section-6.7">6.7</a>. <a href="./rfc2758">RFC 2758</a> Definitions of Managed Objects for Service Level</span>
<span class="h3"> Agreements Performance Monitoring</span>
This specification is both IPv4 and IPv6 aware and needs no changes.
<span class="h3"><a class="selflink" id="section-6.8" href="#section-6.8">6.8</a>. <a href="./rfc2786">RFC 2786</a> Diffie-Helman USM Key Management Information Base and</span>
<span class="h3"> Textual Convention</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.9" href="#section-6.9">6.9</a>. <a href="./rfc2903">RFC 2903</a> Generic AAA Architecture</span>
There are no IPv4 dependencies in this specification.
<span class="h3"><a class="selflink" id="section-6.10" href="#section-6.10">6.10</a>. <a href="./rfc2934">RFC 2934</a> Protocol Independent Multicast MIB for IPv4</span>
This document is specific to IPv4.
<span class="h3"><a class="selflink" id="section-6.11" href="#section-6.11">6.11</a>. <a href="./rfc3179">RFC 3179</a> Script MIB Extensibility Protocol Version 1.1</span>
There are no IPv4 dependencies in this specification.
<span class="grey">Nesser II & Bergstrom Informational [Page 35]</span><span id="page-36" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Summary of Results</span>
In the initial survey of RFCs, 36 positives were identified out of a
total of 153, broken down as follows:
Standards: 6 out of 15 or 40.00%
Draft Standards: 4 out of 15 or 26.67%
Proposed Standards: 26 out of 112 or 23.21%
Experimental RFCs: 0 out of 11 or 0.00%
Of those identified, many require no action because they document
outdated and unused protocols, while others are document protocols
that are actively being updated by the appropriate working groups.
Additionally there are many instances of standards that should be
updated but do not cause any operational impact if they are not
updated. The remaining instances are documented below.
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Standards</span>
<span class="h4"><a class="selflink" id="section-7.1.1" href="#section-7.1.1">7.1.1</a>. STD 16, Structure of Management Information (RFCs 1155 and 1212)</span>
<a href="./rfc1155">RFC 1155</a> and <a href="./rfc1212">RFC 1212</a> (along with the informational document <a href="./rfc1215">RFC</a>
<a href="./rfc1215">1215</a>) define SMIv1. These documents have been superseded by RFCs
2578, 2579, and 2580 which define SMIv2. Since SMIv1 is no longer
being used as the basis for new IETF MIB modules, the limitations
identified in this Internet Standard do not require any action.
<span class="h4"><a class="selflink" id="section-7.1.2" href="#section-7.1.2">7.1.2</a>. STD 17 Simple Network Management Protocol (<a href="./rfc1213">RFC 1213</a>)</span>
The limitations identified have been addressed, because <a href="./rfc1213">RFC 1213</a> has
been split into multiple modules which are all IPv6 capable.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Draft Standards</span>
<span class="h4"><a class="selflink" id="section-7.2.1" href="#section-7.2.1">7.2.1</a>. BGP4 MIB (<a href="./rfc1657">RFC 1657</a>)</span>
This problem is currently being addressed by the Inter Domain Routing
(IDR) WG [<a href="#ref-2" title=""Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4)"">2</a>].
<span class="h4"><a class="selflink" id="section-7.2.2" href="#section-7.2.2">7.2.2</a>. SMDS MIB (<a href="./rfc1694">RFC 1694</a>)</span>
See Internet Area standards. Once a specification for IPv6 over SMDS
is created a new MIB must be defined.
<span class="h4"><a class="selflink" id="section-7.2.3" href="#section-7.2.3">7.2.3</a>. RIPv2 MIB (<a href="./rfc1724">RFC 1724</a>)</span>
There is no updated MIB module to cover the problems outlined. A new
MIB module should be defined.
<span class="grey">Nesser II & Bergstrom Informational [Page 36]</span><span id="page-37" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h4"><a class="selflink" id="section-7.2.4" href="#section-7.2.4">7.2.4</a>. OSPFv2 MIB (<a href="./rfc1850">RFC 1850</a>)</span>
This problem is currently being addressed by the OSPF WG [<a href="#ref-3" title=""Management Information Base for OSPFv3"">3</a>].
<span class="h4"><a class="selflink" id="section-7.2.5" href="#section-7.2.5">7.2.5</a>. Transport MIB (<a href="./rfc1906">RFC 1906</a>)</span>
<a href="./rfc1906">RFC 1906</a> has been obsoleted by <a href="./rfc3417">RFC 3417</a>, Transport Mappings for SNMP,
and the limitations of this specification have been addressed by that
RFC, which defines TCs that can be used to specify transport domains
in an IP version-independent way. <a href="./rfc3419">RFC 3419</a> recommends that those TCs
be used in place of SnmpUDPAddress when IPv6 support is required and
for all new applications that are not SNMP-specific.
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Proposed Standards</span>
<span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a>. MIB for Multiprotocol Interconnect over X.25 (<a href="./rfc1461">RFC 1461</a>)</span>
This problem has not been addressed. If a user requirement for IPv6
over X.25 develops (which is thought to be unlikely) then this MIB
module will need to be updated in order to accommodate it.
<span class="h4"><a class="selflink" id="section-7.3.2" href="#section-7.3.2">7.3.2</a>. PPP IPCP MIB (<a href="./rfc1473">RFC 1473</a>)</span>
There is no updated MIB to cover the problems outlined. A new MIB
should be defined.
<span class="h4"><a class="selflink" id="section-7.3.3" href="#section-7.3.3">7.3.3</a>. Appletalk MIB (<a href="./rfc1742">RFC 1742</a>)</span>
This problem has not been addressed. If a user requirement for IPv6
over Appletalk develops (which is thought to be unlikely) then this
MIB module will need to be updated (or a new MIB module will need to
be created) in order to accommodate it.
<span class="h4"><a class="selflink" id="section-7.3.4" href="#section-7.3.4">7.3.4</a>. The Definitions of Managed Objects for IP Mobility</span>
<span class="h4"> Support using SMIv2 (<a href="./rfc2006">RFC 2006</a>)</span>
The problems are being resolved by the MIP6 WG [<a href="#ref-4" title=""The Mobile IPv6 MIB"">4</a>].
<span class="h4"><a class="selflink" id="section-7.3.5" href="#section-7.3.5">7.3.5</a>. SMIv2 IP MIB (<a href="./rfc2011">RFC 2011</a>)</span>
This issue is being resolved by the IPv6 WG [<a href="#ref-5" title=""Management Information Base for the Internet Protocol (IP)"">5</a>].
<span class="h4"><a class="selflink" id="section-7.3.6" href="#section-7.3.6">7.3.6</a>. SNMPv2 TCP MIB (<a href="./rfc2012">RFC 2012</a>)</span>
This issue is being resolved by the IPv6 WG [<a href="#ref-6" title=""Management Information Base for the Transmission Control Protocol (TCP)"">6</a>].
<span class="grey">Nesser II & Bergstrom Informational [Page 37]</span><span id="page-38" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h4"><a class="selflink" id="section-7.3.7" href="#section-7.3.7">7.3.7</a>. SNMPv2 UDP MIB (<a href="./rfc2013">RFC 2013</a>)</span>
This issue is being resolved by the IPv6 WG [<a href="#ref-7" title=""Management Information Base for the User Datagram Protocol (UDP)"">7</a>].
<span class="h4"><a class="selflink" id="section-7.3.8" href="#section-7.3.8">7.3.8</a>. RMON-II MIB (<a href="./rfc2021">RFC 2021</a>)</span>
This issue has been brought to the attention of the RMONMIB WG.
Currently, there is a work in progress [<a href="#ref-8" title=""Remote Network Monitoring Management Information Base Version 2 Using SMIv2"">8</a>] to update <a href="./rfc2021">RFC 2021</a>, but it
does not address the problems that have been identified; it is
expected that there will be a resolution in a future version of that
document.
<span class="h4"><a class="selflink" id="section-7.3.9" href="#section-7.3.9">7.3.9</a>. DataLink Switching using SMIv2 MIB (<a href="./rfc2024">RFC 2024</a>)</span>
The problems have not been addressed and an updated MIB should be
defined.
<span class="h4"><a class="selflink" id="section-7.3.10" href="#section-7.3.10">7.3.10</a>. IP Forwarding Table MIB (<a href="./rfc2096">RFC 2096</a>)</span>
This issue is being worked on by the IPv6 WG [<a href="#ref-9" title=""IP Forwarding Table MIB"">9</a>].
<span class="h4"><a class="selflink" id="section-7.3.11" href="#section-7.3.11">7.3.11</a>. Classical IP & ARP over ATM MIB (<a href="./rfc2320">RFC 2320</a>)</span>
The current version of Classical IP and ARP over ATM (<a href="./rfc2225">RFC 2225</a>) does
not support IPv6. If and when that protocol specification is updated
to add IPv6 support, then new MIB objects to represent IPv6 addresses
will need to be added to this MIB module.
<span class="h4"><a class="selflink" id="section-7.3.12" href="#section-7.3.12">7.3.12</a>. Multicast over UNI 3.0/3.1 ATM MIB (<a href="./rfc2417">RFC 2417</a>)</span>
The current version of Multicast over UNI 3.0/3.1 ATM (<a href="./rfc2022">RFC 2022</a>) does
not support IPv6. If and when that protocol specification is updated
to add IPv6 support, then new MIB objects to represent IPv6 addresses
will need to be added to this MIB module.
<span class="h4"><a class="selflink" id="section-7.3.13" href="#section-7.3.13">7.3.13</a>. ATM MIB (<a href="./rfc2515">RFC 2515</a>)</span>
The AToM MIB WG is currently collecting implementation reports for
<a href="./rfc2515">RFC 2515</a> and is considering whether to advance, revise, or retire
this specification. The problems identified have been brought to the
attention of the WG.
<span class="h4"><a class="selflink" id="section-7.3.14" href="#section-7.3.14">7.3.14</a>. TN3270 MIB (<a href="./rfc2562">RFC 2562</a>)</span>
The problems identified are not being addressed and a new MIB module
may need to be defined.
<span class="grey">Nesser II & Bergstrom Informational [Page 38]</span><span id="page-39" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h4"><a class="selflink" id="section-7.3.15" href="#section-7.3.15">7.3.15</a>. Application MIB (<a href="./rfc2564">RFC 2564</a>)</span>
The problems identified are not being addressed and a new MIB module
may need to be defined. One possible solution might be to use the
<a href="./rfc3419">RFC 3419</a> TCs.
<span class="h4"><a class="selflink" id="section-7.3.16" href="#section-7.3.16">7.3.16</a>. Definitions of Managed Objects for APPN/HPR in IP Networks</span>
(<a href="./rfc2584">RFC 2584</a>)
The problems identified are not addressed and a new MIB may be
defined.
<span class="h4"><a class="selflink" id="section-7.3.17" href="#section-7.3.17">7.3.17</a>. RADIUS MIB (<a href="./rfc2618">RFC 2618</a>)</span>
The problems have not been addressed and a new MIB should be defined.
<span class="h4"><a class="selflink" id="section-7.3.18" href="#section-7.3.18">7.3.18</a>. RADIUS Authentication Server MIB (<a href="./rfc2619">RFC 2619</a>)</span>
The problems have not been addressed and a new MIB should be defined.
<span class="h4"><a class="selflink" id="section-7.3.19" href="#section-7.3.19">7.3.19</a>. RPSL (<a href="./rfc2622">RFC 2622</a>)</span>
Additional objects must be defined for IPv6 addresses and prefixes.
[<a id="ref-10">10</a>] defines extensions to solve this issue, and it is being
considered for publication.
<span class="h4"><a class="selflink" id="section-7.3.20" href="#section-7.3.20">7.3.20</a>. IPv4 Tunnel MIB (<a href="./rfc2667">RFC 2667</a>)</span>
The issue is being resolved.
<span class="h4"><a class="selflink" id="section-7.3.21" href="#section-7.3.21">7.3.21</a>. DOCSIS MIB (<a href="./rfc2669">RFC 2669</a>)</span>
This problem is currently being addressed by the IPCDN WG.
<span class="h4"><a class="selflink" id="section-7.3.22" href="#section-7.3.22">7.3.22</a>. RF MIB For DOCSIS (<a href="./rfc2670">RFC 2670</a>)</span>
This problem is currently being addressed by the IPCDN WG [<a href="#ref-11" title=""Radio Frequency (RF) Interface Management Information Base for DOCSIS 2.0 compliant RF interfaces"">11</a>].
<span class="h4"><a class="selflink" id="section-7.3.23" href="#section-7.3.23">7.3.23</a>. VRRP MIB (<a href="./rfc2787">RFC 2787</a>)</span>
The problems have not been addressed and a new MIB may need to be
defined.
<span class="h4"><a class="selflink" id="section-7.3.24" href="#section-7.3.24">7.3.24</a>. MIB For Traceroute, Pings and Lookups (<a href="./rfc2925">RFC 2925</a>)</span>
The problems have not been addressed and a new MIB may need to be
defined.
<span class="grey">Nesser II & Bergstrom Informational [Page 39]</span><span id="page-40" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h4"><a class="selflink" id="section-7.3.25" href="#section-7.3.25">7.3.25</a>. IPv4 Multicast Routing MIB (<a href="./rfc2932">RFC 2932</a>)</span>
The problems have not been addressed a new MIB must be defined.
<span class="h4"><a class="selflink" id="section-7.3.26" href="#section-7.3.26">7.3.26</a>. IGMP MIB (<a href="./rfc2933">RFC 2933</a>)</span>
This problem is currently being addressed by the MAGMA WG [<a href="#ref-12" title=""Multicast Group Membership Discovery MIB"">12</a>].
<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>. Experimental RFCs</span>
<span class="h4"><a class="selflink" id="section-7.4.1" href="#section-7.4.1">7.4.1</a>. Protocol Independent Multicast MIB for IPv4 (<a href="./rfc2934">RFC 2934</a>)</span>
The problems have not been addressed and a new MIB may need to be
defined.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
This memo examines the IPv6-readiness of specifications; this does
not have security considerations in itself.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
The authors would like to acknowledge the support of the Internet
Society in the research and production of this document.
Additionally the author, Philip J. Nesser II, would like to thank his
partner in all ways, Wendy M. Nesser.
The editor, Andreas Bergstrom, would like to thank Pekka Savola for
his guidance and collection of comments for the editing of this
document. He would further like to thank Juergen Schoenwaelder,
Brian Carpenter, Bert Wijnen and especially C. M. Heard for feedback
on many points of this document.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative Reference</span>
[<a id="ref-1">1</a>] Nesser, II, P. and A. Bergstrom, Editor, "Introduction to the
Survey of IPv4 Addresses in Currently Deployed IETF Standards",
<a href="./rfc3789">RFC 3789</a>, June 2004.
<span class="grey">Nesser II & Bergstrom Informational [Page 40]</span><span id="page-41" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-2">2</a>] Haas, J. and S. Hares, Editors, "Definitions of Managed Objects
for the Fourth Version of Border Gateway Protocol (BGP-4)", Work
in Progress, April 2004.
[<a id="ref-3">3</a>] Joyal, D. and V. Manral, "Management Information Base for
OSPFv3", Work in Progress, April 2004.
[<a id="ref-4">4</a>] Keeni, G., Koide, K., Nagami, K. and S. Gundavelli, "The Mobile
IPv6 MIB", Work in Progress, February 2004.
[<a id="ref-5">5</a>] Routhier, S., Editor, "Management Information Base for the
Internet Protocol (IP)", Work in Progress, April 2004.
[<a id="ref-6">6</a>] Raghunarayan, R., Editor, "Management Information Base for the
Transmission Control Protocol (TCP)", Work in Progress, February
2004.
[<a id="ref-7">7</a>] Fenner, B. and J. Flick, "Management Information Base for the
User Datagram Protocol (UDP)", Work in Progress, April 2004.
[<a id="ref-8">8</a>] Waldbusser, S., "Remote Network Monitoring Management
Information Base Version 2 Using SMIv2", Work in Progress,
February 2004.
[<a id="ref-9">9</a>] Haberman, B., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22IP+Forwarding+Table+MIB%22'>"IP Forwarding Table MIB"</a>, Work in Progress,
February 2004.
[<a id="ref-10">10</a>] Blunk, L., Damas, J., Parent, F. and A. Robachevsky, "Routing
Policy Specification Language next generation (RPSLng)", Work in
Progress, April 2004.
[<a id="ref-11">11</a>] 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.
[<a id="ref-12">12</a>] Chesterfield, J., Editor, "Multicast Group Membership Discovery
MIB", Work in Progress, February 2004.
<span class="grey">Nesser II & Bergstrom Informational [Page 41]</span><span id="page-42" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Authors' Addresses</span>
Please contact the authors with any questions, comments or
suggestions at:
Philip J. Nesser II
Principal
Nesser & Nesser Consulting
13501 100th Ave NE, #5202
Kirkland, WA 98034
Phone: +1 425 481 4303
Fax: +1 425 48
EMail: [email protected]
Andreas Bergstrom (Editor)
Ostfold University College
Rute 503 Buer
N-1766 Halden
Norway
EMail: [email protected]
<span class="grey">Nesser II & Bergstrom Informational [Page 42]</span><span id="page-43" ></span>
<span class="grey"><a href="./rfc3796">RFC 3796</a> IPv4 in the IETF Operations & Management Area June 2004</span>
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
[email protected].
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Nesser II & Bergstrom Informational [Page 43]
Annotations
Select text to annotate