RFC 3795 on Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents

rfc-editor@rfc-editor.org Thu, 10 June 2004 13:57 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06546 for <ietf-announce-archive@ietf.org>; Thu, 10 Jun 2004 09:57:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYQ3h-0002oL-VB for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:57:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYPxB-00013a-00 for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:50:51 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BYPoS-0006Ys-00; Thu, 10 Jun 2004 09:41:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYOpv-0003Jh-OC; Thu, 10 Jun 2004 08:39:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYDa5-0003c7-62 for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 20:38:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06304 for <ietf-announce@ietf.org>; Wed, 9 Jun 2004 20:38:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYDa3-0002pl-Hz for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:38:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYDZ7-0001vf-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:37:10 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BYDYG-0000XF-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:36:16 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5A0XvJ18914; Wed, 9 Jun 2004 17:33:57 -0700 (PDT)
Message-Id: <200406100033.i5A0XvJ18914@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 09 Jun 2004 17:33:57 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Thu, 10 Jun 2004 08:38:44 -0400
Cc: v6ops@ops.ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 3795 on Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60

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@zmail.pt, phil@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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@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@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.
ftp://ftp.isi.edu/in-notes/rfc3795.txt"><ftp://ftp.isi.edu/in-notes/rfc3795.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce