Re: (ngtrans) Another question about RFC2767 and draft-ietf-ngtrans-introduction-...

Chae-yong Chong <cychong@metro.telecom.samsung.co.kr> Thu, 20 September 2001 23:43 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 TAA26678 for <ngtrans-archive@odin.ietf.org>; Thu, 20 Sep 2001 19:43:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA23081; Thu, 20 Sep 2001 16:42:21 -0700 (PDT)
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 QAA16724; Thu, 20 Sep 2001 16:42:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KNfk7B017092 for <ngtrans-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 16:41:46 -0700 (PDT)
Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KNfkA2017091 for ngtrans-dist; Thu, 20 Sep 2001 16:41:46 -0700 (PDT)
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.0+Sun/8.12.0) with ESMTP id f8KNfh7B017084 for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Sep 2001 16:41:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL, v2.1p1) with ESMTP id QAA16598 for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Sep 2001 16:41:44 -0700 (PDT)
Received: from telecom.samsung.co.kr ([165.213.221.4]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA16196 for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:42:34 -0600 (MDT)
Received: from cychong (a22416 [165.213.224.16]) by telecom.samsung.co.kr (8.11.6/8.11.6) with SMTP id f8KNfWP23186 for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Sep 2001 08:41:34 +0900 (KST)
Message-ID: <001401c1422e$afe20a80$10e0d5a5@cychong>
From: Chae-yong Chong <cychong@metro.telecom.samsung.co.kr>
To: ngtrans@sunroof.eng.sun.com
References: <4.3.2-J.20010920175752.00bd3490@158.214.152.238>
Subject: Re: (ngtrans) Another question about RFC2767 and draft-ietf-ngtrans-introduction-...
Date: Fri, 21 Sep 2001 08:47:59 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-Mimeole: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by sunroof.eng.sun.com id f8KNfh7B017085
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Chae-yong Chong <cychong@metro.telecom.samsung.co.kr>
Content-Transfer-Encoding: 8bit

I add some comment for your reply.

----- Original Message ----- 
From: "Kazuaki Tsuchiya" <kazuaki.tsuchiya@itg.hitachi.co.jp>
To: <cychong@metro.telecom.samsung.co.kr>; <Win.Biemolt@sec.nl>
Cc: <ngtrans@sunroof.eng.sun.com>
Sent: Thursday, September 20, 2001 6:05 PM
Subject: Re: (ngtrans) Another question about RFC2767 and draft-ietf-ngtrans-introduction-...


> Hi,
> 
> At 14:21 01/09/20 +0900, owner-ngtrans@sunroof.eng.sun.com wrote:
> >In BIS, when non-IPv6 application want to send a packet to IPv6 host, the Extension Name Resolver
> >translate IPv4 DNS query message(Type 'A') to IPV6 DNS query message(type "A6" or "AAAA").
> >Does the Extension Name resolver need to know the target node's hostname is IPv6' node?
> >If so, how does the Extension Name Resolver know the translation(type "A" to "A6" or "AAAA" is required?
> 
> When BIS wants to send packets to a host(IPv4 or IPv6)
> using IPv4 applications, the Extension Name Resolver
> makes an IPv6 DNS query message from an IPV4 DNS query
> message, and sends both messages to a DNS server.

Does that mean the Extension Name Resolver always translate the DNS query
whether it is for an IPv4 node or IPv6 node? If not, how does Extension Name Resolver
know the target is IPv4 or IPv6?
Is there any difference in DomainName for IPv4 or IPv6?

> 
> o When the target node is an IPv4 host, the server returns
>    an "A" record to BIS.
> 
> o When the target node is an IPv6 host, the server returns
>    an "AAAA" record to BIS.
> 
> So BIS can know whether the target node is IPv4 or IPv6
> automatically. There is no need to know whether the target
> node is IPv4 or IPv6 in advance.
> 


> 
> 
> >And the draft-ietf-ngtrans-introduction-to-ipv6-transition-07.txt said that
> >
> >    IPv6 requirements:          none 
> >    IPv6 address requirements:  none 
> >
> >But RFC2767 said that
> >
> >2.3 Address Mapper
> >
> >...
> >
> >    NOTE: There is only one exception. When initializing the table, it
> >    registers a pair of its own IPv4 address and IPv6 address into the
> >    table statically.
> 
> This just means that BIS needs an IPv6 address for
> speaking in IPv6.
> 
> Thanks.

In my understanding the purpose of BIS is using the non-IPv6 application
in IPv4 node when that node want to communicate the other IPv6 only node.
The BIS implemented IPv4 node should got an IPv6 address. If not, why use
the BIS?

> 
> -- Kazuaki Tsuchiya, Hitachi.
> 
> 
> ------------------------------------------------------------
> Kazuaki Tsuchiya, Hitachi.
>    http://www.v6.hitachi.co.jp
>    mailto:kazuaki.tsuchiya@itg.hitachi.co.jp (NEW!)
>    mailto:tsuchiya@kanagawa.hitachi.co.jp
> 
>