Network Working Group                               Philip J.
IPv6 Operations                                               C. Mickles
Internet-Draft
Expires: March 31, 2004                                        P. Nesser II
draft-ietf-v6ops-ipv4survey-int-01.txt
                                              Nesser & Nesser Consulting
Internet Draft                                        Cleveland Mickles
                                                        AOL Time Warner
                                                              June 2003
                                                  Expires December
                                                                Oct 2003

         Internet Area:

   Survey of IPv4 Addresses in Currently Deployed IETF Internet Area
                               Standards
                 draft-ietf-v6ops-ipv4survey-int-02.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

Status of this Memo

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://
   www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 31, 2004.

Copyright Notice

   Copyright (C) The Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003 Society (2003). All Rights Reserved.

Abstract

   This document seeks to document all usage of IPv4 addresses in
   currently deployed IETF Internet Area documented 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.

1.0 Introduction.............................................02
2.0 Document Organization....................................03
3.0 Full Standards...........................................03
4.0 Draft Standards..........................................09
5.0 Proposed Standards.......................................13
6.0 Experimental RFCs........................................34
7.0  Summary

Table of Results......................................43
8.0 Security Considerations..................................51
9.0 References...............................................51
10.0 Acknowledgements........................................51
11.0 Author's Addresses......................................52
12.0 Intellectual Property Statement.........................52
13.0  Full Copyright Statement...............................53

1.0 Contents

   1.     Introduction

This document is part of a document set aiming to document 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 . . . . . . . . . . . . . . . . . . . . . . .   9
   2.     Document Organization  . . . . . . . . . . . . . . . . . .  10
   3.     Full Standards . . . . . . . . . . . . . . . . . . . . . .  11
   3.1    RFC 791 Internet Protocol  . . . . . . . . . . . . . . . .  11
   3.2    RFC 792 Internet Control Message Protocol  . . . . . . . .  11
   3.3    RFC 826 Ethernet Address Resolution Protocol . . . . . . .  11
   3.4    RFC 891 DCN Local-Network Protocols  . . . . . . . . . . .  11
   3.5    RFC 894 Standard for the current IETF areas (Application,  Internet, Management &
Operations, Routing, Security, Sub-IP and Transport).

This specific document focuses on usage transmission of IPv4 addresses within IP datagrams
          over Ethernet networks . . . . . . . . . . . . . . . . . .  11
   3.6    RFC 895 Standard for the transmission of IP datagrams
          over experimental Ethernet networks  . . . . . . . . . . .  11
   3.7    RFC 903 Reverse Address Resolution Protocol  . . . . . . .  11
   3.8    RFC 919 Broadcasting Internet area.

For a full introduction, please see the intro[1] draft. Datagrams  . . . . . . . . .  11
   3.9    RFC 922 Broadcasting Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

2.0 Document Organization

The following sections 3, 4, 5, and 6 each describe datagrams in the raw analysis presence
          of Full, Draft, and Proposed Standards, and Experimental RFCs.  Each subnets . . . . . . . . . . . . . . . . . . . . . . . .  11
   3.10   RFC is discussed in turn starting with 950 Internet Standard Subnetting Procedure . . . . . .  12
   3.11   RFC 1 1034 Domain Names: Concepts and ending with Facilities . . . . . .  12
   3.12   RFC 3247.
The comments for each RFC are "raw" in nature.  That is, each RFC is
discussed in a vacuum 1035 Domain Names: Implementation and problems or issues discussed do not "look
ahead" to see if any of the issues raised have already been fixed.

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

3.0 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.01 IP datagrams
          over IEEE  802 networks  . . . . . . . . . . . . . . . . .  14
   3.14   RFC 1044 Internet Protocol. RFC0791, RFC0950, RFC0919, RFC0922, RFC792,

3.01.1 Protocol on Network System's
          HYPERchannel:  Protocol Specification  . . . . . . . . . .  14
   3.15   RFC 791 defines IPv4 and will be replaced by the IPv6
specifications.

3.01.2 1055 Nonstandard for transmission of IP datagrams
          over serial lines: SLIP  . . . . . . . . . . . . . . . . .  14
   3.16   RFC 950 specifies IPv4 subnetting and will be replaced by 1088 Standard for the
IPv6 specifications.

3.01.3 transmission of IP datagrams
          over NetBIOS networks  . . . . . . . . . . . . . . . . . .  15
   3.17   RFC 919 is not online and is unavailable 1112 Host Extensions for review.

3.01.4 IP Multicasting . . . . . . .  15
   3.18   RFC 922 specifies how broadcasts should be treated in 1132 Standard for the
presence transmission of subnets. 802.2 packets
          over IPX networks  . . . . . . . . . . . . . . . . . . . .  15
   3.19   RFC 1201 Transmitting IP traffic over ARCNET networks  . .  15
   3.20   RFC 1209 The techniques Transmission of this document will be replaced
by IP Datagrams over the IPv6 specifications.

3.01.5 SMDS
          Service  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   3.21   RFC 792 defines ICMP.  The specification 1390 Transmission of ICMPv6 will serve
as an update.

3.01.6 RFC 1112 defines IP multicast.  A similar updated version for
IPv6 multicasting must be written.

3.02 Domain Name System. RFC1034, RFC1035
 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

3.02.1 RFC 1034 Domain Concepts and Facilities

In Section 3.6. Resource Records ARP over FDDI Networks . .  15
   3.22   RFC 1661 The Point-to-Point Protocol (PPP) . . . . . . . .  15
   3.23   RFC 1662 PPP in HDLC-like Framing  . . . . . . . . . . . .  16
   3.24   RFC 2427 Multiprotocol Interconnect over Frame Relay . . .  16
   4.     Draft Standards  . . . . . . . . . . . . . . . . . . . . .  17
   4.1    RFC 951 Bootstrap Protocol (BOOTP) . . . . . . . . . . . .  17
   4.2    RFC 1188 Proposed Standard for the definition Transmission of A records is:

RDATA           which is the type IP
          Datagrams over FDDI Networks . . . . . . . . . . . . . . .  18
   4.3    RFC 1191 Path MTU discovery  . . . . . . . . . . . . . . .  18
   4.4    RFC 1356 Multiprotocol Interconnect on X.25 and sometimes class dependent data
                which describes ISDN . . .  18
   4.5    RFC 1534 Interoperation Between DHCP and BOOTP . . . . . .  18
   4.6    RFC 1542 Clarifications and Extensions for the resource:

                A               For
          Bootstrap Protocol . . . . . . . . . . . . . . . . . . . .  18
   4.7    RFC 1629 Guidelines for OSI NSAP Allocation in the IN class, a 32 bit
          Internet . . . . . . . . . . . . . . . . . . . . . . . . .  18
   4.8    RFC 1762 The PPP DECnet Phase IV Control Protocol (DNCP) .  18
   4.9    RFC 1989 PPP Link Quality Monitoring . . . . . . . . . . .  18
   4.10   RFC 1990 The PPP Multilink Protocol (MP) . . . . . . . . .  18
   4.11   RFC 1994 PPP Challenge Handshake Authentication
          Protocol (CHAP)  . . . . . . . . . . . . . . . . . . . . .  19
   4.12   RFC 2067 IP address

In Section 5.2.1. Typical functions defines

   1. over HIPPI . . . . . . . . . . . . . . . . . .  19
   4.13   RFC 2131 Dynamic Host name to host address translation.

      This function is often defined to mimic a previous HOSTS.TXT
      based function.  Given a character string, the caller wants
      one or more 32 bit IP addresses.  Under the DNS, it
      translates into a request Configuration Protocol . . . . . . .  20
   4.14   RFC 2132 DHCP Options and BOOTP Vendor Extensions  . . . .  20
   4.15   RFC 2390 Inverse Address Resolution Protocol . . . . . . .  20
   4.16   RFC 2460 Internet Protocol, Version 6 (IPv6)
          Specification  . . . . . . . . . . . . . . . . . . . . . .  20
   4.17   RFC 2461 Neighbor Discovery for type A RRs.  Since the DNS does
      not preserve the order of RRs, this function may choose to
      sort the returned addresses or select the "best" address if
      the service returns only one choice to the client.  Note that
      a multiple address return is recommended, but a single
      address may be the only way to emulate prior HOSTS.TXT
      services.

   2. Host address to host name translation

      This function will often follow the form of previous
      functions.  Given a 32 bit IP address, the caller wants a
      character string.  The octets of the IP address are reversed,
      used as name components, and suffixed with "IN-ADDR.ARPA".  A
      type PTR query is used to get the RR with the primary name of
      the host.  For example, a request for the host name
      corresponding to IP address 1.2.3.4 looks for PTR RRs Version 6 (IPv6)  . . .  20
   4.18   RFC 2462 IPv6 Stateless Address Autoconfiguration  . . . .  20
   4.19   RFC 2463 Internet Control Message Protocol (ICMPv6) for
      domain name "4.3.2.1.IN-ADDR.ARPA".

There are, of course, numerous examples of IPv4 addresses scattered
throughout the document.  There is currently a large debate ongoing
in
          the  Internet Protocol Version 6 (IPv6) Specification  . .  20
   4.20   RFC 3596 DNS community over the use of A6 or AAAA record types for the
resolution of IPv6 addresses.  The fact that current A records are
insufficient Extensions to support IPv6 is not unknown to the Internet community.

 Internet Area: Survey of IPv4 IP version 6  . . . . .  20
   5.     Proposed Standards . . . . . . . . . . . . . . . . . . . .  21
   5.1    RFC 1234 Tunneling IPX traffic through IP networks . . . .  21
   5.2    RFC 1256 ICMP Router Discovery Messages  . . . . . . . . .  22
   5.3    RFC 1277 Encoding Network Addresses Currently Deployed  Mar. 2003

3.02.2 to Support
          Operation over Non-OSI Lower Layers  . . . . . . . . . . .  22
   5.4    RFC 1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION

Section 3.4.1. A RDATA format defines the format for A records:

          +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
          |                    ADDRESS                    |
          +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

      where:

      ADDRESS         A 32 bit Internet address.

      Hosts that have multiple Internet addresses will have
      multiple A records.

      A records cause no additional section processing. 1332 The
      RDATA section of an A line in a master file is an Internet
      address expressed as four decimal numbers separated by dots
      without any imbedded spaces (e.g.,"10.2.0.52" or "192.0.5.6").

Section 3.4.2. WKS RDATA format

    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    |                    ADDRESS                    |
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    |       PROTOCOL        |                       |
    +--+--+--+--+--+--+--+--+                       |
    |                                               |
    /                   <BIT MAP>                   /
    /                                               /
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

      where:

      ADDRESS         An 32 bit PPP Internet address

      PROTOCOL        An 8 bit Protocol Control Protocol
          (IPCP) . . . . . . . . . . . . . . . . . . . . . . . . . .  22
   5.5    RFC 1377 The PPP OSI Network Layer Control Protocol
          (OSINLCP)  . . . . . . . . . . . . . . . . . . . . . . . .  22
   5.6    RFC 1378 The PPP AppleTalk Control Protocol (ATCP) . . . .  22
   5.7    RFC 1469 IP protocol number

      <BIT MAP>       A variable length bit map. Multicast over Token-Ring Local Area
          Networks . . . . . . . . . . . . . . . . . . . . . . . . .  22
   5.8    RFC 1552 The bit map
                  must be a multiple of 8 bits long. PPP Internetworking Packet Exchange
          Control Protocol (IPXCP) . . . . . . . . . . . . . . . . .  22
   5.9    RFC 1570 PPP LCP Extensions  . . . . . . . . . . . . . . .  23
   5.10   RFC 1598 PPP in X.25 PPP-X25 . . . . . . . . . . . . . . .  23
   5.11   RFC 1618 PPP over ISDN . . . . . . . . . . . . . . . . . .  23
   5.12   RFC 1663 PPP Reliable Transmission . . . . . . . . . . . .  23
   5.13   RFC 1752 The WKS record is used to describe Recommendation for the well known services
      supported by a particular protocol on a particular internet
      address.  The PROTOCOL field specifies an IP protocol number,
      and the bit map has one bit per port of the specified protocol. Next Generation
          Protocol . . . . . . . . . . . . . . . . . . . . . . . . .  23
   5.14   RFC 1755 ATM Signaling Support for IP over ATM . . . . . .  23
   5.15   RFC 1763 The first bit corresponds to port 0, the second to port 1, etc.
      If the bit map does not include a bit for a protocol of
      interest, that bit is assumed zero. PPP Banyan Vines Control Protocol (BVCP)  . .  23
   5.16   RFC 1764 The appropriate values and
      mnemonics for ports and protocols are specified PPP XNS IDP Control Protocol (XNSCP)  . . . .  23
   5.17   RFC 1973 PPP in [RFC-1010].

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

      For example, if PROTOCOL=TCP (6), the 26th bit corresponds to
      TCP port 25 (SMTP).  If this bit is set, a SMTP server should be
      listening on TCP port 25; if zero, SMTP service is not supported
      on the specified address.

      The purpose of WKS RRs is to provide availability information for
      servers for TCP and UDP.  If a server supports both TCP and UDP,
      or has multiple Internet addresses, then multiple WKS RRs are
      used.

      WKS RRs cause no additional section processing.

      Section 3.5. IN-ADDR.ARPA domain describe reverse DNS lookups and
      is clearly IPv4 dependent.

There are, of course, numerous examples of IPv4 addresses scattered
throughout the document.

3.03 Frame Relay  . . . . . . . . . . . . . . .  23
   5.18   RFC 894 Standard 1981 Path MTU Discovery for the transmission of IP datagrams over
Ethernet networks

This protocol specifically deals with the transmissions of IPv4 packets
over Ethernet.  A similar version 6 . . . . . . .  23
   5.19   RFC must exist for transmission of IPv6
packets.

3.04 1982 Serial Number Arithmetic  . . . . . . . . . . . .  23
   5.20   5.21 RFC 895 Standard 1995 Incremental Zone Transfer in DNS . . . . . .  24
   5.21   RFC 1996 A Mechanism for the transmission Prompt Notification of Zone
          Changes (DNS NOTIFY) . . . . . . . . . . . . . . . . . . .  24
   5.22   RFC 2003 IP datagrams over
experimental Ethernet networks

This protocol specifically deals with the transmissions of IPv4 packets
over Ethernet.  It is probably unnecessary to provide an updated Encapsulation within IP  . . . . . . . . . . .  24
   5.23   RFC
because of the unlikelihood of the existence of this layer 2 medium.

3.05 2004 Minimal Encapsulation within IP . . . . . . . . .  24
   5.24   RFC 1042 Standard 2005 Applicability Statement for the transmission of IP datagrams over IEEE
802 networks

This protocol specifically deals with the transmissions of IPv4 packets
over Ethernet.  A similar Mobility Support .  24
   5.25   RFC must exist for transmission of IPv6
packets, particularly 2022 Support for 802.5 networks.

3.06 Multicast over UNI 3.0/3.1 based
          ATM Networks . . . . . . . . . . . . . . . . . . . . . . .  24
   5.26   RFC 891 DCN Local-Network Protocols

There are many implicit assumptions about the use of IPv4 addresses in
this document.  It is unlikely to require any updates since no DCN
networks are in existence.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

3.07 2043 The PPP SNA Control Protocol (SNACP)  . . . . . .  24
   5.27   RFC 1044 Internet 2097 The PPP NetBIOS Frames Control Protocol on Network System's HYPERchannel: (NBFCP) .  24
   5.28   RFC 2113 IP Router Alert Option  . . . . . . . . . . . . .  24
   5.29   RFC 2125 The PPP Bandwidth Allocation Protocol Specification

There are a variety of methods used in this standard to map IPv4
addresses to 32 bits fields (BAP) /
          The PPP Bandwidth Allocation Control Protocol (BACP) . . .  25
   5.30   RFC 2136 Dynamic Updates in the HYPERchannel headers.  A new
version of the standard will need Domain Name System (DNS
          UPDATE)  . . . . . . . . . . . . . . . . . . . . . . . . .  25
   5.31   RFC 2181 Clarifications to be written do support IPv6 on
HYPERchannel networks.

3.08 the DNS Specification . . . . .  25
   5.32   RFC 1201 Transmitting 2225 Classical IP traffic and ARP over ARCNET networks

The major concerns of this ATM . . . . . . . . . .  25
   5.33   RFC with respect to IPv4 addresses occur
in the resolution of ARCnet 8bit addresses to IPv4 addresses in an
"ARPlike" method.
A similar method, very similar to this RFC, would need to be written
to support IPv6 addresses 2226 IP Broadcast over ARCNET.

3.09 ATM Networks  . . . . . . . . .  25
   5.34   RFC 1055 Nonstandard 2241 DHCP Options for transmission of IP datagrams over serial
lines:
     SLIP

This Novell Directory Services  . . .  25
   5.35   RFC is more of a analysis of the shortcomings of SLIP which is
unsurprising.  The introduction of 2242 NetWare/IP Domain Name and Information  . . . . .  26
   5.36   RFC 2290 Mobile-IPv4 Configuration Option for PPP as a general replacement IPCP . .  26
   5.37   RFC 2308 Negative Caching of SLIP
has made this protocol essentially unused.  No update need be
considered.

3.10 DNS Queries (DNS NCACHE)  . .  26
   5.38   RFC 1088 Standard 2331 ATM Signaling Support for the transmission of IP datagrams over
     NetBIOS networks

This ATM - UNI
          Signaling 4.0 Update . . . . . . . . . . . . . . . . . . .  26
   5.39   RFC documents a technique to encapsulate IP packets inside NetBIOS
packets.
The technique presented of using NetBIOS names of the form
IP.XX.XX.XX.XX will not work for IPv6 addresses since the length of
IPv6 addresses will not fit within the NetBIOS 15 octet name
limitation.  A new scheme must be invented to similarly encapsulate
IPv6 packets.

3.11 The Point-to-Point 2332 NBMA Next Hop Resolution Protocol (PPP). RFC1661, RFC1662

3.11.1 (NHRP)  . . . .  26
   5.40   RFC 1661 The Point-to-Point Protocol (PPP)

The Point-to-Point 2333 NHRP Protocol (PPP)

3.11.2 Applicability . . . . . . . . . . .  27
   5.41   RFC 1662 2335 A Distributed NHRP Service Using SCSP . . . . . .  27
   5.42   RFC 2363 PPP in HDLC-like Framing

There are no IPv4 dependencies in this protocol. Over FUNI . . . . . . . . . . . . . . . . . .  27
   5.43   RFC 2364 PPP Over AAL5 . . . . . . . . . . . . . . . . . .  27
   5.44   RFC 2371 Transaction Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

3.12 Protocol Version 3.0
          (TIPV3)  . . . . . . . . . . . . . . . . . . . . . . . . .  27
   5.45   RFC 1209 The 2464 Transmission of IP Datagrams IPv6 Packets over the SMDS Service

This Ethernet
          Networks . . . . . . . . . . . . . . . . . . . . . . . . .  29
   5.46   RFC defines running IPv4 and ARP 2467 Transmission of IPv6 Packets over SMDS. FDDI Networks .  29
   5.47   RFC 2470 Transmission of IPv6 Packets over Token Ring
          Networks . . . . . . . . . . . . . . . . . . . . . . . . .  29
   5.48   RFC 2472 IP Version 6 over PPP . . . . . . . . . . . . . .  29
   5.49   RFC 2473 Generic Packet Tunneling in IPv6 Specification  .  29
   5.50   RFC 2484 PPP LCP Internationalization Configuration
          Option . . . . . . . . . . . . . . . . . . . . . . . . . .  29
   5.51   RFC 2485 DHCP Option for The methods described
could easily be extended to support Open Group's User
          Authentication Protocol  . . . . . . . . . . . . . . . . .  29
   5.52   RFC 2486 The Network Access Identifier . . . . . . . . . .  29
   5.53   RFC 2491 IPv6 packets, but a new over Non-Broadcast Multiple Access (NBMA)
          networks . . . . . . . . . . . . . . . . . . . . . . . . .  29
   5.54   RFC would
be required.

 Internet Area: Survey 2492 IPv6 over ATM Networks  . . . . . . . . . . . . .  29
   5.55   RFC 2497 Transmission of IPv4 IPv6 Packets over ARCnet
          Networks . . . . . . . . . . . . . . . . . . . . . . . . .  30
   5.56   RFC 2507 IP Header Compression . . . . . . . . . . . . . .  30
   5.57   RFC 2526 Reserved IPv6 Subnet Anycast Addresses Currently Deployed  Mar. 2003

4.0 Draft Standards

Draft Standards represent the penultimate standard level  . . . . .  30
   5.58   RFC 2529 Transmission of IPv6 over IPv4 Domains without
          Explicit Tunnels . . . . . . . . . . . . . . . . . . . . .  30
   5.59   RFC 2563 DHCP Option to Disable Stateless
          Auto-Configuration 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.

4.01 IPv4 Clients . . . . . . . . . . . .  30
   5.60   RFC 951 Bootstrap 2590 Transmission of IPv6 Packets over Frame Relay
          Networks Specification . . . . . . . . . . . . . . . . . .  30
   5.61   RFC 2601 ILMI-Based Server Discovery for ATMARP  . . . . .  30
   5.62   RFC 2602 ILMI-Based Server Discovery for MARS  . . . . . .  30
   5.63   RFC 2603 ILMI-Based Server Discovery for NHRP  . . . . . .  30
   5.64   RFC 2610 DHCP Options for Service Location Protocol (BOOTP)

This protocol is designed specifically  . . .  30
   5.65   RFC 2615 PPP over SONET/SDH  . . . . . . . . . . . . . . .  31
   5.66   RFC 2625 IP and ARP over Fibre Channel . . . . . . . . . .  31
   5.67   RFC 2671 Extension Mechanisms for use with IPv4.  A new
version will be required to support IPv6.  For example:

Section 3. Packet Format

   All numbers shown are decimal, unless indicated otherwise. DNS (EDNS0)  . . . . . .  31
   5.68   RFC 2672 Non-Terminal DNS Name Redirection . . . . . . . .  31
   5.69   RFC 2673 Binary Labels in the Domain Name System . . . . .  31
   5.70   RFC 2675 IPv6 Jumbograms . . . . . . . . . . . . . . . . .  31
   5.71   RFC 2684 Multiprotocol Encapsulation over ATM
          Adaptation Layer 5 . . . . . . . . . . . . . . . . . . . .  31
   5.72   RFC 2685 Virtual Private Networks Identifier . . . . . . .  31
   5.73   RFC 2686 The
   BOOTP packet is enclosed Multi-Class Extension to Multi-Link PPP . . .  31
   5.74   RFC 2687 PPP in a standard Real-time Oriented HDLC-like Framing . .  32
   5.75   RFC 2688 Integrated Services Mappings for Low Speed
          Networks . . . . . . . . . . . . . . . . . . . . . . . . .  32
   5.76   RFC 2710 Multicast Listener Discovery (MLD) for IPv6 . . .  32
   5.77   RFC 2711 IPv6 Router Alert Option  . . . . . . . . . . . .  32
   5.78   RFC 2728 The Transmission of IP [8] UDP [7] datagram.  For
   simplicity it is assumed that the BOOTP packet is never fragmented.
   Any numeric fields shown are packed in 'standard network byte
   order', i.e. high order bits are sent first.

   In Over the IP header Vertical
          Blanking Interval of a bootrequest, Television Signal . . . . . . . . .  32
   5.79   RFC 2734 IPv4 over IEEE 1394 . . . . . . . . . . . . . . .  33
   5.80   RFC 2735 NHRP Support for Virtual Private Networks . . . .  33
   5.81   RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT)  .  33
   5.82   RFC 2766 Network Address Translation - Protocol
          Translation (NAT-PT) . . . . . . . . . . . . . . . . . . .  33
   5.83   RFC 2776 Multicast-Scope Zone Announcement Protocol
          (MZAP) . . . . . . . . . . . . . . . . . . . . . . . . . .  33
   5.84   RFC 2782 A DNS RR for specifying the client fills in its own location of
          services . . . . . . . . . . . . . . . . . . . . . . . . .  33
   5.85   RFC 2794 Mobile IP
   source address if known, otherwise zero.  When the server address is
   unknown, the Network Access Identifier Extension
          for IPv4 . . . . . . . . . . . . . . . . . . . . . . . . .  33
   5.86   RFC 2834 ARP and IP destination address will be the 'broadcast address'
   255.255.255.255.  This address means 'broadcast on the local cable,
   (I don't know my net number)' [4].

...

      FIELD   BYTES   DESCRIPTION
      -----   -----   ---
...
         ciaddr  4       client IP address;
                         filled in by client in bootrequest if known.

         yiaddr  4       'your' (client) IP address;
                         filled by server if client doesn't
                         know its own address (ciaddr was 0).

         siaddr  4       server IP address;
                         returned in bootreply by server.

         giaddr  4       gateway Broadcast over HIPPI-800 . . . . . . .  33
   5.87   RFC 2835 IP address,
                         used in optional cross-gateway booting.

Since the packet format is a fixed 300 bytes in length, an updated
version of the protocol could easily accommodate an additional 48 bytes
(4 IPV6 fields of 16 bytes and ARP over HIPPI-6400  . . . . . . . . . . .  35
   5.88   RFC 2855 DHCP for IEEE 1394  . . . . . . . . . . . . . . .  35
   5.89   RFC 2874 DNS Extensions to replace the existing 4 IPv4 fields of
4 bytes).

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

4.02 Support IPv6 Address
          Aggregation and Renumbering  . . . . . . . . . . . . . . .  35
   5.90   RFC 1191 Path MTU discovery (IP-MTU)

The entire process of PMTU discovery is predicated on the use of the DF
bit in the IPv4 header, an ICMP message (also IPv4 dependent) 2893 Transition Mechanisms for IPv6 Hosts and TCP
MSS option.  There clearly needs to an PMTUv6 functionality.

4.03-zzzz
          Routers  . . . . . . . . . . . . . . . . . . . . . . . . .  36
   5.91   RFC 1356 Multiprotocol Interconnect on X.25 2916 E.164 number and ISDN

There are IPv4 dependencies within this RFC.

4.04 DNS  . . . . . . . . . . . . . .  36
   5.92   RFC 1534 Interoperation Between 2937 The Name Service Search Option for DHCP and BOOTP (DHCP-BOOTP)

There are no IPv4 dependencies in this protocol.

4.05 . . . . .  36
   5.93   RFC 1542 Clarifications and Extensions 3004 The User Class Option for the Bootstrap Protocol

There are no new issues other than those presented in Section 4.01
above.

4.06 RFC 1629 Guidelines for OSI NSAP Allocation in the Internet
    (OSI-NSAP)

There are no IPv4 dependencies in this protocol.

4.07 DHCP  . . . . . . . . .  36
   5.94   RFC 1762 3011 The PPP DECnet Phase IV Control Protocol (DNCP)
(PPP-DNCP)

There are no IPv4 dependencies in this protocol.

4.08 Subnet Selection Option for DHCP . . . .  36
   5.95   RFC 1989 PPP Link Quality Monitoring (PPP-LINK)

There are no 3021 Using 31-Bit Prefixes for IPv4 dependencies in this protocol.

4.09 P2P Links  . . . .  36
   5.96   RFC 1990 The PPP Multilink Protocol (MP) (PPP-MP)

Section 5.1.3.  Endpoint Discriminator 3024 Reverse Tunneling for Mobile IP, revised  . . . .  36
   5.97   RFC 3046 DHCP Relay Agent Information Option defines a Class header
field.

   Class
        The Class field is one octet and indicates the identifier
        address space.  The most up-to-date values of the LCP Endpoint
        Discriminator Class field are specified in the most recent
        "Assigned Numbers" . . . . . . .  36
   5.98   RFC [7].  Current values are assigned as
        follows:

 Internet Area: Survey 3056 Connection of IPv6 Domains via IPv4 Addresses Currently Deployed  Mar. 2003

        0    Null Class

        1    Locally Assigned Address

        2    Internet Protocol (IP) Address

        3    IEEE 802.1 Globally Assigned MAC Address

        4    PPP Magic-Number Block

        5    Public Switched Network Directory Number Clouds  . . .  36
   5.99   RFC 3068 An Anycast Prefix for 6to4 Relay Routers  . . . .  36
   5.100  RFC 3074 DHC Load Balancing Algorithm  . . . . . . . . . .  37
   5.101  RFC 3077 A new class field needs to be defined by the IANA Link-Layer Tunneling Mechanism for IPv6 addresses.

4.10
          Unidirectional Links . . . . . . . . . . . . . . . . . . .  37
   5.102  RFC 1994 PPP Challenge Handshake Authentication Protocol
     (CHAP) (PPP-CHAP)

There are no IPv4 dependencies in this protocol.

4.11 3115 Mobile IP Vendor/Organization-Specific
          Extensions . . . . . . . . . . . . . . . . . . . . . . . .  37
   5.103  RFC 2067 3145 L2TP Disconnect Cause Information . . . . . . . .  37
   5.104  RFC 3344 IP over HIPPI (IP-HIPPI)

Section 5.1 Packet Formats contains the following excerpt:

   EtherType (16 bits) SHALL be set as defined in Assigned Numbers [8]:
   IP = 2048 ('0800'h), ARP = 2054 ('0806'h), RARP = 32,821 ('8035'h).

Section 5.5 MTU has the following definition:

   The MTU for HIPPI-SC LANs is 65280 bytes.

   This value was selected because it allows the IP packet to fit in
   one 64K byte buffer with up to 256 bytes of overhead.  The overhead
   is 40 bytes at the present time; there are 216 bytes of room for
   expansion.

         HIPPI-FP Header                  8 bytes
         HIPPI-LE Header                 24 bytes
         IEEE 802.2 LLC/SNAP Headers      8 bytes
         Maximum IP packet size (MTU) 65280 bytes
                                      ------------
                           Total      65320 bytes (64K - 216)

This definition is not applicable Mobility Support for IPv6 packets since packets can
be larger than the IPv4 limitation of 65280 bytes.

4.12  . . . . . . . . . .  37
   5.105  RFC 2131 3376 Internet Group Management Protocol, Version 3 . .  37
   5.106  RFC 3402 Dynamic Host Configuration Delegation Discovery System (DDDS)
          Part Two: The Algorithm  . . . . . . . . . . . . . . . . .  37
   5.107  RFC 3403 Dynamic Delegation Discovery System (DDDS)
          Part Three:  The Domain Name System (DNS) Database . . . .  37
   5.108  RFC 3404 Dynamic Delegation Discovery System (DDDS)
          Part Four:  The Uniform Resource Identifiers (URI) . . . .  37
   5.109  RFC 3513 IP Version 6 Addressing Architecture  . . . . . .  37
   5.110  RFC 3518 Point-to-Point Protocol (DHCP)

This version of DHCP is highly assumptive (PPP) Bridging Control
          Protocol (BCP) . . . . . . . . . . . . . . . . . . . . . .  38
   6.     Experimental RFCs  . . . . . . . . . . . . . . . . . . . .  39
   6.1    RFC 1149 Standard for the transmission of IPv4.  Significant work IP datagrams
          on DHCPv6 has been done and is ongoing. avian carriers  . . . . . . . . . . . . . . . . . . . .  39
   6.2    RFC 1183 New DNS RR Definitions  . . . . . . . . . . . . .  39
   6.3    RFC 1226 Internet Area: Survey protocol encapsulation of IPv4 Addresses Currently Deployed  Mar. 2003

4.13 AX.25 frames .  39
   6.4    RFC 2132 DHCP Options and BOOTP Vendor Extensions (DHCP-BOOTP)

This version of DHCP is highly assumptive of IPv4.  Significant work
on DHCPv6 has been done and is ongoing.

4.14-zzzz 1241 Scheme for an internet encapsulation protocol:
          Version 1  . . . . . . . . . . . . . . . . . . . . . . . .  39
   6.5    RFC 2332 NBMA Next Hop Resolution 1307 Dynamically Switched Link Control Protocol (NHRP)

There are IPv4 dependencies within this RFC.

4.15-zzzz  . . .  39
   6.6    RFC 2390 Inverse 1393 Traceroute Using an IP Option . . . . . . . . . .  40
   6.7    RFC 1433 Directed ARP  . . . . . . . . . . . . . . . . . .  40
   6.8    RFC 1464 Using the Domain Name System To Store
          Arbitrary String Attributes  . . . . . . . . . . . . . . .  40
   6.9    RFC 1475 TP/IX: The Next Internet  . . . . . . . . . . . .  40
   6.10   RFC 1561 Use of ISO CLNP in TUBA Environments  . . . . . .  40
   6.11   RFC 1712 DNS Encoding of Geographical Location . . . . . .  41
   6.12   RFC 1735 NBMA Address Resolution Protocol (IARP)

There are IPv4 dependencies within this RFC.

4.16-zzzz (NARP) . . . . .  41
   6.13   RFC 2427 Multiprotocol Interconnect over Frame Relay

There are IPv4 dependencies within this RFC.

4.17 1768 Host Group Extensions for CLNP Multicasting . . .  42
   6.14   RFC 2460 1788 ICMP Domain Name Messages . . . . . . . . . . . .  42
   6.15   RFC 1797 Class A Subnet Experiment . . . . . . . . . . . .  42
   6.16   RFC 1819 Internet Protocol, Stream Protocol Version 6 (IPv6) 2 (ST2)
          Protocol Specification (IPV6)

This document defines - Version ST2+  . . . . . . . . . .  42
   6.17   RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . .  43
   6.18   RFC 1876 A Means for Expressing Location Information in
          the Domain Name System . . . . . . . . . . . . . . . . . .  43
   6.19   RFC 1888 OSI NSAPs and IPv6  . . . . . . . . . . . . . . .  43
   6.20   RFC 2009 GPS-Based Addressing and has no IPv4 issues.

4.18 Routing  . . . . . . . .  43
   6.21   RFC 2461 Neighbor Discovery for 2143 Encapsulating IP Version 6 (IPv6) (IPV6-ND)

This document defines an IPv6 related protocol with the SCSI  . . . . . . . . .  43
   6.22   RFC 2345 Domain Names and has no IPv4 issues.

4.19 Company Name Retrieval . . . . .  43
   6.23   RFC 2462 2443 A Distributed MARS Service Using SCSP . . . . . .  43
   6.24   RFC 2471 IPv6 Stateless Testing Address Autoconfiguration (IPV6-AUTO)

This document defines an IPv6 related protocol and has no IPv4 issues.

4.20 Allocation . . . . . . . . .  44
   6.25   RFC 2463 Internet Control Message Protocol (ICMPv6) for the Internet
     Protocol Version 6 (IPv6) Specification (ICMPv6)

This document defines an IPv6 related protocol and has no IPv4 issues.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.0 Proposed Standards

Proposed Standards are introductory level documents.  There are no
requirements 2520 NHRP with Mobile NHCs . . . . . . . . . . . . . .  44
   6.26   RFC 2521 ICMP Security Failures Messages . . . . . . . . .  44
   6.27   RFC 2540 Detached Domain Name System (DNS) Information . .  44
   6.28   RFC 2823 PPP over Simple Data Link (SDL) using
          SONET/SDH with ATM-like framing  . . . . . . . . . . . . .  44
   6.29   RFC 3123 A DNS RR Type 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 Lists of this
discussion.

5.01 Address Prefixes . . .  44
   6.30   RFC 1234 Tunneling IPX traffic through IP networks (IPX-IP) 3168 The section "Unicast Address Mappings" has the following text:

   For implementations Addition of this memo, the first two octets of the host
   number will always be zero and the last four octets will be the
   node's four octet Explicit Congestion
          Notification  (ECN) to IP address.  This makes address mapping trivial
   for unicast transmissions: the first two octets  . . . . . . . . . . . . . . . .  44
   6.31   RFC 3180 GLOP Addressing in 233/8  . . . . . . . . . . . .  44
   7.     Summary of the host number
   are discarded, leaving the normal four octet Results . . . . . . . . . . . . . . . . . .  45
   7.1    Standards  . . . . . . . . . . . . . . . . . . . . . . . .  45
   7.1.1  RFC 791 Internet Protocol  . . . . . . . . . . . . . . . .  45
   7.1.2  RFC 792 Internet Control Message Protocol  . . . . . . . .  45
   7.1.3  RFC 891 DCN Networks . . . . . . . . . . . . . . . . . . .  45
   7.1.4  RFC 894 IP address.  The
   encapsulation code should use this over Ethernet . . . . . . . . . . . . . . . . .  45
   7.1.5  RFC 895 IP address as the destination
   address of the UDP/IP tunnel packet.

This mapping will not be able to work with IPv6 addresses.

There are also numerous discussions on systems keeping a "peer list"
to map between IP and IPX addresses.  The specifics are not discussed over experimental Ethernets . . . . . . . . . .  45
   7.1.6  RFC 922 Broadcasting Internet Datagrams in the document Presence
          of Subnets . . . . . . . . . . . . . . . . . . . . . . . .  45
   7.1.7  RFC 950 Internet Standard Subnetting Procedure . . . . . .  46
   7.1.8  RFC 1034 Domain Names: Concepts and are left to the individual implementation.

The section "Maximum Transmission Unit"

   Although larger IPX packets are possible, the standard maximum
   transmission unit for IPX is 576 octets.  Consequently, 576 octets
   is the recommended default maximum transmission unit for IPX packets
   being sent with this encapsulation technique.  With the eight octet
   UDP header Facilities . . . . . .  46
   7.1.9  RFC 1035 Domain Names: Implementation and the 20 octet IP header, the resulting Specification  .  46
   7.1.10 RFC 1042 IP packets will
   be 604 octets long.  Note that this is larger than the 576 octet
   maximum size over IEEE 802  . . . . . . . . . . . . . . . .  46
   7.1.11 RFC 1044 IP implementations are required to accept [3].  Any over HyperChannel  . . . . . . . . . . . . . .  46
   7.1.12 RFC 1088 IP
   implementation supporting this encapsulation technique must be
   capable of receiving 604 octet over NetBIOS . . . . . . . . . . . . . . . . .  46
   7.1.13 RFC 1112 Host Extensions for IP packets.

   As improvements in protocols and hardware allow Multicast  . . . . . . . .  46
   7.1.14 RFC 1122 Requirements for larger,
   unfragmented Internet Hosts . . . . . . . . .  46
   7.1.15 RFC 1201 IP transmission units, the 576 octet maximum IPX packet
   size may become a liability.  For this reason, it is recommended
   that the IPX maximum transmission unit size be configurable in
   implementations of this memo.

also has some implications on over ARCNET  . . . . . . . . . . . . . . . . .  46
   7.1.16 RFC 1209 IP addressing.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.02 over SMDS  . . . . . . . . . . . . . . . . . .  47
   7.1.17 RFC 1256 ICMP Router 1390 Transmission of IP and ARP over FDDI Networks . .  47
   7.2    Draft Standards  . . . . . . . . . . . . . . . . . . . . .  47
   7.2.1  RFC 951 Bootstrap Protocol (BOOTP) . . . . . . . . . . . .  47
   7.2.2  RFC 1191 Path MTU Discovery Messages (ICMP-ROUT)

This  . . . . . . . . . . . . . . .  47
   7.2.3  RFC documents a protocol that is very specific to IPv4 1356 Multiprotocol Interconnect on X.25 and a
successor will be needed to provide the functionality.

5.03 ISDN . . .  47
   7.2.4  RFC 1990 The PPP Multilink Protocol (MP) . . . . . . . . .  47
   7.2.5  RFC 2067 IP over HIPPI . . . . . . . . . . . . . . . . . .  47
   7.2.6  RFC 2131 DHCP  . . . . . . . . . . . . . . . . . . . . . .  47
   7.3    Proposed Standards . . . . . . . . . . . . . . . . . . . .  48
   7.3.1  RFC 1234 Tunneling IPX over IP . . . . . . . . . . . . . .  48
   7.3.2  RFC 1256 ICMP Router Discovery . . . . . . . . . . . . . .  48
   7.3.3  RFC 1277 Encoding Network Net Addresses to Support Operation
      over Non-OSI
          Over Non OSI Lower Layers

Section 4.5  TCP/IP (RFC 1006) Network Specific Format states:

The IDP and 2 digit prefix identifies a TCP/IP network where  . . . . . . . . . . . . . . . .  48
   7.3.4  RFC 1006
is applied.  It is necessary to use an 1332 PPP Internet Protocol Control Protocol (IPCP) . .  48
   7.3.5  RFC 1469 IP Address, as there are
insufficient bits to fit in a domain.  It is structured as follows:

      __________________________________________________________
      |_Digit___||_1-12____|13-17_(optional)_|18-22_(optional)_|_
      |_Meaning_||IP_Address_|____port_______|__Transport_Set__|_

For TCP/IP there shall be a 20 digit long network-specific part.
First 12 digits are Multicast over Token Ring  . . . . . . . . . .  48
   7.3.6  RFC 2003 IP Encapsulation within IP  . . . . . . . . . . .  48
   7.3.7  RFC 2004 Minimal Encapsulation within IP . . . . . . . . .  48
   7.3.8  RFC 2022 Support for the Multicast over UNI 3.0/3.1 based
          ATM Networks . . . . . . . . . . . . . . . . . . . . . . .  48
   7.3.9  RFC 2113 IP Router Alert Option  . . . . . . . . . . . . .  48
   7.3.10 RFC 2165 SLP . . . . . . . . . . . . . . . . . . . . . . .  49
   7.3.11 RFC 2225 Classical IP & ARP over ATM . . . . . . . . . . .  49
   7.3.12 RFC 2226 IP Broadcast over ATM . . . . . . . . . . . . . .  49
   7.3.13 RFC 2371 Transaction IPv3  . . . . . . . . . . . . . . . .  49
   7.3.14 RFC 2625 IP address.  The port number can be up to
65535, and needs 5 digits (this is optional, and is defaulted as
defined in ARP over Fibre Channel . . . . . . . . . .  49
   7.3.15 RFC 1006).  Finally, there is 2672 Non-Terminal DNS Redirection  . . . . . . . . . .  49
   7.3.16 RFC 2673 Binary Labels in DNS  . . . . . . . . . . . . . .  49
   7.3.17 IP over Vertical Blanking Interval of a third part to the address,
which is defined here as ``transport set'' that indicates what kind of
IP-based transport protocols is used.  This is a decimal number from
0-65535 which is really a 16-bit flag word.  1 is TCP, 2 is UDP.
Further values of this code are assigned by the IANA. If the transport
set is not there or no bits are set, it means ``default'' which is
TCP. This is encoded in 5 digits.

For example, the IP Address 10.0.0.6 with port 9 over UDP is encoded
as:

_______________________________________________________________________
|Part_____|_|_____IDP_________|___________________DSP__________________|
_
|Component|_|AFI__|___IDI_____|Prefix|___IP_Address____|_Port__|_T_Set_|
_
|Octet____|_|____|____________|_1-2__|______3-14_______|_15-19_|_20-24_|
_
|Value____|T|elex_|007_28722__|__03__|_010_000_000_006_|_00009_|_00002_|
__
|Cncrt_Dec|_|54___|007_28722__|__03__|_010_000_000_006_|_00009_|_00002_|
_
|Cncrt_Bin|_|54___|00_72_87_22_|_03__|01_00_00_00_00_06|00_00_9|0_00_02|
_
 Internet Area: Survey of TV Signal (RFC
          2728)  . . . . . . . . . . . . . . . . . . . . . . . . . .  49
   7.3.18 RFC 2734 IPv4 Addresses Currently Deployed  Mar. 2003

This 12 octet field for decimal versions of over IEEE 1394 . . . . . . . . . . . . . . .  49
   7.3.19 RFC 2834 ARP & IP addresses is
insufficient Broadcasts Over HIPPI 800  . . . . . . .  49
   7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400 . . . . . . .  50
   7.3.21 RFC 3344 Mobility Support for a decimal version of IPv6 addresses.  It is possible
to define a new encoding IPv4 . . . . . . . . . . . .  50
   7.3.22 RFC 3376 Internet Group Management Protocol, Version 3 . .  50
   7.4    Experimental RFCs  . . . . . . . . . . . . . . . . . . . .  50
   7.4.1  RFC 1393 Traceroute using the 20 digit long IP Address + Port +
Transport Set fields in order to accommodate a binary version of an
IPv6 address, port number and Transport Set.  There are several
schemes that could be envisioned.

5.04 IP Option . . . . . . . . . .  50
   7.4.2  RFC 1332 The PPP Internet Protocol 1307 Dynamically Switched Link Control Protocol (IPCP)
      (PPP-IPCP)  . . .  50
   7.4.3  RFC 1735 NBMA Address Resolution Protocol (NARP) . . . . .  50
   7.4.4  RFC 1788 ICMP Domain Name Messages . . . . . . . . . . . .  50
   7.4.5  RFC 1868 ARP Extension - UNARP . . . . . . . . . . . . . .  50
   7.4.6  RFC 2143 IP Over SCSI  . . . . . . . . . . . . . . . . . .  51
   7.4.7  RFC 3180 GLOP Addressing in 233/8  . . . . . . . . . . . .  51
   8.     Security Considerations  . . . . . . . . . . . . . . . . .  52
   9.     Acknowledgements . . . . . . . . . . . . . . . . . . . . .  53
          Normative References . . . . . . . . . . . . . . . . . . .  54
          Authors' Addresses . . . . . . . . . . . . . . . . . . . .  54
          Intellectual Property and Copyright Statements . . . . . .  55

1. Introduction

   This document defines is part of a protocol for devices document set aiming to assign document all usage
   of IPv4 addresses in IETF standards. In an effort to PPP clients once PPP negotiation is completed.  Section 3.  IPCP
Configuration Options defines have the following:

The most up-to-date values
   information in a manageable form, it has been broken into 7 documents
   conforming to the current IETF areas (Application,  Internet,
   Management & Operations, Routing, Security, Sub-IP and Transport).

   This specific document focuses on usage of IPv4 addresses within the IPCP Option Type field are specified
in
   Internet area.

   For a full introduction, please see the most recent "Assigned Numbers" RFC [6].  Current values are
assigned as follows:

   1       IP-Addresses
   2       IP-Compression-Protocol
   3       IP-Address

3.1.  IP-Addresses

   Description introduction [1] document.

2. Document Organization

   The use of following sections 3, 4, 5, and 6 each describe the Configuration Option IP-Addresses has been
      deprecated.  It has been determined through implementation
      experience that it raw analysis
   of Full, Draft, and Proposed Standards, and Experimental RFCs.  Each
   RFC is difficult to ensure negotiation convergence discussed in all cases using this option. turn starting with RFC 1172 [7] provides
      information for implementations requiring backwards
      compatibility.  The IP-Address Configuration Option replaces
      this option, 1 and its use ending in (about)
   RFC 3100. The comments for each RFC are "raw" in nature.  That is,
   each RFC is preferred.

      This option should not be sent discussed in a Configure-Request if a
      Configure-Request has been received which includes either an IP-
      Addresses vacuum and problems or IP-Address option.  This option MAY be sent issues discussed do
   not "look ahead" to see if a
      Configure-Reject is received for any of the IP-Address option, or a
      Configure-Nak issues raised have already been
   fixed.

   Section 7 is received with an IP-Addresses option as an
      appended option.

      Support for this option MAY be removed after the IPCP protocol
      status advances to Internet Draft Standard.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

3.3.  IP-Address

   Description

      This Configuration Option provides a way to negotiate the IP
      address to be used on the local end analysis of the link.  It allows the
      sender data presented in Sections 3, 4, 5,
   and 6.  It is here that all of the Configure-Request to state which IP-address is
      desired, or results are considered as a whole
   and the problems that have been resolved in later RFCs are
   correlated.

3. Full Standards

   Full Internet Standards (most commonly simply referred to request as
   "Standards") are fully mature protocol specification that are widely
   implemented and used throughout the peer provide the information.
      The peer can provide this information Internet.

3.1 RFC 791 Internet Protocol

   This specification defines IPv4 and is replaced by NAKing the option, IPv6
   specifications.

3.2 RFC 792 Internet Control Message Protocol

   This specification defines ICMP, and
      returning a valid IP-address.

      If negotiation about the remote IP-address is required, and the
      peer did not provide the option inherently IPv4 dependent.

3.3 RFC 826 Ethernet Address Resolution Protocol

   There are no IPv4 dependencies in its Configure-Request, this specification.

3.4 RFC 891 DCN Local-Network Protocols

   There are many implicit assumptions about the
      option should be appended to a Configure-Nak.  The value use of IPv4 addresses
   in this document.

3.5 RFC 894 Standard for the
      IP-address given must be acceptable as transmission of IP datagrams over Ethernet
    networks

   This specification specifically deals with the remote IP-address, or
      indicate a request that transmission of IPv4
   packets over Ethernet.

3.6 RFC 895 Standard for the peer provide transmission of IP datagrams over
    experimental Ethernet networks

   This specification specifically deals with the information.

      By default, transmission of IPv4
   packets over experimental Ethernet.

3.7 RFC 903 Reverse Address Resolution Protocol

   There are no IP address IPv4 dependencies in this specification.

3.8 RFC 919 Broadcasting Internet Datagrams

   This specification defines broadcasting for IPv4; IPv6 uses multicast
   so this is assigned.

   A summary not applicable.

3.9 RFC 922 Broadcasting Internet datagrams in the presence of subnets

   This specification defines how broadcasts should be treated in the IP-Address Configuration Option format
   presence of subnets. IPv6 uses multicast so this is shown
   below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |           IP-Address
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
           IP-Address (cont)       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Type

      3

   Length

      6

   IP-Address

      The four octet IP-Address not applicable.

3.10 RFC 950 Internet Standard Subnetting Procedure

   This specification defines IPv4 subnetting; similar functionality is the desired local address
   part of IPv6 addressing architecture to begin with.

3.11 RFC 1034 Domain Names: Concepts and Facilities

   In Section 3.6, "Resource Records", the
      sender definition of A record is:

     RDATA           which is the type and sometimes class dependent
                     data which describes the resource:

                     A         For the IN class, a Configure-Request.  If all four octets are set 32 bit IP address

   And Section 5.2.1, "Typical functions" defines:

     1. Host name to
      zero, host address translation.

        This function is often defined to mimic a previous HOSTS.TXT
        based function.  Given a character string, the caller wants
        one or more 32 bit IP addresses.  Under the DNS, it indicates
        translates into a request that for type A RRs.  Since the peer provide DNS does

        not preserve the IP-Address
      information.

   Default

      No IP address is assigned.

 Internet Area: Survey order of IPv4 Addresses Currently Deployed  Mar. 2003

It is clearly designed RRs, this function may choose to allow new Option Types
        sort the returned addresses or select the "best" address if
        the service returns only one choice to the client.  Note that
        a multiple address return is recommended, but a single
        address may be added and should
offer no problems for use with IPv6 once appropriate options have been
defined.

5.05 RFC 1377 The PPP OSI Network Layer Control Protocol (OSINLCP)
      (PPP-OSINLC)

There are no IPv4 dependencies in this protocol.

5.06 RFC 1378 The PPP AppleTalk Control Protocol (ATCP) (PPP-ATCP)

There are no IPv4 dependencies in this protocol.

5.07 RFC 1469 IP Multicast over Token-Ring Local Area Networks
      (IP-TR-MC) the only way to emulate prior HOSTS.TXT
        services.

     2. Host address to host name translation

        This document defines function will often follow the usage form of IPv4 multicast over IEEE 802.5
Token Ring networks.  A new method for IPv6 multicast over these
networks will need to be defined.

5.08 RFC 1552 previous
        functions.  Given a 32 bit IP address, the caller wants a
        character string.  The PPP Internetworking Packet Exchange Control
      Protocol (IPXCP) (IPXCP)

There are no IPv4 dependencies in this protocol.

5.09 RFC 1570 PPP LCP Extensions (PPP-LCP)

There are no IPv4 dependencies in this protocol.

5.10 RFC 1598 PPP in X.25 PPP-X25

There are no IPv4 dependencies in this protocol.

5.11 RFC 1618 PPP over ISDN (PPP-ISDN)

There are no IPv4 dependencies in this protocol.

5.12 RFC 1663 PPP Reliable Transmission (PPP-TRANS)

There are no IPv4 dependencies in this protocol.

 Internet Area: Survey octets of IPv4 Addresses Currently Deployed  Mar. 2003

5.13 RFC 1752 The Recommendation for the IP Next Generation Protocol
      (IPNG)

This document defines a roadmap for IPv6 development address are reversed,
        used as name components, and suffixed with "IN-ADDR.ARPA".  A
        type PTR query is not
relevant used to this discussion.

5.14 RFC 1755 ATM Signaling Support get the RR with the primary name of
        the host.  For example, a request for the host name
        corresponding to IP over ATM (ATM) address 1.2.3.4 looks for PTR RRs for
        domain name "4.3.2.1.IN-ADDR.ARPA".

   There are no are, of course, numerous examples of IPv4 dependencies in this protocol.

5.15 RFC 1763 The PPP Banyan Vines Control Protocol (BVCP) (BVCP)

There are no IPv4 dependencies in this protocol.

5.16 RFC 1764 The PPP XNS IDP Control Protocol (XNSCP) (XNSCP)

There are no IPv4 dependencies in this protocol.

5.17 RFC 1886 DNS Extensions to support IP version 6 (DNS-IPV6)

This addresses scattered
   throughout the document.

3.12 RFC 1035 Domain Names: Implementation and Specification

   Section 3.4.1, "A RDATA format", defines the AAAA record format for IPv6 as well as PTR records
using the ip6.int domain.  There is currently a large debate going
on in the IPv6 and DNS community over the validity of AAAA versus
A6 A records:

         +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
         |                    ADDRESS                    |
         +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

     where:

     ADDRESS         A 32 bit Internet address.

     Hosts that have multiple Internet addresses will have
     multiple A records.

5.18 RFC 1973 PPP in Frame Relay (PPP-FRAME)

There are

     A records cause no IPv4 dependencies additional section processing.  The
     RDATA section of an A line in this protocol.

5.19 RFC 1981 Path MTU Discovery for a master file is an Internet
     address expressed as four decimal numbers separated by dots
     without any imbedded spaces (e.g.,"10.2.0.52" or "192.0.5.6").

   And Section 3.4.2, "WKS RDATA", format is:

     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
     |                    ADDRESS                    |
     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
     |       PROTOCOL        |                       |
     +--+--+--+--+--+--+--+--+                       |
     |                                               |
     /                   <BIT MAP>                   /

     /                                               /
     +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

       where:

       ADDRESS         An 32 bit Internet address

       PROTOCOL        An 8 bit IP version 6 MTU-IPV6

This protocol describes number

       <BIT MAP>       A variable length bit map.  The bit map
                   must be a multiple of 8 bits long.

       The WKS record is used to describe the well known services
       supported by a particular protocol on a particular internet
       address.  The PROTOCOL field specifies an IPv6 related IP protocol number,
       and is not discussed
in this document.

5.20 RFC 1982 Serial Number Arithmetic (SNA)

There are no IPv4 dependencies in this the bit map has one bit per port of the specified protocol.

 Internet Area: Survey
       The first bit corresponds to port 0, the second to port 1, etc.
       If the bit map does not include a bit for a protocol of IPv4 Addresses Currently Deployed  Mar. 2003

5.21 RFC 1995 Incremental Zone Transfer
       interest, that bit is assumed zero.  The appropriate values and
       mnemonics for ports and protocols are specified in DNS (DNS-IZT)

Although [RFC-1010].

       For example, if PROTOCOL=TCP (6), the examples used in 26th bit corresponds to
       TCP port 25 (SMTP).  If this document use IPv4 addresses,
(i.e. A records) there bit is nothing in set, a SMTP server should be
       listening on TCP port 25; if zero, SMTP service is not supported
       on the protocol specified address.

       The purpose of WKS RRs is to preclude
full and proper functionality using IPv6.

5.22 RFC 1996 A Mechanism provide availability information for Prompt Notification of Zone Changes (DNS
      NOTIFY) (DNS-NOTIFY)

There
       servers for TCP and UDP.  If a server supports both TCP and UDP,
       or has multiple Internet addresses, then multiple WKS RRs are
       used.

       WKS RRs cause no IPv4 dependencies in this protocol.

5.23 RFC 2002 IP Mobility Support (MOBILEIPSU)

This document additional section processing.

   Section 3.5, "IN-ADDR.ARPA domain", describes reverse DNS lookups and
   is designed for use in clearly IPv4 networks. dependent.

   There are are, of course, numerous referrals to other IP "support" mechanisms (i.e. ICMP
Router Discover Messages) that specifically refer to the examples of IPv4 addresses scattered
   throughout the document.

3.13 RFC 1042 Standard for the transmission of ICMP.  An IP Mobility protocol for IPv6 is required.

5.24 RFC 2003 IP Encapsulation within IP (IPENCAPIP) datagrams over IEEE
     802 networks

   This document is designed for use in specification specifically deals with the transmission of IPv4
   packets over IEEE 802 networks.

3.14 RFC 1044 Internet Protocol on Network System's HYPERchannel:
     Protocol Specification

   There are
many referenced to a specified IP version number variety of 4 and 32-bit
addresses.  An IPv6 Encapsulation within IPv6 is required.

5.25 methods used in this standard to map IPv4
   addresses to 32 bits fields in the HYPERchannel headers.  This
   specification does not support IPv6.

3.15 RFC 2004 Minimal Encapsulation within 1055 Nonstandard for transmission of IP (MINI-IP) datagrams over serial
     lines: SLIP

   This document specification is designed more of a analysis of the shortcomings of SLIP
   which is unsurprising.  The introduction of PPP as a general
   replacement of SLIP has made this specification essentially unused.
   No update need be considered.

3.16 RFC 1088 Standard for use in IPv4 networks.  There are
many referenced to the transmission of IP datagrams over NetBIOS
     networks

   This specification documents a specified technique to encapsulate IP version number packets
   inside NetBIOS packets.

   The technique presented of 4 and 32-bit
addresses.  A Minimal using NetBIOS names of the form
   IP.XX.XX.XX.XX will not work for IPv6 Encapsulation within addresses since the length of
   IPv6 is required.

5.26 addresses will not fit within the NetBIOS 15 octet name
   limitation.

3.17 RFC 2005 Applicability Statement 1112 Host Extensions for IP Mobility Support Multicasting

   This specification defines IP multicast.  Parts of the document are
   IPv4 dependent.

3.18 RFC documents 1132 Standard for the interoperation transmission of 802.2 packets over IPX
     networks

   There are no IPv4 mobility as documented dependencies in the preceding 3 section.

5.27 this specification.

3.19 RFC 2022 Support for Multicast 1201 Transmitting IP traffic over UNI 3.0/3.1 based ATM
      Networks (MULTI-UNI)

This protocol specifically maps ARCNET networks

   The major concerns of this specification with respect to IPv4 multicast and a new version
   addresses occur in the resolution of ARCnet 8bit addresses to IPv4
   addresses in an "ARPlike" method.  This is
required incompatible with IPv6.

3.20 RFC 1209 The Transmission of IP Datagrams over the SMDS Service

   This specification defines running IPv4 and ARP over SMDS.  The
   methods described could easily be extended to support IPv6 multicast.

5.28 packets.

3.21 RFC 2043 The PPP SNA Control Protocol (SNACP) (PPP-SNACP)

There are no IPv4 dependencies in this protocol.

 Internet Area: Survey 1390 Transmission of IP and ARP over FDDI Networks

   This specification defines the use of IPv4 Addresses Currently Deployed  Mar. 2003

5.29 RFC 2097 The PPP NetBIOS Frames Control Protocol (NBFCP)
      (PPP-NBFCP) address on FDDI networks.
   There are no numerous IPv4 dependencies in this protocol.

5.30 RFC 2113 IP Router Alert Option (ROUT-ALERT)

This document provides the specification.

   In particular the value of the Protocol Type Code (2048 for IPv4) and
   a new mechanism corresponding Protocol Address length (4 bytes for IPv4.  It IPv4) needs to
   be created.  A discussion of broadcast and multicast addressing
   techniques is expected that
a similar functionality will also included, and similarly must be included in updated for IPv6
   networks.  The defined MTU limitation of 4096 octets of data (with
   256 octets reserved header space) should remain sufficient for IPv6.

5.31

3.22 RFC 2125 The PPP Bandwidth Allocation Protocol (BAP) / 1661 The
      PPP Bandwidth Allocation Control Point-to-Point Protocol (BACP) (BAP-BACP) (PPP)

   There are no IPv4 dependencies in this protocol.

5.32 specification.

3.23 RFC 2136 Dynamic Updates 1662 PPP in the Domain Name System (DNS
      UPDATE) (DNS-UPDATE) HDLC-like Framing

   There are no IPv4 dependencies in this protocol.

5.33 specification.

3.24 RFC 2181 Clarifications to the DNS Specification (DNS-CLAR) 2427 Multiprotocol Interconnect over Frame Relay

   There are no IPv4 dependencies in this protocol.  The only reference
to IP addresses discuss specification.

4. Draft Standards

   Draft Standards represent the use of any cast address, so it should be
assumed that these mechanisms penultimate standard level in the IETF.
   A protocol can only achieve draft standard when there are IPv6 operable.

5.34 RFC 2225 Classical IP multiple,
   independent, interoperable implementations.  Draft Standards are
   usually quite mature and ARP over ATM (IP-ATM)

>From the many references in this document it is clear that this
document widely used.

4.1 RFC 951 Bootstrap Protocol (BOOTP)

   This protocol is designed specifically for IPv4 only.  It use with IPv4, for
   example:

    Section 3. Packet Format

    All numbers shown are decimal, unless indicated otherwise.  The
    BOOTP packet is only later enclosed in the
document that a standard IP [8] UDP [7] datagram.  For
    simplicity it is implicitly stated, as in:

     ar$spln -  length in octets of assumed that the source protocol address. Value
                range is 0 or 4 (decimal).  For IPv4 ar$spln BOOTP packet is 4.

     ar$tpln -  length never fragmented.
    Any numeric fields shown are packed in octets of 'standard network byte
    order', i.e. high order bits are sent first.

    In the target protocol address. Value
                range is 0 or 4 (decimal).  For IPv4 ar$tpln is 4.
and

   For backward compatibility with previous implementations, IP header of a null
   IPv4 protocol bootrequest, the client fills in its own IP
    source address may be received with length = 4 and an
   allocated if known, otherwise zero.  When the server address in storage set to is
    unknown, the value 0.0.0.0.  Receiving
   stations must be liberal in accepting this format of a null IPv4
   address.  However, on transmitting an ATMARP or InATMARP packet, a
   null IPv4 IP destination address must only will be indicated by the length set to zero
   and must have no storage allocated.

 Internet Area: Survey 'broadcast address'
    255.255.255.255.  This address means 'broadcast on the local cable,
    (I don't know my net number)' [4].

         FIELD   BYTES   DESCRIPTION
         -----   -----   ---

     [...]
            ciaddr  4       client IP address;
                            filled in by client in bootrequest if known.

            yiaddr  4       'your' (client) IP address;
                            filled by server if client doesn't
                            know its own address (ciaddr was 0).

            siaddr  4       server IP address;
                            returned in bootreply by server.

            giaddr  4       gateway IP address,
                            used in optional cross-gateway booting.

   Since the packet format is a fixed 300 bytes in length, an updated
   version of IPv4 Addresses Currently Deployed  Mar. 2003

A new the specification for could easily accommodate an additional
   48 bytes (4 IPv6 must be defined.

5.35 fields of 16 bytes to replace the existing 4 IPv4
   fields of 4 bytes).

4.2 RFC 2226 1188 Proposed Standard for the Transmission of IP Broadcast  Datagrams
    over ATM FDDI Networks

   This document is limited to IPv4 multicasting.  A new clearly informally superceded by RFC 1390,
   "Transmission of IP and ARP over FDDI Networks", even though no
   formal deprecation has been done.  Therefore, this specification
for IPv6 must be defined.

5.36 is
   not considered further in this memo.

4.3 RFC 2236 Internet Group Management Protocol, Version 2 (IGMP)

This document describes 1191 Path MTU discovery

   The entire process of version PMTU discovery is predicated on the use of IGMP used for IPv4 multicast.
A similar methodology for IPv6 multicast needs to be defined.

5.37 RFC 2241 DHCP Options for Novell Directory Services
      (DHCP-NDS)

This document defines extensions for the
   DF bit in the IPv4 only version of
DHCP header, an ICMP message (also IPv4 dependent) and it
   TCP MSS option.  This is expected that similar options will be present in
DHCPv6.

5.38 not compatible with IPv6.

4.4 RFC 2242 NetWare/IP Domain Name 1356 Multiprotocol Interconnect on X.25 and Information (NETWAREIP)

Once again these are options to the IPv4 version of DHCP.  It ISDN

   Section 3.2 defines an NLPID for IP as follows:

      The value hex CC (binary 11001100, decimal 204) is
expected IP [6].
      Conformance with this specification requires that similar options will IP be supported.
      See section 5.1 for a diagram of the packet formats.

   Clearly a new NLPID would need to be defined for IPv6 will exist packets.

4.5 RFC 1534 Interoperation Between DHCP and BOOTP

   There are no IPv4 dependencies in DHCPv6.

   PREFERRED_DSS (code 6)

      Length is (n * 4) this specification.

4.6 RFC 1542 Clarifications and Extensions for the value is an array of n IP addresses,
      each four bytes Bootstrap Protocol

   There are no new issues other than those presented in Section 4.1.

4.7 RFC 1629 Guidelines for OSI NSAP Allocation in length. The maximum number of addresses is 5
      and therefore the maximum length value is 20. Internet

   There are no IPv4 dependencies in this specification.

4.8 RFC 1762 The list contains
      the addresses of n NetWare Domain SAP/RIP Server (DSS).

   NEAREST_NWIP_SERVER (code 7)

      Length is (n * 4) and the value is an array of n IP addresses,
      each four bytes PPP DECnet Phase IV Control Protocol (DNCP)

   There are no IPv4 dependencies in length. this specification.

4.9 RFC 1989 PPP Link Quality Monitoring

   There are no IPv4 dependencies in this specification.

4.10 RFC 1990 The maximum number of addresses PPP Multilink Protocol (MP)

   Section 5.1.3, "Endpoint Discriminator Option", defines a Class
   header field:

      Class
         The Class field is 5 one octet and therefore indicates the maximum length value is 20. identifier

         address space.  The list contains
      the addresses of n Nearest NetWare/IP servers.

   PRIMARY_DSS (code 11)

      Length most up-to-date values of 4, and the value is a single IP address.  This LCP Endpoint
         Discriminator Class field
      identifies the Primary Domain SAP/RIP Service server (DSS) for
      this NetWare/IP domain. NetWare/IP administration utility uses
      this value as Primary DSS server when configuring a secondary
      DSS server.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.39 RFC 2290 Mobile-IPv4 Configuration Option for PPP IPCP

This protocol is IPv4 specific.  It is expected that similar
methods will be developed for Mobile IPv6.

5.40 RFC 2308 Negative Caching of DNS Queries (DNS NCACHE)
      (DNS-NCACHE)

Although there are numerous examples in this document that use
IPv4 "A" records, there is nothing specified in the protocol that limits
its effectiveness to IPv4.

5.41 most recent
         "Assigned Numbers" RFC 2331 ATM Signaling Support for IP over ATM - UNI Signaling
      4.0 Update (UNI-SIG)

There [7].  Current values are no IPv4 dependencies in this protocol.

5.42-zzzz RFC 2333 NHRP assigned as
         follows:

           0    Null Class

           1    Locally Assigned Address

           2    Internet Protocol Applicability

There are IPv4 dependencies within this RFC.

5.43-zzzz RFC 2335 A Distributed NHRP Service Using SCSP

There are IPv4 dependencies within this RFC.

5.44 RFC 2363 (IP) Address

           3    IEEE 802.1 Globally Assigned MAC Address

           4    PPP Over FUNI (PPP-FUNI)

There are no IPv4 dependencies in this protocol.

5.45 Magic-Number Block

           5    Public Switched Network Directory Number

   A new class field needs to be defined by the IANA for IPv6 addresses.

4.11 RFC 2364 1994 PPP Over AAL5 (PPP-AAL) Challenge Handshake Authentication Protocol (CHAP)

   There are no IPv4 dependencies in this protocol.

5.46 specification.

4.12 RFC 2371 Transaction Internet Protocol Version 3.0 TIPV3

This document states:

   TIP transaction manager addresses take 2067 IP over HIPPI

   Section 5.1, "Packet Formats", contains the form:

     <hostport><path>

   The <hostport> component comprises:

     <host>[:<port>]
 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

   where <host> is either a <dns name> or an <ip address>; and <port> following excerpt:

    EtherType (16 bits) SHALL be set as defined in Assigned Numbers [8]:
    IP = 2048 ('0800'h), ARP = 2054 ('0806'h), RARP = 32,821 ('8035'h).

   Section 5.5, "MTU", has the following definition:

     The MTU for HIPPI-SC LANs is a decimal number specifying 65280 bytes.

     This value was selected because it allows the port IP packet to fit in
     one 64K byte buffer with up to 256 bytes of overhead.  The overhead
     is 40 bytes at which the transaction
   manager (or proxy) present time; there are 216 bytes of room for
     expansion.

            HIPPI-FP Header                  8 bytes
            HIPPI-LE Header                 24 bytes
            IEEE 802.2 LLC/SNAP Headers      8 bytes
            Maximum IP packet size (MTU) 65280 bytes
                                         ------------
                              Total      65320 bytes (64K - 216)
   This definition is listening not applicable for requests to establish TIP
   connections. If IPv6 packets since packets can
   be larger than the port number IPv4 limitation of 65280 bytes.

4.13 RFC 2131 Dynamic Host Configuration Protocol

   This version of DHCP is omitted, the standard TIP port
   number (3372) highly assumptive of IPv4.  It is used.

   A <dns name> not
   compatible with IPv6.

4.14 RFC 2132 DHCP Options and BOOTP Vendor Extensions

   This is a standard name, acceptable to the domain name
   service. It must be sufficiently qualified to be useful an extension to the
   receiver of the command.

   An <ip address> is an IP address, IPv4-only specification.

4.15 RFC 2390 Inverse Address Resolution Protocol

   There are no IPv4 dependencies in the usual form: four decimal
   numbers separated by period characters. this specification.

4.16 RFC 2460 Internet Protocol, Version 6 (IPv6) Specification

   This document defines IPv6 and further along it states:

  A TIP URL takes the form:

     tip://<transaction manager address>?<transaction string>

   where <transaction manager address> identifies has no IPv4 issues.

4.17 RFC 2461 Neighbor Discovery for IP Version 6 (IPv6)

   This document defines an IPv6 related specification and has no IPv4
   issues.

4.18 RFC 2462 IPv6 Stateless Address Autoconfiguration

   This document defines an IPv6 related specification and has no IPv4
   issues.

4.19 RFC 2463 Internet Control Message Protocol (ICMPv6) for the TIP transaction
   manager (as defined in Section 7 above);
     Internet Protocol Version 6 (IPv6) Specification

   This document defines an IPv6 related specification and <transaction string>
   specifies a transaction identifier, which may take one of two forms
   (standard or non-standard):

   i. "urn:" <NID> ":" <NSS>

     A standard transaction identifier, conforming has no IPv4
   issues.

4.20 RFC 3596 DNS Extensions to support IP version 6

   This specification defines the proposed
     Internet Standard AAAA record for Uniform Resource Names (URNs), IPv6 as specified
     by RFC2141; where <NID> is well as PTR
   records using the Namespace Identifier, ip6.arpa domain, and <NSS> is as such has no IPv6 issues.

5. Proposed Standards

   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 Namespace Specific String. The Namespace ID determines IETF standards
   process.  They therefore are often just proposed ideas that are
   presented to the
     syntactic interpretation Internet community.  Sometimes flaws are exposed or
   they are one of the Namespace Specific String. The
     Namespace Specific String many competing solutions to problems.  In these later
   cases, no discussion is a sequence of characters representing
     a transaction identifier (as defined by <NID>). presented as it would not serve the purpose
   of this discussion.

5.1 RFC 1234 Tunneling IPX traffic through IP networks

   The rules for section "Unicast Address Mappings" has the
     contents following text:

    For implementations of these fields are specified by [6] (valid characters,
     encoding, etc.).

     This format this memo, the first two octets of <transaction string> may the host
    number will always be used to express global
     transaction identifiers in terms of standard representations.
     Examples for <NID> might zero and the last four octets will be <iso> or <xopen>. e.g.

       tip://123.123.123.123/?urn:xopen:xid

     Note that Namespace Ids require registration. See [7] the
    node's four octet IP address.  This makes address mapping trivial
    for details
     on how to do this.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

   ii. <transaction identifier>

     A sequence unicast transmissions: the first two octets of printable ASCII characters (octets with values in the range 32 through 126 inclusive (excluding ":") representing a
     transaction identifier. In host number
    are discarded, leaving the normal four octet IP address.  The
    encapsulation code should use this non-standard case, it is IP address as the
     combination destination
    address of <transaction manager address> and <transaction
     identifier> which ensures global uniqueness. e.g.

       tip://123.123.123.123/?transid1

It is the UDP/IP tunnel packet.

   This mapping will not hard be able to assume that the production of an updated protocol
specification that supports work with IPv6 could be accomplished.

5.47 RFC 2373 addresses.

   There are also numerous discussions on systems keeping a "peer list"
   to map between IP Version 6 Addressing Architecture,

This RFC documents IPv6 addressing and is IPX addresses.  The specifics are not discussed
   in this
document.

5.48 RFC 2374 An IPv6 Aggregatable Global Unicast Address Format,

This RFC documents IPv6 addressing the document and is not discussed in this
document.

5.49 RFC 2464 are left to the individual implementation.

   The section "Maximum Transmission of IPv6 Packets over Ethernet Networks

This RFC documents a method for transmitting IPv6 Unit" also has some implications on
   IP addressing:

    Although larger IPX packets over
ethernet and are possible, the standard maximum
    transmission unit for IPX is not considered in this discussion.

5.50 RFC 2470 Transmission of IPv6 Packets over Token Ring
      Networks

This RFC documents a method 576 octets.  Consequently, 576 octets
    is the recommended default maximum transmission unit for transmitting IPv6 IPX packets over
token ring
    being sent with this encapsulation technique.  With the eight octet
    UDP header and the 20 octet IP header, the resulting IP packets will
    be 604 octets long.  Note that this is not considered in larger than the 576 octet
    maximum size IP implementations are required to accept [3].  Any IP
    implementation supporting this discussion.

5.51 RFC 2472 encapsulation technique must be
    capable of receiving 604 octet IP Version 6 over PPP (IPv6-PPP)

This RFC documents a method for transmitting IPv6 packets over
PPP packets.

    As improvements in protocols and hardware allow for larger,
    unfragmented IP transmission units, the 576 octet maximum IPX packet
    size may become a liability.  For this reason, it is not considered recommended
    that the IPX maximum transmission unit size be configurable in
    implementations of this discussion.

5.52 memo.

5.2 RFC 2473 Generic Packet Tunneling in IPv6 Specification 1256 ICMP Router Discovery Messages

   This specification defines a mechanism very specific to IPv4.

5.3 RFC documents an IPv6 aware protocol and is not considered
in this discussion.

 Internet Area: Survey of IPv4 1277 Encoding Network Addresses Currently Deployed  Mar. 2003

5.53 to Support Operation over
    Non-OSI Lower Layers

   Section 4.5, "TCP/IP (RFC 1006) Network Specific Format" describes a
   structure that reserves 12 digits for the textual representation of
   an IP address.

   This 12 octet field for decimal versions of IP addresses is
   insufficient for a decimal version of IPv6 addresses.  It is possible
   to define a new encoding using the 20 digit long IP Address + Port +
   Transport Set fields in order to accommodate a binary version of an
   IPv6 address, port number and Transport Set.  There are several
   schemes that could be envisioned.

5.4 RFC 2484 1332 The PPP LCP Internationalization Internet Protocol Control Protocol (IPCP)

   This specification defines a mechanism for devices to assign IPv4
   addresses to PPP clients once PPP negotiation is completed.  Section
   3, "IPCP Configuration Options", defines IPCP option types which
   embed the IP address in 4-byte long fields.  This is clearly not
   enough for IPv6.

   However, the specification is clearly designed to allow new Option
   Types to be added and Should offer no problems for use with IPv6 once
   appropriate options have been defined.

5.5 RFC 1377 The PPP OSI Network Layer Control Protocol (OSINLCP)

   There are no IPv4 dependencies in this protocol.

5.54 specification.

5.6 RFC 2485 DHCP Option for 1378 The Open Group's User
      Authentication PPP AppleTalk Control Protocol (ATCP)

   There are no IPv4 dependencies in this specification.

5.7 RFC 1469 IP Multicast over Token-Ring Local Area Networks

   This document defines extensions for the IPv4 only version usage of
DHCP and it IPv4 multicast over IEEE 802.5
   Token Ring networks.  This is expected that similar options will be present in
DHCPv6.

5.55 not compatible with IPv6.

5.8 RFC 2486 1552 The Network Access Identifier (NAI) PPP Internetworking Packet Exchange Control Protocol
    (IPXCP)

   There are no IPv4 dependencies in this protocol.

5.56 specification.

5.9 RFC 2491 IPv6 over Non-Broadcast Multiple Access
      (NBMA) networks (IPv6-NBMA)

This RFC documents a method for transmitting IPv6 packets over
NBMA networks and is not considered 1570 PPP LCP Extensions

   There are no IPv4 dependencies in this discussion.

5.57 specification.

5.10 RFC 2492 IPv6 over ATM Networks (IPv6ATMNET)

This 1598 PPP in X.25 PPP-X25

   There are no IPv4 dependencies in this specification.

5.11 RFC documents a method for transmitting IPv6 packets 1618 PPP over
ATM networks and is not considered ISDN

   There are no IPv4 dependencies in this discussion.

5.58 specification.

5.12 RFC 2497 1663 PPP Reliable Transmission of IPv6 Packets over ARCnet
      Networks

This

   There are no IPv4 dependencies in this specification.

5.13 RFC documents 1752 The Recommendation for the IP Next Generation Protocol

   This document defines a method roadmap for transmitting IPv6 packets over
ARCnet networks development and is not considered in
   relevant to this discussion.

5.59

5.14 RFC 2507 1755 ATM Signaling Support for IP Header Compression

This protocol is both over ATM

   There are no IPv4 and IPv6 aware.

5.60 RFC 2526 Reserved IPv6 Subnet Anycast Addresses

This dependencies in this specification.

5.15 RFC documents IPv6 addressing and is not discussed 1763 The PPP Banyan Vines Control Protocol (BVCP)

   There are no IPv4 dependencies in this
document.

 Internet Area: Survey of specification.

5.16 RFC 1764 The PPP XNS IDP Control Protocol (XNSCP)

   There are no IPv4 Addresses Currently Deployed  Mar. 2003

5.61 dependencies in this specification.

5.17 RFC 2529 Transmission of IPv6 over 1973 PPP in Frame Relay

   There are no IPv4 Domains without
      Explicit Tunnels

This dependencies in this specification.

5.18 RFC documents 1981 Path MTU Discovery for IP version 6

   This specification describes an IPv6 transmission methods related specification and is not
   discussed in this document.

5.62

5.19 RFC 2563 DHCP Option to Disable Stateless Auto-Configuration
      in 1982 Serial Number Arithmetic

   There are no IPv4 Clients

This document is only designated for IPv4.  It is expected that
similar functionality is available dependencies in DHCPv6.

5.63 RFC 2590 Transmission of IPv6 Packets over Frame Relay
      Networks Specification

This this specification.

5.20 5.21 RFC documents IPv6 transmission method over Frame Relay and is
not discussed 1995 Incremental Zone Transfer in DNS

   Although the examples used in this document.

5.64-zzzz document use IPv4 addresses,
   (i.e., A records) there is nothing in the specification to preclude
   full and proper functionality using IPv6.

5.21 RFC 2601 ILMI-Based Server Discovery 1996 A Mechanism for ATMARP Prompt Notification of Zone Changes (DNS
     NOTIFY)

   There are no IPv4 dependencies within in this RFC.

5.65-zzzz specification.

5.22 RFC 2602 ILMI-Based Server Discovery 2003 IP Encapsulation within IP

   This document is designed for MARS use in IPv4 networks.  There are IPv4 dependencies within this RFC.

5.66-zzzz many
   references to a specified IP version number of 4 and 32-bit
   addresses.  This is incompatible with IPv6.

5.23 RFC 2603 ILMI-Based Server Discovery 2004 Minimal Encapsulation within IP

   This document is designed for NHRP use in IPv4 networks.  There are IPv4 dependencies within this RFC.

5.67 many
   references to a specified IP version number of 4 and 32-bit
   addresses.  This is incompatible with IPv6.

5.24 RFC 2610 DHCP Options 2005 Applicability Statement for Service Location Protocol IP Mobility Support

   This document specification documents the interoperation of IPv4 Mobility
   Support; this is only designated not relevant to this discussion.

5.25 RFC 2022 Support for IPv4.  It is expected that
similar functionality is available Multicast over UNI 3.0/3.1 based ATM Networks

   This specification specifically maps IPv4 multicast in DHCPv6.

5.68 UNI based ATM
   networks.  This is incompatible with IPv6.

5.26 RFC 2615 2043 The PPP over SONET/SDH SNA Control Protocol (SNACP)

   There are no IPv4 dependencies in this protocol.

5.69 specification.

5.27 RFC 2671 Extension Mechanisms for DNS (EDNS0) (EDNS0) 2097 The PPP NetBIOS Frames Control Protocol (NBFCP)

   There are no IPv4 dependencies in this protocol.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.70 RFC 2672 Non-Terminal DNS Name Redirection

This document is only defined for IPv4 addresses.  A similar
specification for IPv6 addresses should be defined.

5.71 specification.

5.28 RFC 2673 Binary Labels in the Domain Name System (DNS) 2113 IP Router Alert Option

   This document is only defined for IPv4 addresses.  A similar
specification provides a new mechanism for IPv6 addresses should be defined.

5.72 RFC 2675 IPv6 Jumbograms IPv4. This document defines a IPv6 packet format and is therefore not
discussed in this document.

5.73-zzzz RFC 2684 Multiprotocol Encapsulation over ATM Adaptation

There are IPv4 dependencies within this RFC.

5.74 incompatible
   with IPv6.

5.29 RFC 2686 2125 The PPP Bandwidth Allocation Protocol (BAP) / The Multi-Class Extension to Multi-Link PPP
     Bandwidth Allocation Control Protocol (BACP)

   There are no IPv4 dependencies in this protocol.

5.75 specification.

5.30 RFC 2687 PPP 2136 Dynamic Updates in a Real-time Oriented HDLC-like Framing the Domain Name System (DNS UPDATE)

   There are no IPv4 dependencies in this protocol.

5.76 specification.

5.31 RFC 2688 Integrated Services Mappings for Low Speed Networks 2181 Clarifications to the DNS Specification

   There are no IPv4 dependencies in this protocol.

5.77 RFC 2710 Multicast Listener Discovery (MLD) for IPv6
      (MLD-IPv6)

This document defines specification.  The only
   reference to IP addresses discuss the use of an anycast address, so
   but one can assume that these techniques are IPv6 specific protocol operable.

5.32 RFC 2225 Classical IP and is not discussed ARP over ATM

   From the many references in this document.

5.78 RFC 2711 IPv6 Router Alert Option

This document defines an IPv6 specific protocol and it is not discussed
in clear that this document.

 Internet Area: Survey of
   document is designed for IPv4 Addresses Currently Deployed  Mar. 2003

5.79 RFC 2728 The Transmission of IP Over only.  It is only later in the Vertical Blanking
      Interval document
   that it is implicitly stated, as in:

       ar$spln -  length in octets of a Television Signal

The following data format the source protocol address. Value
                  range is defined:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 or 4 5 6 7 8 9 (decimal).  For IPv4 ar$spln is 4.

       ar$tpln -  length in octets of the target protocol address. Value
                  range is 0 1 2 3 or 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |0|    group    |         uncompressed IP header (20 bytes)     |
    +-+-+-+-+-+-+-+-+                                               +
    |                                                               |
    :                             ....                              :
    +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               |        uncompressed UDP header (8 bytes)      |
    +-+-+-+-+-+-+-+-+                                               +
    |                                                               |
    +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |               |              payload  (<1472 bytes)           |
    +-+-+-+-+-+-+-+-+                                               +
    |                                                               |
    :                              ....                             :
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                              CRC                              |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

This protocol (decimal).  For IPv4 ar$tpln is 4.

   and:

     For backward compatibility with previous implementations, a null
     IPv4 dependent.  Updates protocol address may be received with length = 4 and an
     allocated address in storage set to the value 0.0.0.0.  Receiving
     stations must be made liberal in accepting this format of a null IPv4
     address.  However, on transmitting an ATMARP or InATMARP packet, a
     null IPv4 address must only be indicated by the length set to support
IPv6.

5.80 zero
     and must have no storage allocated.

5.33 RFC 2734 IPv4 2226 IP Broadcast over IEEE 1394 ATM Networks

   This protocol document is limited to IPv4 only.  A similar document must be defined for multicasting.  This is incompatible
   with IPv6.

5.81-zzzz

5.34 RFC 2735 NHRP Support 2241 DHCP Options for Virtual Private Networks

There are IPv4 dependencies within this RFC.

5.82 RFC 2765 Stateless IP/ICMP Translation Algorithm (SIIT)
      (SIIT) Novell Directory Services

   This protocol defines a method for IPv6 transition and is not
discussed in this document.

5.83 an extension to an IPv4-only specification.

5.35 RFC 2766 Network Address Translation - Protocol
      Translation (NAT-PT) (NAT-PT) 2242 NetWare/IP Domain Name and Information

   This protocol defines a method is an extension to an IPv4-only specification, for IPv6 transition example:

     PREFERRED_DSS (code 6)

         Length is (n * 4) and the value is not
discussed an array of n IP addresses,
         each four bytes in this document.

 Internet Area: Survey length. The maximum number of IPv4 Addresses Currently Deployed  Mar. 2003

5.84 RFC 2776 Multicast-Scope Zone Announcement Protocol (MZAP)
      (MZAP)

This protocol addresses is both IPv4 5
         and IPv6 aware therefore the maximum length value is 20. The list contains
         the addresses of n NetWare Domain SAP/RIP Server (DSS).

     NEAREST_NWIP_SERVER (code 7)

         Length is (n * 4) and needs no changes.

5.85 RFC 2782 A DNS RR for specifying the location value is an array of services
(DNS-SRV)

There are no IPv4 dependencies in this protocol.

5.86 RFC 2794 Mobile n IP Network Access Identifier Extension for
     IPv4

This document defines an IPv4 specific protocol addresses,
         each four bytes in length. The maximum number of addresses is 5
         and a similar
functionality must be defined for Mobile IPv6.

5.87 RFC 2834 ARP therefore the maximum length value is 20. The list contains
         the addresses of n Nearest NetWare/IP servers.

     PRIMARY_DSS (code 11)

         Length of 4, and the value is a single IP Broadcast over HIPPI-800 address.  This document uses the generic term "IP Address" in field

         identifies the text but
it also contains the text:

   The HARP message has several fields Primary Domain SAP/RIP Service server (DSS) for
         this NetWare/IP domain. NetWare/IP administration utility uses
         this value as Primary DSS server when configuring a secondary
         DSS server.

5.36 RFC 2290 Mobile-IPv4 Configuration Option for PPP IPCP

   This document is designed for use with Mobile IPv4.  There are
   numerous referrals to other IP "support" mechanisms (i.e. ICMP Router
   Discover Messages) that have specifically refer to the following format
   and values:

   Data sizes and field meaning:
     ar$hrd  16 bits  Hardware type
     ar$pro  16 bits  Protocol type IPv4 of the protocol fields below
     ar$op   16 bits  Operation code (request, reply, or NAK)
     ar$pln   8 bits  byte length ICMP.

5.37 RFC 2308 Negative Caching of each protocol address
     ar$rhl   8 bits  requester's HIPPI hardware address length (q)
     ar$thl   8 bits  target's HIPPI hardware address length (x)
     ar$rpa  32 bits  requester's protocol address
     ar$tpa  32 bits  target's protocol address
     ar$rha  qbytes   requester's HIPPI Hardware address
     ar$tha  xbytes   target's HIPPI Hardware address

   Where :
     ar$hrd  - SHALL contain 28. (HIPARP)

     ar$pro  - SHALL contain DNS Queries (DNS NCACHE)

   Although there are numerous examples in this document that use IPv4
   "A" records, there is nothing in the specification that limits its
   effectiveness to IPv4.

5.38 RFC 2331 ATM Signaling Support for IP protocol code 2048 (decimal).

     ar$op over ATM - SHALL contain the operational value (decimal):
               1  for   HARP_REQUESTs
               2  for   HARP_REPLYs
               8  for InHARP_REQUESTs
               9  for InHARP_REPLYs
               10 for   HARP_NAK
 Internet Area: Survey of UNI Signaling 4.0
     Update

   There are no IPv4 Addresses Currently Deployed  Mar. 2003

     ar$pln  - SHALL contain 4.

and later:

      31    28        23  21          15        10     7         2   0
      +-----+---------+-+-+-----------+---------+-----+---------+-----+
    0 |      04       |1|0|         000         |      03       |  0  |
      +---------------+-+-+---------------------+---------------+-----+
    1 |                              45                               |
      +-----+-+-------+-----------------------+-----------------------+
    2 |[LA] |W|MsgT= 0|          000          |   Dest. Switch Addr   |
      +-----+-+-------+-----------------------+-----------------------+ dependencies in this specification.

5.39 RFC 2332 NBMA Next Hop Resolution Protocol (NHRP)

   This document is very generic in its design and seems to be able to
   support numerous layer 3 |   2   |   2   |          000          |  Source Switch Addr   |
      +---------------+---------------+-------+-----------------------+
    4 |             00 00             |                               |
      +-------------------------------+                               |
    5 |                      Destination ULA                          |
      +-------------------------------+-------------------------------+
    6 |             [LA]              |                               |
      +-------------------------------+                               |
    7 |                         Source ULA                            |
      +===============+===============+===============+===============+
    8 |       AA      |      AA       |       03      |       00      |
      +---------------+---------------+---------------+---------------+
    9 |       00      |      00       |        Ethertype (2054)       |
      +---------------+---------------+-------------------------------+
   10 |              hrd (28)         |           pro (2048)          |
      +---------------+---------------+---------------+---------------+
   11 |             op (ar$op)        |     pln (6)   |   rhl (q)     |
      +---------------+---------------+---------------+---------------+
   12 |    thl = (x)  |   Requester IP Address upper  (24 bits)       |
      +---------------------------------------------------------------+
   13 | Req. IP lower |      Target IP Address upper  (24 bits)       |
      +---------------+-----------------------------------------------+
   14 | Tgt. IP lower | Requester HIPPI Hardware Address bytes 0 - 2  |
      +---------------+-----------------------------------------------+
   15 |         Requester HIPPI Hardware Address bytes addressing schemes and should include both
   IPv4 and IPv6.

5.40 RFC 2333 NHRP Protocol Applicability

   This document is very generic in its design and seems to be able to
   support numerous layer 3 - 6          |
      +-----------------------------------------------+---------------+
   16 |         Requester HW Address bytes 7 - q      | Tgt HW byte 0 |
      +---------------+---------------+---------------+---------------+
   17 |          Target  HIPPI Hardware Address bytes 1 - 4           |
      +---------------------------------------------------------------+
   18 |          Target  HIPPI Hardware Address bytes 5 - 8           |
      +---------------+---------------+---------------+---------------+
   19 |Tgt HW byte 9-x|     FILL      |     FILL      |     FILL      |
      +---------------+---------------+---------------+---------------+
                           HARP - InHARP Message
Which make addressing schemes and should include both
   IPv4 and IPv6.

5.41 RFC 2335 A Distributed NHRP Service Using SCSP

   There are no IPv4 dependencies in this specification.

5.42 RFC 2363 PPP Over FUNI

   There are no IPv4 dependencies in this specification.

5.43 RFC 2364 PPP Over AAL5

   There are no IPv4 dependencies in this specification.

5.44 RFC 2371 Transaction Internet Protocol Version 3.0 (TIPV3)

   This document states:

     TIP transaction manager addresses take the form:

        <hostport><path>

     The <hostport> component comprises:

        <host>[:<port>]

     where <host> is either a <dns name> or an <ip address>; and <port>
     is a decimal number specifying the port at which the transaction
     manager (or proxy) is listening for requests to establish TIP
     connections. If the port number is omitted, the standard TIP port
     number (3372) is used.

     A <dns name> is a standard name, acceptable to the domain name
     service. It must be sufficiently qualified to be useful to the
     receiver of the command.

     An <ip address> is an IP address, in the usual form: four decimal
     numbers separated by period characters.

   And further along it states:

     A TIP URL takes the form:

        tip://<transaction manager address>?<transaction string>

     where <transaction manager address> identifies the TIP transaction
     manager (as defined in Section 7 above); and <transaction string>
     specifies a transaction identifier, which may take one of two forms
     (standard or non-standard):

     i. "urn:" <NID> ":" <NSS>

       A standard transaction identifier, conforming to the proposed
       Internet Standard for Uniform Resource Names (URNs), as specified
       by RFC2141; where <NID> is the Namespace Identifier, and <NSS> is
       the Namespace Specific String. The Namespace ID determines the
       syntactic interpretation of the Namespace Specific String. The
       Namespace Specific String is a sequence of characters representin
       a transaction identifier (as defined by <NID>). The rules for the
       contents of these fields are specified by [6] (valid characters,
       encoding, etc.).

       This format of <transaction string> may be used to express global
       transaction identifiers in terms of standard representations.
       Examples for <NID> might be <iso> or <xopen>. e.g.

          tip://123.123.123.123/?urn:xopen:xid

       Note that Namespace Ids require registration. See [7] for details
       on how to do this.

     ii. <transaction identifier>

       A sequence of printable ASCII characters (octets with values in
       the range 32 through 126 inclusive (excluding ":") representing a
       transaction identifier. In this non-standard case, it is the
       combination of <transaction manager address> and <transaction
       identifier> which ensures global uniqueness. e.g.

          tip://123.123.123.123/?transid1

   These are incompatible with IPv6.

5.45 RFC 2464 Transmission of IPv6 Packets over Ethernet Networks

   This specification documents a method for transmitting IPv6 packets
   over Ethernet and is not considered in this discussion.

5.46 RFC 2467 Transmission of IPv6 Packets over FDDI Networks

   This specification documents a method for transmitting IPv6 packets
   over FDDI and is not considered in this discussion.

5.47 RFC 2470 Transmission of IPv6 Packets over Token Ring Networks

   This specification documents a method for transmitting IPv6 packets
   over Token Ring and is not considered in this discussion.

5.48 RFC 2472 IP Version 6 over PPP

   This specification documents a method for transmitting IPv6 packets
   over PPP and is not considered in this discussion.

5.49 RFC 2473 Generic Packet Tunneling in IPv6 Specification

   This specification documents an IPv6 aware specification and is not
   considered in this discussion.

5.50 RFC 2484 PPP LCP Internationalization Configuration Option

   There are no IPv4 dependencies in this specification.

5.51 RFC 2485 DHCP Option for The Open Group's User Authentication
     Protocol

   This is an extension to an IPv4-only specification.

5.52 RFC 2486 The Network Access Identifier

   There are no IPv4 dependencies in this specification.

5.53 RFC 2491 IPv6 over Non-Broadcast Multiple Access (NBMA) networks

   This specification documents a method for transmitting IPv6 packets
   over NBMA networks and is not considered in this discussion.

5.54 RFC 2492 IPv6 over ATM Networks

   This specification documents a method for transmitting IPv6 packets
   over ATM networks and is not considered in this discussion.

5.55 RFC 2497 Transmission of IPv6 Packets over ARCnet Networks

   This specification documents a method for transmitting IPv6 packets
   over ARCnet networks and is not considered in this discussion.

5.56 RFC 2507 IP Header Compression

   This specification is both IPv4 and IPv6 aware.

5.57 RFC 2526 Reserved IPv6 Subnet Anycast Addresses

   This specification documents IPv6 addressing and is not discussed in
   this document.

5.58 RFC 2529 Transmission of IPv6 over IPv4 Domains without Explicit
     Tunnels

   This specification documents IPv6 transmission methods and is not
   discussed in this protocol only document.

5.59 RFC 2563 DHCP Option to Disable Stateless Auto-Configuration in
     IPv4 aware.  An update Clients

   This is required an extension to
support IPv6.

 Internet Area: Survey an IPv4-only specification.

5.60 RFC 2590 Transmission of IPv6 Packets over Frame Relay Networks
     Specification

   This specification documents IPv6 transmission method over Frame
   Relay and is not discussed in this document.

5.61 RFC 2601 ILMI-Based Server Discovery for ATMARP

   This specification is both IPv4 Addresses Currently Deployed  Mar. 2003

5.88 and IPv6 aware.

5.62 RFC 2835 2602 ILMI-Based Server Discovery for MARS

   This specification is both IPv4 and IPv6 aware.

5.63 RFC 2603 ILMI-Based Server Discovery for NHRP

   This specification is both IPv4 and IPv6 aware.

5.64 RFC 2610 DHCP Options for Service Location Protocol

   This is an extension to an IPv4-only specification.

5.65 RFC 2615 PPP over SONET/SDH

   There are no IPv4 dependencies in this specification.

5.66 RFC 2625 IP and ARP over HIPPI-6400 (GSN) (GSN) Fibre Channel

   This document states:

     Objective and Scope:

      The Ethertype value SHALL be set as defined in Assigned Numbers [18]:

   IP           0x0800  2048  (16 bits)

This major objective of this specification is to promote
      interoperable implementations of IPv4 over FC. This specification
      describes a method for encapsulating IPv4 limited and as expected (after reviewing the previous
section) requires an update to support Address Resolution
      Protocol (ARP) packets over FC.

   This is incompatible with IPv6.

5.67 RFC 2671 Extension Mechanisms for DNS (EDNS0)

   There are numerous other
points no IPv4 dependencies in the documents that confirms this assumption.

5.89 specification.

5.68 RFC 2855 DHCP for IEEE 1394 2672 Non-Terminal DNS Name Redirection

   This document is only designated defined for IPv4.  It is expected that
similar functionality is available in DHCPv6.

5.90 RFC 2874 DNS Extensions to Support IPv4 addresses.  An IPv6 Address Aggregation
      and Renumbering
   specification may be needed.

5.69 RFC 2673 Binary Labels in the Domain Name System

   This document defines a protocol to interact with IPv6 and is not
considered in this document.

5.91 RFC 2893 Transition Mechanisms only defined for IPv4 addresses.  An IPv6 Hosts and Routers
      (TRANS-IPV6)
   specification may be needed.

5.70 RFC 2675 IPv6 Jumbograms

   This document defines a transition mechanism for IPv6 packet format and is therefore not
considered
   discussed in this document.

5.92

5.71 RFC 2915 The Naming Authority Pointer (NAPTR) DNS Resource
      Record (NAPTR) 2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5

   There are no IPv4 dependencies in this protocol.

5.93 specification.

5.72 RFC 2916 E.164 number and DNS 2685 Virtual Private Networks Identifier

   There are no IPv4 dependencies in this protocol.

5.94 specification.

5.73 RFC 2937 2686 The Name Service Search Option Multi-Class Extension to Multi-Link PPP

   There are no IPv4 dependencies in this specification.

5.74 RFC 2687 PPP in a Real-time Oriented HDLC-like Framing

   There are no IPv4 dependencies in this specification.

5.75 RFC 2688 Integrated Services Mappings for DHCP Low Speed Networks

   There are no IPv4 dependencies in this specification.

5.76 RFC 2710 Multicast Listener Discovery (MLD) for IPv6

   This document defines an IPv6 specific specification and is only designated for IPv4.  It is expected that
similar functionality is available not
   discussed in DHCPv6.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.95 this document.

5.77 RFC 3004 The User Class 2711 IPv6 Router Alert Option for DHCP

   This document defines an IPv6 specific specification and is only designated for IPv4.  It is expected that
similar functionality is available not
   discussed in DHCPv6.

5.96 this document.

5.78 RFC 3011 2728 The IPv4 Subnet Selection Option for DHCP Transmission of IP Over the Vertical Blanking Interval
     of a Television Signal

   The following data format is defined:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |0|    group    |         uncompressed IP header (20 bytes)     |
       +-+-+-+-+-+-+-+-+                                               +
       |                                                               |
       :                             ....                              :
       +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |               |        uncompressed UDP header (8 bytes)      |
       +-+-+-+-+-+-+-+-+                                               +
       |                                                               |
       +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |               |              payload  (<1472 bytes)           |
       +-+-+-+-+-+-+-+-+                                               +
       |                                                               |
       :                              ....                             :
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                              CRC                              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   This document is specifically designed for IPv4.

5.97 incompatible with IPv6.

5.79 RFC 3021 Using 31-Bit Prefixes on 2734 IPv4 Point-to-Point Links over IEEE 1394

   This document specification is IPv4 specific and a similar technique could also
be defined for IPv6.

5.98 only.

5.80 RFC 3024 Reverse Tunneling 2735 NHRP Support for Mobile IP, revised Virtual Private Networks

   This protocol assumes IPv4 addressing.  An updated Mobile IPv6 specification should include this functionality.

5.99 RFC 3046 DHCP Relay Agent Information Option

This document is implies only designated for IPv4.  It is expected IPv4 operations, but does not seem to
   present any reason that
similar functionality is available in DHCPv6.

5.100 it would not function for IPv6.

5.81 RFC 3056 Connection of IPv6 Domains via IPv4 Clouds 2765 Stateless IP/ICMP Translation Algorithm (SIIT)

   This is an specification defines a method for IPv6 related document transition and is not
   discussed in this document.

5.101

5.82 RFC 3068 An Anycast Prefix for 6to4 Relay Routers 2766 Network Address Translation - Protocol Translation
     (NAT-PT)

   This is an specification defines a method for IPv6 related document transition and is not
   discussed in this document.

5.102 RFC 3074 DHC Load Balancing Algorithm

There are no IPv4 dependencies in this protocol.

5.103 RFC 3077 A Link-Layer Tunneling Mechanism for Unidirectional
      Links

This protocol is both IPv4 and IPv6 aware and needs no changes.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

5.104

5.83 RFC 3115 Mobile IP Vendor/Organization-Specific Extensions 2776 Multicast-Scope Zone Announcement Protocol (MZAP)

   This specification is an enhancement for Mobile IPv4.  It is expected that a
similar capability will be in Mobile IPv6.

5.105 both IPv4 and IPv6 aware and needs no changes.

5.84 RFC 3145 L2TP Disconnect Cause Information 2782 A DNS RR for specifying the location of services

   There are no IPv4 dependencies in this protocol.

 Internet Area: Survey of specification.

5.85 RFC 2794 Mobile IP Network Access Identifier Extension for IPv4 Addresses Currently Deployed  Mar. 2003

6.0 Experimental RFCs

Experimental RFCs typically define protocols

   This is an extension to an IPv4-only specification.

5.86 RFC 2834 ARP and IP Broadcast over HIPPI-800

   This document uses the generic term "IP Address" in the text but it
   also contains the text:

     The HARP message has several fields 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 following format
     and values:

      Data sizes and field meaning:
        ar$hrd  16 bits  Hardware type
        ar$pro  16 bits  Protocol type of the Internet
community in order to allow potential interoperability protocol fields below
        ar$op   16 bits  Operation code (request, reply, or some other
potential useful scenario.  In a few cases they are presented as
alternatives to the mainstream solution to an acknowledged problem.

6.01 RFC 1183 New DNS RR Definitions (DNS-RR)

There are no IPv4 dependencies in this protocol.

6.02 RFC 1226 Internet NAK)
        ar$pln   8 bits  byte length of each protocol address
        ar$rhl   8 bits  requester's HIPPI hardware address length (q)
        ar$thl   8 bits  target's HIPPI hardware address length (x)
        ar$rpa  32 bits  requester's protocol address
        ar$tpa  32 bits  target's protocol address
        ar$rha  qbytes   requester's HIPPI Hardware address
        ar$tha  xbytes   target's HIPPI Hardware address

     Where :
        ar$hrd  - SHALL contain 28. (HIPARP)

        ar$pro  - SHALL contain the IP protocol encapsulation of AX.25 frames
      (IP-AX.25)

There are no IPv4 dependencies in this protocol.

6.03 RFC 1241 Scheme code 2048 (decimal).

        ar$op   - SHALL contain the operational value (decimal):
                  1  for an internet encapsulation protocol: Version   HARP_REQUESTs
                  2  for   HARP_REPLYs
                  8  for InHARP_REQUESTs
                  9  for InHARP_REPLYs
                  10 for   HARP_NAK
        ar$pln  - SHALL contain 4.

   And later:

       31    28        23  21          15        10     7         2   0
       +-----+---------+-+-+-----------+---------+-----+---------+-----+
     0 |      04       |1|0|         000         |      03       |  0  |
       +---------------+-+-+---------------------+---------------+-----+
     1 |                              45                               |
       +-----+-+-------+-----------------------+-----------------------+
     2 |[LA] |W|MsgT= 0|          000          |   Dest. Switch Addr   |
       +-----+-+-------+-----------------------+-----------------------+
     3 |   2   |   2   |          000          |  Source Switch Addr   |
       +---------------+---------------+-------+-----------------------+
     4 |             00 00             |                               |
       +-------------------------------+                               |
     5 |                      Destination ULA                          |
       +-------------------------------+-------------------------------+
     6 |             [LA]              |                               |
       +-------------------------------+                               |
     7 |                         Source ULA                            |
       +===============+===============+===============+===============+
     8 |       AA      |      AA       |       03      |       00      |
       +---------------+---------------+---------------+---------------+
     9 |       00      |      00       |        Ethertype (2054)       |
       +---------------+---------------+-------------------------------+
    10 |              hrd (28)         |           pro (2048)          |
       +---------------+---------------+---------------+---------------+
    11 |             op (ar$op)        |     pln (6)   |   rhl (q)     |
       +---------------+---------------+---------------+---------------+
    12 |    thl = (x)  |   Requester IP Address upper  (24 bits)       |
       +---------------------------------------------------------------+
    13 | Req. IP lower |      Target IP Address upper  (24 bits)       |
       +---------------+-----------------------------------------------+
    14 | Tgt. IP lower | Requester HIPPI Hardware Address bytes 0 - 2  |
       +---------------+-----------------------------------------------+
    15 |         Requester HIPPI Hardware Address bytes 3 - 6          |
       +-----------------------------------------------+---------------+
    16 |         Requester HW Address bytes 7 - q      | Tgt HW byte 0 |
       +---------------+---------------+---------------+---------------+
    17 |          Target  HIPPI Hardware Address bytes 1 (IN-ENCAP) - 4           |
       +---------------------------------------------------------------+
    18 |          Target  HIPPI Hardware Address bytes 5 - 8           |
       +---------------+---------------+---------------+---------------+
    19 |Tgt HW byte 9-x|     FILL      |     FILL      |     FILL      |
       +---------------+---------------+---------------+---------------+
                            HARP - InHARP Message

   This protocol specifies a protocol that assumes IPv4 but does not
actually have any limitations which would limit its operation in
an IPv6 environment.

6.04 is incompatible with IPv6.

5.87 RFC 1393 Traceroute Using an 2835 IP Option (TRACE-IP) and ARP over HIPPI-6400

   This document uses an IPv4 option.  It states:

     The Ethertype value SHALL be set as defined in Assigned Numbers
     [18]:

     IP           0x0800  2048  (16 bits)

   This is therefore limited to IPv4
networks.  A different technique must be developed for IPv4, and similar to the previous section,
   incompatible with IPv6.

6.05 RFC 1433 Directed ARP (DIR-ARP) There are no IPv4 dependencies numerous other points in this protocol.

6.06 RFC 1464 Using the Domain Name System To Store Arbitrary String
      Attributes

There are no IPv4 dependencies in
   documents that confirm this protocol.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

6.07 assumption.

5.88 RFC 1475 TP/IX: The Next Internet (TP-IX) 2855 DHCP for IEEE 1394

   This is an extension to an IPv4-only specification.

5.89 RFC 2874 DNS Extensions to Support IPv6 Address Aggregation and
     Renumbering
   This document defines IPv7 and has been abandoned by the IETF as a
feasible design.  It specification to interact with IPv6 and is
   not considered in this document.

6.08

5.90 RFC 1561 Use of ISO CLNP in TUBA Environments (CLNP-TUBA) 2893 Transition Mechanisms for IPv6 Hosts and Routers

   This document defines the use of NSAPA addressing a transition mechanism for IPv6 and does is not
use any version of IP, so there are no IPv4 dependencies
   considered in this
protocol.

6.09 document.

5.91 RFC 1712 DNS Encoding of Geographical Location (DNS-ENCODE) 2916 E.164 number and DNS

   There are no IPv4 dependencies in this protocol.

6.10 specification.

5.92 RFC 1735 NBMA Address Resolution Protocol (NARP) (NARP) 2937 The Name Service Search Option for DHCP

   This is an extension to an IPv4-only specification.

5.93 RFC 3004 The User Class Option for DHCP

   This document defines a protocol that is an extension to an IPv4-only specification.

5.94 RFC 3011 The IPv4 specific.  A new
version would need Subnet Selection Option for DHCP

   This is an extension to be documented an IPv4-only specification.

5.95 RFC 3021 Using 31-Bit Prefixes for IPv4 P2P Links

   This specification is specific to support IPv6.

4. Packet Formats

   NARP requests and replies are carried IPv4 address architecture, where a
   modification was needed to use both addresses of a 31-bit prefix.
   This is possible by IPv6 address architecture, but in IP packets as protocol type
   54. most cases not
   recommended; see RFC 3627, Use of /127 Prefix Length Between Routers
   Considered Harmful.

5.96 RFC 3024 Reverse Tunneling for Mobile IP, revised

   This section describes the packet formats is an extension to an IPv4-only specification.

5.97 RFC 3046 DHCP Relay Agent Information Option

   This is an extension to an IPv4-only specification.

5.98 RFC 3056 Connection of NARP requests and
   replies:

   NARP Request

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Version    |   Hop Count   |          Checksum             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |    Code       |           Unused              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Destination IP address                     |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                      Source IP address                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | NBMA length   |                NBMA address                   |
      +-+-+-+-+-+-+-+-+                                               |
      |                  (variable length)                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Source IPv6 Domains via IPv4 Clouds

   This is an IPv6 related document and Destination IP Addresses
     Respectively, these are the IP addresses of the NARP requestor is not discussed in this
   document.

5.99 RFC 3068 An Anycast Prefix for 6to4 Relay Routers

   This is an IPv6 related document and
     the target terminal is not discussed in this
   document.

5.100 RFC 3074 DHC Load Balancing Algorithm

   There are no IPv4 dependencies in this specification.

5.101 RFC 3077 A Link-Layer Tunneling Mechanism for which the NBMA address Unidirectional Links

   This specification is desired.

 Internet Area: Survey of both IPv4 Addresses Currently Deployed  Mar. 2003 and

   NARP Reply

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Version    |   Hop Count   |          Checksum             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |      Code     |           Unused              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Destination IP address                     |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                      Source IP address                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | NBMA length   |                NBMA address                   |
      +-+-+-+-+-+-+-+-+                                               |
      |                  (variable length)                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Source IPv6 aware and Destination needs no changes.

5.102 RFC 3115 Mobile IP Address
     Respectively, these Vendor/Organization-Specific Extensions

   This is an extension to an IPv4-only specification.

5.103 RFC 3145 L2TP Disconnect Cause Information

   There are the no IPv4 dependencies in this specification.

5.104 RFC 3344 IP addresses of the NARP requestor and
     the target terminal Mobility Support for which the NBMA address is desired.

6.11 IPv4

   There are IPv4 dependencies in this specification.

5.105 RFC 1768 Host 3376 Internet Group Extensions for CLNP Multicasting (CLNP-MULT)

This document defines an IPv9 multicast protocol and has been
abandoned by the IETF as a feasible design.  It Management Protocol, Version 3

   This document describes of version of IGMP used for IPv4 multicast.
   This is not considered compatible with IPv6.

5.106 RFC 3402 Dynamic Delegation Discovery System (DDDS) Part Two: The
      Algorithm

   There are no IPv4 dependencies in this document.

6.12 specification.

5.107 RFC 1788 ICMP 3403 Dynamic Delegation Discovery System (DDDS) Part Three:
      The Domain Name Messages (ICMP-DM)

This protocol is used for updates to the in-addr.arp reverse DNS
maps, and is limited to IPv4.

6.13 System (DNS) Database

   There are no IPv4 dependencies in this specification.

5.108 RFC 1797 Class A Subnet Experiment

This document is specific to IPv4.

6.14 3404 Dynamic Delegation Discovery System (DDDS) Part Four:
      The Uniform Resource Identifiers (URI)

   There are no IPv4 dependencies in this specification.

5.109 RFC 1819 Internet Stream Protocol Version 2 (ST2) Protocol
      Specification - 3513 IP Version ST2+ (ST2) 6 Addressing Architecture

   This protocol is IPv4 limited.  In fact it is the definition of
IPv5.  See below.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

   Both ST2 and IP apply the same specification documents IPv6 addressing schemes to identify
   different hosts. ST2 and IP packets differ in the first four bits,
   which contain the internetwork protocol version number: number 5 is
   reserved for ST2 (IP itself has version number 4). As a network
   layer protocol, like IP, ST2 operates independently of its
   underlying subnets. Existing implementations use ARP for address
   resolution, and use the same Layer 2 SAPs as IP.

8.2  Group Name Generator

   GroupName generation is similar to Stream ID generation. The
   GroupName includes a 16-bit unique identifier, a 32-bit creation
   timestamp, and a 32-bit IP address. Group names not discussed in
   this document.

5.110 RFC 3518 Point-to-Point Protocol (PPP) Bridging Control  Protocol
      (BCP)

   There are globally unique.
   A GroupName includes the creator's IP address, so no IPv4 dependencies in this reduces a
   global uniqueness problem to a simple local problem.

   IP-encapsulated ST packets begin with a normal IP header. Most
   fields of specification.

6. Experimental RFCs

   Experimental RFCs typically define protocols that do not have
   widescale implementation or usage on the IP header should be filled Internet.  They are often
   propriety in nature or used in according limited arenas.  They are documented
   to the same
   rules that apply to any other IP packet. Three fields of special
   interest are:

o   Protocol is 5, see [RFC1700], to indicate an ST packet is enclosed,
    as opposed Internet community in order to TCP allow potential
   interoperability or UDP, for example.

and

   The following permanent IP multicast addresses have been assigned to
   ST:

           224.0.0.7 All ST routers (intermediate agents)
           224.0.0.8 All ST hosts (agents) some other potential useful scenario.  In addition, a block of transient IP multicast addresses,
   224.1.0.0 -224.1.255.255, has been allocated for ST multicast
   groups. For instance, the following two functions could be made
   available:

   The ST Header also includes an ST Version Number, a total length
   field, a header checksum, a unique id, and the stream origin 32-bit
   IP address. The unique id and the stream origin 32-bit IP address
   form few
   cases they are presented as alternatives to the stream id (SID). This is shown in Figure 10. Please refer mainstream solution
   to Section 10.6 for an explanation of acknowledged problem.

6.1 RFC 1149 Standard for the notation.

 Internet Area: Survey transmission of IPv4 Addresses Currently Deployed  Mar. 2003

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  ST=5 | Ver=3 |D| Pri |   0   |            TotalBytes         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          HeaderChecksum       |            UniqueID           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                         OriginIPAddress                       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                            Figure 10: ST Header

o   ST is the IP Version Number assigned to identify ST packets. The
    value for ST is 5.

o   OriginIPAddress is datagrams on avian
    carriers

   There are no IPv4 dependencies in this specification.  In fact the second element
   flexibility of the SID. It this specification is the 32-bit
    IP address such that all versions of IP
   should function within its boundaries, presuming that the stream origin, see Section 8.1.

10.3.2  Group

   The Group parameter (PCode = 2) is packets
   remain small enough to be transmitted with the 256 milligrams weight
   limitations.

6.2 RFC 1183 New DNS RR Definitions

   There are no IPv4 dependencies in this specification.

6.3 RFC 1226 Internet protocol encapsulation of AX.25 frames

   There are no IPv4 dependencies in this specification.

6.4 RFC 1241 Scheme for an optional argument used to
   indicate that the stream is internet encapsulation protocol: Version 1

   This specification defines a member specification that assumes IPv4 but does
   not actually have any limitations which would limit its operation in the specified group.
   an IPv6 environment.

6.5 RFC 1307 Dynamically Switched Link Control Protocol

   This specification is IPv4 dependent, for example:

     3.1  Control Message Format

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  PCode = 2    |   PBytes = 16  Identifier                   |           GroupUniqueID   Total length                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                        GroupCreationTime                      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  Function                     |                     GroupInitiatorIPAddress   Event Status                |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |            Relationship       |                 N             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                         Figure 13: Group Parameter

o   GroupUniqueID, GroupInitiatorIPAddress, and GroupCreationTime
    together form the GroupName field. They are allocated by the group
    name generator function, see Section 8.2. GroupUniqueID and
    GroupCreationTime are implementation specific and have only local
    definitions.

10.3.3  MulticastAddress

   The MulticastAddress parameter (PCode = 3) is an optional parameter
   that is used when using IP encapsulation and setting up an IP
   multicast group. This parameter is used to communicate the desired
   IP multicast address to next-hop ST agents that should become
   members of the group, see Section 8.8.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0                Endpoint 1                                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  PCode = 3                Endpoint 2                                     |   PBytes = 8
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                0                       Message                                 |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                        IPMulticastAddress                       Body                                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                        Figure 15:  MulticastAddress

o   IPMulticastAddress is

      Endpoint addresses: 32 bits each

          The internet addresses of the 32-bit IP multicast address to be used
    to receive data packets two communicating parties for
          which the stream.

10.3.5  RecordRoute

   The RecordRoute parameter (PCode = 5) link is used being prepared.

6.6 RFC 1393 Traceroute Using an IP Option

   This document uses an IPv4 option.  It is therefore limited to request that the
   route between the origin and a target be recorded IPv4
   networks, and delivered to
   the user application. The ST agent at is incompatible with IPv6.

6.7 RFC 1433 Directed ARP

   There are no IPv4 dependencies in this specification.

6.8 RFC 1464 Using the origin (or target)
   including Domain Name System To Store Arbitrary String
    Attributes

   There are no IPv4 dependencies in this parameter, specification.

6.9 RFC 1475 TP/IX: The Next Internet

   This document defines IPv7 and has to determine the parameter's length,
   indicated been abandoned by the PBytes field. ST agents processing messages
   containing IETF as a
   feasible design.  It is not considered in this parameter add their receiving IP address document.

6.10 RFC 1561 Use of ISO CLNP in TUBA Environments

   This document defines the
   position indicated by the FreeOffset field, space permitting. If no
   space is available, the parameter is passed unchanged. When included
   by the origin, all agents between the origin and the target add
   their IP addresses use of NSAP addressing and does not use any
   version of IP, so there are no IPv4 dependencies in this information
   specification.

6.11 RFC 1712 DNS Encoding of Geographical Location

   There are no IPv4 dependencies in this specification.

6.12 RFC 1735 NBMA Address Resolution Protocol (NARP)

   This document defines a specification that is made available to the
   application at the target. When included by the target, all agents
   between the target IPv4 specific, for
   example:

    4. Packet Formats

    NARP requests and the origin, inclusive, add their replies are carried in IP addresses
   and this information is made available to the application at packets as protocol type
    54.  This section describes the
   origin. packet formats of NARP requests and
    replies:

    NARP Request

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   PCode = 5   |     PBytes    Version    |       0   Hop Count   |  FreeOffset          Checksum             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          IP Address 1     Type      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                              ...                              :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    Code       |                          IP Address N           Unused              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                           Figure 17: RecordRoute

o   PBytes is the length of the parameter in bytes. Length is
    determined by the agent (target or origin) that first introduces
    the parameter.  Once set, the length of the parameter remains
    unchanged.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

o   FreeOffset indicates the offset, relative to the start of the
    parameter, for the next IP address to be recorded. When the
    FreeOffset is greater than, or equal to, PBytes the RecordRoute
    parameter is full.

o
       |                    Destination IP Address is filled in, space permitting, by each ST agent
    processing this parameter.

10.3.6  Target address                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      Source IP address                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | NBMA length   |                NBMA address                   |
       +-+-+-+-+-+-+-+-+                                               |
       |                  (variable length)                            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Source and TargetList

   Several control messages use a parameter called TargetList (PCode =
   6), which contains information about the targets to which the
   message pertains. For each Target in the TargetList, the information
   includes Destination IP Addresses
        Respectively, these are the 32-bit IP address addresses of the target, the SAP applicable to
   the next higher layer protocol, NARP requestor
        and the length of the SAP
   (SAPBytes). Consequently, a Target structure can be of variable
   length. Each entry has target terminal for which the format shown in Figure 18. NBMA address is desired.

   And:

    NARP Reply

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                        Target    Version    |   Hop Count   |          Checksum             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |      Code     |           Unused              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                    Destination IP Address address                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      Source IP address                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  TargetBytes NBMA length   |  SAPBytes                NBMA address                   |     SAP       :    Padding
       +-+-+-+-+-+-+-+-+                                               |
       |                  (variable length)                            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                             Figure 18: Target

There

      Source and Destination IP Address
        Respectively, these are many other examples, but the IP addresses of the NARP requestor
        and the target terminal for which the NBMA address is desired.

   This is incompatible with IPv6.

6.13 RFC 1768 Host Group Extensions for CLNP Multicasting

   This specification defines multicasting for CLNP, which is not an IP
   protocol, and therefore has no IPv4 dependencies.

6.14 RFC 1788 ICMP Domain Name Messages

   This specification is used for updates to the in-addr.arpa reverse
   DNS maps, and is limited to IPv4.

6.15 RFC 1797 Class A Subnet Experiment

   This document is specific to IPv4 address architecture, and as such,
   has no IPv6 dependencies.

6.16 RFC 1819 Internet Stream Protocol Version 2 (ST2) Protocol
     Specification - Version ST2+

   This specification is IPv4 limited.  In fact it does is the definition of
   IPv5.  It has been abandoned by the IETF as feasible design, and is
   not serve any purpose to
include them all.

6.15 considered in this discussion.

6.17 RFC 1868 ARP Extension - UNARP (UNARP)

   This protocol specifies specification defines an extension to IPv4 ARP.  It is expected that ARP to delete entries
   from ARP caches on a similar
method should be implemented in IPv6.

6.16 link.

6.18 RFC 1876 A Means for Expressing Location Information in the Domain
     Name System (DNS-LOC)

   This document defines a methodology for applying this technology
   which is IPv4 dependent.  The protocol specification itself has no IPv4
   dependencies.

6.17

6.19 RFC 1888 OSI NSAPs and IPv6

   This is an IPv6 related document and is not discussed in this
   document.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

6.18

6.20 RFC 2009 GPS-Based Addressing and Routing (GPS-AR)

   The document states:

     The future version of IP (IP v6) will certainly have a sufficient
     number of bits in its addressing space to provide an address for
     even smaller GPS addressable units.  In this proposal, however, we
     assume the current version of IP (IP v4) and we make sure that we
     manage the addressing space more economically than that.  We will
     call the smallest GPS addressable unit a GPS-square.

6.19

   This specification does not seem to have real IPv4 dependencies.

6.21 RFC 2143 Encapsulating IP with the Small Computer System
      Interface (IP-SCSI) SCSI

   This protocol specification will only operate using IPv4.  As stated in the
   document:

     It was decided that the ten byte header offers the greatest
     flexibility for encapsulating version 4 IP datagrams for the
     following reasons:

6.20 [...]

   This is incompatible with IPv6.

6.22 RFC 2345 Domain Names and Company Name Retrieval

   There are no IPv4 dependencies in this protocol.

6.21-zzzz specification.

6.23 RFC 2443 A Distributed MARS Service Using SCSP (MARS-SCSP)

There are

   This document gives default values for use on IPv4 dependencies within this RFC.

6.22 networks, but is
   designed to be extensible so it will work with IPv6 with appropriate
   IANA definitions.

6.24 RFC 2471 IPv6 Testing Address Allocation

   This is an IPv6 related document and is not discussed in this
   document.

6.23

6.25 RFC 2481 A Proposal to add Explicit Congestion Notification
      (ECN) to IP (ECN-IP) 2520 NHRP with Mobile NHCs

   This protocol specification is both IPv4 and IPv6 aware and needs no changes.

6.24-zzzz RFC 2520 NHRP with Mobile NHCs

There are IPv4 dependencies within this RFC.

6.25

6.26 RFC 2521 ICMP Security Failures Messages (ICMP-SEC)

   There are no IPv4 dependencies in this protocol.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

6.26 specification.

6.27 RFC 2540 Detached Domain Name System (DNS) Information
      (DNS-INFO)

   There are no IPv4 dependencies in this protocol.

6.27 RFC 2770 GLOP Addressing in 233/8

This document is specific to IPv4. specification.

6.28 RFC 2823 PPP over Simple Data Link (SDL) using SONET/SDH with
     ATM-like framing (PPP-SDL)

   There are no IPv4 dependencies in this protocol. specification.

6.29 RFC 3123 A DNS RR Type for Lists of Address Prefixes (APL RR)

   This protocol specification is both IPv4 and IPv6 aware and needs no changes.

 Internet Area: Survey

6.30 RFC 3168 The Addition of Explicit Congestion Notification  (ECN) to
     IP

   This specification is both IPv4 Addresses Currently Deployed  Mar. 2003

7.0 and IPv6 aware and needs no changes.

6.31 RFC 3180 GLOP Addressing in 233/8

   This document is specific to IPv4 multicast addressing.

7. Summary of the Results

   In the initial survey of RFCs 62 52 positives were identified out of a
   total of 159, 185, broken down as follows:

      Standards				 16				 17 of 18 24 or 88.89% 70.83%

      Draft Standards			  6 of 16 20 or 37.50% 30.00%

      Proposed Standards			 35		 22 of 98 110 or 35.71% 20.00%

      Experimental RFCs			  5			 7 of 27 31 or 18.52% 22.58%

   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.

7.1 Standards

7.1.01  STD3  Requirements for Internet Hosts (RFC 1122 )

7.1.1 RFC 1122 is essentially a requirements document for IPv4 hosts and a
similar document for IPv6 hosts should be written.

7.1.02 STD 5 791 Internet Protocol (RFC 791, 922, 792, & 1122)

   RFC 791 has been updated in the definition of IPv6 in RFC 2460.

7.1.2 RFC 922 has been included in the IPv6 Addressing Architecture, RFC
2373. 792 Internet Control Message Protocol

   RFC 792 has been updated in the definition of ICMPv6 in RFC 2463.

7.1.3 RFC 1122 891 DCN Networks

   DCN has long since been updated in the definition of Multicast Listener
Discovery in ceased to be used, so this specification is
   no longer relevant.

7.1.4 RFC 2710.

7.1.03 STD 13 Domain Name System (RFCs 1034 & 1035)

New resource records for IPv6 addresses have been defined (AAAA & A6).

7.1.04 STD 41 894 IP over Ethernet (RFC 894)

   This problem has been fixed by RFC2464, A Method for the Transmission
   of IPv6 Packets over Ethernet Networks.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

7.1.05 STD 42

7.1.5 RFC 895 IP over Experimental experimental Ethernets (RFC 895)

See above section.

7.1.06 STD 43 IP over IEEE 8.02 (RFC 1042)

The functionality

   It is believed that experimental Ethernet networks are not being used
   anymore, so the specification is no longer relevant.

7.1.6 RFC 922 Broadcasting Internet Datagrams in the Presence of this Subnets

   Broadcasting is not used in IPv6, but similar functionality has been
   included in RFC 3513, IPv6 Addressing Architecture.

7.1.7 RFC 950 Internet Standard Subnetting Procedure

   Broadcasting is not used in IPv6, but similar functionality has been
   included in subsequent standards RFC 3513, IPv6 Addressing Architecture.

7.1.8 RFC 1034 Domain Names: Concepts and Facilities

   The problems have been fixed by defining new resource records for
   IPv6 addresses.

7.1.9 RFC 1035 Domain Names: Implementation and Specification

   The problems have been fixed by defining new resource records for
   IPv6 addresses.

7.1.10 RFC 1042 IP over XXX.

7.1.07 STD 44 DCN Networks (RFC 891) IEEE 802

   This protocol is no longer used and an updated protocol should not be
created.

7.1.08 STD 45 problem has been fixed by RFC2470, Transmission of IPv6 Packets
   over Token Ring Networks.

7.1.11 RFC 1044 IP over HyperChannel (RFC 1044)

   No updated document exists for this protocol.  It this specification.  It is unclear
   whether one is needed.

7.1.12 RFC 1088 IP over NetBIOS

   No updated document exists for this specification.  It is unclear
   whether one is needed.

7.1.13 RFC 1112 Host Extensions for IP Multicast

   The IPv4-specific parts of RFC 1112 have been updated in RFC 2710,
   Multicast Listener Discovery for IPv6.

7.1.14 RFC 1122 Requirements for Internet Hosts

   RFC 1122 is unclear whether
one essentially a requirements document for IPv4 hosts.
   Similar work is needed.  An updated protocol MAY be created.

7.1.09 STD 46 in progress
   (draft-ietf-ipv6-node-requirements-xx.txt).

7.1.15 RFC 1201 IP over Arcnet (RFC 1201) ARCNET

   This problem has been fixed by RFC 2497, A Method for the
   Transmission of IPv6 Packets over ARCnet Networks.

7.1.10 STD 48 IP over Netbios (RFC 1088)

A new protocol specification for tunneling IPv6 packets through
Netbios networks should be defined.

7.1.11 STD 52

7.1.16 RFC 1209 IP over SMDS (RFC 1209)

An

   No updated protocol document exists for the transmission this specification.  It is unclear
   whether one is needed.

7.1.17 RFC 1390 Transmission of IP and ARP over FDDI Networks

   This problem has been fixed by RFC 2467, "Transmission of IPv6 packets
   Packets over SMDS
must be written. FDDI Networks".

7.2 Draft Standards

7.2.1 Boot RFC 951 Bootstrap Protocol (RFC 951) (BOOTP)

   This problem has been fixed in the DHCPv6 and Auto Configuration
protocols of IPv6: by RFC 2462: 2462, IPv6 Stateless Address
   Autoconfiguration, and RFC3315, Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) currently an
Internet Draft.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003 (DHCPv6).

7.2.2 RFC 1191 Path MTU Discovery (RFC 1191)

   This problem has been fixed in RFC 1981, Path MTU Discovery for IP
   version 6.

7.2.3 RFC 1356 Multiprotocol Interconnect on X.25 and ISDN

   This problem can be fixed by defining a new NLPID for IPv6. Note that
   an NLPID has already been defined in RFC 2427, Multiprotocol
   Interconnect over Frame Relay.

7.2.4 RFC 1990 The PPP Multilink Protocol (RFC 1990) (MP)

   A new class identifier ("6") for IPv6 packets must be has been registered
   with the IANA.  It is RECOMMENDED that the (currently unassigned) value of
6 be assigned IANA by the IANA with a description of "Internet Protocol
(IPv6) Address."  An application for original author, fixing this assignment has been sent to
the IANA.

7.2.4 problem.

7.2.5 RFC 2067 IP over HIPPI (RFC 2067)

An

   No updated protocol document exists for the transmission of IPv6 packets over HIPPI MAY
be written.

7.2.5 DHCP (RFC 2131)

The problems are being fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues. this specification.  It is unclear
   whether one is needed.

7.2.6 RFC 2131 DHCP Options (RFC 2132)

The problems are being

   This problem has been fixed by in RFC 3315, Dynamic Host Configuration
   Protocol for IPv6 (DHCPv6).

   Further, the work consensus of the DHC WG.  Several very
advanced IDs address all DHC WG has been that the issues. options
   defined for DHCPv4 will not be automatically "carried forward" to
   DHCPv6.  Therefore, any further analysis of additionally specified
   DHCPv4 Options has been omitted from this memo.

7.3 Proposed Standards

7.3.01

7.3.1 RFC 1234 Tunneling IPX over IP (RFC 1234)

This problem remains unresolved and a new protocol specification
must

   No updated document exists for this specification.  In practice, the
   similar effect can be created.

7.3.02 achieved by the use of a layer 2 tunneling
   protocol. It is unclear whether an updated document is needed.

7.3.2 RFC 1256 ICMP Router Discovery (RFC 1256)

   This problem has been resolved in RFC 2461, Neighbor Discovery for IP
   Version 6 (IPv6)
 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

7.3.03 (IPv6).

7.3.3 RFC 1277 Encoding Net Addresses to Support Operation Over Non OSI
      Lower Layers (RFC 1277)

This

   No updated document exists for this specification; the problem is unresolved, but it MAY might
   be resolved with by the creation of a new encoding scheme definition.

7.3.04 if necessary. It
   is unclear whether an update is needed.

7.3.4 RFC 1332 PPP Internet Protocol Control Protocol (RFC 1332) (IPCP)

   This problem has been resolved in RFC 2472, IP Version 6 over PPP.

7.3.05 IP Multicast over Token Ring (RFC 1469)

The functionality of this specification has been essentially covered
in RFC 2470, IPv6 over Token Ring in section 8.

7.3.06  IP Mobility Support (RFC 2002)

The problems are being resolved by the Mobile IP WG and there is
a mature ID (draft-ietf-mobileip-ipv6-15.txt)

7.3.07  IP Encapsulation within IP (RFC 2003)

This functionality for Mobile IPv6 is accomplished using the Routing
Header as defined in RFC 2460, Internet Protocol, Version 6 (IPv6)
Specification.

7.3.08  Minimal Encapsulation within IP (RFC 2004)

See Section 7.3.27

7.3.09  Applicability Statement for IP Mobility Support (2005)

See Section 7.3.26

7.3.10  IP Router Alert Option (RFC 2113)

The problems identified are resolved in RFC 2711, IPv6 Router
Alert Option.

7.3.11  SLP (RFC 2165)

The problems have been addressed in RFC 3111, Service Location
Protocol Modifications for IPv6.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

7.3.12  Classical IP & ARP over ATM (RFC 2225)

The problems have been resolved in RFC 2492, IPv6 Version 6 over ATM
Networks.

7.3.13 PPP.

7.3.5 RFC 1469 IP Broadcast Multicast over ATM (RFC 2226) Token Ring

   The problems have functionality of this specification has been resolved essentially covered
   in RFC 2492, 2470, Transmission of IPv6 Packets over ATM Token Ring Networks.

7.3.14  IGMPv2 (RFC 2236)

The problems have been resolved in

7.3.6 RFC 2710, Multicast Listener
Discovery (MLD) for IPv6.

7.3.15  DHCP Options for NDS (RFC 2241)

The problems are being fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.16  Netware/IP Domain Name and Information (RFC 2242)

The problems are being 2003 IP Encapsulation within IP

   This problem has been fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.17  Mobile IPv4 Comfit Options defining different IP-in-IP
   encapsulation, for PPP IPCP (RFC 2290)

The problems are not being addressed and must be addressed example, RFC 2473, Generic Packet Tunneling in a new
protocol.

7.3.18  Transaction
   IPv6 Specification.

7.3.7 RFC 2004 Minimal Encapsulation within IP v3 (RFC 2371)

The problems identified are not addressed and a new standard MAY
be defined.

7.3.19  DHCP Option

   No updated document exists for Open Group User Authentication Protocol
        (RFC 2485)

The problems are being fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.20  DHCP this specification. It is unclear
   whether one is needed.

7.3.8 RFC 2022 Support for Multicast over UNI 3.0/3.1 based ATM Networks

   No updated document exists for this specification. It is unclear
   whether one is needed.

7.3.9 RFC 2113 IP Router Alert Option to Disable Stateless Autoconfiguration
        (RFC 2563)
 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

The problems are being

   This problem has been fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.21  Non-Terminal DNS Redirection (RFC 2672) in RFC 2711, IPv6 Router Alert Option.

7.3.10 RFC 2165 SLP

   The problems have not been addressed and a new specification MAY
be defined.

7.3.22  Binary Labels in DNS (RFC 2673) RFC 3111, Service Location
   Protocol Modifications for IPv6.

7.3.11 RFC 2225 Classical IP & ARP over ATM

   The problems have not been addressed and a new specification MAY
be defined.

7.3.23 resolved in RFC 2492, IPv6 over ATM Networks.

7.3.12 RFC 2226 IP Broadcast over Vertical Blanking Interval of a TV Signal (RFC 2728) ATM

   The problems have not been addressed and a new specification MAY
be defined.

7.3.24  IPv4 over IEEE 1394 (RFC 2734)

This problem is being addressed by the resolved in RFC 2492, IPv6 WG and an ID over ATM Networks.

7.3.13 RFC 2371 Transaction IPv3

   No updated document exists
(draft-ietf-ipngwg-ipngwg-1394-02.txt).

7.3.25  Mobile IP Network Access Identity Extensions for IPv4
        (RFC 2794)

The problems are not being addressed and must be addressed in a new
protocol.

7.3.26  ARP & this specification. It is unclear
   whether one is needed.

7.3.14 RFC 2625 IP Broadcasts Over HIPPI 800 (RFC 2834)

The problems are not being addressed and MAY be addressed in a new
protocol.

7.3.27 ARP & IP Broadcasts Over HIPPI 6400 (RFC 2835)

The problems are not being addressed and MAY be addressed over Fibre Channel

   There is work in a new
protocol.

7.3.28  DHCP progress to fix these problems
   (draft-desanti-ipv6-over-fibre-channel-02.txt).

7.3.15 RFC 2672 Non-Terminal DNS Redirection

   No updated document exists for IEEE 1394 (RFC 2855)

This problem this specification. It is being dually addressed by the IPv6 and DHC WGs and IDs unclear
   whether one is needed.

7.3.16 RFC 2673 Binary Labels in DNS

   No updated document exists that address for this issue.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

7.3.29  DHCP Name Server Search Option (RFC 2937)

The problem specification. It is being fixed by the work unclear
   whether one is needed.

7.3.17 IP over Vertical Blanking Interval of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.30  DHCP User Class Option a TV Signal (RFC 3004)

The problem 2728)

   No updated document exists for this specification. It is being fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.31 unclear
   whether one is needed.

7.3.18 RFC 2734 IPv4 Subnet Selection DHCP Option (RFC 3011)

The over IEEE 1394

   This problem is being has been fixed by the work RFC 3146, Transmission of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.32  Using 31-Bit Prefixes IPv6 Packets
   Over IEEE 1394 Networks.

7.3.19 RFC 2834 ARP & IP Broadcasts Over HIPPI 800

   No updated document exists for IPv4 P2P Links (RFC 3021) this specification. It is unclear
   whether one is needed.

7.3.20 RFC 2835 ARP & IP Broadcasts Over HIPPI 6400

   No action updated document exists for this specification. It is unclear
   whether one is needed.

7.3.33  Reverse Tunneling

7.3.21 RFC 3344 Mobility Support for Mobile IP (RFC 3024) IPv4

   The problems are not being addressed have been resolved by two upcoming RFCs, already waiting
   publication (draft-ietf-mobileip-ipv6-24.txt and must be addressed
   draft-ietf-mobileip-mipv6-ha-ipsec-06.txt).

   Since the first Mobile IPv4 specification in RFC 2002, a new
protocol.

7.3.34  DHCP Relay Agent Information Option (RFC 3046)

The number of
   extensions to it have been specified.  As all of these depend on on
   MIPv4, they have been omitted from further analysis in this memo.

7.3.22 RFC 3376 Internet Group Management Protocol, Version 3

   This problem is being fixed by the work of the DHC WG.  Several very
advanced IDs address all the issues.

7.3.35  Mobile IP Vender/Organization Specific Extensions (RFC 3115)

The problems are not being addressed and must be addressed in a new
protocol. MLDv2 specification
   (draft-vida-mld-v2-xx.txt).

7.4 Experimental RFCs

7.4.1 RFC 1393 Traceroute using an IP Option (RFC 1393)

   This protocol specification relies on IPv4 and a new protocol standard MAY be
produced.

 Internet Area: Survey the use of IPv4 Addresses Currently Deployed  Mar. 2003 an IPv4 option. No
   replacement document exists, and it is unclear whether one is needed.

7.4.2 RFC 1307 Dynamically Switched Link Control Protocol

   No updated document exists for this specification. It is unclear
   whether one is needed.

7.4.3 RFC 1735 NBMA ARP (RFC 1735) Address Resolution Protocol (NARP)

   This functionality has been defined in RFC 2491, IPv6 over
   Non-Broadcast Multiple Access (NBMA) networks and RFC 2332, NBMA Next
   Hop Resolution Protocol.

7.4.3  ST2+ Protocol (RFC 1819)

This protocol relies on IPv4 and a new protocol standard MAY be
produced. (NHRP).

7.4.4 RFC 1788 ICMP Domain Name Messages

   No updated document exists for this specification. However, DNS
   Dynamic Updates should provide similar functionality, so an update
   does not seem necessary.

7.4.5 RFC 1868 ARP Extensions (RFC 1868) Extension - UNARP

   This protocol relies mechanism defined a mechanism to purge ARP caches on IPv4 and a new protocol standard MAY be
produced.

7.4.5 link.
   That functionality already exists in RFC 2461, Neighbor Discovery for
   IPv6.

7.4.6 RFC 2143 IP Over SCSI (RFC 2143)

This protocol relies on IPv4

   No updated document exists for this specification. It is unclear
   whether one is needed.

7.4.7 RFC 3180 GLOP Addressing in 233/8

   Similar functionality is provided by RFC 3306, Unicast-Prefix-based
   IPv6 Multicast Addresses, and a new protocol standard MAY be
produced.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

8.0 no action is necessary.

8. Security Considerations

   This memo examines the IPv6-readiness of specifications; this does
   not have security considerations in itself.

9.0 References

9.1 Normative

[1] [Survey of IPv4 Addresses in Currently Deployed IETF Standards]
    Philip J. Nesser II, Andreas Bergstrom. "Introduction to the
    Survey ", draft-ietf-v6ops-ipv4survey-intro-01.txt
    IETF work in progress, June 2003

[2] [Survey of IPv4 Addresses in Currently Deployed IETF Standards]
    Philip J. Nesser II, Andreas Bergstrom: " IETF Sub-IP Area
    Standards ", draft-ietf-v6ops- ipv4survey-subip-01.txt,
    IETF work in progress. June 2003,

10.0

9. Acknowledgements

   The author would like to acknowledge the support of the Internet
   Society in the research and production of this document. Additionally
   the author would like to thanks his partner in all ways, Wendy M.
   Nesser.

   The editor, Cleveland Mickles, would like to thank Steve Bellovin and
   Russ Housley for their comments and Pekka Savola for his comments and
   guidance during the editing of this document.  Additionally the
editor he would
   like to thank, thank his wife, Lesia R. Mickles Lesia, for her patient support.

 Internet Area:

   Pekka Savola helped in editing the latest versions of the document.

Normative References

   [1]  II, P. and A. Bergstrom, "Introduction to the Survey of IPv4
        Addresses in Currently Deployed  Mar. 2003

11.0 Author's IETF  Standards",
        draft-ietf-v6ops-ipv4survey-intro-04 (work in progress), October
        2003.

Authors' Addresses

Please contact the authors with any questions, comments or suggestions
at:

   Cleveland Mickles  (Primary Editor)
America Online, Inc (owned by AOL Time Warner)
12100 Sunrise Valley Drive.          Phone:  +1 703-265-5618

   Reston, VA 20191,  20191
   USA                Email:  micklesc@aol.net

   EMail: cmickles.ee88@gtalumni.org

   Philip J. Nesser II (Author)
Principal
   Nesser & Nesser Consulting
   13501 100th Ave NE, #5202		Phone:  +1 425 481 4303
   Kirkland, WA  98034			Email:
   USA

   EMail: phil@nesser.com
Fax:    +1 425 48

12.0

Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   intellectual property 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; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication 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 implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.

 Internet Area: Survey of IPv4 Addresses Currently Deployed  Mar. 2003

13.0

Full Copyright Statement

   Copyright (C) The Internet Society (2000). (2003). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of develop-
   ing
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The lim-
   ited limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns. assignees.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DIS-
   CLAIMS DISCLAIMS 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.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.