From owner-ngtrans@sunroof.eng.sun.com  Mon Apr 10 07:37:43 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 HAA05805
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Apr 2000 07:37:42 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA29279;
	Mon, 10 Apr 2000 05:36:56 -0600 (MDT)
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 EAA13565;
	Mon, 10 Apr 2000 04:36:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3ABYvr00515
	for ngtrans-dist; Mon, 10 Apr 2000 04:34:57 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3ABYb700495
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 04:34:38 -0700 (PDT)
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 EAA11182
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 04:34:36 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA28523
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 05:34:36 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05554;
	Mon, 10 Apr 2000 07:34:34 -0400 (EDT)
Message-Id: <200004101134.HAA05554@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-mech-05.txt
Date: Mon, 10 Apr 2000 07:34:34 -0400
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		: Transition Mechanisms for IPv6 Hosts and Routers
	Author(s)	: R. Gilligan, E. Nordmark
	Filename	: draft-ietf-ngtrans-mech-05.txt
	Pages		: 29
	Date		: 06-Apr-00
	
This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4
routing infrastructures.  They are designed to allow IPv6 nodes to
maintain complete compatibility with IPv4, which should greatly
simplify the deployment of IPv6 in the Internet, and facilitate the
eventual transition of the entire Internet to IPv6.

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

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-mech-05.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-mech-05.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:	<20000406142914.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-mech-05.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Mon Apr 10 07:37:49 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 HAA05819
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Apr 2000 07:37:48 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA29269;
	Mon, 10 Apr 2000 05:36:55 -0600 (MDT)
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 EAA13573;
	Mon, 10 Apr 2000 04:36:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3ABYpH00508
	for ngtrans-dist; Mon, 10 Apr 2000 04:34:51 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3ABYX700487
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 04:34:35 -0700 (PDT)
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 EAA11166
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 04:34:31 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA28499
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 05:34:31 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05538;
	Mon, 10 Apr 2000 07:34:29 -0400 (EDT)
Message-Id: <200004101134.HAA05538@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-socks-gateway-04.txt
Date: Mon, 10 Apr 2000 07:34:29 -0400
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		: A SOCKS-based IPv6/IPv4 Gateway Mechanism
	Author(s)	: H. Kitamura
	Filename	: draft-ietf-ngtrans-socks-gateway-04.txt
	Pages		: 14
	Date		: 06-Apr-00
	
This document describes an IPv6/IPv4 gateway mechanism that is based
on the SOCKS protocol [SOCKSv5]. By applying the SOCKS mechanism to
support the heterogeneous communications relays between IPv6 and IPv4
at the SOCKS server, the SOCKS-based IPv6/IPv4 gateway mechanism is
accomplished.
Since it is accomplished without introducing new protocols, it
provides the same communication environment that is provided by the
SOCKS mechanism. The same appearance is provided to the heterogeneous
communications. No conveniences or functionalities of current
communications are sacrificed.
The SOCKS-based gateway mechanism enables smooth heterogeneous
communications between the IPv6 nodes and IPv4 nodes.

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

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-socks-gateway-04.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-socks-gateway-04.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:	<20000406142904.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-socks-gateway-04.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Mon Apr 10 15:35:19 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 PAA01323
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Apr 2000 15:35:18 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA06186;
	Mon, 10 Apr 2000 13:33:02 -0600 (MDT)
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 MAA09383;
	Mon, 10 Apr 2000 12:32:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3AJV4s01155
	for ngtrans-dist; Mon, 10 Apr 2000 12:31:04 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3AJUt701148
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Apr 2000 12:30:57 -0700 (PDT)
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 MAA03799;
	Mon, 10 Apr 2000 12:29:32 -0700 (PDT)
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 MAA04666;
	Mon, 10 Apr 2000 12:29:17 -0700 (PDT)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.222] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12ejs3-0004GU-00; Mon, 10 Apr 2000 12:29:15 -0700
Message-Id: <4.2.2.20000410122510.01a70a30@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 10 Apr 2000 12:29:12 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) working group last call for MECH-05 - closes 24 April 2000
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.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 following MECH-05 draft has just been published and contains changes 
from accumulated comments. The author and the chairs felt it appropriate to 
redo the last call.

Thus there will be a two-week ngtrans working group last call.

Comments to the list by 24 April 2000.


Thanks,

Bob

 >----------------Begin Forwarded Message----------------<

Date: Mon, 10 Apr 2000 07:34:34 -0400
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-mech-05.txt
To: IETF-Announce@, @
Cc: ngtrans@sunroof.eng.sun.com

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		: Transition Mechanisms for IPv6 Hosts and Routers
	Author(s)	: R. Gilligan, E. Nordmark
	Filename	: draft-ietf-ngtrans-mech-05.txt
	Pages		: 29
	Date		: 06-Apr-00
	
This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4
routing infrastructures.  They are designed to allow IPv6 nodes to
maintain complete compatibility with IPv4, which should greatly
simplify the deployment of IPv6 in the Internet, and facilitate the
eventual transition of the entire Internet to IPv6.

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

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-mech-05.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-mech-05.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.
 >----------------End Forwarded Message----------------<




From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 11 14:14:32 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 OAA15603
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Apr 2000 14:14:27 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA09596;
	Tue, 11 Apr 2000 12:12:56 -0600 (MDT)
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 LAA15502;
	Tue, 11 Apr 2000 11:08:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3BI3NU01998
	for ngtrans-dist; Tue, 11 Apr 2000 11:03:23 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3BI3F701991
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 11:03:16 -0700 (PDT)
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 LAA08629
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 11:03:15 -0700 (PDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA22847
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 11:03:14 -0700 (PDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id 112AD3FE; Tue, 11 Apr 2000 13:03:14 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP
	id 81BD8437; Tue, 11 Apr 2000 13:03:13 -0500 (CDT)
Received: by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id OAA0000770461; Tue, 11 Apr 2000 14:03:12 -0400 (EDT)
Date: Tue, 11 Apr 2000 14:03:12 -0400 (EDT)
From: Sowmini Varadhan <varadhan@zk3.dec.com>
Message-Id: <200004111803.OAA0000770461@anw.zk3.dec.com>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
Cc: brian@icair.org, moore@cs.utk.edu, varadhan@quarry.zk3.dec.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Sowmini Varadhan <varadhan@zk3.dec.com>


A few questions about draft-ietf-ngtrans-6to4-04.txt (which clarified
several details missing in draft*6to4-03.txt!)

- the spec does not insist that  the 6to4 router must have V4ADDR
  configured on one of its interfaces. All I could find stated was:

  "2. IPv6 Prefix Allocation

   Suppose that a subscriber site has at least one valid, globally
   unique 32-bit IPv4 address, referred to in this document as V4ADDR.
   This address MUST be duly allocated to the site by an address
   registry (possibly via a service provider) and it MUST NOT be a
   private address [RFC 1918].
    :
    :
   The subscriber site is then deemed to have the following IPv6 address
   prefix, without any further assignment procedures being necessary:
      Prefix length: 48 bits
      Format prefix: 001
      TLA value: 0x0002
      NLA value: V4ADDR",

   and, in Section 5.1,

  "It is RECOMMENDED that in any case each site should use only one IPv4
   address per 6to4 router, and that should be the address assigned to
   the external interface of the 6to4 router. " 

  But, there is only 1 node in the 6to4 site that will accept  and decapsulate
  packets with V4 dst set to V4ADDR, so this node MUST be a 6to4 router
  for sending_rule to be deployed. So it looks like there must necessarily
  be at least 1 6to4 router in a 6to4 site that has V4ADDR configured on
  one of its interfaces, and, if there are multiple 6to4 routers in a site
  that use the same V4ADDR, only one of these will actually execute
  the decapsulation_rule, so 6to4 sites should (SHOULD?) use a different
  V4ADDR for each 6to4 router?



- I was having some difficulty parsing the statement below, taken from
  Page 5 (in the newly added Terminology section):

  "Note: an IPv6 node may in some cases use a 6to4 address for a
   configured tunnel. Such a node may function as a 6to4 host and it may
   also serve as a 6to4 router for other 6to4 hosts, but these are
   distinct functions."

 Is this statement trying to say that
  o a host with a 6to4 address on its config-tunnel interface, 
              and simultaneously be a 
  o a 6to4 router on its virtual 6to4 interface?

  Or is it trying to say something else?

- Anything about NUD on 6to4 links? For example, does the 6to4 link 
  have link-layer addresses (and therefore options) for NUD? It feels like
  link-layer options are redundant for NUD, for the same reasons that
  they are redundant over configured tunnels. 

- 2010 should be 2002 in the lines taken from Section 5.4 below:

  "2010::/16 routing advertisements within the native IPv6 world.  Like.."

  "routing policy to ensure that traffic to 2010::/16 follows the.."

--Sowmini



From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 11 15:05:58 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 PAA17428
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Apr 2000 15:05:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA18419;
	Tue, 11 Apr 2000 13:04:15 -0600 (MDT)
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 LAA28324;
	Tue, 11 Apr 2000 11:58:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3BIqau02068
	for ngtrans-dist; Tue, 11 Apr 2000 11:52:36 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3BIqQ702061
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 11:52:28 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA03832;
	Tue, 11 Apr 2000 11:40:44 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01778;
	Tue, 11 Apr 2000 12:40:43 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id DAA24204;
	Wed, 12 Apr 2000 03:40:37 +0900 (JST)
To: Bob Fink <fink@es.net>
cc: NGtrans List <ngtrans@sunroof.eng.sun.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>
In-reply-to: fink's message of Mon, 10 Apr 2000 12:29:12 MST.
      <4.2.2.20000410122510.01a70a30@imap2.es.net>
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) working group last call for MECH-05 - closes 24 April 2000
From: itojun@iijlab.net
Date: Wed, 12 Apr 2000 03:40:36 +0900
Message-ID: <24202.955478436@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>The following MECH-05 draft has just been published and contains changes 
>from accumulated comments. The author and the chairs felt it appropriate to 
>redo the last call.

	I got two comments on it.  Thank you for clarifying ingress filtering
	rules.

itojun


section 3.6 says this:

>   After the decapsulation the node SHOULD silently discard a packet
>   with an invalid IPv6 source address.  This includes IPv6 multicast
>   addresses, the unspecified address, and the loopback address but also
>   IPv4-mapped IPv6 source addresses where the IPv4 part of the address
    ~~~~~~~~~~~~~~~~~~~~~~~
>   is an (IPv4) multicast address, broadcast address, 0.0.0.0, or
>   127.0.0.1.  In general it SHOULD apply the rules for martian
>   filtering in [18] and ingress filtering [13] on the IPv4-compatible
>   source address.

The underlined part is a typo.  It should be "IPv4-compatible IPv6 source".
In certain cases it is more secure to drop packets with IPv4-mapped IPv6
address as well, though.



mech-05 page 19 suggests to use fe80:0:0:0:0:0:ipv4addr as link-local address
for tunnel interfaces.  It was not in RFC1933.

>   The Interface Identifier [14] of an IPv4 interface is the 32-bit IPv4
>   address of that interface, with the bytes in the same order in which
>   they would appear in the header of an IPv4 packet, padded at the left
>   with zeros to a total of 64 bits.  Note that the "Universal/Local"
>   bit is zero, indicating that the Interface Identifier is not globally
>   unique.  When the host has more than one IPv4 address in use on the
>   physical interface concerned, an administrative choice of one of
>   these IPv4 addresses is made.
>   The IPv6 Link-local address [14] for an IPv4 virtual interface is
>   formed by appending the Interface Identifier, as defined above, to
>   the prefix FE80::/64.
>
>   +-------+-------+-------+-------+-------+-------+------+------+
>   |  FE      80      00      00      00      00      00     00  |
>   +-------+-------+-------+-------+-------+-------+------+------+
>   |  00      00   |  00   |  00   |   IPv4 Address              |
>   +-------+-------+-------+-------+-------+-------+------+------+

The wording is not very clear about if it is a requirement or one example.
This looks for me to be just an example, since there's no real requirement
for putting IPv4 address into the link-local address, since:
- we do not use lowermost 4 bytes for special use
- the story does not change even if we use random number with u/l bit set to 0
- we will know about duplication by DAD
I agree IPv4 address is a good pick for avoiding duplication, however,
it becomes tricky whenever IPv4 address of the node changes (renumbered).
I'd suggest to make it clearer that it is only an example.


From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 11 16:22:38 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 QAA19515
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Apr 2000 16:22:36 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA14012;
	Tue, 11 Apr 2000 14:20:32 -0600 (MDT)
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 NAA13600;
	Tue, 11 Apr 2000 13:13:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3BK6MV02129
	for ngtrans-dist; Tue, 11 Apr 2000 13:06:22 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3BK6D702122
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 13:06:15 -0700 (PDT)
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 NAA07955
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 13:06:12 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA09101
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 13:06:11 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id VAA37532; Tue, 11 Apr 2000 21:01:36 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id VAA22510; Tue, 11 Apr 2000 21:01:45 +0100 (BST)
Message-ID: <38F38439.9249A74F@hursley.ibm.com>
Date: Tue, 11 Apr 2000 14:59:53 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Sowmini Varadhan <varadhan@zk3.dec.com>
CC: ngtrans@sunroof.eng.sun.com, brian@icair.org, moore@cs.utk.edu,
        varadhan@quarry.zk3.dec.com
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
References: <200004111803.OAA0000770461@anw.zk3.dec.com>
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

Sowmini,

Good comments. Most of them I can deal with as text clarifications, but 
what do you recommend we should say for NUD?

FYI, the multicast section will be largely removed in the next version;
it's broken. Dave Thaler offered to do a separate draft on multicast.

   Brian

Sowmini Varadhan wrote:
> 
> A few questions about draft-ietf-ngtrans-6to4-04.txt (which clarified
> several details missing in draft*6to4-03.txt!)
> 
> - the spec does not insist that  the 6to4 router must have V4ADDR
>   configured on one of its interfaces. All I could find stated was:
> 
>   "2. IPv6 Prefix Allocation
> 
>    Suppose that a subscriber site has at least one valid, globally
>    unique 32-bit IPv4 address, referred to in this document as V4ADDR.
>    This address MUST be duly allocated to the site by an address
>    registry (possibly via a service provider) and it MUST NOT be a
>    private address [RFC 1918].
>     :
>     :
>    The subscriber site is then deemed to have the following IPv6 address
>    prefix, without any further assignment procedures being necessary:
>       Prefix length: 48 bits
>       Format prefix: 001
>       TLA value: 0x0002
>       NLA value: V4ADDR",
> 
>    and, in Section 5.1,
> 
>   "It is RECOMMENDED that in any case each site should use only one IPv4
>    address per 6to4 router, and that should be the address assigned to
>    the external interface of the 6to4 router. "
> 
>   But, there is only 1 node in the 6to4 site that will accept  and decapsulate
>   packets with V4 dst set to V4ADDR, so this node MUST be a 6to4 router
>   for sending_rule to be deployed. So it looks like there must necessarily
>   be at least 1 6to4 router in a 6to4 site that has V4ADDR configured on
>   one of its interfaces, and, if there are multiple 6to4 routers in a site
>   that use the same V4ADDR, only one of these will actually execute
>   the decapsulation_rule, so 6to4 sites should (SHOULD?) use a different
>   V4ADDR for each 6to4 router?
> 
> - I was having some difficulty parsing the statement below, taken from
>   Page 5 (in the newly added Terminology section):
> 
>   "Note: an IPv6 node may in some cases use a 6to4 address for a
>    configured tunnel. Such a node may function as a 6to4 host and it may
>    also serve as a 6to4 router for other 6to4 hosts, but these are
>    distinct functions."
> 
>  Is this statement trying to say that
>   o a host with a 6to4 address on its config-tunnel interface,
>               and simultaneously be a
>   o a 6to4 router on its virtual 6to4 interface?
> 
>   Or is it trying to say something else?
> 
> - Anything about NUD on 6to4 links? For example, does the 6to4 link
>   have link-layer addresses (and therefore options) for NUD? It feels like
>   link-layer options are redundant for NUD, for the same reasons that
>   they are redundant over configured tunnels.
> 
> - 2010 should be 2002 in the lines taken from Section 5.4 below:
> 
>   "2010::/16 routing advertisements within the native IPv6 world.  Like.."
> 
>   "routing policy to ensure that traffic to 2010::/16 follows the.."
> 
> --Sowmini


From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 11 17:59:17 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 RAA22823
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Apr 2000 17:59:16 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA26926;
	Tue, 11 Apr 2000 15:57:17 -0600 (MDT)
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 OAA04934;
	Tue, 11 Apr 2000 14:54:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3BLrb202278
	for ngtrans-dist; Tue, 11 Apr 2000 14:53:37 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3BLrT702271
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 14:53:31 -0700 (PDT)
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 OAA04667
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 14:53:30 -0700 (PDT)
Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20485
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 14:53:30 -0700 (PDT)
Received: by ztxmail03.ztx.compaq.com (Postfix, from userid 12345)
	id C30E0431; Tue, 11 Apr 2000 16:53:29 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail03.ztx.compaq.com (Postfix) with ESMTP
	id 529BC4AF; Tue, 11 Apr 2000 16:53:29 -0500 (CDT)
Received: by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id RAA0000805401; Tue, 11 Apr 2000 17:53:29 -0400 (EDT)
Date: Tue, 11 Apr 2000 17:53:29 -0400 (EDT)
From: Sowmini Varadhan <varadhan@zk3.dec.com>
Message-Id: <200004112153.RAA0000805401@anw.zk3.dec.com>
To: brian@hursley.ibm.com, varadhan@zk3.dec.com
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
Cc: brian@icair.org, moore@cs.utk.edu, ngtrans@sunroof.eng.sun.com,
        varadhan@quarry.zk3.dec.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Sowmini Varadhan <varadhan@zk3.dec.com>

> From owner-ngtrans@sunroof.eng.sun.com Tue Apr 11 16:26:03 2000
> Sowmini,
> 
> Good comments. Most of them I can deal with as text clarifications, but 
> what do you recommend we should say for NUD?

How about something similar to Section 3.8 of draft-ietf-ngtrans-mech-05.txt?

> FYI, the multicast section will be largely removed in the next version;
> it's broken. Dave Thaler offered to do a separate draft on multicast.

Good! The cross-references to PIM were non-intuitive so I'm glad it's
going to be addressed separately.

--Sowmini


From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 11 18:33:43 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 SAA23376
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Apr 2000 18:33:42 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA22639;
	Tue, 11 Apr 2000 16:32:46 -0600 (MDT)
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 PAA24774;
	Tue, 11 Apr 2000 15:32:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3BMUvI02467
	for ngtrans-dist; Tue, 11 Apr 2000 15:30:57 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.85.31] (may be forged))
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3BMUl702460
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 15:30:47 -0700 (PDT)
Received: from lillen (lillen.Eng.Sun.COM [129.146.86.161])
	by jurassic.eng.sun.com (8.10.1+Sun/8.10.1) with SMTP id e3BMUiw970082;
	Tue, 11 Apr 2000 15:30:44 -0700 (PDT)
Date: Tue, 11 Apr 2000 14:48:12 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) working group last call for MECH-05 - closes 24 April 2000
To: itojun@iijlab.net
Cc: Bob Fink <fink@es.net>, NGtrans List <ngtrans@sunroof.eng.sun.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>
In-Reply-To: "Your message with ID" <24202.955478436@coconut.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.955489692.6658.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>


> The underlined part is a typo.  It should be "IPv4-compatible IPv6 source".
> In certain cases it is more secure to drop packets with IPv4-mapped IPv6
> address as well, though.

Oops - I'll fix.

> mech-05 page 19 suggests to use fe80:0:0:0:0:0:ipv4addr as link-local address
> for tunnel interfaces.  It was not in RFC1933.

Yes, but it was in mech-04.


> The wording is not very clear about if it is a requirement or one example.
> This looks for me to be just an example, since there's no real requirement
> for putting IPv4 address into the link-local address, since:
> - we do not use lowermost 4 bytes for special use
> - the story does not change even if we use random number with u/l bit set to
> 0 - we will know about duplication by DAD
> I agree IPv4 address is a good pick for avoiding duplication, however,
> it becomes tricky whenever IPv4 address of the node changes (renumbered).
> I'd suggest to make it clearer that it is only an example.

I'll stick in a "MUST" to get:
The Interface Identifier [14] for such an Interface MUST be the 32-bit 
IPv4 address of that interface, with the bytes in the same order in 
...

(I think I got the text from 6over4 originally.)

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 01:56:15 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 BAA06175
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 01:56:14 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA18876;
	Tue, 11 Apr 2000 23:55:34 -0600 (MDT)
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 WAA21386;
	Tue, 11 Apr 2000 22:55:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3C5rhj02790
	for ngtrans-dist; Tue, 11 Apr 2000 22:53:43 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3C5rX702783
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 22:53:34 -0700 (PDT)
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 WAA17830
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Apr 2000 22:53:31 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA18276;
	Tue, 11 Apr 2000 23:53:30 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id OAA01156;
	Wed, 12 Apr 2000 14:53:28 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Bob Fink <fink@es.net>, NGtrans List <ngtrans@sunroof.eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>
In-reply-to: Erik.Nordmark's message of Tue, 11 Apr 2000 14:48:12 MST.
      <Roam.SIMC.2.0.6.955489692.6658.nordmark@jurassic>
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) working group last call for MECH-05 - closes 24 April 2000
From: itojun@iijlab.net
Date: Wed, 12 Apr 2000 14:53:28 +0900
Message-ID: <1154.955518808@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> The wording is not very clear about if it is a requirement or one example.
>> This looks for me to be just an example, since there's no real requirement
>> for putting IPv4 address into the link-local address, since:
>> - we do not use lowermost 4 bytes for special use
>> - the story does not change even if we use random number with u/l bit set to
>> 0 - we will know about duplication by DAD
>> I agree IPv4 address is a good pick for avoiding duplication, however,
>> it becomes tricky whenever IPv4 address of the node changes (renumbered).
>> I'd suggest to make it clearer that it is only an example.
>I'll stick in a "MUST" to get:
>The Interface Identifier [14] for such an Interface MUST be the 32-bit 
>IPv4 address of that interface, with the bytes in the same order in 
>...
>(I think I got the text from 6over4 originally.)

	hmm, MUST looks too strong to me, as the choice for interface
	identifier does not raise any interop issue.  also it would prevent us
	from becoming IPv4 renumber independent.  how about SHOULD?

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 07:14:47 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 HAA15349
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 07:14:46 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA11056;
	Wed, 12 Apr 2000 05:13:44 -0600 (MDT)
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 EAA02556;
	Wed, 12 Apr 2000 04:13:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CBCWh02878
	for ngtrans-dist; Wed, 12 Apr 2000 04:12:32 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CBCL702871
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 04:12:22 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id EAA07839
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 04:12:20 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA10528
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 05:12:19 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15266;
	Wed, 12 Apr 2000 07:12:18 -0400 (EDT)
Message-Id: <200004121112.HAA15266@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-templin-ngtrans-v6v4compat-00.txt
Date: Wed, 12 Apr 2000 07:12:17 -0400
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.


	Title		: An IPv6-IPv4 Compatibility Aggregatable Global Unicast Address Format
	Author(s)	: F. Templin
	Filename	: draft-templin-ngtrans-v6v4compat-00.txt
	Pages		: 12
	Date		: 07-Apr-00
	
This memo specifies an IPv6-IPv4 compatibility aggregatable global
unicast address format for any IPv6 host, gateway or router that has at
least one globally unique IPv4 address. The approach outlined in this memo allows for large-scale incremental deployment of IPv6 hosts within
heterogeneous IPv6/v4 domains without incurring aggregation scaling issues at the border gateways. This address format supports both global routing within the native IPv6 routing domain and automatic tunneling across IPv4 networks with no native IPv6 support. This memo additionally specifies a non-globally routable IPv6-IPv4 compatibility address format for use within private networks with non-globally unique IPv4 addresses. Finally, this memo proposes a method for global routing of such addresses through a combination of mechanisms specified in this document and other works in progress in the NGTRANS working group.

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

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-templin-ngtrans-v6v4compat-00.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-templin-ngtrans-v6v4compat-00.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:	<20000411135429.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-templin-ngtrans-v6v4compat-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 07:23:29 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 HAA15350
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 07:14:46 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA11058;
	Wed, 12 Apr 2000 05:13:44 -0600 (MDT)
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 EAA13421;
	Wed, 12 Apr 2000 04:13:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CBBvI02869
	for ngtrans-dist; Wed, 12 Apr 2000 04:11:57 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CBBk702862
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 04:11:47 -0700 (PDT)
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 EAA14043
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 04:11:45 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA09704
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 04:11:43 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15180;
	Wed, 12 Apr 2000 07:11:41 -0400 (EDT)
Message-Id: <200004121111.HAA15180@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-hometun-00.txt
Date: Wed, 12 Apr 2000 07:11:41 -0400
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		: IPv6 over IPv4 tunnels for home to Internet access
	Author(s)	: F. Dupont
	Filename	: draft-ietf-ngtrans-hometun-00.txt
	Pages		: 3
	Date		: 11-Apr-00
	
Many Internet access providers for residential customers provide
only one dynamic IPv4 address to their clients. This document
proposes in such cases to use an IPv6 over IPv4 tunnel with IPSec
(this gives a static global routable address or prefix with security)
and to implement the processing at the server end of unsolicited
neighbor advertisements for overriding the IPv4 address at the
client end when it changes.

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

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-hometun-00.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-hometun-00.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:	<20000411095927.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-hometun-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 10:28:30 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 KAA21992
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 10:28:30 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA09919;
	Wed, 12 Apr 2000 08:27:08 -0600 (MDT)
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 HAA04420;
	Wed, 12 Apr 2000 07:26:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CEOl902940
	for ngtrans-dist; Wed, 12 Apr 2000 07:24:47 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CEOe702933
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 07:24:40 -0700 (PDT)
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 HAA29760
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 07:24:40 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA08199
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 08:24:38 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA23476; Wed, 12 Apr 2000 15:20:31 +0100
Received: from hursley.ibm.com (lig32-227-11-59.us.lig-dial.ibm.com [32.227.11.59]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA20306; Wed, 12 Apr 2000 15:20:41 +0100 (BST)
Message-ID: <38F48631.362847B7@hursley.ibm.com>
Date: Wed, 12 Apr 2000 09:20:33 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Sowmini Varadhan <varadhan@zk3.dec.com>
CC: moore@cs.utk.edu, ngtrans@sunroof.eng.sun.com, varadhan@quarry.zk3.dec.com
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
References: <200004112153.RAA0000805401@anw.zk3.dec.com>
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

Sowmini Varadhan wrote:
> 
> > From owner-ngtrans@sunroof.eng.sun.com Tue Apr 11 16:26:03 2000
> > Sowmini,
> >
> > Good comments. Most of them I can deal with as text clarifications, but
> > what do you recommend we should say for NUD?
> 
> How about something similar to Section 3.8 of draft-ietf-ngtrans-mech-05.txt?

Yes, I thought exactly that while reviewing -mech-05 yesterday. In fact
one possibility is to add a general comment that anything not covered
in the 6to4 spec is done exactly as described for tunnels in -mech-05.

    Brian


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 11:10:56 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 LAA23802
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 11:10:55 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA06689;
	Wed, 12 Apr 2000 09:08:46 -0600 (MDT)
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 IAA04814;
	Wed, 12 Apr 2000 08:05:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CF3xk02982
	for ngtrans-dist; Wed, 12 Apr 2000 08:03:59 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CF3q702975
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 08:03:52 -0700 (PDT)
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 IAA28028
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 08:03:52 -0700 (PDT)
Received: from ztxmail05.ztx.compaq.com (ztxmail05.ztx.compaq.com [161.114.1.209])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA22211
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 08:03:51 -0700 (PDT)
Received: by ztxmail05.ztx.compaq.com (Postfix, from userid 12345)
	id 051996E2; Wed, 12 Apr 2000 10:03:48 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail05.ztx.compaq.com (Postfix) with ESMTP
	id 44A1041A; Wed, 12 Apr 2000 10:03:48 -0500 (CDT)
Received: by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id LAA0000925400; Wed, 12 Apr 2000 11:03:47 -0400 (EDT)
Date: Wed, 12 Apr 2000 11:03:47 -0400 (EDT)
From: Sowmini Varadhan <varadhan@zk3.dec.com>
Message-Id: <200004121503.LAA0000925400@anw.zk3.dec.com>
To: brian@hursley.ibm.com, varadhan@zk3.dec.com
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
Cc: moore@cs.utk.edu, ngtrans@sunroof.eng.sun.com, varadhan@quarry.zk3.dec.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Sowmini Varadhan <varadhan@zk3.dec.com>

> one possibility is to add a general comment that anything not covered
> in the 6to4 spec is done exactly as described for tunnels in -mech-05.

I'm not sure it would be a good idea to default to mech-05
for all issues, because it would  raise the question "which kind of 
tunnels - automatic or configured?", and pull in details like 
unidirectional/bidirectional connectivity, link-local address 
requirements etc. 

Maybe a cross-reference to Section 3.8 would be sufficient?

--Sowmini


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 12:34:29 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 MAA26728
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 12:34:28 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA08431;
	Wed, 12 Apr 2000 10:33:06 -0600 (MDT)
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 JAA16115;
	Wed, 12 Apr 2000 09:31:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CGUYG03028
	for ngtrans-dist; Wed, 12 Apr 2000 09:30:34 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CGUQ703021
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 09:30:27 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id JAA15852
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 09:30:26 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA06651
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 10:30:20 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA13378; Wed, 12 Apr 2000 17:26:11 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA23304; Wed, 12 Apr 2000 17:26:20 +0100 (BST)
Message-ID: <38F4A3A9.D7C08878@hursley.ibm.com>
Date: Wed, 12 Apr 2000 11:26:17 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Sowmini Varadhan <varadhan@zk3.dec.com>
CC: moore@cs.utk.edu, ngtrans@sunroof.eng.sun.com, varadhan@quarry.zk3.dec.com
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
References: <200004121503.LAA0000925400@anw.zk3.dec.com>
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

Sowmini Varadhan wrote:
> 
> > one possibility is to add a general comment that anything not covered
> > in the 6to4 spec is done exactly as described for tunnels in -mech-05.
> 
> I'm not sure it would be a good idea to default to mech-05
> for all issues, because it would  raise the question "which kind of
> tunnels - automatic or configured?", and pull in details like
> unidirectional/bidirectional connectivity, link-local address
> requirements etc.

True. I have no strong view on this.
 
> Maybe a cross-reference to Section 3.8 would be sufficient?

I will certainly do that in any case.

Thanks

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 12:59:28 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 MAA27572
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 12:59:27 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA28208;
	Wed, 12 Apr 2000 10:58:44 -0600 (MDT)
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 JAA03256;
	Wed, 12 Apr 2000 09:57:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CGtmj03056
	for ngtrans-dist; Wed, 12 Apr 2000 09:55:48 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CGtf703049
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 09:55:42 -0700 (PDT)
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 JAA21255
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 09:55:41 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA03379
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 09:55:40 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA09536; Wed, 12 Apr 2000 17:55:26 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA23540; Wed, 12 Apr 2000 17:55:38 +0100 (BST)
Message-ID: <38F4AA90.D79E2834@hursley.ibm.com>
Date: Wed, 12 Apr 2000 11:55:44 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: templin@erg.sri.com, NGTRANS List <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <200004101135.HAA05668@ietf.org>
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

Hi Fred,

An interesting draft. I'm not sure that I know yet whether I like it or
hate it :-)

The "hate" issue is whether the notion of triggering automatic encapsulation
has dangers (security, routing loops, etc.). Looking into the ID field to 
trigger encapsulation is a kludge, and we have to decide if it's one we 
can live with. I think you need to do what we did for 6to4: 
write out the sending rule, and draw diagrams of various secenarios,
to understand what is really going on.

The notion of translating the ID in the gateway is definitely a no-no.
We aren't allowed to break the end to end model with IPv6 since we rely on
it for IPSEC, and we mandate IPSEC for IPv6. 

You may have noticed in the latest version of 6to4 that we deprecate using
Net 10 addresses to generate a 6to4 prefix, but I think the idea of using
them (tagged "local") to generate a host ID is probably safe. It is also vital,
since the fundamental objection to your scheme is that we don't have enough
unique IPv4 addresses anyway, so they are no good as unique identifiers.

Given that, I see your scheme and 6to4 as potentially complementary.

Unfortunately the text on multicast in 6to4 that you cite turns out to
be rubbish. It will be removed from the next version of the 6to4 draft,
and a separate document has been promised by an expert.

I hope we get a chance to review this at the Pittsburgh IETF, complete
with scenarios.

    Brian Carpenter


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 13:26:45 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 NAA28463
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 13:26:44 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA18711;
	Wed, 12 Apr 2000 11:25:50 -0600 (MDT)
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 KAA27733;
	Wed, 12 Apr 2000 10:24:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CHN6r03088
	for ngtrans-dist; Wed, 12 Apr 2000 10:23:06 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CHMx703081
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 10:22:59 -0700 (PDT)
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 KAA09622
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 10:22:58 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA16480
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 12 Apr 2000 11:22:57 -0600 (MDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id KAA27993;
	Wed, 12 Apr 2000 10:22:53 -0700 (PDT)
Message-ID: <38F4B0ED.2563C20B@erg.sri.com>
Date: Wed, 12 Apr 2000 10:22:53 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian E Carpenter <brian@hursley.ibm.com>
CC: NGTRANS List <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <200004101135.HAA05668@ietf.org> <38F4AA90.D79E2834@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Brian,

Thankyou for your initial comments. I'd like to point out that
this work has evolved independently from the 'ngtrans' works, of
which I have only very recently become aware. I have had my head
buried in a project involving a combination of Mobile IP and a
MANET-like micro-mobility routing protocol since about July of
last year and needed to come up with a way of leveraging the
advanced features of Mobile IPv6 from within an heterogeneous
IPv6/IPv4 network. So, I gradually devised the scheme described
in this draft with reference to the IPNG RFC's and by adding
extensions to the INRIA IPv6 implementation under FreeBSD.

When I finally got a chance to catch my breath from the focused
project work about a month ago, I caught my first glimpse of '6to4'
and realized that I had been working in something of a parallel
universe. But, I felt it appropriate to disclose my approach to
the 'ngtrans' group in the case that any of my methods might prove
helpful in the transition to IPv6.

I will take a closer look at your comments and send my responses.
As to reviewing the draft, I have been in communication with the
'ngtrans' working group chairs who have invited me to present
either at the upcoming interim meeting or at the next IETF in
Pittsburgh. I believe the interim meeting will be held in Palo
Alto, CA sometime within the next two months, and this would be
the more convenient timing and location for me. But, I can also
attend Pittsburgh if this would be preferred.

Regards,

Fred
templin@erg.sri.com


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 12 14:04:32 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 OAA29844
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Apr 2000 14:04:31 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA18399;
	Wed, 12 Apr 2000 12:03:12 -0600 (MDT)
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 KAA07659;
	Wed, 12 Apr 2000 10:56:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3CHt6W03123
	for ngtrans-dist; Wed, 12 Apr 2000 10:55:06 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3CHt0703116
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 10:55:00 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id KAA17633
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 10:54:59 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey [129.146.85.69])
	by sappey.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA23260
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Apr 2000 10:54:59 -0700 (PDT)
Message-ID: <38F4B873.202FE3CC@sappey.eng.sun.com>
Date: Wed, 12 Apr 2000 10:54:59 -0700
From: Alain Durand <Alain.Durand@eng.sun.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Interim Meeting: Call for volunteers
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@eng.sun.com>
Content-Transfer-Encoding: 7bit

Hi everybody

After the announce of the interim meeting, we have received some
comments about the date and the potential benefits of an
interim meeting. Some people expressed the concern that too much
traveling was already taking place.

For such a meeting to be successful, it has to be well prepared and well

focused. What we (chairs) have in mind is examining the security issues
and
the difficult corner cases associated with each of the mechanisms we
have today.

So we would like to make a call for volunteer. We're looking for people
to
pick a document (one they have not directly contribute to), and
screen it for any potential security issue (e.g. denial of service
attack).
We're also looking for people to build complex scenarios involving one
or more mechanism and reporting what would failed.

If you think you can volunteer, please sent  e-mail directly to me
(not to the list) and indicate:
a) which document you'd like to examine
b) which case you'd be looking at (security or corner cases)
c) if you think you could be ready for an interim meeting in May or June

    or if you would prefer to report in the normal meeting in Pittsburgh

    in August.

Depending on the result of this call for volunteer, we will announce
or cancel the interim meeting.

As people need time to organize travel arrangements, this call for
volunteer will end Monday, 5pm, California time.

    - Alain.





From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 13:10:57 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 NAA08348
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 13:10:55 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA23169;
	Thu, 13 Apr 2000 11:06:57 -0600 (MDT)
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 KAA04119;
	Thu, 13 Apr 2000 10:05:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DH3xO03672
	for ngtrans-dist; Thu, 13 Apr 2000 10:03:59 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DH3p703665
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 10:03:52 -0700 (PDT)
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 KAA19456
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 10:03:51 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA12354
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 10:03:50 -0700 (PDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id KAA06417;
	Thu, 13 Apr 2000 10:03:43 -0700 (PDT)
Message-ID: <38F5FDF0.5361B1A9@erg.sri.com>
Date: Thu, 13 Apr 2000 10:03:44 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian E Carpenter <brian@hursley.ibm.com>
CC: NGTRANS List <ngtrans@sunroof.eng.sun.com>, templin@erg.sri.com
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <200004101135.HAA05668@ietf.org> <38F4AA90.D79E2834@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Brian,

Sorry for the delay on this. As promised, here are some responses
to your initial comments:

Brian E Carpenter wrote:
> 
> Hi Fred,
> 
> An interesting draft. I'm not sure that I know yet whether I like it or
> hate it :-)
> 
> The "hate" issue is whether the notion of triggering automatic encapsulation
> has dangers (security, routing loops, etc.).

I definitely havn't had had enough time to investigate the security
aspects of this fully, but I'm fairly confident there are no new
opportunities for routing loops that didn't previously exist. I will
investigate further for these and other potential pitfalls, however.

> Looking into the ID field to
> trigger encapsulation is a kludge, and we have to decide if it's one we
> can live with.

I didn't percieve any negative connotations from this comment, but I
think I should point out that my encapsulation method derives directly
from either existing standards or proposed extensions to existing
standards that I describe in the draft. So, I don't agree that this
method could be considered a "kludge".

First, the IANA OUI (00-00-5E) is an official assignment from the
IEEE Registration Authority, and the Internet Assigned Numbers
documents describe its standard usage for EUI48-format IEEE 802
addresses. Any other usage of the IANA OUI is in violation of the
current standards.

Secondly, the IEEE has specified a new address format called EUI64
which has been adopted by Internet RFC 2373 for the formation of
interface identifiers. EUI64 additionaly specifies a method for
encapsulating legacy EUI48 addresses within EUI64 addresses; namely,
if the two octets of the EUI64 address immediately following the three
octet OUI are 0xFFFE, then the EUI64 address encapsulates a legacy
EUI48 address. (EUI64 also reserves the value 0xFFFF for the two octets
following the OUI for future use.)

So, at a minimum, software must examine the octet immediately following
the OUI to determine whether the address is in native EUI64 format, or
whether it (potentially) encapsulates a legacy EUI48 address. Finally,
EUI64 implies that, beyond the two "special" encodings described in the
previous paragraph, administrative authourities for individual OUI's
should define an EUI64 addressing architecture specific to the OUI
they administer. My draft proposes one possible EUI64 addressing
architecture for IANA's OUI assignment that simultaneously:

  1) satisfies the EUI64 standard
  2) provides a format for encapsulation of IPv4 addresses
  3) allows maximal expansion for future IANA use

So, if my proposed extensions to support EUI64 addresses under the
IANA OUI are eventually adopted, my method for embedding IPv4
addresses would become a "standard"; not a "kludge".

I know I've already beaten this horse to death, but I feel I should
point out what this means to S/W implementations. In the INRIA
implementation, at least, IPv6 addresses can be accessed as either
16 contiguous octets or 4 contiguous 4-octet integers. To check for
an embedded IPv4 address encapsulated in the method described in
my draft, the INRIA S/W only needs to do a compare of the third
integer in the IPv6 address against the value: 0x02005EFE in
big-endian architectures or: 0xFE5E0002 in little-endian architectures.
So, a single machine instruction tells whether/not the interface
identifier encapsulates an IPv4 address.

One final whimsical thought on this subject is that the 6to4 draft
points out that IPv4 is essentially treated as a virtual link layer;
a concept which I fully agree with. If so, then what better place
to encode the IPv4 address than in the interface identifier portion
of the IPv6 address? (Tounge is in cheek, here...)    

> I think you need to do what we did for 6to4:
> write out the sending rule, and draw diagrams of various secenarios,
> to understand what is really going on.

I agree with this, and will write out the sending rules as you
suggest before presenting the draft at an upcoming meeting. I believe
the method described in my draft will satisfy most of the same
scenarios as 6to4 (I will verify this), but since it was designed
with Mobile IP and MANET-style routing in mind I believe it may also
address additional scenarios.

For instance, a mobile host with an IPv6-IPv4 compatibility address
constructed in the method described in my draft could leave its home
subnet and keep its EUI64 interface identifier when joining a new
subnet. There, it might learn a new IPv6 routing prefix from router
advertisments and construct a care-of address that is topologically
correct for the new subnet using IPv6 address auto-configuration.
Yet, the interface identifier would still preserve the embedded IPv4
address.  
 
> The notion of translating the ID in the gateway is definitely a no-no.
> We aren't allowed to break the end to end model with IPv6 since we rely on
> it for IPSEC, and we mandate IPSEC for IPv6.

OK - thanks for pointing this out.
 
> You may have noticed in the latest version of 6to4 that we deprecate using
> Net 10 addresses to generate a 6to4 prefix, but I think the idea of using
> them (tagged "local") to generate a host ID is probably safe. It is also vital,
> since the fundamental objection to your scheme is that we don't have enough
> unique IPv4 addresses anyway, so they are no good as unique identifiers.

OK. My document might seem to imply that these IPv6-IPv4 compatibility
addresses would need to be deployed everywhere (thereby exhausting the
already-exhausted IPv4 address space), but in reality there would only
need to be at most one such address deployed per subnet; other hosts
could use native IPv6 addresses. I will try to make this clearer as
I write up the scenarios.
 
> Given that, I see your scheme and 6to4 as potentially complementary.
> 
> Unfortunately the text on multicast in 6to4 that you cite turns out to
> be rubbish. It will be removed from the next version of the 6to4 draft,
> and a separate document has been promised by an expert.
> 
> I hope we get a chance to review this at the Pittsburgh IETF, complete
> with scenarios.

OK. I'm looking forward to meeting the group and discussing the draft
at an upcoming meeting. Thanks for your comments.
 
>     Brian Carpenter

Fred
templin@erg.sri.com


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 17:06:46 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 RAA14088
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 17:06:44 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA17567;
	Thu, 13 Apr 2000 15:04:43 -0600 (MDT)
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 OAA00764;
	Thu, 13 Apr 2000 14:01:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DKxtj03808
	for ngtrans-dist; Thu, 13 Apr 2000 13:59:55 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DKxm703801
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 13:59:48 -0700 (PDT)
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 NAA16155
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 13:59:47 -0700 (PDT)
Received: from bbmail1-out.unisys.com (bbmail1-out.unisys.com [192.63.108.40])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA20576
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 13:59:45 -0700 (PDT)
Received: from trsvrbk.tr.unisys.com (trsvrbk.tr.unisys.com [192.63.236.1])
	by bbmail1-out.unisys.com (8.9.3/8.9.3) with ESMTP id UAA00838;
	Thu, 13 Apr 2000 20:57:28 GMT
Received: from US-TR-EXCH-1.tr.unisys.com by trsvrbk.tr.unisys.com (8.8.5/8.8.5) id UAA05264 ; Thu, 13 Apr 2000 20:58:53 GMT
Received: by us-tr-exch-1.tr.unisys.com with Internet Mail Service (5.5.2650.21)
	id <2H5LRHZB>; Thu, 13 Apr 2000 16:59:56 -0400
Message-ID: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com>
From: "Sellers, Julian P" <Julian.Sellers@UNISYS.com>
To: "'Fred L. Templin'" <templin@erg.sri.com>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.
	txt
Date: Thu, 13 Apr 2000 16:59:36 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Sellers, Julian P" <Julian.Sellers@UNISYS.com>

Fred,

The following is from 3.1 of the draft:

	It is also important to notice that, in the intra-domain case, IPv4
    addresses may not be globally unique but may be allocated through some
    private network addressing scheme which has meaning only within the
    context of that domain. But, we can construct a SECOND form of the
    IPv6-IPv4 compatibility address described in section 2 by inverting
    the sense of the 'u/l' bit for private IPv4 addresses. For example,
    a node with the private (non globally unique) IPv4 address 10.0.0.1
    could be assigned the IPv6-IPv4 compatibility address:

	3FFE:1a05:510:200:0000:5EFE:10.0.0.1

    (using the same example IPv6 prefix and IANA OUI given in section 2)
    with the 'u/l' bit in the EUI-64 interface identifier cleared to
    indicate that this is a LOCAL address. But, such an address could be
    treated using the same routing decision policies given above in the
    intra-domain case since private addresses are eligible for IPv4 routing
	 within that domain.

I don't think this is acceptable because when the u/l bit is clear, no
assumptions can be made regarding the interface-id contents.  Anyone can
assign an interface-id of 0000:5EFE:xxxx:xxxx in which xxxx:xxxx is not an
IPv4 address.

Julian


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 17:33:54 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 RAA14536
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 17:33:53 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA10433;
	Thu, 13 Apr 2000 15:32:48 -0600 (MDT)
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 OAA08717;
	Thu, 13 Apr 2000 14:32:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DLUdl03850
	for ngtrans-dist; Thu, 13 Apr 2000 14:30:39 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DLUW703843
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 14:30:32 -0700 (PDT)
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 OAA24087
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 14:30:32 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA11567
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 14:30:29 -0700 (PDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id OAA08709;
	Thu, 13 Apr 2000 14:30:23 -0700 (PDT)
Message-ID: <38F63C70.BE34391D@erg.sri.com>
Date: Thu, 13 Apr 2000 14:30:24 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Sellers, Julian P" <Julian.Sellers@unisys.com>
CC: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>,
        templin@erg.sri.com
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Julian,

Yes, I think your point is valid. I think perhaps my document
"overloads" the meaning of the u/l bit in that I was planning to
use it to infer whether the embedded IPv4 address is globally
routable or not. (In addition to the intended EUI64 meaning,
which is to tell whether/not a link-level address is eligible
for joining an unrestricted multiple-access datalink.)

However, I think I can re-word the draft to say that the u/l bit
will also be '1' even in the case that the embedded IPv4 address
is non globally routable (i.e. network 10 and its siblings). Two
factors make this possible:

 1) The IPv4 forwarding code in an inter-domain IPv6-in-IPv4 tunnel
    endpoint would recognize the embedded IPv4 address as non globally
    routable and would thus refuse to forward it. (Layer-3
    consideration). 

 2) The EUI64 addresses constructed using the method described in my
    draft would never be used in place of an OEM network interface
    manufacturer's burned-in IEEE 802 MAC address at the datalink
    level. (Layer-2 consideration).

I'll go back and see if I can address this with better wording
in the draft.

Thanks,

Fred
templin@erg.sri.com  

"Sellers, Julian P" wrote:
> 
> Fred,
> 
> The following is from 3.1 of the draft:
> 
>         It is also important to notice that, in the intra-domain case, IPv4
>     addresses may not be globally unique but may be allocated through some
>     private network addressing scheme which has meaning only within the
>     context of that domain. But, we can construct a SECOND form of the
>     IPv6-IPv4 compatibility address described in section 2 by inverting
>     the sense of the 'u/l' bit for private IPv4 addresses. For example,
>     a node with the private (non globally unique) IPv4 address 10.0.0.1
>     could be assigned the IPv6-IPv4 compatibility address:
> 
>         3FFE:1a05:510:200:0000:5EFE:10.0.0.1
> 
>     (using the same example IPv6 prefix and IANA OUI given in section 2)
>     with the 'u/l' bit in the EUI-64 interface identifier cleared to
>     indicate that this is a LOCAL address. But, such an address could be
>     treated using the same routing decision policies given above in the
>     intra-domain case since private addresses are eligible for IPv4 routing
>          within that domain.
> 
> I don't think this is acceptable because when the u/l bit is clear, no
> assumptions can be made regarding the interface-id contents.  Anyone can
> assign an interface-id of 0000:5EFE:xxxx:xxxx in which xxxx:xxxx is not an
> IPv4 address.
> 
> Julian


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 19:36: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 TAA15924
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 19:36:50 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA00520;
	Thu, 13 Apr 2000 17:35:30 -0600 (MDT)
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 QAA18060;
	Thu, 13 Apr 2000 16:35:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DNY1Z03971
	for ngtrans-dist; Thu, 13 Apr 2000 16:34:01 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DNXt703964
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:33:55 -0700 (PDT)
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 QAA05733
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:33:54 -0700 (PDT)
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 RAA29490
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 17:33:53 -0600 (MDT)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.222] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12ft7P-0007MA-00; Thu, 13 Apr 2000 16:33:51 -0700
Message-Id: <4.2.2.20000410163708.01960628@imap2.es.net>
X-Sender: rlfink@imap2.es.net
Disposition-Notification-To: <fink@es.net>
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 13 Apr 2000 16:33:48 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) draft minutes of NGtrans WG Meeting at IETF-47 in Adelaide
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>
Content-Transfer-Encoding: 8bit

NGtrans folk,

Enclosed are the draft minutes of the Adelaide ngtrans meetings. Please 
send any errors, omissions, changes, etc. directly to me.

Sorry for the delay, but have been on travel from Adelaide until this week.


Thanks,

Bob

=============================
Minutes of NGtrans WG Meeting
27/29 March 2000
Adelaide IETF-47
___

Chairs:

Alain Durand <Alain.Durand@eng.sun.com>
Bob Fink <fink@es.net>
Tony Hain <tonyhain@microsoft.com>

This ngtrans meeting reported by Bob Fink and Tony Hain.
Attendance was ~150.

Alain Durand & Bob Fink chaired the meeting.

___

Administrative information:

Discussion ngtrans: <mailto: ngtrans@sunroof.eng.sun.com>
Subscribe ngtrans: <mailto: majordomo@sunroof.eng.sun.com> "subscribe ngtrans"
Archive ngtrans: <http://www.wcug.wwu.edu/lists/ngtrans/>
Web site: <http://www.6bone.net/ngtrans>

Discussion 6bone: <mailto: 6bone@isi.edu>
Subscribe 6bone: <mailto: majordomo@isi.edu> "subscribe 6bone"
Archive 6bone: <http://www.wcug.wwu.edu/lists/6bone/>
Web site: <http://www.6bone.net>

___

Agenda

Project status report - Bob Fink

BT Patent IPR status - Bob Fink

MECH-04 update status - Erik Nordmark

6to4-04 new draft - Brian Carpenter

DSTM-01 new draft - Laurent Toutain

SOCKS-03 new draft - Hirsohi Kitamura

TRANSLATOR-03 new draft - Kazu Yamamoto

BROKER-02 - Ivano Guardini

Tunnel Discovery - ALain Durand

TCPUDP-RELAY-00 new draft - Jun-ichiro itojun Hagino

TRANSITION-03 new draft - Alain Durand

6PAPA-01 new draft - Bob Fink

pTLA-00 new draft - Bob Fink

ABUSE-00 new draft  - Jun-ichiro itojun Hagino

Interim NGtrans meeting planning - Alain Durand & Bob Fink

PingERv6 Report - Les Cottrell

Relocated 6bone registry - David Kessens

6tap report - Florent Parent

pTLA reliability report - Ivano Guardini

Root name server issues - Akira Kato

---

Project status report - Bob Fink

Bob presented the status of all ngtrans projects from the ngtrans web
site's project status pages:

<http://www.6bone.net/ngtrans/ngtrans_project-status.html>

Let Bob know of any errors.

---

BT Patent IPR status - Bob Fink

Bob Fink related the background and current status of the BT patent issue.

  1. BT notified the IETF Secretariat on Nov 5, 1999 that:

     "In accordance with the IETF Rules, BT would like to disclose that we
      have recently applied for patents in the IPv6 space relating to:
       * the establishment of tunnels using DNS as the tunnel
         endpoint discovery mechanism and

       * a mechanism that enables translation and tunneling
         to be combined into a single device.

     BT does so in the belief that these recent patent application are
     relevant to present discussions within the IETF."

2. After the IETF Secretariat queried BT, a reply was received on
    Nov 12, 1999, saying:

    "Also in accordance with IETF Rules, BT hereby gives the assurance that,
     following approval by the IESG of the relevant Internet standards
     specification, BT will grant licences under these patent applications
     and under any resultant patents, on openly specified, reasonable and
     non-discriminatory terms, to implement the Internet standards specifi-
     cation, provided the licensee similarly grants licences under its
     necessary applications/patents."
3.  BT is under no responsibility to say more about their possible patents
     than they already have.
4.  From the information on hand, or likely to become available, there is
     no clear way of telling if any work now underway in ngtrans is possibly
     affected by BT patents.
5.  If any ngtrans work eventually is covered by BT patents, BT's assurance
     to grant licenses is minimally acceptable according to Steve Coya, IETF
     Secretariat:
     "Note that during the Stockholm meeting, the concept of determining
      whether the licensing was openly specified, reasonable and non-discri-
      minatory terms would be based on implementor feedback (i.e. if enough
      folks entered into an agreement, that would be sufficient to "prove" or
      demonstrate that the licensing arrangements were palatable. This
      will be treated like an option when/if the protocol is submitted for
      consideration as a Draft Standard."
6.   Thus there is no reason to do other than proceed with all work now
      underway in ngtrans.

Not hearing anything to the contrary, Bob declared the BT issue closed
for now.

---

ABUSE-00 new draft  - Jun-ichiro itojun Hagino

Itojun gave a report of potential abuses to IPv6 transition mechanisms
that is available at:

<http://6bone.net/ngtrans/IETF47-Adelaide/draft-itojun-ipv6-transition-abuse 
-00a.txt>

The document talks about possible abuse of IPv6 transition technologies,
which may lead to denial-of-service (DoS) attacks and other problems.
IPv6 transition technologies, namely IPv6 over IPv4 tunnelling speci-
fications and some others, have room for abuse by malicious parties.
Detailed descriptions and possible workarounds are supplied.

The specific areas of problems noted were:

  Abuse of IPv4 compatible address
  Abuse of 6to4 address
  Abuse of IPv4 mapped address

For which he gave possible solutions (see the paper).

His recommendations to future proposals were:

  If you use tunnels, require explicit configuration
    Manual configuration
    Authenticated automatic configuration

  Don't put IPv4 address into IPv6 address, for purpose of relays

  Do not define IPv6 addresses that are not used on the wire
    Makes it much harder to check

and his summary:

  Bad guys can abuse some of transition techniques

  Don't run 6to4/auto tunnel relay, if you don't need one
    Be careful about v4 mapped address

  What to do next?
    Incorporate checks presented here, into original proposals
    Publish it as separate document (informational?)

  Let us check other proposals as well

  Let us deploy native IPv6 network sooner, so that we no longer need tunnels

---

MECH-04 update status - Erik Nordmark

Erik noted changes he has made to MECH-04 in preparation for MECH-05.

-  Specified when to put IPv6 addresses in the DNS.

-  Added reference to the tunnel mib for TTL specification for the tunnels.

-  Added recommendations for use of source and target link layer address
    options for the tunnel links.

-  Added checks in the decapsulation checking both an IPv4-compatible
    IPv6 source address and the outer IPv4 source addresses for multicast,
    broadcast, all-zeros etc.

Erik will issue MECH-05 as soon as he can (already done on April 6 and a wg
last call issued).

---
6to4-04 new draft - Brian Carpenter

Brian presented the changes from -03 to -04 and highlighted issues remaining.

CHANGES
•	added terminology section
•	another revision of address selection text
•	described link local address formation
•	changed sending rule to refer to next hop
•	removed confusing text on IPv4 header padding
•	clarification/corrections to exterior routing discussion
       (scenarios with & without BGP)
•	clarified MTU text again
•	added section on routing loops
•	added and removed text on multicast
•	added text on RSIP
•	reformulated section on Intranet usage
        (use of Net 10 addresses now forbidden)
•	clarifications/response to detail comments

ISSUES
•	text on PIM-SM needs checking by a PIM-SM expert
•	Is link-local address really needed?
•	host-only draft: volunteer needed
•	Is this ready for PS?

Brian thanked Jim Bound's group for their comments.

Regarding link local there was a debate about its need. Itojun argued that
it was necessary, and it was agreed to pursue this discussion on the list.

There was discussion of the need to rewrite the multicast section.

Steve Deering was asked to comment on PIM-SM usage in 6to4. He felt that
the problem generalized to the NBMA network case, noting that MARS was
the state-of-the-art in this regard.

There was concern about the applicability of IPv4 tools in the IPv6 space

There was a call for review of the multicast section by experts.

Brian noted that the security section already talks about ingress filtering
in regards to Itojun's abuse concerns (covered earlier in these minutes).

Brian stated that he would like to try to move 6to4 to PS before Pittsburgh.

---

DSTM-01 new draft - Laurent Toutain

Laurent made a few comments on the new DSTM-01 draft and DSTM status in 
general:

• cleaned up text

• 6->4 is mandatory

• 4->6 is optional

• 4->4 is optional

• implementation in bsd (inria)

• dhcpv6 concurrent work : only 4 messages needed

• modify dns when v4 query fails

• question about timeouts : timer in dstm based on pool

• will use implementations to adjust timers : new text next time

---

SOCKS-03 new draft - Hirsohi Kitamura

Hiroshi gave a status report on the new -03 draft:

• IESG comments were incorporated into -03

• there are two available independent implementations
   NEC:  <http://www.socks.nec.com>
   KAME: <ftp://kame.net/pub/kame/misc/socks64-...>

• there are about 5000 downloads/year of the SOCKS code
   from 80 different countries

• a -04 will be out soon to answer other comments

---

TRANSLATOR-03 new draft - Kazu Yamamoto

Kazu gave a status report on the new -03 draft called
Overview of Transition Techniques for IPv6-only to Talk to IPv4-only
Communication, which was previously called Categorizing Translators
between IPv4 and IPv6

Background

• The previous version "02" was published in Oct 1999

• Comments from IESG in Dec 1999

   Wording
     Bilingual -> dual-stack
     Proxy -> application level gateway
     Definition of "translator" is unclear
   Weakness
     Some explanations in this memo are not applicable to SIIT (FTP, IPsec, 
...)
     SOCKS5 is not TCP-relay

   Situation is changing
     This draft was based on a paper of INET 1998 (written in 1997)
     It is getting harder to modify IPv6 hosts

• Version "03" was published in Mar 2000

Differences between -02 and -03

• Title
   OLD: Categorizing Translators between IPv4 and IPv6
   NEW: Overview of Transition Techniques for IPv6-only to Talk to IPv4-only
    Communication

• Wording
   Defined "translator" in this memo an intermediate component between an IPv4
   host and an IPv6 host to enable direct communication between them, without
   requiring any modifications to them

• Accepted IESG's comments

• Assumption
   OLD: We can change IPv6 hosts as we like
   NEW: It is difficult to change IPv6 hosts
   Outside the scope
     SOCKS5
     SIIT
     BIS
   Mechanisms requiring specific functionality for IPv6 hosts

• Address mapping:
   OLD: Suggested to use both DNS hack and resolver hack
   NEW: Suggest to use DNS hack only
        Resolver hack means changing IPv6 hosts

Next step

• Authors hope:
   to publish it as Informational RFC
   then to help the ROADMAP document project

Kazu asked the chairs to please return -03 to the IESG to continue
processing there towards Informational RFC.

---

BROKER-02 - Ivano Guardini

Ivano gave a status report of the older -02 draft:

• WG last call after Washington IETF
• One comment about MIME type
• -02 draft not updated yet

• Plan A:
    Include MIME media-type definition in the document?
    Other WG may benefit from the MIME-type

• Plan B:
    Publish framework as Informational
    Publish MIME-type as separate,informational RFC

• Actions for Plan B
    Remove implementation section (appendix)
    Add short discussion as MIME-type as implementation option
    Open door for the use of Tunnel Broker concept in other areas
    Publish framework as Informational RFC
    Publish MIME-type description in a separate document

• Proposed MIME type
    application/tunnel
    parameters: ipv6/ipv4
      src,dst v4 & v6 address
      Tunnel management procedure
        TTL with sub-parameter TTL value
        something smarter?
      Textual description
      ...

• a -03 draft will be published soon

---

Tunnel Discovery - ALain Durand

Alain presented his ideas on Tunnel Endpoint Discovery, exploring
new directions:
<http://6bone.net/ngtrans/IETF47-Adelaide/tep1.ppt>

Granularity of tunnel end point discovery mechanism
	
• Automatic tunnels: 1 host (/128)
• 6over4: 1 host (/128)
• Tunnel broker: typically 1 host (/128)
• 6to4: 1 site (/48)
• Might be a need for other granularity:
   /64, /56, /49 intra-site
   /35, /29, /24 wan

Potential candidate: DNS...

• DNS is a natural distributed model
   network administrators know DNS
   DNS can handle different levels of granularity
• But:
   DO NOT CREATE ANY NEW RR TYPE
   DO NOT CALL DNS FOR EVERY SINGLE PACKET

Tunnel End Point Discovery Process Steps

1. Source S sends a packet to D1, packet goes to exit router R,
    but R has no route for D1...
2. Router R uses DNS to discover Tunnel End Point  (TEP) IPv4 address.
    It also discovers that TEP is responsible for P/24. There is a TTL
    associated to the DNS response.
3. Router R create a uni-directional tunnel to TEP
    and add a route for P/24 through that tunnel.
    Packets are routed to D1 using P/24 IPv6 infrastructure
4. Source S2 now sends a packet to D2. As D2 is part of P/24,
    router R already has a route for it. It does not need to do another DNS 
query.
    It routes the packet through the existing tunnel.
5. After TTL expires, router R delete the tunnel and the route for P/24

DNS mechanism

• Dedicated reverse tree tunnel6.ip6.int
• DNAME for delegation
• Wildcard entries for PTR
• Reserved label "tunnel6" tag prefix len

Configuration example

• Tunnel end point for 3ffe:0300::/24 is 129.88.26.7

   \[x3ffe/16].tunnel6.ip6.int IN DNAME 16.tunnel6.6bone.net.

   \[x03/8].16.tunnel6.6bone.net. IN DNAME 24.tunnel6.imag.fr.

   *.24.tunnel6.imag.fr. IN PTR basta.imag.fr.

   basta.imag.fr IN A 129.88.26.7

Query example

• Query:

   PTR for 1.0.0....0.0.3.0.e.f.f.3.tunnel6.ip6.int.

• Response:

   1.0.0....0.0.3.0.e.f.f.3.24.tunnel6.imag.fr. IN PTR basta.imag.fr.
   basta.imag.fr. IN A 129.88.26.7

At the end of Alain's presentation there were various comments:

• that iesg needs to decide about ipv6.int

• that using dns to do routing is a bad idea

• that using dns for real-time services will fail

• that using dns will be more painful than the account can absorb

• that this needs service location & routing to make it work

• question about what is better about this than 6to4

No conclusion was reached about the pursuit of this effort, stay tuned.

---

TCPUDP-RELAY-00 new draft - Jun-ichiro itojun Hagino

Itojun gave a presentation of his new draft called An IPv6-to-IPv4
transport relay translator:

• Transparent TCP relay
   Has been used in firewall-oriented products like TIS gauntret
• We can use it for IPv6-to-IPv4 translation
• No extra configuration/code on end node
• No tricky MTU issues
• Stateful TCP relay box
   A TCP connection goes through single TCP relay box
   Can place multiple boxes against multiple clients
• We have been using it for more than 3 years, working just great
   ... we thought we'd better document it
• The talk will focus on:
   IPv6-to-IPv4 translation (IPv4-to-IPv6 is possible)
   TCP relay (UDP is also possible)

Transparent TCP relays (IPv4-to-IPv4)

• A originates TCP to X (A -> X)
• TCP relay box hijacks the connection and terminate it at B (A -> B)
• TCP relay box originates TCP to X (Y -> X)
• TCP relay box relays content across two TCP connections
• originating node (A) --> TCP relay box (as X, interface is B)
    address on IP header: A -> X
• TCP relay box (Y) --> destination node (X)
    address on IP header: Y -> X

Transparent TCP relays (IPv6-to-IPv4)

• Reserve an IPv6 /64 prefix R6::/64, announce routes
• A6 originates TCP to C6::X4 (A6 -> R6::X4)
• TCP relay box hijacks the connection and terminate it at B6 (A6 -> B6)
• TCP relay box originates TCP to X4 (Y4 -> X4)
• TCP relay box relays content across two TCP connections
• IPv6 TCP: originating node (A6) --> TCP relay box (as R6::X4, interface 
is B6)
    address on IPv6 header: A6 -> R6::X4
• IPv4 TCP: TCP relay box (Y4) --> destination node (X4)
    address on IPv4 header: Y4 -> X4

Address mapping

• Similar to other translation techniques
• Modified DNS server
   For installation to large site
• Special entries in /etc/hosts
   For small installation
• Modified resolver on the originating node
   Not recommended, modifying originating node makes it hard to deploy

Multiple servers, for scalability/availability

• Setup multiple TCP relay boxes
• Assign different reserved prefix, advertise all of them
• Present different fake address by DNS round-robin or alike
   Once TCP is established we don't change address pair
• When B6/Y4 goes down, connections through D6/Z4 will be okay

Notes

• No need to care about path MTU/fragmentation issues
   Per-packet translation needs a great care
• Need to care about urgent data
• Can relay UDP
   Recognize UDP "connection" like NAT does
• Can relay IPv4-to-IPv6
   Address mapping issue
• To relay FTP need to rewrite payload data
• Access control is mandatory
   Malicious party can take advantage of it to anonymize connection
• KAME has been using this for 3 years, works quite well
   Served 100+ nodes at ipngwg Tokyo interim meeting
   We have been using it in many occasions
• Two "tricky" name server implementations exist
   totd/newbie
   {Free,Net,Open}BSD includes this FreeBSD 4.0: IPv6 enabled by default!

Wrap-up

• IPv6-to-IPv4 translation using TCP relays
• Simple implementation, works very well
• No change in end node - can serve any of existing IPv6 nodes
• Would like to issue it as an informational RFC, to help future implementers
   Not a new protocol, fits best to informational
• ngtrans project, or individual submission?

• To try it out from terminal room: to your IPv4 133.138.1.134,
     telnet 3ffe:501:4819:ffff::133.138.1.134
     ssh -v 3ffe:501:4819:ffff::133.138.1.134

   Travels Adelaide -- Tokyo -- your place, may add delay

Noted that it should refer to existing list of applications affected by nat

It was agreed that ngtrans would take on this as a project. Tthere was
some minor debate about whether it should be Informational or Standards
track, which resulted in the chairs determining (for now) that Informational
RFC was most consistent with other ongoing and past projects.

---

TRANSITION-03 new draft - Alain Durand

Alain gave a status report on the "roadmap" transition document effort:

Update

• New scenarii
   large new IPv6 network
   ISP
• Update of all references
• Clarification text on
   Tunnel Broker, Bis, BiAPI, 6to4, DSTM, OSPF, 6PAPA
• Remove all mention to particular implementation

New Structure

1. Introduction
2. General deployment issues
3. Basic transition mechanisms (RFC1933 & update)
4. The tools
4.1 connecting IPv6 islands
4.2 communication between IPv4 & IPv6
5 & 6. scenarii

Work continues!

---

6PAPA-01 new draft - Bob Fink

Bob noted that he had not issued a new draft for balloting, nor the 6bone
steering committee, as the RIRs were now reviewing their IPv6 address
allocation policies which could affect 6PAPA. Thus he will wait until
it is clear that the 6bone prequalification for sub-TLA allocation will
stay in place.

---

pTLA-00 new draft - Bob Fink

Bob reported that he had written the pTLA draft for the purpose of
documenting existing pTLA/pNLA 6bone prefix formats, and would soon
do a wg last call for Informational.

---

Interim NGtrans meeting plannng - Alain Durand & Bob Fink

Alain & Bob expressed the need to have an interim ngtrans meeting to:

• review state of the tools for
   security issues & corner cases
• recent proposals
• explore new directions
• industry evaluation

It was proposed to hold it in the San Francisco area, probably hosted
by Sun. Some possible dates were balloted for interest:

~4 for May 23-25

~6 for May 30-31, June 1 (just after US memorial day)

~8 for June 6-8 (conflict in Japan)

Sentiments seemed low on the need for an interim. The chairs
agreed to continue looking into the viability of a meeting as well as
when it might be, if one was held. Stay tuned.

---

PingERv6 Report - Les Cottrell

Bob Fink introduced Les Cottrell (of the US SLAC accelerator laboratory)
noting that his group's efforts to use inexpensive and easily deployable
methods to measure the quality of Internet paths had been highly successful
for IPv4, and that Les' group at SLAC had extended them to IPv6.

Les presented their work:

<http://6bone.net/ngtrans/IETF47-Adelaide/pinger61.ppt>

PingER (for IPv4)
• Simple active end-to-end ping monitoring
• Main community is HENP & ESnet sites
• 30 monitoring sites in 15 countries
• 593 nodes at 424 sites in 72 countries
• ~ 2200 pairs

PingER6 (for IPv6)

• A small amount of bandwidth is carved off ESnet connection to provide
   native IPv6 service to SLAC
• Recompiled Linux 2.2.5-15 (Red Hat 6.0) kernel with IPv6 support
• Downloaded & installed inet-apps (including ping) from inner.net and
   patch for glibc-2.1 systems
• Wrote Perl module to provide IPv6 DNS lookup
• Currently one monitoring site at SLAC

• PingER6 has been an international effort
• 6Bone and 6REN sites participating in 10 countries, 40 sites
• Currently little knowledge of networks and connections.
• Not surprisingly, same issues as the ipv4 Internet.
   Not enough bandwidth
• but it is only experimental
• How to persuade users to try it out ?
   Bob Fink big help in signing people up
   Contact warrenm@slac.stanford.edu to join PingER6
• Next steps
   Address concerns over security
   More Monitoring Sites
• 6-Tap a good place for a PingER
• China ?

Les thanked all the sites who have participated.

More Information requested from all possible participants

•IEPM/PingER home site
<http://www-iepm.slac.stanford.edu/>

• Very interesting Polish 6BONE ping site
<http://6bone-gw.6bone.pl/mrtg/>


Les was asked to discuss relationship to similar tools, and Les responded
that PingER results were well aligned to special hardware solution, like
Internet Surveyor, for a cheap solution.

Les noted that icmp is treated differently, but that practice shows there
is little affect in most places due to rate limiting. When this is observed
to be a problem new target sites are chosen.

He closed noting that the PingER6 efforts will continue and encourage all
interested to participate.

---

Relocated 6bone registry - David Kessens

---

6tap report - Florent Parent

Florent reproted on the current status of the 6tap, which is jointly
managed by Canarie/Viagenie and ESnet at the Chicago StarTAP.

• a tunnel server will be installed next week as an extension of native
IPv6 service to provide site-level tunnel support (as opposed to the
tunnel brokers individual host tunnel support).

• in addition, a route server & registry service will be developed
     solaris 8 server w/ATM to ESnet
     MRTd (Merit)
     IPv6 registry (Kessens)

• next: 6to4 relay service & stats

<http://www.6tap.net>

---

pTLA reliability report - Ivano Guardini

Ivano gave a report on the reliability of routing in the 6bone:

<http://6bone.net/ngtrans/IETF47-Adelaide/reliability-6bone.ppt>

• bgp4+ monitoring effort

• ~50% more prefixes announced than the pTLA list would suggest

• unaggregated prefixes are the bulk: multi-homed leaking

• filtering out nosiest sites: 80% of sites are almost always reachable

• most stable plotted against most unstable: instability growing

• upper bound of route instability for 80% of sites is less than 5%

• stability is good for 80%: multihoming is a problem

Results

• The results of the CSELT's 6bone monitoring effort confirm that BGP4+
routing within the 6bone backbone has become highly reliable both with
respect to stability and route availability

• this in turn highlights the good level of maturity reached by the
currently available IPv6 technology some other issues still need to be solved

• multihoming is still a problem

• A subset of these results is regularly updated at:
  <http://carmen.cselt.it/ipv6/bgp/graphs/index.html>

===

Root name server issues - Akira Kato

Akiro gave a brief report on upcoming experimentation
plans for the new BIND release in the root name servers

• experimental operation is planned with a few servers
   which will be operational soon

• separate box for v6

• 3ffe:000[1-d]::/32 for each server or
     use /24 or/28 to each server
     advertise /32 : may violate 6bone routing
     need to modify bgp pathlen filters

Various comments and questions were made:

• why special addresses?

• are these unicast or anycast?

• routing propagation is the issue: special addr not necessary

• no room to add aaaa/a6 in 512 byte

• is edns0 mandatory for ipv6 queries

• ip6.int may be server as well

• one or two servers operational soon

• 512 mtu is bogus in v6

• deployment requires careful thought

• don't worry about edns0 because it covers IPv4 requirements

• separate roots proposed

---

Meeting adjourned.

-end




From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 19:38:46 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 TAA15957
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 19:38:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA01856;
	Thu, 13 Apr 2000 17:37:32 -0600 (MDT)
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 QAA18498;
	Thu, 13 Apr 2000 16:37:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DNaXD03989
	for ngtrans-dist; Thu, 13 Apr 2000 16:36:33 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DNaQ703982
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:36:27 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA06273
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:36:26 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey [129.146.85.69])
	by sappey.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA11069
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:36:22 -0700 (PDT)
Message-ID: <38F659F5.34E41091@sappey.eng.sun.com>
Date: Thu, 13 Apr 2000 16:36:21 -0700
From: Alain Durand <Alain.Durand@eng.sun.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com> <38F63C70.BE34391D@erg.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@eng.sun.com>
Content-Transfer-Encoding: 7bit

The main problem I see with this proposal is related to the sending rules.
I'm not sure to understand how it works.

Next is a quote of the original comments I sent to the author when he
first presented me his draft.


    - Alain.

<==
section 3.1:
    A source node with an
    IPv6-IPv4 compatibility address which sends an IPv6 message to a
    destination node with an IPv6-IPv4 compatibility address can employ
    routing policy decisions such as:

      - if the IPv6 routing table has an entry for the destination's
        IPv6 prefix, and there is a path to gateway for the destination's
        IPv6 prefix through the IPv6 routing infrastructure (*), send as
        a native IPv6 packet to the IPv6 gateway for that prefix

      - if the IPv4 routing table has an entry for a prefix of the
        destination's embedded IPv4 address, tunnel the IPv6 packet
        through the IPv4 routing infrastructure (using IP protocol 41)
        by encapsulating it in the manner described in [MECH] (**)

      - if the IPv6 routing table has an entry for 'default', and there
        is a path to the default IPv6 gateway through the IPv6 routing
        infrastructure (*), send as a native IPv6 packet to the default
        IPv6 gateway

      (*) If there is no path to the IPv6 gateway through the IPv6
          routing infrastructure, tunnel the IPV6 packet through the
          IPv4 routing infrastructure using the gateway's embedded
          IPv4 address as the destination for the tunneled packet.
          This implies that the gateways must also use IPv6-IPv4
          compatibility addresses.

      (**) [MECH] specifies an automatic tunneling mechanism for
           IPv4-compatible addresses formed as the 96-bit prefix
           0:0:0:0:0:0/96 followed by the embedded IPv4 address.
           But, this same mechanism may be used for the IPv6-IPv4
           compatibility address format proposed in this draft
           by truncating the leading 96-bits of the address.
<==

I do not understand choice 1)
"if there is a path to gateway for the destination's
IPv6 prefix through the IPv6 routing infrastructure". This proposal does
not specify how do one discover the existence of such a path.
Typically, how do a host discover that the destination is on an isolated,
non connected IPv6 island?

I fear to understand this this is known by the existence of a non
default IPv6 route for that host...

But, typically a host will have routes for the local prefixes and a default
route
to the nearest router. More, when sending a packet, the host has
no clue about the destination prefix ; all it knows is the destination
address. I would NOT recommend to automatically derived
a /64 prefix out of this destination address and to use this to
walk through the routing table and, worst of all, recommend
that any host should get a default free set of the IPv6 routes...

So, in a typical case where a host only has routing entries for
the local prefixes and the default route AND an IPv4 address,
and my understanding of choice 1) is correct, that is default route
is not taken into account, communication of two 'normal' IPv6 nodes on the same
subnet
will use native IPv6 and communication to any other IPv6 hosts
implementing this proposal will use tunnels over IPv4 regardless
of the IPv6 connectivity. This is, at best, not really optimal...






From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 13 19:46:45 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 TAA16033
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Apr 2000 19:46:45 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA07274;
	Thu, 13 Apr 2000 17:45:52 -0600 (MDT)
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 QAA20092;
	Thu, 13 Apr 2000 16:45:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3DNiYX04007
	for ngtrans-dist; Thu, 13 Apr 2000 16:44:34 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3DNiR704000
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Apr 2000 16:44:27 -0700 (PDT)
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 QAA19845;
	Thu, 13 Apr 2000 16:44:26 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA02010;
	Thu, 13 Apr 2000 16:44:26 -0700 (PDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id QAA09811;
	Thu, 13 Apr 2000 16:44:24 -0700 (PDT)
Message-ID: <38F65BDA.6260391F@erg.sri.com>
Date: Thu, 13 Apr 2000 16:44:26 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@eng.sun.com>
CC: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com> <38F63C70.BE34391D@erg.sri.com> <38F659F5.34E41091@sappey.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Alain and others,

I'm about to leave for the day and will be on travel until Wednesday
of next week. I will take this message with me and will respond to
it (and any other comments the group may have) when I return.

Thanks, and sorry I can't respond more immediately...

Fred
templin@erg.sri.com

Alain Durand wrote:
> 
> The main problem I see with this proposal is related to the sending rules.
> I'm not sure to understand how it works.
> 
> Next is a quote of the original comments I sent to the author when he
> first presented me his draft.
> 
>     - Alain.
> 
> <==
> section 3.1:
>     A source node with an
>     IPv6-IPv4 compatibility address which sends an IPv6 message to a
>     destination node with an IPv6-IPv4 compatibility address can employ
>     routing policy decisions such as:
> 
>       - if the IPv6 routing table has an entry for the destination's
>         IPv6 prefix, and there is a path to gateway for the destination's
>         IPv6 prefix through the IPv6 routing infrastructure (*), send as
>         a native IPv6 packet to the IPv6 gateway for that prefix
> 
>       - if the IPv4 routing table has an entry for a prefix of the
>         destination's embedded IPv4 address, tunnel the IPv6 packet
>         through the IPv4 routing infrastructure (using IP protocol 41)
>         by encapsulating it in the manner described in [MECH] (**)
> 
>       - if the IPv6 routing table has an entry for 'default', and there
>         is a path to the default IPv6 gateway through the IPv6 routing
>         infrastructure (*), send as a native IPv6 packet to the default
>         IPv6 gateway
> 
>       (*) If there is no path to the IPv6 gateway through the IPv6
>           routing infrastructure, tunnel the IPV6 packet through the
>           IPv4 routing infrastructure using the gateway's embedded
>           IPv4 address as the destination for the tunneled packet.
>           This implies that the gateways must also use IPv6-IPv4
>           compatibility addresses.
> 
>       (**) [MECH] specifies an automatic tunneling mechanism for
>            IPv4-compatible addresses formed as the 96-bit prefix
>            0:0:0:0:0:0/96 followed by the embedded IPv4 address.
>            But, this same mechanism may be used for the IPv6-IPv4
>            compatibility address format proposed in this draft
>            by truncating the leading 96-bits of the address.
> <==
> 
> I do not understand choice 1)
> "if there is a path to gateway for the destination's
> IPv6 prefix through the IPv6 routing infrastructure". This proposal does
> not specify how do one discover the existence of such a path.
> Typically, how do a host discover that the destination is on an isolated,
> non connected IPv6 island?
> 
> I fear to understand this this is known by the existence of a non
> default IPv6 route for that host...
> 
> But, typically a host will have routes for the local prefixes and a default
> route
> to the nearest router. More, when sending a packet, the host has
> no clue about the destination prefix ; all it knows is the destination
> address. I would NOT recommend to automatically derived
> a /64 prefix out of this destination address and to use this to
> walk through the routing table and, worst of all, recommend
> that any host should get a default free set of the IPv6 routes...
> 
> So, in a typical case where a host only has routing entries for
> the local prefixes and the default route AND an IPv4 address,
> and my understanding of choice 1) is correct, that is default route
> is not taken into account, communication of two 'normal' IPv6 nodes on the same
> subnet
> will use native IPv6 and communication to any other IPv6 hosts
> implementing this proposal will use tunnels over IPv4 regardless
> of the IPv6 connectivity. This is, at best, not really optimal...


From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 14 11:22:31 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 LAA08938
	for <ngtrans-archive@odin.ietf.org>; Fri, 14 Apr 2000 11:22:30 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA07424;
	Fri, 14 Apr 2000 09:21:15 -0600 (MDT)
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 IAA11566;
	Fri, 14 Apr 2000 08:19:54 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3EFItG04252
	for ngtrans-dist; Fri, 14 Apr 2000 08:18:55 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3EFIm704245
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Apr 2000 08:18:48 -0700 (PDT)
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 IAA26470
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Apr 2000 08:18:48 -0700 (PDT)
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 IAA03750;
	Fri, 14 Apr 2000 08:18:47 -0700 (PDT)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.222] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12g7rq-0001ji-00; Fri, 14 Apr 2000 08:18:46 -0700
Message-Id: <4.2.2.20000414080900.0487dad8@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 14 Apr 2000 08:15:58 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) working group last call for pTLA-00 - closes 28 April 2000
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>,
        Randy Bush <randy@psg.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 pTLA-00 draft has been published for over a month and has only 
attracted a few typo comments so I won't reissue it until I receive more 
comments from this last call. As mentioned at the ngtrans in Adelaide the 
purpose of this draft is to document existing pTLA/pNLA structure used on 
the 6bone, and is intended for Informational RFC.

Thus there will be a two-week ngtrans working group last call.

Comments to the list by 28 April 2000.


Thanks,

Bob

	Title		: 6BONE pTLA and pNLA Formats (pTLA)
	Author(s)	: R. Fink
	Filename	: draft-ietf-ngtrans-6bone-ptla-00.txt
	Pages		: 4
	Date		: 10-Mar-00

<http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6bone-ptla-00.txt>




From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 14 15:12:05 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 PAA13203
	for <ngtrans-archive@odin.ietf.org>; Fri, 14 Apr 2000 15:12:03 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA00956;
	Fri, 14 Apr 2000 13:10:36 -0600 (MDT)
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 MAA18305;
	Fri, 14 Apr 2000 12:09:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3EJ8lg04380
	for ngtrans-dist; Fri, 14 Apr 2000 12:08:47 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3EJ8b704372
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Apr 2000 12:08:37 -0700 (PDT)
Received: from lillen (lillen.Eng.Sun.COM [129.146.86.161])
	by jurassic.eng.sun.com (8.10.1+Sun/8.10.1) with SMTP id e3EJ8Xw532698;
	Fri, 14 Apr 2000 12:08:33 -0700 (PDT)
Date: Fri, 14 Apr 2000 11:23:05 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) working group last call for MECH-05 - closes 24 April 2000
To: itojun@iijlab.net
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, Bob Fink <fink@es.net>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>
In-Reply-To: "Your message with ID" <1154.955518808@coconut.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.955736585.6265.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>


> 	hmm, MUST looks too strong to me, as the choice for interface
> 	identifier does not raise any interop issue.  also it would prevent us
> 	from becoming IPv4 renumber independent.  how about SHOULD?

SHOULD it is.
I'll submit -06 with a SHOULD (and the typo you found corrected).

  Erik



From owner-ngtrans@sunroof.eng.sun.com  Sun Apr 16 14:46:47 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 OAA09631
	for <ngtrans-archive@odin.ietf.org>; Sun, 16 Apr 2000 14:46:47 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA28097;
	Sun, 16 Apr 2000 12:45:21 -0600 (MDT)
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 LAA14819;
	Sun, 16 Apr 2000 11:43:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3GIh3V05319
	for ngtrans-dist; Sun, 16 Apr 2000 11:43:03 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3GIgs705312
	for <ngtrans@sunroof.eng.sun.com>; Sun, 16 Apr 2000 11:42:54 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA17638
	for <ngtrans@sunroof.eng.sun.com>; Sun, 16 Apr 2000 11:42:52 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA27756
	for <ngtrans@sunroof.eng.sun.com>; Sun, 16 Apr 2000 12:42:51 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id DAA08874;
	Mon, 17 Apr 2000 03:42:48 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Bob Fink <fink@es.net>, NGtrans List <ngtrans@sunroof.eng.sun.com>,
        Alain Durand <Alain.Durand@sun.com>,
        Tony Hain <tonyhain@microsoft.com>, Randy Bush <randy@psg.com>
In-reply-to: Erik.Nordmark's message of Fri, 14 Apr 2000 11:23:05 MST.
      <Roam.SIMC.2.0.6.955736585.6265.nordmark@jurassic>
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) working group last call for MECH-05 - closes 24 April 2000
From: itojun@iijlab.net
Date: Mon, 17 Apr 2000 03:42:47 +0900
Message-ID: <8872.955910567@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> 	hmm, MUST looks too strong to me, as the choice for interface
>> 	identifier does not raise any interop issue.  also it would prevent us
>> 	from becoming IPv4 renumber independent.  how about SHOULD?
>SHOULD it is.
>I'll submit -06 with a SHOULD (and the typo you found corrected).

	thanks,

	for future documentations...
	it seems that RFC2472 4.1 is very well-written for interface identifier
	selection for pseudo interfaces (and tunnel interface fits with the
	section very well).  it may be nice if we make a separate document
	from the section and refer it.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 18 07:02:58 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 HAA00478
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Apr 2000 07:02:57 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA04894;
	Tue, 18 Apr 2000 05:02:02 -0600 (MDT)
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 EAA15801;
	Tue, 18 Apr 2000 04:01:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3IB0O206332
	for ngtrans-dist; Tue, 18 Apr 2000 04:00:24 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3IB0G706325
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 04:00:16 -0700 (PDT)
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 EAA05846
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 04:00:15 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA03999
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 05:00:14 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00337;
	Tue, 18 Apr 2000 07:00:13 -0400 (EDT)
Message-Id: <200004181100.HAA00337@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-mech-06.txt
Date: Tue, 18 Apr 2000 07:00:13 -0400
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		: Transition Mechanisms for IPv6 Hosts and Routers
	Author(s)	: R. Gilligan, E. Nordmark
	Filename	: draft-ietf-ngtrans-mech-06.txt
	Pages		: 29
	Date		: 17-Apr-00
	
This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4
routing infrastructures.  They are designed to allow IPv6 nodes to
maintain complete compatibility with IPv4, which should greatly
simplify the deployment of IPv6 in the Internet, and facilitate the
eventual transition of the entire Internet to IPv6.

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

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-mech-06.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-mech-06.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:	<20000417081817.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-mech-06.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 18 20:27:40 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 UAA14980
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Apr 2000 20:27:39 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA10226;
	Tue, 18 Apr 2000 18:26:40 -0600 (MDT)
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 RAA23847;
	Tue, 18 Apr 2000 17:25:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3J0Opi07053
	for ngtrans-dist; Tue, 18 Apr 2000 17:24:51 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3J0Oj707046
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:24:45 -0700 (PDT)
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 RAA13988
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:24:45 -0700 (PDT)
Received: from hotmail.com (f251.law8.hotmail.com [216.33.240.76])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id SAA09361
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 18:24:44 -0600 (MDT)
Received: (qmail 31917 invoked by uid 0); 19 Apr 2000 00:24:40 -0000
Message-ID: <20000419002440.31916.qmail@hotmail.com>
Received: from 128.32.201.94 by www.hotmail.com with HTTP;
	Tue, 18 Apr 2000 17:24:40 PDT
X-Originating-IP: [128.32.201.94]
From: "Pedro Revriego" <revirieg@hotmail.com>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Configured Tunnels 
Date: Tue, 18 Apr 2000 17:24:40 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Pedro Revriego" <revirieg@hotmail.com>


Hi,


I have been looking at some implementations of configured IPv6 in IPv4 
tunnels  and most of then use a tunnel interface for each tunnel.

Would not this be a problem for a router that wants to use a lot of 
configured tunnels ?

Are there any alternative approaches that do not use an interface to set the 
tunnel ??


Best Regards,


Pedro
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 18 20:37:06 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 UAA15117
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Apr 2000 20:37:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA15028;
	Tue, 18 Apr 2000 18:36:23 -0600 (MDT)
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 RAA22677;
	Tue, 18 Apr 2000 17:36:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3J0Z4S07075
	for ngtrans-dist; Tue, 18 Apr 2000 17:35:04 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3J0Yt707068
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:34:55 -0700 (PDT)
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 RAB25707
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:34:56 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA14335
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 18:34:54 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id JAA15151;
	Wed, 19 Apr 2000 09:34:49 +0900 (JST)
To: "Pedro Revriego" <revirieg@hotmail.com>
cc: ngtrans@sunroof.eng.sun.com
In-reply-to: revirieg's message of Tue, 18 Apr 2000 17:24:40 PDT.
      <20000419002440.31916.qmail@hotmail.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) Configured Tunnels 
From: itojun@iijlab.net
Date: Wed, 19 Apr 2000 09:34:49 +0900
Message-ID: <15149.956104489@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>I have been looking at some implementations of configured IPv6 in IPv4 
>tunnels  and most of then use a tunnel interface for each tunnel.
>Would not this be a problem for a router that wants to use a lot of 
>configured tunnels ?

	we have configured 1024 tunnel interfaces with no problem in kernel.
	(there were some problem with routing daemons :-)
	does it look enough?
	freenet6.net uses 500 or some tunnel interfaces in their servers, IIRC.

	possible problem comes from tunnel lookup cost.  we'll need to
	search over these tunnels against incoming packets.  we have never
	measured possible impact/overehead with it though...

>Are there any alternative approaches that do not use an interface to set the 
>tunnel ??

	maybe special entries in routing table?

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 18 20:42:13 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 UAA15156
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Apr 2000 20:42:12 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA17100;
	Tue, 18 Apr 2000 18:41:28 -0600 (MDT)
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 RAA26777;
	Tue, 18 Apr 2000 17:41:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3J0eVV07097
	for ngtrans-dist; Tue, 18 Apr 2000 17:40:31 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3J0eO707090
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:40:25 -0700 (PDT)
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 RAA16929
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 17:40:24 -0700 (PDT)
Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA16614
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 18:40:21 -0600 (MDT)
Received: from cthulhu.engr.sgi.com (gate3-relay.engr.sgi.com [130.62.1.234]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id RAA22238; Tue, 18 Apr 2000 17:35:35 -0700 (PDT)
	mail_from (zamsden@clock.engr.sgi.com)
Received: from clock.engr.sgi.com (clock.engr.sgi.com [163.154.34.45])
	by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF)
	via ESMTP id RAA50739;
	Tue, 18 Apr 2000 17:40:16 -0700 (PDT)
	mail_from (zamsden@clock.engr.sgi.com)
Received: from clock.engr.sgi.com (localhost [127.0.0.1]) by clock.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id RAA54768; Tue, 18 Apr 2000 17:50:27 -0700 (PDT)
Message-Id: <200004190050.RAA54768@clock.engr.sgi.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: "Pedro Revriego" <revirieg@hotmail.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Configured Tunnels 
From: Zachary Amsden <zamsden@cthulhu.engr.sgi.com>
In-Reply-To: Your message of "Tue, 18 Apr 2000 17:24:40 PDT."
             <20000419002440.31916.qmail@hotmail.com> 
Date: Tue, 18 Apr 2000 17:50:26 -0700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Zachary Amsden <zamsden@cthulhu.engr.sgi.com>

> Hi,
> I have been looking at some implementations of configured IPv6 in IPv4 
> tunnels  and most of then use a tunnel interface for each tunnel.

That is most likely because a tunnel per interface is convenient to implement. 
 Multiple tunnels through the same interface is a possibility, but adds 
complexity to the interface.  It also provides a bottleneck point, over which 
you may develop locking contention.

> Would not this be a problem for a router that wants to use a lot of 
> configured tunnels ?

How many is a lot?  Order of magnitude changes many things.  I don't see it as 
a problem, unless the implementation is required to walk the device list for 
some common operation.  To my knowledge, no one has measured the performance 
of large tunnel configurations (in the thousands).  I'm not even sure there 
are enough islands to create such a large tunnel setup yet...

> Are there any alternative approaches that do not use an interface to set the 
> tunnel ??

You could do tunneling in user space, you could use multiple tunnels per 
tunnel device, you could add tunneling information to the routing table, ...

-- 
Zachary Amsden  zamsden@engr.sgi.com  3-6919  31-2-510  Core Protocols




From owner-ngtrans@sunroof.eng.sun.com  Tue Apr 18 21:19:01 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 VAA15451
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Apr 2000 21:19:01 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA02113;
	Tue, 18 Apr 2000 19:17:53 -0600 (MDT)
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 SAA27770;
	Tue, 18 Apr 2000 18:17:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3J1GUh07147
	for ngtrans-dist; Tue, 18 Apr 2000 18:16:30 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3J1GL707140
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 18:16:22 -0700 (PDT)
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 SAA17417
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 18:15:51 -0700 (PDT)
Received: from hotmail.com (f336.law8.hotmail.com [216.33.240.211])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id TAA01158
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 19:15:35 -0600 (MDT)
Received: (qmail 66367 invoked by uid 0); 19 Apr 2000 01:15:35 -0000
Message-ID: <20000419011535.66366.qmail@hotmail.com>
Received: from 128.32.201.94 by www.hotmail.com with HTTP;
	Tue, 18 Apr 2000 18:15:35 PDT
X-Originating-IP: [128.32.201.94]
From: "Pedro Revriego" <revirieg@hotmail.com>
To: itojun@iijlab.net, revirieg@hotmail.com
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Configured Tunnels
Date: Tue, 18 Apr 2000 18:15:35 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Pedro Revriego" <revirieg@hotmail.com>


Hi Again,

In fact I was considering putting the tunnel information in the routing 
table (including the IPv4 addresses for the endpoints of the tunnel) and 
then in both incoming and outgoing messages you can use the table look up 
functions to figure out which tunnel you are using.

The problem is that in the RFC 1933 (actually in the draft) it is mentioned 
the use of NUD in the tunnels and link local addreses and
I do not know how to fit that in the routing table approach...


Best Regards,

Pedro Reviriego
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 19 00:01:41 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 AAA18780
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Apr 2000 00:01:40 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id WAA00680;
	Tue, 18 Apr 2000 22:00:58 -0600 (MDT)
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 UAA02604;
	Tue, 18 Apr 2000 20:59:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3J3wwd07291
	for ngtrans-dist; Tue, 18 Apr 2000 20:58:58 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3J3wq707284
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 20:58:52 -0700 (PDT)
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 UAA16778
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 20:58:52 -0700 (PDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id VAA29899
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Apr 2000 21:58:51 -0600 (MDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 18 Apr 2000 20:57:14 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <271M4650>; Tue, 18 Apr 2000 20:57:13 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF010F59@red-msg-24.redmond.corp.microsoft.com>
From: Brian Zill <bzill@microsoft.com>
To: "'Pedro Revriego'" <revirieg@hotmail.com>, ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) Configured Tunnels 
Date: Tue, 18 Apr 2000 20:57:07 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian Zill <bzill@microsoft.com>

> I have been looking at some implementations
> of configured IPv6 in IPv4 tunnels and most
> of then use a tunnel interface for each tunnel.

Our implementation currently uses a single tunnel pseudo-interface to handle
all tunnels.

> Are there any alternative approaches that do
> not use an interface to set the tunnel ??

Well, you can put them all on one as we did.  However, it's awkward for some
things, and has some non-intuitive side-effects.  So we're thinking about
changing to the separate pseudo-interface per configured tunnel model.

--Brian


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 12:31:06 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 MAA15108
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 12:31:06 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA14620;
	Thu, 20 Apr 2000 10:29:42 -0600 (MDT)
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 JAA20771;
	Thu, 20 Apr 2000 09:27:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3KGPi108601
	for ngtrans-dist; Thu, 20 Apr 2000 09:25:44 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3KGPb708594
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 09:25:37 -0700 (PDT)
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 JAA06426
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 09:25:36 -0700 (PDT)
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 JAA08925
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 09:25:35 -0700 (PDT)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.222] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12iJlg-0004FA-00; Thu, 20 Apr 2000 09:25:29 -0700
Message-Id: <4.2.2.20000420091721.018f9d88@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 20 Apr 2000 09:25:26 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) working group last call for MECH-06 (was MECH-05) - closes 24
  April 2000
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>,
        Randy Bush <randy@psg.com>, Erik Nordmark <Erik.Nordmark@eng.sun.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>

Note that while I was posting the MECH-05 last call, a MECH-06 came out 
(negligible changes, but Erik can say what is different).

So please use this updated version at:

<http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-mech-06.txt>

I will still close the wg last call next Monday unless there is an objection.


Thanks,

Bob

=============
NGtrans Folk,

The following MECH-05 draft has just been published and contains changes 
from accumulated comments. The author and the chairs felt it appropriate to 
redo the last call.

Thus there will be a two-week ngtrans working group last call.

Comments to the list by 24 April 2000.


Thanks,

Bob

 >----------------Begin Forwarded Message----------------<

Date: Mon, 10 Apr 2000 07:34:34 -0400
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-mech-05.txt
To: IETF-Announce@, @
Cc: ngtrans@sunroof.eng.sun.com

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		: Transition Mechanisms for IPv6 Hosts and Routers
	Author(s)	: R. Gilligan, E. Nordmark
	Filename	: draft-ietf-ngtrans-mech-05.txt
	Pages		: 29
	Date		: 06-Apr-00
	
This document specifies IPv4 compatibility mechanisms that can be
implemented by IPv6 hosts and routers.  These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4
routing infrastructures.  They are designed to allow IPv6 nodes to
maintain complete compatibility with IPv4, which should greatly
simplify the deployment of IPv6 in the Internet, and facilitate the
eventual transition of the entire Internet to IPv6.

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

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-mech-05.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-mech-05.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.
 >----------------End Forwarded Message----------------<






From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 13:31:41 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 NAA16669
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 13:31:40 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA00641;
	Thu, 20 Apr 2000 11:30:42 -0600 (MDT)
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 KAA07185;
	Thu, 20 Apr 2000 10:28:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3KHRsu08641
	for ngtrans-dist; Thu, 20 Apr 2000 10:27:54 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3KHRl708634
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 10:27:47 -0700 (PDT)
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 KAA06915;
	Thu, 20 Apr 2000 10:27:45 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA16604;
	Thu, 20 Apr 2000 10:27:44 -0700 (PDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id KAA28504;
	Thu, 20 Apr 2000 10:27:40 -0700 (PDT)
Message-ID: <38FF3DF5.39CB4560@erg.sri.com>
Date: Thu, 20 Apr 2000 10:27:17 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@eng.sun.com>
CC: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com> <38F63C70.BE34391D@erg.sri.com> <38F659F5.34E41091@sappey.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Alain,

I'm just back from my trip; sorry it has taken me so long to
respond to your message. Regarding your comments on the sending
rules, just so that the group is aware I am including below my
previous response to your personal inquiry from back on March 20th.

But, I'd like to point out (as I also mentioned in a response to
Brian Carpenter) that my work evolved from a focused project that
investigated only one possible IPv6-IPv4 compatibility scenario, and
the text from section 3.1 derived out of that one isolated scenario.
So, I don't think it would be energy well spent to try to defend or
refine this particular text further; that would be like trying to
describe the structure of a complex tree by focusing on one of the
leaves.

Instead, I'd like to take a step back and take a top-down (rather
than bottom-up) look at the possible application for my draft by
writing out a variety of scenarios as was done in the 6to4 draft.
(Brian Carpenter also suggested such an approach). This would allow
a study to compare the relative merits for the 6to4 approach, the
approach in my draft, or a combined approach on a case-by-case basis.
In the process, I would expect the text from section 3.1 from my
draft would be replaced by discussion of sending rules as they
relate to the individual scenarios. My plan would be to then update
the existing draft with the new text describing the scenarios and
present the new version of the draft at the next WG meeting.

Do you concur with this approach?

Regards,

Fred Templin
templin@erg.sri.com   

> > section 3.1:
> >     A source node with an
> >     IPv6-IPv4 compatibility address which sends an IPv6 message to a
> >     destination node with an IPv6-IPv4 compatibility address can employ
> >     routing policy decisions such as:
> > 
> >       - if the IPv6 routing table has an entry for the destination's
> >         IPv6 prefix, and there is a path to gateway for the destination's
> >         IPv6 prefix through the IPv6 routing infrastructure (*), send as
> >         a native IPv6 packet to the IPv6 gateway for that prefix
> > 
> >       - if the IPv4 routing table has an entry for a prefix of the
> >         destination's embedded IPv4 address, tunnel the IPv6 packet
> >         through the IPv4 routing infrastructure (using IP protocol 41)
> >         by encapsulating it in the manner described in [MECH] (**)
> > 
> >       - if the IPv6 routing table has an entry for 'default', and there
> >         is a path to the default IPv6 gateway through the IPv6 routing
> >         infrastructure (*), send as a native IPv6 packet to the default
> >         IPv6 gateway
> > 
> >       (*) If there is no path to the IPv6 gateway through the IPv6
> >           routing infrastructure, tunnel the IPV6 packet through the
> >           IPv4 routing infrastructure using the gateway's embedded
> >           IPv4 address as the destination for the tunneled packet.
> >           This implies that the gateways must also use IPv6-IPv4
> >           compatibility addresses.
> > 
> >       (**) [MECH] specifies an automatic tunneling mechanism for
> >            IPv4-compatible addresses formed as the 96-bit prefix
> >            0:0:0:0:0:0/96 followed by the embedded IPv4 address.
> >            But, this same mechanism may be used for the IPv6-IPv4
> >            compatibility address format proposed in this draft
> >            by truncating the leading 96-bits of the address.
> > <==
> > 
> > I do not understand choice 1)
> > "if there is a path to gateway for the destination's
> > IPv6 prefix through the IPv6 routing infrastructure". This proposal does
> > not specify how do one discover the existence of such a path.
> > Typically, how do a host discover that the destination is on an isolated,
> > non connected IPv6 island?
> 
> By this, I mean the source node consults its own IPv6 routing table
> for a prefix match on the IPv6 address of the destination. If there
> is a "reasonable" match, then send the message to the IPv6 gateway
> listed in the IPv6 routing table for this message. But, the source
> node would then need to consult its own IPv6 routing table for a
> prefix match on the IPv6 address of the gateway. This might result
> in an automatic IPv6-in-IPv4 tunnel to the gateway which would then
> forward the message to the destination over either native IPv6
> routing or through yet another automatic tunnel.
>  
> > I fear to understand this this is known by the existence of a non
> > default IPv6 route for that host...
> > 
> > But, typically a host will have routes for the local prefixes and a default route
> > to the nearest router. More, when sending a packet, the host has
> > no clue about the destination prefix ; all it knows is the destination
> > address. I would NOT recommend to automatically derived
> > a /64 prefix out of this destination address and to use this to
> > walk through the routing table and, worst of all, recommend
> > that any host should get a default free set of the IPv6 routes...
> > 
> > So, in a typical case where a host only has routing entries for
> > the local prefixes and the default route AND an IPv4 address,
> > and my understanding of choice 1) is correct, that is default route
> > is not taken into account, communication of two nodes on the same subnet
> > will use native IPv6 and communication to any other IPv6 hosts
> > implementing this proposal will use tunnels over IPv4 regardless
> > of the IPv6 connectivity. This is, at best, not really optimal...
> 
> You're probably right that most hosts will have routes only for the
> local IPv6 prefixes and a default route to the nearest IPv6 router.
> My routing policy decisions above are cast in wet mud at best and
> need alot more thought. It's almost a situation of there being too
> much flexibility with my scheme, but I think a much tighter set of
> routing policy decisions could be constructed given futher analysis.
> 
> Perhaps the optimal solution would be something like a simultaneous
> consultation of both the IPv6 and IPv4 routing tables followed by a
> choice of the "best" route. For example, if the IPv6 routing table
> lookup returns "default" as the best route, but the IPv4 routing
> table returns a host route for the embedded IPv4 address in the
> interface ID, you might opt to tunnel over IPv4 rather than send
> to the default IPv6 router.


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 15:33:45 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 PAA19756
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 15:33:44 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA01480;
	Thu, 20 Apr 2000 13:32:38 -0600 (MDT)
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 MAA02238;
	Thu, 20 Apr 2000 12:30:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3KJSpa08746
	for ngtrans-dist; Thu, 20 Apr 2000 12:28:51 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3KJSi708739
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 12:28:45 -0700 (PDT)
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 MAA23801
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 12:28:43 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA00060
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 12:28:42 -0700 (PDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA44564; Thu, 20 Apr 2000 20:28:22 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA31350; Thu, 20 Apr 2000 20:28:17 +0100 (BST)
Message-ID: <38FF5A59.559ADE19@hursley.ibm.com>
Date: Thu, 20 Apr 2000 14:28:25 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Sowmini Varadhan <varadhan@zk3.dec.com>
CC: ngtrans@sunroof.eng.sun.com, moore@cs.utk.edu
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
References: <200004111803.OAA0000770461@anw.zk3.dec.com>
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

Sowmini Varadhan wrote:
>   ....So it looks like there must necessarily
>   be at least 1 6to4 router in a 6to4 site that has V4ADDR configured on
>   one of its interfaces, and, if there are multiple 6to4 routers in a site
>   that use the same V4ADDR, only one of these will actually execute
>   the decapsulation_rule, so 6to4 sites should (SHOULD?) use a different
>   V4ADDR for each 6to4 router?

While thinking how to fix the text for this comment, I concluded that we can't 
insert the SHOULD since it would preclude anycast towards the decapsulator. Since
6to4 is stateless, there is no reason to prevent anycast. The first part of the
sentence is valid and I've inserted a corresponding requirement.

There will be fixes for the rest of your comments in the next version.

Thanks.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 15:38:58 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 PAA19813
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 15:38:58 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA05526;
	Thu, 20 Apr 2000 13:37:55 -0600 (MDT)
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 MAA06798;
	Thu, 20 Apr 2000 12:36:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3KJZOj08768
	for ngtrans-dist; Thu, 20 Apr 2000 12:35:24 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3KJZH708761
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 12:35:18 -0700 (PDT)
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 MAA03434
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 12:35:15 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA03536
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 13:35:14 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA48198 for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 20:35:02 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA20354 for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 20:35:02 +0100 (BST)
Message-ID: <38FF5BEE.E3B28886@hursley.ibm.com>
Date: Thu, 20 Apr 2000 14:35:10 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) 6to4 issue: link local
References: <4.2.2.20000410163708.01960628@imap2.es.net>
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

From the Adelaide draft minutes:

> Regarding link local there was a debate about its need. Itojun argued that
> it was necessary, and it was agreed to pursue this discussion on the list.

Actually I though he argued that it wasn't necessary, and Steve Deering argued
that it was. As far as there was an opinion in the room, it seemed to be yes,
we should define link local addresses for 6to4 routers; for example they might be
used for establishing adjacency for a multicast routing protocol.

So I will leave it in the draft for now. It's the only open issue I have today.
There will be a new draft soon.

    Brian


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 21:13:36 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 VAA23835
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 21:13:36 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA18668;
	Thu, 20 Apr 2000 19:12:45 -0600 (MDT)
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 SAA02976;
	Thu, 20 Apr 2000 18:10:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3L19d009064
	for ngtrans-dist; Thu, 20 Apr 2000 18:09:39 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3L19U709057
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 18:09:31 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id SAA02830
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 18:09:29 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA17631
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:09:28 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA18710;
	Fri, 21 Apr 2000 10:09:07 +0900 (JST)
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: brian's message of Thu, 20 Apr 2000 14:35:10 EST.
      <38FF5BEE.E3B28886@hursley.ibm.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) 6to4 issue: link local
From: itojun@iijlab.net
Date: Fri, 21 Apr 2000 10:09:07 +0900
Message-ID: <18708.956279347@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> Regarding link local there was a debate about its need. Itojun argued that
>> it was necessary, and it was agreed to pursue this discussion on the list.
>Actually I though he argued that it wasn't necessary, and Steve Deering argued
>that it was.

	just to clarify: Brian is correct, I argued that it wasn't necessary.

>As far as there was an opinion in the room, it seemed to be yes,
>we should define link local addresses for 6to4 routers; for example they might be
>used for establishing adjacency for a multicast routing protocol.

	I'm still not convinced.  Without mapping to link layer address
	(= IPv4) it will only confuse source selection on sender, and
	will confuse peers if you use linklocal as source address.
	Also, I thought that it is the beauty of 6to4 that we don't need
	ND on 6to4 cloud.

	How about adding link-local to interface, but mark it as deprecated
	address (i.e. lifetime expired) to make sure it won't be picked
	as source?

itojun


From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 22:34:00 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 WAA26261
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 22:33:59 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA14184;
	Thu, 20 Apr 2000 20:33:01 -0600 (MDT)
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 TAA18624;
	Thu, 20 Apr 2000 19:31:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3L2Tmo09147
	for ngtrans-dist; Thu, 20 Apr 2000 19:29:48 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3L2Td709139
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:29:40 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id TAA22065
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:29:39 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by sappey.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA01365
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Apr 2000 17:35:11 -0700 (PDT)
Message-ID: <38FE50BF.1C54B6B5@sappey.eng.sun.com>
Date: Wed, 19 Apr 2000 17:35:11 -0700
From: Alain Durand <Alain.Durand@eng.sun.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Interim Meeting: Canceled
References: <38F4B873.202FE3CC@sappey.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@eng.sun.com>
Content-Transfer-Encoding: 7bit

From all the responses I got and after discussion with the other chairs,
we have decided to cancel the interim meeting in May.

We eventually came to the conclusion that with enough preparation
we could achieve the reviews in Pittsburg and thus save a long trip
for those who are not in the bay area.

I would like to thank the people who volunteered to do some of the reviews,

I will get back to them and we will present their work during the regular
meeting in Pittsburg.

    - Alain.



From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 22:34:10 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 WAA26272
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 22:34:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA14221;
	Thu, 20 Apr 2000 20:33:06 -0600 (MDT)
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 TAA10330;
	Thu, 20 Apr 2000 19:31:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3L2Tjo09146
	for ngtrans-dist; Thu, 20 Apr 2000 19:29:45 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3L2TZ709129
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:29:35 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id TAA22028
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:29:34 -0700 (PDT)
Received: from sappey.eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by sappey.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA05037;
	Thu, 20 Apr 2000 18:18:26 -0700 (PDT)
Message-ID: <38FFAC62.53C3DD56@sappey.eng.sun.com>
Date: Thu, 20 Apr 2000 18:18:26 -0700
From: Alain Durand <Alain.Durand@eng.sun.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: itojun@iijlab.net
CC: Brian E Carpenter <brian@hursley.ibm.com>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) 6to4 issue: link local
References: <18708.956279347@coconut.itojun.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@eng.sun.com>
Content-Transfer-Encoding: 7bit

itojun@iijlab.net wrote:

>
>         How about adding link-local to interface, but mark it as deprecated
>         address (i.e. lifetime expired) to make sure it won't be picked
>         as source?

Well, the point of having link local is that it may be needed by some routing
protocols, e.g. RIPng.
Can we imagine two 6to4 domains exchanging  routes via RIPng or somethig similar?
If yes, Link local are needed and should not be deprecated for the relevant protocol
to be able to use them.

However, I'm not convinced that the benefits are worth the burden of having an
extra address that will almost never be used.
Could we say that a Link Local is not needed today and if we need it later,
(say for multicast routing to work) we will define it then?

    - Alain.



From owner-ngtrans@sunroof.eng.sun.com  Thu Apr 20 22:39:27 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 WAA26294
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Apr 2000 22:39:26 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA15666;
	Thu, 20 Apr 2000 20:37:58 -0600 (MDT)
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 TAA19141;
	Thu, 20 Apr 2000 19:36:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3L2Zqb09175
	for ngtrans-dist; Thu, 20 Apr 2000 19:35:52 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3L2Zh709168
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:35:43 -0700 (PDT)
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 TAA22544
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 19:35:42 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA14958;
	Thu, 20 Apr 2000 20:35:41 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id LAA19855;
	Fri, 21 Apr 2000 11:35:30 +0900 (JST)
To: Alain Durand <Alain.Durand@sun.com>
cc: Brian E Carpenter <brian@hursley.ibm.com>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Alain.Durand's message of Thu, 20 Apr 2000 18:18:26 MST.
      <38FFAC62.53C3DD56@sappey.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) 6to4 issue: link local
From: itojun@iijlab.net
Date: Fri, 21 Apr 2000 11:35:30 +0900
Message-ID: <19853.956284530@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

>>
>>         How about adding link-local to interface, but mark it as deprecated
>>         address (i.e. lifetime expired) to make sure it won't be picked
>>         as source?
>Well, the point of having link local is that it may be needed by some routing
>protocols, e.g. RIPng.
>Can we imagine two 6to4 domains exchanging  routes via RIPng or somethig similar?
>If yes, Link local are needed and should not be deprecated for the relevant protocol
>to be able to use them.

	no, RIPng does not work.  You cannot transmit to ff02::9 over 6to4
	cloud.  Here are some analysis I have made.
	sorry if the wording sound harsh or inaccurate, I intend to update
	those.  the analysis is based on 03 draft.  however, even if we assign
	link locals (as 04 says) the analysis does not change, since you
	cannot use link-local unicast/multicast on top of 6to4 cloud.

itojun



---
/*
 * 6to4 interface, based on draft-ietf-ngtrans-6to4-03.txt.
 *
 * 6to4 interface is NOT capable of link-layer (I mean, IPv4) multicasting.
 * There is no address mapping defined from IPv6 multicast address to IPv4
 * address.  Therefore, we do not have IFF_MULTICAST on the interface.
 *
 * Due to the lack of address mapping for link-local addresses, we cannot
 * throw packets toward link-local addresses (fe80::x).  Also, we cannot throw
 * packets to link-local multicast addresses (ff02::x).
 *
 * Here are interesting symptoms due to the lack of link-local address:
 *
 * Unicast routing exchange:
 * - RIPng: Impossible.  Uses link-local multicast packet toward ff02::2,
 *   and link-local addresses as nexthop.
 * - OSPFv6: Impossible.  OSPFv6 assumes that there's link-local address
 *   assigned to the link, and makes use of them.  Also, HELLO packets use
 *   link-local multicast addresses (ff02::5 and ff02::6).
 * - BGP4+: Maybe.  You can only use global address as nexthop, and global
 *   address as TCP endpoint address.
 *
 * Multicast routing protocols:
 * - PIM: Hello packet cannot be used to discover adjacent PIM routers.
 *   Adjacent PIM routers must be configured manually (is it really spec-wise
 *   correct thing to do?).
 *
 * ICMPv6:
 * - Redirects cannot be used due to the lack of link-local address.


From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 21 02:57:28 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 CAA09537
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Apr 2000 02:57:27 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA23802;
	Fri, 21 Apr 2000 00:56:14 -0600 (MDT)
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 XAA10073;
	Thu, 20 Apr 2000 23:52:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3L6pRV09329
	for ngtrans-dist; Thu, 20 Apr 2000 23:51:27 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3L6pK709322
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 23:51:20 -0700 (PDT)
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 XAA10033
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Apr 2000 23:51:20 -0700 (PDT)
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 AAA22748
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 00:51:20 -0600 (MDT)
Received: from 209-239-204-80.oak.jps.net (Truckee) [209.239.204.80] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12iXHZ-0001ss-00; Thu, 20 Apr 2000 23:51:18 -0700
Message-Id: <4.2.2.20000420204433.019f40e0@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 20 Apr 2000 20:44:53 -0700
To: itojun@iijlab.net, Brian E Carpenter <brian@hursley.ibm.com>
From: Bob Fink <fink@es.net>
Subject: Re: (ngtrans) 6to4 issue: link local
Cc: NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: <18708.956279347@coconut.itojun.org>
References: <brian's message of Thu, 20 Apr 2000 14:35:10 EST. <38FF5BEE.E3B28886@hursley.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>

At 10:09 AM 4/21/2000 +0900, itojun@iijlab.net wrote:

> >> Regarding link local there was a debate about its need. Itojun argued that
> >> it was necessary, and it was agreed to pursue this discussion on the list.
> >Actually I though he argued that it wasn't necessary, and Steve Deering 
> argued
> >that it was.
>
>         just to clarify: Brian is correct, I argued that it wasn't necessary.

I'll change the minutes then. Thanks.


> >As far as there was an opinion in the room, it seemed to be yes,
> >we should define link local addresses for 6to4 routers; for example they 
> might be
> >used for establishing adjacency for a multicast routing protocol.
>
>         I'm still not convinced.  Without mapping to link layer address
>         (= IPv4) it will only confuse source selection on sender, and
>         will confuse peers if you use linklocal as source address.
>         Also, I thought that it is the beauty of 6to4 that we don't need
>         ND on 6to4 cloud.
>
>         How about adding link-local to interface, but mark it as deprecated
>         address (i.e. lifetime expired) to make sure it won't be picked
>         as source?
>
>itojun



From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 21 14:55:02 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 OAA23703
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Apr 2000 14:55:01 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA04357;
	Fri, 21 Apr 2000 12:53:48 -0600 (MDT)
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 LAA10693;
	Fri, 21 Apr 2000 11:51:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3LIoan09571
	for ngtrans-dist; Fri, 21 Apr 2000 11:50:36 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3LIoT709564
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 11:50:29 -0700 (PDT)
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 LAA26135
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 11:50:27 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA02105;
	Fri, 21 Apr 2000 12:50:24 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id TAA32118; Fri, 21 Apr 2000 19:50:11 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id TAA17538; Fri, 21 Apr 2000 19:50:09 +0100 (BST)
Message-ID: <3900A170.E003716A@hursley.ibm.com>
Date: Fri, 21 Apr 2000 13:44:00 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: itojun@iijlab.net
CC: Alain Durand <Alain.Durand@sun.com>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) 6to4 issue: link local
References: <19853.956284530@coconut.itojun.org>
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

Hi,

Comments below...

itojun@iijlab.net wrote:
> 
> >>
> >>         How about adding link-local to interface, but mark it as deprecated
> >>         address (i.e. lifetime expired) to make sure it won't be picked
> >>         as source?
> >Well, the point of having link local is that it may be needed by some routing
> >protocols, e.g. RIPng.
> >Can we imagine two 6to4 domains exchanging  routes via RIPng or somethig similar?
> >If yes, Link local are needed and should not be deprecated for the relevant protocol
> >to be able to use them.
> 
>         no, RIPng does not work.  You cannot transmit to ff02::9 over 6to4
>         cloud.  Here are some analysis I have made.
>         sorry if the wording sound harsh or inaccurate, I intend to update
>         those.  

There is no problem with your wording!

>         the analysis is based on 03 draft.  however, even if we assign
>         link locals (as 04 says) the analysis does not change, since you
>         cannot use link-local unicast/multicast on top of 6to4 cloud.
> 
> itojun
> 
> ---
> /*
>  * 6to4 interface, based on draft-ietf-ngtrans-6to4-03.txt.
>  *
>  * 6to4 interface is NOT capable of link-layer (I mean, IPv4) multicasting.
>  * There is no address mapping defined from IPv6 multicast address to IPv4
>  * address.  Therefore, we do not have IFF_MULTICAST on the interface.

Correct; that is the difference from 6over4.

>  *
>  * Due to the lack of address mapping for link-local addresses, we cannot
>  * throw packets toward link-local addresses (fe80::x).  

Well, with the current draft we can if we need to.

>    Also, we cannot throw
>  * packets to link-local multicast addresses (ff02::x).

Correct.

>  *
>  * Here are interesting symptoms due to the lack of link-local address:
>  *
>  * Unicast routing exchange:
>  * - RIPng: Impossible.  Uses link-local multicast packet toward ff02::2,
>  *   and link-local addresses as nexthop.
>  * - OSPFv6: Impossible.  OSPFv6 assumes that there's link-local address
>  *   assigned to the link, and makes use of them.  Also, HELLO packets use
>  *   link-local multicast addresses (ff02::5 and ff02::6).

Correct. I never imagined using RIP or OSPF, or any IGP.

>  * - BGP4+: Maybe.  You can only use global address as nexthop, and global
>  *   address as TCP endpoint address.

I don't think there is any problem using BGP4+, especially now that
a link local format is defined.

>  *
>  * Multicast routing protocols:
>  * - PIM: Hello packet cannot be used to discover adjacent PIM routers.
>  *   Adjacent PIM routers must be configured manually (is it really spec-wise
>  *   correct thing to do?).

Yes, there is a problem with PIM. Dave Thaler is working on a multicast
solution.

>  *
>  * ICMPv6:
>  * - Redirects cannot be used due to the lack of link-local address.

Well, they can be used now! Actually this suggests that we *do* need
the definition and that it is of immediate use.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 21 14:59:17 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 OAA23774
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Apr 2000 14:59:16 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA06794;
	Fri, 21 Apr 2000 12:58:19 -0600 (MDT)
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 LAA27158;
	Fri, 21 Apr 2000 11:56:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3LIu4F09589
	for ngtrans-dist; Fri, 21 Apr 2000 11:56:04 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3LItw709582
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 11:55:58 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA11273
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 11:55:57 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA05470
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 12:55:56 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id TAA41148; Fri, 21 Apr 2000 19:55:44 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id TAA25848; Fri, 21 Apr 2000 19:55:43 +0100 (BST)
Message-ID: <3900A2B9.7F8812EA@hursley.ibm.com>
Date: Fri, 21 Apr 2000 13:49:29 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@eng.sun.com>
CC: itojun@iijlab.net, NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) 6to4 issue: link local
References: <18708.956279347@coconut.itojun.org> <38FFAC62.53C3DD56@sappey.eng.sun.com>
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

Alain Durand wrote:
...
> However, I'm not convinced that the benefits are worth the burden of having an
> extra address that will almost never be used.
> Could we say that a Link Local is not needed today and if we need it later,
> (say for multicast routing to work) we will define it then?

If it is needed even once, e.g. for ICMPv6 redirect as itojun suggested,
we need to define it. 

My opinion is that we should define it anyway, so that there is no risk
of confusion the first time someone actually needs it. Please remember
that the text we are discussing consists in total of:

>    The link-local address of a 6to4 pseudo-interface performing 6to4
>    encapsulation is formed as described in Section 3.7 of [MECH].

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 21 22:56:32 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 WAA00526
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Apr 2000 22:56:31 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA07607;
	Fri, 21 Apr 2000 20:55:40 -0600 (MDT)
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 TAA15988;
	Fri, 21 Apr 2000 19:53:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3M2r1b09760
	for ngtrans-dist; Fri, 21 Apr 2000 19:53:01 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3M2qq709753
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Apr 2000 19:52:52 -0700 (PDT)
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 TAA06776;
	Fri, 21 Apr 2000 19:52:50 -0700 (PDT)
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 TAA11912;
	Fri, 21 Apr 2000 19:52:49 -0700 (PDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id LAA04738;
	Sat, 22 Apr 2000 11:52:19 +0900 (JST)
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: Alain Durand <Alain.Durand@eng.sun.com>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: brian's message of Fri, 21 Apr 2000 13:49:29 EST.
      <3900A2B9.7F8812EA@hursley.ibm.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) 6to4 issue: link local
From: itojun@iijlab.net
Date: Sat, 22 Apr 2000 11:52:19 +0900
Message-ID: <4736.956371939@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> However, I'm not convinced that the benefits are worth the burden of having an
>> extra address that will almost never be used.
>> Could we say that a Link Local is not needed today and if we need it later,
>> (say for multicast routing to work) we will define it then?
>If it is needed even once, e.g. for ICMPv6 redirect as itojun suggested,
>we need to define it. 

	sorry if my analysis was unclear.
	no, ICMPv6 redirect cannot be used even if you assign link-local
	onto 6to4 interface.  what we really need is link-local address
	AND mapping from link-local to IPv4 address.

	to use ICMPv6, the following conditions must be satisfied:
	- "gateway" field on routing table needs to be link-local on
	  originating host of the packet (due to validation rules in RFC2461
	  section 8, IIRC)
	- source address on ICMPv6 packet needs to be link-local of router

	If you configure the following routing table on the originating host:

destination	gateway		interface
default		fe80::x		6to4

	you'll need to know mapping from fe80::x to IPv4 destination address
	to send packet via router on fe80::x%6to4 (I love this notation :-)).
	This is not possible since we do not have mapping between fe80::x
	to IPv4 address, in 6to4 spec.

	if we are to use IPv4 address embedded into the last 4 bytes in
	interface identifier field... hmm, I have never thought about it...
	we will see two IPv4 address on 6to4 address (2002::/16).

	I'm not sure if we have real use of ICMPv6 redirect here.
	on 6to4 cloud, most of the nodes are routers (6to4 relays),
	not hosts.  routers do not update their routing table on inbound
	ICMPv6 packets.

	To summarize:
	- not sure if ICMPv6 has real use on 6to4 cloud
	- to use ICMPv6 on 6to4 cloud, we need link-local address AND
	  mapping from link-local to IPv4 address.  ICMPv6 does not work
	  if we don't have the mapping defined.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Sun Apr 23 09:20:42 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 JAA07634
	for <ngtrans-archive@odin.ietf.org>; Sun, 23 Apr 2000 09:20:41 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24903;
	Sun, 23 Apr 2000 07:19:37 -0600 (MDT)
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 GAA02473;
	Sun, 23 Apr 2000 06:17:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3NDEmB10191
	for ngtrans-dist; Sun, 23 Apr 2000 06:14:48 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3NDEd710184
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Apr 2000 06:14:40 -0700 (PDT)
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 GAA29046
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Apr 2000 06:14:36 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24506;
	Sun, 23 Apr 2000 07:14:34 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id WAA17929;
	Sun, 23 Apr 2000 22:14:24 +0900 (JST)
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: Alain Durand <Alain.Durand@sun.com>,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: brian's message of Fri, 21 Apr 2000 13:44:00 EST.
      <3900A170.E003716A@hursley.ibm.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) 6to4 issue: link local
From: itojun@iijlab.net
Date: Sun, 23 Apr 2000 22:14:24 +0900
Message-ID: <17927.956495664@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


	Again, to summarize:
	- if we attach link-local address to 6to4 interface, without
	  defining mapping between link-local addresses to IPv4, it's harmful.

>>  * - BGP4+: Maybe.  You can only use global address as nexthop, and global
>>  *   address as TCP endpoint address.
>I don't think there is any problem using BGP4+, especially now that
>a link local format is defined.

	no we shouldn't attach link-locals to nexthop, unless we have
	mapping from link-local address to IPv4 address on 6to4 cloud.

	Please consider the following scenario:
	- A (global 6to4 address = Ga, link-local address = La) and
	  B (global 6to4 address = Gb, link-local address = Lb) are making
	  BGP connection.
	- A advertises a prefix P/plen, to B.
	- B would install the route as:
		destination = P/plen
		gateway = La%6to4
	  since A attached link-local address to nexthop field.
	- B now cannot transmit pacets to P/plen, since B does not know how
	  to transmit packets to La%6to4.

	If we do not attach link-local address to 6to4 interface, the problem
	will not occur.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 26 19:00:09 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 TAA06427
	for <ngtrans-archive@odin.ietf.org>; Wed, 26 Apr 2000 19:00:09 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA09784;
	Wed, 26 Apr 2000 16:59:11 -0600 (MDT)
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 PAA05995;
	Wed, 26 Apr 2000 15:50:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3QMgIb12587
	for ngtrans-dist; Wed, 26 Apr 2000 15:42:18 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3QMgB712580
	for <ngtrans@sunroof.eng.sun.com>; Wed, 26 Apr 2000 15:42:11 -0700 (PDT)
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 PAA02799
	for <ngtrans@sunroof.eng.sun.com>; Wed, 26 Apr 2000 15:41:54 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA02723;
	Wed, 26 Apr 2000 15:41:52 -0700 (PDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id PAA16966;
	Wed, 26 Apr 2000 15:41:51 -0700 (PDT)
Message-ID: <390770B0.A106B7D2@erg.sri.com>
Date: Wed, 26 Apr 2000 15:41:52 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@sun.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com> <38F63C70.BE34391D@erg.sri.com> <38F659F5.34E41091@sappey.eng.sun.com> <38FF3DF5.39CB4560@erg.sri.com> <38FF3F74.2579068F@sappey.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Alain,

Again, I apologize for taking so long to get back to you. My mailer
somehow buried your reply, and I'm just seeing your message for the
first time today. Some comments on your message:

> I understand your approach and desire to look at the problem
> from a higher point of view.

OK. I will work on the scenarios and publish them in a revised
verion of the draft.

> However, I will not consider the sending rules as minor items.
> If they do  not work, there is a major flow in the proposal,
> and, for me, this would be a show stop.

Nor do I consider the sending rules minor items; I am only interested
in approaches that have practical and near-term application for ngtrans;
after all, these transition mechanisms are theoretically for the short
term only and must give way to a fully-native IPv6 infrastructure in
the future.

Please remember that this is version 0 of the draft, however, and that
the sending rules in section 3 derive from one specific scenario. The
sending rules in the draft were my attempt to describe the way my
prototype implementation works for a very specific scenario in which:

  - All hosts engaging in the scheme are single, isolated IPv6 hosts
    within otherwise all-IPv4 subnets
  - All hosts engaging in the scheme are assigned IPv6-IPv4 compatiblity
    addresses as described in my draft

In this scenario (as in any other), prefix information populated in
the IPv6 routing table can provide finer-grained matches for destination
addresses than by just having a 'default' route. But, there NEED NOT be
any routing info other than for 'default' in the IPv6 routing table for
my method to work in this scenario. Additionally, it is highly unlikely
that all IPv6 hosts in the Internet would be assigned IPv6-IPv4
compatibility
addresses as the sending rules for my specific scenario assumes. But, I
have
not yet taken a top-down look at any of the commonly-expected IPv6/IPv4
transition/compatibility deployment scenarios to investigate a set of
sending
rules that will work in the generalized case. So, I simply ask for a
fair
chance to investigate the scenarios and present a generalized set of
sending
rules. I'm confident that this can be done. But if it can't be done,
I'll be
the first to agree that it "doesn't work".

Fred
templin@erg.sri.com      
 
>     - Alain.


From owner-ngtrans@sunroof.eng.sun.com  Wed Apr 26 19:55:20 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 TAA06826
	for <ngtrans-archive@odin.ietf.org>; Wed, 26 Apr 2000 19:55:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA14314;
	Wed, 26 Apr 2000 17:54:27 -0600 (MDT)
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 QAA21293;
	Wed, 26 Apr 2000 16:54:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3QNrCb12651
	for ngtrans-dist; Wed, 26 Apr 2000 16:53:12 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3QNr5712644
	for <ngtrans@sunroof.eng.sun.com>; Wed, 26 Apr 2000 16:53:05 -0700 (PDT)
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 QAA25260
	for <ngtrans@sunroof.eng.sun.com>; Wed, 26 Apr 2000 16:53:06 -0700 (PDT)
Received: from sfo.erg.sri.com (sfo.erg.sri.com [128.18.100.4])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA13511;
	Wed, 26 Apr 2000 17:53:05 -0600 (MDT)
Received: from erg.sri.com (walleye.erg.sri.com [128.18.4.214])
	by sfo.erg.sri.com (8.9.1/8.9.0) with ESMTP id QAA17510;
	Wed, 26 Apr 2000 16:53:03 -0700 (PDT)
Message-ID: <3907815F.74F17A3C@erg.sri.com>
Date: Wed, 26 Apr 2000 16:53:03 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
Organization: SRI International
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alain Durand <Alain.Durand@sun.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: I-D ACTION:draft-templin-ngtrans-v6v4compat-00.txt
References: <236F133B43F4D211A4B00090273C79DC02C2F6A1@us-rv-exch-2.rsvl.unisys.com> <38F63C70.BE34391D@erg.sri.com> <38F659F5.34E41091@sappey.eng.sun.com> <38FF3DF5.39CB4560@erg.sri.com> <38FF3F74.2579068F@sappey.eng.sun.com> <390770B0.A106B7D2@erg.sri.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Fred L. Templin" <templin@erg.sri.com>
Content-Transfer-Encoding: 7bit

Alain,

> In this scenario (as in any other), prefix information populated in
> the IPv6 routing table can provide finer-grained matches for destination
> addresses than by just having a 'default' route. But, there NEED NOT be
> any routing info other than for 'default' in the IPv6 routing table for
> my method to work in this scenario.

Acutally, in the specific and constrained scenario presented in my
draft,
hosts need not even have a 'default' route in their IPv6 routing tables;
at a minimum, they need only have a 'default' route in their IPv4
tables.
But again, the sending rules in my draft are specific to that one
constrained
scenario; my plan is to produce a generalized set of sending rules based
on my analyses of the various anticipated ngtrans deployment schemes.

Fred
templin@erg.sri.com


From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 28 06:58:17 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 GAA27000
	for <ngtrans-archive@odin.ietf.org>; Fri, 28 Apr 2000 06:58:16 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA22552;
	Fri, 28 Apr 2000 04:55:26 -0600 (MDT)
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 DAA10922;
	Fri, 28 Apr 2000 03:54:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3SAohP13843
	for ngtrans-dist; Fri, 28 Apr 2000 03:50:43 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3SAoX713836
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 03:50:33 -0700 (PDT)
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 DAA19318
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 03:50:28 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA08537
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 03:50:27 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26933;
	Fri, 28 Apr 2000 06:50:26 -0400 (EDT)
Message-Id: <200004281050.GAA26933@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-ipv4survey-00.txt
Date: Fri, 28 Apr 2000 06:50:25 -0400
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		: Survey of IPv4 Addresses in Currently Deployed IETF 
                          Standards
	Author(s)	: P. Nesser II
	Filename	: draft-ietf-ngtrans-ipv4survey-00.txt
	Pages		: 8
	Date		: 27-Apr-00
	
This document seeks to document all usage of IPv4 addresses in currently
deployed IETF documented standards.  In order to successfully transition
from an all IPv4 Internet to an all IPv6 Internet, many interim steps will be taken. One of these steps is the evolution of current protocols that have IPv4 dependencies.  It is hoped that these protocols (and their implementations) will be redesigned to be network address independent, but failing that will at leasy dually support IPv4 and IPv6.  To this end, all Standards (Full, Draft, Proposed and Experimental) will be survey and any dependencies will be documented.

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

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-ipv4survey-00.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-ipv4survey-00.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:	<20000427121149.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-ipv4survey-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Apr 28 12:34:48 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 MAA05399
	for <ngtrans-archive@odin.ietf.org>; Fri, 28 Apr 2000 12:34:47 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA16965;
	Fri, 28 Apr 2000 10:33:19 -0600 (MDT)
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 JAA07493;
	Fri, 28 Apr 2000 09:32:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3SGUMk13937
	for ngtrans-dist; Fri, 28 Apr 2000 09:30:22 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3SGU9713930
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 09:30:11 -0700 (PDT)
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 JAA04373
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 09:30:06 -0700 (PDT)
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 JAA23070
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Apr 2000 09:30:03 -0700 (PDT)
Received: from rasp2-70.lbl.gov (Truckee) [131.243.212.170] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12lDeO-0004ww-00; Fri, 28 Apr 2000 09:29:57 -0700
Message-Id: <4.2.2.20000428092816.0e941130@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 28 Apr 2000 09:29:51 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) final minutes from ngtrans Adelaide
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>
Content-Transfer-Encoding: 8bit

Final minutes as submitted to secretariat.

Only change was correcting Itojun link-local comment on 6to4.


Bob

===
Minutes of NGtrans WG Meeting
27/29 March 2000
Adelaide IETF-47
___

Chairs:

Alain Durand <Alain.Durand@eng.sun.com>
Bob Fink <fink@es.net>
Tony Hain <tonyhain@microsoft.com>

This ngtrans meeting reported by Bob Fink and Tony Hain.
Attendance was ~150.

Alain Durand & Bob Fink chaired the meeting.

___

Administrative information:

Discussion ngtrans: <mailto: ngtrans@sunroof.eng.sun.com>
Subscribe ngtrans: <mailto: majordomo@sunroof.eng.sun.com> "subscribe ngtrans"
Archive ngtrans: <http://www.wcug.wwu.edu/lists/ngtrans/>
Web site: <http://www.6bone.net/ngtrans>

Discussion 6bone: <mailto: 6bone@isi.edu>
Subscribe 6bone: <mailto: majordomo@isi.edu> "subscribe 6bone"
Archive 6bone: <http://www.wcug.wwu.edu/lists/6bone/>
Web site: <http://www.6bone.net>

___

Agenda

Project status report - Bob Fink

BT Patent IPR status - Bob Fink

MECH-04 update status - Erik Nordmark

6to4-04 new draft - Brian Carpenter

DSTM-01 new draft - Laurent Toutain

SOCKS-03 new draft - Hirsohi Kitamura

TRANSLATOR-03 new draft - Kazu Yamamoto

BROKER-02 - Ivano Guardini

Tunnel Discovery - ALain Durand

TCPUDP-RELAY-00 new draft - Jun-ichiro itojun Hagino

TRANSITION-03 new draft - Alain Durand

6PAPA-01 new draft - Bob Fink

pTLA-00 new draft - Bob Fink

ABUSE-00 new draft  - Jun-ichiro itojun Hagino

Interim NGtrans meeting planning - Alain Durand & Bob Fink

PingERv6 Report - Les Cottrell

Relocated 6bone registry - David Kessens

6tap report - Florent Parent

pTLA reliability report - Ivano Guardini

Root name server issues - Akira Kato

---

Project status report - Bob Fink

Bob presented the status of all ngtrans projects from the ngtrans web
site's project status pages:

<http://www.6bone.net/ngtrans/ngtrans_project-status.html>

Let Bob know of any errors.

---

BT Patent IPR status - Bob Fink

Bob Fink related the background and current status of the BT patent issue.

  1. BT notified the IETF Secretariat on Nov 5, 1999 that:

     "In accordance with the IETF Rules, BT would like to disclose that we
      have recently applied for patents in the IPv6 space relating to:
       * the establishment of tunnels using DNS as the tunnel
         endpoint discovery mechanism and

       * a mechanism that enables translation and tunneling
         to be combined into a single device.

     BT does so in the belief that these recent patent application are
     relevant to present discussions within the IETF."

2. After the IETF Secretariat queried BT, a reply was received on
    Nov 12, 1999, saying:

    "Also in accordance with IETF Rules, BT hereby gives the assurance that,
     following approval by the IESG of the relevant Internet standards
     specification, BT will grant licences under these patent applications
     and under any resultant patents, on openly specified, reasonable and
     non-discriminatory terms, to implement the Internet standards specifi-
     cation, provided the licensee similarly grants licences under its
     necessary applications/patents."
3.  BT is under no responsibility to say more about their possible patents
     than they already have.
4.  From the information on hand, or likely to become available, there is
     no clear way of telling if any work now underway in ngtrans is possibly
     affected by BT patents.
5.  If any ngtrans work eventually is covered by BT patents, BT's assurance
     to grant licenses is minimally acceptable according to Steve Coya, IETF
     Secretariat:
     "Note that during the Stockholm meeting, the concept of determining
      whether the licensing was openly specified, reasonable and non-discri-
      minatory terms would be based on implementor feedback (i.e. if enough
      folks entered into an agreement, that would be sufficient to "prove" or
      demonstrate that the licensing arrangements were palatable. This
      will be treated like an option when/if the protocol is submitted for
      consideration as a Draft Standard."
6.   Thus there is no reason to do other than proceed with all work now
      underway in ngtrans.

Not hearing anything to the contrary, Bob declared the BT issue closed
for now.

---

ABUSE-00 new draft  - Jun-ichiro itojun Hagino

Itojun gave a report of potential abuses to IPv6 transition mechanisms
that is available at:

<http://6bone.net/ngtrans/IETF47-Adelaide/draft-itojun-ipv6-transition-abuse 
   -00a.txt>

The document talks about possible abuse of IPv6 transition technologies,
which may lead to denial-of-service (DoS) attacks and other problems.
IPv6 transition technologies, namely IPv6 over IPv4 tunnelling speci-
fications and some others, have room for abuse by malicious parties.
Detailed descriptions and possible workarounds are supplied.

The specific areas of problems noted were:

  Abuse of IPv4 compatible address
  Abuse of 6to4 address
  Abuse of IPv4 mapped address

For which he gave possible solutions (see the paper).

His recommendations to future proposals were:

  If you use tunnels, require explicit configuration
    Manual configuration
    Authenticated automatic configuration

  Don't put IPv4 address into IPv6 address, for purpose of relays

  Do not define IPv6 addresses that are not used on the wire
    Makes it much harder to check

and his summary:

  Bad guys can abuse some of transition techniques

  Don't run 6to4/auto tunnel relay, if you don't need one
    Be careful about v4 mapped address

  What to do next?
    Incorporate checks presented here, into original proposals
    Publish it as separate document (informational?)

  Let us check other proposals as well

  Let us deploy native IPv6 network sooner, so that we no longer need tunnels

---

MECH-04 update status - Erik Nordmark

Erik noted changes he has made to MECH-04 in preparation for MECH-05.

-  Specified when to put IPv6 addresses in the DNS.

-  Added reference to the tunnel mib for TTL specification for the tunnels.

-  Added recommendations for use of source and target link layer address
    options for the tunnel links.

-  Added checks in the decapsulation checking both an IPv4-compatible
    IPv6 source address and the outer IPv4 source addresses for multicast,
    broadcast, all-zeros etc.

Erik will issue MECH-05 as soon as he can (already done on April 6 and a wg
last call issued).

---
6to4-04 new draft - Brian Carpenter

Brian presented the changes from -03 to -04 and highlighted issues remaining.

CHANGES
•	added terminology section
•	another revision of address selection text
•	described link local address formation
•	changed sending rule to refer to next hop
•	removed confusing text on IPv4 header padding
•	clarification/corrections to exterior routing discussion
       (scenarios with & without BGP)
•	clarified MTU text again
•	added section on routing loops
•	added and removed text on multicast
•	added text on RSIP
•	reformulated section on Intranet usage
        (use of Net 10 addresses now forbidden)
•	clarifications/response to detail comments

ISSUES
•	text on PIM-SM needs checking by a PIM-SM expert
•	Is link-local address really needed?
•	host-only draft: volunteer needed
•	Is this ready for PS?

Brian thanked Jim Bound's group for their comments.

Regarding link local there was a debate about its need. Itojun argued that
it wasn't necessary, and it was agreed to pursue this discussion on the list.

There was discussion of the need to rewrite the multicast section.

Steve Deering was asked to comment on PIM-SM usage in 6to4. He felt that
the problem generalized to the NBMA network case, noting that MARS was
the state-of-the-art in this regard.

There was concern about the applicability of IPv4 tools in the IPv6 space

There was a call for review of the multicast section by experts.

Brian noted that the security section already talks about ingress filtering
in regards to Itojun's abuse concerns (covered earlier in these minutes).

Brian stated that he would like to try to move 6to4 to PS before Pittsburgh.

---

DSTM-01 new draft - Laurent Toutain

Laurent made a few comments on the new DSTM-01 draft and DSTM status in 
general:

• cleaned up text

• 6->4 is mandatory

• 4->6 is optional

• 4->4 is optional

• implementation in bsd (inria)

• dhcpv6 concurrent work : only 4 messages needed

• modify dns when v4 query fails

• question about timeouts : timer in dstm based on pool

• will use implementations to adjust timers : new text next time

---

SOCKS-03 new draft - Hirsohi Kitamura

Hiroshi gave a status report on the new -03 draft:

• IESG comments were incorporated into -03

• there are two available independent implementations
   NEC:  <http://www.socks.nec.com>
   KAME: <ftp://kame.net/pub/kame/misc/socks64-...>

• there are about 5000 downloads/year of the SOCKS code
   from 80 different countries

• a -04 will be out soon to answer other comments

---

TRANSLATOR-03 new draft - Kazu Yamamoto

Kazu gave a status report on the new -03 draft called
Overview of Transition Techniques for IPv6-only to Talk to IPv4-only
Communication, which was previously called Categorizing Translators
between IPv4 and IPv6

Background

• The previous version "02" was published in Oct 1999

• Comments from IESG in Dec 1999

   Wording
     Bilingual -> dual-stack
     Proxy -> application level gateway
     Definition of "translator" is unclear
   Weakness
     Some explanations in this memo are not applicable to SIIT (FTP, IPsec, 
...)
     SOCKS5 is not TCP-relay

   Situation is changing
     This draft was based on a paper of INET 1998 (written in 1997)
     It is getting harder to modify IPv6 hosts

• Version "03" was published in Mar 2000

Differences between -02 and -03

• Title
   OLD: Categorizing Translators between IPv4 and IPv6
   NEW: Overview of Transition Techniques for IPv6-only to Talk to IPv4-only
    Communication

• Wording
   Defined "translator" in this memo an intermediate component between an IPv4
   host and an IPv6 host to enable direct communication between them, without
   requiring any modifications to them

• Accepted IESG's comments

• Assumption
   OLD: We can change IPv6 hosts as we like
   NEW: It is difficult to change IPv6 hosts
   Outside the scope
     SOCKS5
     SIIT
     BIS
   Mechanisms requiring specific functionality for IPv6 hosts

• Address mapping:
   OLD: Suggested to use both DNS hack and resolver hack
   NEW: Suggest to use DNS hack only
        Resolver hack means changing IPv6 hosts

Next step

• Authors hope:
   to publish it as Informational RFC
   then to help the ROADMAP document project

Kazu asked the chairs to please return -03 to the IESG to continue
processing there towards Informational RFC.

---

BROKER-02 - Ivano Guardini

Ivano gave a status report of the older -02 draft:

• WG last call after Washington IETF
• One comment about MIME type
• -02 draft not updated yet

• Plan A:
    Include MIME media-type definition in the document?
    Other WG may benefit from the MIME-type

• Plan B:
    Publish framework as Informational
    Publish MIME-type as separate,informational RFC

• Actions for Plan B
    Remove implementation section (appendix)
    Add short discussion as MIME-type as implementation option
    Open door for the use of Tunnel Broker concept in other areas
    Publish framework as Informational RFC
    Publish MIME-type description in a separate document

• Proposed MIME type
    application/tunnel
    parameters: ipv6/ipv4
      src,dst v4 & v6 address
      Tunnel management procedure
        TTL with sub-parameter TTL value
        something smarter?
      Textual description
      ...

• a -03 draft will be published soon

---

Tunnel Discovery - ALain Durand

Alain presented his ideas on Tunnel Endpoint Discovery, exploring
new directions:
<http://6bone.net/ngtrans/IETF47-Adelaide/tep1.ppt>

Granularity of tunnel end point discovery mechanism
	
• Automatic tunnels: 1 host (/128)
• 6over4: 1 host (/128)
• Tunnel broker: typically 1 host (/128)
• 6to4: 1 site (/48)
• Might be a need for other granularity:
   /64, /56, /49 intra-site
   /35, /29, /24 wan

Potential candidate: DNS...

• DNS is a natural distributed model
   network administrators know DNS
   DNS can handle different levels of granularity
• But:
   DO NOT CREATE ANY NEW RR TYPE
   DO NOT CALL DNS FOR EVERY SINGLE PACKET

Tunnel End Point Discovery Process Steps

1. Source S sends a packet to D1, packet goes to exit router R,
    but R has no route for D1...
2. Router R uses DNS to discover Tunnel End Point  (TEP) IPv4 address.
    It also discovers that TEP is responsible for P/24. There is a TTL
    associated to the DNS response.
3. Router R create a uni-directional tunnel to TEP
    and add a route for P/24 through that tunnel.
    Packets are routed to D1 using P/24 IPv6 infrastructure
4. Source S2 now sends a packet to D2. As D2 is part of P/24,
    router R already has a route for it. It does not need to do another DNS 
query.
    It routes the packet through the existing tunnel.
5. After TTL expires, router R delete the tunnel and the route for P/24

DNS mechanism

• Dedicated reverse tree tunnel6.ip6.int
• DNAME for delegation
• Wildcard entries for PTR
• Reserved label "tunnel6" tag prefix len

Configuration example

• Tunnel end point for 3ffe:0300::/24 is 129.88.26.7

   \[x3ffe/16].tunnel6.ip6.int IN DNAME 16.tunnel6.6bone.net.

   \[x03/8].16.tunnel6.6bone.net. IN DNAME 24.tunnel6.imag.fr.

   *.24.tunnel6.imag.fr. IN PTR basta.imag.fr.

   basta.imag.fr IN A 129.88.26.7

Query example

• Query:

   PTR for 1.0.0....0.0.3.0.e.f.f.3.tunnel6.ip6.int.

• Response:

   1.0.0....0.0.3.0.e.f.f.3.24.tunnel6.imag.fr. IN PTR basta.imag.fr.
   basta.imag.fr. IN A 129.88.26.7

At the end of Alain's presentation there were various comments:

• that iesg needs to decide about ipv6.int

• that using dns to do routing is a bad idea

• that using dns for real-time services will fail

• that using dns will be more painful than the account can absorb

• that this needs service location & routing to make it work

• question about what is better about this than 6to4

No conclusion was reached about the pursuit of this effort, stay tuned.

---

TCPUDP-RELAY-00 new draft - Jun-ichiro itojun Hagino

Itojun gave a presentation of his new draft called An IPv6-to-IPv4
transport relay translator:

• Transparent TCP relay
   Has been used in firewall-oriented products like TIS gauntret
• We can use it for IPv6-to-IPv4 translation
• No extra configuration/code on end node
• No tricky MTU issues
• Stateful TCP relay box
   A TCP connection goes through single TCP relay box
   Can place multiple boxes against multiple clients
• We have been using it for more than 3 years, working just great
   ... we thought we'd better document it
• The talk will focus on:
   IPv6-to-IPv4 translation (IPv4-to-IPv6 is possible)
   TCP relay (UDP is also possible)

Transparent TCP relays (IPv4-to-IPv4)

• A originates TCP to X (A -> X)
• TCP relay box hijacks the connection and terminate it at B (A -> B)
• TCP relay box originates TCP to X (Y -> X)
• TCP relay box relays content across two TCP connections
• originating node (A) --> TCP relay box (as X, interface is B)
    address on IP header: A -> X
• TCP relay box (Y) --> destination node (X)
    address on IP header: Y -> X

Transparent TCP relays (IPv6-to-IPv4)

• Reserve an IPv6 /64 prefix R6::/64, announce routes
• A6 originates TCP to C6::X4 (A6 -> R6::X4)
• TCP relay box hijacks the connection and terminate it at B6 (A6 -> B6)
• TCP relay box originates TCP to X4 (Y4 -> X4)
• TCP relay box relays content across two TCP connections
• IPv6 TCP: originating node (A6) --> TCP relay box (as R6::X4, interface 
is B6)
    address on IPv6 header: A6 -> R6::X4
• IPv4 TCP: TCP relay box (Y4) --> destination node (X4)
    address on IPv4 header: Y4 -> X4

Address mapping

• Similar to other translation techniques
• Modified DNS server
   For installation to large site
• Special entries in /etc/hosts
   For small installation
• Modified resolver on the originating node
   Not recommended, modifying originating node makes it hard to deploy

Multiple servers, for scalability/availability

• Setup multiple TCP relay boxes
• Assign different reserved prefix, advertise all of them
• Present different fake address by DNS round-robin or alike
   Once TCP is established we don't change address pair
• When B6/Y4 goes down, connections through D6/Z4 will be okay

Notes

• No need to care about path MTU/fragmentation issues
   Per-packet translation needs a great care
• Need to care about urgent data
• Can relay UDP
   Recognize UDP "connection" like NAT does
• Can relay IPv4-to-IPv6
   Address mapping issue
• To relay FTP need to rewrite payload data
• Access control is mandatory
   Malicious party can take advantage of it to anonymize connection
• KAME has been using this for 3 years, works quite well
   Served 100+ nodes at ipngwg Tokyo interim meeting
   We have been using it in many occasions
• Two "tricky" name server implementations exist
   totd/newbie
   {Free,Net,Open}BSD includes this FreeBSD 4.0: IPv6 enabled by default!

Wrap-up

• IPv6-to-IPv4 translation using TCP relays
• Simple implementation, works very well
• No change in end node - can serve any of existing IPv6 nodes
• Would like to issue it as an informational RFC, to help future implementers
   Not a new protocol, fits best to informational
• ngtrans project, or individual submission?

• To try it out from terminal room: to your IPv4 133.138.1.134,
     telnet 3ffe:501:4819:ffff::133.138.1.134
     ssh -v 3ffe:501:4819:ffff::133.138.1.134

   Travels Adelaide -- Tokyo -- your place, may add delay

Noted that it should refer to existing list of applications affected by nat

It was agreed that ngtrans would take on this as a project. Tthere was
some minor debate about whether it should be Informational or Standards
track, which resulted in the chairs determining (for now) that Informational
RFC was most consistent with other ongoing and past projects.

---

TRANSITION-03 new draft - Alain Durand

Alain gave a status report on the "roadmap" transition document effort:

Update

• New scenarii
   large new IPv6 network
   ISP
• Update of all references
• Clarification text on
   Tunnel Broker, Bis, BiAPI, 6to4, DSTM, OSPF, 6PAPA
• Remove all mention to particular implementation

New Structure

1. Introduction
2. General deployment issues
3. Basic transition mechanisms (RFC1933 & update)
4. The tools
4.1 connecting IPv6 islands
4.2 communication between IPv4 & IPv6
5 & 6. scenarii

Work continues!

---

6PAPA-01 new draft - Bob Fink

Bob noted that he had not issued a new draft for balloting, nor the 6bone
steering committee, as the RIRs were now reviewing their IPv6 address
allocation policies which could affect 6PAPA. Thus he will wait until
it is clear that the 6bone prequalification for sub-TLA allocation will
stay in place.

---

pTLA-00 new draft - Bob Fink

Bob reported that he had written the pTLA draft for the purpose of
documenting existing pTLA/pNLA 6bone prefix formats, and would soon
do a wg last call for Informational.

---

Interim NGtrans meeting plannng - Alain Durand & Bob Fink

Alain & Bob expressed the need to have an interim ngtrans meeting to:

• review state of the tools for
   security issues & corner cases
• recent proposals
• explore new directions
• industry evaluation

It was proposed to hold it in the San Francisco area, probably hosted
by Sun. Some possible dates were balloted for interest:

~4 for May 23-25

~6 for May 30-31, June 1 (just after US memorial day)

~8 for June 6-8 (conflict in Japan)

Sentiments seemed low on the need for an interim. The chairs
agreed to continue looking into the viability of a meeting as well as
when it might be, if one was held. Stay tuned.

---

PingERv6 Report - Les Cottrell

Bob Fink introduced Les Cottrell (of the US SLAC accelerator laboratory)
noting that his group's efforts to use inexpensive and easily deployable
methods to measure the quality of Internet paths had been highly successful
for IPv4, and that Les' group at SLAC had extended them to IPv6.

Les presented their work:

<http://6bone.net/ngtrans/IETF47-Adelaide/pinger61.ppt>

PingER (for IPv4)
• Simple active end-to-end ping monitoring
• Main community is HENP & ESnet sites
• 30 monitoring sites in 15 countries
• 593 nodes at 424 sites in 72 countries
• ~ 2200 pairs

PingER6 (for IPv6)

• A small amount of bandwidth is carved off ESnet connection to provide
   native IPv6 service to SLAC
• Recompiled Linux 2.2.5-15 (Red Hat 6.0) kernel with IPv6 support
• Downloaded & installed inet-apps (including ping) from inner.net and
   patch for glibc-2.1 systems
• Wrote Perl module to provide IPv6 DNS lookup
• Currently one monitoring site at SLAC

• PingER6 has been an international effort
• 6Bone and 6REN sites participating in 10 countries, 40 sites
• Currently little knowledge of networks and connections.
• Not surprisingly, same issues as the ipv4 Internet.
   Not enough bandwidth
• but it is only experimental
• How to persuade users to try it out ?
   Bob Fink big help in signing people up
   Contact warrenm@slac.stanford.edu to join PingER6
• Next steps
   Address concerns over security
   More Monitoring Sites
• 6-Tap a good place for a PingER
• China ?

Les thanked all the sites who have participated.

More Information requested from all possible participants

•IEPM/PingER home site
<http://www-iepm.slac.stanford.edu/>

• Very interesting Polish 6BONE ping site
<http://6bone-gw.6bone.pl/mrtg/>


Les was asked to discuss relationship to similar tools, and Les responded
that PingER results were well aligned to special hardware solution, like
Internet Surveyor, for a cheap solution.

Les noted that icmp is treated differently, but that practice shows there
is little affect in most places due to rate limiting. When this is observed
to be a problem new target sites are chosen.

He closed noting that the PingER6 efforts will continue and encourage all
interested to participate.

---

Relocated 6bone registry - David Kessens

---

6tap report - Florent Parent

Florent reproted on the current status of the 6tap, which is jointly
managed by Canarie/Viagenie and ESnet at the Chicago StarTAP.

• a tunnel server will be installed next week as an extension of native
IPv6 service to provide site-level tunnel support (as opposed to the
tunnel brokers individual host tunnel support).

• in addition, a route server & registry service will be developed
     solaris 8 server w/ATM to ESnet
     MRTd (Merit)
     IPv6 registry (Kessens)

• next: 6to4 relay service & stats

<http://www.6tap.net>

---

pTLA reliability report - Ivano Guardini

Ivano gave a report on the reliability of routing in the 6bone:

<http://6bone.net/ngtrans/IETF47-Adelaide/reliability-6bone.ppt>

• bgp4+ monitoring effort

• ~50% more prefixes announced than the pTLA list would suggest

• unaggregated prefixes are the bulk: multi-homed leaking

• filtering out nosiest sites: 80% of sites are almost always reachable

• most stable plotted against most unstable: instability growing

• upper bound of route instability for 80% of sites is less than 5%

• stability is good for 80%: multihoming is a problem

Results

• The results of the CSELT's 6bone monitoring effort confirm that BGP4+
routing within the 6bone backbone has become highly reliable both with
respect to stability and route availability

• this in turn highlights the good level of maturity reached by the
currently available IPv6 technology some other issues still need to be solved

• multihoming is still a problem

• A subset of these results is regularly updated at:
  <http://carmen.cselt.it/ipv6/bgp/graphs/index.html>

===

Root name server issues - Akira Kato

Akiro gave a brief report on upcoming experimentation
plans for the new BIND release in the root name servers

• experimental operation is planned with a few servers
   which will be operational soon

• separate box for v6

• 3ffe:000[1-d]::/32 for each server or
     use /24 or/28 to each server
     advertise /32 : may violate 6bone routing
     need to modify bgp pathlen filters

Various comments and questions were made:

• why special addresses?

• are these unicast or anycast?

• routing propagation is the issue: special addr not necessary

• no room to add aaaa/a6 in 512 byte

• is edns0 mandatory for ipv6 queries

• ip6.int may be server as well

• one or two servers operational soon

• 512 mtu is bogus in v6

• deployment requires careful thought

• don't worry about edns0 because it covers IPv4 requirements

• separate roots proposed

---

Meeting adjourned.

-end



From owner-ngtrans@sunroof.eng.sun.com  Sun Apr 30 07:32:23 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 HAA01942
	for <ngtrans-archive@odin.ietf.org>; Sun, 30 Apr 2000 07:32:22 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA08814;
	Sun, 30 Apr 2000 05:31:23 -0600 (MDT)
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 EAA10387;
	Sun, 30 Apr 2000 04:29:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) id e3UBRvU14622
	for ngtrans-dist; Sun, 30 Apr 2000 04:27:57 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1+Sun/8.10.1.Beta0) with ESMTP id e3UBRY714615
	for <ngtrans@sunroof.eng.sun.com>; Sun, 30 Apr 2000 04:27:34 -0700 (PDT)
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 EAA21323
	for <ngtrans@sunroof.eng.sun.com>; Sun, 30 Apr 2000 04:27:33 -0700 (PDT)
Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA02642
	for <ngtrans@sunroof.eng.sun.com>; Sun, 30 Apr 2000 04:27:31 -0700 (PDT)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id OAA22196;
	Sun, 30 Apr 2000 14:27:03 +0300 (IDT)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id NAA15310;
	Sun, 30 Apr 2000 13:27:19 +0300
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <JHFAWASP>; Sun, 30 Apr 2000 14:21:06 +0300
Message-ID: <CE835E918749D21191B10060084C377E01E15B6B@ismail1.icomverse.com>
From: "Klein, Eric" <Eric_Klein@starhome.com>
To: Brian E Carpenter <brian@hursley.ibm.com>,
        Sowmini Varadhan
	 <varadhan@zk3.dec.com>
Cc: ngtrans@sunroof.eng.sun.com, moore@cs.utk.edu
Subject: RE: (ngtrans) draft-ietf-ngtrans-6to4-04.txt
Date: Sun, 30 Apr 2000 14:21:05 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Klein, Eric" <Eric_Klein@starhome.com>

Brian, 

This draft it states:
	5.8 Usage within Intranets

	   There is nothing to stop the above scenario being deployed within
a
	   private corporate network as part of its internal transition to
IPv6;
	   the corporate IPv4 backbone would serve as the virtual link layer
for
	   individual corporate sites using 2002:: prefixes.  The V4ADDR
MUST be
	   a duly allocated global IPv4 address, which MUST be unique within
the
	   private network. The Intranet thereby obtains globally unique
IPv6
	   addresses even if it is internally using private IPv4 addresses
[RFC
	   1918].

This may seem like a silly question, but is there an allocation of addresses
to be used strictly for private networks similar to what is specified in 
RFC 1918        Address Allocation for Private Internets   February 1996


3. Private Address Space

	   The Internet Assigned Numbers Authority (IANA) has reserved the
	   following three blocks of the IP address space for private
internets:

	     10.0.0.0        -   10.255.255.255  (10/8 prefix)
	     172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
	     192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

	   We will refer to the first block as "24-bit block", the second as
	   "20-bit block", and to the third as "16-bit" block. Note that (in
	   pre-CIDR notation) the first block is nothing but a single class
A
	   network number, while the second block is a set of 16 contiguous
	   class B network numbers, and third block is a set of 256
contiguous
	   class C network numbers.

This is a very valid need for private networks that are currently using
these private networks, and wish them to remain private. There needs to be
some method for both converting these on an IPv4 network that is
transitioning to IPv6 network and in the final IPv6 network.


