[rfc-dist] RFC 3795 on Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Jun 9 17:33:55 PDT 2004


A new Request for Comments is now available in online RFC libraries.


        RFC 3795

        Title:      Survey of IPv4 Addresses in Currently Deployed
                    IETF Application Area Standards Track and
                    Experimental Documents
        Author(s):  R. Sofia, P. Nesser, II
        Status:     Informational
        Date:       June 2004
        Mailbox:    rsofia at zmail.pt, phil at nesser.com
        Pages:      50
        Characters: 92584
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-v6ops-ipv4survey-apps-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3795.txt


This document describes IPv4 addressing dependencies in an attempt to
clarify the necessary steps in re-designing and re-implementing
specifications to become network address independent, or at least, to
dually support IPv4 and IPv6.  This transition requires several
interim steps, one of them being the evolution of current IPv4
dependent specifications to a format independent of the type of IP
addressing schema used.  Hence, it is hoped that specifications will
be re-designed and re-implemented to become network address
independent, or at least to dually support IPv4 and IPv6.

To achieve that step, it is necessary to survey and document all IPv4
dependencies experienced by current standards (Full, Draft, and
Proposed) as well as Experimental RFCs.  Hence, this document
describes IPv4 addressing dependencies that deployed IETF Application
Area documented Standards may experience.

This document is a product of the IPv6 Operations Working Group of the
IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list