From owner-ngtrans@sunroof.eng.sun.com  Mon Oct  2 14:29:41 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12139
	for <ngtrans-archive@odin.ietf.org>; Mon, 2 Oct 2000 14:29:41 -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 MAA25264;
	Mon, 2 Oct 2000 12:29:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA05417;
	Mon, 2 Oct 2000 11:27:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e92IPp622805
	for ngtrans-dist; Mon, 2 Oct 2000 11:25:51 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e92IPj322798
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 11:25:45 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA05517
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 11:25:44 -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 LAA06302
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 11:25:43 -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 LAA23840;
	Mon, 2 Oct 2000 11:25:42 -0700 (PDT)
Message-ID: <39D8D328.364EB09C@erg.sri.com>
Date: Mon, 02 Oct 2000 11:25:44 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
X-Mailer: Mozilla 4.73 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) IPv6-IPv4 compatibility address - new draft version available
References: <20000929.162911.18619584.kazu@Mew.org>
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

Hello,

A new version of the draft entitled:

  "An IPv6-IPv4 Compatibility Aggregatable Global Unicast Address
   Format for Incremental Deployment of IPv6 Nodes Within Predominantly
   IPv4-based Intranets"

is available in the Internet Drafts repository at:

  http://www.ietf.org/internet-drafts/draft-templin-ngtrans-v6v4compat-01.txt

Major changes since version '00' include:

  1) Limits the scope for automatic IPv6-in-IPv4 tunneling to INTRA-SITE
     application only, as indicated by the title change

  2) Deployment considerations giving concrete examples of when this
     mechanism is useful

  3) Unambiguous sending rule for when to route via IPv6 vs. when to
     tunnel via IPv4

  4) Unambiguous address selection rule which imposes no major changes
     for current works in progress

  5) "Automatic deprecation" whereby the mechanism "turns itself off"
     when no longer needed

The draft abstract is attached below. Please send comments to the ngtrans
distribution and/or myself.

Regards,

Fred Templin
templin@erg.sri.com

Abstract:

   This document specifies an IPv6-IPv4 compatibility aggregatable
   global unicast address format and its application for incremental
   IPv6 deployment for hosts and routers within predominantly IPv4-based
   Intranets. This document assumes that, during the IPv4 to IPv6 co-
   existence and transition phase, many sites will deploy IPv6
   incrementally (not all at once) on hosts and routers within their
   pre-existing IPv4 interior routing domains; especially those sites
   which have large and complex pre-existing IPv4 infrastructures. In
   such cases, the address format and methods described in this document
   will enable IPv6 deployment for hosts and routers which do not share
   a common multiple access datalink with their default IPv6 gateways.

   While other works in progress in the NGTRANS working group propose
   mechanisms for assigning globally-unique IPv6 address prefixes to
   sites and methods for inter-domain routing between such sites, the
   approach outlined in this memo enables large-scale incremental
   deployment of IPv6 hosts and routers within an individual site's
   pre-existing IPv4 infrastructure without incurring aggregation
   scaling issues at the border gateways nor requiring site-wide
   deployment of special IPv4 services such as multicast. The approach
   proposed by this document supports IPv6 routing within both the
   site-local and global IPv6 routing domains as well as automatic IPv6
   in IPv4 tunneling across portions of a site's IPv4 network which have
   no native IPv6 support. Moreover, this approach supports automatic
   tunneling within sites which use non globally-unique IPv4 address
   assignments, such as when Network Address Translation [NAT] is used.


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct  2 21:58:48 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA17899
	for <ngtrans-archive@odin.ietf.org>; Mon, 2 Oct 2000 21:58: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 TAA11956;
	Mon, 2 Oct 2000 19:58:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA13619;
	Mon, 2 Oct 2000 18:58:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e931vKD23044
	for ngtrans-dist; Mon, 2 Oct 2000 18:57:20 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e931v7323037
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 18:57:13 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA24104
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 18:56:57 -0700 (PDT)
Received: from ztxmail02.ztx.compaq.com (ztxmail02.ztx.compaq.com [161.114.1.206])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA25091
	for <ngtrans@sunroof.eng.sun.com>; Mon, 2 Oct 2000 18:56:52 -0700 (PDT)
Received: by ztxmail02.ztx.compaq.com (Postfix, from userid 12345)
	id 8A2022E79; Mon,  2 Oct 2000 20:56:52 -0500 (CDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by ztxmail02.ztx.compaq.com (Postfix) with ESMTP
	id 3670C1333; Mon,  2 Oct 2000 20:56:52 -0500 (CDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id VAA0000868384; Mon, 2 Oct 2000 21:56:00 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200010030156.VAA0000868384@anw.zk3.dec.com>
To: "Fred L. Templin" <templin@erg.sri.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) IPv6-IPv4 compatibility address - new draft version available 
In-reply-to: Your message of "Mon, 02 Oct 2000 11:25:44 PDT."
             <39D8D328.364EB09C@erg.sri.com> 
Date: Mon, 02 Oct 2000 21:55:59 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Hi Fred,

This draft looks better to me than before and also I am seeing the
advantage it brings to the IPv6 LAN for deployment.  I think we need to
pursue this very seriously in NGTRANS.  I need to reread it again with
my implementor hat on (last read was with my architecture hat on).  But
I think this is inherently useful as I thought 6to4 was as input to you.

regards,
/jim


From owner-ngtrans@sunroof.eng.sun.com  Tue Oct  3 21:19:37 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25587
	for <ngtrans-archive@odin.ietf.org>; Tue, 3 Oct 2000 21:19: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 TAA24649;
	Tue, 3 Oct 2000 19:19:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA26783;
	Tue, 3 Oct 2000 18:18:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e941Hb123843
	for ngtrans-dist; Tue, 3 Oct 2000 18:17:37 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e941HV323836
	for <ngtrans@sunroof.eng.sun.com>; Tue, 3 Oct 2000 18:17:31 -0700 (PDT)
Received: from eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by jurassic.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e941HHh303631;
	Tue, 3 Oct 2000 18:17:18 -0700 (PDT)
Message-ID: <39DA8494.7C1D66B9@eng.sun.com>
Date: Tue, 03 Oct 2000 18:15:00 -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: "Fred L. Templin" <templin@erg.sri.com>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) IPv6-IPv4 compatibility address - new draft version 
 available
References: <20000929.162911.18619584.kazu@Mew.org> <39D8D328.364EB09C@erg.sri.com>
Content-Type: text/plain; charset=iso-8859-15
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

"Fred L. Templin" wrote:

> Hello,
>
> A new version of the draft entitled:
>
>   "An IPv6-IPv4 Compatibility Aggregatable Global Unicast Address
>    Format for Incremental Deployment of IPv6 Nodes Within Predominantly
>    IPv4-based Intranets"
>

Let me point the following scenario:

Two IPv6 nodes A & B share the same /64 subnet (s), with one of them
(a)  implementing your scheme and the other one (b) not.

Communication from (a) to (b) implies a router (r) on subnet (s) that
understand your scheme.

A typical setup for (b) with current implementations  will be:
    - a default route to a router (R) [Note (R) may be different than (r)]
    - a route for subnet (s) on the interface attached to this link.

When (b) will try to send a packet to (a), it will see (a) is part
of the same subnet, assume that it is on the same link and
will think that (a) is a neighbor thus try neighbor solicitation.
Neighbor discovery will not work. It will get no response.
Communication is broken.

To solve this issue, I see 2 solutions:

- (b) should not believe that (a) is on the same link even though it share
   the same subnet. For that, all routers must advertise the subnet as not on
link.
   You get into the case of a multilink subnet, which is not trivial.
   E.g. traffic from (b) to (a) might go first on (R). So (R) has to either
   implement your scheme or learn from (r) about the attached remote hosts...
   not trivial at all. Btw, it is the case you describe as not working on page
10.

- Or you mandate that all hosts within subnet (s) must implement your scheme.

The second option is, in my opinion, the only viable one. But then I fear it
removes a lot of the value of your proposal, targeted at incremental deployment.

The  problem you are trying to solve seems to be to bring IPv6 connectivity
to an isolated host within a site which has already deployed an IPv6
infrastructure in only some parts of the network .
I think this may be solve more easily by other methods, such as an
internal tunnel broker.

On another point, you claim that your proposal works even in the presence of
NAT or multiple NAT within a site. I do not see how this can be done.
For example, if 2 nodes share the same IPv4 address 10.0.0.1 and are
part of the same /64 IPv6 subnet, I do not see how the tunnel can be set up.

    - Alain.



From owner-ngtrans@sunroof.eng.sun.com  Wed Oct  4 14:47:41 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28754
	for <ngtrans-archive@odin.ietf.org>; Wed, 4 Oct 2000 14:47:40 -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 MAA25760;
	Wed, 4 Oct 2000 12:47:28 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA02926;
	Wed, 4 Oct 2000 11:46:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e94Ij1u24729
	for ngtrans-dist; Wed, 4 Oct 2000 11:45:01 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e94Iis324722
	for <ngtrans@sunroof.eng.sun.com>; Wed, 4 Oct 2000 11:44:54 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA02560;
	Wed, 4 Oct 2000 11:44:53 -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 MAA24116;
	Wed, 4 Oct 2000 12:44:51 -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 LAA13751;
	Wed, 4 Oct 2000 11:44:50 -0700 (PDT)
Message-ID: <39DB7AA3.D737C3E4@erg.sri.com>
Date: Wed, 04 Oct 2000 11:44:51 -0700
From: "Fred L. Templin" <templin@erg.sri.com>
X-Mailer: Mozilla 4.73 [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
Subject: Re: (ngtrans) IPv6-IPv4 compatibility address - new draft version 
 available
References: <20000929.162911.18619584.kazu@Mew.org> <39D8D328.364EB09C@erg.sri.com> <39DA8494.7C1D66B9@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 assume that since you are only talking about IPv6 correspondent nodes
that share the same /64 prefix, you are OK with the case of nodes that
DO NOT share the same /64 prefix - correct? I THINK this will be a fairly
significant (if not predominant) case - would you agree? That said, I
will address the particular scenario you are concerned with:

Alain Durand wrote:
> Let me point the following scenario:
> 
> Two IPv6 nodes A & B share the same /64 subnet (s), with one of them
> (a)  implementing your scheme and the other one (b) not.

When you say "share the same /64 subnet", do you mean "share the same /64
address prefix, but do NOT share the same (multiple access) datalink", or
"share the same datalink"? If the latter, then there is no problem because
(a) would hear (r)'s router advertisements and would automatically discontinue
use of its IPv6-IPv4 compatibility address and construct an IPv6 address via
address autoconfiguration with an interface identifier constructed via a
native IEEE 802.2 MAC address. (b) would cease using (a)'s IPv6-IPv4
compatibility address when it learns that (a) now has a native address due
to the address selection rule which prefers native addresses over IPv6-IPv6
compatibility addresses.

If instead you mean the former (as I presume), then the only logical
scenario is that (a) does NOT share a common datalink with (r) and (b)
DOES share a common datalink with (r). So, I'll continue from here with
this scenario in mind:
 
> Communication from (a) to (b) implies a router (r) on subnet (s) that
> understand your scheme.

Yes, where "subnet" means a common /64 network prefix, but NOT a common
multiple access datalink.
 
> A typical setup for (b) with current implementations  will be:
>     - a default route to a router (R) [Note (R) may be different than (r)]
>     - a route for subnet (s) on the interface attached to this link.
> 
> When (b) will try to send a packet to (a), it will see (a) is part
> of the same subnet, assume that it is on the same link and
> will think that (a) is a neighbor thus try neighbor solicitation.
> Neighbor discovery will not work. It will get no response.
> Communication is broken.
> 
> To solve this issue, I see 2 solutions:
> 
> - (b) should not believe that (a) is on the same link even though it share
>    the same subnet. For that, all routers must advertise the subnet as not on
> link.
>    You get into the case of a multilink subnet, which is not trivial.
>    E.g. traffic from (b) to (a) might go first on (R). So (R) has to either
>    implement your scheme or learn from (r) about the attached remote hosts...
>    not trivial at all. Btw, it is the case you describe as not working on page
> 10.
> 
> - Or you mandate that all hosts within subnet (s) must implement your scheme.
> 
> The second option is, in my opinion, the only viable one. But then I fear it
> removes a lot of the value of your proposal, targeted at incremental deployment.

As the document states:

=>   When a sender has an interface which shares a common 64-bit routing
=>   prefix with an IPv6-IPv4 compatibility destination address, however,
=>   the sender must assume that the destination is NOT directly reachable
=>   at the datalink level - even though the shared site-level routing
=>   prefix implies otherwise. Instead, if the sender comprises a dual-
=>   stack configuration, it should automatically tunnel the IPv6 packet
=>   (via IPv6-in-IPv4 tunneling as described in [MECH]) to the IPv4
=>   address embedded within the IPv6-IPv4 compatibility destination
=>   address' interface identifier. If the sender is an IPv6-only node
=>   that DOES NOT comprise a dual-stack configuration, however, it has no
=>   means for automatically tunneling the packet via IPv4. In this case:
=>
=>  - If the sender is the host that originates the packet, it should send
=>  the packet to a router that lists the 64-bit prefix in its router
=>  advertisements. If no such router exists, the sender should drop the
=>  packet and return a "No route to host" error indication to the ori-
=>  ginating application.
=>
=>  - If the sender is a router that forwards the packet, it should drop
=>  the packet and send an ICMPv6 "Destination Unreachable" message to the
=>  source

This implies that, for INTRA-SITE operation, IPv6 nodes must implement the
following simple test in ip6_output():

  if (<the destination's /64 prefix matches one of my interface prefixes>) {
+   if (<bytes 8-11 of the destination address == 0x02005EFE>) {
+     <assume destination is NOT on-link; send to a router which
+      advertises this /64 prefix>
+   } else
      <assume destination is on-link; perform ND and/or send directly
       to destination>
  } else {
    <perform an IPv6 routing lookup, and send to the best next-hop gateway>
  }

(Only the pseudo-code lines preceded by "+" are new). So, the solution
proposed by the document is basically the same as your proposed soluton
#2. But, two points about this:

  1) This is only required for INTRA-site operation between currently
     deployed IPv6 nodes and newly-deployed nodes using IPv6-IPv4
     compatibility addresses, and thus only represents a single case
     which may very well not be the predominant case. But even so, are
     there *REALLY* lots of currently-deployed IPv6 nodes which have
     cast-in-stone implementations that won't be upgraded to reflect the
     latest changes to the IPNG and NGTRANS protocol standards in due
     course?? If not, then it becomes merely a race as to whether
     newly-deployed nodes with IPv6-IPv4 compatibility addresses will
     proliferate before the above-described code changes are propagated
     to existing IPv6 nodes. Even if the newly-deployed nodes win the
     race, the INTRA-site issue will go away as existing nodes upgrade
     their IPv6 implementations - unless you believe existing nodes 
     predominantly have implementations which are cast-in-stone and
     will never change. (I somehow tend not to belive this is the case.)

  2) If you are concerned that (b) will discover some (R) that does
     not handle IPv6-IPv4 compatibility addresses when it *could have*
     discovered an (r) that *does* handle such addresses, an easy fix
     is to have (r) advertise a /96 prefix. For example, if the /64
     prefix is:

      3FFE:1a05:510:2422::/64

     and (r) is capable of performing automatic tunneling as per the
     IPv6-IPv4 compatibility scheme, then (r) could advertise:

      3FFE:1a05:510:2422:0200:5EFE::/96

     Then, (b) would prefer (r) over (R) for IPv6-IPv4 compatibility
     address destinations. I didn't want to "go there" in the draft, but
     perhaps I should have..
	 
> The  problem you are trying to solve seems to be to bring IPv6 connectivity
> to an isolated host within a site which has already deployed an IPv6
> infrastructure in only some parts of the network .
> I think this may be solve more easily by other methods, such as an
> internal tunnel broker.

The isolated host is just one limited example of what this is good for. This
scheme also supports entire isolated IPv6 *networks* that are buried within an
administrative domain with a predominantly IPv4-based infrastructure. In this
case, the isolated IPv6 networks will have gateways which use IPv6-IPv4
compatibility addresses for tunnelling across the IPv4 infrastructure, but
will use native IPv6 addresses internally. In fact, if you extrapolate upwards
in terms of what is meant by an "administrative domain", you could postulate
native IPv6 prefixes assignments for all border gateways at the core of the
existing Internet. Then, individual institutions would either deploy native
IPv6 networks or would use IPv6-IPv4 compatibility addresses to automatically
tunnel across portions of the pre-existing IPv4 Internet leading up to the
core. In this case, 6TO4 prefixes would never be needed!!

In short, I believe 6to4 is most useful near the "core" of the heterogeneous
IPv6/IPv4 Internet while my proposed scheme is most useful near the "edges".
To say that transition scenarios will be limited to only one or the other
seems rather inflexible to me. 

> On another point, you claim that your proposal works even in the presence of
> NAT or multiple NAT within a site. I do not see how this can be done.
> For example, if 2 nodes share the same IPv4 address 10.0.0.1 and are
> part of the same /64 IPv6 subnet, I do not see how the tunnel can be set up.

If there is a SINGLE private address space in effect within an administrative
domain, then presumably each node will have a unique IPv4 address assignment
within that address space; else IPv4 would be broken. (i.e. For a single
private address space "A", the address assignment 10.0.0.1 must be unique).
If an administrative domain has MULTIPLE independent private address spaces,
then there can potentially be duplicate address assignments on an inter-address
space  basis. (i.e. 10.0.0.1 might exist in both private address space "A"
and private address space "B".) In the case of MULTIPLE independent address
spaces, there must be a unique /64 prefix assignment for each private address
space. Since IPv6 prefix allocations to administrative authorities are expected
to be on a /48 (or larger) granularity, the SLA can be used for "subnetting" to
assign a unique /64 prefix to each private address space. Then, intra-site
IPv6-in-IPv4 tunnelling can be done WITHIN address spaces "A" and "B"
independently of one another, while IPv6 routing can be done between address
spaces "A" and "B" even if the correspondent hosts happen to have identical
(private) IPv4 address assignments. This was not explained in detail in the
document, but can be added easily.
 
>     - Alain.

Fred
templin@erg.sri.com


From owner-ngtrans@sunroof.eng.sun.com  Wed Oct 18 08:49:41 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18223
	for <ngtrans-archive@odin.ietf.org>; Wed, 18 Oct 2000 08:49:40 -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 GAA14398;
	Wed, 18 Oct 2000 06:49:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA16779;
	Wed, 18 Oct 2000 05:48:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9IClj711050
	for ngtrans-dist; Wed, 18 Oct 2000 05:47:45 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9IClc311043
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 05:47:38 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA29405
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 05:47:39 -0700 (PDT)
Received: from smtp.eisa.net.au (melb-mail.eisa.net.au [203.166.224.42])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA21017
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 05:47:36 -0700 (PDT)
Received: from computer.eisa.net.au (pppm15-9.eisa.net.au [203.42.188.9])
	by smtp.eisa.net.au (8.9.0/8.9.0) with ESMTP id XAA04172
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 23:47:30 +1100
Message-Id: <5.0.0.25.2.20001018234502.00a8c010@mail.eisa.net.au>
X-Sender: maharrop@mail.eisa.net.au
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 18 Oct 2000 23:45:30 +1000
To: ngtrans@sunroof.eng.sun.com
From: Mark Harrop <maharrop@eisa.net.au>
Subject: (ngtrans) List.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Mark Harrop <maharrop@eisa.net.au>

Hi..

Couls some kind soul pls email me the address and commands to join this list ?

Ta!
Mark Harrop



From owner-ngtrans@sunroof.eng.sun.com  Wed Oct 18 18:50:28 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14131
	for <ngtrans-archive@odin.ietf.org>; Wed, 18 Oct 2000 18:50:27 -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 QAA16338;
	Wed, 18 Oct 2000 16:50:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA24068;
	Wed, 18 Oct 2000 15:49:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9IMmiG12423
	for ngtrans-dist; Wed, 18 Oct 2000 15:48:44 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9IMkh312408;
	Wed, 18 Oct 2000 15:46:44 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA11847;
	Wed, 18 Oct 2000 15:46:39 -0700 (PDT)
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA05586;
	Wed, 18 Oct 2000 15:46:38 -0700 (PDT)
Received: from penelope.ecs.soton.ac.uk (penelope.ecs.soton.ac.uk [152.78.68.135])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id XAA19133;
	Wed, 18 Oct 2000 23:46:33 +0100 (BST)
Received: from penelope (penelope [152.78.68.135])
	by penelope.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id XAA25692;
	Wed, 18 Oct 2000 23:46:32 +0100 (BST)
Date: Wed, 18 Oct 2000 23:46:32 +0100 (BST)
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: members@ipv6forum.com, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, users@ipv6.org
Subject: (ngtrans) IPv6 2000: presentations are available online
Message-ID: <Pine.SOL.4.20.0010182333390.24003-100000@penelope.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Tim Chown <tjc@ecs.soton.ac.uk>


Hi,

Please excuse the "spam" but there is a new collection of IPv6 presentations
available online, taken from the XIWT/IPv6 Forum event that is being held
in Washington DC tomorrow and Friday.

See http://www.ipv6forum.com and look for the XIWT logo.

There are HTML, Powerpoint and PDF versions of most talks available; the rest 
will be added shortly.  Many deployment and application areas are covered.

If you want to go straight in to the presentations index, it's at:

http://www.ipv6forum.com/navbar/events/xiwt00/presentations/

Cheers,
Tim



From owner-ngtrans@sunroof.eng.sun.com  Wed Oct 18 19:22:40 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17652
	for <ngtrans-archive@odin.ietf.org>; Wed, 18 Oct 2000 19:22:40 -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 RAA03229;
	Wed, 18 Oct 2000 17:22:32 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA02915;
	Wed, 18 Oct 2000 16:22:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9INKul12508
	for ngtrans-dist; Wed, 18 Oct 2000 16:20:56 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9INKm312501
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 16:20:49 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA02021
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 16:20:47 -0700 (PDT)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id QAA15942
	for <ngtrans@sunroof.eng.sun.com>; Wed, 18 Oct 2000 16:20:47 -0700 (PDT)
Received: from rasp2-70.lbl.gov (Truckee.lbl.gov) [131.243.212.170] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13m2Vp-0001Jo-00; Wed, 18 Oct 2000 16:20:46 -0700
Message-Id: <5.0.0.25.0.20001018161613.00a5b4c8@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 18 Oct 2000 16:16:56 -0700
To: Mark Harrop <maharrop@eisa.net.au>, ngtrans@sunroof.eng.sun.com
From: Bob Fink <fink@es.net>
Subject: Re: (ngtrans) List.
In-Reply-To: <5.0.0.25.2.20001018234502.00a8c010@mail.eisa.net.au>
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 11:45 PM 10/18/2000 +1000, Mark Harrop wrote:
>Hi..
>
>Couls some kind soul pls email me the address and commands to join this list ?


Look at the ngtrans web pages pointed to from the 6bone web pages:

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

<http://www.6bone.net/ngtrans/>


Bob



From owner-ngtrans@sunroof.eng.sun.com  Thu Oct 26 13:36:59 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA27835
	for <ngtrans-archive@odin.ietf.org>; Thu, 26 Oct 2000 13:36:58 -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 LAA17108;
	Thu, 26 Oct 2000 11:36:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA08244;
	Thu, 26 Oct 2000 10:27:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9QHQKu18556
	for ngtrans-dist; Thu, 26 Oct 2000 10:26:20 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9QHQD318549
	for <ngtrans@sunroof.eng.sun.com>; Thu, 26 Oct 2000 10:26:13 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA03937
	for <ngtrans@sunroof.eng.sun.com>; Thu, 26 Oct 2000 10:26:12 -0700 (PDT)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id KAA09825
	for <ngtrans@sunroof.eng.sun.com>; Thu, 26 Oct 2000 10:26:12 -0700 (PDT)
Received: from rlfink.lbl.gov (Truckee.lbl.gov) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13oqn5-0000Fs-00; Thu, 26 Oct 2000 10:26:11 -0700
Message-Id: <5.0.0.25.0.20001026101107.02f58660@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Thu, 26 Oct 2000 10:26:01 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) NGtrans WG meetings in San Diego
Cc: Alain Durand <Alain.Durand@sun.com>, Bob Fink <fink@es.net>,
        Tony Hain <tonyhain@microsoft.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 WG FOlk:

Below are the just released agenda slots for ngtrans in San Diego.

We, the co-chairs, will be putting together an agenda over the next little 
while. Please send your suggested agenda items, or requests to speak on 
specific topics, to the co-chairs (use the cc list above).

===
WEDNESDAY, December 13, 2000
0900-1130 Morning Sessions
OPS     ngtrans         Next Generation Transition WG

THURSDAY, December 14, 2000
1300-1500 Afternoon Sessions I
OPS     ngtrans         Next Generation Transition WG
===


Thanks,

Bob



From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 12:16:50 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA14246
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 12:16: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 KAA29903;
	Fri, 27 Oct 2000 10:16:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA19094;
	Fri, 27 Oct 2000 09:15:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RGE4P19371
	for ngtrans-dist; Fri, 27 Oct 2000 09:14:04 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RGDv319364
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 09:13:57 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA21452
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 09:13:57 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA14565
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 09:13:56 -0700 (PDT)
Received: from esealnt409.al.sw.ericsson.se (esealnt409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id e9RGDtZ23375
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 18:13:56 +0200 (MEST)
Received: FROM esealnt743.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Fri Oct 27 18:13:54 2000 +0200
Received: by esealnt743.al.sw.ericsson.se with Internet Mail Service (5.5.2651.58)
	id <VXA7GFKQ>; Fri, 27 Oct 2000 18:13:53 +0200
Message-ID: <6346FEEF1F24D31183830008C791C55B04D35A28@eitrmnt101.tei.ericsson.se>
From: "Pietro Biasci (TEI)" <Pietro.Biasci@tei.ericsson.se>
To: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) SOCKS and IPv6
Date: Fri, 27 Oct 2000 18:05:44 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.58)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Pietro Biasci (TEI)" <Pietro.Biasci@tei.ericsson.se>

Hi all,

Is there someone of you that can help me to find some good and detailed review about IPv6/IPv4 gateway mechanism based on SOCKS other than the "draft-ietf-ngtrans-socks-gateway-05.txt" ?

Thanks and Regards, Pietro


From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 15:26:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA08081
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 15:26:08 -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 NAA21779;
	Fri, 27 Oct 2000 13:25:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA22132;
	Fri, 27 Oct 2000 12:24:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RJNkw19566
	for ngtrans-dist; Fri, 27 Oct 2000 12:23:47 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RJM0319548;
	Fri, 27 Oct 2000 12:22:01 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA13660;
	Fri, 27 Oct 2000 12:21:58 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA19021;
	Fri, 27 Oct 2000 13:21:49 -0600 (MDT)
Received: from hunkular.glarp.com (localhost [127.0.0.1])
	by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id NAA09586;
	Fri, 27 Oct 2000 13:21:37 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200010271921.NAA09586@hunkular.glarp.com>
To: snap-users@kame.net, freebsd-questions@FreeBSD.ORG,
        ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: (ngtrans) 6over4 for KAME (FreeBSD)
Date: Fri, 27 Oct 2000 13:21:37 -0600
From: Brad Huntting <huntting@hunkular.glarp.com>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brad Huntting <huntting@hunkular.glarp.com>


Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
FreeBSD?

I have a pointer to a UCLA project called "Virtual Ethernet" by
Quang Nguyen (no email address given), but it was written for the
Inria stack and FreeBSD2.  If there's nothing else available, I
may use this as a guide.


thanx,
brad


From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 17:08:24 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA01388
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 17:08:24 -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 PAA23290;
	Fri, 27 Oct 2000 15:08:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA15359;
	Fri, 27 Oct 2000 14:07:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RL6Lp19669
	for ngtrans-dist; Fri, 27 Oct 2000 14:06:21 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RL6F319662
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 14:06:16 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e9RL5XR23050
	for ngtrans@sunroof.eng.sun.com; Fri, 27 Oct 2000 14:05:33 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RJVu319599;
	Fri, 27 Oct 2000 12:31:56 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA23685;
	Fri, 27 Oct 2000 12:31:56 -0700 (PDT)
Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA25835;
	Fri, 27 Oct 2000 13:31:54 -0600 (MDT)
Received: from localhost (jan@localhost)
	by pogo.caustic.org (8.11.0/ignatz) with ESMTP id e9RJVlw78953;
	Fri, 27 Oct 2000 12:31:47 -0700 (PDT)
Date: Fri, 27 Oct 2000 12:31:47 -0700 (PDT)
From: "f.johan.beisser" <jan@caustic.org>
To: Brad Huntting <huntting@hunkular.glarp.com>
cc: snap-users@kame.net, freebsd-questions@FreeBSD.ORG,
        ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: (ngtrans) Re: 6over4 for KAME (FreeBSD)
In-Reply-To: <200010271921.NAA09586@hunkular.glarp.com>
Message-ID: <Pine.BSF.4.21.0010271230100.78517-100000@pogo.caustic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "f.johan.beisser" <jan@caustic.org>


i'm not sure if this is what you mean, but:

http://www.kfu.com/~nsayer/6to4/

also, i think that it is documented on http://www.kame.net.

of course, i oculd very well be talking out of my butt.

-- jan



On Fri, 27 Oct 2000, Brad Huntting wrote:

> 
> Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
> FreeBSD?
> 
> I have a pointer to a UCLA project called "Virtual Ethernet" by
> Quang Nguyen (no email address given), but it was written for the
> Inria stack and FreeBSD2.  If there's nothing else available, I
> may use this as a guide.
> 


-------/ f. johan beisser /--------------------------------------+
  http://caustic.org/~jan                      jan@caustic.org
   "Never laugh at someone until you've walked a mile in their
         shoes. Then laugh. For you are a mile away, and
                      you have their shoes."




From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 17:34:07 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07497
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 17:34:07 -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 PAA08844;
	Fri, 27 Oct 2000 15:34:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA17846;
	Fri, 27 Oct 2000 14:33:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RLWik19794
	for ngtrans-dist; Fri, 27 Oct 2000 14:32:44 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RLWe319787
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 14:32:40 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e9RLW0T23299
	for ngtrans@sunroof.eng.sun.com; Fri, 27 Oct 2000 14:32:00 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RLII319711;
	Fri, 27 Oct 2000 14:18:19 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA19207;
	Fri, 27 Oct 2000 14:18:19 -0700 (PDT)
Received: from minuet.das.harvard.edu (minuet.das.harvard.edu [140.247.50.251])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA22172;
	Fri, 27 Oct 2000 14:18:18 -0700 (PDT)
Received: from endor.eas.harvard.edu (endor.harvard.edu [128.103.50.55])
	by minuet.das.harvard.edu (8.9.1/8.9.1) with ESMTP id RAA26395;
	Fri, 27 Oct 2000 17:18:03 -0400 (EDT)
From: Dan Lanciani <ddl@deas.harvard.edu>
Received: (from ddl@localhost)
	by endor.eas.harvard.edu (8.8.8/8.8.8) id RAA13943;
	Fri, 27 Oct 2000 17:18:02 -0400 (EDT)
Date: Fri, 27 Oct 2000 17:18:02 -0400 (EDT)
Message-Id: <200010272118.RAA13943@endor.eas.harvard.edu>
To: huntting@hunkular.glarp.com, jan@caustic.org
Subject: (ngtrans) Re: 6over4 for KAME (FreeBSD)
Cc: freebsd-questions@FreeBSD.ORG, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, snap-users@kame.net
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Dan Lanciani <ddl@deas.harvard.edu>

|i'm not sure if this is what you mean, but:
|
|http://www.kfu.com/~nsayer/6to4/

I think that might not be what he meant. :)  However, speaking of 6to4,
how accepting are the 6bone sites of 0x2002 prefix addresses?  At first
glance, www.6bone.net and www.kame.net are happy to respond to packets
from 6to4 addresses, but some of the public IPv6 "tool" web sites don't
have a route to any 6to4 relay at all (or at least that seems to be the
case).  IMHO, 6to4 is a great way to encourage IPv6 deployment (especially
with Microsoft pushing it), but the addresses need to be treated as more
than a temporary hack if people are to commit.  (Alternately, I suppose
6to4 addresses could simply overtake "real" addresses. :)

				Dan Lanciani
				ddl@harvard.edu



From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 17:49:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10948
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 17:49: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 PAA19741;
	Fri, 27 Oct 2000 15:49:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA19274;
	Fri, 27 Oct 2000 14:49:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RLmH419857
	for ngtrans-dist; Fri, 27 Oct 2000 14:48:17 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RLkQ319841;
	Fri, 27 Oct 2000 14:46:27 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA21483;
	Fri, 27 Oct 2000 14:46:27 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA27530;
	Fri, 27 Oct 2000 14:46:27 -0700 (PDT)
Received: from hunkular.glarp.com (localhost [127.0.0.1])
	by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id PAA17119;
	Fri, 27 Oct 2000 15:46:26 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200010272146.PAA17119@hunkular.glarp.com>
To: "f.johan.beisser" <jan@caustic.org>
cc: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com, cmj@3Com.com
Subject: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
In-Reply-To: Your message of "Fri, 27 Oct 2000 12:31:47 PDT."
             <Pine.BSF.4.21.0010271230100.78517-100000@pogo.caustic.org> 
Date: Fri, 27 Oct 2000 15:46:25 -0600
From: Brad Huntting <huntting@hunkular.glarp.com>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brad Huntting <huntting@hunkular.glarp.com>


> http://www.kfu.com/~nsayer/6to4/

Actually this web page brings up another issue that a freind and
I were discussing just yesterday.  Anyone who's actually tried to
use 6to4 (2002::/16) has probably noticed that they need a default
route to reach the 6bone.  But even assuming you actually find such
a router it is almost always on the far side of the Internet; which
means that your packets get to take the scenic route on their way
to the 6bone.

One simple solution to this would seem to be to use a well known
IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
gateways.

In this way, anyone using 6to4 could reliably use 2002:(a.b.c.d)::1
(actual IPv6 address syntax will vary) as a default route to the
6bone.

6to4 gateways would advertise to the their IPv4 peers that they
have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
they can advertise a route for 2002::/16.

Does anyone see a problem with this?  I dont suppose there's already
a block of IPv4 address space set aside for anycast?


brad


From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 18:18:20 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17191
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 18:18:19 -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 QAA06190;
	Fri, 27 Oct 2000 16:18:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA06057;
	Fri, 27 Oct 2000 15:17:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RMFRt19928
	for ngtrans-dist; Fri, 27 Oct 2000 15:15:27 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RMFK319921
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 15:15:20 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA00363
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 15:15:20 -0700 (PDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id PAA09124
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 15:15:19 -0700 (PDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 27 Oct 2000 14:58:01 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <VX4RW04B>; Fri, 27 Oct 2000 14:40:48 -0700
Message-ID: <CB7153628BD3724096258CBFD70AA891041DB8@red-msg-04.redmond.corp.microsoft.com>
From: Brian Zill <bzill@microsoft.com>
To: "'f.johan.beisser'" <jan@caustic.org>,
        Brad Huntting
	 <huntting@hunkular.glarp.com>
Cc: snap-users@kame.net, freebsd-questions@FreeBSD.ORG,
        ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: (ngtrans) RE: 6over4 for KAME (FreeBSD)
Date: Fri, 27 Oct 2000 14:40:23 -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>

6to4 and 6over4, while having unfortunately similar names, are quite
different things.

6to4 is a form of automatic IPv6 tunneling over IPv4.  The IPv4 address of
the "home" end of the tunnel is encoded into the IPv6 prefix.  See
draft-ietf-ngtrans-6to4-07.txt.

6over4 is another IPv6 over "foo", where "foo" in this case is a
multicast-enabled IPv4 network, instead of say Ethernet or FDDI.  See RFC
2529.

My recollection is that an implementation of 6over4 for some BSD flavor
exists, since I recall someone performing some interoperability testing
between our implementation and that implementation.  UCLA sounds familiar.
Aren't two interoperating implementations a requirement for Proposed
Standard? (RFC 2529 is at PS) I'm not aware of any others offhand, but it
wouldn't surprise me if there were some.

--Brian

> -----Original Message-----
> From: f.johan.beisser [mailto:jan@caustic.org]
> Sent: Friday, 27 October, 2000 12:32
> To: Brad Huntting
> Cc: snap-users@kame.net; freebsd-questions@FreeBSD.ORG;
> ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com
> Subject: Re: 6over4 for KAME (FreeBSD)
> 
> 
> 
> i'm not sure if this is what you mean, but:
> 
> http://www.kfu.com/~nsayer/6to4/
> 
> also, i think that it is documented on http://www.kame.net.
> 
> of course, i oculd very well be talking out of my butt.
> 
> -- jan
> 
> 
> 
> On Fri, 27 Oct 2000, Brad Huntting wrote:
> 
> > 
> > Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
> > FreeBSD?
> > 
> > I have a pointer to a UCLA project called "Virtual Ethernet" by
> > Quang Nguyen (no email address given), but it was written for the
> > Inria stack and FreeBSD2.  If there's nothing else available, I
> > may use this as a guide.
> > 
> 
> 
> -------/ f. johan beisser /--------------------------------------+
>   http://caustic.org/~jan                      jan@caustic.org
>    "Never laugh at someone until you've walked a mile in their
>          shoes. Then laugh. For you are a mile away, and
>                       you have their shoes."
> 
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 


From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 19:23:55 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01274
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 19:23:53 -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 RAA11055;
	Fri, 27 Oct 2000 17:23:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA17029;
	Fri, 27 Oct 2000 16:23:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RNLZM19978
	for ngtrans-dist; Fri, 27 Oct 2000 16:21:35 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RNLM319963;
	Fri, 27 Oct 2000 16:21:22 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA16454;
	Fri, 27 Oct 2000 16:21:22 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA07676;
	Fri, 27 Oct 2000 16:21:21 -0700 (PDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Fri, 27 Oct 2000 16:01:03 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 27 Oct 2000 16:01:42 -0700 (Pacific Daylight Time)
Received: from DINO.platinum.corp.microsoft.com ([172.30.236.100]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Fri, 27 Oct 2000 16:01:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C04069.DEC25102"
Subject: (ngtrans) RE: 6over4 for KAME (FreeBSD)
Date: Fri, 27 Oct 2000 16:01:41 -0700
Message-ID: <5B90AD65A9E8934987DB0C8C0762657401D42BFD@DF-BOWWOW.platinum.corp.microsoft.com>
Thread-Topic: 6over4 for KAME (FreeBSD)
Thread-Index: AcBAYYRv2TnjaFLORzOg22lBbUiJXAACEImQ
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Brian Zill" <bzill@microsoft.com>, "f.johan.beisser" <jan@caustic.org>,
        "Brad Huntting" <huntting@hunkular.glarp.com>
Cc: <snap-users@kame.net>, <freebsd-questions@FreeBSD.ORG>,
        <ngtrans@sunroof.eng.sun.com>, <ipng@sunroof.eng.sun.com>
X-OriginalArrivalTime: 27 Oct 2000 23:01:42.0392 (UTC) FILETIME=[DF075F80:01C04069]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C04069.DEC25102
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Brian Zill writes:
> Aren't two interoperating implementations a requirement for Proposed
> Standard?

No, I believe it's a requirement for *Draft* Standard.

-Dave

------_=_NextPart_001_01C04069.DEC25102
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4576.0">
<TITLE>RE: 6over4 for KAME (FreeBSD)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Brian Zill writes:</FONT>

<BR><FONT SIZE=3D2>&gt; Aren't two interoperating implementations a =
requirement for Proposed</FONT>

<BR><FONT SIZE=3D2>&gt; Standard?</FONT>
</P>

<P><FONT SIZE=3D2>No, I believe it's a requirement for *Draft* =
Standard.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C04069.DEC25102--


From owner-ngtrans@sunroof.eng.sun.com  Fri Oct 27 19:23:57 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA01299
	for <ngtrans-archive@odin.ietf.org>; Fri, 27 Oct 2000 19:23:57 -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 RAA11047;
	Fri, 27 Oct 2000 17:23:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA22682;
	Fri, 27 Oct 2000 16:23:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RNLZ519977
	for ngtrans-dist; Fri, 27 Oct 2000 16:21:35 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RNLM319964;
	Fri, 27 Oct 2000 16:21:22 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA16460;
	Fri, 27 Oct 2000 16:21:22 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA07682;
	Fri, 27 Oct 2000 16:21:22 -0700 (PDT)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Fri, 27 Oct 2000 15:59:54 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 27 Oct 2000 16:00:33 -0700 (Pacific Daylight Time)
Received: from DINO.platinum.corp.microsoft.com ([172.30.236.100]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Fri, 27 Oct 2000 16:00:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C04069.B595E605"
Subject: RE: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
Date: Fri, 27 Oct 2000 16:00:32 -0700
Message-ID: <5B90AD65A9E8934987DB0C8C0762657401D42BFC@DF-BOWWOW.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
Thread-Index: AcBAX8/yFxWAnLZoTDWo6dNJtNiVywACYDig
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Brad Huntting" <huntting@hunkular.glarp.com>,
        "f.johan.beisser" <jan@caustic.org>
Cc: <ngtrans@sunroof.eng.sun.com>, <ipng@sunroof.eng.sun.com>, <cmj@3Com.com>
X-OriginalArrivalTime: 27 Oct 2000 23:00:33.0268 (UTC) FILETIME=[B5D3E340:01C04069]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C04069.B595E605
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This was mentioned in the NGtrans meeting in Pittsburgh,=20
and no such an anycast address doesn't currently exist.

What would be needed would be to get a prefix short=20
enough to pass the prefix length filters in the Internet,
and then just use 1 of the addresses in that large prefix.

(Some would argue that having packets take the scenic
route as you describe is desirable, however.)

-Dave

> -----Original Message-----
> From: Brad Huntting [mailto:huntting@hunkular.glarp.com]
> Sent: Friday, October 27, 2000 2:46 PM
> To: f.johan.beisser
> Cc: ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com;=20
> cmj@3Com.com
> Subject: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
>=20
>=20
>=20
> > http://www.kfu.com/~nsayer/6to4/
>=20
> Actually this web page brings up another issue that a freind and
> I were discussing just yesterday.  Anyone who's actually tried to
> use 6to4 (2002::/16) has probably noticed that they need a default
> route to reach the 6bone.  But even assuming you actually find such
> a router it is almost always on the far side of the Internet; which
> means that your packets get to take the scenic route on their way
> to the 6bone.
>=20
> One simple solution to this would seem to be to use a well known
> IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> gateways.
>=20
> In this way, anyone using 6to4 could reliably use 2002:(a.b.c.d)::1
> (actual IPv6 address syntax will vary) as a default route to the
> 6bone.
>=20
> 6to4 gateways would advertise to the their IPv4 peers that they
> have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
> they can advertise a route for 2002::/16.
>=20
> Does anyone see a problem with this?  I dont suppose there's already
> a block of IPv4 address space set aside for anycast?
>=20
>=20
> brad

------_=_NextPart_001_01C04069.B595E605
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4576.0">
<TITLE>RE: (ngtrans) An IPv4 anycast address for 6to4&lt;-&gt;6bone =
gateways</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>This was mentioned in the NGtrans meeting in =
Pittsburgh, </FONT>

<BR><FONT SIZE=3D2>and no such an anycast address doesn't currently =
exist.</FONT>
</P>

<P><FONT SIZE=3D2>What would be needed would be to get a prefix short =
</FONT>

<BR><FONT SIZE=3D2>enough to pass the prefix length filters in the =
Internet,</FONT>

<BR><FONT SIZE=3D2>and then just use 1 of the addresses in that large =
prefix.</FONT>
</P>

<P><FONT SIZE=3D2>(Some would argue that having packets take the =
scenic</FONT>

<BR><FONT SIZE=3D2>route as you describe is desirable, however.)</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>

<BR><FONT SIZE=3D2>&gt; From: Brad Huntting [<A =
HREF=3D"mailto:huntting@hunkular.glarp.com">mailto:huntting@hunkular.glar=
p.com</A>]</FONT>

<BR><FONT SIZE=3D2>&gt; Sent: Friday, October 27, 2000 2:46 PM</FONT>

<BR><FONT SIZE=3D2>&gt; To: f.johan.beisser</FONT>

<BR><FONT SIZE=3D2>&gt; Cc: ngtrans@sunroof.eng.sun.com; =
ipng@sunroof.eng.sun.com; </FONT>

<BR><FONT SIZE=3D2>&gt; cmj@3Com.com</FONT>

<BR><FONT SIZE=3D2>&gt; Subject: (ngtrans) An IPv4 anycast address for =
6to4&lt;-&gt;6bone gateways</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://www.kfu.com/~nsayer/6to4/">http://www.kfu.com/~nsayer/6to4=
/</A></FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; Actually this web page brings up another issue =
that a freind and</FONT>

<BR><FONT SIZE=3D2>&gt; I were discussing just yesterday.&nbsp; Anyone =
who's actually tried to</FONT>

<BR><FONT SIZE=3D2>&gt; use 6to4 (2002::/16) has probably noticed that =
they need a default</FONT>

<BR><FONT SIZE=3D2>&gt; route to reach the 6bone.&nbsp; But even =
assuming you actually find such</FONT>

<BR><FONT SIZE=3D2>&gt; a router it is almost always on the far side of =
the Internet; which</FONT>

<BR><FONT SIZE=3D2>&gt; means that your packets get to take the scenic =
route on their way</FONT>

<BR><FONT SIZE=3D2>&gt; to the 6bone.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; One simple solution to this would seem to be to =
use a well known</FONT>

<BR><FONT SIZE=3D2>&gt; IPv4 &quot;anycast&quot; address (call it =
&quot;a.b.c.d&quot; for now) for all 6to4</FONT>

<BR><FONT SIZE=3D2>&gt; gateways.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; In this way, anyone using 6to4 could reliably =
use 2002:(a.b.c.d)::1</FONT>

<BR><FONT SIZE=3D2>&gt; (actual IPv6 address syntax will vary) as a =
default route to the</FONT>

<BR><FONT SIZE=3D2>&gt; 6bone.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; 6to4 gateways would advertise to the their IPv4 =
peers that they</FONT>

<BR><FONT SIZE=3D2>&gt; have a route for &quot;a.b.c.d&quot;.&nbsp; And =
for their IPv6 peers (the 6bone)</FONT>

<BR><FONT SIZE=3D2>&gt; they can advertise a route for 2002::/16.</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; Does anyone see a problem with this?&nbsp; I =
dont suppose there's already</FONT>

<BR><FONT SIZE=3D2>&gt; a block of IPv4 address space set aside for =
anycast?</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; brad</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C04069.B595E605--


From owner-ngtrans@sunroof.eng.sun.com  Sat Oct 28 04:29:48 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA13267
	for <ngtrans-archive@odin.ietf.org>; Sat, 28 Oct 2000 04:29:48 -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 CAA23280;
	Sat, 28 Oct 2000 02:29:41 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA16749;
	Sat, 28 Oct 2000 01:29:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9S8SFm20383
	for ngtrans-dist; Sat, 28 Oct 2000 01:28:16 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9S8Pq320368;
	Sat, 28 Oct 2000 01:25:53 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA14671;
	Sat, 28 Oct 2000 01:25:51 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA20149;
	Sat, 28 Oct 2000 01:25:50 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id EAA09946;
        Sat, 28 Oct 2000 04:25:40 -0400 (EDT)
Message-Id: <200010280825.EAA09946@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Brad Huntting <huntting@hunkular.glarp.com>
cc: "f.johan.beisser" <jan@caustic.org>, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com, cmj@3Com.com
Subject: Re: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways 
In-reply-to: Your message of "Fri, 27 Oct 2000 15:46:25 MDT."
             <200010272146.PAA17119@hunkular.glarp.com> 
X-SUBJECT-MSG-FROM: Brad Huntting <huntting@hunkular.glarp.com> 
Date: Sat, 28 Oct 2000 04:25:39 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> One simple solution to this would seem to be to use a well known
> IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> gateways.
 
I've thought about this a bit, and would like it slightly better
if the v4 anycast address were used as the link layer address
for a variant of router discovery (rather than assuming a default
route to the anycast address).  It's more versatile that way.
 
Keith


From owner-ngtrans@sunroof.eng.sun.com  Sat Oct 28 12:12:30 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA24988
	for <ngtrans-archive@odin.ietf.org>; Sat, 28 Oct 2000 12:12:29 -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 KAA00582;
	Sat, 28 Oct 2000 10:12:22 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA05224;
	Sat, 28 Oct 2000 09:12:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9SGBER20573
	for ngtrans-dist; Sat, 28 Oct 2000 09:11:14 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9SG9b320558;
	Sat, 28 Oct 2000 09:09:37 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA21488;
	Sat, 28 Oct 2000 09:09:38 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA00011;
	Sat, 28 Oct 2000 10:09:36 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e9SG8lY34786;
	Sat, 28 Oct 2000 18:08:48 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA01909;
	Sat, 28 Oct 2000 18:08:47 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id SAA29477;
	Sat, 28 Oct 2000 18:09:15 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200010281609.SAA29477@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: snap-users@kame.net
cc: freebsd-questions@FreeBSD.ORG, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com
Subject: (ngtrans) Re: (KAME-snap 3558) 6over4 for KAME (FreeBSD) 
In-reply-to: Your message of Fri, 27 Oct 2000 13:21:37 MDT.
             <200010271921.NAA09586@hunkular.glarp.com> 
Date: Sat, 28 Oct 2000 18:09:15 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
   FreeBSD?
   
=> I have one and I know there is (was?) one done by the CAIRN group
(perhaps the one you have referenced).

   I have a pointer to a UCLA project called "Virtual Ethernet" by
   Quang Nguyen (no email address given), but it was written for the
   Inria stack and FreeBSD2.  If there's nothing else available, I
   may use this as a guide.
   
=> of course mine is for the INRIA stack but it is rather easy to
adapt or rewrite... The only issue is you can't delete multicast
structures because of the chaining but this is not an important
issue (because of the lack of interest for 6over4?).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Sat Oct 28 12:27:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA28168
	for <ngtrans-archive@odin.ietf.org>; Sat, 28 Oct 2000 12:27: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 KAA03921;
	Sat, 28 Oct 2000 10:26:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA07861;
	Sat, 28 Oct 2000 09:26:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9SGPa320615
	for ngtrans-dist; Sat, 28 Oct 2000 09:25:36 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9SGNw320600;
	Sat, 28 Oct 2000 09:23:58 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA06240;
	Sat, 28 Oct 2000 09:23:58 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03201;
	Sat, 28 Oct 2000 10:23:56 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e9SGMPY28939;
	Sat, 28 Oct 2000 18:22:25 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA02250;
	Sat, 28 Oct 2000 18:22:24 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id SAA29597;
	Sat, 28 Oct 2000 18:22:50 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200010281622.SAA29597@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Brian Zill <bzill@microsoft.com>
cc: "'f.johan.beisser'" <jan@caustic.org>,
        Brad Huntting <huntting@hunkular.glarp.com>, snap-users@kame.net,
        freebsd-questions@FreeBSD.ORG, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com
Subject: (ngtrans) Re: 6over4 for KAME (FreeBSD) 
In-reply-to: Your message of Fri, 27 Oct 2000 14:40:23 PDT.
             <CB7153628BD3724096258CBFD70AA891041DB8@red-msg-04.redmond.corp.microsoft.com> 
Date: Sat, 28 Oct 2000 18:22:50 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   My recollection is that an implementation of 6over4 for some BSD flavor
   exists, since I recall someone performing some interoperability testing
   between our implementation and that implementation.

=> I did some interoperability testing at the interim meeting in Tokyo
using a 3Com multicast router (for fun!). I can remember details, only
it was very soon in the morning...

   UCLA sounds familiar.

=> I got one day the CAIRN code but when I tried to port it to FreeBSD 3.x
I discovered I had only some parts then I kept only the name (virtual
Ethernet -> vet) which is in fact the (first/only) thing needed to implement
a new flavor of IPv6 over IPv4 (I have 4 different ones :-).

   Aren't two interoperating implementations a requirement for Proposed
   Standard? (RFC 2529 is at PS) I'm not aware of any others offhand, but it
   wouldn't surprise me if there were some.
   
=> Cisco supported this but this was removed... Obviously 6to4 (a *different*
thing) is far more popular (for bad reasons IMHO).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Sat Oct 28 15:04:09 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA05519
	for <ngtrans-archive@odin.ietf.org>; Sat, 28 Oct 2000 15:04:09 -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 NAA16295;
	Sat, 28 Oct 2000 13:03:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA17075;
	Sat, 28 Oct 2000 12:03:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9SJ2V220679
	for ngtrans-dist; Sat, 28 Oct 2000 12:02:32 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9SJ0m320663;
	Sat, 28 Oct 2000 12:00:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA18151;
	Sat, 28 Oct 2000 12:00:47 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA15357;
	Sat, 28 Oct 2000 13:00:46 -0600 (MDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA02393;
        Sat, 28 Oct 2000 15:00:22 -0400 (EDT)
Message-Id: <200010281900.PAA02393@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
cc: Brian Zill <bzill@microsoft.com>, "'f.johan.beisser'" <jan@caustic.org>,
        Brad Huntting <huntting@hunkular.glarp.com>, snap-users@kame.net,
        freebsd-questions@FreeBSD.ORG, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: 6over4 for KAME (FreeBSD) 
In-reply-to: Your message of "Sat, 28 Oct 2000 18:22:50 +0200."
             <200010281622.SAA29597@givry.rennes.enst-bretagne.fr> 
Date: Sat, 28 Oct 2000 15:00:22 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> => Cisco supported this but this was removed... Obviously 6to4 (a *different*
> thing) is far more popular (for bad reasons IMHO).

6to4 and 6over4 solve different problems; there's very little overlap in 
their applicability.   So if there is more interest in 6to4 than 6over4 
it may be only a reflection that it is easier to upgrade a private intranet 
to support native IPv6 (thus bypassing 6over4) than to upgrade the
public Internet to support native IPv6.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 03:51:03 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA25714
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 03:51:03 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA18971;
	Mon, 30 Oct 2000 01:50:45 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id AAA06110;
	Mon, 30 Oct 2000 00:40:06 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9U8dHT21236
	for ngtrans-dist; Mon, 30 Oct 2000 00:39:17 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9U8dB321229
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 00:39:11 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id AAA28674
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 00:39:12 -0800 (PST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA11808
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 00:39:11 -0800 (PST)
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 13qATG-00094T-00
	for ngtrans@sunroof.eng.sun.com; Mon, 30 Oct 2000 00:39:10 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) back to back
Message-Id: <E13qATG-00094T-00@rip.psg.com>
Date: Mon, 30 Oct 2000 00:39:10 -0800
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

say a provider manages to turn on native ipv6 on an entire large backbone,
so it is running native v4 and native v6.

  o please describe the gating/translation for a native v6 flow from a v6
    customer to a customer of one of the backbone's peers where that peer
    backbone has not put up native v6.

  o please describe where the v4 packts a v4 customer of this backbone are
    gated/ translated when they want to talk to a v6-native on the same
    backbone.

randy


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 11:32:32 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15257
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 11:32:30 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00949;
	Mon, 30 Oct 2000 09:32:16 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA28399;
	Mon, 30 Oct 2000 08:31:01 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UGTwQ21470
	for ngtrans-dist; Mon, 30 Oct 2000 08:29:58 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UGTp321463
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:29:51 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA28048
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:29:51 -0800 (PST)
Received: from mail-gw1.hursley.ibm.com (mail-gw1.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA05997
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:29:49 -0800 (PST)
Received: from sp15en17.hursley.ibm.com (sp15at17.hursley.ibm.com [9.20.45.103])
	by mail-gw1.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id QAA27776;
	Mon, 30 Oct 2000 16:29:39 GMT
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43])
	by sp15en17.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id QAA24136;
	Mon, 30 Oct 2000 16:29:30 GMT
Message-ID: <39FDA1E3.243ED996@hursley.ibm.com>
Date: Mon, 30 Oct 2000 10:29:23 -0600
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: Christian Huitema <huitema@microsoft.com>
CC: "'Brad Huntting'" <huntting@hunkular.glarp.com>,
        "f.johan.beisser" <jan@caustic.org>, ngtrans@sunroof.eng.sun.com,
        cmj@3Com.com
Subject: (ngtrans) Re: An IPv4 anycast address for 6to4<->6bone gateways
References: <B5468CB3A359784A81A0923A24C01CA60BAF65@red-msg-03.redmond.corp.microsoft.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

Personally, I'd prefer to re-allocate Net 10 for this :-)

Yes, this is an interesting approach. Anybody want to write a draft?

N.B. 6to4 is an NGTRANS work item. I have removed IPNGWG from the copies.

   Brian

Christian Huitema wrote:
> 
> Actually, what you want is to reserve sufficiently large IP address prefix,
> so that it will be accepted without questions by BGP routers -- at least a
> /19; a class B would be nice; in fact, if an address rich institution would
> donate a class B for that purpose, that would be even better; asking the
> IANA to reserve 191.255/16 for that purpose would also look cool. It would
> also be useful to dedicate an IPv4 AS number to that purpose.
> 
> The IPv6 routers that have a complete access to both IPv6 and IPv4 would
> announce the corresponding prefix in their local IGP, as a route to an
> external network. The ASes that run such routers and are willing to provide
> access to the v6 network would announce a path to the v6 AS and to the 6to4
> prefix using BGP; they could easily use the existing structure of peering
> and transit agreement to control to whom they are willing to provide
> service. The whole v6 network will appear to v4 as a single AS, with lots of
> peering points all over the place.
> 
> The 6to4 gateways would then send use an address under the 6to4 prefix as a
> default route for reaching v6 packets. It will normally reach the service
> provided by their ISP, or by the closest ISP according to inter-domain
> routing.
> 
> This scheme has many advantages. It is simple to implement in 6to4 gateways,
> it allows ISP to control to whom they are providing service, it allows for
> independent deployments of gateways to the 6Bone and the v6 network by
> multiple ISPs, it allows for scaling by deploying a large number of "peering
> points."
> 
> In the acknowledgement section: I believe that scheme was first proposed by
> Randy Bush.
> 
> -- Christian Huitema
> 
> > -----Original Message-----
> > From: Brad Huntting [mailto:huntting@hunkular.glarp.com]
> > Sent: Friday, October 27, 2000 2:46 PM
> > To: f.johan.beisser
> > Cc: ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com;
> > cmj@3Com.com
> > Subject: An IPv4 anycast address for 6to4<->6bone gateways
> >
> >
> >
> > > http://www.kfu.com/~nsayer/6to4/
> >
> > Actually this web page brings up another issue that a freind and
> > I were discussing just yesterday.  Anyone who's actually tried to
> > use 6to4 (2002::/16) has probably noticed that they need a default
> > route to reach the 6bone.  But even assuming you actually find such
> > a router it is almost always on the far side of the Internet; which
> > means that your packets get to take the scenic route on their way
> > to the 6bone.
> >
> > One simple solution to this would seem to be to use a well known
> > IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> > gateways.
> >
> > In this way, anyone using 6to4 could reliably use 2002:(a.b.c.d)::1
> > (actual IPv6 address syntax will vary) as a default route to the
> > 6bone.
> >
> > 6to4 gateways would advertise to the their IPv4 peers that they
> > have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
> > they can advertise a route for 2002::/16.
> >
> > Does anyone see a problem with this?  I dont suppose there's already
> > a block of IPv4 address space set aside for anycast?
> >
> >
> > brad
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                      http://playground.sun.com/ipng
> > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------
> >
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Program Director, Internet Standards & Technology, IBM 
On assignment for IBM at http://www.iCAIR.org 
Board Chairman, Internet Society http://www.isoc.org
Non-IBM email: brian@icair.org


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 11:49:47 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19692
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 11:49:47 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA13746;
	Mon, 30 Oct 2000 09:49:35 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA02204;
	Mon, 30 Oct 2000 08:48:42 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UGlra21525
	for ngtrans-dist; Mon, 30 Oct 2000 08:47:53 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UGlf321518
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:47:41 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA01929
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:47:28 -0800 (PST)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA28627
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 08:47:28 -0800 (PST)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 30 Oct 2000 08:47:27 -0800 (Pacific Standard Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <V5H1ZTKT>; Mon, 30 Oct 2000 08:47:18 -0800
Message-ID: <B5468CB3A359784A81A0923A24C01CA60192356E@red-msg-03.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Brian E Carpenter'" <brian@hursley.ibm.com>
Cc: "'Brad Huntting'" <huntting@hunkular.glarp.com>,
        "f.johan.beisser"
	 <jan@caustic.org>, ngtrans@sunroof.eng.sun.com,
        cmj@3Com.com
Subject: (ngtrans) RE: An IPv4 anycast address for 6to4<->6bone gateways
Date: Mon, 30 Oct 2000 08:47:11 -0800
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Christian Huitema <huitema@microsoft.com>

That, or you incorporate it in the 6to4 draft. What do you prefer?

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
> Sent: Monday, October 30, 2000 8:29 AM
> To: Christian Huitema
> Cc: 'Brad Huntting'; f.johan.beisser; ngtrans@sunroof.eng.sun.com;
> cmj@3Com.com
> Subject: Re: An IPv4 anycast address for 6to4<->6bone gateways
> 
> 
> Personally, I'd prefer to re-allocate Net 10 for this :-)
> 
> Yes, this is an interesting approach. Anybody want to write a draft?
> 
> N.B. 6to4 is an NGTRANS work item. I have removed IPNGWG from 
> the copies.
> 
>    Brian
> 
> Christian Huitema wrote:
> > 
> > Actually, what you want is to reserve sufficiently large IP 
> address prefix,
> > so that it will be accepted without questions by BGP 
> routers -- at least a
> > /19; a class B would be nice; in fact, if an address rich 
> institution would
> > donate a class B for that purpose, that would be even 
> better; asking the
> > IANA to reserve 191.255/16 for that purpose would also look 
> cool. It would
> > also be useful to dedicate an IPv4 AS number to that purpose.
> > 
> > The IPv6 routers that have a complete access to both IPv6 
> and IPv4 would
> > announce the corresponding prefix in their local IGP, as a 
> route to an
> > external network. The ASes that run such routers and are 
> willing to provide
> > access to the v6 network would announce a path to the v6 AS 
> and to the 6to4
> > prefix using BGP; they could easily use the existing 
> structure of peering
> > and transit agreement to control to whom they are willing to provide
> > service. The whole v6 network will appear to v4 as a single 
> AS, with lots of
> > peering points all over the place.
> > 
> > The 6to4 gateways would then send use an address under the 
> 6to4 prefix as a
> > default route for reaching v6 packets. It will normally 
> reach the service
> > provided by their ISP, or by the closest ISP according to 
> inter-domain
> > routing.
> > 
> > This scheme has many advantages. It is simple to implement 
> in 6to4 gateways,
> > it allows ISP to control to whom they are providing 
> service, it allows for
> > independent deployments of gateways to the 6Bone and the v6 
> network by
> > multiple ISPs, it allows for scaling by deploying a large 
> number of "peering
> > points."
> > 
> > In the acknowledgement section: I believe that scheme was 
> first proposed by
> > Randy Bush.
> > 
> > -- Christian Huitema
> > 
> > > -----Original Message-----
> > > From: Brad Huntting [mailto:huntting@hunkular.glarp.com]
> > > Sent: Friday, October 27, 2000 2:46 PM
> > > To: f.johan.beisser
> > > Cc: ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com;
> > > cmj@3Com.com
> > > Subject: An IPv4 anycast address for 6to4<->6bone gateways
> > >
> > >
> > >
> > > > http://www.kfu.com/~nsayer/6to4/
> > >
> > > Actually this web page brings up another issue that a freind and
> > > I were discussing just yesterday.  Anyone who's actually tried to
> > > use 6to4 (2002::/16) has probably noticed that they need a default
> > > route to reach the 6bone.  But even assuming you actually 
> find such
> > > a router it is almost always on the far side of the 
> Internet; which
> > > means that your packets get to take the scenic route on their way
> > > to the 6bone.
> > >
> > > One simple solution to this would seem to be to use a well known
> > > IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> > > gateways.
> > >
> > > In this way, anyone using 6to4 could reliably use 
> 2002:(a.b.c.d)::1
> > > (actual IPv6 address syntax will vary) as a default route to the
> > > 6bone.
> > >
> > > 6to4 gateways would advertise to the their IPv4 peers that they
> > > have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
> > > they can advertise a route for 2002::/16.
> > >
> > > Does anyone see a problem with this?  I dont suppose 
> there's already
> > > a block of IPv4 address space set aside for anycast?
> > >
> > >
> > > brad
> > > 
> --------------------------------------------------------------------
> > > IETF IPng Working Group Mailing List
> > > IPng Home Page:                      
http://playground.sun.com/ipng
> > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------
> >
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Program Director, Internet Standards & Technology, IBM 
On assignment for IBM at http://www.iCAIR.org 
Board Chairman, Internet Society http://www.isoc.org
Non-IBM email: brian@icair.org


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:00:22 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05645
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:00:16 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA09376;
	Mon, 30 Oct 2000 10:59:49 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA22250;
	Mon, 30 Oct 2000 09:58:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UHuxa21601
	for ngtrans-dist; Mon, 30 Oct 2000 09:56:59 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UHuq321594
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 09:56:52 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA09408
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 09:56:51 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA06857
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:56:42 -0700 (MST)
Received: from zed.isi.edu (root@zed.isi.edu [128.9.160.57])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id JAA19490;
	Mon, 30 Oct 2000 09:56:37 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.9.3/8.8.6) id JAA26007;
	Mon, 30 Oct 2000 09:56:37 -0800
Message-Id: <200010301756.JAA26007@zed.isi.edu>
Subject: Re: (ngtrans) Re: An IPv4 anycast address for 6to4<->6bone gateways
To: brian@hursley.ibm.com
Date: Mon, 30 Oct 2000 09:56:37 -0800 (PST)
Cc: huitema@microsoft.com (Christian Huitema),
        huntting@hunkular.glarp.com ('Brad Huntting'),
        jan@caustic.org (f.johan.beisser), ngtrans@sunroof.eng.sun.com,
        cmj@3Com.com
In-Reply-To: <39FDA1E3.243ED996@hursley.ibm.com> from "Brian E Carpenter" at Oct 30, 2000 10:29:23 AM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bill Manning <bmanning@ISI.EDU>
Content-Transfer-Encoding: 7bit


While this would make life a bit easier, I am dubious of such a tactic.
Tends to leave things in a transition state in perpetuity.  


-- 
--bill


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:23:20 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12472
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:23:17 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA27718;
	Mon, 30 Oct 2000 11:23:00 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA29038;
	Mon, 30 Oct 2000 10:22:24 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UIKbJ21627
	for ngtrans-dist; Mon, 30 Oct 2000 10:20:37 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UIKT321620
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:20:30 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA28517
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:20:29 -0800 (PST)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA25758
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 11:20:28 -0700 (MST)
Received: from df-virus2.platinum.corp.microsoft.com ([172.30.236.33]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Mon, 30 Oct 2000 10:19:40 -0800
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 30 Oct 2000 10:20:46 -0800 (Pacific Standard Time)
Received: from DINO.platinum.corp.microsoft.com ([172.30.236.100]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Mon, 30 Oct 2000 10:20:46 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0429E.1EC7052D"
Subject: RE: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
Date: Mon, 30 Oct 2000 10:20:45 -0800
Message-ID: <5B90AD65A9E8934987DB0C8C0762657420FC6A@DF-BOWWOW.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
Thread-Index: AcBAgGmDb/m/943rTniohma2XBi6QQCGe5Zg
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Dan Lanciani" <ddl@deas.harvard.edu>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 30 Oct 2000 18:20:46.0221 (UTC) FILETIME=[1F350BD0:01C0429E]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Dave Thaler" <dthaler@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C0429E.1EC7052D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dan Lanciani <ddl@harvard.edu> writes:
> |(Some would argue that having packets take the scenic
> |route as you describe is desirable, however.)
>=20
> What is the argument for this?

I've heard two arguments so far:

1) The business motivation for an ISP to deploy a 6to4 relay
   is probably more likely to be that an IPv6-native ISP wants
   to provide good connectivity to its IPv6-native customers=20
   from 6to4 sites.  A relay close to the 6to4 site would
   probably not be the site's ISP or the native destination's
   ISP... it would probably be some third party ISP's relay
   which would be used for transit and may have lousy=20
   connectivity.  Using the relay closest to the native=20
   destination would more closely match the v4 route,
   and quite possibly provide a higher degree of reliability.
   So the "scenic" route can actually be less scenic.

2) For the immediate future where IPv6 packets aren't
   forwarded in hardware by the majority of IPv6 routers,
   it can be faster to forward IPv6-in-IPv4 encapsulated=20
   packets than to forward IPv4 native packets
   (i.e. if the bottleneck is the pps forwarding rate
   and not the BW overhead of encapsulation).  As a result,
   the "scenic" route can actually have higher performance.

-Dave

------_=_NextPart_001_01C0429E.1EC7052D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4576.0">
<TITLE>RE: (ngtrans) An IPv4 anycast address for 6to4&lt;-&gt;6bone =
gateways</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Dan Lanciani &lt;ddl@harvard.edu&gt; writes:</FONT>

<BR><FONT SIZE=3D2>&gt; |(Some would argue that having packets take the =
scenic</FONT>

<BR><FONT SIZE=3D2>&gt; |route as you describe is desirable, =
however.)</FONT>

<BR><FONT SIZE=3D2>&gt; </FONT>

<BR><FONT SIZE=3D2>&gt; What is the argument for this?</FONT>
</P>

<P><FONT SIZE=3D2>I've heard two arguments so far:</FONT>
</P>

<P><FONT SIZE=3D2>1) The business motivation for an ISP to deploy a 6to4 =
relay</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; is probably more likely to be that an =
IPv6-native ISP wants</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; to provide good connectivity to its =
IPv6-native customers </FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; from 6to4 sites.&nbsp; A relay close to =
the 6to4 site would</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; probably not be the site's ISP or the =
native destination's</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; ISP... it would probably be some third =
party ISP's relay</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; which would be used for transit and may =
have lousy </FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; connectivity.&nbsp; Using the relay =
closest to the native </FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; destination would more closely match the =
v4 route,</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; and quite possibly provide a higher =
degree of reliability.</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; So the &quot;scenic&quot; route can =
actually be less scenic.</FONT>
</P>

<P><FONT SIZE=3D2>2) For the immediate future where IPv6 packets =
aren't</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; forwarded in hardware by the majority of =
IPv6 routers,</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; it can be faster to forward IPv6-in-IPv4 =
encapsulated </FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; packets than to forward IPv4 native =
packets</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; (i.e. if the bottleneck is the pps =
forwarding rate</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; and not the BW overhead of =
encapsulation).&nbsp; As a result,</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp; the &quot;scenic&quot; route can =
actually have higher performance.</FONT>
</P>

<P><FONT SIZE=3D2>-Dave</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0429E.1EC7052D--


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:33:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA14471
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:32:58 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA05397;
	Mon, 30 Oct 2000 11:32:28 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA03179;
	Mon, 30 Oct 2000 10:31:34 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UIUb921656
	for ngtrans-dist; Mon, 30 Oct 2000 10:30:37 -0800 (PST)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UIUX321649
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:30:33 -0800 (PST)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e9UITnW24033
	for ngtrans@sunroof.eng.sun.com; Mon, 30 Oct 2000 10:29:49 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9S1IO320151
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 18:18:24 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA14554
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 18:18:21 -0700 (PDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id SAA27915
	for <ngtrans@sunroof.eng.sun.com>; Fri, 27 Oct 2000 18:18:20 -0700 (PDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 27 Oct 2000 18:13:22 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <VX4RY24B>; Fri, 27 Oct 2000 18:11:46 -0700
Message-ID: <B5468CB3A359784A81A0923A24C01CA60BAF65@red-msg-03.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Brad Huntting'" <huntting@hunkular.glarp.com>,
        "f.johan.beisser"
	 <jan@caustic.org>
Cc: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com, cmj@3Com.com
Subject: (ngtrans) RE: An IPv4 anycast address for 6to4<->6bone gateways
Date: Fri, 27 Oct 2000 18:11:26 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Christian Huitema <huitema@microsoft.com>

Actually, what you want is to reserve sufficiently large IP address prefix,
so that it will be accepted without questions by BGP routers -- at least a
/19; a class B would be nice; in fact, if an address rich institution would
donate a class B for that purpose, that would be even better; asking the
IANA to reserve 191.255/16 for that purpose would also look cool. It would
also be useful to dedicate an IPv4 AS number to that purpose.

The IPv6 routers that have a complete access to both IPv6 and IPv4 would
announce the corresponding prefix in their local IGP, as a route to an
external network. The ASes that run such routers and are willing to provide
access to the v6 network would announce a path to the v6 AS and to the 6to4
prefix using BGP; they could easily use the existing structure of peering
and transit agreement to control to whom they are willing to provide
service. The whole v6 network will appear to v4 as a single AS, with lots of
peering points all over the place.

The 6to4 gateways would then send use an address under the 6to4 prefix as a
default route for reaching v6 packets. It will normally reach the service
provided by their ISP, or by the closest ISP according to inter-domain
routing.

This scheme has many advantages. It is simple to implement in 6to4 gateways,
it allows ISP to control to whom they are providing service, it allows for
independent deployments of gateways to the 6Bone and the v6 network by
multiple ISPs, it allows for scaling by deploying a large number of "peering
points."

In the acknowledgement section: I believe that scheme was first proposed by
Randy Bush.

-- Christian Huitema

> -----Original Message-----
> From: Brad Huntting [mailto:huntting@hunkular.glarp.com]
> Sent: Friday, October 27, 2000 2:46 PM
> To: f.johan.beisser
> Cc: ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com; 
> cmj@3Com.com
> Subject: An IPv4 anycast address for 6to4<->6bone gateways
> 
> 
> 
> > http://www.kfu.com/~nsayer/6to4/
> 
> Actually this web page brings up another issue that a freind and
> I were discussing just yesterday.  Anyone who's actually tried to
> use 6to4 (2002::/16) has probably noticed that they need a default
> route to reach the 6bone.  But even assuming you actually find such
> a router it is almost always on the far side of the Internet; which
> means that your packets get to take the scenic route on their way
> to the 6bone.
> 
> One simple solution to this would seem to be to use a well known
> IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> gateways.
> 
> In this way, anyone using 6to4 could reliably use 2002:(a.b.c.d)::1
> (actual IPv6 address syntax will vary) as a default route to the
> 6bone.
> 
> 6to4 gateways would advertise to the their IPv4 peers that they
> have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
> they can advertise a route for 2002::/16.
> 
> Does anyone see a problem with this?  I dont suppose there's already
> a block of IPv4 address space set aside for anycast?
> 
> 
> brad
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------
> 



From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:36:53 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA14906
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:36:48 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA08465;
	Mon, 30 Oct 2000 11:36:19 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA04296;
	Mon, 30 Oct 2000 10:35:07 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UIXuO21700
	for ngtrans-dist; Mon, 30 Oct 2000 10:33:56 -0800 (PST)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UIXp321693
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:33:52 -0800 (PST)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e9UIX8Q24069
	for ngtrans@sunroof.eng.sun.com; Mon, 30 Oct 2000 10:33:08 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9S1gp320191;
	Fri, 27 Oct 2000 18:42:51 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA19037;
	Fri, 27 Oct 2000 18:42:52 -0700 (PDT)
Received: from minuet.das.harvard.edu (minuet.das.harvard.edu [140.247.50.251])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA23383;
	Fri, 27 Oct 2000 18:42:51 -0700 (PDT)
Received: from endor.deas.harvard.edu (endor.harvard.edu [128.103.50.55])
	by minuet.das.harvard.edu (8.9.1/8.9.1) with ESMTP id VAA29470;
	Fri, 27 Oct 2000 21:42:45 -0400 (EDT)
From: Dan Lanciani <ddl@deas.harvard.edu>
Received: (from ddl@localhost)
	by endor.deas.harvard.edu (8.8.8/8.8.8) id VAA14538;
	Fri, 27 Oct 2000 21:42:44 -0400 (EDT)
Date: Fri, 27 Oct 2000 21:42:44 -0400 (EDT)
Message-Id: <200010280142.VAA14538@endor.deas.harvard.edu>
To: dthaler@Exchange.Microsoft.com, huntting@hunkular.glarp.com,
        jan@caustic.org
Subject: RE: (ngtrans) An IPv4 anycast address for 6to4<->6bone gateways
Cc: cmj@3Com.com, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Dan Lanciani <ddl@deas.harvard.edu>

|What would be needed would be to get a prefix short
|enough to pass the prefix length filters in the Internet,
|and then just use 1 of the addresses in that large prefix.

Or for less waste, somebody could just donate a pre-CIDR class-C.  Are
there any ISPs of any significance that don't exempt them from the prefix
length constraints?

|(Some would argue that having packets take the scenic
|route as you describe is desirable, however.)

What is the argument for this?

				Dan Lanciani
				ddl@harvard.edu



From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:40:56 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15441
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:40:53 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA12229;
	Mon, 30 Oct 2000 11:40:40 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA04884;
	Mon, 30 Oct 2000 10:39:19 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UIcOf21731
	for ngtrans-dist; Mon, 30 Oct 2000 10:38:24 -0800 (PST)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UIcI321724
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:38:19 -0800 (PST)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e9UIbZA24110
	for ngtrans@sunroof.eng.sun.com; Mon, 30 Oct 2000 10:37:35 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9SDvS320513;
	Sat, 28 Oct 2000 06:57:29 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA01130;
	Sat, 28 Oct 2000 06:57:28 -0700 (PDT)
Received: from aurora.cs.ucla.edu (Aurora.CS.UCLA.EDU [131.179.96.157])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA05188;
	Sat, 28 Oct 2000 06:57:15 -0700 (PDT)
Received: (from lixia@localhost)
	by aurora.cs.ucla.edu (8.9.3+Sun/UCLACS-5.0) id GAA20174;
	Sat, 28 Oct 2000 06:55:46 -0700 (PDT)
From: Lixia Zhang <lixia@CS.UCLA.EDU>
Message-Id: <200010281355.GAA20174@aurora.cs.ucla.edu>
Subject: (ngtrans) Re: 6over4 for KAME (FreeBSD)
In-Reply-To: <CB7153628BD3724096258CBFD70AA891041DB8@red-msg-04.redmond.corp.microsoft.com>
 from Brian Zill at "Oct 27, 2000 02:40:23 pm"
To: Brian Zill <bzill@microsoft.com>
Date: Sat, 28 Oct 2000 06:55:45 -0700 (PDT)
CC: "'f.johan.beisser'" <jan@caustic.org>,
        Brad Huntting <huntting@hunkular.glarp.com>, snap-users@kame.net,
        freebsd-questions@freebsd.org, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com, yjin@CS.UCLA.EDU
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Lixia Zhang <lixia@CS.UCLA.EDU>
Content-Transfer-Encoding: 7bit

> 6to4 and 6over4, while having unfortunately similar names, are quite
> different things.
> 
> 6to4 is a form of automatic IPv6 tunneling over IPv4.  The IPv4 address of
> the "home" end of the tunnel is encoded into the IPv6 prefix.  See
> draft-ietf-ngtrans-6to4-07.txt.
> 
> 6over4 is another IPv6 over "foo", where "foo" in this case is a
> multicast-enabled IPv4 network, instead of say Ethernet or FDDI.  See RFC
> 2529.
> 
> My recollection is that an implementation of 6over4 for some BSD flavor
> exists, since I recall someone performing some interoperability testing
> between our implementation and that implementation.  UCLA sounds
> familiar.

yes we did an implementation a few years back, I also recall the
interoperability test.
Someone from 3com picked up our code?
Yixin, can you recall more details?

Lixia



> Aren't two interoperating implementations a requirement for Proposed
> Standard? (RFC 2529 is at PS) I'm not aware of any others offhand, but it
> wouldn't surprise me if there were some.
> 
> --Brian
> 
> > -----Original Message-----
> > From: f.johan.beisser [mailto:jan@caustic.org]
> > Sent: Friday, 27 October, 2000 12:32
> > To: Brad Huntting
> > Cc: snap-users@kame.net; freebsd-questions@FreeBSD.ORG;
> > ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com
> > Subject: Re: 6over4 for KAME (FreeBSD)
> > 
> > 
> > 
> > i'm not sure if this is what you mean, but:
> > 
> > http://www.kfu.com/~nsayer/6to4/
> > 
> > also, i think that it is documented on http://www.kame.net.
> > 
> > of course, i oculd very well be talking out of my butt.
> > 
> > -- jan
> > 
> > 
> > 
> > On Fri, 27 Oct 2000, Brad Huntting wrote:
> > 
> > > 
> > > Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
> > > FreeBSD?
> > > 
> > > I have a pointer to a UCLA project called "Virtual Ethernet" by
> > > Quang Nguyen (no email address given), but it was written for the
> > > Inria stack and FreeBSD2.  If there's nothing else available, I
> > > may use this as a guide.
> > > 
> > 
> > 
> > -------/ f. johan beisser /--------------------------------------+
> >   http://caustic.org/~jan                      jan@caustic.org
> >    "Never laugh at someone until you've walked a mile in their
> >          shoes. Then laugh. For you are a mile away, and
> >                       you have their shoes."
> > 
> > 
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                      http://playground.sun.com/ipng
> > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------
> > 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------




From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 13:44:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15819
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 13:44:05 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14732;
	Mon, 30 Oct 2000 11:43:50 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA06428;
	Mon, 30 Oct 2000 10:43:23 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9UIgVJ21766
	for ngtrans-dist; Mon, 30 Oct 2000 10:42:31 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9UIgO321759
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:42:25 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA06499
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:42:24 -0800 (PST)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id KAA18565
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 10:42:24 -0800 (PST)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 30 Oct 2000 10:42:23 -0800 (Pacific Standard Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <V5H15409>; Mon, 30 Oct 2000 10:27:25 -0800
Message-ID: <B5468CB3A359784A81A0923A24C01CA601923571@red-msg-03.redmond.corp.microsoft.com>
From: Christian Huitema <huitema@microsoft.com>
To: "'Bill Manning'" <bmanning@ISI.EDU>, brian@hursley.ibm.com
Cc: huntting@hunkular.glarp.com, jan@caustic.org, ngtrans@sunroof.eng.sun.com,
        cmj@3Com.com
Subject: RE: (ngtrans) Re: An IPv4 anycast address for 6to4<->6bone gatewa
	ys
Date: Mon, 30 Oct 2000 10:27:16 -0800
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Christian Huitema <huitema@microsoft.com>

> From: Bill Manning [mailto:bmanning@ISI.EDU]
> 
> While this would make life a bit easier, I am dubious of such 
> a tactic.
> Tends to leave things in a transition state in perpetuity.  
> 

A condition for easy migration out of the "tunnelling" state is that it be
easy to have connectivity to the "real" IPv6 network; this means that people
trust that opting for a real IPv6 address will not somehow result in lower
performances. So I would say that the anycast proposal actually ensures that
we don't stay in a perpetual transition.

-- Christian Huitema


From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 20:47:58 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20582
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 20:47:57 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA19355;
	Mon, 30 Oct 2000 18:47:46 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA09013;
	Mon, 30 Oct 2000 17:47:25 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) id e9V1kLa22327
	for ngtrans-dist; Mon, 30 Oct 2000 17:46:21 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) with ESMTP id e9V1kCj22312
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 17:46:12 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA29057
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 17:46:13 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id RAA28298
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 17:46:12 -0800 (PST)
Received: from rlfink.lbl.gov (Truckee.lbl.gov) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13qQV9-0007Xl-00; Mon, 30 Oct 2000 17:46:12 -0800
Message-Id: <5.0.0.25.0.20001030145148.00a79ac0@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Mon, 30 Oct 2000 17:45:15 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) draft agenda for San Diego IETF49 - 30Oct2000
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>,
        Bob Fink <fink@es.net>, 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 WG Folk:

Below is a very rough first draft agenda for the ngtrans meeting in San Diego.

Please continue to send your suggested agenda items, or requests to speak 
on specific topics, to the co-chairs (use the cc list above).

For those listed as probabley, but not yet scheduled, please let me hear 
from you or your item will NOT be scheduled.


Thanks,

Bob

========================
IETF49 - San Diego, CA
---
WEDNESDAY, December 13, 2000
0900-1130 Morning Sessions
OPS     ngtrans         Next Generation Transition WG

---
THURSDAY, December 14, 2000
1300-1500 Afternoon Sessions I
OPS     ngtrans         Next Generation Transition WG

===

Agenda

Agenda Bashing

NGtrans Project status - 10 mins, Bob Fink
<http://www.6bone.net/ngtrans/ngtrans_project-status.html>

Guidelines for IPv6 local experiments - 5 Mins, Itojun
<http://www.ietf.org/internet-drafts/draft-itojun-ipv6-local-experiment-01.txt>

Dual Stack deployment using DSTM and 6to4 - 10 mins, George Tsirtsis
<http://www.ietf.org/internet-drafts/draft-tsirtsis-6to4-and-dstm-00.txt>

IPv4 over Mobile IPv6 for Dual Stack nodes - 5 mins, George Tsirtsis
<http://www.ietf.org/internet-drafts/draft-tsirtsis-v4-over-mipv6-00.txt>


---
Probable topics, but not yet scheduled:

6to4 multicast - x mins, Dave Thaler
<http://search.ietf.org/internet-drafts/draft-thaler-ngtrans-6to4-multicast-01.txt>

6to4 scaling issues - x mins, Tony Hain
<http://search.ietf.org/internet-drafts/draft-hain-6to4-scaling-00.txt>

Tunnels end point in DNS - x mins, Alain Durand
<http://search.ietf.org/internet-drafts/draft-durand-ngtrans-tunnel-endpoint-00.txt>

Mime type - x mins, Alain Durand
<http://search.ietf.org/internet-drafts/draft-durand-ngtrans-tunnel-mime-type-00.txt>

v6v4compat - x mins, Fred Templin
<http://search.ietf.org/internet-drafts/draft-templin-ngtrans-v6v4compat-01.txt> 


Hometun - x mins, Francis Dupont
<http://search.ietf.org/internet-drafts/draft-ietf-ngtrans-hometun-00.txt>

Multicast Translator - x mins, Kazuaki Tsuchiya
<http://search.ietf.org/internet-drafts/draft-tsuchiya-mtp-00.txt>

-end







From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 20:47:59 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20581
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 20:47:56 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA19379;
	Mon, 30 Oct 2000 18:47:47 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA09035;
	Mon, 30 Oct 2000 17:47:30 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) id e9V1kY222328
	for ngtrans-dist; Mon, 30 Oct 2000 17:46:34 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) with ESMTP id e9V1kCj22314
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 17:46:12 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA00024
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 17:46:12 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id SAA18126
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 18:46:11 -0700 (MST)
Received: from rlfink.lbl.gov (Truckee.lbl.gov) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13qQV7-0007Xl-00; Mon, 30 Oct 2000 17:46:10 -0800
Message-Id: <5.0.0.25.0.20001030125446.030ddcb8@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Mon, 30 Oct 2000 17:45:52 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) wg actions needing list comments from Pittsburgh meeting
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,

There are numerous open items from the Pittsburgh meeting needing comments 
from the list that are shown below. The notes of this meeting are at:

<http://www.6bone.net/ngtrans/minutes/IETF48-Pittsburgh.html>


Thanks,

Bob


---
6to4 multicast - 10 mins, Dave Thaler
goal is to make multicast work over nbma link
scale : state per receiver
ask list to move to wg draft:
<http://search.ietf.org/internet-drafts/draft-thaler-ngtrans-6to4-multicast-01.txt>

---
6to4 scaling issues - 10 mins, Tony Hain
IPv4 internet looks like single nbma link to 6to4 nodes
ask list to move to wg draft (possibly combined with tunnel endpoint):
<http://search.ietf.org/internet-drafts/draft-hain-6to4-scaling-00.txt>

---
Tunnels end point in DNS - 5 mins, Alain Durand
ask list to move to wg draft (possibly combined with 6to4scale):
<http://search.ietf.org/internet-drafts/draft-durand-ngtrans-tunnel-endpoint-00.txt>

---
Mime type - 5 mins, Alain Durand
ask list to move to wg draft:
<http://search.ietf.org/internet-drafts/draft-durand-ngtrans-tunnel-mime-type-00.txt>

---
v6v4compat - 5 mins, Fred Templin
new format address designed for : 6to4 routers detached from hosts
embed the external router address at 6to4 level & host ipv4 in low 64
are the rest of the draft scenarios being dropped?
what new does this add to auto tunneling?
when to tunnel vs route? take to list for further discussion:
<http://search.ietf.org/internet-drafts/draft-templin-ngtrans-v6v4compat-01.txt>

---
Hometun - 10 mins, Francis Dupont
unsolicited NA with override to fix the tunnel endpoint
security esp header
provides security, but where is the access control?
each packet has its own SA : if it was v6 esp it would work
would cut protocol machinery : take to mail list:
<http://search.ietf.org/internet-drafts/draft-ietf-ngtrans-hometun-00.txt>

---
Multicast Translator - 5 mins, Kazuaki Tsuchiya
take to list for further discussion : chairs to discuss experimental vs. std
<http://search.ietf.org/internet-drafts/draft-tsuchiya-mtp-00.txt>

---
end







From owner-ngtrans@sunroof.eng.sun.com  Mon Oct 30 21:18:33 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA28818
	for <ngtrans-archive@odin.ietf.org>; Mon, 30 Oct 2000 21:18:31 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA08668;
	Mon, 30 Oct 2000 19:18:20 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA08120;
	Mon, 30 Oct 2000 18:17:58 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) id e9V2GhL22385
	for ngtrans-dist; Mon, 30 Oct 2000 18:16:43 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) with ESMTP id e9V2GZj22378
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 18:16:36 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA14352
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 18:16:35 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id SAA15858
	for <ngtrans@sunroof.eng.sun.com>; Mon, 30 Oct 2000 18:16:34 -0800 (PST)
Received: from rlfink.lbl.gov (Truckee.lbl.gov) [131.243.136.210] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13qQyX-0007h3-00; Mon, 30 Oct 2000 18:16:33 -0800
Message-Id: <5.0.0.25.0.20001030181353.00a8c068@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Mon, 30 Oct 2000 18:16:29 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) important meeting dates -  IETF49
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,

Here are the important meeting dates for IETF49.

Please note the 17 November initial document submission cutoff date, and 
the 24 November final submission cutoff date.


Thanks,

Bob

-----------------------
IMPORTANT MEETING DATES
October 2 - Working Group and BOF scheduling begins
October 9 - Registration begins
November 17 - Working Group and BOF scheduling closes at 17:00 ET
November 17 - Internet Draft Cut-off for inital document (-00) submissions
November 24 - Internet-Draft final submission cutoff date at 17:00 ET
December 1 - Pre-Registration and Pre-payment cutoff date at 12:00 ET
December 4 - Working Group agendas due date by 17:00 ET
December 6 - Registration Cancellation cutoff date by 17:00 ET
December 10 - 15, 2000 - 49th IETF Meeting
January 12 - Proceedings submission cutoff date by 17:00 ET
All times are in US Eastern Time




From owner-ngtrans@sunroof.eng.sun.com  Tue Oct 31 13:58:27 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04413
	for <ngtrans-archive@odin.ietf.org>; Tue, 31 Oct 2000 13:58:27 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA03902;
	Tue, 31 Oct 2000 11:58:11 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA04519;
	Tue, 31 Oct 2000 08:46:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) id e9VGjFd22774
	for ngtrans-dist; Tue, 31 Oct 2000 08:45:15 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) with ESMTP id e9VGj8j22767
	for <ngtrans@sunroof.eng.sun.com>; Tue, 31 Oct 2000 08:45:08 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA00967
	for <ngtrans@sunroof.eng.sun.com>; Tue, 31 Oct 2000 08:45:08 -0800 (PST)
Received: from mail-gw1.hursley.ibm.com (mail-gw1.hursley.ibm.com [194.196.110.15])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA07282
	for <ngtrans@sunroof.eng.sun.com>; Tue, 31 Oct 2000 08:45:07 -0800 (PST)
Received: from sp15en17.hursley.ibm.com (sp15at17.hursley.ibm.com [9.20.45.103])
	by mail-gw1.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id QAA16908;
	Tue, 31 Oct 2000 16:45:02 GMT
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42])
	by sp15en17.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id QAA21166;
	Tue, 31 Oct 2000 16:44:54 GMT
Message-ID: <39FEEE56.76059CBF@hursley.ibm.com>
Date: Tue, 31 Oct 2000 10:07:50 -0600
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: Christian Huitema <huitema@microsoft.com>
CC: "'Brad Huntting'" <huntting@hunkular.glarp.com>,
        "f.johan.beisser" <jan@caustic.org>, ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Re: An IPv4 anycast address for 6to4<->6bone gateways
References: <B5468CB3A359784A81A0923A24C01CA60192356E@red-msg-03.redmond.corp.microsoft.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

It needs to be a separate document; the base document is in the RFC Editor queue.

  Brian

Christian Huitema wrote:
> 
> That, or you incorporate it in the 6to4 draft. What do you prefer?
> 
> > -----Original Message-----
> > From: Brian E Carpenter [mailto:brian@hursley.ibm.com]
> > Sent: Monday, October 30, 2000 8:29 AM
> > To: Christian Huitema
> > Cc: 'Brad Huntting'; f.johan.beisser; ngtrans@sunroof.eng.sun.com;
> > cmj@3Com.com
> > Subject: Re: An IPv4 anycast address for 6to4<->6bone gateways
> >
> >
> > Personally, I'd prefer to re-allocate Net 10 for this :-)
> >
> > Yes, this is an interesting approach. Anybody want to write a draft?
> >
> > N.B. 6to4 is an NGTRANS work item. I have removed IPNGWG from
> > the copies.
> >
> >    Brian
> >
> > Christian Huitema wrote:
> > >
> > > Actually, what you want is to reserve sufficiently large IP
> > address prefix,
> > > so that it will be accepted without questions by BGP
> > routers -- at least a
> > > /19; a class B would be nice; in fact, if an address rich
> > institution would
> > > donate a class B for that purpose, that would be even
> > better; asking the
> > > IANA to reserve 191.255/16 for that purpose would also look
> > cool. It would
> > > also be useful to dedicate an IPv4 AS number to that purpose.
> > >
> > > The IPv6 routers that have a complete access to both IPv6
> > and IPv4 would
> > > announce the corresponding prefix in their local IGP, as a
> > route to an
> > > external network. The ASes that run such routers and are
> > willing to provide
> > > access to the v6 network would announce a path to the v6 AS
> > and to the 6to4
> > > prefix using BGP; they could easily use the existing
> > structure of peering
> > > and transit agreement to control to whom they are willing to provide
> > > service. The whole v6 network will appear to v4 as a single
> > AS, with lots of
> > > peering points all over the place.
> > >
> > > The 6to4 gateways would then send use an address under the
> > 6to4 prefix as a
> > > default route for reaching v6 packets. It will normally
> > reach the service
> > > provided by their ISP, or by the closest ISP according to
> > inter-domain
> > > routing.
> > >
> > > This scheme has many advantages. It is simple to implement
> > in 6to4 gateways,
> > > it allows ISP to control to whom they are providing
> > service, it allows for
> > > independent deployments of gateways to the 6Bone and the v6
> > network by
> > > multiple ISPs, it allows for scaling by deploying a large
> > number of "peering
> > > points."
> > >
> > > In the acknowledgement section: I believe that scheme was
> > first proposed by
> > > Randy Bush.
> > >
> > > -- Christian Huitema
> > >
> > > > -----Original Message-----
> > > > From: Brad Huntting [mailto:huntting@hunkular.glarp.com]
> > > > Sent: Friday, October 27, 2000 2:46 PM
> > > > To: f.johan.beisser
> > > > Cc: ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com;
> > > > cmj@3Com.com
> > > > Subject: An IPv4 anycast address for 6to4<->6bone gateways
> > > >
> > > >
> > > >
> > > > > http://www.kfu.com/~nsayer/6to4/
> > > >
> > > > Actually this web page brings up another issue that a freind and
> > > > I were discussing just yesterday.  Anyone who's actually tried to
> > > > use 6to4 (2002::/16) has probably noticed that they need a default
> > > > route to reach the 6bone.  But even assuming you actually
> > find such
> > > > a router it is almost always on the far side of the
> > Internet; which
> > > > means that your packets get to take the scenic route on their way
> > > > to the 6bone.
> > > >
> > > > One simple solution to this would seem to be to use a well known
> > > > IPv4 "anycast" address (call it "a.b.c.d" for now) for all 6to4
> > > > gateways.
> > > >
> > > > In this way, anyone using 6to4 could reliably use
> > 2002:(a.b.c.d)::1
> > > > (actual IPv6 address syntax will vary) as a default route to the
> > > > 6bone.
> > > >
> > > > 6to4 gateways would advertise to the their IPv4 peers that they
> > > > have a route for "a.b.c.d".  And for their IPv6 peers (the 6bone)
> > > > they can advertise a route for 2002::/16.
> > > >
> > > > Does anyone see a problem with this?  I dont suppose
> > there's already
> > > > a block of IPv4 address space set aside for anycast?
> > > >
> > > >
> > > > brad
> > > >
> > --------------------------------------------------------------------
> > > > IETF IPng Working Group Mailing List
> > > > IPng Home Page:
> http://playground.sun.com/ipng
> > > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > > --------------------------------------------------------------------
> > >
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                      http://playground.sun.com/ipng
> > FTP archive:                      ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------
> 
> --
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Brian E Carpenter
> Program Director, Internet Standards & Technology, IBM
> On assignment for IBM at http://www.iCAIR.org
> Board Chairman, Internet Society http://www.isoc.org
> Non-IBM email: brian@icair.org




From owner-ngtrans@sunroof.eng.sun.com  Tue Oct 31 14:23:32 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12630
	for <ngtrans-archive@odin.ietf.org>; Tue, 31 Oct 2000 14:23:31 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA22690;
	Tue, 31 Oct 2000 12:23:10 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA22236;
	Tue, 31 Oct 2000 10:05:07 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) id e9VI42722876
	for ngtrans-dist; Tue, 31 Oct 2000 10:04:02 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.2.Beta0+Sun/8.11.2.Beta0) with ESMTP id e9VI1uj22861;
	Tue, 31 Oct 2000 10:01:56 -0800 (PST)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA12474;
	Tue, 31 Oct 2000 10:01:54 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA19866;
	Tue, 31 Oct 2000 10:01:53 -0800 (PST)
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id JAA15608;
	Tue, 31 Oct 2000 09:59:53 -0800 (PST)
Received: from chicago.nsd.3com.com (chicago.nsd.3com.com [129.213.157.11])
	by new-york.3com.com (8.8.8/8.8.8) with ESMTP id JAA05038;
	Tue, 31 Oct 2000 09:59:53 -0800 (PST)
Received: from cyndi (vpn-243.nsd.3com.com [129.213.205.243])
	by chicago.nsd.3com.com (8.8.8/8.8.8) with SMTP id JAA17414;
	Tue, 31 Oct 2000 09:59:43 -0800 (PST)
Message-Id: <3.0.6.32.20001031095834.01960af0@mailhost.ewd.3com.com>
X-Sender: cmj@mailhost.ewd.3com.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 31 Oct 2000 09:58:34 -0800
To: Lixia Zhang <lixia@CS.UCLA.EDU>, Brian Zill <bzill@microsoft.com>
From: Cyndi Jung <cmj@3Com.com>
Subject: Re: (ngtrans) Re: 6over4 for KAME (FreeBSD)
Cc: "'f.johan.beisser'" <jan@caustic.org>,
        Brad Huntting <huntting@hunkular.glarp.com>, snap-users@kame.net,
        freebsd-questions@freebsd.org, ngtrans@sunroof.eng.sun.com,
        ipng@sunroof.eng.sun.com, yjin@CS.UCLA.EDU
In-Reply-To: <200010281355.GAA20174@aurora.cs.ucla.edu>
References: <CB7153628BD3724096258CBFD70AA891041DB8@red-msg-04.redmond.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Cyndi Jung <cmj@3Com.com>


We did some interoperability testing between the UCLA code and
the Microsoft code, but we never picked up the code, and in fact
had toruble putting the UCLA software together until Yixin somehow 
put a kernel together that would work for our test.  It was a proof 
of concept, but it didn't go beyond that.  

The UCLA code was built on the Francis' stack from Inria, and I don't know
how different that is from the KAME stack. Francis had the 6over4 from UCLA
in his code when we went to Tokyo last year for the interim IPng
meeting and TAHI interoperability test - I helped him do a little
interoperability test there with Richard Draves from Microsoft, by
giving them a multi-hop IPv4 network with multicast service - it was no 
surprise to any of us that it worked, but it was nice to see.

So, Francis - you are the last person seen (by me) with a working 6over4 on
freeBSD!

Cyndi

At 06:55 AM 10/28/00 -0700, Lixia Zhang wrote:
>> 6to4 and 6over4, while having unfortunately similar names, are quite
>> different things.
>> 
>> 6to4 is a form of automatic IPv6 tunneling over IPv4.  The IPv4 address of
>> the "home" end of the tunnel is encoded into the IPv6 prefix.  See
>> draft-ietf-ngtrans-6to4-07.txt.
>> 
>> 6over4 is another IPv6 over "foo", where "foo" in this case is a
>> multicast-enabled IPv4 network, instead of say Ethernet or FDDI.  See RFC
>> 2529.
>> 
>> My recollection is that an implementation of 6over4 for some BSD flavor
>> exists, since I recall someone performing some interoperability testing
>> between our implementation and that implementation.  UCLA sounds
>> familiar.
>
>yes we did an implementation a few years back, I also recall the
>interoperability test.
>Someone from 3com picked up our code?
>Yixin, can you recall more details?
>
>Lixia
>
>
>
>> Aren't two interoperating implementations a requirement for Proposed
>> Standard? (RFC 2529 is at PS) I'm not aware of any others offhand, but it
>> wouldn't surprise me if there were some.
>> 
>> --Brian
>> 
>> > -----Original Message-----
>> > From: f.johan.beisser [mailto:jan@caustic.org]
>> > Sent: Friday, 27 October, 2000 12:32
>> > To: Brad Huntting
>> > Cc: snap-users@kame.net; freebsd-questions@FreeBSD.ORG;
>> > ngtrans@sunroof.eng.sun.com; ipng@sunroof.eng.sun.com
>> > Subject: Re: 6over4 for KAME (FreeBSD)
>> > 
>> > 
>> > 
>> > i'm not sure if this is what you mean, but:
>> > 
>> > http://www.kfu.com/~nsayer/6to4/
>> > 
>> > also, i think that it is documented on http://www.kame.net.
>> > 
>> > of course, i oculd very well be talking out of my butt.
>> > 
>> > -- jan
>> > 
>> > 
>> > 
>> > On Fri, 27 Oct 2000, Brad Huntting wrote:
>> > 
>> > > 
>> > > Has anyone started writing a 6over4 (rfc2529) driver for KAME and/or
>> > > FreeBSD?
>> > > 
>> > > I have a pointer to a UCLA project called "Virtual Ethernet" by
>> > > Quang Nguyen (no email address given), but it was written for the
>> > > Inria stack and FreeBSD2.  If there's nothing else available, I
>> > > may use this as a guide.
>> > > 
>> > 
>> > 
>> > -------/ f. johan beisser /--------------------------------------+
>> >   http://caustic.org/~jan                      jan@caustic.org
>> >    "Never laugh at someone until you've walked a mile in their
>> >          shoes. Then laugh. For you are a mile away, and
>> >                       you have their shoes."
>> > 
>> > 
>> > --------------------------------------------------------------------
>> > IETF IPng Working Group Mailing List
>> > IPng Home Page:                      http://playground.sun.com/ipng
>> > FTP archive:                      ftp://playground.sun.com/pub/ipng
>> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
>> > --------------------------------------------------------------------
>> > 
>> --------------------------------------------------------------------
>> IETF IPng Working Group Mailing List
>> IPng Home Page:                      http://playground.sun.com/ipng
>> FTP archive:                      ftp://playground.sun.com/pub/ipng
>> Direct all administrative requests to majordomo@sunroof.eng.sun.com
>> --------------------------------------------------------------------
>
>
>



