Re: Connecting IPv6 Routing Domains Over the IPv4 Internet

"Jim Fleming" <JimFleming@prodigy.net> Tue, 26 June 2001 02:50 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id WAA05110 for ietf-outbound.10@ietf.org; Mon, 25 Jun 2001 22:50:03 -0400 (EDT)
Received: from pimout2-int.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA04742 for <ietf@ietf.org>; Mon, 25 Jun 2001 22:37:11 -0400 (EDT)
Received: from jim (ip-20-149-33.chicago-n.navipath.net [64.20.149.33]) by pimout2-int.prodigy.net (8.11.0/8.11.0) with SMTP id f5Q2blp135454; Mon, 25 Jun 2001 22:37:47 -0400
Message-ID: <010201c0fde8$c4225c00$d2931440@jim>
From: Jim Fleming <JimFleming@prodigy.net>
To: "Ole J. Jacobsen" <ole@cisco.com>
Cc: "ietf@ietf. org" <ietf@ietf.org>
References: <Pine.HPX.4.02.10106251932430.23766-100000@diablo.cisco.com>
Subject: Re: Connecting IPv6 Routing Domains Over the IPv4 Internet
Date: Mon, 25 Jun 2001 21:36:11 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Are these the references you mean ?

[0] Fink, R., "IPv6-What and Where It Is," The Internet Protocol Journal,
Volume 2, No. 1, March 1999.

[1] IPng and IPv6 information, including formal specifications, can be found
at: http://playground.sun.com/pub/ipng/html

[2] "The Case for IPv6," an Internet Draft of the IAB, can be found at:
http://www.6bone.net/misc/case-for-ipv6.html

[3] IETF IPv6 Transition Working Group (ngtrans) information, including
status of all its current projects, can be found at:
http://www.6bone.net/ngtrans/

[4] "Transition Mechanisms for IPv6 Hosts and Routers," RFC 1933, can be
found at: http://www.ietf.org/rfc/rfc1933.txt

[5] The 6bone IPv6 Testbed Network is explained at: http://www.6bone.net

[6] "Connection of IPv6 Domains via IPv4 Clouds without Explicit Tunnels"
("6to4"), an Internet Draft of the IETF ngtrans WG, can be found at:
http://www.6bone.net/misc/6to4.txt

[7] "IPv6 Aggregatable Global Unicast Address Format," RFC 2374, can be
found at: http://www.ietf.org/rfc/rfc2374.txt

[8] "Transmission of IPv6 Packets over IPv4 Domains without Explicit
Tunnels" ("6over4"), RFC 2529, can be found at:
http://www.ietf.org/rfc/rfc2529.txt

[9] "Neighbor Discovery for IP Version 6 (IPv6)," RFC 2461, can be found at:
http://www.ietf.org/rfc/rfc2461.txt

[10] IETF IPv6 Working Group (ipngwg) information, can be found at:
http://www.ietf.org/html.charters/ipngwgcharter.html


----- Original Message -----
From: "Ole J. Jacobsen" <ole@cisco.com>
To: "Jim Fleming" <JimFleming@prodigy.net>
Cc: "ietf@ietf. org" <ietf@ietf.org>
Sent: Monday, June 25, 2001 9:34 PM
Subject: Re: Connecting IPv6 Routing Domains Over the IPv4 Internet


> Yes it was. See the references at the end of the article you refer to. It
> clearly says that most of the documents were produced by the ngtrans
> working group of the IETF.
>
> Ole
>
>
>
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office of the CTO, Cisco Systems
> Tel: +1 408-527-8972
> GSM: +1 415-370-4628
> E-mail: ole@cisco.com
> URL: http://www.cisco.com/ipj
>
>
>
> On Mon, 25 Jun 2001, Jim Fleming wrote:
>
> > http://www.cisco.com/warp/public/759/ipj_3-1/ipj_3-1_routing.html
> > Connecting IPv6 Routing Domains Over the IPv4 Internet
> > by Brian E. Carpenter, IBM & iCAIR
> > Keith Moore, University of Tennessee
> > Bob Fink, Energy Sciences Network
> > -------------------------------------------
> >
> > Was this done "inside" the IETF ?
> >
> >
> > Jim Fleming
> > http://www.unir.com
> > Mars 128n 128e
> > http://www.unir.com/images/architech.gif
> > http://www.unir.com/images/address.gif
> > http://www.unir.com/images/headers.gif
> > http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
> > http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp
> > http://www.ietf.org/mail-archive/ietf/Current/msg12213.html
> > http://www.ietf.org/mail-archive/ietf/Current/msg12223.html
> >
> >
>