Survey of IPv4 Addresses in Currently Deployed IETF Operations & Management Area Standards Track and Experimental Documents
RFC 3796

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 05

Network Working Group                                     P. Nesser, II
Request for Comments: 3796                   Nesser & Nesser Consulting
Category: Informational                                A. Bergstrom, Ed.
                                              Ostfold University College
                                                               June 2004

          Survey of IPv4 Addresses in Currently Deployed IETF
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.

Nesser II & Bergstrom        Informational                      [Page 1]
RFC 3796     IPv4 in the IETF Operations & Management Area     June 2004

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Document Organization. . . . . . . . . . . . . . . . . . . . .  2
   3.  Full Standards . . . . . . . . . . . . . . . . . . . . . . . .  3
   4.  Draft Standards. . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Proposed Standards . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Experimental RFCs. . . . . . . . . . . . . . . . . . . . . . . 34
   7.  Summary of Results . . . . . . . . . . . . . . . . . . . . . . 36
       7.1.  Standards. . . . . . . . . . . . . . . . . . . . . . . . 36
       7.2.  Draft Standards. . . . . . . . . . . . . . . . . . . . . 36
       7.3.  Proposed Standards . . . . . . . . . . . . . . . . . . . 37
       7.4.  Experimental RFCs. . . . . . . . . . . . . . . . . . . . 40
   8.  Security Considerations. . . . . . . . . . . . . . . . . . . . 40
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 40
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40
       10.1. Normative Reference. . . . . . . . . . . . . . . . . . . 40
       10.2. Informative References . . . . . . . . . . . . . . . . . 41
   11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 42
   12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 43

1.  Introduction

   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 [1].

2.  Document Organization

   The document is organized as described below:

   Sections 3, 4, 5, and 6 each describe the raw analysis of Full,
   Draft, and Proposed Standards, and Experimental RFCs.  Each RFC is
   discussed in its turn starting with RFC 1 and ending with (around)
   RFC 3100. 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.

   Section 7 is an analysis of the data presented in Sections 3, 4, 5,
   and 6.  It is here that all of the results are considered as a whole
   and the problems that have been resolved in later RFCs are
   correlated.

Nesser II & Bergstrom        Informational                      [Page 2]
RFC 3796     IPv4 in the IETF Operations & Management Area     June 2004

3.  Full Standards

   Full Internet Standards (most commonly simply referred to as
   "Standards") are fully mature protocol specification that are widely
   implemented and used throughout the Internet.

3.1.  RFC 1155 Structure of Management Information

   Section 3.2.3.2.  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.

3.2.  RFC 1212 Concise MIB definitions

   In section 4.1.6 IpAddress is defined as:

      (6)  IpAddress-valued: 4 sub-identifiers, in the familiar
           a.b.c.d notation.

3.3.  RFC 1213 Management Information Base