Re: (ngtrans) draft-ietf-ngtrans-dns-ops-req-03.txt

itojun@iijlab.net Wed, 12 December 2001 16:07 UTC

Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11926 for <ngtrans-archive@odin.ietf.org>; Wed, 12 Dec 2001 11:07:01 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA23446; Wed, 12 Dec 2001 09:03:53 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA24660; Wed, 12 Dec 2001 08:03:55 -0800 (PST)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.2.Beta1+Sun/8.12.2.Beta1) with ESMTP id fBCG3SvU027300 for <ngtrans-dist@sunroof.eng.sun.com>; Wed, 12 Dec 2001 08:03:28 -0800 (PST)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.2.Beta1+Sun/8.12.2.Beta1/Submit) id fBCG3SvC027299 for ngtrans-dist; Wed, 12 Dec 2001 08:03:28 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.12.2.Beta1+Sun/8.12.2.Beta1) with ESMTP id fBCG3PvU027292 for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Dec 2001 08:03:25 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id IAA16949 for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Dec 2001 08:03:26 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA09830 for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Dec 2001 08:03:25 -0800 (PST)
Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 5D1CD4B22; Thu, 13 Dec 2001 01:03:19 +0900 (JST)
To: Alain Durand <Alain.Durand@sun.com>
Cc: ngtrans@sunroof.eng.sun.com
In-reply-to: Alain.Durand's message of Tue, 11 Dec 2001 09:02:13 PST. <5.1.0.14.0.20011211084929.00b194c0@jurassic.eng.sun.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-dns-ops-req-03.txt
From: itojun@iijlab.net
Date: Thu, 13 Dec 2001 01:03:19 +0900
Message-ID: <20276.1008172999@itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

>>         I do not understand why DNS is so special for you.
>It is special because it is a key component of the Internet infrastructure.
>Break DNS and everything else break.
>See also RFC2826.

	I still do not believe it is special, looking from DNS transport
	point of view.  situation should be either of the following:
	- exisitng ngtrans tools can support DNS situation,
	- existing ngtrans tools cannot support DNS situation, in this case,
	  other protocols need a new transition tool as well.
	and I guess the situation is the former.

>Doing this at site boundary requires at one IPv4 address per site.
>There will be IPv6 only sites/networks/ISPs in the future with no IPv4 at all,
>so while this approach works now it does not work in the long run.
>Due to the extraordinary amount of time it takes to change the resolvers,
>we have to address the long term problem now.

	I wonder how you propose to solve transition issues with other problems
	in this situation (like accessing HTTPv4 servers).  if there's no
	soltion, we need a new tool in ngtrans toolbox (or toybox).

	also, in my view people will need to run dual stack (or "giant IPv6
	network with single IPv4 global address") for a very very long time.
	the view could be affecting my comments.

itojun