RFC 4029 on Scenarios and Analysis for Introducing IPv6 into ISP Networks
rfc-editor@rfc-editor.org Sat, 19 March 2005 01:49 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03550; Fri, 18 Mar 2005 20:49:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCTAN-00063e-PT; Fri, 18 Mar 2005 20:54:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCSz9-000636-Ah; Fri, 18 Mar 2005 20:42:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DCSz7-000631-Dh for ietf-announce@megatron.ietf.org; Fri, 18 Mar 2005 20:42:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01991 for <ietf-announce@ietf.org>; Fri, 18 Mar 2005 20:42:35 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DCT3e-0005Ri-Pc for ietf-announce@ietf.org; Fri, 18 Mar 2005 20:47:20 -0500
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 j2J1fgq24123; Fri, 18 Mar 2005 17:41:42 -0800 (PST)
Message-Id: <200503190141.j2J1fgq24123@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 18 Mar 2005 17:41:42 -0800
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: v6ops@ops.ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4029 on Scenarios and Analysis for Introducing IPv6 into ISP Networks
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-Score: -14.6 (--------------)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
A new Request for Comments is now available in online RFC libraries.
RFC 4029
Title: Scenarios and Analysis for Introducing IPv6 into
ISP Networks
Author(s): M. Lind, V. Ksinant, S. Park, A. Baudot, P. Savola
Status: Informational
Date: March 2005
Mailbox: mikael.lind@teliasonera.com,
vladimir.ksinant@fr.thalesgroup.com,
soohong.park@samsung.com,
alain.baudot@francetelecom.com, psavola@funet.fi
Pages: 28
Characters: 64388
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-v6ops-isp-scenarios-analysis-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4029.txt
This document describes different scenarios for the
introduction of IPv6 into an ISP's existing IPv4 network without
disrupting the IPv4 service. The scenarios for introducing IPv6
are analyzed, and the relevance of already defined transition
mechanisms are evaluated. Known challenges are also identified.
This document is a product of the IPv6 Operations Working Group of the
IETF.
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.
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