From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  2 10:28:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00855
	for <ngtrans-archive@odin.ietf.org>; Wed, 2 Aug 2000 10:28:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA13765;
	Wed, 2 Aug 2000 08:28:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA06517;
	Wed, 2 Aug 2000 07:26:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e72EPxR25760
	for ngtrans-dist; Wed, 2 Aug 2000 07:25:59 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e72EPq625753
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 07:25:52 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA12687
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 07:25:53 -0700 (PDT)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA02740
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 07:25:52 -0700 (PDT)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 55F90323; Wed,  2 Aug 2000 10:25:52 -0400 (EDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP id 45C231ED
	for <ngtrans@sunroof.eng.sun.com>; Wed,  2 Aug 2000 10:25:48 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id KAA0000927864; Wed, 2 Aug 2000 10:25:35 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008021425.KAA0000927864@anw.zk3.dec.com>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) DSTM Issue: DHCPv6 mail I sent 
Date: Wed, 02 Aug 2000 10:25:35 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Hi Folks,

I will point to this mail at the DSTM talk today.

regards,
/jim

------- Forwarded Message

Return-Path: owner-dhcp-v6@bucknell.edu
Received: from yquarry.zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id JAA0000006868; Wed, 2 Aug 2000 09:47:26 -0400 (EDT)
Received: from zmamail01.zma.compaq.com by yquarry.zk3.dec.com (8.8.8/1.1.22.3/11Mar00-0650AM)
	id JAA0000029637; Wed, 2 Aug 2000 09:47:26 -0400 (EDT)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 4401F3A12; Wed,  2 Aug 2000 09:46:56 -0400 (EDT)
Received: from mail.bucknell.edu (marge.bucknell.edu [134.82.9.1])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id 05BB6478B; Wed,  2 Aug 2000 09:46:51 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by mail.bucknell.edu (8.10.1/8.10.1) with SMTP id e72Dgdi20718;
	Wed, 2 Aug 2000 09:42:39 -0400 (EDT)
Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102])
	by mail.bucknell.edu (8.10.1/8.10.1) with ESMTP id e72DgOi08584
	for <dhcp-v6@bucknell.edu>; Wed, 2 Aug 2000 09:42:24 -0400 (EDT)
Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345)
	id 70CA9926; Wed,  2 Aug 2000 09:42:09 -0400 (EDT)
Received: from anw.zk3.dec.com (alpha.zk3.dec.com [16.140.128.4])
	by zmamail02.zma.compaq.com (Postfix) with ESMTP id 3FF4916F2
	for <dhcp-v6@bucknell.edu>; Wed,  2 Aug 2000 09:42:09 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id JAA0001465507; Wed, 2 Aug 2000 09:42:08 -0400 (EDT)
From: Jim Bound <bound@ZK3.DEC.COM>
Message-Id: <200008021342.JAA0001465507@anw.zk3.dec.com>
To: DHCPv6 discussion list <dhcp-v6@bucknell.edu>
Subject: Results in my mind of DHCPv6 Meeting
Date: Wed, 02 Aug 2000 09:42:08 -0400
X-Mts: smtp
Reply-To: dhcp-v6@bucknell.edu
Sender: owner-dhcp-v6@bucknell.edu
X-Listprocessor-Version: 8.2.10/991025/16:55 -- ListProc(tm) by CREN

Hi Folks,

Well this was an eye opening meeting.  This is my view of the key 
issues.  The authors also had another eye opening meeting with the
Chair and others after the dhc6 WG meeting.

#1 DHCPv6 is a market requirement and we need to get a WG cosensus
spec done quickly that can be implemented quickly.  At the meeting I
stated that we did not have to worry about catching the next train
to ship DHCPv6.  I WAS WRONG.  After speaking with several WG members
and listening, and connecting with several customer type IPv6 test
beds the WG needs to get this spec done A.S.A.P. and reach consensus.

#2 The WG does not have consensus that the more complicated parts
of DHCPv6 which are different than the DHCPv4 model is a good 
architecture idea.  It may be possible to reach consensus locating 
these parts (to be defined in other mail later) and take them
out of the initial draft for consensus to get an implementable spec
for the market A.S.A.P.

#3 Stream-line DHCPv6 or develop a competing proposal.  I think fine 
tuning the current spec working with members of the WG who have 
volunteered to help unofficially (to be worked and provided by
the Chair later) is the best approach to achieve dhcpv6 consensus
and get a spec all implementors will write code to is the optimal
approach to meet the IPv6 market needs.

#4 An integration of the DHCPv4 learnings within DHCPv6.  What we
have done here was not enough for some WG members and that was good
input.  Mike Carney had sent mail before the previous draft of
what we felt dhcpv4 did good and what dhcpv4 does the market would
like done better.  Then contrasted dhcpv6 with dhcpv4 and suggested
some resolution.  I think Mike should resend that mail and we can
expand or detract and use as input to the WG to begin that discussion
again.

The Chair is going to set up an interim WG meeting A.S.A.P.  My 
hope is we can address these key issues as a team and get the IPv6
market a spec we can all implement quickly and move onto standards
track and permit future extensibility we can work on together
to evolve dhcpv6.  My input to you is we need to make sure dhcpv6
can be extended from the core protocol I believe we can develop
quickly.

I will have a dhcpv6 state diagram for the WG in about 2 weeks
and will provide some IPv6 input to you all for the discussion.
THis is not now for the draft but for discussion with the WG.

regards,
/jim


------- End of Forwarded Message



From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  2 21:38:23 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09158
	for <ngtrans-archive@odin.ietf.org>; Wed, 2 Aug 2000 21:38:22 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA14051;
	Wed, 2 Aug 2000 19:37:50 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA10748;
	Wed, 2 Aug 2000 18:37:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e731aV626269
	for ngtrans-dist; Wed, 2 Aug 2000 18:36:31 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e731aO626262
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 18:36:25 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA28226
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 18:36:24 -0700 (PDT)
Received: from hotmail.com (f298.law7.hotmail.com [216.33.236.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id TAA13430
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 19:36:24 -0600 (MDT)
Received: (qmail 87861 invoked by uid 0); 3 Aug 2000 01:36:24 -0000
Message-ID: <20000803013624.87860.qmail@hotmail.com>
Received: from 147.73.128.245 by www.hotmail.com with HTTP;
	Wed, 02 Aug 2000 18:36:23 PDT
X-Originating-IP: [147.73.128.245]
From: "" <gtsirt@hotmail.com>
To: ngtrans@sunroof.eng.sun.com
Cc: george.tsirtsis@bt.com
Subject: (ngtrans) draft-soliman-siit-dstm-00.txt
Date: Wed, 02 Aug 2000 18:36:23 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "" <gtsirt@hotmail.com>

Hesham/Erik,

I was talking to Hesham Soliman today so I know the draft (as 99% of all 
drafts :-) was done last minute before the I-D dead line so some things like 
Security Consideration did not get done.
Anyway here are some comments from a first pass on the draft.

For your security section
DOS Attacks
The DELTA update mechanism introduces a DoS attack problem which is very 
similar to the one that NAT-PT has and I am sorry to say a bit worse, not 
much though:). I explain; When an IPv4 only node tries to communicate with 
your IPv6 only nodes, it sends a DNS query for that node and DSTM mechanisms 
are used to reserve and map an IPv4 address to the IPv6 address of that 
node. The mapped IPv4 address is then returned to the IPv4 only node and can 
be used to initiate communications.
According to your draft this mapping is then have to also be broadcasted to 
all the SIIT translators of the site so that wherever the incoming IPv4 
packets come from, the SIIT box on that path will be able to translate to 
the correct IPv6 address.
As in NAT-PT incoming connection, an attacker can just send DNS queries for 
different IPv6 only nodes, which will result in starving of the DSTM server 
from IPv4 addresses. The part that is worse than NAT-PT is that you also 
have to send this information to the SIIT servers, creating some signaling 
overheads on the networka and state on the servers which might be important 
if you have a large number of SIIT boxes. Of course you need to also timeout 
this state timely but  I guess this is implementation detail.

A more general comment
In this draft it seams the aim is to support mobile nodes with mobile IPv6 
only stack and mobile IPv6 support so, translation is used for IPv4 
communications, which is a bot of a shame...
I think that it should be possible to make a DualStack IPv4 and IPv6 node 
work using DSTM and Mobile IPv6 signaling, without need for translation. I 
will try to put in a draft some ideas I have on that as soon as I get a 
chance...

Good work
George

*
This is George not having access to his proper e-mail
*
George Tsirtsis
Internet Transport Research
Adastral Park
BT
Proper e-mail: george.tsirtsis@bt.com
*
Notice: This contribution is the personal view of the
author and does not necessarily reflect the technical nor
commercial direction of British Telecommunications plc.


________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com



From owner-ngtrans@sunroof.eng.sun.com  Mon Aug  7 13:00:54 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13130
	for <ngtrans-archive@odin.ietf.org>; Mon, 7 Aug 2000 13:00:53 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA05791;
	Mon, 7 Aug 2000 11:00:24 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA00704;
	Mon, 7 Aug 2000 09:59:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e77GwgL00295
	for ngtrans-dist; Mon, 7 Aug 2000 09:58:42 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e77Gwc600288
	for <ngtrans@sunroof.eng.sun.com>; Mon, 7 Aug 2000 09:58:38 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id JAA18202
	for ngtrans@sunroof.eng.sun.com; Mon, 7 Aug 2000 09:56:44 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e730tQ626247
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 17:55:26 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA22122
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 17:55:25 -0700 (PDT)
Received: from ouaf.tycool.net (ouaf.tycool.net [207.171.238.84])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA23158
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 18:55:23 -0600 (MDT)
Received: from rouget (ouaf.tycool.net [207.171.238.84])
	by ouaf.tycool.net (8.9.3+Sun/8.9.3) with SMTP id RAA05381
	for <ngtrans@sunroof.eng.sun.com>; Wed, 2 Aug 2000 17:53:41 -0700 (PDT)
Message-ID: <005c01bffce6$025a1940$a0844993@tycool.net>
From: "Alain Durand" <alain.durand@sun.com>
To: <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) Slides for IETF48
Date: Wed, 2 Aug 2000 17:58:58 -0700
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
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Alain Durand" <alain.durand@sun.com>
Content-Transfer-Encoding: 7bit

I would like to request all today's presenter who haven't done so yet
to sent the chaira a copy of their slides.

Thanks again for keeping your presentation within time limits so we could
have everybody on the agenda.

     - Alain.






From owner-ngtrans@sunroof.eng.sun.com  Mon Aug  7 14:32:54 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09506
	for <ngtrans-archive@odin.ietf.org>; Mon, 7 Aug 2000 14:32:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA19320;
	Mon, 7 Aug 2000 12:31:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA08601;
	Mon, 7 Aug 2000 11:25:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e77IOPs00578
	for ngtrans-dist; Mon, 7 Aug 2000 11:24:25 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e77IO9600560
	for <ngtrans@sunroof.eng.sun.com>; Mon, 7 Aug 2000 11:24:09 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA22763
	for <ngtrans@sunroof.eng.sun.com>; Mon, 7 Aug 2000 11:24:07 -0700 (PDT)
Received: from ziggy.stardust.com (ns.stardust.com [205.184.205.34])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA14792
	for <ngtrans@sunroof.eng.sun.com>; Mon, 7 Aug 2000 12:24:01 -0600 (MDT)
Received: from pleiades (dhcp204-96.stardust.com [205.184.204.96])
	by ziggy.stardust.com (8.9.3/8.9.3/Debian/GNU) with SMTP id LAA28068
	for <ngtrans@sunroof.eng.sun.com>; Mon, 7 Aug 2000 11:14:52 -0700
Message-Id: <3.0.5.32.20000807111454.0144fe90@stardust.com>
X-Sender: jasonu@stardust.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 07 Aug 2000 11:14:54 -0700
To: ngtrans@sunroof.eng.sun.com
From: Jason Utz <jasonu@stardust.com>
Subject: (ngtrans) Call for IPv6 papers - iBAND at ISPCON
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e77IOA600562
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jason Utz <jasonu@stardust.com>
Content-Transfer-Encoding: 8bit

Greetings!

IPv6 is one of the core technologies covered at the iBAND events. We would
like to continue its progress at the upcoming iBAND at ISPCON Conference on
November 8-10, 2000, in San Jose, CA. iBAND at ISPCON is a gathering place
for key industry people to come together and learn about developments in
the new Internet technologies:

* Service Provisioning * Traffic Management * Performance Measurement *

Your iBAND at ISPCON participation will help expose network engineers and
other technology savvy professionals to the latest and greatest in IPv6
technology.
 
My name is Jason Utz, conference manager for iBAND at ISPCON Conference.
Stardust.com's CTO Martin Hall and I would like to invite you to share you
progress and ideas with other relevant professionals in one or more ways:

· Speaker Proposal * BOF Proposal * Showcase Participation *

We value your expertise and look forward to receiving your speaker
proposals to reflect the state of the art in IPv6 technology. Proposals are
due no later than Friday, August 18, 2000. To find guidance and more
information, please visit 

http://www.stardust.com/iband5/speakers.htm

http://www.stardust.com for network engineers offers additional
opportunities to supply information and progress for IPv6 updates and
technologies:

- conference sessions available in MP3 format,
- live interviews on Stardust.com TalkRadio,
- provide white papers and have them maintained in a Stardust.com Web library.

All these options provide you with a large arena to deliver your working
group's information and other updates. Please visit http://www.stardust.com
to see what our site offers to its visitors.

We want to help you drive this technology area forward so please let me
know how you'd like to participate. Please contact me via email with any
questions.


Best regards,

Jason Utz
Conference Manager
Stardust.com
Jasonu@stardust.com
www.stardust.com

***************** Stardust.com*********************
	            Visit Stardust.com
	       http://www.stardust.com
	   Making sense of new Internet stuff
    Visit Stardust Talkradio Mondays in MP3 Format!
***************************************************
Home of the IP Multicast Initiative (IPMI)
the QoS Forum (QOSF) and the
Wireless Multimedia Forum (WMF) NEW!
***************************************************
UPCOMING EVENTS:
*iBAND at ISPCON - Nov. 8-10, 2000, San Jose, CA
*WISE, The Wireless Internet Services Event - Nov. 6-7, San Jose, CA
*****************************************************
Jason Utz          
Conference Manager

15575 Los Gatos Blvd Suite C        Fax  408/402-0567
Los Gatos, CA 95032 


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug  8 20:11:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17739
	for <ngtrans-archive@odin.ietf.org>; Tue, 8 Aug 2000 20:11:21 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA01179;
	Tue, 8 Aug 2000 18:11:07 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA24079;
	Tue, 8 Aug 2000 17:10:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7908wI02544
	for ngtrans-dist; Tue, 8 Aug 2000 17:08:58 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7908s602537
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 17:08:54 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id RAA19659
	for ngtrans@sunroof.eng.sun.com; Tue, 8 Aug 2000 17:06:59 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e78Np2602512
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 16:51:03 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA23366
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 16:51:03 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA18734
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 17:51:01 -0600 (MDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id QAA75460;
	Tue, 8 Aug 2000 16:51:00 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <39909CE4.BA19F36C@aciri.org>
Date: Tue, 08 Aug 2000 16:51:00 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
CC: vern@ee.lbl.gov
Subject: (ngtrans) another 6to4 question/comment
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit


Section 7 (ICMP messages) of the 6to4 document says that 6to4 routers
will "often" be unable to forward an IPv4 ICMP message as an ICMPv6
message because of a lack of data copied into the ICMP message.

Section 4.1.3 of RFC1933 says that "many" older IPv4 routers don't
return enough data, and that more modern IPv4 routers "may" return
enough data.

I was wondering how often "often" is and how many "many" is, so Vern did
a quick trace on a UCB internet access link (attached below) and found
that 93% of unreachables potentially returned by backbone routers (host,
net), and 99% of time exceeded messages carried the minimum amount of
data.

Maybe you all knew this already, but I was surprised.  Does this mean
that, for 6to4 especially, the IPv4 segment---which amounts to most of
the path early on---is undiagnosable from an IPv6 host?  Or are there
some neat tricks around this?  How much of a problem is this in fact?

PF



From owner-ngtrans@sunroof.eng.sun.com  Tue Aug  8 20:11:22 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17763
	for <ngtrans-archive@odin.ietf.org>; Tue, 8 Aug 2000 20:11:22 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA01180;
	Tue, 8 Aug 2000 18:11:07 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA10538;
	Tue, 8 Aug 2000 17:10:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7909YX02553
	for ngtrans-dist; Tue, 8 Aug 2000 17:09:34 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7909T602546
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 17:09:29 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id RAA19688
	for ngtrans@sunroof.eng.sun.com; Tue, 8 Aug 2000 17:07:34 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e78NwF602524
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 16:58:15 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA08183
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 16:58:14 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA09016
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Aug 2000 16:58:14 -0700 (PDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id QAA75506;
	Tue, 8 Aug 2000 16:58:13 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <39909E95.A1EB5840@aciri.org>
Date: Tue, 08 Aug 2000 16:58:13 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Subject: (ngtrans) oops, forgot to attach trace (another 6to4 question/comment)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit



PF

From Vern:
----------------------------------------------------------


I took an hour-long trace on one of the two UCB
Internet links.  It totalled
167,779 ICMPs (clearly, no smurf attacks!).  These
broke down as follows:

        54,430 echo request
        46,896 echo reply
        32,689 unreachable
                23,646 unreachable port (a wide
variety of ports)
                 5,434 unreachable host
                 3,390 administratively prohibited
                   108 unreachable net
                    55 prohibited access
                        (old flavor of admin
prohibited, I believe)
                    43 need fragmentation
                        (huh, not much useful MTU
discovery, eh?)
                    12 unreachable protocol
                     1 another flavor of
prohibited access
        29,428 time exceeded (about 75% of these
are Skitter)
         3,605 source quench (!)
           564 timestamp request
           136 timestamp reply
             8 redirect (!)

Of the unreachables potentially returned by
backbone routers (host, net),
93% returned just 8 bytes beyond the IP header
(assuming no IP options);
3% returned 58 bytes beyond; 1.25% returned 44
bytes beyond; 0.6% returned
528 bytes beyond; and the remaining 1.7% returned
sundry values around 40
bytes beyond (probably they could've returned a
bit more if the original
packet had been longer).

So, you can only rely on 8 bytes beyond the IP
header :-(.

                Vern



From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  9 08:43:14 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15907
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Aug 2000 08:43:10 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA03243;
	Wed, 9 Aug 2000 02:51:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA17193;
	Wed, 9 Aug 2000 01:51:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e798oOv03017
	for ngtrans-dist; Wed, 9 Aug 2000 01:50:24 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e798oH603010
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 01:50:18 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA17131
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 01:50:17 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA02605
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 02:50:15 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e798oB618180;
	Wed, 9 Aug 2000 10:50:11 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA08338;
	Wed, 9 Aug 2000 10:50:11 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id KAA17438;
	Wed, 9 Aug 2000 10:52:03 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008090852.KAA17438@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Paul Francis <francis@aciri.org>
cc: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Subject: Re: (ngtrans) another 6to4 question/comment 
In-reply-to: Your message of Tue, 08 Aug 2000 16:51:00 PDT.
             <39909CE4.BA19F36C@aciri.org> 
Date: Wed, 09 Aug 2000 10:52:03 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:
   
   I was wondering how often "often" is and how many "many" is, so Vern did
   a quick trace on a UCB internet access link (attached below) and found
   that 93% of unreachables potentially returned by backbone routers (host,
   net), and 99% of time exceeded messages carried the minimum amount of
   data.
   
=> 93% seems a very low number for me (:-)!

   Maybe you all knew this already, but I was surprised.

=> we knew. ICMP data (first bytes of the offending packet) is near
unusable but the real problem is most of the (misconfigured) firewalls
just drop all ICMPs on the floor, ie. if something goes wrong then
you'll get only a dark hole... This is a nightmare for infrastructures
using encapsulation like IPsec VPNs.

   Does this mean that, for 6to4 especially, the IPv4 segment---which
   amounts to most of the path early on---is undiagnosable from an IPv6
   host?

=> if you get ICMPs you can do something useful according to the type
of error. Typically you can keep some state and reflect it for next
packets in the same flow (the definition of flow depends on errors
and on the type of tunnels, configured tunnels are far better than 6to4
for this point).

   Or are there some neat tricks around this?

=> look at RFC 2473 for instance...

   How much of a problem is this in fact?
   
=> short ICMP data delay error signaling and fail with short flows but
the real problem is spurious ICMP filtering...

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  9 10:53:34 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06300
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Aug 2000 10:53:33 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA14763;
	Wed, 9 Aug 2000 08:08:53 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA05314;
	Wed, 9 Aug 2000 07:06:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e79E58M03249
	for ngtrans-dist; Wed, 9 Aug 2000 07:05:08 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e79E51603242
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 07:05:02 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA09400
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 07:05:01 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA09136
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 08:05:00 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA88612; Wed, 9 Aug 2000 15:00:43 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA23236; Wed, 9 Aug 2000 15:01:28 +0100 (BST)
Message-ID: <39916441.33CBA51C@hursley.ibm.com>
Date: Wed, 09 Aug 2000 09:01:37 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Paul Francis <francis@aciri.org>
CC: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Subject: Re: (ngtrans) another 6to4 question/comment
References: <39909CE4.BA19F36C@aciri.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Paul,

As far as I can see this issue affects all 6-in-4 tunnel solutions,
not just 6to4. And yes, I can imagine it being a problem for diagnosis
(essentially it means that diagnosis would need to be done from an IPv4
host, not from the IPv6 host).

But since IPv4 will be the carrier network for IPv6 for many years,
I think network operators will just have to deal with this. I would expect
network management systems to be dual stack and capable of diagnosing
the IPv4 path when a 6-in-4 tunnel fails.

Actually this must be an issue today for plenty of 4-in-4 tunnel
deployments of various flavours.

   Brian

Paul Francis wrote:
> 
> Section 7 (ICMP messages) of the 6to4 document says that 6to4 routers
> will "often" be unable to forward an IPv4 ICMP message as an ICMPv6
> message because of a lack of data copied into the ICMP message.
> 
> Section 4.1.3 of RFC1933 says that "many" older IPv4 routers don't
> return enough data, and that more modern IPv4 routers "may" return
> enough data.
> 
> I was wondering how often "often" is and how many "many" is, so Vern did
> a quick trace on a UCB internet access link (attached below) and found
> that 93% of unreachables potentially returned by backbone routers (host,
> net), and 99% of time exceeded messages carried the minimum amount of
> data.
> 
> Maybe you all knew this already, but I was surprised.  Does this mean
> that, for 6to4 especially, the IPv4 segment---which amounts to most of
> the path early on---is undiagnosable from an IPv6 host?  Or are there
> some neat tricks around this?  How much of a problem is this in fact?
> 
> PF


From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  9 10:57:24 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06966
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Aug 2000 10:57:23 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA26227;
	Wed, 9 Aug 2000 08:56:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA16143;
	Wed, 9 Aug 2000 07:55:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e79EsUQ03350
	for ngtrans-dist; Wed, 9 Aug 2000 07:54:30 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e79EsL603343
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 07:54:22 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA28740
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 07:54:21 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA22597
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 07:54:18 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id KAA27311;
        Wed, 9 Aug 2000 10:54:15 -0400 (EDT)
Message-Id: <200008091454.KAA27311@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Francis <francis@aciri.org>
cc: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Subject: Re: (ngtrans) another 6to4 question/comment 
In-reply-to: Your message of "Tue, 08 Aug 2000 16:51:00 PDT."
             <39909CE4.BA19F36C@aciri.org> 
X-SUBJECT-MSG-FROM: Paul Francis <francis@aciri.org> 
Date: Wed, 09 Aug 2000 10:54:14 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

I looked at this problem when we did the first draft of 6to4.
Basically I conculded that when 6to4 was incorporated into a 
host, that host might be able to make some use of an IPv4
ICMP message, (since the host already keeps track of connection
state and there might be only one connection from that host to 
any particular remote 6to4 address block) but it was unlikely 
that a 6to4 router would be able to return any reasonable kind 
of ICMPv6 message to a host behind it.    the router would 
presumably not want to keep track of per-connection state, and 
even if it did, the chances of multiple connections with the 
same destination would be increased.

so I would expect applications running over 6to4 to see 
"connection timed out" errors (after a delay)
where they might otherwise see "network unreachable" errors. 
and already-open connections would get wedged more often.

it would be really nice if we could come up with some sort
of hybrid 6/4 traceroute/pathchar utility.  but I suspect 
this will require explicit support from 6to4 routers,
at the very least.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  9 15:58:12 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18199
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Aug 2000 15:58:12 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA06883;
	Wed, 9 Aug 2000 13:57:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA01235;
	Wed, 9 Aug 2000 10:18:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e79HHtU03527
	for ngtrans-dist; Wed, 9 Aug 2000 10:17:55 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e79HHm603520
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 10:17:49 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA27678
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 10:17:47 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA23907
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 11:17:23 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id SAA50112; Wed, 9 Aug 2000 18:16:17 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id SAA19450; Wed, 9 Aug 2000 18:17:11 +0100 (BST)
Message-ID: <3991921B.6B2E8EFB@hursley.ibm.com>
Date: Wed, 09 Aug 2000 12:17:15 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Paul Francis <francis@aciri.org>
CC: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Subject: Re: (ngtrans) another 6to4 question/comment
References: <006f01c0021d$2ba7d3a0$03c4cc3f@pacbell.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

True enough. 6to4 is connectionless tunnelling I guess. 

  Brian

Paul Francis wrote:
> 
> >
> > As far as I can see this issue affects all 6-in-4 tunnel solutions,
> > not just 6to4. And yes, I can imagine it being a problem for diagnosis
> 
> Yes, but with configured tunnels (including v4-v4 tunnels, which I assume is
> what most v4-v4 tunnels are), the tunnel entry point maintains knowledge
> about the state of the tunnel, so you can get some diagnostics etc. out of
> it.  You can't do this with 6to4, which is why I was specifically refering
> to 6to4...
> 
> PF


From owner-ngtrans@sunroof.eng.sun.com  Wed Aug  9 17:18:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20759
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Aug 2000 17:18:20 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA02678;
	Wed, 9 Aug 2000 15:07:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA24398;
	Wed, 9 Aug 2000 11:36:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e79IZAG03652
	for ngtrans-dist; Wed, 9 Aug 2000 11:35:10 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e79IZ5603645
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 11:35:05 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA20132
	for ngtrans@sunroof.eng.sun.com; Wed, 9 Aug 2000 11:33:09 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e79GIk603473
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 09:18:46 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA01417
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 09:18:46 -0700 (PDT)
Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA05149
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Aug 2000 10:18:43 -0600 (MDT)
Received: from vaio ([63.204.196.3])
 by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FZ1000DO979BR@mta6.snfc21.pbi.net> for
 ngtrans@sunroof.eng.sun.com; Wed,  9 Aug 2000 09:16:21 -0700 (PDT)
Date: Wed, 09 Aug 2000 09:16:27 -0700
From: Paul Francis <francis@aciri.org>
Subject: RE: (ngtrans) another 6to4 question/comment
In-reply-to: <39916441.33CBA51C@hursley.ibm.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ngtrans@sunroof.eng.sun.com, vern@ee.lbl.gov
Message-id: <006f01c0021d$2ba7d3a0$03c4cc3f@pacbell.net>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Priority: 3 (Normal)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit

>
> As far as I can see this issue affects all 6-in-4 tunnel solutions,
> not just 6to4. And yes, I can imagine it being a problem for diagnosis

Yes, but with configured tunnels (including v4-v4 tunnels, which I assume is
what most v4-v4 tunnels are), the tunnel entry point maintains knowledge
about the state of the tunnel, so you can get some diagnostics etc. out of
it.  You can't do this with 6to4, which is why I was specifically refering
to 6to4...

PF




From owner-ngtrans@sunroof.eng.sun.com  Sat Aug 12 14:55:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04986
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Aug 2000 14:55:29 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA27204;
	Sat, 12 Aug 2000 12:55:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA25166;
	Sat, 12 Aug 2000 11:52:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7CIpVe06498
	for ngtrans-dist; Sat, 12 Aug 2000 11:51:31 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7CIpO606491
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 11:51:25 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA19984
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 11:51:24 -0700 (PDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA06597
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 11:51:23 -0700 (PDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13Mx9F-0006Mw-00
	for ngtrans@sunroof.eng.sun.com; Thu, 10 Aug 2000 11:33:45 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Message-Id: <E13Mx9F-0006Mw-00@rip.psg.com>
Date: Thu, 10 Aug 2000 11:33:45 -0700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

folk generally like the approach and the document.  but, on the iesg
telechat today, the following issues were raised in respect to
draft-ietf-ngtrans-6to4-06.txt:

  o the title is too similar to rfc2529 

  o there needs to be a clear statement that

    - this is a temporary transition mechanism

    - that it has serious scaling problems due to routing table explosion,
      and hence should have some sort time or size limit placed on its
      use, and maybe have a recommendation that it be blocked [by isps]
      by some size or date

  o if this is not meant as long-term technology, should it be ps?  maybe
    a note or an applicability statement would help.

randy


From owner-ngtrans@sunroof.eng.sun.com  Sat Aug 12 22:21:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09373
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Aug 2000 22:21:16 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA02822;
	Sat, 12 Aug 2000 20:21:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA05921;
	Sat, 12 Aug 2000 19:20:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7D2JVV06657
	for ngtrans-dist; Sat, 12 Aug 2000 19:19:31 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7D2JN606650
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:19:25 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA09158
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:19:23 -0700 (PDT)
Received: from jazz.viagenie.qc.ca (jazz.viagenie.qc.ca [206.123.31.2])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA23355
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:19:23 -0700 (PDT)
Received: from classic.viagenie.qc.ca (modemcable245.48-201-24.que.mc.videotron.net [24.201.48.245])
	by jazz.viagenie.qc.ca (Viagenie/8.11.0) with ESMTP id e7D2Knd99885;
	Sat, 12 Aug 2000 22:20:49 -0400 (EDT)
X-Accept-Language: fr,en,es
Message-Id: <4.3.2.7.2.20000812215109.0324df10@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 12 Aug 2000 22:02:33 -0400
To: Randy Bush <randy@psg.com>, ngtrans@sunroof.eng.sun.com
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
In-Reply-To: <E13Mx9F-0006Mw-00@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Content-Transfer-Encoding: 8bit

At/À 11:33 2000-08-10 -0700, Randy Bush you wrote/vous écriviez:
>folk generally like the approach and the document.  but, on the iesg
>telechat today, the following issues were raised in respect to
>draft-ietf-ngtrans-6to4-06.txt:
>
>   o the title is too similar to rfc2529
>
>   o there needs to be a clear statement that
>
>     - this is a temporary transition mechanism

to me, transition by definition is temporary, at least in the ipv4-to-ipv6 
context.
so a "temporary transition" looks bizarre to me.

ipv4 to ipv6 transition mechanisms are temporary. when everything is 
converted to ipv6, then no more transition tools/standard/mechanisms is needed.

The only problem is finding the timeframe. I'm not sure if someone really 
want to estimate that and put here somewhere in a RFC... ;-))


>     - that it has serious scaling problems due to routing table explosion,

right.

>       and hence should have some sort time or size limit placed on its
>       use, and maybe have a recommendation that it be blocked [by isps]
>       by some size or date

date seems to me very difficult to estimate.
size is probably much better, and also is clearly related to the routing 
table explosion problem.
Say for example that max size = 50K routing table (about half of the 
current routing table).
then what happen around the 50000th:
  + who is going to decide who has the "right" to use 6to4 and who hasn't
  + how can we really know the number of 6to4 routers, where some networks 
can be up and down.
  + if we want (I don't but not sure of any other way to resolve this) a 
registry to handle those issues, then we are back on square one: i.e. 6to4 
is easy. registry is more difficult, so we kill 6to4.


>   o if this is not meant as long-term technology,

as said: to me, no transition is going to be long-term.

>should it be ps?  maybe
>     a note or an applicability statement would help.

I think this is the only thing that can really be done in the RFC. size and 
date looks to me not really useful to define. An applicability statement 
saying that "this doesn't scale for the full internet and that other 
mechanisms must be deployed to replace 6to4 in the event of routing table 
explosion", seems to me the only real thing that we can add.

my 2 cents.

Marc.


>randy


Marc Blanchet
Viagénie inc.
tel: 418-656-9254
http://www.viagenie.qc.ca

----------------------------------------------------------
Normos (http://www.normos.org): Internet standards portal:
IETF RFC, drafts, IANA, W3C, ATMForum, ISO, ... all in one place.



From owner-ngtrans@sunroof.eng.sun.com  Sat Aug 12 22:39:22 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10473
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Aug 2000 22:39:22 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA06350;
	Sat, 12 Aug 2000 20:39:18 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA26799;
	Sat, 12 Aug 2000 19:39:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7D2bhT06684
	for ngtrans-dist; Sat, 12 Aug 2000 19:37:43 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7D2ba606677
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:37:37 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA09686
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:37:35 -0700 (PDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA26030
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Aug 2000 19:37:35 -0700 (PDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13NneT-000IKp-00; Sat, 12 Aug 2000 19:37:29 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <E13Mx9F-0006Mw-00@rip.psg.com>
	<4.3.2.7.2.20000812215109.0324df10@mail.viagenie.qc.ca>
Message-Id: <E13NneT-000IKp-00@rip.psg.com>
Date: Sat, 12 Aug 2000 19:37:29 -0700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

>>   o there needs to be a clear statement that
>>     - this is a temporary transition mechanism
> to me, transition by definition is temporary, at least in the ipv4-to-ipv6
> context.  so a "temporary transition" looks bizarre to me.
> ipv4 to ipv6 transition mechanisms are temporary. when everything is
> converted to ipv6, then no more transition tools/standard/mechanisms is
> needed.
> The only problem is finding the timeframe. I'm not sure if someone really 
> want to estimate that and put here somewhere in a RFC... ;-))

well, do tell us when you work it all out.

>>     - that it has serious scaling problems due to routing table explosion,
> right.
>>       and hence should have some sort time or size limit placed on its
>>       use, and maybe have a recommendation that it be blocked [by isps]
>>       by some size or date
> date seems to me very difficult to estimate.
> size is probably much better, and also is clearly related to the routing 
> table explosion problem.
> Say for example that max size = 50K routing table (about half of the 
> current routing table).
> then what happen around the 50000th:
>   + who is going to decide who has the "right" to use 6to4 and who hasn't
>   + how can we really know the number of 6to4 routers, where some networks 
> can be up and down.
>   + if we want (I don't but not sure of any other way to resolve this) a
> registry to handle those issues, then we are back on square one: i.e. 6to4
> is easy. registry is more difficult, so we kill 6to4.

does this tell us anything about whether this scheme should be recommended
for deployment or how it should be deployed?

but i suspect that folk are going to want a serious answer to this issue.
recommending deployment of things with unscoped scaling problems is losing
popularity.

> An applicability statement saying that "this doesn't scale for the full
> internet and that other mechanisms must be deployed to replace 6to4 in the
> event of routing table explosion", seems to me the only real thing that we
> can add.

if we intend this to be a proposed standard, it might help if we were more
specific about what the scaling issues are, how they can be anticipated, and
what might be done to ameliorate, bypass, or replace them.

randy


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 10:38:32 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10033
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 10:38:31 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA23407;
	Mon, 14 Aug 2000 08:38:18 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA09989;
	Mon, 14 Aug 2000 07:36:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EEZd307433
	for ngtrans-dist; Mon, 14 Aug 2000 07:35:39 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EEZV607426
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 07:35:32 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA09854
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 07:35:31 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA21329
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 08:35:30 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7EEYk631285;
	Mon, 14 Aug 2000 16:34:46 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id QAA18938;
	Mon, 14 Aug 2000 16:34:46 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id QAA42855;
	Mon, 14 Aug 2000 16:37:06 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008141437.QAA42855@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Randy Bush <randy@psg.com>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Thu, 10 Aug 2000 11:33:45 PDT.
             <E13Mx9F-0006Mw-00@rip.psg.com> 
Date: Mon, 14 Aug 2000 16:37:06 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

     o if this is not meant as long-term technology, should it be ps?  maybe
       a note or an applicability statement would help.
   
=> I'd like to get an applicability statement too. Obviously
6to4 (as other transition mechanisms) has a narrow applicability space,
for instance it is not useful for ISPs (they'd prefer configured (ie.
managed) tunnels) nor home users (because of the dynamic IPv4 address).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 11:50:52 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12814
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 11:50:52 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA17052;
	Mon, 14 Aug 2000 09:48:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA10604;
	Mon, 14 Aug 2000 08:19:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EFIJM07495
	for ngtrans-dist; Mon, 14 Aug 2000 08:18:19 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EFIA607484
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 08:18:12 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA16179
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 08:18:11 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA21946
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 08:18:09 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id QAA132072; Mon, 14 Aug 2000 16:16:55 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA25330; Mon, 14 Aug 2000 16:17:54 +0100 (BST)
Message-ID: <39980DAB.2B016564@hursley.ibm.com>
Date: Mon, 14 Aug 2000 10:18:03 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <E13Mx9F-0006Mw-00@rip.psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Randy,

Randy Bush wrote:
> 
> folk generally like the approach and the document.  but, on the iesg
> telechat today, the following issues were raised in respect to
> draft-ietf-ngtrans-6to4-06.txt:
> 
>   o the title is too similar to rfc2529

Not surprising really, for various reasons such as it is
a very similar idea (i.e. treat IPv4 as the link layer).
Is this a definite request for a cosmetic change? What change
would be acceptable?

> 
>   o there needs to be a clear statement that
> 
>     - this is a temporary transition mechanism

As others have said, it's a transition mechanism. It seems entirely
redundant to say that it's temporary, but I can do it if it makes
someone happy.

> 
>     - that it has serious scaling problems due to routing table explosion,
>       and hence should have some sort time or size limit placed on its
>       use, ...

The scaling issue is supposed to be covered by the rules about advertizing
the 2002:: prefix, specifically section 5.2.2:

>    On its native IPv6 interface, the relay router MUST advertise a route
>    to 2002::/16. It MUST NOT advertise a longer 2002:: routing prefix on
>    that interface. Routing policy within the native IPv6 routing domain
>    determines the scope of that advertisement, thereby limiting the
>    visibility of the relay router in that domain.

I'd like to understand why this leaves any scaling concerns, since it specifically
limits the number of IPv6 routing table entries to one.

>       ...and maybe have a recommendation that it be blocked [by isps]
>       by some size or date

I don't think it's the IETF's business to make such a recommendation, in fact
it would be unconscionable to do so and impossible to suggest a date.

>   o if this is not meant as long-term technology, should it be ps?  maybe
>     a note or an applicability statement would help.

Yes, as the other transition techniques are PS. I can't see why a separate
applicability statement would help, but if somebody will make specific
suggestions we can add text in the introduction.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 12:57:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14721
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 12:57:29 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA18704;
	Mon, 14 Aug 2000 10:57:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA08895;
	Mon, 14 Aug 2000 09:56:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EGtZx07691
	for ngtrans-dist; Mon, 14 Aug 2000 09:55:35 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EGtS607684
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 09:55:28 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA18694
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 09:55:27 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA17245
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 10:55:26 -0600 (MDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2172.1);
	 Mon, 14 Aug 2000 09:54:53 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 14 Aug 2000 09:55:21 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Mon, 14 Aug 2000 09:55:20 -0700
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C00610.506DF240"
Subject: RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Mon, 14 Aug 2000 09:54:30 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A5690D8CF0A5@SIT.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
Thread-Index: AcAF/SbATTo1Iq4cTV2/Uv5UM5rBogAEuqNA
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 14 Aug 2000 16:55:20.0530 (UTC) FILETIME=[6E3FEB20:01C00610]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C00610.506DF240
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Francis Dupont writes:
> Obviously
> 6to4 (as other transition mechanisms) has a narrow applicability
space,
> for instance it is not useful for ISPs (they'd prefer configured (ie.
> managed) tunnels) nor home users (because of the dynamic IPv4
address).

I'm a home user with a dynamic IPv4 address, and it works just fine
for me.  I'd say it's far more useful for home users than configured
tunnels is, since 6to4 can deal with dynamic IPv4 addresses much better
than configured tunnels.

-Dave

------_=_NextPart_001_01C00610.506DF240
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Francis Dupont writes:</FONT>

<BR><FONT SIZE=3D2>&gt; Obviously</FONT>

<BR><FONT SIZE=3D2>&gt; 6to4 (as other transition mechanisms) has a =
narrow applicability space,</FONT>

<BR><FONT SIZE=3D2>&gt; for instance it is not useful for ISPs (they'd =
prefer configured (ie.</FONT>

<BR><FONT SIZE=3D2>&gt; managed) tunnels) nor home users (because of the =
dynamic IPv4 address).</FONT>
</P>

<P><FONT SIZE=3D2>I'm a home user with a dynamic IPv4 address, and it =
works just fine</FONT>

<BR><FONT SIZE=3D2>for me.&nbsp; I'd say it's far more useful for home =
users than configured</FONT>

<BR><FONT SIZE=3D2>tunnels is, since 6to4 can deal with dynamic IPv4 =
addresses much better</FONT>

<BR><FONT SIZE=3D2>than configured tunnels.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C00610.506DF240--


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 13:57:20 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16093
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 13:57:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA08167;
	Mon, 14 Aug 2000 11:56:10 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA06068;
	Mon, 14 Aug 2000 10:52:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EHpe207859
	for ngtrans-dist; Mon, 14 Aug 2000 10:51:40 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EHpX607852
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 10:51:34 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA25068
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 10:51:32 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA05761
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 10:51:29 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7EHpO642316;
	Mon, 14 Aug 2000 19:51:24 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id TAA20253;
	Mon, 14 Aug 2000 19:51:23 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id TAA43632;
	Mon, 14 Aug 2000 19:53:46 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008141753.TAA43632@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
cc: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Mon, 14 Aug 2000 09:54:30 PDT.
             <19398D273324D3118A2B0008C7E9A5690D8CF0A5@SIT.platinum.corp.microsoft.com> 
Date: Mon, 14 Aug 2000 19:53:46 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   > home users (because of the dynamic IPv4 address).
   
   I'm a home user with a dynamic IPv4 address, and it works just fine
   for me.

=> is your 6to4 prefix changing with your dynamic IPv4 address?
I think most users would like to get a *static* IPv6 prefix...

   I'd say it's far more useful for home users than configured
   tunnels is, since 6to4 can deal with dynamic IPv4 addresses much better
   than configured tunnels.
   
=> but is it much better than configured tunnels + my draft
(draft-ietf-ngtrans-hometun-00.txt)?

Francis.Dupont@enst-bretagne.fr

PS: I really need to implement my draft in order to have a tunnel
broker with support somewhere. I have a free FreeBSD 4.1 here,
is this good for tunnel broker people?


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 15:26:31 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17584
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 15:26:31 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA24599;
	Mon, 14 Aug 2000 13:25:30 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA20762;
	Mon, 14 Aug 2000 12:24:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EJNVU07979
	for ngtrans-dist; Mon, 14 Aug 2000 12:23:31 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EJNO607972
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 12:23:25 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA15083
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 12:23:22 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA23106
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 13:23:22 -0600 (MDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2172.1);
	 Mon, 14 Aug 2000 12:20:36 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 14 Aug 2000 12:21:03 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Mon, 14 Aug 2000 12:20:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C00619.1FFB2278"
Subject: RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
Date: Mon, 14 Aug 2000 10:57:34 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A5690D8CF0A9@SIT.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
Thread-Index: AcAGGCtzzDHLpeJ5Rai4Bi/JCltQhgAAPDvg
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 14 Aug 2000 19:20:15.0505 (UTC) FILETIME=[ACDBD010:01C00624]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C00619.1FFB2278
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Francis Dupont writes:
>  In your previous mail you wrote:
>=20
>    > home users (because of the dynamic IPv4 address).
>   =20
>    I'm a home user with a dynamic IPv4 address, and it works just fine
>    for me.
>=20
> =3D> is your 6to4 prefix changing with your dynamic IPv4 address?

Yep.

> I think most users would like to get a *static* IPv6 prefix...

I think most users (especially home users) shouldn't have to know=20
the difference or care.

-Dave

------_=_NextPart_001_01C00619.1FFB2278
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Francis Dupont writes:</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp; In your previous mail you wrote:</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; &gt; home users (because of =
the dynamic IPv4 address).</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; I'm a home user with a dynamic =
IPv4 address, and it works just fine</FONT>

<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; for me.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; =3D&gt; is your 6to4 prefix changing with your =
dynamic IPv4 address?</FONT>
</P>

<P><FONT SIZE=3D2>Yep.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; I think most users would like to get a *static* =
IPv6 prefix...</FONT>
</P>

<P><FONT SIZE=3D2>I think most users (especially home users) shouldn't =
have to know </FONT>

<BR><FONT SIZE=3D2>the difference or care.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C00619.1FFB2278--


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 18:10:09 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19706
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 18:10:08 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA03036;
	Mon, 14 Aug 2000 16:09:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA15268;
	Mon, 14 Aug 2000 15:08:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EM7em08136
	for ngtrans-dist; Mon, 14 Aug 2000 15:07:40 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EM7V608129
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:07:31 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA03788
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:07:31 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA18721
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:07:30 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA20660;
        Mon, 14 Aug 2000 18:07:21 -0400 (EDT)
Message-Id: <200008142207.SAA20660@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
cc: "Dave Thaler" <dthaler@Exchange.Microsoft.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of "Mon, 14 Aug 2000 19:53:46 +0200."
             <200008141753.TAA43632@givry.rennes.enst-bretagne.fr> 
X-SUBJECT-MSG-FROM: Francis Dupont <Francis.Dupont@enst-bretagne.fr> 
Date: Mon, 14 Aug 2000 18:07:20 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> I think most users would like to get a *static* IPv6 prefix...

sure, if they had any sense.  but 6to4 is still useful even if
you cannot get a static prefix.  

Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 18:11:27 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19760
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 18:11:26 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA02392;
	Mon, 14 Aug 2000 16:08:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA03426;
	Mon, 14 Aug 2000 15:06:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EM5bE08118
	for ngtrans-dist; Mon, 14 Aug 2000 15:05:37 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EM5S608111
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:05:28 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA27825
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:05:28 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA17228
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:05:24 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA20593;
        Mon, 14 Aug 2000 18:05:14 -0400 (EDT)
Message-Id: <200008142205.SAA20593@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
cc: Randy Bush <randy@psg.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of "Mon, 14 Aug 2000 16:37:06 +0200."
             <200008141437.QAA42855@givry.rennes.enst-bretagne.fr> 
X-SUBJECT-MSG-FROM: Francis Dupont <Francis.Dupont@enst-bretagne.fr> 
Date: Mon, 14 Aug 2000 18:05:14 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> for instance it is not useful for ISPs (they'd prefer configured (ie.
> managed) tunnels) nor home users (because of the dynamic IPv4 address).

home users do not necessarily have dynamic IPv4 addresses.

and 6to4 is somewhat useful even with dynamic IPv4 addresses.

Keith



From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 14 18:12:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19790
	for <ngtrans-archive@odin.ietf.org>; Mon, 14 Aug 2000 18:12:16 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA04295;
	Mon, 14 Aug 2000 16:11:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA04158;
	Mon, 14 Aug 2000 15:09:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7EM98h08154
	for ngtrans-dist; Mon, 14 Aug 2000 15:09:08 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7EM8x608147
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:08:59 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA03996
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:09:00 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA19655
	for <ngtrans@sunroof.eng.sun.com>; Mon, 14 Aug 2000 15:08:57 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA20700;
        Mon, 14 Aug 2000 18:08:53 -0400 (EDT)
Message-Id: <200008142208.SAA20700@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
cc: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of "Mon, 14 Aug 2000 10:57:34 PDT."
             <19398D273324D3118A2B0008C7E9A5690D8CF0A9@SIT.platinum.corp.microsoft.com> 
X-SUBJECT-MSG-FROM: "Dave Thaler" <dthaler@Exchange.Microsoft.com> 
Date: Mon, 14 Aug 2000 18:08:52 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> > I think most users would like to get a *static* IPv6 prefix...
> 
> I think most users (especially home users) shouldn't have to know
> the difference or care.

I don't think that is likely.  There will always be more things you
can do with a static prefix than with a dynamic one. 

Keith


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 09:23:26 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14281
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 09:23:26 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04603;
	Tue, 15 Aug 2000 07:23:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA07973;
	Tue, 15 Aug 2000 06:22:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FDLOG08445
	for ngtrans-dist; Tue, 15 Aug 2000 06:21:24 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FDLH608438
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:21:17 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA17130
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:21:17 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA03443
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:21:16 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7FDLC622317;
	Tue, 15 Aug 2000 15:21:12 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id PAA25606;
	Tue, 15 Aug 2000 15:21:11 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id PAA46743;
	Tue, 15 Aug 2000 15:23:38 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008151323.PAA46743@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Mon, 14 Aug 2000 10:57:34 PDT.
             <19398D273324D3118A2B0008C7E9A5690D8CF0A9@SIT.platinum.corp.microsoft.com> 
Date: Tue, 15 Aug 2000 15:23:38 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   > I think most users would like to get a *static* IPv6 prefix...
   
   I think most users (especially home users) shouldn't have to know
   the difference or care.
   
=> they have to know and care... Unfortunately today they don't know
then even they care they cannot do something: we (IPv6 people) have
to educate them and show to them the difference between the Internet
and an on-line service (or here in France "the Internet is not a
super Minitel). I believe this is an important point for IPv6 success...

About 6to4, I'd like to get in the applicability statement something
like "if the embedded IPv4 address changes (<home user example>) then the
6to4 prefix will change".

Thanks

Francis.Dupont@enst-bretagne.fr

PS: I don't know how to educate home users. Many of them seem to be
really unsatisfied by Linux masquerade or other instances of NAT...
but how to explain why/how IPv6 is a better solution for them.
ISPs wouldn't like to give to them the possibility to run their own
servers (dynamic IPv4 addresses are not only for technical reasons :-).


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 09:23:36 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14292
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 09:23:35 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04741;
	Tue, 15 Aug 2000 07:23:24 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA17297;
	Tue, 15 Aug 2000 06:23:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FDMJw08467
	for ngtrans-dist; Tue, 15 Aug 2000 06:22:19 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FDM1608456
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:22:01 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA07938
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:22:01 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA03886
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:22:00 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7FDLu639482;
	Tue, 15 Aug 2000 15:21:56 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id PAA25616;
	Tue, 15 Aug 2000 15:21:56 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id PAA46759;
	Tue, 15 Aug 2000 15:24:23 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008151324.PAA46759@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Mon, 14 Aug 2000 10:57:34 PDT.
             <19398D273324D3118A2B0008C7E9A5690D8CF0A9@SIT.platinum.corp.microsoft.com> 
Date: Tue, 15 Aug 2000 15:24:23 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   > I think most users would like to get a *static* IPv6 prefix...
   
   I think most users (especially home users) shouldn't have to know
   the difference or care.
   
=> they have to know and care... Unfortunately today they don't know
then even they care they cannot do something: we (IPv6 people) have
to educate them and show to them the difference between the Internet
and an on-line service (or here in France "the Internet is not a
super Minitel). I believe this is an important point for IPv6 success...

About 6to4, I'd like to get in the applicability statement something
like "if the embedded IPv4 address changes (<home user example>) then the
6to4 prefix will change".

Thanks

Francis.Dupont@enst-bretagne.fr

PS: I don't know how to educate home users. Many of them seem to be
really unsatisfied by Linux masquerade or other instances of NAT...
but how to explain why/how IPv6 is a better solution for them.
ISPs wouldn't like to give to them the possibility to run their own
servers (dynamic IPv4 addresses are not only for technical reasons :-).


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 09:23:50 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14303
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 09:23:50 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04793;
	Tue, 15 Aug 2000 07:23:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA27829;
	Tue, 15 Aug 2000 06:22:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FDLvf08454
	for ngtrans-dist; Tue, 15 Aug 2000 06:21:57 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FDLm608447
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:21:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA17188
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:21:48 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA03737
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:21:47 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7FDLh639477;
	Tue, 15 Aug 2000 15:21:43 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id PAA25612;
	Tue, 15 Aug 2000 15:21:43 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id PAA46751;
	Tue, 15 Aug 2000 15:24:10 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008151324.PAA46751@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Mon, 14 Aug 2000 10:57:34 PDT.
             <19398D273324D3118A2B0008C7E9A5690D8CF0A9@SIT.platinum.corp.microsoft.com> 
Date: Tue, 15 Aug 2000 15:24:09 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   > I think most users would like to get a *static* IPv6 prefix...
   
   I think most users (especially home users) shouldn't have to know
   the difference or care.
   
=> they have to know and care... Unfortunately today they don't know
then even they care they cannot do something: we (IPv6 people) have
to educate them and show to them the difference between the Internet
and an on-line service (or here in France "the Internet is not a
super Minitel). I believe this is an important point for IPv6 success...

About 6to4, I'd like to get in the applicability statement something
like "if the embedded IPv4 address changes (<home user example>) then the
6to4 prefix will change".

Thanks

Francis.Dupont@enst-bretagne.fr

PS: I don't know how to educate home users. Many of them seem to be
really unsatisfied by Linux masquerade or other instances of NAT...
but how to explain why/how IPv6 is a better solution for them.
ISPs wouldn't like to give to them the possibility to run their own
servers (dynamic IPv4 addresses are not only for technical reasons :-).


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 09:50:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15235
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 09:50:15 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA14482;
	Tue, 15 Aug 2000 07:41:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA18998;
	Tue, 15 Aug 2000 06:40:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FDdsq08504
	for ngtrans-dist; Tue, 15 Aug 2000 06:39:54 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FDdl608497
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:39:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA10649
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 06:39:47 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA13739
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:39:46 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7FDde629620;
	Tue, 15 Aug 2000 15:39:40 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id PAA25725;
	Tue, 15 Aug 2000 15:39:40 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id PAA46959;
	Tue, 15 Aug 2000 15:42:07 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008151342.PAA46959@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Keith Moore <moore@cs.utk.edu>
cc: "Dave Thaler" <dthaler@Exchange.Microsoft.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Mon, 14 Aug 2000 18:08:52 EDT.
             <200008142208.SAA20700@astro.cs.utk.edu> 
Date: Tue, 15 Aug 2000 15:42:07 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   > > I think most users would like to get a *static* IPv6 prefix...
   > 
   > I think most users (especially home users) shouldn't have to know
   > the difference or care.
   
   I don't think that is likely.  There will always be more things you
   can do with a static prefix than with a dynamic one. 
   
=> I agree but I believe a large fraction of home users don't know how
to get a static prefix (*). Today they get by default with most of ISPs
a single dynamic IPv4 address and they have to give money for a static
address (up to 50USD/month) and more for a very small prefix...

Francis.Dupont@enst-bretagne.fr

PS (*): to get a static prefix at a reasonable price.


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 10:13:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15619
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 10:13:20 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04887;
	Tue, 15 Aug 2000 08:13:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA23112;
	Tue, 15 Aug 2000 07:12:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FEAwo08552
	for ngtrans-dist; Tue, 15 Aug 2000 07:10:58 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FEAp608545
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:10:52 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA22724
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:10:52 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA03381
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:10:50 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA159120; Tue, 15 Aug 2000 15:09:37 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA26502; Tue, 15 Aug 2000 15:10:36 +0100 (BST)
Message-ID: <39994F30.72333B91@hursley.ibm.com>
Date: Tue, 15 Aug 2000 09:09:52 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
CC: Dave Thaler <dthaler@Exchange.Microsoft.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <200008151323.PAA46743@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Francis Dupont wrote:
...
> About 6to4, I'd like to get in the applicability statement something
> like "if the embedded IPv4 address changes (<home user example>) then the
> 6to4 prefix will change".

The base 6to4 proposal isn't aimed at home users. This remark is relevant
to Tony's draft, but that is not what we are trying to get published
right now.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 10:52:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16281
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 10:52:21 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA07950;
	Tue, 15 Aug 2000 08:52:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA07258;
	Tue, 15 Aug 2000 07:47:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FEkgl08582
	for ngtrans-dist; Tue, 15 Aug 2000 07:46:42 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FEkZ608575
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:46:36 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA14236
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:46:35 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA18588
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 07:46:33 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7FEdR642541;
	Tue, 15 Aug 2000 16:39:27 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id QAA26036;
	Tue, 15 Aug 2000 16:39:27 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id QAA47383;
	Tue, 15 Aug 2000 16:41:54 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008151441.QAA47383@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: Dave Thaler <dthaler@Exchange.Microsoft.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of Tue, 15 Aug 2000 09:09:52 CDT.
             <39994F30.72333B91@hursley.ibm.com> 
Date: Tue, 15 Aug 2000 16:41:54 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   Francis Dupont wrote:
   ...
   > About 6to4, I'd like to get in the applicability statement something
   > like "if the embedded IPv4 address changes (<home user example>) then the
   > 6to4 prefix will change".
   
   The base 6to4 proposal isn't aimed at home users.

=> we agree but this is not in the current draft...

   This remark is relevant to Tony's draft, but that is not what we
   are trying to get published right now.
   
=> I don't know exactly Randy means by a note or an applicability statement
but IMHO this will be useful and should be in a 6to4 related document
(Tony's is fine for me if we can assume it will be published soon).

Thanks

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 11:11:24 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16639
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 11:11:24 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA22165;
	Tue, 15 Aug 2000 09:11:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA04820;
	Tue, 15 Aug 2000 08:08:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FF7nZ08607
	for ngtrans-dist; Tue, 15 Aug 2000 08:07:49 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FF7e608600
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:07:41 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA10388
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:07:40 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA19372
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 09:07:35 -0600 (MDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id LAA03762;
        Tue, 15 Aug 2000 11:05:55 -0400 (EDT)
Message-Id: <200008151505.LAA03762@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
cc: "Dave Thaler" <dthaler@Exchange.Microsoft.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of "Tue, 15 Aug 2000 15:24:23 +0200."
             <200008151324.PAA46759@givry.rennes.enst-bretagne.fr> 
X-SUBJECT-MSG-FROM: Francis Dupont <Francis.Dupont@enst-bretagne.fr> 
Date: Tue, 15 Aug 2000 11:05:55 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> PS: I don't know how to educate home users. Many of them seem to be
> really unsatisfied by Linux masquerade or other instances of NAT...
> but how to explain why/how IPv6 is a better solution for them.

people figure these things out.  the more sophisticated users figure
out how to exploit the better technology, and then they educate the
less sophisticated ones.  the average home user may not understand
why IPv6 is better, but someone will tell him that if he gets 6to4 
installed on his PC then he can run this cool new distributed game ..
so he'll do it.  either that or the distributed game will come with
the 6to4 code bundled in, and they'll get installed at the same time.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 11:18:52 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16750
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 11:18:52 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA27609;
	Tue, 15 Aug 2000 09:18:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA19707;
	Tue, 15 Aug 2000 08:15:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FFEkL08625
	for ngtrans-dist; Tue, 15 Aug 2000 08:14:46 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FFEd608618
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:14:39 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA27538
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:14:38 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA06142
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:14:38 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id QAA150856; Tue, 15 Aug 2000 16:13:24 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA23474; Tue, 15 Aug 2000 16:14:24 +0100 (BST)
Message-ID: <39995E06.4B4D2C6E@hursley.ibm.com>
Date: Tue, 15 Aug 2000 10:13:10 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <200008151441.QAA47383@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

I would rather that the base document defines its own applicability;
Tony's is an extension to the base concept. I thought that the base
document was already pretty clear on its scope, that's why I'm
asking for help on the words that need to be added. It's true that with
the publication of Tony's draft, I should add that the issue
of massive scaling to tiny sites is not covered by the base document

   Brian

Francis Dupont wrote:
> 
>  In your previous mail you wrote:
> 
>    Francis Dupont wrote:
>    ...
>    > About 6to4, I'd like to get in the applicability statement something
>    > like "if the embedded IPv4 address changes (<home user example>) then the
>    > 6to4 prefix will change".
> 
>    The base 6to4 proposal isn't aimed at home users.
> 
> => we agree but this is not in the current draft...
> 
>    This remark is relevant to Tony's draft, but that is not what we
>    are trying to get published right now.
> 
> => I don't know exactly Randy means by a note or an applicability statement
> but IMHO this will be useful and should be in a 6to4 related document
> (Tony's is fine for me if we can assume it will be published soon).
> 
> Thanks
> 
> Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 11:27:00 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16902
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 11:27:00 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA03715;
	Tue, 15 Aug 2000 09:26:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA21042;
	Tue, 15 Aug 2000 08:22:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FFLii08647
	for ngtrans-dist; Tue, 15 Aug 2000 08:21:44 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FFLc608640
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:21:38 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA20870
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:21:38 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA11035
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:21:36 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id QAA130930; Tue, 15 Aug 2000 16:20:26 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA24282; Tue, 15 Aug 2000 16:21:26 +0100 (BST)
Message-ID: <39995FA0.F5795167@hursley.ibm.com>
Date: Tue, 15 Aug 2000 10:20:00 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <E13Mx9F-0006Mw-00@rip.psg.com> <39980DAB.2B016564@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

For the record...

Brian E Carpenter wrote:
> 
> Randy,
> 
> Randy Bush wrote:
...
> >   o there needs to be a clear statement that
> >
> >     - this is a temporary transition mechanism
> 
> As others have said, it's a transition mechanism. It seems entirely
> redundant to say that it's temporary, but I can do it if it makes
> someone happy.

From the first paragraph of the introduction:

  "Also note that this is not considered
   to be a long term solution and that sites should migrate in due
   course to native IPv6 prefixes."

Section 5.6, Transition considerations, paragraphs 4 and 5, discuss 
the specific steps for migrating away from 6to4.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 11:33:30 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17100
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 11:33:29 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA09136;
	Tue, 15 Aug 2000 09:33:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA22172;
	Tue, 15 Aug 2000 08:28:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FFS6I08668
	for ngtrans-dist; Tue, 15 Aug 2000 08:28:06 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FFS0608661
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:28:00 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA14526
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 08:27:59 -0700 (PDT)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA05329
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 09:27:57 -0600 (MDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id LAA00260;
	Tue, 15 Aug 2000 11:27:22 -0400 (EDT)
Date: Tue, 15 Aug 2000 11:27:22 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200008151527.LAA00260@newdev.harvard.edu>
To: brian@hursley.ibm.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Cc: ngtrans@sunroof.eng.sun.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Scott Bradner <sob@harvard.edu>

>From the first paragraph of the introduction:

  "Also note that this is not considered
   to be a long term solution and that sites should migrate in due
   course to native IPv6 prefixes." 

I do not think this is an agressive enough statement

Scott


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 12:17:00 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18256
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 12:17:00 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA12854;
	Tue, 15 Aug 2000 10:15:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA04455;
	Tue, 15 Aug 2000 09:12:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FGBw608723
	for ngtrans-dist; Tue, 15 Aug 2000 09:11:58 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FGBp608716
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 09:11:51 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA17698
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 09:11:51 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA09916
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 10:11:49 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA127850; Tue, 15 Aug 2000 17:10:39 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA22702; Tue, 15 Aug 2000 17:11:40 +0100 (BST)
Message-ID: <39996AF0.410EBFA2@hursley.ibm.com>
Date: Tue, 15 Aug 2000 11:08:16 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <200008151527.LAA00260@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Scott Bradner wrote:
> 
> >From the first paragraph of the introduction:
> 
>   "Also note that this is not considered
>    to be a long term solution and that sites should migrate in due
>    course to native IPv6 prefixes."
> 
> I do not think this is an agressive enough statement

So what would be aggressive enough, given that defining a timeline
is clearly impossible?

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 13:13:59 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19674
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 13:13:59 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA04579;
	Tue, 15 Aug 2000 11:13:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA09865;
	Tue, 15 Aug 2000 10:11:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FHAdf08751
	for ngtrans-dist; Tue, 15 Aug 2000 10:10:39 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FHAX608744
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 10:10:33 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA03727
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 10:10:32 -0700 (PDT)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA29265
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 10:10:30 -0700 (PDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id NAA00583
	for ngtrans@sunroof.eng.sun.com; Tue, 15 Aug 2000 13:10:23 -0400 (EDT)
Date: Tue, 15 Aug 2000 13:10:23 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200008151710.NAA00583@newdev.harvard.edu>
To: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Scott Bradner <sob@harvard.edu>


> So what would be aggressive enough, given that defining a timeline
> is clearly impossible?

something like
  This mechanism has significant scaling issues particularly in regards to
  the growth of the routing table.  It is meant to be a temporary, stop-gap
  mechanism to provide IPv6 connectivity until such a time when native-mode
  IPv6 connectivity is commonly provided by ISPs.  Users must assume that
  they will have to migrate to native IPv6 prefixes when this is the case.


scott


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 14:51:06 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21882
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 14:51:06 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01208;
	Tue, 15 Aug 2000 12:50:31 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA07915;
	Tue, 15 Aug 2000 11:46:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FIiiL08814
	for ngtrans-dist; Tue, 15 Aug 2000 11:44:44 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FIic608807
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:44:38 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA25833
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:44:36 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA13624
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:44:35 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id TAA127896; Tue, 15 Aug 2000 19:43:24 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id TAA20980; Tue, 15 Aug 2000 19:44:24 +0100 (BST)
Message-ID: <39998D5E.A564EF28@hursley.ibm.com>
Date: Tue, 15 Aug 2000 13:35:10 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <200008151710.NAA00583@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Scott Bradner wrote:
> 
> > So what would be aggressive enough, given that defining a timeline
> > is clearly impossible?
> 
> something like
>   This mechanism has significant scaling issues particularly in regards to
>   the growth of the routing table.  

But this is not really the case. Basic 6to4 adds one entry, 2002::/16, to the 
native IPv6 routing table. There are scaling issues for massive numbers of tiny 
sites- covered by Tony's draft - and I do need to add a statement that the base
document does not cover that situation. (Tony's draft wasn't out when
this -06 draft was done.) So I agree that scaling should be mentioned but the
words will be a bit different.

>   It is meant to be a temporary, stop-gap

I agree of course with "temporary." I object to "stop-gap", it's pejorative.
How about "start-up"?

>   mechanism to provide IPv6 connectivity until such a time when native-mode
>   IPv6 connectivity is commonly provided by ISPs.  Users must assume that
>   they will have to migrate to native IPv6 prefixes when this is the case.

Correct. In fact the only requirement is that your *own* ISP has native
support, so it's a bit stronger.

Thanks

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 14:57:45 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21968
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 14:57:44 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA07738;
	Tue, 15 Aug 2000 12:57:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA28584;
	Tue, 15 Aug 2000 11:55:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FIs9i08836
	for ngtrans-dist; Tue, 15 Aug 2000 11:54:09 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FIs0608829
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:54:01 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA11045
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:53:59 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA21003
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:53:58 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA10243;
        Tue, 15 Aug 2000 14:53:56 -0400 (EDT)
Message-Id: <200008151853.OAA10243@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Scott Bradner <sob@harvard.edu>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt 
In-reply-to: Your message of "Tue, 15 Aug 2000 13:10:23 EDT."
             <200008151710.NAA00583@newdev.harvard.edu> 
X-SUBJECT-MSG-FROM: Scott Bradner <sob@harvard.edu> 
Date: Tue, 15 Aug 2000 14:53:56 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

  This mechanism has significant scaling issues particularly in regards to
  the growth of the routing table. 

I don't see how that's true.  As currently defined the mechanism uses at
most one IPv6 routing table entry.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 15:04:03 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22144
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 15:04:02 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA12920;
	Tue, 15 Aug 2000 13:03:31 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA29953;
	Tue, 15 Aug 2000 11:59:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FIwfT08858
	for ngtrans-dist; Tue, 15 Aug 2000 11:58:41 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FIwY608851
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:58:35 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA23541
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 11:58:33 -0700 (PDT)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA08471
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 12:58:30 -0600 (MDT)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id OAA01009;
	Tue, 15 Aug 2000 14:58:19 -0400 (EDT)
Date: Tue, 15 Aug 2000 14:58:19 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200008151858.OAA01009@newdev.harvard.edu>
To: brian@hursley.ibm.com, sob@harvard.edu
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Cc: ngtrans@sunroof.eng.sun.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Scott Bradner <sob@harvard.edu>



> > > So what would be aggressive enough, given that defining a timeline
> > > is clearly impossible?
> > 
> > something like
> >   This mechanism has significant scaling issues particularly in regards to
> >   the growth of the routing table.  
> 
> But this is not really the case. Basic 6to4 adds one entry, 2002::/16, to the 
> native IPv6 routing table. There are scaling issues for massive numbers of tiny 
> sites-covered by Tony's draft - and I do need to add a statement that the base
> document does not cover that situation. (Tony's draft wasn't out when
> this -06 draft was done.) So I agree that scaling should be mentioned but the
> words will be a bit different.

it adds random (from the point of view of the v6 network topology) values
below 2002::/16

> >   It is meant to be a temporary, stop-gap
> 
> I agree of course with "temporary." I object to "stop-gap", it's pejorative.
> How about "start-up"?

works for me

> >   mechanism to provide IPv6 connectivity until such a time when native-mode
> >   IPv6 connectivity is commonly provided by ISPs.  Users must assume that
> >   they will have to migrate to native IPv6 prefixes when this is the case.
> 
> Correct. In fact the only requirement is that your *own* ISP has native
> support, so it's a bit stronger.

OK


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 15:56:20 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23132
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 15:56:20 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA26761;
	Tue, 15 Aug 2000 13:56:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA13158;
	Tue, 15 Aug 2000 12:54:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FJqnZ08952
	for ngtrans-dist; Tue, 15 Aug 2000 12:52:49 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FJqg608945
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 12:52:42 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA07813
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 12:52:40 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA23816
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 13:52:39 -0600 (MDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2172.1);
	 Tue, 15 Aug 2000 12:50:56 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 15 Aug 2000 12:51:23 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Tue, 15 Aug 2000 12:40:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C006F0.7EEDE914"
Subject: RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Date: Tue, 15 Aug 2000 12:39:15 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A5690D8CF0AF@SIT.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Thread-Index: AcAG7VDoFYMWlQjrQqKnLU3XPwd3eQAAqbtQ
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Brian E Carpenter" <brian@hursley.ibm.com>,
        "Scott Bradner" <sob@harvard.edu>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 15 Aug 2000 19:40:07.0618 (UTC) FILETIME=[9DD39220:01C006F0]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C006F0.7EEDE914
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Brian Carpenter writes:
> Scott Bradner wrote:
> >   This mechanism has significant scaling issues=20
> particularly in regards to
> >   the growth of the routing table. =20
>=20
> But this is not really the case. Basic 6to4 adds one entry,=20
> 2002::/16, to the=20
> native IPv6 routing table. There are scaling issues for=20
> massive numbers of tiny=20
> sites- covered by Tony's draft - and I do need to add a=20
> statement that the base
> document does not cover that situation. (Tony's draft wasn't out when
> this -06 draft was done.) So I agree that scaling should be=20
> mentioned but the
> words will be a bit different.

Right, even with Tony's draft, no additional prefixes are injected
into the v6 infrastructure.  The v6 infrastructure has exactly
one additional prefix (2002::/16).

With Tony's draft (if I understand it correctly), the 6to4=20
*site* adds additional prefixes to the internal tables on=20
the 6to4 site gateway router (and doesn't advertise them).
In the worst case, the number of prefixes on a site router=20
will be the number of prefixes in the v6 infrastructure=20
that are known to relays.

Tony's draft can say this, but I don't see any scaling
problems with the base 6to4 draft.

-Dave

------_=_NextPart_001_01C006F0.7EEDE914
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Brian Carpenter writes:</FONT>

<BR><FONT SIZE=3D2>&gt; Scott Bradner wrote:</FONT>

<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; This mechanism has significant =
scaling issues </FONT>

<BR><FONT SIZE=3D2>&gt; particularly in regards to</FONT>

<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp; the growth of the routing =
table.&nbsp; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; But this is not really the case. Basic 6to4 adds =
one entry, </FONT>

<BR><FONT SIZE=3D2>&gt; 2002::/16, to the </FONT>

<BR><FONT SIZE=3D2>&gt; native IPv6 routing table. There are scaling =
issues for </FONT>

<BR><FONT SIZE=3D2>&gt; massive numbers of tiny </FONT>

<BR><FONT SIZE=3D2>&gt; sites- covered by Tony's draft - and I do need =
to add a </FONT>

<BR><FONT SIZE=3D2>&gt; statement that the base</FONT>

<BR><FONT SIZE=3D2>&gt; document does not cover that situation. (Tony's =
draft wasn't out when</FONT>

<BR><FONT SIZE=3D2>&gt; this -06 draft was done.) So I agree that =
scaling should be </FONT>

<BR><FONT SIZE=3D2>&gt; mentioned but the</FONT>

<BR><FONT SIZE=3D2>&gt; words will be a bit different.</FONT>
</P>

<P><FONT SIZE=3D2>Right, even with Tony's draft, no additional prefixes =
are injected</FONT>

<BR><FONT SIZE=3D2>into the v6 infrastructure.&nbsp; The v6 =
infrastructure has exactly</FONT>

<BR><FONT SIZE=3D2>one additional prefix (2002::/16).</FONT>
</P>

<P><FONT SIZE=3D2>With Tony's draft (if I understand it correctly), the =
6to4 </FONT>

<BR><FONT SIZE=3D2>*site* adds additional prefixes to the internal =
tables on </FONT>

<BR><FONT SIZE=3D2>the 6to4 site gateway router (and doesn't advertise =
them).</FONT>

<BR><FONT SIZE=3D2>In the worst case, the number of prefixes on a site =
router </FONT>

<BR><FONT SIZE=3D2>will be the number of prefixes in the v6 =
infrastructure </FONT>

<BR><FONT SIZE=3D2>that are known to relays.</FONT>
</P>

<P><FONT SIZE=3D2>Tony's draft can say this, but I don't see any =
scaling</FONT>

<BR><FONT SIZE=3D2>problems with the base 6to4 draft.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C006F0.7EEDE914--


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 15 16:12:53 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23598
	for <ngtrans-archive@odin.ietf.org>; Tue, 15 Aug 2000 16:12:53 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA10734;
	Tue, 15 Aug 2000 14:12:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA12155;
	Tue, 15 Aug 2000 13:12:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7FK9rB08986
	for ngtrans-dist; Tue, 15 Aug 2000 13:09:53 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7FK9k608979
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 13:09:46 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA24820
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 13:09:45 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA14461
	for <ngtrans@sunroof.eng.sun.com>; Tue, 15 Aug 2000 13:09:43 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id VAA175534; Tue, 15 Aug 2000 21:08:32 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id VAA18808; Tue, 15 Aug 2000 21:09:33 +0100 (BST)
Message-ID: <3999A0E4.47C81D25@hursley.ibm.com>
Date: Tue, 15 Aug 2000 14:58:28 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Scott Bradner <sob@harvard.edu>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <200008151858.OAA01009@newdev.harvard.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Scott Bradner wrote:
> 
> > > > So what would be aggressive enough, given that defining a timeline
> > > > is clearly impossible?
> > >
> > > something like
> > >   This mechanism has significant scaling issues particularly in regards to
> > >   the growth of the routing table.
> >
> > But this is not really the case. Basic 6to4 adds one entry, 2002::/16, to the
> > native IPv6 routing table. There are scaling issues for massive numbers of tiny
> > sites-covered by Tony's draft - and I do need to add a statement that the base
> > document does not cover that situation. (Tony's draft wasn't out when
> > this -06 draft was done.) So I agree that scaling should be mentioned but the
> > words will be a bit different.
> 
> it adds random (from the point of view of the v6 network topology) values
> below 2002::/16

Not on the native IPv6 side of the relay router - the *only* route that
goes into the native BGP4+ world is 2002::/16. If you do decide to run
BGP4+ on the 6to4 side of the relay router (which is optional), yes there
will be more specific routes that side, but it's a finite administrative
domain so there is a bound on the scaling issue. It looks as if I need
to spell that out more explicitly. 

  Brian

> 
> > >   It is meant to be a temporary, stop-gap
> >
> > I agree of course with "temporary." I object to "stop-gap", it's pejorative.
> > How about "start-up"?
> 
> works for me
> 
> > >   mechanism to provide IPv6 connectivity until such a time when native-mode
> > >   IPv6 connectivity is commonly provided by ISPs.  Users must assume that
> > >   they will have to migrate to native IPv6 prefixes when this is the case.
> >
> > Correct. In fact the only requirement is that your *own* ISP has native
> > support, so it's a bit stronger.
> 
> OK

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Program Director, Internet Standards & Technology, IBM 
On assignment for IBM at http://www.iCAIR.org 
Board Chairman, Internet Society http://www.isoc.org
Non-IBM email: brian@icair.org


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 21 17:04:42 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09440
	for <ngtrans-archive@odin.ietf.org>; Mon, 21 Aug 2000 17:04:42 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA18344;
	Mon, 21 Aug 2000 15:04:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA23009;
	Mon, 21 Aug 2000 14:03:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7LL2jA13245
	for ngtrans-dist; Mon, 21 Aug 2000 14:02:45 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7LL0e613229;
	Mon, 21 Aug 2000 14:00:42 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA19947;
	Mon, 21 Aug 2000 14:00:38 -0700 (PDT)
Received: from ztxmail02.ztx.compaq.com (ztxmail02.ztx.compaq.com [161.114.1.206])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA12322;
	Mon, 21 Aug 2000 14:00:31 -0700 (PDT)
Received: by ztxmail02.ztx.compaq.com (Postfix, from userid 12345)
	id 567143E27; Mon, 21 Aug 2000 16:00:31 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail02.ztx.compaq.com (Postfix) with ESMTP
	id 8067311F4; Mon, 21 Aug 2000 16:00:30 -0500 (CDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id QAA0000544911; Mon, 21 Aug 2000 16:58:32 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008212058.QAA0000544911@anw.zk3.dec.com>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        dhcp-v6@bucknell.edu, members@ipv6forum.com, tech@ipv6forum.com
Cc: reinhard.scholl@etsi.fr
Subject: (ngtrans) IPv6 ETSI Test Event Web Page Pointer
Date: Mon, 21 Aug 2000 16:58:32 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

  ** PLEASE DO NOT RESPOND TO THIS MAIL **

Hi Folks,

Even though UNH cannot participate in this test event our colleagues
under the guidance of Francis Dupont at ENST in France have come to the
aid of IPv6 developers (thank you ENST and Francis) and working with
Reihhard Scholl there will be an IPv6 test event Oct 2-6.

I believe this is a very important event and vendors should really try
to attend.  Plus it is in a nice place "French Riviera" not that there
won't be a lot of hard work done of course.  This is serious stuff folks
and 3GPP needs our support and this test event.  Please see the
following URL:

http://www.etsi.org/bake-off

regards and thanks for your support,
/jim


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 22 08:59:50 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04205
	for <ngtrans-archive@odin.ietf.org>; Tue, 22 Aug 2000 08:59:45 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA09978;
	Tue, 22 Aug 2000 06:59:15 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA04425;
	Tue, 22 Aug 2000 05:57:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7MCuju13750
	for ngtrans-dist; Tue, 22 Aug 2000 05:56:45 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7MCua613743;
	Tue, 22 Aug 2000 05:56:36 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA05904;
	Tue, 22 Aug 2000 05:56:37 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gollum.axion.bt.co.uk (gollum.axion.bt.co.uk [132.146.17.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA19531;
	Tue, 22 Aug 2000 05:56:35 -0700 (PDT)
Received: from cbtlipnt02.btlabs.bt.co.uk by gollum (local) with ESMTP;
          Tue, 22 Aug 2000 13:57:15 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <PTMLK736>;
          Tue, 22 Aug 2000 13:55:56 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5AB6@mbtlipnt02.btlabs.bt.co.uk>
To: ngtrans@sunroof.eng.sun.com
Cc: ipng@sunroof.eng.sun.com
Subject: (ngtrans) Dual Stack Mobility + Use of MIPv6 CCoA
Date: Tue, 22 Aug 2000 13:52:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.88)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

All,

As promised, this draft shows how IPv4 based communications can be
supported by a dual stack mobile node that only supports Mobile IPv6
(MIPv6). The aim is to use MIPv6 for mobility services while the
Mobile can still use its dual stack capabilities for IPv4
communications without the need for translation.

This draft is also relevant to recent discussions on the IPng list regarding
use of CCoA as source address in Mobile IPv6 Spec. In the draft we use the
MIPv6 CCoA to request an IPv4 address from the local DHCPv6 server (ala
DSTM).

Regards
George


> -----Original Message-----
> From:	Internet-Drafts@ietf.org [SMTP:Internet-Drafts@ietf.org]
> Sent:	Tuesday, August 22, 2000 12:08 PM
> To:	IETF-Announce
> Subject:	I-D ACTION:draft-tsirtsis-v4-over-mipv6-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: IPv4 over Mobile IPv6 for Dual Stack nodes
> 	Author(s)	: G. Tsirtsis, A. O'Neill, S. Corson
> 	Filename	: draft-tsirtsis-v4-over-mipv6-00.txt
> 	Pages		: 4
> 	Date		: 21-Aug-00
> 	
> In this document we show how IPv4 based communications can be
> supported by a dual stack mobile node that only supports Mobile IPv6
> (MIPv6). The aim is to use MIPv6 for mobility services while the
> Mobile can still use its dual stack capabilities for IPv4
> communications without the need for translation.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-tsirtsis-v4-over-mipv6-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 22 18:23:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16947
	for <ngtrans-archive@odin.ietf.org>; Tue, 22 Aug 2000 18:23:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA26438;
	Tue, 22 Aug 2000 16:23:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA17733;
	Tue, 22 Aug 2000 15:22:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7MML8o14058
	for ngtrans-dist; Tue, 22 Aug 2000 15:21:08 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7MMKx614051
	for <ngtrans@sunroof.eng.sun.com>; Tue, 22 Aug 2000 15:21:00 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA12765
	for <ngtrans@sunroof.eng.sun.com>; Tue, 22 Aug 2000 15:21:00 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA28302
	for <ngtrans@sunroof.eng.sun.com>; Tue, 22 Aug 2000 15:20:59 -0700 (PDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA03343;
	Tue, 22 Aug 2000 15:20:57 -0700 (PDT)
Message-Id: <200008222220.PAA03343@boreas.isi.edu>
To: IETF-Announce: ;
Subject: (ngtrans) RFC 2893 on IPv6 Transition Mechanism
Cc: rfc-ed@ISI.EDU, ngtrans@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 22 Aug 2000 15:20:57 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: RFC Editor <rfc-ed@ISI.EDU>


--NextPart


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


        RFC 2893

        Title:	    Transition Mechanisms for IPv6 Hosts and Routers
        Author(s):  R. Gilligan, E. Nordmark
        Status:     Standards Track
	Date:       August 2000
        Mailbox:    gilligan@freegate.com, nordmark@eng.sun.com
        Pages:      29
        Characters: 62731
        Obsoletes:  1933

        I-D Tag:    draft-ietf-ngtrans-mech-06.txt 

        URL:        ftp://ftp.isi.edu/in-notes/rfc2893.txt


This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4 routing
infrastructures.  They are designed to allow IPv6 nodes to maintain
complete compatibility with IPv4, which should greatly simplify the
deployment of IPv6 in the Internet, and facilitate the eventual
transition of the entire Internet to IPv6.  This document obsoletes
RFC 1933.

This document is a product of the Next Generation Transition Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <000822151847.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2893

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2893.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <000822151847.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--


From owner-ngtrans@sunroof.eng.sun.com  Wed Aug 23 10:38:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13147
	for <ngtrans-archive@odin.ietf.org>; Wed, 23 Aug 2000 10:38:00 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA25683;
	Wed, 23 Aug 2000 08:37:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA23560;
	Wed, 23 Aug 2000 07:36:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7NEZVd14451
	for ngtrans-dist; Wed, 23 Aug 2000 07:35:31 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7NEZI614444
	for <ngtrans@sunroof.eng.sun.com>; Wed, 23 Aug 2000 07:35:19 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA27500
	for <ngtrans@sunroof.eng.sun.com>; Wed, 23 Aug 2000 07:35:08 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gollum.axion.bt.co.uk (gollum.axion.bt.co.uk [132.146.17.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA20223
	for <ngtrans@sunroof.eng.sun.com>; Wed, 23 Aug 2000 07:35:08 -0700 (PDT)
Received: from cbtlipnt01.btlabs.bt.co.uk by gollum (local) with ESMTP;
          Wed, 23 Aug 2000 15:15:55 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <3GLRMRLP>;
          Wed, 23 Aug 2000 15:14:37 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5AC5@mbtlipnt02.btlabs.bt.co.uk>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) 6to4 and dstm
Date: Wed, 23 Aug 2000 15:11:19 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.88)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

All,

You may want to have a look at this draft (see below). The draft shows one
way for Dual Stack Intranets to be deployed with minimum need for IPv4
address space and no native IPv6 connectivity.

The purpose of this draft as well as the one I sent out yesterday
(draft-tsirtsis-v4-over-mipv6-00.txt) is to show that Dual Stack deployment
is not only still possible but also easy. I had a private comment on the
v4-over-mipv6 draft saying that this is trivial and indeed it is! That is
the point!

It seams to me that a lot of people have given up on the idea of Dual Stack
especially in mobile networks. Although the idea that 3G is going IPv6 ONLY
(for at least some services) is kind of cool and it makes us all feel nice
about IPv6 deployment, we should not loose sight of the fact that in
engineering terms Dual Stack is what we want and need. The above drafts are
just meant to show that this is still possible!

The dstm/6to4 draft also touches on something that has been talked about as
a future work item in ngtrans. i.e: interactions between transition tools.
This is just an example, there is still a lot of work to be done.


Regards
George

Notice: This contribution is the personal view of the 
author and does not necessarily reflect the technical nor
commercial direction of his employer.

> -----Original Message-----
> From:	Internet-Drafts@ietf.org [SMTP:Internet-Drafts@ietf.org]
> Sent:	Wednesday, August 23, 2000 11:35 AM
> To:	IETF-Announce
> Subject:	I-D ACTION:draft-tsirtsis-6to4-and-dstm-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: Dual Stack deployment using DSTM and 6to4
> 	Author(s)	: G. Tsirtsis
> 	Filename	: draft-tsirtsis-6to4-and-dstm-00.txt
> 	Pages		: 5
> 	Date		: 22-Aug-00
> 	
> It is desirable that most of IPv6 deployment is based on Dual Stack
> IPv4 and IPv6 nodes so that interoperability with the current IPv4
> based Internet be seamless. The 6to4 transition mechanism offers a
> automated mechanisms for addressing an IPv6 site as well as
> interconnectivity with other IPv6 sites when no native IPv6
> connectivity is available. DSTM provides a mechanism for dynamic
> IPv4 address allocation to Dual Stack nodes and a mechanism to send
> packets over a network that only supports IPv6 routing. By combining
> the two mechanisms we show how Dual Stack Intranets may be deployed
> with minimum need for IPv4 address space and no native IPv6
> connectivity.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-tsirtsis-6to4-and-dstm-00.txt
> 


From chantall@upperside.fr  Wed Aug 23 12:46:32 2000
Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18258
	for <ngtrans-archive@odin.ietf.org>; Wed, 23 Aug 2000 12:46:32 -0400 (EDT)
Received: from oleane  (dyn-1-1-008.Vin.dialup.oleane.fr [195.25.4.8])  by smtp1.cluster.oleane.net  with SMTP id SAA55167; Wed, 23 Aug 2000 18:16:44 +0200 (CEST)
Message-ID: <005f01c00d1d$c4d6d480$0401a8c0@oleane.com>
From: "Chantal Ladouce" <chantall@upperside.fr>
To: "info" <info@upperside.fr>
Subject: Upper Side's conferences 
Date: Wed, 23 Aug 2000 18:16:37 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0053_01C00D2E.47076EA0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300

This is a multi-part message in MIME format.

------=_NextPart_000_0053_01C00D2E.47076EA0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

VoIP, Security, Policing: once again, Upper Side's conferences address =
the hottest topics in the IP world and gather the most eminent =
specialists in each of these domains.
Get more details on the web site:
http://www.upperside.fr
and download the programme of the IPSec Global Summit, IP Policing and =
H.323 events.


------=_NextPart_000_0053_01C00D2E.47076EA0
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT color=3D#000000 size=3D2>VoIP, Security, Policing: once =
again, Upper=20
Side's conferences address the hottest topics in the IP world and gather =
the=20
most eminent specialists in each of these domains.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT><FONT size=3D2>Get more =
details on the web=20
site:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr">http://www.upperside.fr</A></FONT></DIV>=

<DIV><FONT size=3D2></FONT><FONT color=3D#000000 size=3D2>and download =
the programme=20
of the IPSec Global Summit, IP Policing and H.323=20
events.</FONT></FONT></DIV></DIV></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0053_01C00D2E.47076EA0--



From owner-ngtrans@sunroof.eng.sun.com  Wed Aug 23 21:36:46 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26321
	for <ngtrans-archive@odin.ietf.org>; Wed, 23 Aug 2000 21:36:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA00218;
	Wed, 23 Aug 2000 19:36:41 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA15495;
	Wed, 23 Aug 2000 18:36:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7O1ZJv14761
	for ngtrans-dist; Wed, 23 Aug 2000 18:35:19 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7O1ZA614754;
	Wed, 23 Aug 2000 18:35:10 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA23647;
	Wed, 23 Aug 2000 18:35:10 -0700 (PDT)
Received: from extmx.itri.org.tw (extmx.itri.org.tw [140.96.158.1])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA29607;
	Wed, 23 Aug 2000 19:34:48 -0600 (MDT)
Received: from nti.itri.org.tw (nti.itri.org.tw [140.96.157.2])
	by extmx.itri.org.tw (8.8.8/8.8.8) with ESMTP id JAA05755;
	Thu, 24 Aug 2000 09:37:52 +0800 (CST)
Received: from tsao (pc104125.ccl.itri.org.tw [140.96.104.125])
	by nti.itri.org.tw (8.8.8/8.8.8) with SMTP id JAA24419;
	Thu, 24 Aug 2000 09:35:35 +0800 (CST)
Message-ID: <00b501c00d6b$a5e7fd80$7d68608c@tsao>
From: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>
To: <ngtrans@sunroof.eng.sun.com>
Cc: <ipng@sunroof.eng.sun.com>
References: <5104D4DBC598D211B5FE0000F8FE7EB2078A5AB6@mbtlipnt02.btlabs.bt.co.uk>
Subject: (ngtrans) Mobile IPv4/ Mobile IPv6 Interworking Issues
Date: Thu, 24 Aug 2000 09:35:55 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00B2_01C00DAE.B3910470"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>

This is a multi-part message in MIME format.

------=_NextPart_000_00B2_01C00DAE.B3910470
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear All,=20

Sorry for interrupting you.
The IPv4/IPv6 interworking problems seems to involve both Mobile IP and =
IPv4/IPv6 transition issues. We also have a draft which is relevant to =
this topic. The document specifies mechanisms to solve mobility problems =
in IPv4 and IPv6 interconnected networks for IPv4 or IPv6 mobile nodes. =
The solution adopts dual stack model that implements a new address =
mapper on mobile nodes. The dual stack model with the address mapper can =
facilicate the mobility services for IPv4 or IPv6 mobile nodes in =
between IPv4 and IPv6 networks. You can get it from the following URL, =
if you are interested in it
http://www.ietf.org/internet-drafts/draft-tsao-mobileip-duelstack-model-0=
0.txt

I appreciate your suggestions and comments. Thank you.

Best Regards,

Shiao-Li Tsao




----- Original Message -----=20
From: <george.tsirtsis@bt.com>
To: <ngtrans@sunroof.eng.sun.com>
Cc: <ipng@sunroof.eng.sun.com>
Sent: Tuesday, August 22, 2000 8:52 PM
Subject: (ngtrans) Dual Stack Mobility + Use of MIPv6 CCoA


> All,
>=20
> As promised, this draft shows how IPv4 based communications can be
> supported by a dual stack mobile node that only supports Mobile IPv6
> (MIPv6). The aim is to use MIPv6 for mobility services while the
> Mobile can still use its dual stack capabilities for IPv4
> communications without the need for translation.
>=20
> This draft is also relevant to recent discussions on the IPng list =
regarding
> use of CCoA as source address in Mobile IPv6 Spec. In the draft we use =
the
> MIPv6 CCoA to request an IPv4 address from the local DHCPv6 server =
(ala
> DSTM).
>=20
> Regards
> George
>=20
>=20
> > -----Original Message-----
> > From: Internet-Drafts@ietf.org [SMTP:Internet-Drafts@ietf.org]
> > Sent: Tuesday, August 22, 2000 12:08 PM
> > To: IETF-Announce
> > Subject: I-D ACTION:draft-tsirtsis-v4-over-mipv6-00.txt
> >=20
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >=20
> >=20
> > Title : IPv4 over Mobile IPv6 for Dual Stack nodes
> > Author(s) : G. Tsirtsis, A. O'Neill, S. Corson
> > Filename : draft-tsirtsis-v4-over-mipv6-00.txt
> > Pages : 4
> > Date : 21-Aug-00
> >=20
> > In this document we show how IPv4 based communications can be
> > supported by a dual stack mobile node that only supports Mobile IPv6
> > (MIPv6). The aim is to use MIPv6 for mobility services while the
> > Mobile can still use its dual stack capabilities for IPv4
> > communications without the need for translation.
> >=20
> > A URL for this Internet-Draft is:
> > =
http://www.ietf.org/internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt
> >=20
> > Internet-Drafts are also available by anonymous FTP. Login with the
> > username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > "get draft-tsirtsis-v4-over-mipv6-00.txt".
> >=20
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html=20
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >=20
> >=20
> > Internet-Drafts can also be obtained by e-mail.
> >=20
> > Send a message to:
> > mailserv@ietf.org.
> > In the body type:
> > "FILE /internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt".
> >=20
> > NOTE: The mail server at ietf.org can return the document in
> > MIME-encoded form by using the "mpack" utility.  To use this
> > feature, insert the command "ENCODING mime" before the "FILE"
> > command.  To decode the response(s), you will need "munpack" or
> > a MIME-compliant mail reader.  Different MIME-compliant mail readers
> > exhibit different behavior, especially when dealing with
> > "multipart" MIME messages (i.e. documents which have been split
> > up into multiple messages), so check your local documentation on
> > how to manipulate these messages.
> >=20
> >=20
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.

------=_NextPart_000_00B2_01C00DAE.B3910470
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Courier New" size=3D2>Dear All, </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Sorry for interrupting =
you.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><FONT face=3D"Courier New" =
size=3D2>The=20
IPv4/IPv6 interworking problems seems to involve both&nbsp;Mobile IP=20
and&nbsp;IPv4/IPv6 transition issues. </FONT></FONT><FONT =
face=3D"Courier New"=20
size=3D2>We&nbsp;also have a draft which is relevant to this=20
topic.&nbsp;The&nbsp;document specifies mechanisms to solve=20
mobility&nbsp;problems in IPv4 and IPv6 interconnected networks for IPv4 =
or IPv6=20
mobile nodes. The solution&nbsp;adopts dual stack model that implements =
a new=20
address mapper&nbsp;on mobile nodes. </FONT><FONT face=3D"Courier New" =
size=3D2>The=20
dual stack model with the address mapper can facilicate t</FONT><FONT=20
face=3D"Courier New" size=3D2>he mobility services for&nbsp;IPv4 or IPv6 =
mobile=20
nodes&nbsp;in between IPv4 and IPv6 networks. </FONT><FONT =
face=3D"Courier New"=20
size=3D2>You can get it from the following URL, if you are interested in =

it</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-tsao-mobileip-duelstack=
-model-00.txt">http://www.ietf.org/internet-drafts/draft-tsao-mobileip-du=
elstack-model-00.txt</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>I&nbsp;appreciate your =
suggestions and=20
comments. Thank you.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Best Regards,<BR></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Shiao-Li =
Tsao<BR><BR></DIV></FONT>
<DIV><FONT face=3D"Courier New" size=3D2>&nbsp;</DIV></FONT>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>----- Original Message ----- =
</FONT>
<DIV><FONT face=3D"Courier New" size=3D2>From: &lt;</FONT><A=20
href=3D"mailto:george.tsirtsis@bt.com"><FONT face=3D"Courier New"=20
size=3D2>george.tsirtsis@bt.com</FONT></A><FONT face=3D"Courier New"=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>To: &lt;</FONT><A=20
href=3D"mailto:ngtrans@sunroof.eng.sun.com"><FONT face=3D"Courier New"=20
size=3D2>ngtrans@sunroof.eng.sun.com</FONT></A><FONT face=3D"Courier =
New"=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Cc: &lt;</FONT><A=20
href=3D"mailto:ipng@sunroof.eng.sun.com"><FONT face=3D"Courier New"=20
size=3D2>ipng@sunroof.eng.sun.com</FONT></A><FONT face=3D"Courier New"=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Sent: Tuesday, August 22, 2000 =
8:52=20
PM</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Subject: (ngtrans) Dual Stack =
Mobility +=20
Use of MIPv6 CCoA</FONT></DIV></DIV>
<DIV><BR></DIV><FONT face=3D"Courier New" size=3D2>&gt; All,<BR>&gt; =
<BR>&gt; As=20
promised, this draft shows how IPv4 based communications can be<BR>&gt;=20
supported by a dual stack mobile node that only supports Mobile =
IPv6<BR>&gt;=20
(MIPv6). The aim is to use MIPv6 for mobility services while the<BR>&gt; =
Mobile=20
can still use its dual stack capabilities for IPv4<BR>&gt; =
communications=20
without the need for translation.<BR>&gt; <BR>&gt; This draft is also =
relevant=20
to recent discussions on the IPng list regarding<BR>&gt; use of CCoA as =
source=20
address in Mobile IPv6 Spec. In the draft we use the<BR>&gt; MIPv6 CCoA =
to=20
request an IPv4 address from the local DHCPv6 server (ala<BR>&gt; =
DSTM).<BR>&gt;=20
<BR>&gt; Regards<BR>&gt; George<BR>&gt; <BR>&gt; <BR>&gt; &gt; =
-----Original=20
Message-----<BR>&gt; &gt; From: </FONT><A=20
href=3D"mailto:Internet-Drafts@ietf.org"><FONT face=3D"Courier New"=20
size=3D2>Internet-Drafts@ietf.org</FONT></A><FONT face=3D"Courier New" =
size=3D2>=20
[</FONT><A href=3D"mailto:SMTP:Internet-Drafts@ietf.org"><FONT =
face=3D"Courier New"=20
size=3D2>SMTP:Internet-Drafts@ietf.org</FONT></A><FONT face=3D"Courier =
New"=20
size=3D2>]<BR>&gt; &gt; Sent: Tuesday, August 22, 2000 12:08 PM<BR>&gt; =
&gt; To:=20
IETF-Announce<BR>&gt; &gt; Subject: I-D=20
ACTION:draft-tsirtsis-v4-over-mipv6-00.txt<BR>&gt; &gt; <BR>&gt; &gt; A =
New=20
Internet-Draft is available from the on-line Internet-Drafts<BR>&gt; =
&gt;=20
directories.<BR>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; Title : IPv4 over =
Mobile=20
IPv6 for Dual Stack nodes<BR>&gt; &gt; Author(s) : G. Tsirtsis, A. =
O'Neill, S.=20
Corson<BR>&gt; &gt; Filename : =
draft-tsirtsis-v4-over-mipv6-00.txt<BR>&gt; &gt;=20
Pages : 4<BR>&gt; &gt; Date : 21-Aug-00<BR>&gt; &gt; <BR>&gt; &gt; In =
this=20
document we show how IPv4 based communications can be<BR>&gt; &gt; =
supported by=20
a dual stack mobile node that only supports Mobile IPv6<BR>&gt; &gt; =
(MIPv6).=20
The aim is to use MIPv6 for mobility services while the<BR>&gt; &gt; =
Mobile can=20
still use its dual stack capabilities for IPv4<BR>&gt; &gt; =
communications=20
without the need for translation.<BR>&gt; &gt; <BR>&gt; &gt; A URL for =
this=20
Internet-Draft is:<BR>&gt; &gt; </FONT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-tsirtsis-v4-over-mipv6-=
00.txt"><FONT=20
face=3D"Courier New"=20
size=3D2>http://www.ietf.org/internet-drafts/draft-tsirtsis-v4-over-mipv6=
-00.txt</FONT></A><BR><FONT=20
face=3D"Courier New" size=3D2>&gt; &gt; <BR>&gt; &gt; Internet-Drafts =
are also=20
available by anonymous FTP. Login with the<BR>&gt; &gt; username<BR>&gt; =
&gt;=20
"anonymous" and a password of your e-mail address. After logging =
in,<BR>&gt;=20
&gt; type "cd internet-drafts" and then<BR>&gt; &gt; "get=20
draft-tsirtsis-v4-over-mipv6-00.txt".<BR>&gt; &gt; <BR>&gt; &gt; A list =
of=20
Internet-Drafts directories can be found in<BR>&gt; &gt; </FONT><A=20
href=3D"http://www.ietf.org/shadow.html"><FONT face=3D"Courier New"=20
size=3D2>http://www.ietf.org/shadow.html</FONT></A><FONT face=3D"Courier =
New"=20
size=3D2> <BR>&gt; &gt; or </FONT><A=20
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt"><FONT face=3D"Courier =
New"=20
size=3D2>ftp://ftp.ietf.org/ietf/1shadow-sites.txt</FONT></A><BR><FONT=20
face=3D"Courier New" size=3D2>&gt; &gt; <BR>&gt; &gt; <BR>&gt; &gt; =
Internet-Drafts=20
can also be obtained by e-mail.<BR>&gt; &gt; <BR>&gt; &gt; Send a =
message=20
to:<BR>&gt; &gt; </FONT><A href=3D"mailto:mailserv@ietf.org"><FONT=20
face=3D"Courier New" size=3D2>mailserv@ietf.org</FONT></A><FONT =
face=3D"Courier New"=20
size=3D2>.<BR>&gt; &gt; In the body type:<BR>&gt; &gt; "FILE=20
/internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt".<BR>&gt; &gt; =
<BR>&gt;=20
&gt; NOTE: The mail server at ietf.org can return the document =
in<BR>&gt; &gt;=20
MIME-encoded form by using the "mpack" utility.&nbsp; To use =
this<BR>&gt; &gt;=20
feature, insert the command "ENCODING mime" before the "FILE"<BR>&gt; =
&gt;=20
command.&nbsp; To decode the response(s), you will need "munpack" =
or<BR>&gt;=20
&gt; a MIME-compliant mail reader.&nbsp; Different MIME-compliant mail=20
readers<BR>&gt; &gt; exhibit different behavior, especially when dealing =

with<BR>&gt; &gt; "multipart" MIME messages (i.e. documents which have =
been=20
split<BR>&gt; &gt; up into multiple messages), so check your local =
documentation=20
on<BR>&gt; &gt; how to manipulate these messages.<BR>&gt; &gt; <BR>&gt; =
&gt;=20
<BR>&gt; &gt; Below is the data which will enable a MIME compliant mail=20
reader<BR>&gt; &gt; implementation to automatically retrieve the ASCII =
version=20
of the<BR>&gt; &gt; Internet-Draft.</FONT></BODY></HTML>

------=_NextPart_000_00B2_01C00DAE.B3910470--



From owner-ngtrans@sunroof.eng.sun.com  Thu Aug 24 05:14:09 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13281
	for <ngtrans-archive@odin.ietf.org>; Thu, 24 Aug 2000 05:14:08 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA16863;
	Thu, 24 Aug 2000 03:14:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id CAA07958;
	Thu, 24 Aug 2000 02:13:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7O9Cku15045
	for ngtrans-dist; Thu, 24 Aug 2000 02:12:46 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7O9B9615030;
	Thu, 24 Aug 2000 02:11:09 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id CAA28902;
	Thu, 24 Aug 2000 02:11:08 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA15777;
	Thu, 24 Aug 2000 03:11:06 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e7O9A8631245;
	Thu, 24 Aug 2000 11:10:09 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id LAA06808;
	Thu, 24 Aug 2000 11:10:08 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id LAA95355;
	Thu, 24 Aug 2000 11:10:34 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200008240910.LAA95355@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>
cc: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: Re: (ngtrans) Mobile IPv4/ Mobile IPv6 Interworking Issues 
In-reply-to: Your message of Thu, 24 Aug 2000 09:35:55 +0800.
             <00b501c00d6b$a5e7fd80$7d68608c@tsao> 
Date: Thu, 24 Aug 2000 11:10:34 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   The IPv4/IPv6 interworking problems seems to involve both Mobile IP and
   IPv4/IPv6 transition issues. We also have a draft which is relevant to
   this topic.

=> George's draft (draft-tsirtsis-v4-over-mipv6-00.txt) is very different,
he doesn't propose an integrated IPv4/IPv6 mobility but something very
simple (ie. trivial :-) based on two remarks:
 - new mobile phone infrastructures will be based on IPv6 (mainly because
   the lack of addresses in IPv4)
 - mobile phones will be dual stack hosts (because this is the safe way
   and this is not too expensive)
then a transition mechanism like DSTM which uses IPv4 over IPv6 tunnels
will be able to use freely/transparently all IPv6 devices like mobile IPv6
(I think George has EMA in mind but this applies too).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Thu Aug 24 06:03:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13712
	for <ngtrans-archive@odin.ietf.org>; Thu, 24 Aug 2000 06:03:42 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA04957;
	Thu, 24 Aug 2000 04:03:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA11327;
	Thu, 24 Aug 2000 03:03:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7OA2Bx15128
	for ngtrans-dist; Thu, 24 Aug 2000 03:02:11 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7OA24615121;
	Thu, 24 Aug 2000 03:02:04 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA11359;
	Thu, 24 Aug 2000 03:02:04 -0700 (PDT)
Received: from extmx.itri.org.tw (extmx.itri.org.tw [140.96.158.1])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA19187;
	Thu, 24 Aug 2000 03:01:31 -0700 (PDT)
Received: from nti.itri.org.tw (nti.itri.org.tw [140.96.157.2])
	by extmx.itri.org.tw (8.8.8/8.8.8) with ESMTP id SAA30997;
	Thu, 24 Aug 2000 18:04:00 +0800 (CST)
Received: from tsao (pc104125.ccl.itri.org.tw [140.96.104.125])
	by nti.itri.org.tw (8.8.8/8.8.8) with SMTP id SAA18067;
	Thu, 24 Aug 2000 18:01:38 +0800 (CST)
Message-ID: <009501c00db2$5aedfd60$7d68608c@tsao>
From: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
Cc: <ngtrans@sunroof.eng.sun.com>, <ipng@sunroof.eng.sun.com>
References: <200008240910.LAA95355@givry.rennes.enst-bretagne.fr>
Subject: Re: (ngtrans) Mobile IPv4/ Mobile IPv6 Interworking Issues 
Date: Thu, 24 Aug 2000 18:01:58 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0092_01C00DF5.659ADB50"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>

This is a multi-part message in MIME format.

------=_NextPart_000_0092_01C00DF5.659ADB50
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

Thanks for your comments.=20

Yes, George's draft is different from the Mobile IPv4/v6 Interworking =
proposal(draft-tsao-mobileip-duelstack-model-00.txt). However, these two =
drafts can be used to solve some of the mobility problems in IPv6/IPv4 =
interworking. That is why I pose the related draft on the mailing list.=20

Regards,
Shiao-Li


----- Original Message -----=20
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
To: "Shiao-Li Charles Tsao" <sltsao@ccl.itri.org.tw>
Cc: <ngtrans@sunroof.eng.sun.com>; <ipng@sunroof.eng.sun.com>
Sent: Thursday, August 24, 2000 5:10 PM
Subject: Re: (ngtrans) Mobile IPv4/ Mobile IPv6 Interworking Issues=20


> In your previous mail you wrote:
>=20
>    The IPv4/IPv6 interworking problems seems to involve both Mobile IP =
and
>    IPv4/IPv6 transition issues. We also have a draft which is relevant =
to
>    this topic.
>=20
> =3D> George's draft (draft-tsirtsis-v4-over-mipv6-00.txt) is very =
different,
> he doesn't propose an integrated IPv4/IPv6 mobility but something very
> simple (ie. trivial :-) based on two remarks:
>  - new mobile phone infrastructures will be based on IPv6 (mainly =
because
>    the lack of addresses in IPv4)
>  - mobile phones will be dual stack hosts (because this is the safe =
way
>    and this is not too expensive)
> then a transition mechanism like DSTM which uses IPv4 over IPv6 =
tunnels
> will be able to use freely/transparently all IPv6 devices like mobile =
IPv6
> (I think George has EMA in mind but this applies too).
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr

------=_NextPart_000_0092_01C00DF5.659ADB50
Content-Type: text/html;
	charset="big5"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dbig5" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Courier New" size=3D2>Thanks for your comments. =
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Yes, George's draft =
is&nbsp;different from=20
the Mobile IPv4/v6 Interworking=20
proposal(draft-tsao-mobileip-duelstack-model-00.txt). However, these two =
drafts=20
can be used to solve&nbsp;some of the mobility problems in IPv6/IPv4=20
interworking.&nbsp;That is why I pose the related draft on the mailing =
list.=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Shiao-Li</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3D"Courier New" size=3D2>----- Original Message ----- =
</FONT>
<DIV><FONT face=3D"Courier New" size=3D2>From: "Francis Dupont" =
&lt;</FONT><A=20
href=3D"mailto:Francis.Dupont@enst-bretagne.fr"><FONT face=3D"Courier =
New"=20
size=3D2>Francis.Dupont@enst-bretagne.fr</FONT></A><FONT face=3D"Courier =
New"=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>To: "Shiao-Li Charles Tsao" =
&lt;</FONT><A=20
href=3D"mailto:sltsao@ccl.itri.org.tw"><FONT face=3D"Courier New"=20
size=3D2>sltsao@ccl.itri.org.tw</FONT></A><FONT face=3D"Courier New"=20
size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Cc: &lt;</FONT><A=20
href=3D"mailto:ngtrans@sunroof.eng.sun.com"><FONT face=3D"Courier New"=20
size=3D2>ngtrans@sunroof.eng.sun.com</FONT></A><FONT face=3D"Courier =
New"=20
size=3D2>&gt;; &lt;</FONT><A =
href=3D"mailto:ipng@sunroof.eng.sun.com"><FONT=20
face=3D"Courier New" size=3D2>ipng@sunroof.eng.sun.com</FONT></A><FONT=20
face=3D"Courier New" size=3D2>&gt;</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Sent: Thursday, August 24, 2000 =
5:10=20
PM</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Subject: Re: (ngtrans) Mobile =
IPv4/ Mobile=20
IPv6 Interworking Issues </FONT></DIV></DIV>
<DIV><BR></DIV><FONT face=3D"Courier New" size=3D2>&gt; In your previous =
mail you=20
wrote:<BR>&gt; <BR>&gt; &nbsp;&nbsp; The IPv4/IPv6 interworking problems =
seems=20
to involve both Mobile IP and<BR>&gt; &nbsp;&nbsp; IPv4/IPv6 transition =
issues.=20
We also have a draft which is relevant to<BR>&gt; &nbsp;&nbsp; this=20
topic.<BR>&gt; <BR>&gt; =3D&gt; George's draft=20
(draft-tsirtsis-v4-over-mipv6-00.txt) is very different,<BR>&gt; he =
doesn't=20
propose an integrated IPv4/IPv6 mobility but something very<BR>&gt; =
simple (ie.=20
trivial :-) based on two remarks:<BR>&gt; &nbsp;- new mobile phone=20
infrastructures will be based on IPv6 (mainly because<BR>&gt; =
&nbsp;&nbsp; the=20
lack of addresses in IPv4)<BR>&gt; &nbsp;- mobile phones will be dual =
stack=20
hosts (because this is the safe way<BR>&gt; &nbsp;&nbsp; and this is not =
too=20
expensive)<BR>&gt; then a transition mechanism like DSTM which uses IPv4 =
over=20
IPv6 tunnels<BR>&gt; will be able to use freely/transparently all IPv6 =
devices=20
like mobile IPv6<BR>&gt; (I think George has EMA in mind but this =
applies=20
too).<BR>&gt; <BR>&gt; Regards<BR>&gt; <BR>&gt; </FONT><A=20
href=3D"mailto:Francis.Dupont@enst-bretagne.fr"><FONT face=3D"Courier =
New"=20
size=3D2>Francis.Dupont@enst-bretagne.fr</FONT></A></BODY></HTML>

------=_NextPart_000_0092_01C00DF5.659ADB50--



From owner-ngtrans@sunroof.eng.sun.com  Thu Aug 24 20:26:44 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25726
	for <ngtrans-archive@odin.ietf.org>; Thu, 24 Aug 2000 20:26:44 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA00318;
	Thu, 24 Aug 2000 18:26:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA06146;
	Thu, 24 Aug 2000 17:26:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7P0P2v15642
	for ngtrans-dist; Thu, 24 Aug 2000 17:25:02 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7P0Os615635
	for <ngtrans@sunroof.eng.sun.com>; Thu, 24 Aug 2000 17:24:55 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA23987
	for <ngtrans@sunroof.eng.sun.com>; Thu, 24 Aug 2000 17:24:54 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA24969
	for <ngtrans@sunroof.eng.sun.com>; Thu, 24 Aug 2000 17:24:53 -0700 (PDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Thu, 24 Aug 2000 17:14:32 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 24 Aug 2000 15:59:13 -0700 (Pacific Daylight Time)
Received: from speak.platinum.corp.microsoft.com ([172.30.236.197]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Thu, 24 Aug 2000 15:59:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C00E1D.935E74C0"
Subject: RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Date: Thu, 24 Aug 2000 15:49:35 -0700
Message-ID: <CC2E64D4B3BAB646A87B5A3AE97090420CC76B87@speak.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
Thread-Index: AcAG8tMkH9ql3+7+T9mkBRbZFj+u+QHKM8rg
From: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>,
        "Brian E Carpenter" <brian@hursley.ibm.com>,
        "Scott Bradner" <sob@harvard.edu>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 24 Aug 2000 22:59:05.0300 (UTC) FILETIME=[E6F50940:01C00E1E]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Tony Hain" <tonyhain@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C00E1D.935E74C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dave's understanding is correct, in this version of the draft the only
place that routing tables grow is the site gateway that is keeping track
of the prefix/relay mappings. My guess about the IESG concern is that
there will always be those that want to optimize their entry point onto
the link (existing IPv4 infrastructure) based on some policy. While the
native IPv6 network is relatively flat, the nearest 2002::/16 prefix
announcement is likely to fill most policy concerns. When there is
hierarchy in the native IPv6 space, it will be less clear which path to
2002::/16 fits the policy in both the IPv6 space and across the IPv4
based link, or if it will even be possible to align those policies.
Neither document deals with this problem, but since it is a scale issue
(native space growth), it would make more sense to add it to mine with
notes in the base doc that these are concerns. We really do need to get
the base doc out the door.=20
=20
Tony
=20
-----Original Message-----
From: Dave Thaler=20
Sent: Tuesday, August 15, 2000 12:39 PM
To: Brian E Carpenter; Scott Bradner
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt



Brian Carpenter writes:=20
> Scott Bradner wrote:=20
> >   This mechanism has significant scaling issues=20
> particularly in regards to=20
> >   the growth of the routing table. =20
>=20
> But this is not really the case. Basic 6to4 adds one entry,=20
> 2002::/16, to the=20
> native IPv6 routing table. There are scaling issues for=20
> massive numbers of tiny=20
> sites- covered by Tony's draft - and I do need to add a=20
> statement that the base=20
> document does not cover that situation. (Tony's draft wasn't out when=20
> this -06 draft was done.) So I agree that scaling should be=20
> mentioned but the=20
> words will be a bit different.=20

Right, even with Tony's draft, no additional prefixes are injected=20
into the v6 infrastructure.  The v6 infrastructure has exactly=20
one additional prefix (2002::/16).=20

With Tony's draft (if I understand it correctly), the 6to4=20
*site* adds additional prefixes to the internal tables on=20
the 6to4 site gateway router (and doesn't advertise them).=20
In the worst case, the number of prefixes on a site router=20
will be the number of prefixes in the v6 infrastructure=20
that are known to relays.=20

Tony's draft can say this, but I don't see any scaling=20
problems with the base 6to4 draft.=20

-Dave=20


------_=_NextPart_001_01C00E1D.935E74C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>RE: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt</TITLE>

<META content=3D"MSHTML 5.60.2257.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D679413522-24082000><FONT face=3DArial color=3D#0000ff =
size=3D2>Dave's=20
understanding is correct, in this version of the draft the only place =
that=20
routing tables grow is the site gateway that is keeping track of the=20
prefix/relay mappings. My guess about the IESG concern is that there =
will always=20
be those that want to optimize their entry point onto the link=20
(existing&nbsp;IPv4 infrastructure)&nbsp;based on some policy. While the =
native=20
IPv6 network is relatively flat, the nearest 2002::/16 prefix =
announcement is=20
likely to fill most policy concerns. When there is hierarchy in the=20
native&nbsp;IPv6 space, it will be less clear which path to 2002::/16 =
fits the=20
policy in both the IPv6 space and across the IPv4 based link, or if it =
will even=20
be possible to align those policies. Neither document deals with this =
problem,=20
but since it is a scale issue (native space growth), it would make more =
sense to=20
add it to mine with notes in the base doc that these are concerns. We =
really do=20
need to get the base doc out the door. </FONT></SPAN></DIV>
<DIV><SPAN class=3D679413522-24082000><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D679413522-24082000><FONT face=3DArial color=3D#0000ff =

size=3D2>Tony</FONT></SPAN></DIV>
<DIV><SPAN class=3D679413522-24082000><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Dave Thaler =
<BR><B>Sent:</B>=20
Tuesday, August 15, 2000 12:39 PM<BR><B>To:</B> Brian E Carpenter; Scott =

Bradner<BR><B>Cc:</B> ngtrans@sunroof.eng.sun.com<BR><B>Subject:</B> RE: =

(ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt<BR><BR></FONT></DIV><!-- =
Converted from text/plain format -->
<P><FONT size=3D2>Brian Carpenter writes:</FONT> <BR><FONT size=3D2>&gt; =
Scott=20
Bradner wrote:</FONT> <BR><FONT size=3D2>&gt; &gt;&nbsp;&nbsp; This =
mechanism has=20
significant scaling issues </FONT><BR><FONT size=3D2>&gt; particularly =
in regards=20
to</FONT> <BR><FONT size=3D2>&gt; &gt;&nbsp;&nbsp; the growth of the =
routing=20
table.&nbsp; </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt; But this=20
is not really the case. Basic 6to4 adds one entry, </FONT><BR><FONT =
size=3D2>&gt;=20
2002::/16, to the </FONT><BR><FONT size=3D2>&gt; native IPv6 routing =
table. There=20
are scaling issues for </FONT><BR><FONT size=3D2>&gt; massive numbers of =
tiny=20
</FONT><BR><FONT size=3D2>&gt; sites- covered by Tony's draft - and I do =
need to=20
add a </FONT><BR><FONT size=3D2>&gt; statement that the base</FONT> =
<BR><FONT=20
size=3D2>&gt; document does not cover that situation. (Tony's draft =
wasn't out=20
when</FONT> <BR><FONT size=3D2>&gt; this -06 draft was done.) So I agree =
that=20
scaling should be </FONT><BR><FONT size=3D2>&gt; mentioned but =
the</FONT>=20
<BR><FONT size=3D2>&gt; words will be a bit different.</FONT> </P>
<P><FONT size=3D2>Right, even with Tony's draft, no additional prefixes =
are=20
injected</FONT> <BR><FONT size=3D2>into the v6 infrastructure.&nbsp; The =
v6=20
infrastructure has exactly</FONT> <BR><FONT size=3D2>one additional =
prefix=20
(2002::/16).</FONT> </P>
<P><FONT size=3D2>With Tony's draft (if I understand it correctly), the =
6to4=20
</FONT><BR><FONT size=3D2>*site* adds additional prefixes to the =
internal tables=20
on </FONT><BR><FONT size=3D2>the 6to4 site gateway router (and doesn't =
advertise=20
them).</FONT> <BR><FONT size=3D2>In the worst case, the number of =
prefixes on a=20
site router </FONT><BR><FONT size=3D2>will be the number of prefixes in =
the v6=20
infrastructure </FONT><BR><FONT size=3D2>that are known to =
relays.</FONT> </P>
<P><FONT size=3D2>Tony's draft can say this, but I don't see any =
scaling</FONT>=20
<BR><FONT size=3D2>problems with the base 6to4 draft.</FONT> </P>
<P><FONT size=3D2>-Dave</FONT> </P></BODY></HTML>

------_=_NextPart_001_01C00E1D.935E74C0--


From owner-ngtrans@sunroof.eng.sun.com  Fri Aug 25 16:08:55 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28446
	for <ngtrans-archive@odin.ietf.org>; Fri, 25 Aug 2000 16:08:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA15075;
	Fri, 25 Aug 2000 14:08:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA02020;
	Fri, 25 Aug 2000 13:08:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7PK1RN16331
	for ngtrans-dist; Fri, 25 Aug 2000 13:01:27 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7PK1K616323
	for <ngtrans@sunroof.eng.sun.com>; Fri, 25 Aug 2000 13:01:20 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA28537
	for <ngtrans@sunroof.eng.sun.com>; Fri, 25 Aug 2000 13:01:18 -0700 (PDT)
Received: from mail-gw2.hursley.ibm.com (mail-gw2.hursley.ibm.com [194.196.110.19])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA11121
	for <ngtrans@sunroof.eng.sun.com>; Fri, 25 Aug 2000 14:01:17 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21])
	by mail-gw2.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id VAA29182;
	Fri, 25 Aug 2000 21:00:07 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id VAA25236; Fri, 25 Aug 2000 21:01:05 +0100 (BST)
Message-ID: <39A6CEB5.76386DD5@hursley.ibm.com>
Date: Fri, 25 Aug 2000 14:53:25 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-6to4-06.txt
References: <E13Mx9F-0006Mw-00@rip.psg.com>
		<4.3.2.7.2.20000812215109.0324df10@mail.viagenie.qc.ca> <E13NneT-000IKp-00@rip.psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Randy Bush wrote: (in response to Marc Blanchet)

> > An applicability statement saying that "this doesn't scale for the full
> > internet and that other mechanisms must be deployed to replace 6to4 in the
> > event of routing table explosion", seems to me the only real thing that we
> > can add.
> 
> if we intend this to be a proposed standard, it might help if we were more
> specific about what the scaling issues are, how they can be anticipated, and
> what might be done to ameliorate, bypass, or replace them.
> 

The trouble is that 6to4 doesn't have any such scaling issues. It creates
exactly one routing native IPv6 routing entry and relay routers scale just as
well as any other tunnel end point or transit router solution. There's a specific
scaling issue in the scenario covered by Tony's draft, but that's out of scope
for the base document. The tweaks I am putting in this afternoon will
hopefully make this clearer.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 28 00:50:28 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17354
	for <ngtrans-archive@odin.ietf.org>; Mon, 28 Aug 2000 00:50:27 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id WAA09013;
	Sun, 27 Aug 2000 22:50:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id VAA07480;
	Sun, 27 Aug 2000 21:49:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7S4mal19849
	for ngtrans-dist; Sun, 27 Aug 2000 21:48:36 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7S4mT619842;
	Sun, 27 Aug 2000 21:48:29 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id VAA02981;
	Sun, 27 Aug 2000 21:48:27 -0700 (PDT)
Received: from ups.cisco.com (ups.cisco.com [171.69.18.21])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id WAA08542;
	Sun, 27 Aug 2000 22:48:27 -0600 (MDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188])
	by ups.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id VAA20344;
	Sun, 27 Aug 2000 21:48:26 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@ups
Message-Id: <v04220802b5cf984ad6c0@[10.19.130.188]>
Date: Sun, 27 Aug 2000 21:48:34 -0700
To: ipng@sunroof.eng.sun.com
From: Steve Deering <deering@cisco.com>
Subject: (ngtrans) IPv6 address allocation comments
Cc: Bob Hinden <hinden@iprg.nokia.com>, ngtrans@sunroof.eng.sun.com
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

Dear IPng Working Group,

The following text was generated by the IPv6 Directorate, IAB, and IESG
as comments on the draft IPv6 address allocation policy developed by the
Regional Internet Registries (RIRs).  Though it is not a product of the
IPng working group, we (the IPng chairs) believe that it is consistent
with the (rough) consensus position of the working group, based on
previous discussions on the ipngwg mailing list, and we wanted to give
the working group a chance to look at it before it goes to the RIRs.
The RIRs will be holding policy meetings starting in mid-September and
the plan is to send these comments to the RIRs on September 1st to give
them time to review it before their meetings, so if you'd like to provide
further input to the text, please do so before Friday of this week.

Steve Deering / Bob Hinden

---------

Comments on IPv6 address allocation guidelines
----------------------------------------------

 -DRAFT--DRAFT---DRAFT----DRAFT-----DRAFT 6 of August 25, 2000
 

During a discussion between IETF and RIR experts at the Adelaide IETF,
a suggestion was made that it might be appropriate to allocate /56 prefixes
instead of /48 for homes and small businesses. However, subsequent
analysis has revealed significant advantages in using /48 uniformly. 
This note is an update following further discussions at the Pittsburgh 
IETF.

By way of preamble, note that IPv6 partitions address space into public
topology and site topology, and the expectation is that the RIRs will 
only need to manage the public topology. However, they may need to
provide guidance and to ensure fairness of address distribution.

Also note that it is widely expected that all IPv6 subscribers,
whether domestic (homes), mobile (vehicles or individuals), or 
enterprises of any size, will eventually possess multiple always-on 
hosts, at least one subnet with the potential for additional
subnetting, and therefore some internal routing capability. 
Note that in the mobile environment, the device connecting
a mobile site to the network may in fact be a third generation
cellular telephone. In other words the subscriber allocation unit 
is not always a host; it is always potentially a site.

This then sets the scene for proposing a fixed boundary
at /48 for all subscribers except the very largest. First we
give the arguments for such a guideline, and then we demonstrate
that it is entirely compatible with responsible stewardship
of the total IPv6 address space. Finally a technical annex
goes into some important details.

The arguments for such a fixed boundary are:

 - only by having an ISP-independent boundary can we guarantee 
   that a change of ISP will not require a costly internal
   restructuring or consolidation of subnets.

 - to enable straightforward site renumbering, i.e. when a site
   renumbers from one prefix to another, the whole process,
   including parallel running of the two prefixes, would be
   greatly complicated if the prefixes had different lengths
   (depending of course on the size and complexity of the site).

 - there are various possible approaches to multihoming for IPv6 sites,
   in addition to the techniques already used for IPv4 multihoming.
   More work remains to be done in this area, but it seems likely that 
   several approaches will be deployed in practice, each with their 
   own advantages and disadvantages. Some (but not all) will work
   better with a fixed prefix boundary. The technical annex
   discusses multihoming in more detail.
     
 - to allow easy growth of the subscribers' networks -- no need
   to keep going back to ISPs for more space (except for that
   relatively small number of subscribers for which a /48 is
   not enough).

 - to get the ISPs and registries out of the business of judging 
   sites' needs for address space, unless the site requests more 
   space than a /48, with several advantages:

   - ISPs no longer need to ask for details of their customers' 
     network architecture and growth plans
   - ISPs and registries no longer have to judge rates of address
     consumption by customer type
   - registry operations will be made more efficient by reducing
     the need for evaluations and judgements
   - address space will no longer be a precious resource for customers,
     removing the major incentive for subscribers to install v6/v6 NATs, 
     which would defeat the ability of IPv6 to restore address transparency.

 - to allow the site to maintain a single reverse-DNS zone covering
   all prefixes.

   - If and only if a site can use the same subnetting structure
     under each of its prefixes, then it can use the same zone file
     for the address-to-name mapping of all of them.  And, using the
     conventions of RFC 2874, it can roll the reverse mapping data
     into the "forward" (name-keyed) zone.

Specific advantages of the fixed boundary being at /48 include

 - to leave open the technical option of retro-fitting the GSE
   (Global, Site and End-System Designator, a.k.a "8+8")
   proposal for separating locators and identifiers, which assumes
   a fixed boundary between global and site addressing at /48. 
   Although the GSE technique was deferred a couple of years ago,
   it still has strong proponents.  Also, the IRTF Namespace 
   Research Group is actively looking into topics closely related 
   to GSE.  It is still possible that GSE or a derivative of GSE 
   will be used with IPv6 in the future.

 - since the site local prefix is fec0::/48, global site prefixes
   of /48 will allow sites to easily maintain a simple 1 to 1 
   mapping between the global topology and the site local topology 
   in the SLA field.

 - similarly, if the 6to4 proposal is standardized, migration from
   a 6to4 prefix, which is /48 by construction, to a native IPv6 prefix 
   will be simplified if the native prefix is /48

 - existing running code and products conforming to existing RFCs

Note that none of these reasons imply an expectation that
homes, vehicles, etc. will intrinsically require 16 bits of 
subnet space.

The question naturally arises whether giving a /48 to every
subscriber represents a profligate waste of address space.
Objective analysis shows that this is not the case. A /48
prefix under the Aggregatable Global Unicast Address (TLA) 
format prefix actually contains 45 variable
bits, i.e. the number of available prefixes is 2**45
or about 35 trillion (35,184,372,088,832). If we take the
limiting case of assigning one prefix per human, then the 
utilization of the TLA space appears to be limited to 
approximately 0.03% on reasonable assumptions. 

More precisely,

 - RFC 1715 defines an "H ratio" based on experience in
   address space assignment in various networks. Applied
   to a 45 bit address space, and projecting a world
   population of 10.7 billion by 2050 (see
   http://www.popin.org/pop1998/ ), the required
   assignment efficiency is log_10(1.07*10^10) / 45 = 0.22.  
   This is less than the efficiencies of telephone numbers and 
   DECnetIV or IPv4 addresses shown in RFC 1715, i.e. gives
   no grounds for concern.

 - We are highly confident in the validity of this analysis,
   based on experience with IPv4 and several other address spaces,
   and on extremely ambitious scaling goals for the Internet
   amounting to an 80 bit address space *per person*. Even so,
   being acutely aware of the history of under-estimating demand,
   we have reserved more than 85% of the address space (i.e. the
   bulk of the space not under the Aggregatable Global Unicast 
   Address (TLA) format prefix).   
   Therefore, if the analysis does one day turn out to be wrong, 
   our successors will still have the option of imposing much more 
   restrictive allocation policies on the remaining 85%.

 - It has been suggested that even if the above analysis is valid
   for terrestrial and near-Earth networks, it may fail for
   interplanetary networking and beyond. This is conceivable, but 
   the challenges in dealing with packet transit times of many minutes
   or more, and with such remote deployment, are such as to turn 
   addressing into a side issue.

 - For transient use by non-routing hosts (e.g., temporary addresses 
   acquired and released while passing through wireless cells, and 
   for stand-alone dial-up users who prefer transient addresses for 
   privacy reasons), a prefix longer than /48 would be OK. But a
   subscriber who wants "static" IPv6 address space ought
   to be allocated a /48 for the reasons given above.

Final comments:

We argue that although careful stewardship of IPv6 address space
is essential, this is completely compatible with the convenience
and simplicity of a uniform prefix size for IPv6 sites of any size.
The numbers are such that there seems to be no objective risk
of running out of space, giving an unfair amount of space to
early customers, or of getting back into the over-constrained
IPv4 situation where address conservation and route aggregation
damage each other.

----

Technical Annex

The technical principles that apply to address allocation seek to balance 
healthy conservation practices and wisdom with a certain ease of access. On 
one hand, with any resource, one wants to spend wisely; the housewife in 
the bazaar doesn't spend more than she needs to for a purchase even if her 
purse is unlimited. On the other hand, the IPv6 address space is in no sense 
as precious a resource as the IPv4 address space, and unwarranted 
conservatism acts as a disincentive in a marketplace already dampened by 
other factors. So from a market development perspective, we would like to 
see it be very easy for a user or an ISP to obtain as many IPv6 addresses as 
she really needs without a prospect of immediate renumbering or of scaling 
inefficiencies.

The IETF makes no comment on business issues or relationships. However, in 
general, we observe that technical delegation policy can have strong 
business impacts. For example, early versions of the IPv6 addressing 
architecture proposed that the 50-60 dominant IPv4 ISPs (as demonstrated in 
http://www.caida.org/analysis/topology/as_core_network/AS_Network.xml and 
http://www.telstra.net/ops/bgptable.html) be given sweeping allocations, 
and permitted to redelegate subsets of them to their downstream peers. This 
would have the technical effect of biasing routing of traffic between those 
lesser ISPs through their upstream neighbors. To avoid that, the lesser 
ISPs would be forced to arrange special-case punch-through agreements with 
their other peers, as they do now in the IPv4 world. This would tend to 
lock in existing Tier 1 and Tier 2 operators indefinitely. In 
addition, technically, routing would suffer; it is desirable for every ISP's 
traffic to be routed by the best available path consistent with policy, and 
to be resilient to temporary outages, rather than seeing traffic to be 
biased through a few operators for potentially historic reasons. One would 
like to achieve this as a natural result rather than having to consciously 
counteract the aggregation of addresses. So a strong requirement of the 
address delegation plan is that it not be predicated on or unduly bias 
business relationships or models.

The IPv6 address, as currently defined, consists of 64 bits of "network 
number" and 64 bits of "host number". The technical reasons for this are 
several. The requirements for IPv6 agreed to in 1993 included a plan to be 
able to address approximately 2^40 networks and 2^50 hosts; the 64/64 split 
effectively accomplishes this. Procedures used in host address assignment, 
such as the router advertisement of a network's prefix to hosts, which in 
turn place a locally unique number in the host portion, depend on this 
split. Examples of obvious choices of host number (IEEE Mac Address, E.164 
number, E.214 IMSI, etc) suggest that no assumption should be made that 
bits may be stolen from that range for subnet numbering; current generation 
MAC layers and E.164 numbers specify up to 64 bit objects. Therefore, subnet 
numbers must be assumed to come from the network part. This is not to 
preclude routing protocols such as IS-IS level 1 (intra-area) routing, 
which routes individual host addresses, but says that it may not be 
depended upon in the world outside that zone.

The IETF has also gone to a great deal of effort to minimize the impacts of 
network renumbering. None-the-less, renumbering of IPv6 networks is neither 
invisible nor completely painless. Therefore, renumbering should be 
considered an acceptable event, but to be avoided if reasonably avoidable.


The IETF's IPNG working group has recommended that the address block given 
to a single edge network which may be recursively subnetted be a 48 bit 
prefix. This gives each such network 2^16 subnet numbers to use in routing, 
and a very large number of unique host numbers within each network. This is 
deemed to be large enough for most enterprises, and to leave plenty of room 
for delegation of address blocks to aggregating entities.

It is not obvious, however, that all edge networks are likely to be 
recursively subnetted; an individual PC in a home, or a single cell in a 
mobile telephone network, for example, may or may not be further 
subnetted (depending whether they are acting as gateways to personal, 
home, or vehicular networks). When a network number is delegated to a place 
which will not require subnetting, therefore, wisdom suggests that it be given 
a single 64 bit prefix - perhaps shared among the dial-in connections to the 
same ISP router. It is suggested that business practices therefore consider 
whether the edge network is or is not likely to be recursively subnetted, 
and allocate /48 or /64 prefixes accordingly. However this decision may be 
taken in the knowledge that there is objectively no shortage of /48s,
and the expectation that personal, home and vehicle networks will
become the norm.


The RIR communities, with the IAB, have determined that reasonable address 
prefixes delegated to service providers should be on the order of 29 to 35 
bits in length, giving individual delegations support for 2^13 (8K) to 2^19 
(512K) subscriber networks. Allocations are to be given in a manner such 
that an initial prefix may be subsumed by subsequent larger allocations 
without forcing existing subscriber networks to renumber. We concur that 
this meets the technical requirement for manageable and scalable backbone 
routing while simultaneously allowing for managed growth of individual 
delegations.

The same type of rule could be used in the allocation of addresses in edge 
networks; if there is doubt whether an edge network will in turn be 
subnetted, the edge network might be encouraged to allocate the first 64 
bit prefix out of a block of 8..256, preserving room for growth of that 
allocation without renumbering up to a point.


In the realm of multi-homed networks, the techniques used in IPv4 can all 
be applied, but they have known scaling problems. Specifically,
if the same prefix is advertised by multiple ISPs, the routing tables
will grow as a function of the number of multihomed sites. To go beyond this
for IPv6, we only have initial proposals on the table at this time,
and active work is under way in the IETF IPNGWG working group. 

Key characteristics of a definitive multi-homing proposal 
include (at minimum) that it provides routing connectivity to any 
multi-homed network globally, conserves address space, produces high 
quality routes at least as well as the single-homed host case previously 
discussed via any of the network's providers, enables a multi-homed network 
to connect to multiple ISPs, does not inherently bias routing to use any 
proper subset of those networks, does not unduly damage route
aggregation, and scales to very large numbers of multi-homed networks.

One class of solution being considered amounts to permanent parallel running 
of two (or more) prefixes per site.  In the absence of a fixed prefix boundary, 
such a site might be required to have multiple different internal 
subnet numbering strategies, (one for each prefix length) or, if it 
only wanted one, be forced to use the most restrictive one as defined by 
the longest prefix it received from any of its ISPs. 
In this approach, a multi-homed network would have an address 
block from each of its upstream providers. Each host would either
have exactly one address picked from the set of upstream 
providers, or one address per host from each of the upstream providers.
The first case is essentially a variant on RFC 2260, with known scaling
limits.

In the second case (multiple addresses per host), if two multi-homed networks 
communicate, having respectively m and n upstream providers, then the one 
initiating the connection will select one address pair from the n*m 
potential address pairs to connect from and to, and in so doing will select 
the providers, and therefore the applicable route, for the life of the 
connection. Given that each path will have a different ambient bit rate, 
loss rate, and delay, if neither host is in possession of any routing 
or metric information, the initiating host has only a 1/(m*n) probability 
of selecting the optimal address pair. Work on better-than-random address
selection is in progress in the IETF, but is incomplete. In addition, use 
of a singly-announced address for a long-lived session exposes that session to 
being broken by routing outages, near the source and elsewhere in the 
network. This approach also tends to encourage ASPs who offer a 
service of bypassing end-to-end IP routing to improve user response times, 
often known as "content-based routing".

An existence proof exists in the existing IPv4 Internet that a network whose 
address is distinct from and globally advertised to all upstream providers 
permits the routing network to select the optimal path within the 
applicable policy. Present-day routing policies are not QoS policies but 
reachability policies, which means that they will not necessarily select 
the optimal delay, bit rate, or loss rate, but the route will be the best 
within the metrics that are indeed in use. One may therefore conclude that 
this would work correctly for IPv6 networks as well, apart from scaling issues.

It would be useful to study a more scalable version of the latter approach for
IPv6. One interim option is to allocate 29-35 bit prefixes regionally, and 
allocate /48 prefixes out of them to multi-homed networks they contain or 
touch. Within the region, each such /48 is globally advertised. Outside the 
region, the /29-/35 bit prefix may be advertised, to improve aggregation and 
scaling. A multi-homed network which spans multiple regions may use an address 
block from each region, and internally advertise its addresses to stop the edge 
network from inappropriately using external connectivity for internal 
traffic. In this context, the word "region" is intentionally vague but
relates more to network topology than to geography. The GSE proposal also
tackled multihoming somewhat in this way.

---------


From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 28 15:29:12 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18970
	for <ngtrans-archive@odin.ietf.org>; Mon, 28 Aug 2000 15:29:10 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA07348;
	Mon, 28 Aug 2000 13:29:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA24634;
	Mon, 28 Aug 2000 12:28:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7SJRlI20526
	for ngtrans-dist; Mon, 28 Aug 2000 12:27:47 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7SJQ2620511;
	Mon, 28 Aug 2000 12:26:02 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA22256;
	Mon, 28 Aug 2000 12:26:01 -0700 (PDT)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA27783;
	Mon, 28 Aug 2000 12:26:01 -0700 (PDT)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 80CB42259; Mon, 28 Aug 2000 15:26:00 -0400 (EDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id 5598A23B0; Mon, 28 Aug 2000 15:26:00 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id PAA0001030265; Mon, 28 Aug 2000 15:24:24 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008281924.PAA0001030265@anw.zk3.dec.com>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        dhcp-v6@bucknell.edu, members@ipv6forum.com, tech@ipv6forum.com
Cc: reinhard.scholl@etsi.fr
Subject: (ngtrans) UPDATE: IPv6 ETSI Test Event Web Page Pointer
Date: Mon, 28 Aug 2000 15:24:23 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

  ** PLEASE DO NOT RESPOND TO THIS MAIL **

Folks,

Just wanted to add that the test/interoperability suites that will be
done for the attached will include test suites from Ericsson provided to
Francis Dupont and his team.  It will not just be a last minute effort for 
testing but a well thought out group of test assertions and procedures.  

Thank You Ericsson for your assistance on this IPv6 implementation
effort.

thanks
/jim

--------------------------------

Hi Folks,

Even though UNH cannot participate in this test event our colleagues
under the guidance of Francis Dupont at ENST in France have come to the
aid of IPv6 developers (thank you ENST and Francis) and working with
Reihhard Scholl there will be an IPv6 test event Oct 2-6.

I believe this is a very important event and vendors should really try
to attend.  Plus it is in a nice place "French Riviera" not that there
won't be a lot of hard work done of course.  This is serious stuff folks
and 3GPP needs our support and this test event.  Please see the
following URL:

http://www.etsi.org/bake-off

regards and thanks for your support,
/jim




From owner-ngtrans@sunroof.eng.sun.com  Mon Aug 28 23:14:13 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26029
	for <ngtrans-archive@odin.ietf.org>; Mon, 28 Aug 2000 23:14:12 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA23078;
	Mon, 28 Aug 2000 21:14:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA29499;
	Mon, 28 Aug 2000 20:13:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7T3D4f20853
	for ngtrans-dist; Mon, 28 Aug 2000 20:13:04 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7T3BC620838;
	Mon, 28 Aug 2000 20:11:13 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA27494;
	Mon, 28 Aug 2000 20:11:13 -0700 (PDT)
Received: from ztxmail01.ztx.compaq.com (ztxmail01.ztx.compaq.com [161.114.1.205])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA07149;
	Mon, 28 Aug 2000 20:11:12 -0700 (PDT)
Received: by ztxmail01.ztx.compaq.com (Postfix, from userid 12345)
	id B971D2FBF; Mon, 28 Aug 2000 22:11:11 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail01.ztx.compaq.com (Postfix) with ESMTP
	id 07D602FA6; Mon, 28 Aug 2000 22:11:11 -0500 (CDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id XAA0000588078; Mon, 28 Aug 2000 23:11:08 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008290311.XAA0000588078@anw.zk3.dec.com>
To: Steve Deering <deering@cisco.com>
Cc: ipng@sunroof.eng.sun.com, Bob Hinden <hinden@iprg.nokia.com>,
        ngtrans@sunroof.eng.sun.com, bound@zk3.dec.com
Subject: Re: (ngtrans) IPv6 address allocation comments 
In-reply-to: Your message of "Sun, 27 Aug 2000 21:48:34 PDT."
             <v04220802b5cf984ad6c0@[10.19.130.188]> 
Date: Mon, 28 Aug 2000 23:11:07 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Excellent work and every word of it.  I can't see how anyone can argue
against it but I bet someone will.  Nice IPv6 document too.

p.s. One Nit - I have noticed the word "she" in the text please make all
references to be gender-neutral.  In the seventies and eighties we fixed
at least in this profession the reference to ownership or pronounns
from he, his, or him to gender-neutral statements.  Likewise I don't
want to see "she" or "her" please make this document gender-neutral.

regards,
/jim 




From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 29 11:36:36 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22505
	for <ngtrans-archive@odin.ietf.org>; Tue, 29 Aug 2000 11:36:31 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA02975;
	Tue, 29 Aug 2000 09:36:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA23151;
	Tue, 29 Aug 2000 08:33:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7TFWn421254
	for ngtrans-dist; Tue, 29 Aug 2000 08:32:49 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7TFWg621247
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 08:32:42 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA29034
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 08:32:42 -0700 (PDT)
Received: from ztxmail02.ztx.compaq.com (ztxmail02.ztx.compaq.com [161.114.1.206])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA00518
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 08:32:41 -0700 (PDT)
Received: by ztxmail02.ztx.compaq.com (Postfix, from userid 12345)
	id D821C119E; Tue, 29 Aug 2000 10:32:29 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail02.ztx.compaq.com (Postfix) with ESMTP
	id 2616F11DB; Tue, 29 Aug 2000 10:32:29 -0500 (CDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id LAA0000603932; Tue, 29 Aug 2000 11:32:11 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008291532.LAA0000603932@anw.zk3.dec.com>
To: george.tsirtsis@bt.com
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) 6to4 and dstm 
In-reply-to: Your message of "Wed, 23 Aug 2000 15:11:19 BST."
             <5104D4DBC598D211B5FE0000F8FE7EB2078A5AC5@mbtlipnt02.btlabs.bt.co.uk> 
Date: Tue, 29 Aug 2000 11:32:10 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Hi George,

>You may want to have a look at this draft (see below). The draft shows one
>way for Dual Stack Intranets to be deployed with minimum need for IPv4
>address space and no native IPv6 connectivity.
>
>The purpose of this draft as well as the one I sent out yesterday
>(draft-tsirtsis-v4-over-mipv6-00.txt) is to show that Dual Stack deployment
>is not only still possible but also easy. I had a private comment on the
>v4-over-mipv6 draft saying that this is trivial and indeed it is! That is
>the point!

I think this is a very good idea and draft. It appears we (DSTM authors)
need to develop another spec to put the DNS parts back in DSTM (or AIIH)
and also for draft-soliman-siit-dstm-00.txt.

If so how quick does the WG need a dstm-with-dns-and-aiih draft?

Would San Diego be quick enough?

thanks
/jim


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 29 12:21:49 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24359
	for <ngtrans-archive@odin.ietf.org>; Tue, 29 Aug 2000 12:21:48 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA01168;
	Tue, 29 Aug 2000 10:21:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA09185;
	Tue, 29 Aug 2000 09:21:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7TGK7K21297
	for ngtrans-dist; Tue, 29 Aug 2000 09:20:07 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7TGK0621290
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 09:20:00 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA17911
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 09:20:00 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gandalf.axion.bt.co.uk (gandalf.axion.bt.co.uk [132.146.17.29])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA28048
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 09:19:58 -0700 (PDT)
Received: from cbtlipnt02.btlabs.bt.co.uk by gandalf (local) with ESMTP;
          Tue, 29 Aug 2000 17:19:32 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <PTMLPDNH>;
          Tue, 29 Aug 2000 17:19:27 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5AE4@mbtlipnt02.btlabs.bt.co.uk>
To: bound@zk3.dec.com
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) 6to4 and dstm 
Date: Tue, 29 Aug 2000 17:16:17 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.88)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

Jim,

I think a separate DSTM draft for incoming connections will be very good and
by San Diego will be grate.

There is also a general question about the future of drafts like
v4-over-mipv6, dstm-and-6to4 as well as Soliman's siit-dstm  and possible
others that seam to *combine* existing ngtrans tools rather than create new
ones. I think this work is important in that it makes us understand the
tools and the implications of their use.

Any thoughts on that?

George
> -----Original Message-----
> From:	Jim Bound [SMTP:bound@zk3.dec.com]
> Sent:	Tuesday, August 29, 2000 4:32 PM
> To:	george.tsirtsis@bt.com
> Cc:	ngtrans@sunroof.eng.sun.com
> Subject:	Re: (ngtrans) 6to4 and dstm 
> 
> Hi George,
	...

> I think this is a very good idea and draft. It appears we (DSTM authors)
> need to develop another spec to put the DNS parts back in DSTM (or AIIH)
> and also for draft-soliman-siit-dstm-00.txt.
> 
> If so how quick does the WG need a dstm-with-dns-and-aiih draft?
> 
> Would San Diego be quick enough?
> 
> thanks
> /jim


From owner-ngtrans@sunroof.eng.sun.com  Tue Aug 29 23:49:10 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07552
	for <ngtrans-archive@odin.ietf.org>; Tue, 29 Aug 2000 23:49:09 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA15731;
	Tue, 29 Aug 2000 21:49:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA08404;
	Tue, 29 Aug 2000 20:48:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e7U3let21859
	for ngtrans-dist; Tue, 29 Aug 2000 20:47:40 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e7U3lX621852
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 20:47:33 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA14296
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 20:47:32 -0700 (PDT)
Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA07320
	for <ngtrans@sunroof.eng.sun.com>; Tue, 29 Aug 2000 20:47:32 -0700 (PDT)
Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345)
	id 3D70119BA; Tue, 29 Aug 2000 23:47:32 -0400 (EDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail02.zma.compaq.com (Postfix) with ESMTP
	id ED1511AC3; Tue, 29 Aug 2000 23:47:31 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id XAA0000821448; Tue, 29 Aug 2000 23:47:18 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200008300347.XAA0000821448@anw.zk3.dec.com>
To: <george.tsirtsis@bt.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) 6to4 and dstm 
In-reply-to: Your message of "Tue, 29 Aug 2000 17:16:17 BST."
             <5104D4DBC598D211B5FE0000F8FE7EB2078A5AE4@mbtlipnt02.btlabs.bt.co.uk> 
Date: Tue, 29 Aug 2000 23:47:18 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

George,

>I think a separate DSTM draft for incoming connections will be very good and
>by San Diego will be grate.

OK.. That is doable.  We have to ressurect parts of AIIH.
Which Erik wanted done at the Pittsburgh NGTRANS meeting too for
siit-dstm.

>There is also a general question about the future of drafts like
>v4-over-mipv6, dstm-and-6to4 as well as Soliman's siit-dstm  and possible
>others that seam to *combine* existing ngtrans tools rather than create new
>ones. I think this work is important in that it makes us understand the
>tools and the implications of their use.
>
>Any thoughts on that?

I think this is one of the stellar achievements of the NGTRANS Working
Group and the folks working very hard on this set of problems.  We can
resuse the ideas and mechanisms in all the drafts almost like a
a matrix to plug this mechanism for this problem.  The working group and
chairs should be very proud of this work we have produced on all fronts.
Your recent Dual Stack Mobile and Solimans siit-dstm exemplifies this I
think.  This was the objective of the Grenoble France Interim meeting
about 19 months ago and I think we have achieved success from the goals
of that meeting.  Also NAT-PT used SIIT...very good engineering....

Of course this means that the NGTRANS Roadmap document will get
recursive :----)...

regards,
/jim



