(ngtrans) draft-ietf-ngtrans-dns-ops-req-03.txt
itojun@iijlab.net Tue, 11 December 2001 16:07 UTC
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19568 for <ngtrans-archive@odin.ietf.org>; Tue, 11 Dec 2001 11:07:22 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA23542; Tue, 11 Dec 2001 08:05:44 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA21844; Tue, 11 Dec 2001 08:05:33 -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 fBBG5DvU021320 for <ngtrans-dist@sunroof.eng.sun.com>; Tue, 11 Dec 2001 08:05:13 -0800 (PST)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.2.Beta1+Sun/8.12.2.Beta1/Submit) id fBBG5Dx2021319 for ngtrans-dist; Tue, 11 Dec 2001 08:05:13 -0800 (PST)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-ngtrans@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.12.2.Beta1+Sun/8.12.2.Beta1) with ESMTP id fBBG59vU021312 for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Dec 2001 08:05:09 -0800 (PST)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id IAA21718 for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Dec 2001 08:05:09 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA21673 for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Dec 2001 08:05:08 -0800 (PST)
Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 6E9274B23; Wed, 12 Dec 2001 01:05:04 +0900 (JST)
To: Alain.Durand@sun.com
Cc: ngtrans@sunroof.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: (ngtrans) draft-ietf-ngtrans-dns-ops-req-03.txt
From: itojun@iijlab.net
Date: Wed, 12 Dec 2001 01:05:04 +0900
Message-ID: <10591.1008086704@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. when you are on an IPv6-only node and needs to access IPv4-only resources, you either: - make your node dual stack by configuring IPv4 connectivity, by routing IPv4, DSTM, whatever - use translators at the site exit point, like NAT-PT IMHO this is no different for DNS servers/resolvers. if you are an IPv6-only recursive DNS resolver, and you need to look up resources on IPv4-only DNS servers, you need an IPv4 connectivity, or you use DNS-ALG at the site exit point. another point in this is that we don't need public open relay bridging system - transition mechanisms can be installed per site (so it is the matter of site configuration). if I mimic the logic in the draft, we'll need public open relay bridging system for HTTP, as HTTP has redirect: header and can invite you from IPv6 server to IPv4 server (chain of referrals). the thing that worries me very much is the recent trend in the ngtrans wg - the use of public datagram open relay for transition technologies. they behave very badly if abused. it includes 6to4, shipworm, and this draft. itojun