From owner-ngtrans@sunroof.eng.sun.com  Thu Feb  3 17:24:51 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01208
	for <ngtrans-archive@odin.ietf.org>; Thu, 3 Feb 2000 17:24:49 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA27120;
	Thu, 3 Feb 2000 15:24:27 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA10318;
	Thu, 3 Feb 2000 14:12:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e13MAwp28073
	for ngtrans-dist; Thu, 3 Feb 2000 14:10:58 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e13MApj28066
	for <ngtrans@sunroof.eng.sun.com>; Thu, 3 Feb 2000 14:10:51 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA10050
	for <ngtrans@sunroof.eng.sun.com>; Thu, 3 Feb 2000 14:10:50 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id PAA19677
	for <ngtrans@sunroof.eng.sun.com>; Thu, 3 Feb 2000 15:10:49 -0700 (MST)
Received: from alderhill.wins.lbl.gov (alderhill) [128.3.9.223] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12GUSb-0002Sq-00; Thu, 3 Feb 2000 14:10:46 -0800
Message-Id: <4.2.2.20000203140008.00d69100@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 03 Feb 2000 14:10:41 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) NGtrans scheduling and agenda planning for 47th IETF in
  Adelaide
Cc: Alain Durand <Alain.Durand@imag.fr>, Bob Fink <fink@es.net>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>,
        Bert Wijnen <WIJNEN@VNET.IBM.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>

NGtrans folk,

The IETF has released their first agenda for the Adelaide meetings.

The following time slots are for IPv6 activities.

>MONDAY, March 27, 2000
>1730-1930  Break
>1930-2200  Evening Sessions
>         OPS  ngtrans    Next Generation Transition WG
>
>
>WEDNESDAY, March 29, 2000
>0900-1130  Morning Sessions (multicasted)
>1130-1300  Break
>1300-1500  Afternoon Sessions I
>         OPS  ngtrans    Next Generation Transition WG


The tentative agenda for ngtrans as we see it from active projects is 
below, plus a few items with ? that we want to solcit speakers for. Please 
confirm your willingness to cover the topics if your name is shown, or let 
us know if you can't. Also, new items are solicited, ? or not.

Comments either to the list, the chairs or both :-)


Thanks,

Bob

=====================================

Project status report - Fink, 10 mins

BT Patent IPR resolution - Fink, 5 mins

MECH - Nordmark, 10-20 mins

6to4 - Carpenter, 30 mins

DSTM - Bound, 10-20 mins

SOCKS - Kitamura, 10 mins

TRANSLATOR - Kazu, 10 mins

BROKER - Guardini, 10 mins

Tunnel Discovery - Durand, 10 mins

TCPUDP-RELAY - Kazu, 15 mins

6PAPA - Fink, 5 mins

pTLA - Fink, 5 mins

?

total time pre-6bone - 2 hr 10 mins - 2 hrs 30 mins

6bone - 1 hrs 50 mins - 1 hr 30 mins

  PingERv6 Report - Les Cottrell - 10 mins
  relocated 6bone registry - David Kessens - 5 mins
  6tap report ?
  pTLA reliability report ?
  tools for finding ghost routes ?
  ?

-end





From owner-ngtrans@sunroof.eng.sun.com  Tue Feb  8 17:27:48 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12783
	for <ngtrans-archive@odin.ietf.org>; Tue, 8 Feb 2000 17:27:43 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA02677;
	Tue, 8 Feb 2000 14:26:54 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA26238;
	Tue, 8 Feb 2000 14:26:22 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e18MP1f03817
	for ngtrans-dist; Tue, 8 Feb 2000 14:25:01 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e18MOs003810
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Feb 2000 14:24:55 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA25834
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Feb 2000 14:24:54 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id OAA05136
	for <ngtrans@sunroof.eng.sun.com>; Tue, 8 Feb 2000 14:24:52 -0800 (PST)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.222] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12IJ3v-00050B-00; Tue, 8 Feb 2000 14:24:47 -0800
Message-Id: <4.2.2.20000208142353.0187a180@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 08 Feb 2000 14:24:46 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) cut-off date is March 10 for Internet-Drafts prior to the IETF
  meeting in Adelaide
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>

NGtrans Folks,

For you info


===
>Date: Tue, 8 Feb 2000 16:11:10 -0500 (Eastern Standard Time)
>From: Steve Coya <scoya@ietf.org>
>To: wgchairs@ietf.org
>Subject: Getting close to "that" time
>
>
>Greetings,
>
>The cut-off date for Internet-Drafts prior to the IETF meeting in Adelaide
>is March 10. We'll be sending out a notice later this week.
>
>We (that is, Natalia) processed over 300 I-D submissions the week
>following the DC meeting I-D cutoff. One of the problems encountered was
>keeping documents in a special holding queue. There were, of course, the
>many -00 submissions of draft-ietf-acronym- filename types.
>
>It was suggested that we require all -00 submissions be sent directly to
>the WG chairs (fear not, I explained the reality of things :-).
>
>Believe me, it IS a hassle trying to process all the I-D submissions and
>keep track of all those we must hold while waiting for a WG chair to say
>ok (or no way).
>
>As such, I'm asking chairs to do their best to quickly respond when
>queried about -00 submissions. I would also ask that if the chairs are
>copied on the original submission, there is no need to wait for Natalia's
>query before responding :-)
>
>If ANYONE has a suggestion on how to we might be able to efficiently
>handle initial submissions, please feel free to let me know.
>
>BTW, moving the deadline back YAW is not a good suggestion, albeit
>tempting :-)
>
>Thanks.
>
>
>Steve
>
>
>




From owner-ngtrans@sunroof.eng.sun.com  Wed Feb  9 04:32:00 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02761
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Feb 2000 04:31:59 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA15963;
	Wed, 9 Feb 2000 01:31:06 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id BAA05570;
	Wed, 9 Feb 2000 01:29:45 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e199SOW04358
	for ngtrans-dist; Wed, 9 Feb 2000 01:28:24 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e199SG004351
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:28:16 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id BAA05504
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:28:15 -0800 (PST)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA22408
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:28:15 -0800 (PST)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id KAA28753
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 10:28:13 +0100 (MET)
Received: from comte.danubius by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id KAA01231; Wed, 9 Feb 2000 10:28:11 +0100 (MET)
Received: from eth.ericsson.se (localhost [127.0.0.1])
	by comte.danubius (8.8.8+Sun/8.8.8) with ESMTP id KAA25068
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 10:28:11 +0100 (MET)
Message-ID: <38A1332B.CB7022FA@eth.ericsson.se>
Date: Wed, 09 Feb 2000 10:28:11 +0100
From: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) Bump-in-the-stack
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Content-Transfer-Encoding: 7bit

Hi,

 I have a question about BIS.
 BIS is useful for IPv4 applications to communicate with both IPv4 and
IPv6 hosts. Is it possible for IPv6 applications to work with BIS? I
mean that if az IPv6 packet arrives, it will be translated to IPv4 by
the tranlator module without examining that it is addressed to an IPv6
or an IPv4 application.

Thanks,

        Kornel Szegedi



From owner-ngtrans@sunroof.eng.sun.com  Wed Feb  9 04:49:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02804
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Feb 2000 04:49:08 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA14747;
	Wed, 9 Feb 2000 02:48:49 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id BAA08522;
	Wed, 9 Feb 2000 01:48:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e199ksc04389
	for ngtrans-dist; Wed, 9 Feb 2000 01:46:54 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e199kl004382
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:46:48 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id BAA21839
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:46:48 -0800 (PST)
Received: from ss3000e.cselt.it (ss3000e.cselt.it [163.162.41.5])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA27996
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 01:46:46 -0800 (PST)
Received: from satchmo (satchmo.cselt.it [163.162.170.11])
 by ss3000e.cselt.it (PMDF V5.2-31 #37044)
 with SMTP id <0FPN00FD8PPY32@ss3000e.cselt.it> for
 ngtrans@sunroof.eng.sun.com; Wed,  9 Feb 2000 10:44:22 +0100 (MET)
Date: Wed, 09 Feb 2000 10:43:50 +0100 (MET)
From: Fabrizio Invernizzi <Fabrizio.Invernizzi@CSELT.IT>
Subject: Re: (ngtrans) Bump-in-the-stack
In-reply-to: <38A1332B.CB7022FA@eth.ericsson.se>
To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Message-id: <Pine.GSO.3.96.1000209103943.19970G-100000@satchmo>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Fabrizio Invernizzi <Fabrizio.Invernizzi@CSELT.IT>

Hi.

I think that, in theory, a BIS would translate only IPv4->IPv6 and
IPv6->IPv4 traffic.

I installed an hitachi BIS (the only one i know to exist) on a windows NT
machine and it works great for IPv4 application (I use winamp IPv4, for
example), but if i try to use IPv6 applications (for example sdr whith
MSR6 stack) these don't work.


Fabrizio  


On Wed, 9 Feb 2000, Kornel Szegedi wrote:

> Hi,
> 
>  I have a question about BIS.
>  BIS is useful for IPv4 applications to communicate with both IPv4 and
> IPv6 hosts. Is it possible for IPv6 applications to work with BIS? I
> mean that if az IPv6 packet arrives, it will be translated to IPv4 by
> the tranlator module without examining that it is addressed to an IPv6
> or an IPv4 application.
> 
> Thanks,
> 
>         Kornel Szegedi
> 
> 



From owner-ngtrans@sunroof.eng.sun.com  Wed Feb  9 05:11:13 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02948
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Feb 2000 05:11:12 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA04368;
	Wed, 9 Feb 2000 02:10:40 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA22904;
	Wed, 9 Feb 2000 02:10:19 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e19A93M04439
	for ngtrans-dist; Wed, 9 Feb 2000 02:09:03 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e19A8t004432
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 02:08:55 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id CAA13344;
	Wed, 9 Feb 2000 02:08:54 -0800 (PST)
Date: Wed, 9 Feb 2000 02:08:12 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) Bump-in-the-stack
To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Message-ID: <Roam.SIMC.2.0.6.950090892.6873.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>

If you have an IPv6 stack I think it would make more
sense to use bump-in-the-API (BIA) than BIS. BIA 
basically makes IPv4 applications communicate using IPv6 by remapping things
at the API layer.

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Wed Feb  9 09:35:51 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07137
	for <ngtrans-archive@odin.ietf.org>; Wed, 9 Feb 2000 09:35:50 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA18721;
	Wed, 9 Feb 2000 06:28:16 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id GAA06747;
	Wed, 9 Feb 2000 06:27:02 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e19EPkl04540
	for ngtrans-dist; Wed, 9 Feb 2000 06:25:46 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e19EPd004533
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 06:25:40 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id GAA21178
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 06:25:40 -0800 (PST)
Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA23964
	for <ngtrans@sunroof.eng.sun.com>; Wed, 9 Feb 2000 06:25:39 -0800 (PST)
Received: from newton.ebina.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id XAA23858; Wed, 9 Feb 2000 23:25:38 +0900 (JST)
Received: from ppp ([172.16.110.11])
	by newton.ebina.hitachi.co.jp (8.9.0/3.7W-EBINA) with SMTP id XAA25998;
	Wed, 9 Feb 2000 23:25:38 +0900 (JST)
Message-Id: <200002091425.XAA25998@newton.ebina.hitachi.co.jp>
X-Sender: tsuchi@gpc.ebina.hitachi.co.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-J (32)
Date: Wed, 09 Feb 2000 23:27:41 +0900
To: ngtrans@sunroof.eng.sun.com
From: Kazuaki Tsuchiya <tsuchi@ebina.hitachi.co.jp>
Subject: Re: (ngtrans) Bump-in-the-stack
Cc: tsuchi@ebina.hitachi.co.jp
In-Reply-To: <Pine.GSO.3.96.1000209103943.19970G-100000@satchmo>
References: <38A1332B.CB7022FA@eth.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazuaki Tsuchiya <tsuchi@ebina.hitachi.co.jp>

Hi Ngtrans folks,

At 10:43 00/02/09 +0100, Fabrizio Invernizzi wrote:
> I think that, in theory, a BIS would translate only
> IPv4->IPv6 and IPv6->IPv4 traffic.
> 
> I installed an hitachi BIS (the only one i know to exist)
> on a windows NT machine and it works great for IPv4 appli-
> cation (I use winamp IPv4, for example), but if i try to
> use IPv6 applications (for example sdr whith MSR6 stack)
> these don't work.
> 

Yes, that's right. But it is a Hitachi Toolnet6's
implementation issue, not a BIS technical issue.
If we implement an "Extension Name Resolver" as
follows, Toolnet6 would be able to communicate with
other IPv6 hosts using pure IPv6 applications/stack.


"Extension Name Resolver":

  When an "Extension Name Resolver" gets an IPv6
  address, as an answer to a query which tries to
  resolve 'AAAA' records for a target host name, the
  resolver returns the IPv6 address to IPv6 applica-
  tions as is. 
    * Note that in the case there is no need for
      the IP conversion by a translator.

Thanks.

-- Kazuaki Tsuchiya, Hitachi.

------------------------------------------------------------
Kazuaki Tsuchiya (mailto:tsuchi@ebina.hitachi.co.jp)
  Hitachi,Ltd. Enterprise Server Division
    Phone: +81-46-235-8268(Dial-in) Fax: +81-46-235-8324


From owner-ngtrans@sunroof.eng.sun.com  Thu Feb 10 05:24:11 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18230
	for <ngtrans-archive@odin.ietf.org>; Thu, 10 Feb 2000 05:24:10 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA00488;
	Thu, 10 Feb 2000 02:23:44 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA21557;
	Thu, 10 Feb 2000 02:23:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1AALpX05999
	for ngtrans-dist; Thu, 10 Feb 2000 02:21:51 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1AALi005992
	for <ngtrans@sunroof.eng.sun.com>; Thu, 10 Feb 2000 02:21:44 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA09784
	for <ngtrans@sunroof.eng.sun.com>; Thu, 10 Feb 2000 02:21:44 -0800 (PST)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA10436
	for <ngtrans@sunroof.eng.sun.com>; Thu, 10 Feb 2000 03:21:43 -0700 (MST)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id LAA14464;
	Thu, 10 Feb 2000 11:21:32 +0100 (MET)
Received: from pythagoras.danubius by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id LAA10066; Thu, 10 Feb 2000 11:21:29 +0100 (MET)
Received: from eth.ericsson.se (localhost [127.0.0.1])
	by pythagoras.danubius (8.8.8+Sun/8.8.8) with ESMTP id LAA16602;
	Thu, 10 Feb 2000 11:21:29 +0100 (MET)
Message-ID: <38A29129.E912F5F6@eth.ericsson.se>
Date: Thu, 10 Feb 2000 11:21:29 +0100
From: Lajos Szabo <Lajos.Szabo@eth.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Kazuaki Tsuchiya <tsuchi@ebina.hitachi.co.jp>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Bump-in-the-stack
References: <38A1332B.CB7022FA@eth.ericsson.se> <200002091425.XAA25998@newton.ebina.hitachi.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Lajos Szabo <Lajos.Szabo@eth.ericsson.se>
Content-Transfer-Encoding: 7bit

Kazuaki Tsuchiya wrote:

 >If we implement an "Extension Name Resolver" as
 >follows, Toolnet6 would be able to communicate with
 >other IPv6 hosts using pure IPv6 applications/stack.
 >
 >"Extension Name Resolver":
 >When an "Extension Name Resolver" gets an IPv6
 >address, as an answer to a query which tries to
 >resolve 'AAAA' records for a target host name, the
 >resolver returns the IPv6 address to IPv6 applica-
 >tions as is.
 >  * Note that in the case there is no need for
 >    the IP conversion by a translator

Ok, that's clear. We speak about the communication which is triggered by
the IPv6 only host. In this case the packet reaches the dual host and
the mapper tries to find a mapping entry for the source and destination
address. The destination address will be the dual host's IPv4 address
and the mapper will assign one to the source address. Then the
translation will be done automatically (whether it's needed or not).
So I don't see how the IPv6 application on the IPv6 only host can
communicate with the IPv6 application on the dual host.
Is that possible?

          Lajos Szabo



From owner-ngtrans@sunroof.eng.sun.com  Fri Feb 11 15:26:45 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19114
	for <ngtrans-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:26:43 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA27118;
	Fri, 11 Feb 2000 12:24:21 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id MAA04026;
	Fri, 11 Feb 2000 12:23:19 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1BKKZ007598
	for ngtrans-dist; Fri, 11 Feb 2000 12:20:35 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1BKKP007591
	for <ngtrans@sunroof.eng.sun.com>; Fri, 11 Feb 2000 12:20:26 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id MAA16346
	for <ngtrans@sunroof.eng.sun.com>; Fri, 11 Feb 2000 12:20:24 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA22081
	for <ngtrans@sunroof.eng.sun.com>; Fri, 11 Feb 2000 12:20:23 -0800 (PST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA15920;
	Fri, 11 Feb 2000 12:20:14 -0800 (PST)
Message-Id: <200002112020.MAA15920@boreas.isi.edu>
To: IETF-Announce: ;
Subject: (ngtrans) RFC 2772 on 6Bone Backbone Routing Guidelines
Cc: rfc-ed@ISI.EDU, ngtrans@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 11 Feb 2000 12:20:14 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: RFC Editor <rfc-ed@ISI.EDU>


--NextPart


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


        RFC 2772

        Title:	    6Bone Backbone Routing Guidelines
        Author(s):  R. Rockell, R. Fink
        Status:     Informational
	Date:       February 2000
        Mailbox:    rrockell@sprint.net, fink@es.net
        Pages:      14
        Characters: 28565
	Obsoletes:  2546
        I-D Tag:    draft-ietf-ngtrans-harden-04.txt

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


The 6Bone is an Ipv6 testbed to assist in the evolution and deployment
of IPv6. Because of this, it is important that the core backbone of
the IPv6 network maintain stability, and that all operators have a
common set of rules and guidelines by which to deploy IPv6 routing
equipment. 
 
This document provides a set of guidelines for all 6bone routing
equipment operators to use as a reference for efficient and stable
deployment of 6bone routing systems. As the complexity of the 6Bone
grows,the adherence to a common set of rules becomes increasingly
important in order for an efficient, scalable backbone to exist.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

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

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

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

RETRIEVE: rfc
DOC-ID: rfc2772

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

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

--OtherAccess--
--NextPart--


From owner-ngtrans@sunroof.eng.sun.com  Sat Feb 12 03:45:08 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19435
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Feb 2000 03:45:07 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA28610;
	Sat, 12 Feb 2000 00:44:43 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA25368;
	Sat, 12 Feb 2000 00:44:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1C8gii08067
	for ngtrans-dist; Sat, 12 Feb 2000 00:42:44 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1C8gU008045
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:31 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA12122
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:29 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id BAA26737
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 01:42:25 -0700 (MST)
Received: from rlfink.lbl.gov (Truckee) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12JY8G-0000VB-00; Sat, 12 Feb 2000 00:42:24 -0800
Message-Id: <4.2.2.20000212004151.00ae6e90@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 12 Feb 2000 00:41:56 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) Fwd: RFC 2766 on NAT-PT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>


>To: IETF-Announce: ;
>Subject: RFC 2766 on NAT-PT
>Cc: rfc-ed@ISI.EDU
>Date: Wed, 09 Feb 2000 15:56:44 -0800
>From: RFC Editor <rfc-ed@ISI.EDU>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 2766
>
>         Title:      Network Address Translation - Protocol Translation
>                     (NAT-PT)
>         Author(s):  G. Tsirtsis, P. Srisuresh
>         Status:     Standards Track
>         Date:       February 2000
>         Mailbox:    george.tsirtsis@bt.com, srisuresh@yahoo.com
>         Pages:      21
>         Characters: 49836
>         Updates/Obsoletes/SeeAlso: None
>         I-D Tag:    draft-ietf-ngtrans-natpt-07.txt
>
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2766.txt
>
>
>This document specifies an IPv4-to-IPv6 transition mechanism, in
>addition to those already specified in [TRANS]. This solution
>attempts to provide transparent routing, as defined in [NAT-TERM], to
>end-nodes in V6 realm trying to communicate with end-nodes in V4
>realm and vice versa. This is achieved using a combination of Network
>Address Translation and Protocol Translation. The scheme described
>does not mandate dual-stacks (i.e., IPv4 as well as V6 protocol
>support) or special purpose routing requirements (such as requiring
>tunneling support) on end nodes. This scheme is based on a
>combination of address translation theme as described in [NAT-TERM]
>and V6/V4 protocol translation theme as described in [SIIT].
>
>This document is a product of the Next Generation Transition Working
>Group of the IETF.
>
>This document specifies an Internet standards track protocol for
>the Internet community, and requests discussion and suggestions
>for improvements.  Please refer to the current edition of the
>"Internet Official Protocol Standards" (STD 1) for the
>standardization state and status of this protocol.  Distribution
>of this memo is unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-Type: text/plain
>Content-ID: <000209155448.RFC@RFC-EDITOR.ORG>
>
>RETRIEVE: rfc
>DOC-ID: rfc2766
>
><ftp://ftp.isi.edu/in-notes/rfc2766.txt>




From owner-ngtrans@sunroof.eng.sun.com  Sat Feb 12 03:45:08 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19438
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Feb 2000 03:45:08 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA28621;
	Sat, 12 Feb 2000 00:44:45 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA04736;
	Sat, 12 Feb 2000 00:44:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1C8giB08066
	for ngtrans-dist; Sat, 12 Feb 2000 00:42:44 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1C8gT008043
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:30 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA12115
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:23 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id BAA26733
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 01:42:24 -0700 (MST)
Received: from rlfink.lbl.gov (Truckee) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12JY8E-0000VB-00; Sat, 12 Feb 2000 00:42:23 -0800
Message-Id: <4.2.2.20000212004137.00b3bc68@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 12 Feb 2000 00:41:48 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) Fwd: RFC 2765 on SIIT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>


>To: IETF-Announce: ;
>Subject: RFC 2765 on SIIT
>Cc: rfc-ed@ISI.EDU
>Date: Wed, 09 Feb 2000 15:53:13 -0800
>From: RFC Editor <rfc-ed@ISI.EDU>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 2765
>
>         Title:      Stateless IP/ICMP Translation Algorithm (SIIT)
>         Author(s):  E. Nordmark
>         Status:     Standards Track
>         Date:       February 2000
>         Mailbox:    nordmark@sun.com
>         Pages:      27
>         Characters: 59465
>         Updates/Obsoletes/SeeAlso: None
>         I-D Tag:    draft-ietf-ngtrans-siit-08.txt
>
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2765.txt
>
>
>This document specifies a transition mechanism algorithm in addition
>to the mechanisms already specified in [TRANS-MECH].  The algorithm
>translates between IPv4 and IPv6 packet headers (including ICMP
>headers) in separate translator "boxes" in the network without
>requiring any per-connection state in those "boxes".  This new
>algorithm can be used as part of a solution that allows IPv6 hosts,
>which do not have a permanently assigned IPv4 addresses, to
>communicate with IPv4-only hosts.  The document neither specifies
>address assignment nor routing to and from the IPv6 hosts when they
>communicate with the IPv4-only hosts.
>
>This document is a product of the Next Generation Transition Working
>Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>This document specifies an Internet standards track protocol for
>the Internet community, and requests discussion and suggestions
>for improvements.  Please refer to the current edition of the
>"Internet Official Protocol Standards" (STD 1) for the
>standardization state and status of this protocol.  Distribution
>of this memo is unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-Type: text/plain
>Content-ID: <000209155024.RFC@RFC-EDITOR.ORG>
>
>RETRIEVE: rfc
>DOC-ID: rfc2765
>
><ftp://ftp.isi.edu/in-notes/rfc2765.txt>




From owner-ngtrans@sunroof.eng.sun.com  Sat Feb 12 03:53:40 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19440
	for <ngtrans-archive@odin.ietf.org>; Sat, 12 Feb 2000 03:45:08 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA28611;
	Sat, 12 Feb 2000 00:44:44 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA12164;
	Sat, 12 Feb 2000 00:44:23 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1C8gmj08068
	for ngtrans-dist; Sat, 12 Feb 2000 00:42:48 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1C8gU008047
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:31 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id AAA12123
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 00:42:29 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id BAA26743
	for <ngtrans@sunroof.eng.sun.com>; Sat, 12 Feb 2000 01:42:27 -0700 (MST)
Received: from rlfink.lbl.gov (Truckee) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12JY8H-0000VB-00; Sat, 12 Feb 2000 00:42:26 -0800
Message-Id: <4.2.2.20000212004159.00add788@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 12 Feb 2000 00:42:06 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) Fwd: RFC 2767 on Dual Stack Hosts using BIS
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>


>To: IETF-Announce: ;
>Subject: RFC 2767 on Dual Stack Hosts using BIS
>Cc: rfc-ed@ISI.EDU
>Date: Wed, 09 Feb 2000 15:59:43 -0800
>From: RFC Editor <rfc-ed@ISI.EDU>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 2767
>
>         Title:      Dual Stack Hosts using the "Bump-In-the-Stack"
>                     Technique (BIS)
>         Author(s):  K. Tsuchiya, H. Higuchi, Y. Atarashi
>         Status:     Informational
>         Date:       February 2000
>         Mailbox:    tsuchi@ebina.hitachi.co.jp,
>                     h-higuti@ebina.hitachi.co.jp,
>                     atarashi@ebina.hitachi.co.jp
>         Pages:      13
>         Characters: 26402
>         Updates/Obsoletes/SeeAlso: None
>         I-D Tag:    draft-ietf-ngtrans-bis-00.txt
>
>         URL:        ftp://ftp.isi.edu/in-notes/rfc2767.txt
>
>
>In the especially initial stage of the transition from IPv4 to
>IPv6, it is hard to provide a complete set of IPv6 applications.
>This memo proposes a mechanism of dual stack hosts using the technique
>called "Bump-in-the-Stack" in the IP security area. The
>mechanism allows the hosts to communicate with other IPv6 hosts
>using existing IPv4 applications.
>
>This document is a product of the Next Generation Transition Working
>Group of the IETF.
>
>This memo provides information for the Internet community.  It does
>not specify an Internet standard of any kind.  Distribution of this
>memo is unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>Content-Type: text/plain
>Content-ID: <000209155711.RFC@RFC-EDITOR.ORG>
>
>RETRIEVE: rfc
>DOC-ID: rfc2767
>
><ftp://ftp.isi.edu/in-notes/rfc2767.txt>




From owner-ngtrans@sunroof.eng.sun.com  Sun Feb 13 20:58:18 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15152
	for <ngtrans-archive@odin.ietf.org>; Sun, 13 Feb 2000 20:58:17 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA17894;
	Sun, 13 Feb 2000 17:57:49 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA27966;
	Sun, 13 Feb 2000 17:56:50 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1E1tcC09012
	for ngtrans-dist; Sun, 13 Feb 2000 17:55:38 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1E1tV009005
	for <ngtrans@sunroof.eng.sun.com>; Sun, 13 Feb 2000 17:55:31 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA13189
	for <ngtrans@sunroof.eng.sun.com>; Sun, 13 Feb 2000 17:55:31 -0800 (PST)
Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA25133
	for <ngtrans@sunroof.eng.sun.com>; Sun, 13 Feb 2000 17:55:30 -0800 (PST)
Received: from newton.ebina.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id KAA26835; Mon, 14 Feb 2000 10:55:29 +0900 (JST)
Received: from ppp ([172.16.110.11])
	by newton.ebina.hitachi.co.jp (8.9.0/3.7W-EBINA) with SMTP id KAA08969;
	Mon, 14 Feb 2000 10:55:28 +0900 (JST)
Message-Id: <200002140155.KAA08969@newton.ebina.hitachi.co.jp>
X-Sender: tsuchi@gpc.ebina.hitachi.co.jp
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-J (32)
Date: Mon, 14 Feb 2000 10:57:40 +0900
To: Lajos Szabo <Lajos.Szabo@eth.ericsson.se>, ngtrans@sunroof.eng.sun.com
From: Kazuaki Tsuchiya <tsuchi@ebina.hitachi.co.jp>
Subject: Re: (ngtrans) Bump-in-the-stack
Cc: h-higuti@ebina.hitachi.co.jp, atarashi@ebina.hitachi.co.jp,
        tsuchi@ebina.hitachi.co.jp
In-Reply-To: <38A29129.E912F5F6@eth.ericsson.se>
References: <38A1332B.CB7022FA@eth.ericsson.se>
 <200002091425.XAA25998@newton.ebina.hitachi.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazuaki Tsuchiya <tsuchi@ebina.hitachi.co.jp>

Lajos,

Terribly sorry for my misunderstanding what you asked.

Yes, you are right. When communication is triggered by
the IPv6 only host and the IPv6 packets arrive at BIS,
it doesn't know whether it should toss them to IPv4
applications after translating them into IPv4 packets
or it should toss them to IPv6 applications as is. In
the case BIS cannot but translate them into IPv4 auto-
matically. So BIS cannot communicate with the IPv6 only
host using the IPv6 application. That is BIS technical
issue.

-- Kazuaki Tsuchiya, Hitachi.

At 11:21 00/02/10 +0100, Lajos Szabo wrote:
> Kazuaki Tsuchiya wrote:
> 
>  >If we implement an "Extension Name Resolver" as
>  >follows, Toolnet6 would be able to communicate with
>  >other IPv6 hosts using pure IPv6 applications/stack.
>  >
>  >"Extension Name Resolver":
>  >When an "Extension Name Resolver" gets an IPv6
>  >address, as an answer to a query which tries to
>  >resolve 'AAAA' records for a target host name, the
>  >resolver returns the IPv6 address to IPv6 applica-
>  >tions as is.
>  >  * Note that in the case there is no need for
>  >    the IP conversion by a translator
> 
> Ok, that's clear. We speak about the communication which is triggered by
> the IPv6 only host. In this case the packet reaches the dual host and
> the mapper tries to find a mapping entry for the source and destination
> address. The destination address will be the dual host's IPv4 address
> and the mapper will assign one to the source address. Then the
> translation will be done automatically (whether it's needed or not).
> So I don't see how the IPv6 application on the IPv6 only host can
> communicate with the IPv6 application on the dual host.
> Is that possible?
> 
>           Lajos Szabo
> 
> 
> 
------------------------------------------------------------
Kazuaki Tsuchiya (mailto:tsuchi@ebina.hitachi.co.jp)
  Hitachi,Ltd. Enterprise Server Division
    Phone: +81-46-235-8268(Dial-in) Fax: +81-46-235-8324


From owner-ngtrans@sunroof.eng.sun.com  Wed Feb 16 05:02:14 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21427
	for <ngtrans-archive@odin.ietf.org>; Wed, 16 Feb 2000 05:02:09 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA18616;
	Wed, 16 Feb 2000 03:00:41 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA18448;
	Wed, 16 Feb 2000 02:00:08 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1G9wqY11351
	for ngtrans-dist; Wed, 16 Feb 2000 01:58:52 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1G9wj011344
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 01:58:46 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id BAA18364
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 01:58:45 -0800 (PST)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA03097
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 01:58:44 -0800 (PST)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id KAA17052;
	Wed, 16 Feb 2000 10:58:38 +0100 (MET)
Received: from comte.danubius by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id KAA11641; Wed, 16 Feb 2000 10:58:35 +0100 (MET)
Received: from eth.ericsson.se (localhost [127.0.0.1])
	by comte.danubius (8.8.8+Sun/8.8.8) with ESMTP id KAA11525;
	Wed, 16 Feb 2000 10:58:34 +0100 (MET)
Message-ID: <38AA74CA.32BE1D13@eth.ericsson.se>
Date: Wed, 16 Feb 2000 10:58:34 +0100
From: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans <ngtrans@sunroof.eng.sun.com>, george.tsirtsis@bt.com,
        srisuresh@yahoo.com
Subject: (ngtrans) NAT-PT
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Content-Transfer-Encoding: 7bit

        Hi,

 I have a question about NAT.
 In rfc2766, chapter 3.1 "Basic-NAT-PT Operation" a technique is
introduced which does not use  DNS-ALG. The following example can be
found here:

| Say the IPv6 Node A wants to communicate with the IPv4 Node C.  Node A
creates a packet with:
|
|       Source Address, SA=FEDC:BA98::7654:3210 and
|       Destination Address, DA = PREFIX::132.146.243.30
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

My question is: how can Node A acquire the address of Node C? Node A
sends an "AAAA" query to the local DNS server. Suppose it does not know
the address of Node C, so it forwards the query to the next level DNS
server. The query passes through the NAT-PT (if we assume that the
server is located outside the NAT-PT) but since no DNS-ALG is present
there it is not translated to a type "A" query,  and no address will be
returned by the DNS server.
    Is my understanding right or is there something I did't take into
account?

                        Kornel




From owner-ngtrans@sunroof.eng.sun.com  Wed Feb 16 05:46:19 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21834
	for <ngtrans-archive@odin.ietf.org>; Wed, 16 Feb 2000 05:46:17 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA26860;
	Wed, 16 Feb 2000 02:45:53 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA24612;
	Wed, 16 Feb 2000 02:45:37 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) id e1GAiRk11402
	for ngtrans-dist; Wed, 16 Feb 2000 02:44:27 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta13+Sun/8.10.0.Beta13) with ESMTP id e1GAiK011395
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 02:44:21 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA14897
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 02:44:19 -0800 (PST)
From: george.tsirtsis@bt.com
Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA19149
	for <ngtrans@sunroof.eng.sun.com>; Wed, 16 Feb 2000 02:44:19 -0800 (PST)
Received: from cbtlipnt01.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Wed, 16 Feb 2000 10:43:13 +0000
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2448.0) id <10L923X4>;
          Wed, 16 Feb 2000 10:43:53 -0000
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB202DBA261@mbtlipnt02.btlabs.bt.co.uk>
To: Kornel.Szegedi@eth.ericsson.se
Cc: ngtrans@sunroof.eng.sun.com, srisuresh@yahoo.com
Subject: (ngtrans) RE: NAT-PT
Date: Wed, 16 Feb 2000 10:44:05 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com


> -----Original Message-----
> From:	Kornel Szegedi [SMTP:Kornel.Szegedi@eth.ericsson.se]
> Sent:	Wednesday, February 16, 2000 9:59 AM
> To:	ngtrans; george.tsirtsis@bt.com; srisuresh@yahoo.com
> Subject:	NAT-PT
> 
>         Hi,
> 
>  I have a question about NAT.
>  In rfc2766, chapter 3.1 "Basic-NAT-PT Operation" a technique is
> introduced which does not use  DNS-ALG. The following example can be
> found here:
> 
> | Say the IPv6 Node A wants to communicate with the IPv4 Node C.  Node A
> creates a packet with:
> |
> |       Source Address, SA=FEDC:BA98::7654:3210 and
> |       Destination Address, DA = PREFIX::132.146.243.30
>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> My question is: how can Node A acquire the address of Node C? Node A
> sends an "AAAA" query to the local DNS server. Suppose it does not know
> the address of Node C, so it forwards the query to the next level DNS
> server. The query passes through the NAT-PT (if we assume that the
> server is located outside the NAT-PT) but since no DNS-ALG is present
> there it is not translated to a type "A" query,  and no address will be
> returned by the DNS server.
> 
>     Is my understanding right or is there something I did't take into
> account?
> 
> 
	Kornel,

	NAT-PT requires the existence of DNS-ALG so its OK.
	If you *do not* want to use DNS-ALG you may be able to use the SIIT
mechanism in combination with NAT-PT. SIIT recognises IPv4 addresses as IPv4
mapped IPv6 addresses in which case the PREFIX in the example above is
always 0::0/96. 

	Hope this helps
	George



>                         Kornel
> 


