RFC 3791 on Survey of IPv4 Addresses in Currently Deployed IETF Routing Area Standards Track and Experimental Documents
rfc-editor@rfc-editor.org Thu, 10 June 2004 13:46 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 JAA04828 for <ietf-announce-archive@ietf.org>; Thu, 10 Jun 2004 09:46:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYPt9-0000Lh-6r for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:46:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYPj7-0005mf-00 for ietf-announce-archive@ietf.org; Thu, 10 Jun 2004 09:36:19 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BYPbv-0003rf-01; Thu, 10 Jun 2004 09:28:51 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BYPXP-0004D8-VD; Thu, 10 Jun 2004 09:24:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYOpn-0003Ik-9c; Thu, 10 Jun 2004 08:39:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BYDSM-00017j-O9 for ietf-announce@megatron.ietf.org; Wed, 09 Jun 2004 20:30:10 -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 UAA05827 for <ietf-announce@ietf.org>; Wed, 9 Jun 2004 20:30:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BYDSL-0004BY-46 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:30:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BYDRJ-0003Hc-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:29:06 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BYDQa-0002ML-00 for ietf-announce@ietf.org; Wed, 09 Jun 2004 20:28:21 -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 i5A0QnJ15282; Wed, 9 Jun 2004 17:26:49 -0700 (PDT)
Message-Id: <200406100026.i5A0QnJ15282@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:26:49 -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 3791 on Survey of IPv4 Addresses in Currently Deployed IETF Routing 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 3791
Title: Survey of IPv4 Addresses in Currently Deployed
IETF Routing Area Standards Track and Experimental
Documents
Author(s): C. Olvera, P. Nesser, II
Status: Informational
Date: June 2004
Mailbox: cesar.olvera@consulintel.es, phil@nesser.com
Pages: 15
Characters: 27567
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-v6ops-ipv4survey-routing-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3791.txt
This investigation work seeks to document all usage of IPv4 addresses
in currently deployed IETF Routing 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.
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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce