From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  1 22:52:11 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18183
	for <ngtrans-archive@lists.ietf.org>; Wed, 1 Jan 2003 22:52:11 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA25825;
	Wed, 1 Jan 2003 20:54:29 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h023sPXs027088;
	Wed, 1 Jan 2003 19:54:27 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h023s316015598
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 1 Jan 2003 19:54:03 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h023s3CD015597
	for ngtrans-bumvof58w; Wed, 1 Jan 2003 19:54:03 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h023s016015590
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Jan 2003 19:54:00 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h023sBXq027070
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Jan 2003 19:54:11 -0800 (PST)
Received: from hpsexgw03.hpsglobal.com ([203.200.72.56])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA03457
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Jan 2003 19:54:04 -0800 (PST)
Received: by HPSEXGW03 with Internet Mail Service (5.5.2653.19)
	id <Z0GSA2L7>; Thu, 2 Jan 2003 09:24:29 +0530
Message-ID: <AD112C8ABC61D511B88500902785FCE1049A8BD0@HPSB31EX57>
From: "Thakur, Anand" <Anand.Thakur@hpsglobal.com>
To: "Fred L. Templin" <ftemplin@IPRG.nokia.com>,
        Jeroen Massar
	 <jeroen@unfix.org>
Cc: "'Michael R. Cole'" <mc5w@earthlink.net>, ngtrans@sunroof.eng.sun.com
Subject: RE: ReN: (ngtrans) IPv6 tranisition issues
Date: Thu, 2 Jan 2003 09:24:16 +0530 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Thakur, Anand" <Anand.Thakur@hpsglobal.com>

Wish you and your loved ones a Very Happy and Prosperous New Year as well

regards
Anand Thakur
HCL Perot Systems (A SEI CMM Level 5 Company)
Plot No 3, Sector 125, NOIDA (UP)-201301, India
* Tel  +91 120 4432755-79, X3348 (EPABX)
mobile:9811748512

> -----Original Message-----
> From:	Fred L. Templin [SMTP:ftemplin@IPRG.nokia.com]
> Sent:	Wednesday, January 01, 2003 5:56 AM
> To:	Jeroen Massar
> Cc:	'Thakur, Anand'; 'Michael R. Cole'; ngtrans@sunroof.eng.sun.com
> Subject:	Re: ReN: (ngtrans) IPv6 tranisition issues
> 
> Jeroen Massar wrote:
> > First I would like to wish everybody a happy and fruitful 2003.
> > Asian Pacific people are already in 2003 there now I think as it's 16:00
> > CET
> > Oh and ofcourse happy IPv6'ing ;)
> 
> Huh? It was still 2002 when I submitted the -09 version of the
> ISATAP spec to the repository. (Guess I need to be more aware of
> what timezone I'm in!) Anyone interested can view the latest
> draft version at:
> 
>    http://www.geocities.com/osprey67/isatap-09.txt
> 
> > Greets,
> >  Jeroen
> 
> Happy New Year to all,
> 
> Fred Templin
> ftemplin@iprg.nokia.com
> 
> 
> 


From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 05:28:50 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00780
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 05:28:49 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA10637;
	Mon, 6 Jan 2003 03:31:21 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06AVIXs019327;
	Mon, 6 Jan 2003 02:31:20 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06AUw16005774
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:30:58 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06AUwmY005773
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 02:30:58 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06AUt16005766
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:30:55 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06AV4uk005477
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:31:04 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA22862
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:30:57 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06AUxto000634
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 08:30:59 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 08:30:44 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 08:29:47 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017E9F9A@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: (ngtrans) IPv6 tranisition issues
Thread-Index: AcKvjgPlKRlrasWZRe+YhCKfIslFPgF34l9g
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: <nick@arc.net.my>
Cc: "Pekka Savola" <pekkas@netcore.fi>,
        "Thakur, Anand" <Anand.Thakur@hpsglobal.com>,
        <ngtrans@sunroof.eng.sun.com>, <engsg@i2r.a-star.edu.sg>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06AUt16005767
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 Hi Nick,

>
>
>Yes, in a typing fury I forgot/missed the IPv6 solution for mobility.
>IPv6 is streamlined and designed for mobility in mind. Again there are
>the patches in IPv4, although riddled with triangular routing issues.
>But then again is there anyone really into mobile IP? And I use NTT
>DoCoMo and likes in Japan as examples for this and not a 'hotspot' cafe
>answer on 802.11.
>

  In IPv4, attacks against ARP protocol (mobile IPv4 trusts in ARP protocol) are easy to implment. DHCP can also be bypassed easily. So, neighbour protocol with AH is more secure solution. Regards,

		Marcelo.



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 05:55:19 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01054
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 05:55:19 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA29656;
	Mon, 6 Jan 2003 03:57:54 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06Avmum008777;
	Mon, 6 Jan 2003 02:57:51 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06AvT16006366
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:57:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06AvTJo006365
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 02:57:29 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06AvQ16006355
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:57:26 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06AvZXq022604
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 02:57:36 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA22618
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:57:29 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06AvVto002387
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 08:57:31 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 08:57:17 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: ReN: (ngtrans) IPv6 tranisition issues 
Date: Mon, 6 Jan 2003 08:56:20 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: ReN: (ngtrans) IPv6 tranisition issues 
Thread-Index: AcKwvbefP8x4FOKlSNuIAW8pNlfVnQEsbqdQ
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Michael R. Cole" <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06AvQ16006356
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


  I think that NAT is a good workaround and it can be done to support all aplications (the cost is more complex code -- Code more complex = more bugs = more security problems = poor performance = ...). NAT is implemented in routers and firewalls. So, it put more dificulty to implementators, provides problems to performance, etc. NAT and VPNs solutions normally don´t work very well together. I think that NAT is something that several vendors would like to kill :-). Routing and firewalling could do only your work, without regarding address translation. In IPv6, routing is more easy and NAT is not necessary anymore. So, packets can flow faster in Internet. 
REgards,

			Marcelo.

-----Mensagem original-----
De: Michael R. Cole [mailto:mc5w@earthlink.net]
Enviada em: terça-feira, 31 de dezembro de 2002 09:20
Para: ngtrans@sunroof.eng.sun.com
Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues 



----- Original Message -----
From: "Keith Moore" <moore@cs.utk.edu>
To: "Michael R. Cole" <mc5w@earthlink.net>
Cc: <ngtrans@sunroof.eng.sun.com>
Sent: Tuesday, December 31, 2002 12:28 AM
Subject: Re: ReN: (ngtrans) IPv6 tranisition issues


> >  A NAT box is just simply
> > a retooled router,
>
> that's a truly bizarre statement.  I suppose it's true from a
> hardware perspective, but it's like saying that a NAT box is
> just a retooled computer with a couple of network interfaces -
> true, but irrelevant to the question at hand.
>
> > just that some are better and some are worse.
>
> all NATs break applications.  some NATs know about a few more
> protocols than others, but no NAT can handle every possible protocol,
> many protocols simply cannot be made to work transparently through NAT.
>
> Keith
>

Your definition of the word break must be different than the one in the
dictionary. If an application works with a NAT box, then it is NOT BROKEN!
Your claim would also say that a timesharing system with only 1 public IPv4
address would not work which is what a cone NAT mimics. That is, a cone NAT
fools that public Internet into thinking that a LAN or other subnet is in
actuality a single machine. At any rate, a NAT box is a patch that gets
around the problem that a good sized chunk of the IPv4 address space was
wastefully allocated to the original players at essentially zero cost.

Maybe your first experience with a NAT box was with a really crummy one? If
that is your only experience or of you have no experience with NAT boxes,
then you have no business crticizing them. Some NAT software that I have
tried was absolutely horrible.

I am not trying to say that the better NAT boxes will work with ALL
applications. Somehow, the cable companies are able to use them at their
headends without breaking applications. However, I have noticed that
enterprise-class NAT boxes use a server-client setup so that applications
are not really aware or can tell that they are indirectly connected to the
Internet. Symmetric NAT boxes probably do work better in part because they
mimic a timesharing system with one public IPv4 address for each user.

Of course, some applications are very picky about what they will eat.

MIke Cole, mc5w@earthlink.net





From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 06:26:33 2003
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01364
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 06:26:32 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA07804;
	Mon, 6 Jan 2003 03:27:53 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06BRnum011749;
	Mon, 6 Jan 2003 03:27:51 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06BRU16006693
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:27:30 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06BRU86006692
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 03:27:30 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06BRR16006685
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:27:28 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06BRaXq025860
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:27:36 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA27835
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 03:27:30 -0800 (PST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06BRWto004287
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 09:27:32 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 09:27:17 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 09:26:21 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017E9F9E@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcKxlcpBZRZqy/ONQ+GZieAgUMD9JgD4DlIw
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: <nick@arc.net.my>, "Keith Moore" <moore@cs.utk.edu>
Cc: <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06BRS16006686
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 FOlks,

  Look, please, in this URL. It seems that Microsoft wants to impulsionate Ipv6 development too :-).
http://news.com.com/2100-1033-885664.html
Best Regards,

			Marcelo

-----Mensagem original-----
De: nick@arc.net.my [mailto:nick@arc.net.my]
Enviada em: sábado, 28 de dezembro de 2002 07:04
Para: Keith Moore
Cc: ngtrans@sunroof.eng.sun.com
Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues


Keith,

Thank you for your input. I have looked at various angles on this but
end up at a dead-end every time. As in my earlier postings looking at
IPv6 and the many obvious advatages in QoS, multicast, routing, address
space, mobility, etc, there is always an IPv4 solution for this. The
solution may be a dodgy patch, not as streamlined or designed from the
ground up as the IPv6 version, but it works and John Q. Public is not
going to rush out now or even look at including an IPv6 subnet in  his
current IPv4 setup.

The key word here is 'now'. Perhaps later or of course when 3G networks
are available, but when?. A good example is to look at the Y2K issue.
Most companies started addressing the issue at the last minute only. And
this could possibly be the path with the IP address shortage issue.

So what compelling enough reason can be presented to Mr. John here for
him to even consider IPv6. Even start looking at a staggered transition
plan. Or even hardware/software developers -most of these are either
from Europe and Japan.

Regards,
-nick/




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 07:07:51 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01785
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 07:07:50 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA27974;
	Mon, 6 Jan 2003 05:10:39 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06CAZXs000223;
	Mon, 6 Jan 2003 04:10:37 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06CAG16007024
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:10:16 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06CAGOv007023
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 04:10:16 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06CAE16007016
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:10:14 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06CANuk016090
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:10:23 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA24144
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:10:17 -0800 (PST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h06CA2615240;
	Mon, 6 Jan 2003 14:10:02 +0200
Date: Mon, 6 Jan 2003 14:10:02 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Marcelo Barbosa Lima <mlima@cpqd.com.br>
cc: nick@arc.net.my, "Thakur, Anand" <Anand.Thakur@hpsglobal.com>,
        <ngtrans@sunroof.eng.sun.com>, <engsg@i2r.a-star.edu.sg>
Subject: Re: RES: (ngtrans) IPv6 tranisition issues
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017E9F9A@MAILSRV1.aquarius.cpqd.com.br>
Message-ID: <Pine.LNX.4.44.0301061408220.15213-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
> >Yes, in a typing fury I forgot/missed the IPv6 solution for mobility.
> >IPv6 is streamlined and designed for mobility in mind. Again there are
> >the patches in IPv4, although riddled with triangular routing issues.
> >But then again is there anyone really into mobile IP? And I use NTT
> >DoCoMo and likes in Japan as examples for this and not a 'hotspot' cafe
> >answer on 802.11.
> >
> 
>   In IPv4, attacks against ARP protocol (mobile IPv4 trusts in ARP
> protocol) are easy to implment. DHCP can also be bypassed easily. So,
> neighbour protocol with AH is more secure solution. Regards,

Less market speak, more technology, please.

Securing the neighbor protocol with AH is _hard_.

Please check out SEND working group.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 07:35:48 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02103
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 07:35:47 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA10280;
	Mon, 6 Jan 2003 05:38:22 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06CcEum019069;
	Mon, 6 Jan 2003 04:38:16 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Cbu16007437
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:37:56 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06Cbt5N007436
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 04:37:55 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Cbq16007429
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:37:52 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06Cc1uk019033
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:38:01 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA12823
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 04:37:55 -0800 (PST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06Cbvto008261
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:37:57 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 10:37:42 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: RES: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 10:36:45 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017F55DE@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: RES: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1fMcIU1Z6MVBGRiGBP+xFOpcIIAAAdtMg
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Pekka Savola" <pekkas@netcore.fi>
Cc: <nick@arc.net.my>, "Thakur, Anand" <Anand.Thakur@hpsglobal.com>,
        <ngtrans@sunroof.eng.sun.com>, <engsg@i2r.a-star.edu.sg>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06Cbr16007430
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 Pekka Savola,

   Sorry for my "market speak" but, of the RFC 2461:

   "Neighbor Discovery protocol packet exchanges can be authenticated
   using the IP Authentication Header [IPv6-AUTH].  A node SHOULD
   include an Authentication Header when sending Neighbor Discovery
   packets if a security association for use with the IP Authentication
   Header exists for the destination address.  The security associations
   may have been created through manual configuration or through the
   operation of some key management protocol.

   Received Authentication Headers in Neighbor Discovery packets MUST be
   verified for correctness and packets with incorrect authentication
   MUST be ignored.

   It SHOULD be possible for the system administrator to configure a
   node to ignore any Neighbor Discovery messages that are not
   authenticated using either the Authentication Header or Encapsulating
   Security Payload.  The configuration technique for this MUST be
   documented.  Such a switch SHOULD default to allowing unauthenticated
   messages.

   Confidentiality issues are addressed by the IP Security Architecture
   and the IP Encapsulating Security Payload documents [IPv6-SA, IPv6-
   ESP]."

  In a local enviroment is relatively more simple to create secutity associates between peers. Even PKI solution can be implemented. There are some purposes regarding authentication in Neighbor discovery protocol. I looked for a RFC/draft about it, but I did not find it. Please, who know where I can find it email me. If it is hard to implement, I think that it is not, because is more simple to establish SAs in local network.
Regards,

			Marcelo. 

-----Mensagem original-----
De: Pekka Savola [mailto:pekkas@netcore.fi]
Enviada em: segunda-feira, 6 de janeiro de 2003 10:10
Para: Marcelo Barbosa Lima
Cc: nick@arc.net.my; Thakur, Anand; ngtrans@sunroof.eng.sun.com;
engsg@i2r.a-star.edu.sg
Assunto: Re: RES: (ngtrans) IPv6 tranisition issues


On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
> >Yes, in a typing fury I forgot/missed the IPv6 solution for mobility.
> >IPv6 is streamlined and designed for mobility in mind. Again there are
> >the patches in IPv4, although riddled with triangular routing issues.
> >But then again is there anyone really into mobile IP? And I use NTT
> >DoCoMo and likes in Japan as examples for this and not a 'hotspot' cafe
> >answer on 802.11.
> >
> 
>   In IPv4, attacks against ARP protocol (mobile IPv4 trusts in ARP
> protocol) are easy to implment. DHCP can also be bypassed easily. So,
> neighbour protocol with AH is more secure solution. Regards,

Less market speak, more technology, please.

Securing the neighbor protocol with AH is _hard_.

Please check out SEND working group.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 09:15:21 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03819
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 09:15:19 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA20048;
	Mon, 6 Jan 2003 07:18:06 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06EHoum000735;
	Mon, 6 Jan 2003 06:18:00 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06EHS16007831
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 06:17:28 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06EHSTI007830
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 06:17:28 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06EHQ16007823
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 06:17:26 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06EHYuk000657
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 06:17:34 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA23072
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 06:17:28 -0800 (PST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h06EHEs15915;
	Mon, 6 Jan 2003 16:17:14 +0200
Date: Mon, 6 Jan 2003 16:17:14 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Marcelo Barbosa Lima <mlima@cpqd.com.br>
cc: nick@arc.net.my, "Thakur, Anand" <Anand.Thakur@hpsglobal.com>,
        <ngtrans@sunroof.eng.sun.com>, <engsg@i2r.a-star.edu.sg>
Subject: Re: RES: RES: (ngtrans) IPv6 tranisition issues
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017F55DE@MAILSRV1.aquarius.cpqd.com.br>
Message-ID: <Pine.LNX.4.44.0301061608230.15866-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
>    Sorry for my "market speak" but, of the RFC 2461:
> 
>    "Neighbor Discovery protocol packet exchanges can be authenticated
>    using the IP Authentication Header [IPv6-AUTH].  A node SHOULD
>    include an Authentication Header when sending Neighbor Discovery
>    packets if a security association for use with the IP Authentication
>    Header exists for the destination address.  The security associations
>    may have been created through manual configuration or through the
>    operation of some key management protocol.
> 
>    Received Authentication Headers in Neighbor Discovery packets MUST be
>    verified for correctness and packets with incorrect authentication
>    MUST be ignored.

Yeah, the language is wishy-washy -- when specifying, people didn't sit 
down and consider what it actually requires to make it work.
 
>    It SHOULD be possible for the system administrator to configure a
>    node to ignore any Neighbor Discovery messages that are not
>    authenticated using either the Authentication Header or Encapsulating
>    Security Payload.  The configuration technique for this MUST be
>    documented.  Such a switch SHOULD default to allowing unauthenticated
>    messages.
> 
>    Confidentiality issues are addressed by the IP Security Architecture
>    and the IP Encapsulating Security Payload documents [IPv6-SA, IPv6-
>    ESP]."
> 
>   In a local enviroment is relatively more simple to create secutity
> associates between peers. Even PKI solution can be implemented. There
> are some purposes regarding authentication in Neighbor discovery
> protocol. I looked for a RFC/draft about it, but I did not find it.
> Please, who know where I can find it email me. If it is hard to
> implement, I think that it is not, because is more simple to establish
> SAs in local network. Regards,

How do you implement automatic keying when you don't have an IP address?
Therein is a bootstrapping problem.

Manual keying is possible but very burdensome, as you will also have to
create security associations with link-local multicast addresses.  Of
course, this is only possible in subnets where you know which nodes will
be there so pre-configuration will be possible (wrt. e.g. WLAN hotspots
are not so.)

The IETF web page is down at the moment, but check SEND working group 
page when it's available.  In particular check out these drafts:

draft-ietf-send-psreq-00.txt (under revision, new tentative version posted 
on the list)
draft-arkko-manual-icmpv6-sas-01.txt

> -----Mensagem original-----
> De: Pekka Savola [mailto:pekkas@netcore.fi]
> Enviada em: segunda-feira, 6 de janeiro de 2003 10:10
> Para: Marcelo Barbosa Lima
> Cc: nick@arc.net.my; Thakur, Anand; ngtrans@sunroof.eng.sun.com;
> engsg@i2r.a-star.edu.sg
> Assunto: Re: RES: (ngtrans) IPv6 tranisition issues
> 
> 
> On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
> > >Yes, in a typing fury I forgot/missed the IPv6 solution for mobility.
> > >IPv6 is streamlined and designed for mobility in mind. Again there are
> > >the patches in IPv4, although riddled with triangular routing issues.
> > >But then again is there anyone really into mobile IP? And I use NTT
> > >DoCoMo and likes in Japan as examples for this and not a 'hotspot' cafe
> > >answer on 802.11.
> > >
> > 
> >   In IPv4, attacks against ARP protocol (mobile IPv4 trusts in ARP
> > protocol) are easy to implment. DHCP can also be bypassed easily. So,
> > neighbour protocol with AH is more secure solution. Regards,
> 
> Less market speak, more technology, please.
> 
> Securing the neighbor protocol with AH is _hard_.
> 
> Please check out SEND working group.
> 
> 

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 10:30:38 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05535
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 10:30:37 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA23029;
	Mon, 6 Jan 2003 08:33:09 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06FX6um014277;
	Mon, 6 Jan 2003 07:33:08 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06FWl16008098
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 07:32:47 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06FWl2I008097
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 07:32:47 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06FWj16008090
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 07:32:45 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06FWrXq029656
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 07:32:53 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA07782
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 07:32:47 -0800 (PST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06FWnto017420
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 13:32:49 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 13:32:35 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: RES: RES: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 13:31:38 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017F55DF@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: RES: RES: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1jow0hYmkI6LvQPOd5PMKDQJw3AABv7ZQ
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Pekka Savola" <pekkas@netcore.fi>
Cc: <nick@arc.net.my>, "Thakur, Anand" <Anand.Thakur@hpsglobal.com>,
        <ngtrans@sunroof.eng.sun.com>, <engsg@i2r.a-star.edu.sg>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06FWj16008091
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 I understand what you are saying. For this case, I think exaclty in manual configuration.  Using pre-shared secret or certificate digital. Really, the objetcive is to limit mobilility to only networks where the MN is permited (I dont want stranger laptops loging in my network :-). In public networks (cellular network, for example), authentication can be null (authentication would be take care to higher layers). One similar solution to IEEE 802.11b. In ARP and DHCP, this is impossible. So, in MIPv4 never can have this aditional security. Some authentication is more secure than no authentication. Manual key can be used in controlled and private enviroments. In the practice, nobody will want unkown hosts connected in your network. In public networks where we dont have pre-shared secrets or public Key Infrastructure, authentication can be done in higher layers. So, The possibility of implement authentication is real. This makes me to believe that MIPv6 is more secure than MIP4 !
regarding this subject.
Best Regards,

			Marcelo.

-----Mensagem original-----
De: Pekka Savola [mailto:pekkas@netcore.fi]
Enviada em: segunda-feira, 6 de janeiro de 2003 12:17
Para: Marcelo Barbosa Lima
Cc: nick@arc.net.my; Thakur, Anand; ngtrans@sunroof.eng.sun.com;
engsg@i2r.a-star.edu.sg
Assunto: Re: RES: RES: (ngtrans) IPv6 tranisition issues


On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
>    Sorry for my "market speak" but, of the RFC 2461:
> 
>    "Neighbor Discovery protocol packet exchanges can be authenticated
>    using the IP Authentication Header [IPv6-AUTH].  A node SHOULD
>    include an Authentication Header when sending Neighbor Discovery
>    packets if a security association for use with the IP Authentication
>    Header exists for the destination address.  The security associations
>    may have been created through manual configuration or through the
>    operation of some key management protocol.
> 
>    Received Authentication Headers in Neighbor Discovery packets MUST be
>    verified for correctness and packets with incorrect authentication
>    MUST be ignored.

Yeah, the language is wishy-washy -- when specifying, people didn't sit 
down and consider what it actually requires to make it work.
 
>    It SHOULD be possible for the system administrator to configure a
>    node to ignore any Neighbor Discovery messages that are not
>    authenticated using either the Authentication Header or Encapsulating
>    Security Payload.  The configuration technique for this MUST be
>    documented.  Such a switch SHOULD default to allowing unauthenticated
>    messages.
> 
>    Confidentiality issues are addressed by the IP Security Architecture
>    and the IP Encapsulating Security Payload documents [IPv6-SA, IPv6-
>    ESP]."
> 
>   In a local enviroment is relatively more simple to create secutity
> associates between peers. Even PKI solution can be implemented. There
> are some purposes regarding authentication in Neighbor discovery
> protocol. I looked for a RFC/draft about it, but I did not find it.
> Please, who know where I can find it email me. If it is hard to
> implement, I think that it is not, because is more simple to establish
> SAs in local network. Regards,

How do you implement automatic keying when you don't have an IP address?
Therein is a bootstrapping problem.

Manual keying is possible but very burdensome, as you will also have to
create security associations with link-local multicast addresses.  Of
course, this is only possible in subnets where you know which nodes will
be there so pre-configuration will be possible (wrt. e.g. WLAN hotspots
are not so.)

The IETF web page is down at the moment, but check SEND working group 
page when it's available.  In particular check out these drafts:

draft-ietf-send-psreq-00.txt (under revision, new tentative version posted 
on the list)
draft-arkko-manual-icmpv6-sas-01.txt

> -----Mensagem original-----
> De: Pekka Savola [mailto:pekkas@netcore.fi]
> Enviada em: segunda-feira, 6 de janeiro de 2003 10:10
> Para: Marcelo Barbosa Lima
> Cc: nick@arc.net.my; Thakur, Anand; ngtrans@sunroof.eng.sun.com;
> engsg@i2r.a-star.edu.sg
> Assunto: Re: RES: (ngtrans) IPv6 tranisition issues
> 
> 
> On Mon, 6 Jan 2003, Marcelo Barbosa Lima wrote:
> > >Yes, in a typing fury I forgot/missed the IPv6 solution for mobility.
> > >IPv6 is streamlined and designed for mobility in mind. Again there are
> > >the patches in IPv4, although riddled with triangular routing issues.
> > >But then again is there anyone really into mobile IP? And I use NTT
> > >DoCoMo and likes in Japan as examples for this and not a 'hotspot' cafe
> > >answer on 802.11.
> > >
> > 
> >   In IPv4, attacks against ARP protocol (mobile IPv4 trusts in ARP
> > protocol) are easy to implment. DHCP can also be bypassed easily. So,
> > neighbour protocol with AH is more secure solution. Regards,
> 
> Less market speak, more technology, please.
> 
> Securing the neighbor protocol with AH is _hard_.
> 
> Please check out SEND working group.
> 
> 

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords





From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 12:50:31 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08726
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 12:50:31 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA08276;
	Mon, 6 Jan 2003 09:51:56 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06Hpkum015554;
	Mon, 6 Jan 2003 09:51:51 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Hpa16009087
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 09:51:36 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06Hpakt009086
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 09:51:36 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06HpW16009073
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 09:51:32 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06HpVuk015457
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 09:51:31 -0800 (PST)
Received: from smtp.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA22627
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:51:25 -0700 (MST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 5762414032; Mon,  6 Jan 2003 12:51:25 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 19443-02; Mon, 6 Jan 2003 12:51:24 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id 4038F1402F; Mon,  6 Jan 2003 12:51:24 -0500 (EST)
Date: Mon, 6 Jan 2003 12:51:24 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Cc: mc5w@earthlink.net, ngtrans@sunroof.eng.sun.com
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Message-Id: <20030106125124.18a5d0d7.moore@cs.utk.edu>
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
References: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: 9ff723688857aa27aa08a41ac9e38bb4751498d9
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit

On Mon, 6 Jan 2003 08:56:20 -0200
"Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:

> 
>   I think that NAT is a good workaround and it can be done to support all aplications

you are mistaken.  your statement is completely and utterly incorrect.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 13:00:20 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08920
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 13:00:20 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA02110;
	Mon, 6 Jan 2003 11:03:07 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06I33Xs006833;
	Mon, 6 Jan 2003 10:03:05 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06I2r16009277
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:02:53 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06I2r8X009276
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 10:02:53 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06I2p16009269
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:02:51 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06I2ouk019131
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:02:50 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA10294
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:02:43 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h06I2jto026241
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 16:02:45 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 06 Jan 2003 16:02:30 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 16:01:34 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017E9FA6@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1rInlxeU3if/nTVm61IbjKjGdAwAAAtaA
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06I2p16009270
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 Hi Keith,

   I dont know one application what NAT (or reverse NAT) are not abble to support or what one NAT implementation can be extended to provide support it. If NAT implemantation is smart and application sense, I think that I can do translation of IP addresses and ports in application data (without cryptography), if necessary, like I do in FTP and other tricky protocols. Can you tell me applications where NAT can not be used? Regards,

			Marcelo.

-----Mensagem original-----
De: Keith Moore [mailto:moore@cs.utk.edu]
Enviada em: segunda-feira, 6 de janeiro de 2003 15:51
Para: Marcelo Barbosa Lima
Cc: mc5w@earthlink.net; ngtrans@sunroof.eng.sun.com
Assunto: Re: RES: ReN: (ngtrans) IPv6 tranisition issues


On Mon, 6 Jan 2003 08:56:20 -0200
"Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:

> 
>   I think that NAT is a good workaround and it can be done to support all aplications

you are mistaken.  your statement is completely and utterly incorrect.

Keith



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 13:02:13 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08975
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 13:02:12 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA03456;
	Mon, 6 Jan 2003 11:05:07 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06I52um019805;
	Mon, 6 Jan 2003 10:05:05 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06I4p16009347
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:04:51 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06I4ppE009344
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 10:04:51 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06I4l16009336
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:04:48 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06I4luk019702
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:04:47 -0800 (PST)
Received: from purgatory.unfix.org (cust.92.136.adsl.cistron.nl [195.64.92.136])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA17339
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:04:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 209C97B45; Mon,  6 Jan 2003 19:04:37 +0100 (CET)
Received: from limbo (limbo.unfix.org [::ffff:10.100.13.33])
	(using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 393427ABD; Mon,  6 Jan 2003 19:04:31 +0100 (CET)
From: "Jeroen Massar" <jeroen@unfix.org>
To: "'Keith Moore'" <moore@cs.utk.edu>,
        "'Marcelo Barbosa Lima'" <mlima@cpqd.com.br>
Cc: <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 19:05:54 +0100
Organization: Unfix
Message-ID: <005101c2b5ae$4213dc50$210d640a@unfix.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
In-Reply-To: <20030106125124.18a5d0d7.moore@cs.utk.edu>
X-Virus-Scanned: by AMaViS @ purgatory.unfix.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06I4m16009337
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Jeroen Massar" <jeroen@unfix.org>
Content-Transfer-Encoding: 8bit

Keith Moore wrote:

> On Mon, 6 Jan 2003 08:56:20 -0200
> "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> 
> > 
> >   I think that NAT is a good workaround and it can be done 
> to support all aplications
> 
> you are mistaken.  your statement is completely and utterly incorrect.

/me sings Netmeeting (H323 or something) and many more ;)

And then still one can't setup a box behind a nat to do FTP and then
have the outside world contact it unless the admin of the NAT box
is doing per connection redirection. Which is simply not done.

NAT != P2P -> and thus not the idea why people invented the internet.

Greets,
 Jeroen




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 13:52:54 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10326
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 13:52:54 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA09520;
	Mon, 6 Jan 2003 11:54:14 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06IsAXs023326;
	Mon, 6 Jan 2003 10:54:12 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Irx16010952
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:53:59 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06Irx1W010951
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 10:53:59 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Irv16010944
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:53:57 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06Iruuk005608
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 10:53:56 -0800 (PST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA07242
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:53:51 -0700 (MST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA29312;
	Mon, 6 Jan 2003 10:53:50 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h06Irn229767;
	Mon, 6 Jan 2003 10:53:49 -0800
X-mProtect: <200301061853> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdJMspMC; Mon, 06 Jan 2003 10:53:48 PST
Message-ID: <3E19D30F.1060803@iprg.nokia.com>
Date: Mon, 06 Jan 2003 11:03:43 -0800
From: "Fred L. Templin" <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
CC: Marcelo Barbosa Lima <mlima@cpqd.com.br>, mc5w@earthlink.net,
        ngtrans@sunroof.eng.sun.com
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
References: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br> <20030106125124.18a5d0d7.moore@cs.utk.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <ftemplin@iprg.nokia.com>
Content-Transfer-Encoding: 7bit

Keith,

No offense intended, but I am beginning to suspect that you have
somehow implemented an "automatic insult generator" in your mailer
that is triggered anytime someone mentions the word "NAT". :^}

Fred Templin
ftemplin@iprg.nokia.com

Keith Moore wrote:
> On Mon, 6 Jan 2003 08:56:20 -0200
> "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> 
> 
>>  I think that NAT is a good workaround and it can be done to support all aplications
> 
> 
> you are mistaken.  your statement is completely and utterly incorrect.
> 
> Keith




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 14:04:54 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10698
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 14:04:53 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA27159;
	Mon, 6 Jan 2003 11:06:37 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06J6YXs027694;
	Mon, 6 Jan 2003 11:06:36 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06J6N16011330
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:06:23 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06J6M3j011329
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 11:06:22 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06J6J16011319
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:06:19 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06J6IXq027572
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:06:18 -0800 (PST)
Received: from zmamail04.zma.compaq.com (zmamail04.zma.compaq.com [161.114.64.104])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA08897
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 12:06:13 -0700 (MST)
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net [16.103.130.96])
	by zmamail04.zma.compaq.com (Postfix) with ESMTP
	id A37774307; Mon,  6 Jan 2003 14:06:12 -0500 (EST)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 6 Jan 2003 14:06:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 14:06:10 -0500
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B03240D8B@tayexc13.americas.cpqcorp.net>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1tVZUFaApZVO4RcCDZBjNb8XELAAAHJuQ
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Fred L. Templin" <ftemplin@iprg.nokia.com>,
        "Keith Moore" <moore@cs.utk.edu>
Cc: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>, <mc5w@earthlink.net>,
        <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 06 Jan 2003 19:06:11.0272 (UTC) FILETIME=[AD1B5480:01C2B5B6]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06J6J16011320
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Bound, Jim" <Jim.Bound@hp.com>
Content-Transfer-Encoding: 8bit

Fred,

I did not think Keiths mail was insulting.  What he has said and is
saying in most cases is correct. NAT breaks end-to-end period.  Work
arounds are unacceptable to any business person I know for many many
reasons identified in the RFC on NAT Implications.

How would you rephrase:

you are mistaken.  your statement is completely and utterly incorrect

To make is not insulting?  Though I would not find that insulting.
Keith has been personnally attacked and very rudely many many times in
this discussion format.  I have too and unlike Keith I have offered
several to even discuss it out of the IETF on the street or in some
private location to get to root of their issue with me or others
personally.  So given the way he has been treated well I think he has
been extremely kind.

Let me try this.  NAT is bad for the Internet and bad for users and bad
for security and bad for people and does not work with end-to-end
applications.  Period.

Of course I really don't seriously care what people think on this list
but what the market thinks about NAT unless we want to build a standard
then that is our work here and I will care.  Fortuneately the market is
waking up and want NAT gone is my reading and it will be gone with IPv6.
Period.

Respectfully,
/jim


/jim

 


> -----Original Message-----
> From: Fred L. Templin [mailto:ftemplin@iprg.nokia.com] 
> Sent: Monday, January 06, 2003 2:04 PM
> To: Keith Moore
> Cc: Marcelo Barbosa Lima; mc5w@earthlink.net; 
> ngtrans@sunroof.eng.sun.com
> Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> Keith,
> 
> No offense intended, but I am beginning to suspect that you 
> have somehow implemented an "automatic insult generator" in 
> your mailer that is triggered anytime someone mentions the 
> word "NAT". :^}
> 
> Fred Templin
> ftemplin@iprg.nokia.com
> 
> Keith Moore wrote:
> > On Mon, 6 Jan 2003 08:56:20 -0200
> > "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> > 
> > 
> >>  I think that NAT is a good workaround and it can be done 
> to support 
> >> all aplications
> > 
> > 
> > you are mistaken.  your statement is completely and utterly 
> incorrect.
> > 
> > Keith
> 
> 
> 



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 14:08:45 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10793
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 14:08:44 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA29555;
	Mon, 6 Jan 2003 11:10:37 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JAXum011767;
	Mon, 6 Jan 2003 11:10:36 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JAL16011537
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:10:21 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06JALOt011535
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 11:10:21 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JAH16011523
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:10:17 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JAGXq029015
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:10:16 -0800 (PST)
Received: from smtp.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA12734
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 12:10:10 -0700 (MST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 3F56E14032; Mon,  6 Jan 2003 14:10:10 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 25988-08; Mon, 6 Jan 2003 14:10:09 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id 3E4D214029; Mon,  6 Jan 2003 14:10:09 -0500 (EST)
Date: Mon, 6 Jan 2003 14:09:58 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Cc: mc5w@earthlink.net, ngtrans@sunroof.eng.sun.com
Subject: Re: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Message-Id: <20030106140958.1c1b54f3.moore@cs.utk.edu>
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017E9FA6@MAILSRV1.aquarius.cpqd.com.br>
References: <D49EA2F934FFAD45B337C07A9753C00E017E9FA6@MAILSRV1.aquarius.cpqd.com.br>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: 8345f4188b4e8cc2abad0e8c997caab4b50355e6
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit

On Mon, 6 Jan 2003 16:01:34 -0200
"Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:

> 
>  Hi Keith,
> 
>    I dont know one application what NAT (or reverse NAT) are not abble > to support or what one NAT implementation can be extended to provide > support it. If NAT implemantation is smart and application sense, I > think that I can do translation of IP addresses and ports in > application data (without cryptography), if necessary, like I do in > FTP and other tricky protocols. 

you are completely mistaken.  the NAT does not have sufficient information to perform the conversion even if it is aware of the protocol that the application is using.

> Can you tell me applications where NAT can not be used? Regards,

almost any distributed application fails in the presence of NAT unless there is a central server via which communications are routed.  the ones I'm most familiar with are used in distributed computation: netsolve, globus, pvm.  but SIP has this problem also.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 14:09:53 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10814
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 14:09:52 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA00164;
	Mon, 6 Jan 2003 11:11:39 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JBaum012148;
	Mon, 6 Jan 2003 11:11:38 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JBO16011603
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:11:25 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06JBOZS011602
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 11:11:24 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JBL16011592
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:11:21 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JBKuk012016
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:11:20 -0800 (PST)
Received: from smtp.cs.utk.edu (klutz.cs.utk.edu [160.36.56.50])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA02631
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:11:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by smtp.cs.utk.edu (Postfix) with ESMTP
	id 73F8B14032; Mon,  6 Jan 2003 14:11:14 -0500 (EST)
Received: from smtp.cs.utk.edu ([127.0.0.1]) by localhost (klutz [127.0.0.1]) (amavisd-new) with ESMTP id 27447-07; Mon, 6 Jan 2003 14:11:13 -0000 (EST)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by smtp.cs.utk.edu (Postfix) with SMTP
	id 8488614029; Mon,  6 Jan 2003 14:11:13 -0500 (EST)
Date: Mon, 6 Jan 2003 14:11:03 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Fred L. Templin" <ftemplin@IPRG.nokia.com>
Cc: mlima@cpqd.com.br, mc5w@earthlink.net, ngtrans@sunroof.eng.sun.com
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Message-Id: <20030106141103.01a3ecec.moore@cs.utk.edu>
In-Reply-To: <3E19D30F.1060803@iprg.nokia.com>
References: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
	<20030106125124.18a5d0d7.moore@cs.utk.edu>
	<3E19D30F.1060803@iprg.nokia.com>
X-Mailer: Sylpheed version 0.8.5claws (GTK+ 1.2.10; )
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new amavisd-new-20020630 with ClamAV
X-Razor-id: ed63ea7b46ecd51906e2c0d68a0c00ad4a40d526
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Content-Transfer-Encoding: 7bit

On Mon, 06 Jan 2003 11:03:43 -0800
"Fred L. Templin" <ftemplin@IPRG.nokia.com> wrote:

> Keith,
> 
> No offense intended, but I am beginning to suspect that you have
> somehow implemented an "automatic insult generator" in your mailer
> that is triggered anytime someone mentions the word "NAT". :^}

it's difficult to not respond when people make irresponsible comments about NAT.


From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 14:24:21 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11462
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 14:24:20 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA28669;
	Mon, 6 Jan 2003 12:25:54 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JPoXs006416;
	Mon, 6 Jan 2003 11:25:53 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JPc16012248
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:25:38 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06JPc86012247
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 11:25:38 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JPZ16012237
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:25:35 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JPZuk018769
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:25:35 -0800 (PST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA09802
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:25:30 -0800 (PST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA01011;
	Mon, 6 Jan 2003 11:25:28 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h06JPRo29760;
	Mon, 6 Jan 2003 11:25:27 -0800
X-mProtect: <200301061925> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdCzHndN; Mon, 06 Jan 2003 11:25:25 PST
Message-ID: <3E19DA79.6040708@iprg.nokia.com>
Date: Mon, 06 Jan 2003 11:35:21 -0800
From: "Fred L. Templin" <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Bound, Jim" <Jim.Bound@hp.com>
CC: Keith Moore <moore@cs.utk.edu>, Marcelo Barbosa Lima
 <mlima@cpqd.com.br>,
        mc5w@earthlink.net, ngtrans@sunroof.eng.sun.com
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
References: <9C422444DE99BC46B3AD3C6EAFC9711B03240D8B@tayexc13.americas.cpqcorp.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <ftemplin@iprg.nokia.com>
Content-Transfer-Encoding: 7bit

Hi Jim,

Bound, Jim wrote:
> Fred,
> 
> I did not think Keiths mail was insulting.

Exactly why I prefaced my note with "No offense intended";
just trying to make light of an ongoing discussion that has
(to me) become almost humerous by its cyclical nature. (Ever
see the movie "Groundhog Day"?)

Perhaps this was inappropriate, and hopefully has come at no
expense to Keith (apologies if it has). I certainly didn't
intend to single Keith out as being solely responsible for
perpetuating the thread.

Thanks,

Fred
ftemplin@iprg.nokia.com



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan  6 14:47:04 2003
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12387
	for <ngtrans-archive@lists.ietf.org>; Mon, 6 Jan 2003 14:47:04 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA26330;
	Mon, 6 Jan 2003 11:47:25 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06JlLum025949;
	Mon, 6 Jan 2003 11:47:23 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06JlB16012808
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:47:11 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h06JlBkr012807
	for ngtrans-bumvof58w; Mon, 6 Jan 2003 11:47:11 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h06Jl716012800
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:47:07 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h06Jl7Xq013121
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 11:47:07 -0800 (PST)
Received: from zmamail05.zma.compaq.com (zmamail05.zma.compaq.com [161.114.64.105])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA12532
	for <ngtrans@sunroof.eng.sun.com>; Mon, 6 Jan 2003 12:47:01 -0700 (MST)
Received: from tayexg11.americas.cpqcorp.net (tayexg11.americas.cpqcorp.net [16.103.130.96])
	by zmamail05.zma.compaq.com (Postfix) with ESMTP
	id 052864E39; Mon,  6 Jan 2003 14:46:59 -0500 (EST)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 6 Jan 2003 14:46:59 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Mon, 6 Jan 2003 14:46:59 -0500
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B034BFE93@tayexc13.americas.cpqcorp.net>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1uWV4nCg1oWrzRXy0hVOUraGsZQAAtfQQ
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Fred L. Templin" <ftemplin@IPRG.nokia.com>
Cc: "Keith Moore" <moore@cs.utk.edu>,
        "Marcelo Barbosa Lima" <mlima@cpqd.com.br>, <mc5w@earthlink.net>,
        <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 06 Jan 2003 19:46:59.0866 (UTC) FILETIME=[60951FA0:01C2B5BC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h06Jl716012801
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Bound, Jim" <Jim.Bound@hp.com>
Content-Transfer-Encoding: 8bit

Hi Fred,

Missed the light part.  My apologies.  It is just some are so rude in
email I cannot help but wish them the worst from that view.  And I do.

/jim

 


> -----Original Message-----
> From: Fred L. Templin [mailto:ftemplin@IPRG.nokia.com] 
> Sent: Monday, January 06, 2003 2:35 PM
> To: Bound, Jim
> Cc: Keith Moore; Marcelo Barbosa Lima; mc5w@earthlink.net; 
> ngtrans@sunroof.eng.sun.com
> Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> Hi Jim,
> 
> Bound, Jim wrote:
> > Fred,
> > 
> > I did not think Keiths mail was insulting.
> 
> Exactly why I prefaced my note with "No offense intended";
> just trying to make light of an ongoing discussion that has
> (to me) become almost humerous by its cyclical nature. (Ever 
> see the movie "Groundhog Day"?)
> 
> Perhaps this was inappropriate, and hopefully has come at no 
> expense to Keith (apologies if it has). I certainly didn't 
> intend to single Keith out as being solely responsible for 
> perpetuating the thread.
> 
> Thanks,
> 
> Fred
> ftemplin@iprg.nokia.com
> 
> 



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan  7 05:21:21 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08648
	for <ngtrans-archive@lists.ietf.org>; Tue, 7 Jan 2003 05:21:20 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA14905;
	Tue, 7 Jan 2003 03:22:41 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07AMbXs019723;
	Tue, 7 Jan 2003 02:22:39 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07AMH16019419
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:22:17 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h07AMH4P019418
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 02:22:17 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07AMD16019405
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:22:13 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07AMMuk020484
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:22:22 -0800 (PST)
Received: from barao.cpqd.com.br (barao.cpqd.com.br [200.231.0.47])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA14744
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 03:22:16 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by barao.cpqd.com.br (8.12.5/8.12.5) with SMTP id h07AMI79026805
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 08:22:18 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Tue, 07 Jan 2003 08:22:04 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Tue, 7 Jan 2003 08:21:09 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017E9FAE@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1uWV4nCg1oWrzRXy0hVOUraGsZQAAtfQQAB3z/WA=
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Bound, Jim" <Jim.Bound@hp.com>,
        "Fred L. Templin" <ftemplin@IPRG.nokia.com>
Cc: "Keith Moore" <moore@cs.utk.edu>, <mc5w@earthlink.net>,
        <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h07AME16019406
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


  Folks,

   I think that Keith´s answer did not offend to me. I want only a good debate about IPv6´s subjects. I really believe that is possible to write code STATEFUL to NAT where whatever application can be supported. I believe that all connections/sessions related to one application can be inpesctioned (in application layer)and port numbers and IP address translated like in simple FTP.  Of this way, NAT can provide support to many applications more complex. AGAIN, stateful NAT with application sense can be implemented to support this application. I really dont see reasons to that one NAT applications-specific module can not be implemented. In Linux, for example, exists IRC, Netmeeting and ICQ modules to masquerading. I also believe that few implementation do it. My apologies for my "irresponsible comments about NAT". I only thougth that it was a free debate between civilized people.
Best Regards,

			Marcelo.

-----Mensagem original-----
De: Bound, Jim [mailto:Jim.Bound@hp.com]
Enviada em: segunda-feira, 6 de janeiro de 2003 17:47
Para: Fred L. Templin
Cc: Keith Moore; Marcelo Barbosa Lima; mc5w@earthlink.net;
ngtrans@sunroof.eng.sun.com
Assunto: RE: RES: ReN: (ngtrans) IPv6 tranisition issues


Hi Fred,

Missed the light part.  My apologies.  It is just some are so rude in
email I cannot help but wish them the worst from that view.  And I do.

/jim

 


> -----Original Message-----
> From: Fred L. Templin [mailto:ftemplin@IPRG.nokia.com] 
> Sent: Monday, January 06, 2003 2:35 PM
> To: Bound, Jim
> Cc: Keith Moore; Marcelo Barbosa Lima; mc5w@earthlink.net; 
> ngtrans@sunroof.eng.sun.com
> Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> Hi Jim,
> 
> Bound, Jim wrote:
> > Fred,
> > 
> > I did not think Keiths mail was insulting.
> 
> Exactly why I prefaced my note with "No offense intended";
> just trying to make light of an ongoing discussion that has
> (to me) become almost humerous by its cyclical nature. (Ever 
> see the movie "Groundhog Day"?)
> 
> Perhaps this was inappropriate, and hopefully has come at no 
> expense to Keith (apologies if it has). I certainly didn't 
> intend to single Keith out as being solely responsible for 
> perpetuating the thread.
> 
> Thanks,
> 
> Fred
> ftemplin@iprg.nokia.com
> 
> 



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan  7 05:51:37 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09118
	for <ngtrans-archive@lists.ietf.org>; Tue, 7 Jan 2003 05:51:36 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA22786;
	Tue, 7 Jan 2003 03:52:54 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07Aqmum023903;
	Tue, 7 Jan 2003 02:52:51 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07AqR16019740
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:52:27 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h07AqR2h019739
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 02:52:27 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07AqO16019732
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:52:24 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.Central.Sun.COM [129.147.5.36])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07AqXuk023870
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 02:52:33 -0800 (PST)
Received: from barao.cpqd.com.br (barao.cpqd.com.br [200.231.0.47])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA22625
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 03:52:27 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by barao.cpqd.com.br (8.12.5/8.12.5) with SMTP id h07AqS79028946
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 08:52:28 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Tue, 07 Jan 2003 08:52:15 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Tue, 7 Jan 2003 08:51:20 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017E9FAF@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1t3dIzDGO75+DRT+4Qv5pvGXegQAgXdjg
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h07AqP16019733
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit

  Hi Keith,

>you are completely mistaken.  the NAT does not have sufficient information to perform the >>>conversion even if it is aware of the protocol that the application is using.

   I think that I can to implement a stateful NAT module able to see the several connections in ongoing applications and get these informations. I implemented one Linux Kernel Module to filtering RPC-based services. It was abble to look in communication between portmapper and client RPC and get RPC servers´s port numbers. In this way, the filter creates rules on-the-fly to these services. I believe that be possible make the same to NAT modules.

>almost any distributed application fails in the presence of NAT unless there is a central server >via which communications are routed.  the ones I'm most familiar with are used in distributed >computation: netsolve, globus, pvm.  but SIP has this problem also.

  I think that you are correct to current NAT implementations. But I think that it is possible implement applications-specific NAT. I dont know SIP protocol, but if it is similar to H323, it is possible to implement a special NA module abble to see sinnaling UDP sessions end get port numbers to be used in the call and to do address/port translation. 

  Marcelo.



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan  7 07:30:05 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10994
	for <ngtrans-archive@lists.ietf.org>; Tue, 7 Jan 2003 07:30:05 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA15284;
	Tue, 7 Jan 2003 05:30:27 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07CUNXs004961;
	Tue, 7 Jan 2003 04:30:25 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07CU116020273
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 04:30:01 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h07CU1X9020272
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 04:30:01 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07CTv16020265
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 04:29:57 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.Central.Sun.COM [129.147.5.36])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07CU7Xq004840
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 04:30:07 -0800 (PST)
Received: from grebe.mail.pas.earthlink.net (grebe.mail.pas.earthlink.net [207.217.120.46])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA02483
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 05:30:02 -0700 (MST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org)
	by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18Vspw-0005UO-00; Tue, 07 Jan 2003 04:28:04 -0800
Date: Tue, 7 Jan 2003 07:25:19 -0500
From: Keith Moore <moore@cs.utk.edu>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Cc: moore@cs.utk.edu, Jim.Bound@hp.com, ftemplin@IPRG.nokia.com,
        mc5w@earthlink.net, ngtrans@sunroof.eng.sun.com
Subject: Re: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
Message-Id: <20030107072519.25221467.moore@cs.utk.edu>
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017E9FAE@MAILSRV1.aquarius.cpqd.com.br>
References: <D49EA2F934FFAD45B337C07A9753C00E017E9FAE@MAILSRV1.aquarius.cpqd.com.br>
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>
Content-Transfer-Encoding: 8bit

On Tue, 7 Jan 2003 08:21:09 -0200
"Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:

> 
>   Folks,
> 
>    I think that Keith´s answer did not offend to me. I want only a good
> debate about IPv6´s subjects. I really believe that is possible to write code
> STATEFUL to NAT where whatever application can be supported. I believe that 
> all connections/sessions related to one application can be inpesctioned (in 
> application layer) and port numbers and IP address translated like in 
> simple FTP.  

you are still incorrect.  I am sorry if this sounds impolite or offensive, but 
facts are facts.  Even 3-party FTP fails in the presence of NAT.

think of it this way - if there are more than two hosts involved in an 
application, then it's not necessarily the case that a single NAT can see all 
of the addresses that get passed around between hosts.  if a NAT is between
host A and host B, there may be ways that host A and host B can learn 
addresses for each other without the traffic passing through that NAT.

if you want to discuss this further, please do so in private mail.  it's not
relevant to IPv6, since NATs have no place interfering with communication 
between IPv6 hosts.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Tue Jan  7 10:13:20 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16941
	for <ngtrans-archive@lists.ietf.org>; Tue, 7 Jan 2003 10:13:19 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA22095;
	Tue, 7 Jan 2003 08:14:38 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07FEVum027283;
	Tue, 7 Jan 2003 07:14:34 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07FEA16021012
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 07:14:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h07FEABB021011
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 07:14:10 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h07FE716021004
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 07:14:07 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h07FEHXq001132
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 07:14:17 -0800 (PST)
Received: from zmamail05.zma.compaq.com (zmamail05.zma.compaq.com [161.114.64.105])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA04757
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 07:14:11 -0800 (PST)
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103])
	by zmamail05.zma.compaq.com (Postfix) with ESMTP
	id CD4EE927; Tue,  7 Jan 2003 10:14:10 -0500 (EST)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 7 Jan 2003 10:14:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Tue, 7 Jan 2003 10:14:09 -0500
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B034BFEB7@tayexc13.americas.cpqcorp.net>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK1uWV4nCg1oWrzRXy0hVOUraGsZQAAtfQQAB3z/WAACsty0A==
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>,
        "Fred L. Templin" <ftemplin@IPRG.nokia.com>
Cc: "Keith Moore" <moore@cs.utk.edu>, <mc5w@earthlink.net>,
        <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 07 Jan 2003 15:14:10.0384 (UTC) FILETIME=[6E062500:01C2B65F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h07FE716021005
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Bound, Jim" <Jim.Bound@hp.com>
Content-Transfer-Encoding: 8bit

Folks,

Lets just listen to Christians mail.  Me included.

No comment from me at this point.   I would not advocate the development of state machines in code to support NAT at this point with IPv6 so close though.

Regards,
/jim

 


> -----Original Message-----
> From: Marcelo Barbosa Lima [mailto:mlima@cpqd.com.br] 
> Sent: Tuesday, January 07, 2003 5:21 AM
> To: Bound, Jim; Fred L. Templin
> Cc: Keith Moore; mc5w@earthlink.net; ngtrans@sunroof.eng.sun.com
> Subject: RES: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> 
>   Folks,
> 
>    I think that Keith´s answer did not offend to me. I want 
> only a good debate about IPv6´s subjects. I really believe 
> that is possible to write code STATEFUL to NAT where whatever 
> application can be supported. I believe that all 
> connections/sessions related to one application can be 
> inpesctioned (in application layer)and port numbers and IP 
> address translated like in simple FTP.  Of this way, NAT can 
> provide support to many applications more complex. AGAIN, 
> stateful NAT with application sense can be implemented to 
> support this application. I really dont see reasons to that 
> one NAT applications-specific module can not be implemented. 
> In Linux, for example, exists IRC, Netmeeting and ICQ modules 
> to masquerading. I also believe that few implementation do 
> it. My apologies for my "irresponsible comments about NAT". I 
> only thougth that it was a free debate between civilized 
> people. Best Regards,
> 
> 			Marcelo.
> 
> -----Mensagem original-----
> De: Bound, Jim [mailto:Jim.Bound@hp.com]
> Enviada em: segunda-feira, 6 de janeiro de 2003 17:47
> Para: Fred L. Templin
> Cc: Keith Moore; Marcelo Barbosa Lima; mc5w@earthlink.net; 
> ngtrans@sunroof.eng.sun.com
> Assunto: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> Hi Fred,
> 
> Missed the light part.  My apologies.  It is just some are so 
> rude in email I cannot help but wish them the worst from that 
> view.  And I do.
> 
> /jim
> 
>  
> 
> 
> > -----Original Message-----
> > From: Fred L. Templin [mailto:ftemplin@IPRG.nokia.com]
> > Sent: Monday, January 06, 2003 2:35 PM
> > To: Bound, Jim
> > Cc: Keith Moore; Marcelo Barbosa Lima; mc5w@earthlink.net; 
> > ngtrans@sunroof.eng.sun.com
> > Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> > 
> > 
> > Hi Jim,
> > 
> > Bound, Jim wrote:
> > > Fred,
> > > 
> > > I did not think Keiths mail was insulting.
> > 
> > Exactly why I prefaced my note with "No offense intended"; 
> just trying 
> > to make light of an ongoing discussion that has (to me) 
> become almost 
> > humerous by its cyclical nature. (Ever see the movie 
> "Groundhog Day"?)
> > 
> > Perhaps this was inappropriate, and hopefully has come at no
> > expense to Keith (apologies if it has). I certainly didn't 
> > intend to single Keith out as being solely responsible for 
> > perpetuating the thread.
> > 
> > Thanks,
> > 
> > Fred
> > ftemplin@iprg.nokia.com
> > 
> > 
> 
> 



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 01:50:02 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17142
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 01:50:01 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA01355;
	Tue, 7 Jan 2003 22:50:34 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h086oOum029310;
	Tue, 7 Jan 2003 22:50:29 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h086o416024514
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 22:50:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h086o41C024513
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 22:50:04 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h086o216024506
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 22:50:02 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h086oCuk029286
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 22:50:12 -0800 (PST)
Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA21756
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:50:06 -0700 (MST)
Received: from 1cust219.tnt3.cleveland3.oh.da.uu.net ([65.238.96.219] helo=k6500a)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18WA2P-00010m-00
	for ngtrans@sunroof.eng.sun.com; Tue, 07 Jan 2003 22:50:06 -0800
Message-ID: <002401c2b6e3$9b910880$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br> <20030106125124.18a5d0d7.moore@cs.utk.edu> <3E19D30F.1060803@iprg.nokia.com>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Wed, 8 Jan 2003 02:00:18 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Fred L. Templin" <ftemplin@IPRG.nokia.com>
To: "Keith Moore" <moore@cs.utk.edu>
Cc: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>; <mc5w@earthlink.net>;
<ngtrans@sunroof.eng.sun.com>
Sent: Monday, January 06, 2003 2:03 PM
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues


> Keith,
>
> No offense intended, but I am beginning to suspect that you have
> somehow implemented an "automatic insult generator" in your mailer
> that is triggered anytime someone mentions the word "NAT". :^}
>
> Fred Templin
> ftemplin@iprg.nokia.com
>
> Keith Moore wrote:
> > On Mon, 6 Jan 2003 08:56:20 -0200
> > "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> >
> >
> >>  I think that NAT is a good workaround and it can be done to support
all aplications
> >
> >
> > you are mistaken.  your statement is completely and utterly incorrect.
> >
> > Keith
>
>
>

Keith Moore SHOULD have written:

NAT breaks Unix applications but not Windows applications.

My opinion: the original purpose of TCP port numbers and UDP port numbers
was to allow more than one process or user to share the same connection or
other resource. For instance, when two or more people access a web site each
one gets a one or more port numbers to go with the site's address. This way,
the web site only needs to have ONE address.

LIkewise, NAT essentially does the same thing on the other end by allowing a
LAN or other subnet to pretend to be a single timesharing machine with only
ONE IPv4 address. This is much like how if I open a 2nd instance of Internet
Explorer on my browser (which currently does not have NAT software) it uses
port 81 instead of port 80. That is, the 2nd instance figures that somebody
else grabbed port 80 first so it just goes and finds another open port. NAT
is just simply an extension of existing concepts that were first applied to
mainframes that were connected to Arpanet.

I have played around with enough firewalls and NAT packages to know that
software quality varies all over the place. As for the claim that NAT breaks
applications there is sometimes a problem with pushing the right buttons to
get it to work. Norton Antivirus 2002 for instance will crash some web pages
because I have script blocking enabled - it is not really possible to tell
if a script is friendly or malicious. Likewise, Popup Stopper has an
override feature to allow friendly popups.

Mike Cole, mc5w@earthlink.net




From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 02:09:22 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22565
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 02:09:22 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA11417;
	Tue, 7 Jan 2003 23:11:07 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h087B4um002249;
	Tue, 7 Jan 2003 23:11:05 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h087Ai16024649
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:10:44 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h087AiK9024648
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 23:10:44 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h087Af16024641
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:10:41 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h087Apuk002213
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:10:51 -0800 (PST)
Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA29318
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 00:10:46 -0700 (MST)
Received: from 1cust219.tnt3.cleveland3.oh.da.uu.net ([65.238.96.219] helo=k6500a)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18WAMP-00025y-00
	for ngtrans@sunroof.eng.sun.com; Tue, 07 Jan 2003 23:10:45 -0800
Message-ID: <006101c2b6e6$7f95eb20$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References: <9C422444DE99BC46B3AD3C6EAFC9711B034BFEB7@tayexc13.americas.cpqcorp.net>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Wed, 8 Jan 2003 02:20:59 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Bound, Jim" <Jim.Bound@hp.com>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>; "Fred L. Templin"
<ftemplin@IPRG.nokia.com>
Cc: "Keith Moore" <moore@cs.utk.edu>; <mc5w@earthlink.net>;
<ngtrans@sunroof.eng.sun.com>
Sent: Tuesday, January 07, 2003 10:14 AM
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues


> Folks,
>
> Lets just listen to Christians mail.  Me included.
>
> No comment from me at this point.   I would not advocate the development
of state machines in code to support NAT at this point with IPv6 so close
though.
>
> Regards,
> /jim bound

IPv6 is still a long ways from production deployment. Some protocols are
still in the experimental stage or pre-experimental stage. Likewise, I have
not found a supported IPv6 dual stack implementation for Windows 2000 not
that I have no idea if I can run it through Earthlink.

There is also the problem that companies want extensive experience and they
want people to get experience from an invisible gremlin named Not Me. There
was even a company here in Cleveland who this past June advertised that they
wanted somebody with 2 years of experience with Windows 2000 - they were too
stupid to realize that Windows 2000 was not really released until October of
2000. Corporate stupidgroupthink will probably stretch out implementation of
IPv6 for possibly as long as 30 years!!!!




From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 02:55:54 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12805
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 02:55:54 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA13372;
	Wed, 8 Jan 2003 00:58:30 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h087wQum009088;
	Tue, 7 Jan 2003 23:58:28 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h087w916024816
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:58:09 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h087w8EC024815
	for ngtrans-bumvof58w; Tue, 7 Jan 2003 23:58:08 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h087w616024808
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:58:06 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h087wEXq018693
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Jan 2003 23:58:14 -0800 (PST)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA24141
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 00:58:09 -0700 (MST)
Received: from INET-VRS-02.redmond.corp.microsoft.com ([157.54.8.110]) by mail2.microsoft.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 7 Jan 2003 23:58:08 -0800
Received: from 157.54.8.109 by INET-VRS-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 07 Jan 2003 23:58:08 -0800
Received: from red-msg-04.redmond.corp.microsoft.com ([157.54.12.74]) by INET-HUB-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3710.0);
	 Tue, 7 Jan 2003 23:58:08 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Tue, 7 Jan 2003 23:58:07 -0800
Message-ID: <CB7153628BD3724096258CBFD70AA891066F25A9@red-msg-04.redmond.corp.microsoft.com>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK25Aaqm07SASymSES0tkRldjseGgAAVMTA
From: "Brian Zill" <bzill@microsoft.com>
To: "Michael R. Cole" <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 08 Jan 2003 07:58:08.0107 (UTC) FILETIME=[AE813BB0:01C2B6EB]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h087w616024809
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Brian Zill" <bzill@microsoft.com>
Content-Transfer-Encoding: 8bit

> Keith Moore SHOULD have written:
> 
> NAT breaks Unix applications but not Windows applications.

Er, no.  There is nothing magical about your choice of operating system
with regards to Internet architecture.  Maybe you've been lucky with the
particular applications you use, but I can guarantee you that there are
both Unix and Windows applications (and versions of the same application
for the different platforms) that do not work through a NAT.  It's the
functionality of the app, not the platform on which it runs, that
matters here.

> My opinion: the original purpose of TCP port numbers and UDP 
> port numbers was to allow more than one process or user to 
> share the same connection or other resource.

> LIkewise, NAT essentially does the same thing on the other 
> end by allowing a LAN or other subnet to pretend to be a 
> single timesharing machine with only ONE IPv4 address.

NAT is not equivalent to how a node may multiplex the use of one IP
address among multiple data streams via the disambiguating port numbers.
NATs create a new private address space and expose it to applications as
if it were their real address.  If apps pass their (private) view of
their address around in the data stream to other nodes (which may be
outside of the private space, or worse, in a different instantiation of
the same private space), bad things happen.  Yes, some NATs try to
mitigate these problems by recognizing packets from such apps and
modifying the data stream -- but this is prone to error.  Also, the NAT
needs to know about every such app, making it hard to deploy new apps.
There are various other NAT traversal strategies out there, but none
fully solve the problem.  My opinion: the right way to fix the problems
caused by NAT is to deploy IPv6 and thus restore the Internet to the
state it was before NATs broke it.

--Brian



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 08:51:21 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19769
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 08:51:20 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA06462;
	Wed, 8 Jan 2003 06:54:06 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08Druum027805;
	Wed, 8 Jan 2003 05:54:00 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08Drb16027309
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 8 Jan 2003 05:53:37 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h08DrbMG027308
	for ngtrans-bumvof58w; Wed, 8 Jan 2003 05:53:37 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08DrX16027301
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 05:53:33 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08Drguk027754
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 05:53:43 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA06171
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 05:53:37 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19728;
	Wed, 8 Jan 2003 08:50:18 -0500 (EST)
Message-Id: <200301081350.IAA19728@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-isatap-09.txt
Date: Wed, 08 Jan 2003 08:50:18 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Intra-Site Automatic Tunnel Addressing Protocol 
                          (ISATAP)
	Author(s)	: F. Templin, T. Gleeson, M. Talwar, D. Thaler
	Filename	: draft-ietf-ngtrans-isatap-09.txt
	Pages		: 22
	Date		: 2003-1-7
	
This document specifies an Intra-Site Automatic Tunnel Addressing
Protocol (ISATAP) that connects IPv6 hosts and routers within IPv4
sites.  ISATAP treats the site's IPv4 infrastructure as a link layer
for IPv6 with no requirement for IPv4 multicast.  ISATAP enables
intra-site automatic IPv6-in-IPv4 tunneling whether globally assigned
or private IPv4 addresses are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-isatap-09.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ietf-ngtrans-isatap-09.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-ietf-ngtrans-isatap-09.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.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-1-7161109.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-isatap-09.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-isatap-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-1-7161109.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 11:40:13 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24342
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 11:40:12 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA18924;
	Wed, 8 Jan 2003 09:42:47 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08GghXs021320;
	Wed, 8 Jan 2003 08:42:45 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08GgO16028813
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 8 Jan 2003 08:42:24 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h08GgOG8028812
	for ngtrans-bumvof58w; Wed, 8 Jan 2003 08:42:24 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08GgL16028805
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 08:42:21 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08GgUXq021249
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 08:42:30 -0800 (PST)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA26680
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 08:42:25 -0800 (PST)
Received: from INET-VRS-02.redmond.corp.microsoft.com ([157.54.8.110]) by mail2.microsoft.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Jan 2003 08:42:24 -0800
Received: from 157.54.8.23 by INET-VRS-02.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 08 Jan 2003 08:42:24 -0800
Received: from RED-IMC-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Wed, 8 Jan 2003 08:42:24 -0800
Received: from WIN-IMC-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by RED-IMC-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.5600);
	 Wed, 8 Jan 2003 08:42:24 -0800
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.82]) by WIN-IMC-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3710.0);
	 Wed, 8 Jan 2003 08:42:24 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Wed, 8 Jan 2003 08:42:23 -0800
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA1D2ADF@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: RES: ReN: (ngtrans) IPv6 tranisition issues
Thread-Index: AcK24rfRZ+YqJt/gT4esdL0JHDJMzQAULC4Q
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Michael R. Cole" <mc5w@earthlink.net>, <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 08 Jan 2003 16:42:24.0043 (UTC) FILETIME=[EBB427B0:01C2B734]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h08GgL16028806
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Christian Huitema" <huitema@windows.microsoft.com>
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: Michael R. Cole [mailto:mc5w@earthlink.net]
> Sent: Tuesday, January 07, 2003 11:00 PM
> To: ngtrans@sunroof.eng.sun.com
> Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> ----- Original Message -----
> From: "Fred L. Templin" <ftemplin@IPRG.nokia.com>
> To: "Keith Moore" <moore@cs.utk.edu>
> Cc: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>; <mc5w@earthlink.net>;
> <ngtrans@sunroof.eng.sun.com>
> Sent: Monday, January 06, 2003 2:03 PM
> Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> 
> 
> > Keith,
> >
> > No offense intended, but I am beginning to suspect that you have
> > somehow implemented an "automatic insult generator" in your mailer
> > that is triggered anytime someone mentions the word "NAT". :^}
> >
> > Fred Templin
> > ftemplin@iprg.nokia.com
> >
> > Keith Moore wrote:
> > > On Mon, 6 Jan 2003 08:56:20 -0200
> > > "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> > >
> > >
> > >>  I think that NAT is a good workaround and it can be done to
support
> all aplications
> > >
> > >
> > > you are mistaken.  your statement is completely and utterly
incorrect.
> > >
> > > Keith
> >
> >
> >
> 
> Keith Moore SHOULD have written:
> 
> NAT breaks Unix applications but not Windows applications.

Uh? For one, many networking application are platform independent, and
are equally broken on Unix and Windows. Then, one of the reason
Microsoft is pushing IPv6 is precisely because many high profile Windows
applications are broken by NAT. Examples of broken applications are:
Netmeeting; remote access to your home computer using "terminal server"
or "remote assistance"; hosting a server on your home PC for DirectPlay
games; the Voice over IP, video over IP, file transfer and application
features of Messenger. These are just examples. 

Obviously, we at Microsoft are not sitting on our hands watching
applications fail, and we have developed workarounds for some scenarios.
In particular, we can traverse those NATs that support the UPNP
"Internet Gateway Device" profile. But these workarounds are brittle;
they don't work in all scenarios, they make application programming,
testing and maintenance more complex; and they tend to generate calls to
the support line. In particular, there is no solution in double NAT
scenarios.

-- Christian Huitema



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan  8 17:45:04 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11089
	for <ngtrans-archive@lists.ietf.org>; Wed, 8 Jan 2003 17:45:04 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA01511;
	Wed, 8 Jan 2003 15:47:27 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08MlNXs020160;
	Wed, 8 Jan 2003 14:47:25 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08Ml316001998
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 8 Jan 2003 14:47:03 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h08Ml3cP001997
	for ngtrans-bumvof58w; Wed, 8 Jan 2003 14:47:03 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h08Ml016001990
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 14:47:00 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h08Ml9uk018034
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 14:47:09 -0800 (PST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA04516
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Jan 2003 15:47:03 -0700 (MST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA10757;
	Wed, 8 Jan 2003 14:47:02 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h08Ml1104837;
	Wed, 8 Jan 2003 14:47:01 -0800
X-mProtect: <200301082247> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.19.68.122, claiming to be "dadhcp-172019068122.americas.nokia.com")
	by darkstar.iprg.nokia.com smtpdmTOtYx; Wed, 08 Jan 2003 14:46:59 PST
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
From: Rod Van Meter <Rod.VanMeter@nokia.com>
To: Marcelo Barbosa Lima <mlima@cpqd.com.br>
Cc: "Michael R. Cole" <mc5w@earthlink.net>, ngtrans@sunroof.eng.sun.com
In-Reply-To: <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
References: 
	 <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br>
Content-Type: text/plain; charset=ISO-8859-1
Organization: Nokia Networks
Message-Id: <1042065674.1435.575.camel@dadhcp-172019068122.americas.nokia.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.0 
Date: 08 Jan 2003 14:41:15 -0800
Content-Transfer-Encoding: 8bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Rod Van Meter <Rod.VanMeter@nokia.com>
Content-Transfer-Encoding: 8bit

> -----Mensagem original-----
> De: Michael R. Cole [mailto:mc5w@earthlink.net]
> Enviada em: terga-feira, 31 de dezembro de 2002 09:20
> Para: ngtrans@sunroof.eng.sun.com
> Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues 
> 
> 
> Your claim would also say that a timesharing system with only 1 public IPv4
> address would not work which is what a cone NAT mimics. That is, a cone NAT
> fools that public Internet into thinking that a LAN or other subnet is in
> actuality a single machine.

That's a gross oversimplification that eliminates the actual problem, so
of course it doesn't sound bad when you put it that way.

When a computer has a global address, you open a socket and get a port,
and you can tell anyone anywhere in the world using any communications
medium that they can reach you there.  You can call someone on the
telephone and tell them, "My cool new game server is at port 1982 on
1.2.3.4!" and it works.  You can send the info via snail mail, and it
works.  One friend can tell another friend, and it works.

With NAT, you can't do that, end of story.  The NAT box HIDES
INFORMATION from BOTH ENDS of the conversation, so you can't know what
the people at the other end see your address and port number to be.

It also does not allow YOU to hide information for protocols it expects
to affect.  You can't do FTP over IPSec, because then the NAT box can't
reach into the FTP packets and modify them.

I would have thought that all of this was pretty well understood by
now...

		--Rod




From owner-ngtrans@sunroof.eng.sun.com  Thu Jan  9 09:06:41 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10080
	for <ngtrans-archive@lists.ietf.org>; Thu, 9 Jan 2003 09:06:41 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA26144;
	Thu, 9 Jan 2003 07:09:27 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09E9OXs015104;
	Thu, 9 Jan 2003 06:09:26 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09E9616005552
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:09:06 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h09E96H2005551
	for ngtrans-bumvof58w; Thu, 9 Jan 2003 06:09:06 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09E9316005544
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:09:03 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09E9Buk004885
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:09:12 -0800 (PST)
Received: from d12lmsgate-5.de.ibm.com (d12lmsgate-5.de.ibm.com [194.196.100.238])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA08535
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 07:09:05 -0700 (MST)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-5.de.ibm.com (8.12.3/8.12.3) with ESMTP id h09E8vqf011280;
	Thu, 9 Jan 2003 15:08:57 +0100
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140])
	by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id h09E8vTL136424;
	Thu, 9 Jan 2003 15:08:57 +0100
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03)
          id AA18858 from <brian@hursley.ibm.com>; Thu, 9 Jan 2003 15:08:56 +0100
Message-Id: <3E1D8252.6A77D197@hursley.ibm.com>
Date: Thu, 09 Jan 2003 15:08:18 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Marcelo Barbosa Lima <mlima@cpqd.com.br>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) IPv6 tranisition issues
References: <D49EA2F934FFAD45B337C07A9753C00E017E9FAF@MAILSRV1.aquarius.cpqd.com.br>
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

Marcelo Barbosa Lima wrote:
...
> 
>   I think that you are correct to current NAT implementations. But I think that it is possible implement applications-specific NAT. 

That's not a NAT. That's an application level gateway (ALG) including 
NAT functionality.

This requires every NAT-ALG vendor to develop new software kludges for
every new application. Or to put it another way, it prevents innovative
applications since they cannot penetrate existing NATs. There is no
doubt that NAT is the single biggest barrier to innovation today.

This is of course why we started developing IPv6 in 1994, so can we
please get back to that, instead of continuing to waste resources
discussing NAT?

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Thu Jan  9 09:25:04 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11055
	for <ngtrans-archive@lists.ietf.org>; Thu, 9 Jan 2003 09:25:04 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA08759;
	Thu, 9 Jan 2003 07:28:03 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09ES0Xs022547;
	Thu, 9 Jan 2003 06:28:02 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09ERc16005740
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:27:38 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h09ERcaD005739
	for ngtrans-bumvof58w; Thu, 9 Jan 2003 06:27:38 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09ERZ16005732
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:27:35 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09ERhuk008309
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:27:43 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA21260
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 06:27:36 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10962;
	Thu, 9 Jan 2003 09:24:17 -0500 (EST)
Message-Id: <200301091424.JAA10962@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-isatap-10.txt
Date: Thu, 09 Jan 2003 09:24:17 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Intra-Site Automatic Tunnel Addressing Protocol 
                          (ISATAP)
	Author(s)	: F. Templin, T. Gleeson, M. Talwar, D. Thaler
	Filename	: draft-ietf-ngtrans-isatap-10.txt
	Pages		: 22
	Date		: 2003-1-8
	
This document specifies an Intra-Site Automatic Tunnel Addressing
Protocol (ISATAP) that connects IPv6 hosts and routers within IPv4
sites.  ISATAP treats the site's IPv4 infrastructure as a link layer
for IPv6 with no requirement for IPv4 multicast.  ISATAP enables
intra-site automatic IPv6-in-IPv4 tunneling whether globally assigned
or private IPv4 addresses are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-isatap-10.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ietf-ngtrans-isatap-10.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-ietf-ngtrans-isatap-10.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.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-1-9092441.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-isatap-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-isatap-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-1-9092441.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jan  9 13:13:52 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19571
	for <ngtrans-archive@lists.ietf.org>; Thu, 9 Jan 2003 13:13:51 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA02050;
	Thu, 9 Jan 2003 11:15:20 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09IErum005591;
	Thu, 9 Jan 2003 10:15:04 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09IEX16008522
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Thu, 9 Jan 2003 10:14:34 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h09IEXrI008521
	for ngtrans-bumvof58w; Thu, 9 Jan 2003 10:14:33 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h09IET16008514
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 10:14:31 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h09IEbXq021644
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 10:14:37 -0800 (PST)
Received: from srv58.asomi.net (srv58.asomi.net [216.55.177.58])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA25945
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 10:14:32 -0800 (PST)
Received: from 192.168.0.2 (rp.asomi.net [64.144.5.25])
	by srv58.asomi.net (8.9.2/8.9.2) with ESMTP id MAA07966
	for <ngtrans@sunroof.eng.sun.com>; Thu, 9 Jan 2003 12:14:28 -0600 (CST)
Date: Thu,  9 Jan 2003 12:14:57 -0600
From: Caitlin Bestler <caitlinb@rp.asomi.net>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
To: ngtrans@sunroof.eng.sun.com
X-Priority: 3
Message-ID: <r01050300-1023-42F7CCBA23FE11D79C1E003065D48EE0@[192.168.0.2]>
MIME-Version: 1.0
Content-Type: text/plain; Charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: Mailsmith 1.5.3 (Blindsider)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Caitlin Bestler <caitlinb@rp.asomi.net>
Content-Transfer-Encoding: 7bit

On 1/8/03, Rod Van Meter wrote:

>> -----Mensagem original-----
>> De: Michael R. Cole [mailto:mc5w@earthlink.net]
>> Enviada em: terga-feira, 31 de dezembro de 2002 09:20
>> Para: ngtrans@sunroof.eng.sun.com
>> Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues 
>> 
>> 
>> Your claim would also say that a timesharing system with
>> only 1 public IPv4 address would not work which is what
>> a cone NAT mimics. That is, a cone NAT fools that public
>> Internet into thinking that a LAN or other subnet is in
>> actuality a single machine.
>
>That's a gross oversimplification that eliminates the
>actual problem, so of course it doesn't sound bad when you
>put it that way.
>
>When a computer has a global address, you open a socket
>and get a port, and you can tell anyone anywhere in the
>world using any communications medium that they can reach
>you there.  You can call someone on the telephone and tell
>them, "My cool new game server is at port 1982 on
>1.2.3.4!" and it works.  You can send the info via snail
>mail, and it works.  One friend can tell another friend,
>and it works.
>
Virtually every NAT device I have seen is fully capable of
statically configuring any port to pass-thru to a specific
machine. In other words, the single virtual machine can
offer it service on any port and then use any of its
component machines to implement that service.

So the statement that a NAT creates a single virtual machine
is both very accurate, and highlights very precisely its
limitations.

The next question is how well that Virtual Machine
communicates internally. There are indeed NATs that have no
mechanism to dynamically determine the external port
associated with a given connection, or to dynamically create
a mapping. That is indeed a poor interface, but to be fair
it is a poor interface *within* the virtual machine. There
is nothing wrong with the interface presented to the public
Internet. The left hand not communicating with the right
hand is something any Internet host can achieve, whether it
is composed of a single or multiple machines.

The real point is not that "NAT is evil". There are
legitimate reasons for presenting a single virtual machine
to the public network. Rather the issue is that networks are
forced to use IPv4 NAT to solve other problems such as a
shortage of public IPv4 addresses and keeping the identity
of specific machines within a private network confidential.

NAT "breaks" applications when the hosts it is masquerading
are not actually part of an integrated whole. Properly
deployed, IPv6 allows each host within a private network to
have permanent and/or temporary public addresses as
required.

I believe NAT bashing is counter-productive to IPv6
deployment. Too many comments make it sound as though IPv6
advocates believe that only fools would use a NAT. A lot of
non-fools had very valid reasons to deploy NAT. The best way
to convince them that IPv6 offers better solutions to those
problems is by starting with acknowleding their legitimate
problems and understanding why they chose to deploy NATs in
the first place.

Caitlin Bestler
http://asomi.com/CaitlinBestler/


From owner-ngtrans@sunroof.eng.sun.com  Fri Jan 10 04:00:22 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21323
	for <ngtrans-archive@lists.ietf.org>; Fri, 10 Jan 2003 04:00:21 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA29301;
	Fri, 10 Jan 2003 02:03:01 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A92oum003230;
	Fri, 10 Jan 2003 01:02:55 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A92U16011724
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:02:30 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0A92UrI011723
	for ngtrans-bumvof58w; Fri, 10 Jan 2003 01:02:30 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A92S16011716
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:02:28 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.Central.Sun.COM [129.147.5.36])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A92auk003117
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:02:36 -0800 (PST)
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA26689
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 02:02:30 -0700 (MST)
Received: from 1cust197.tnt3.cleveland3.oh.da.uu.net ([65.238.96.197] helo=k6500a)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18Wv3d-0004b3-00
	for ngtrans@sunroof.eng.sun.com; Fri, 10 Jan 2003 01:02:30 -0800
Message-ID: <002301c2b888$735e2d10$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References: <DAC3FCB50E31C54987CD10797DA511BA1D2ADF@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Fri, 10 Jan 2003 04:12:49 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Michael R. Cole" <mc5w@earthlink.net>; <ngtrans@sunroof.eng.sun.com>
Sent: Wednesday, January 08, 2003 11:42 AM
Subject: RE: RES: ReN: (ngtrans) IPv6 tranisition issues


>
>
> > -----Original Message-----
> > From: Michael R. Cole [mailto:mc5w@earthlink.net]
> > Sent: Tuesday, January 07, 2003 11:00 PM
> > To: ngtrans@sunroof.eng.sun.com
> > Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> >
> >
> > ----- Original Message -----
> > From: "Fred L. Templin" <ftemplin@IPRG.nokia.com>
> > To: "Keith Moore" <moore@cs.utk.edu>
> > Cc: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>; <mc5w@earthlink.net>;
> > <ngtrans@sunroof.eng.sun.com>
> > Sent: Monday, January 06, 2003 2:03 PM
> > Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
> >
> >
> > > Keith,
> > >
> > > No offense intended, but I am beginning to suspect that you have
> > > somehow implemented an "automatic insult generator" in your mailer
> > > that is triggered anytime someone mentions the word "NAT". :^}
> > >
> > > Fred Templin
> > > ftemplin@iprg.nokia.com
> > >
> > > Keith Moore wrote:
> > > > On Mon, 6 Jan 2003 08:56:20 -0200
> > > > "Marcelo Barbosa Lima" <mlima@cpqd.com.br> wrote:
> > > >
> > > >
> > > >>  I think that NAT is a good workaround and it can be done to
> support
> > all aplications
> > > >
> > > >
> > > > you are mistaken.  your statement is completely and utterly
> incorrect.
> > > >
> > > > Keith
> > >
> > >
> > >
> >
> > Keith Moore SHOULD have written:
> >
> > NAT breaks Unix applications but not Windows applications.
>
> Uh? For one, many networking application are platform independent, and
> are equally broken on Unix and Windows. Then, one of the reason
> Microsoft is pushing IPv6 is precisely because many high profile Windows
> applications are broken by NAT. Examples of broken applications are:
> Netmeeting; remote access to your home computer using "terminal server"
> or "remote assistance"; hosting a server on your home PC for DirectPlay
> games; the Voice over IP, video over IP, file transfer and application
> features of Messenger. These are just examples.
>
> Obviously, we at Microsoft are not sitting on our hands watching
> applications fail, and we have developed workarounds for some scenarios.
> In particular, we can traverse those NATs that support the UPNP
> "Internet Gateway Device" profile. But these workarounds are brittle;
> they don't work in all scenarios, they make application programming,
> testing and maintenance more complex; and they tend to generate calls to
> the support line. In particular, there is no solution in double NAT
> scenarios.
>
> -- Christian Huitema
>

The difference between you and Keith is that Keith was NOT willing to
mention which applications and NAT box protocols are problematic. It was as
if he were pulling his reasoning out of thin air and just not bothering to
cite some examples. You also gave me some insight as to why I have been able
to get Sygate Home Network to work very well and Wingate refused to work
with any of my applications. What I have noticed is that the better NAT
software uses both client and server-gateway modules. Is that what is needed
to implement Internet Gateway Device protocol?

Alas, I do not use Netmeeting and I do not have enough bandwidth to use
VOIP. I am also not too crazy allowing remote access to my computer. I am
also willing to bet that most residential NAT box will not support a server
but if you really want to run a web page you need to hire a server farm or
something like that anyways.

Firewalls and popup stoppers also break applications but in these cases the
idea is to deliberately break applications - one time General Motors Finance
thought it would be really cute if they highjacked my computer.

Thanks,

MIke Cole, mc5w@earthlink.net




From owner-ngtrans@sunroof.eng.sun.com  Fri Jan 10 04:16:28 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21698
	for <ngtrans-archive@lists.ietf.org>; Fri, 10 Jan 2003 04:16:28 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA02062;
	Fri, 10 Jan 2003 02:19:10 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9J6um005912;
	Fri, 10 Jan 2003 01:19:08 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9IZ16012061
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:18:35 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0A9IZT7012060
	for ngtrans-bumvof58w; Fri, 10 Jan 2003 01:18:35 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9IW16012053
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:18:32 -0800 (PST)
Received: from pheriche.sun.com (pheriche.Central.Sun.COM [129.147.5.34])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9IeXq001212
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:18:40 -0800 (PST)
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA01710
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 02:18:35 -0700 (MST)
Received: from 1cust197.tnt3.cleveland3.oh.da.uu.net ([65.238.96.197] helo=k6500a)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18WvJC-0006eB-00
	for ngtrans@sunroof.eng.sun.com; Fri, 10 Jan 2003 01:18:34 -0800
Message-ID: <004101c2b88a$b2c5a490$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References:  <D49EA2F934FFAD45B337C07A9753C00E017F55DC@MAILSRV1.aquarius.cpqd.com.br> <1042065674.1435.575.camel@dadhcp-172019068122.americas.nokia.com>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Fri, 10 Jan 2003 04:28:55 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Rod Van Meter" <Rod.VanMeter@nokia.com>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Cc: "Michael R. Cole" <mc5w@earthlink.net>; <ngtrans@sunroof.eng.sun.com>
Sent: Wednesday, January 08, 2003 5:41 PM
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues


> > -----Mensagem original-----
> > De: Michael R. Cole [mailto:mc5w@earthlink.net]
> > Enviada em: terga-feira, 31 de dezembro de 2002 09:20
> > Para: ngtrans@sunroof.eng.sun.com
> > Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues
> >
> >
> > Your claim would also say that a timesharing system with only 1 public
IPv4
> > address would not work which is what a cone NAT mimics. That is, a cone
NAT
> > fools that public Internet into thinking that a LAN or other subnet is
in
> > actuality a single machine.
>
> That's a gross oversimplification that eliminates the actual problem, so
> of course it doesn't sound bad when you put it that way.
>
> When a computer has a global address, you open a socket and get a port,
> and you can tell anyone anywhere in the world using any communications
> medium that they can reach you there.  You can call someone on the
> telephone and tell them, "My cool new game server is at port 1982 on
> 1.2.3.4!" and it works.  You can send the info via snail mail, and it
> works.  One friend can tell another friend, and it works.
>
> With NAT, you can't do that, end of story.  The NAT box HIDES
> INFORMATION from BOTH ENDS of the conversation, so you can't know what
> the people at the other end see your address and port number to be.
>
> It also does not allow YOU to hide information for protocols it expects
> to affect.  You can't do FTP over IPSec, because then the NAT box can't
> reach into the FTP packets and modify them.
>
> I would have thought that all of this was pretty well understood by
> now...
>
> --Rod
>
>
>

Well of course it was an oversimplification but then the NAT box software
that I did get to work on my home network (on a trial basis) seemed to be a
lot smarter than one other that I tried. There is also a commercial grade
NAT+firewall+gateway software package on the market that does have versions
of ping and traceroute that do allow you to find out what address+port
combinations the box is presenting to other people. It is also about twice
the cost (for the same number of users) of the cheapies that are sold for
residential use.

Right now, my budget levels are such that I am not doing that much playing
around with software packages to see how well they work. The only
application that I have for NAT right now is to run Atomic Clock Sync which
does not justify the expense. I would also rather wait for a better
connectivity package that would allow an IPv6 router to run in parallel with
the NAT functionality so that I do not end up buying software twice.

MIke Cole




From owner-ngtrans@sunroof.eng.sun.com  Fri Jan 10 04:21:48 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21829
	for <ngtrans-archive@lists.ietf.org>; Fri, 10 Jan 2003 04:21:46 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA11176;
	Fri, 10 Jan 2003 02:24:45 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9Ofum006829;
	Fri, 10 Jan 2003 01:24:43 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9Nt16012225
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:23:55 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0A9NtPI012224
	for ngtrans-bumvof58w; Fri, 10 Jan 2003 01:23:55 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9Nq16012217
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:23:53 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9O1uk006667
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:24:01 -0800 (PST)
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA06035
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:23:56 -0800 (PST)
Received: from 1cust197.tnt3.cleveland3.oh.da.uu.net ([65.238.96.197] helo=k6500a)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18WvON-00021S-00
	for ngtrans@sunroof.eng.sun.com; Fri, 10 Jan 2003 01:23:55 -0800
Message-ID: <004701c2b88b$72392db0$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References: <D49EA2F934FFAD45B337C07A9753C00E017E9FAF@MAILSRV1.aquarius.cpqd.com.br> <3E1D8252.6A77D197@hursley.ibm.com>
Subject: Re: (ngtrans) IPv6 tranisition issues
Date: Fri, 10 Jan 2003 04:34:15 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Brian E Carpenter" <brian@hursley.ibm.com>
To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Cc: <ngtrans@sunroof.eng.sun.com>
Sent: Thursday, January 09, 2003 9:08 AM
Subject: Re: (ngtrans) IPv6 tranisition issues


> Marcelo Barbosa Lima wrote:
> ...
> >
> >   I think that you are correct to current NAT implementations. But I
think that it is possible implement applications-specific NAT.
>
> That's not a NAT. That's an application level gateway (ALG) including
> NAT functionality.
>
> This requires every NAT-ALG vendor to develop new software kludges for
> every new application. Or to put it another way, it prevents innovative
> applications since they cannot penetrate existing NATs. There is no
> doubt that NAT is the single biggest barrier to innovation today.
>
> This is of course why we started developing IPv6 in 1994, so can we
> please get back to that, instead of continuing to waste resources
> discussing NAT?
>
>    Brian
>

Thanks. I was starting to suspect that there was another kind of box that
performs some NAT functions but without creating as many headaches. That
would explain why one of the packages that I tried worked so well.

MIke Cole




From owner-ngtrans@sunroof.eng.sun.com  Fri Jan 10 04:35:50 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22167
	for <ngtrans-archive@lists.ietf.org>; Fri, 10 Jan 2003 04:35:49 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA13493;
	Fri, 10 Jan 2003 02:37:31 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9bSum008845;
	Fri, 10 Jan 2003 01:37:30 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9b816012478
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:37:08 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0A9b8xN012477
	for ngtrans-bumvof58w; Fri, 10 Jan 2003 01:37:08 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0A9b616012470
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:37:06 -0800 (PST)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0A9bEXq004049
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:37:14 -0800 (PST)
Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA27489
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Jan 2003 01:37:09 -0800 (PST)
Received: from 1cust197.tnt3.cleveland3.oh.da.uu.net ([65.238.96.197] helo=k6500a)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 18Wvb9-0001PL-00
	for ngtrans@sunroof.eng.sun.com; Fri, 10 Jan 2003 01:37:08 -0800
Message-ID: <009901c2b88d$4aa322e0$ca00a8c0@k6500a>
From: "Michael R. Cole" <mc5w@earthlink.net>
To: <ngtrans@sunroof.eng.sun.com>
References: <r01050300-1023-42F7CCBA23FE11D79C1E003065D48EE0@[192.168.0.2]>
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues
Date: Fri, 10 Jan 2003 04:47:28 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Michael R. Cole" <mc5w@earthlink.net>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Caitlin Bestler" <caitlinb@rp.asomi.net>
To: <ngtrans@sunroof.eng.sun.com>
Sent: Thursday, January 09, 2003 1:14 PM
Subject: Re: RES: ReN: (ngtrans) IPv6 tranisition issues


> On 1/8/03, Rod Van Meter wrote:
>
> >> -----Mensagem original-----
> >> De: Michael R. Cole [mailto:mc5w@earthlink.net]
> >> Enviada em: terga-feira, 31 de dezembro de 2002 09:20
> >> Para: ngtrans@sunroof.eng.sun.com
> >> Assunto: Re: ReN: (ngtrans) IPv6 tranisition issues
> >>
> >>
> >> Your claim would also say that a timesharing system with
> >> only 1 public IPv4 address would not work which is what
> >> a cone NAT mimics. That is, a cone NAT fools that public
> >> Internet into thinking that a LAN or other subnet is in
> >> actuality a single machine.
> >
> >That's a gross oversimplification that eliminates the
> >actual problem, so of course it doesn't sound bad when you
> >put it that way.
> >
> >When a computer has a global address, you open a socket
> >and get a port, and you can tell anyone anywhere in the
> >world using any communications medium that they can reach
> >you there.  You can call someone on the telephone and tell
> >them, "My cool new game server is at port 1982 on
> >1.2.3.4!" and it works.  You can send the info via snail
> >mail, and it works.  One friend can tell another friend,
> >and it works.
> >
> Virtually every NAT device I have seen is fully capable of
> statically configuring any port to pass-thru to a specific
> machine. In other words, the single virtual machine can
> offer it service on any port and then use any of its
> component machines to implement that service.
>
> So the statement that a NAT creates a single virtual machine
> is both very accurate, and highlights very precisely its
> limitations.
>
> The next question is how well that Virtual Machine
> communicates internally. There are indeed NATs that have no
> mechanism to dynamically determine the external port
> associated with a given connection, or to dynamically create
> a mapping. That is indeed a poor interface, but to be fair
> it is a poor interface *within* the virtual machine. There
> is nothing wrong with the interface presented to the public
> Internet. The left hand not communicating with the right
> hand is something any Internet host can achieve, whether it
> is composed of a single or multiple machines.
>
> The real point is not that "NAT is evil". There are
> legitimate reasons for presenting a single virtual machine
> to the public network. Rather the issue is that networks are
> forced to use IPv4 NAT to solve other problems such as a
> shortage of public IPv4 addresses and keeping the identity
> of specific machines within a private network confidential.
>
> NAT "breaks" applications when the hosts it is masquerading
> are not actually part of an integrated whole. Properly
> deployed, IPv6 allows each host within a private network to
> have permanent and/or temporary public addresses as
> required.
>
> I believe NAT bashing is counter-productive to IPv6
> deployment. Too many comments make it sound as though IPv6
> advocates believe that only fools would use a NAT. A lot of
> non-fools had very valid reasons to deploy NAT. The best way
> to convince them that IPv6 offers better solutions to those
> problems is by starting with acknowleding their legitimate
> problems and understanding why they chose to deploy NATs in
> the first place.
>
> Caitlin Bestler
> http://asomi.com/CaitlinBestler/
>

Thank you very much for explaining why one of the NAT+gateway packages that
I have tried works so well (that I am tempted to buy it) and the commercial
version has features that should NOT be omitted from any connectivity
software.

However, with only a 33.6 Kbps dialup connection I cannot justify buying a
package yet. I can only justify playing around with a package for the 30-day
trial period.




From owner-ngtrans@sunroof.eng.sun.com  Mon Jan 20 13:00:57 2003
Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25594
	for <ngtrans-archive@lists.ietf.org>; Mon, 20 Jan 2003 13:00:56 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA10461;
	Mon, 20 Jan 2003 11:03:51 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0KI3mgG029749;
	Mon, 20 Jan 2003 10:03:50 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0KI3R16006744
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Mon, 20 Jan 2003 10:03:27 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0KI3RYc006743
	for ngtrans-bumvof58w; Mon, 20 Jan 2003 10:03:27 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0KI3P16006736
	for <ngtrans@sunroof.eng.sun.com>; Mon, 20 Jan 2003 10:03:25 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0KI3V4w023932
	for <ngtrans@sunroof.eng.sun.com>; Mon, 20 Jan 2003 10:03:31 -0800 (PST)
Received: from duque.cpqd.com.br (duque.cpqd.com.br [200.231.0.62])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA25630
	for <ngtrans@sunroof.eng.sun.com>; Mon, 20 Jan 2003 11:03:24 -0700 (MST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by duque.cpqd.com.br (8.12.5/8.12.5) with SMTP id h0KI3Q1x021211
	for <ngtrans@sunroof.eng.sun.com>; Mon, 20 Jan 2003 16:03:26 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 20 Jan 2003 16:03:14 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: (ngtrans) Security in Transiction mechanisms
Date: Mon, 20 Jan 2003 16:02:43 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017EA063@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: Security in Transiction mechanisms
Thread-Index: AcLAriFC3NVdiAExTSGlZrG1s6e2QA==
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h0KI3P16006737
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


 Hi folks,

   I am looking for documents about security considerations in transiction mechanisms. I saw only a good draft about security in 6to4 tunneling. Thanks in advanced,

			Marcelo Lima



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 21 04:59:53 2003
Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24739
	for <ngtrans-archive@lists.ietf.org>; Tue, 21 Jan 2003 04:59:52 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA28420;
	Tue, 21 Jan 2003 03:01:57 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0LA1o50026179;
	Tue, 21 Jan 2003 02:01:55 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0LA1T16010781
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 21 Jan 2003 02:01:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0LA1SvI010780
	for ngtrans-bumvof58w; Tue, 21 Jan 2003 02:01:28 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0LA1Q16010773
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 02:01:26 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0LA1a4w026138
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 02:01:36 -0800 (PST)
Received: from barao.cpqd.com.br (barao.cpqd.com.br [200.231.0.47])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA01952
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 02:01:30 -0800 (PST)
Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35])
	by barao.cpqd.com.br (8.12.5/8.12.5) with SMTP id h0LA1XRx029043
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 08:01:33 -0200
Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Tue, 21 Jan 2003 08:01:20 -0200 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RES: (ngtrans) Security in Transiction mechanisms
Date: Tue, 21 Jan 2003 08:00:51 -0200
Message-ID: <D49EA2F934FFAD45B337C07A9753C00E017EA068@MAILSRV1.aquarius.cpqd.com.br>
Thread-Topic: (ngtrans) Security in Transiction mechanisms
Thread-Index: AcLBKWe8NAJ3ShntRDSBEJYHleqkDQACgyEA
From: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
To: "Eng Soo Guan" <engsg@i2r.a-star.edu.sg>, <ngtrans@sunroof.eng.sun.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id h0LA1Q16010774
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Marcelo Barbosa Lima" <mlima@cpqd.com.br>
Content-Transfer-Encoding: 8bit


  There are some drafts about firewalls, neighbor discovery, 6to4 tunneling, etc. Look at IETF (look at SEND WG, MOBILEIP WG, IPV6 WG). Besides, look for in google or similar for "IPv6 security". There are many good documents about this subject. Regards,

		Marcelo.

-----Mensagem original-----
De: Eng Soo Guan [mailto:engsg@i2r.a-star.edu.sg]
Enviada em: terça-feira, 21 de janeiro de 2003 06:37
Para: Marcelo Barbosa Lima; ngtrans@sunroof.eng.sun.com
Assunto: Re: (ngtrans) Security in Transiction mechanisms


On the topic of security, may I know if there is a good document on security in IPv6?? Where can I find it?

Warmest regards.

SG
Eng Soo Guan
R&D Engineer (Software)
Institute for Communications Research*
http://www.i2r.a-star.edu.sg
Tel:+65 68709342

* On 15 Nov '02, the merger of ICR with the Laboratories for Information Technology to form the Institute for Infocomm Research 
[ I (superscript: 2) R ] was announced. The legal completion of the merger exercise is scheduled to be completed by 1 Apr '03.
>>> "Marcelo Barbosa Lima" <mlima@cpqd.com.br> 01/21/03 01:59 AM >>>

 Hi folks,

   I am looking for documents about security considerations in transiction mechanisms. I saw only a good draft about security in 6to4 tunneling. Thanks in advanced,

			Marcelo Lima





From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 21 07:55:13 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27816
	for <ngtrans-archive@lists.ietf.org>; Tue, 21 Jan 2003 07:55:13 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA27812;
	Tue, 21 Jan 2003 04:56:31 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0LCuSgG008874;
	Tue, 21 Jan 2003 04:56:30 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0LCu816012268
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 21 Jan 2003 04:56:08 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0LCu85W012267
	for ngtrans-bumvof58w; Tue, 21 Jan 2003 04:56:08 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2sun.Eng.Sun.COM (engmail2sun [129.144.134.19])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0LCu516012260
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 04:56:05 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.Central.Sun.COM [129.147.5.36])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0LCuD4w019671
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 04:56:14 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA08471
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Jan 2003 05:56:07 -0700 (MST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27678;
	Tue, 21 Jan 2003 07:52:39 -0500 (EST)
Message-Id: <200301211252.HAA27678@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-isatap-11.txt
Date: Tue, 21 Jan 2003 07:52:39 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Intra-Site Automatic Tunnel Addressing Protocol 
                          (ISATAP)
	Author(s)	: F. Templin, T. Gleeson, M. Talwar, D. Thaler
	Filename	: draft-ietf-ngtrans-isatap-11.txt
	Pages		: 23
	Date		: 2003-1-20
	
This document specifies an Intra-Site Automatic Tunnel Addressing
Protocol (ISATAP) that connects IPv6 hosts and routers within IPv4
sites.  ISATAP treats the site's IPv4 infrastructure as a link layer
for IPv6 with no requirement for IPv4 multicast.  ISATAP enables
intra-site automatic IPv6-in-IPv4 tunneling whether globally assigned
or private IPv4 addresses are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-isatap-11.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ietf-ngtrans-isatap-11.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-ietf-ngtrans-isatap-11.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.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-1-20131746.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-isatap-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-isatap-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-1-20131746.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 22 06:00:05 2003
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21605
	for <ngtrans-archive@lists.ietf.org>; Wed, 22 Jan 2003 06:00:04 -0500 (EST)
Received: from engmail2sun.Eng.Sun.COM ([129.144.134.19])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA21868;
	Wed, 22 Jan 2003 03:01:49 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail2sun.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0MB1b50015009;
	Wed, 22 Jan 2003 03:01:41 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0MAPi16019545
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 22 Jan 2003 02:25:44 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0MAPhSj019544
	for ngtrans-bumvof58w; Wed, 22 Jan 2003 02:25:43 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0MAPd16019532
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 02:25:39 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0MAPmgE011231
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 02:25:48 -0800 (PST)
Received: from kirk.rvdp.org (node147c0.a2000.nl [24.132.71.192])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA01072
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 03:25:34 -0700 (MST)
Received: (from rvdp@localhost)
	by kirk.rvdp.org (8.11.6/8.11.6) id h0MAOfu02030
	for ngtrans@sunroof.eng.sun.com; Wed, 22 Jan 2003 11:24:41 +0100 (CET)
Date: Wed, 22 Jan 2003 11:24:41 +0100
From: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) status of ngtrans?
Message-ID: <20030122102441.GF285@rvdp.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>

What is the exact status of ngtrans? I thought it was closed, but
the mailing list was to remain open. But should ngtrans still accept
new versions of I-Ds? I thought they were supposed to become personal
or v6ops I-Ds. I think it is confusing to have both ngtrans and v6ops.

A statement on http://www.ietf.org/html.charters/ngtrans-charter.html
to redirect people to v6ops would be useful too.

	rvdp


From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 22 08:08:07 2003
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23774
	for <ngtrans-archive@lists.ietf.org>; Wed, 22 Jan 2003 08:08:06 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA06313;
	Wed, 22 Jan 2003 06:10:53 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0MDAogG006042;
	Wed, 22 Jan 2003 05:10:52 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0MDAV16021116
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Wed, 22 Jan 2003 05:10:32 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7/Submit) id h0MDAV4M021115
	for ngtrans-bumvof58w; Wed, 22 Jan 2003 05:10:31 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.7+Sun/8.12.7) with ESMTP id h0MDAT16021108
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 05:10:29 -0800 (PST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0MDAbgE005996
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 05:10:37 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA00762
	for <ngtrans@sunroof.eng.sun.com>; Wed, 22 Jan 2003 05:10:31 -0800 (PST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h0MDAE932349;
	Wed, 22 Jan 2003 15:10:14 +0200
Date: Wed, 22 Jan 2003 15:10:14 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Ronald van der Pol <Ronald.vanderPol@rvdp.org>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) status of ngtrans?
In-Reply-To: <20030122102441.GF285@rvdp.org>
Message-ID: <Pine.LNX.4.44.0301221508470.32260-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Pekka Savola <pekkas@netcore.fi>

On Wed, 22 Jan 2003, Ronald van der Pol wrote:
> What is the exact status of ngtrans? I thought it was closed, but
> the mailing list was to remain open. But should ngtrans still accept
> new versions of I-Ds? I thought they were supposed to become personal
> or v6ops I-Ds. I think it is confusing to have both ngtrans and v6ops.

Currently, the procedure is so that the ngtrans I-D's can continue to be
published as revisions, or be moved under the author's name (the author's
option).

That's the same for all closed wg's.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 28 06:50:20 2003
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22060
	for <ngtrans-archive@lists.ietf.org>; Tue, 28 Jan 2003 06:50:20 -0500 (EST)
Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45])
	by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA14450;
	Tue, 28 Jan 2003 03:49:17 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.SFBay.Sun.COM [129.146.168.88])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0SBnEVM017360;
	Tue, 28 Jan 2003 03:49:15 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.8+Sun/8.12.8) with ESMTP id h0SBmtQb003206
	for <ngtrans-bumvof58w@sunroof.eng.sun.com>; Tue, 28 Jan 2003 03:48:55 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.8+Sun/8.12.8/Submit) id h0SBmtNV003205
	for ngtrans-bumvof58w; Tue, 28 Jan 2003 03:48:55 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail1mpk.Eng.Sun.COM (engmail1mpk [129.146.1.45])
	by sunroof.eng.sun.com (8.12.8+Sun/8.12.8) with ESMTP id h0SBmqQb003198
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Jan 2003 03:48:52 -0800 (PST)
Received: from kathmandu.sun.com (kathmandu.Central.Sun.COM [129.147.5.36])
	by engmail1mpk.Eng.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.2) with ESMTP id h0SBmxVK017338
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Jan 2003 03:48:59 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA11257
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Jan 2003 04:48:54 -0700 (MST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21845;
	Tue, 28 Jan 2003 06:45:22 -0500 (EST)
Message-Id: <200301281145.GAA21845@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-isatap-12.txt
Date: Tue, 28 Jan 2003 06:45:21 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Intra-Site Automatic Tunnel Addressing Protocol 
                          (ISATAP)
	Author(s)	: F. Templin, T. Gleeson, M. Talwar, D. Thaler
	Filename	: draft-ietf-ngtrans-isatap-12.txt
	Pages		: 24
	Date		: 2003-1-27
	
This document specifies an Intra-Site Automatic Tunnel Addressing
Protocol (ISATAP) that connects IPv6 hosts and routers within IPv4
sites.  ISATAP treats the site's IPv4 infrastructure as a link layer
for IPv6 with no requirement for IPv4 multicast.  ISATAP enables
intra-site automatic IPv6-in-IPv4 tunneling whether globally assigned
or private IPv4 addresses are used.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-isatap-12.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ietf-ngtrans-isatap-12.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-ietf-ngtrans-isatap-12.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.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-1-27081555.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-isatap-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-isatap-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-1-27081555.I-D@ietf.org>

--OtherAccess--

--NextPart--




