From owner-ngtrans@sunroof.eng.sun.com  Fri Sep  1 19:05:22 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22484
	for <ngtrans-archive@odin.ietf.org>; Fri, 1 Sep 2000 19:05:21 -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 RAA24567;
	Fri, 1 Sep 2000 17:05:04 -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 QAA00665;
	Fri, 1 Sep 2000 16:03:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e81N2Nl24721
	for ngtrans-dist; Fri, 1 Sep 2000 16:02:23 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e81N2FH24714;
	Fri, 1 Sep 2000 16:02:15 -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 QAA09358;
	Fri, 1 Sep 2000 16:02:15 -0700 (PDT)
Received: from ups.cisco.com (ups.cisco.com [171.69.18.21])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA13778;
	Fri, 1 Sep 2000 16:02:15 -0700 (PDT)
Received: from [10.19.130.190] (deering-office-pb.cisco.com [171.70.84.51])
	by ups.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA01889;
	Fri, 1 Sep 2000 16:02:14 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@ups
Message-Id: <v04220815b5d5e2f8f2e8@[10.19.130.190]>
Date: Fri, 1 Sep 2000 16:02:26 -0700
To: ipng@sunroof.eng.sun.com
From: Steve Deering <deering@cisco.com>
Subject: (ngtrans) Fwd: IAB/IESG Recommendations on IPv6 Address Delegation
Cc: ngtrans@sunroof.eng.sun.com, Bob Hinden <hinden@iprg.nokia.com>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

Appended below is the message that was sent today to the RIRs from the
IAB and IESG, regarding IPv6 address allocation policy.  It contains most
of the material that was in the draft I forwarded here on Sunday, but
reorganized into a more coherent document.

Steve

--------
>Date: Fri, 01 Sep 2000 12:40:48 -0700
>To: lir-wg@ripe.net (RIPE), policy@arin.net (ARIN),
>        apnic-talk@apnic.net (APNIC)
>From: Fred Baker <chair@ietf.org>
>Subject: IAB/IESG Recommendations on IPv6 Address Delegation
>Cc: ipv6-directorate@sunroof.eng.sun.com, iesg@ietf.org, iab@ISI.EDU,
>        ipv6-wg@ripe.net (RIPE), sig-ipv6@lists.apnic.net (APNIC)
>
>Folks:
>
>The RIR community asked the IETF community for advice regarding the
>assignment of IPv6 prefixes to service providers and edge networks, both
>with a view to topological address assignment and to multihomed networks.
>The IPv6 Directorate prepared a statement, which the IESG and IAB have
>reviewed and approved. This is attached.
>
>I trust that this answers the questions you asked, and serves as a basis for
>IPv6 deployment in the near term. If you have questions or issues concerning
>it, I would suggest that you address them to the IPv6 Directorate copying
>the IESG and IAB.
>
>We intend to publish an Informational RFC in the near future documenting the
>contents of this note.
>
>Fred Baker
>
>-----------------------------------------------------------------------
>
>	IAB/IESG Recommendations on IPv6 Address Allocations
>			   September 1, 2000
>
>Introduction
>
>During a discussion between IETF and RIR experts at the Adelaide IETF,
>a suggestion was made that it might be appropriate to allocate /56
>prefixes instead of /48 for homes and small businesses.  However,
>subsequent analysis has revealed significant advantages in using /48
>uniformly.  This note is an update following further discussions at
>the Pittsburgh IETF.
>
>This document was developed by the IPv6 Directorate, IAB and IESG, and
>is a recommendation from the IAB and IESG to the RIRs.
>
>Background
>
>The technical principles that apply to address allocation seek to
>balance healthy conservation practices and wisdom with a certain ease
>of access.  On the one hand, when managing the use of a potentially
>limited resource, one must conserve wisely to prevent exhaustion
>within an expected lifetime.  On the other hand, the IPv6 address
>space is in no sense as precious a resource as the IPv4 address space,
>and unwarranted conservatism acts as a disincentive in a marketplace
>already dampened by other factors.  So from a market development
>perspective, we would like to see it be very easy for a user or an ISP
>to obtain as many IPv6 addresses as they really need without a
>prospect of immediate renumbering or of scaling inefficiencies.
>
>The IETF makes no comment on business issues or relationships.
>However, in general, we observe that technical delegation policy can
>have strong business impacts.  A strong requirement of the address
>delegation plan is that it not be predicated on or unduly bias
>business relationships or models.
>
>The IPv6 address, as currently defined, consists of 64 bits of
>"network number" and 64 bits of "host number".  The technical reasons
>for this are several.  The requirements for IPv6 agreed to in 1993
>included a plan to be able to address approximately 2^40 networks and
>2^50 hosts; the 64/64 split effectively accomplishes this.  Procedures
>used in host address assignment, such as the router advertisement of a
>network's prefix to hosts [RFC 2462], which in turn place a locally
>unique number in the host portion, depend on this split.  Examples of
>obvious choices of host number (IEEE Mac Address, E.164 number, E.214
>IMSI, etc) suggest that no assumption should be made that bits may be
>stolen from that range for subnet numbering; current generation MAC
>layers and E.164 numbers specify up to 64 bit objects.  Therefore,
>subnet numbers must be assumed to come from the network part.  This is
>not to preclude routing protocols such as IS-IS level 1 (intra-area)
>routing, which routes individual host addresses, but says that it may
>not be depended upon in the world outside that zone.
>
>The IETF has also gone to a great deal of effort to minimize the
>impacts of network renumbering.  None-the-less, renumbering of IPv6
>networks is neither invisible nor completely painless.  Therefore,
>renumbering should be considered an acceptable event, but to be
>avoided if reasonably avoidable.
>
>The IETF's IPNG working group has recommended that the address block
>given to a single edge network which may be recursively subnetted be a
>
>48 bit prefix.  This gives each such network 2^16 subnet numbers to
>use in routing, and a very large number of unique host numbers within
>each network.  This is deemed to be large enough for most enterprises,
>and to leave plenty of room for delegation of address blocks to
>aggregating entities.
>
>It is not obvious, however, that all edge networks are likely to be
>recursively subnetted; an individual PC in a home, or a single cell in
>a mobile telephone network, for example, may or may not be further
>subnetted (depending whether they are acting as, e.g., gateways to
>personal, home, or vehicular networks).  When a network number is
>delegated to a place that will not require subnetting, therefore, it
>might be acceptable for an ISP to give a single 64 bit prefix -
>perhaps shared among the dial-in connections to the same ISP router.
>However this decision may be taken in the knowledge that there is
>objectively no shortage of /48s, and the expectation that personal,
>home and vehicle networks will become the norm.  Indeed, it is widely
>expected that all IPv6 subscribers, whether domestic (homes), mobile
>(vehicles or individuals), or enterprises of any size, will eventually
>possess multiple always-on hosts, at least one subnet with the
>potential for additional subnetting, and therefore some internal
>routing capability.  Note that in the mobile environment, the device
>connecting a mobile site to the network may in fact be a third
>generation cellular telephone.  In other words the subscriber
>allocation unit is not always a host; it is always potentially a site.
>
>Address Delegation Recommendations
>
>The RIR communities, with the IAB, have determined that reasonable
>address prefixes delegated to service providers for initial
>allocations should be on the order of 29 to 35 bits in length, giving
>individual delegations support for 2^13 (8K) to 2^19 (512K) subscriber
>networks.  Allocations are to be given in a manner such that an
>initial prefix may be subsumed by subsequent larger allocations
>without forcing existing subscriber networks to renumber.  We concur
>that this meets the technical requirement for manageable and scalable
>backbone routing while simultaneously allowing for managed growth of
>individual delegations.
>
>The same type of rule could be used in the allocation of addresses in
>edge networks; if there is doubt whether an edge network will in turn
>be subnetted, the edge network might be encouraged to allocate the
>first 64 bit prefix out of a block of 8..256, preserving room for
>growth of that allocation without renumbering up to a point.  However,
>for the reasons described below, we recommend use of a fixed boundary
>at /48 for all subscribers except the very largest (who could receive
>multiple /48's), and those clearly transient or otherwise have no
>interest in subnetting (who could receive a /64).  Note that there
>seems to be little benefit in not giving a /48 if future growth is
>anticipated.  In the following, we give the arguments for a uniform
>use of /48 and then demonstrate that it is entirely compatible with
>responsible stewardship of the total IPv6 address space.
>
>The arguments for the fixed boundary are:
>
> - only by having an ISP-independent boundary can we guarantee that a
>   change of ISP will not require a costly internal restructuring or
>   consolidation of subnets.
>
> - to enable straightforward site renumbering, i.e., when a site
>   renumbers from one prefix to another, the whole process, including
>   parallel running of the two prefixes, would be greatly complicated
>   if the prefixes had different lengths (depending of course on the
>   size and complexity of the site).
>
> - there are various possible approaches to multihoming for IPv6
>   sites, including the techniques already used for IPv4 multihoming.
>   The main open issue is finding solutions that scale massively
>   without unduly damaging route aggregation and/or optimal route
>   selection.  Much more work remains to be done in this area, but it
>   seems likely that several approaches will be deployed in practice,
>   each with their own advantages and disadvantages.  Some (but not
>   all) will work better with a fixed prefix boundary.  (Multihoming
>   is discussed in more detail below.)
>
> - to allow easy growth of the subscribers' networks -- no need to
>   keep going back to ISPs for more space (except for that relatively
>   small number of subscribers for which a /48 is not enough).
>
> - remove the burden from the ISPs and registries of judging sites'
>   needs for address space, unless the site requests more space than a
>   /48, with several advantages:
>
>   - ISPs no longer need to ask for details of their customers'
>     network architecture and growth plans
>   - ISPs and registries no longer have to judge rates of address
>     consumption by customer type
>   - registry operations will be made more efficient by reducing the
>     need for evaluations and judgements
>   - address space will no longer be a precious resource for
>     customers, removing the major incentive for subscribers to
>     install v6/v6 NATs, which would defeat the ability of IPv6 to
>     restore address transparency.
>
> - to allow the site to maintain a single reverse-DNS zone covering
>   all prefixes.
>
>   - If and only if a site can use the same subnetting structure under
>     each of its prefixes, then it can use the same zone file for the
>     address-to-name mapping of all of them.  And, using the
>     conventions of RFC 2874, it can roll the reverse mapping data
>     into the "forward" (name-keyed) zone.
>
>Specific advantages of the fixed boundary being at /48 include
>
> - to leave open the technical option of retro-fitting the GSE
>   (Global, Site and End-System Designator, a.k.a "8+8") proposal for
>   separating locators and identifiers, which assumes a fixed boundary
>   between global and site addressing at /48.  Although the GSE
>   technique was deferred a couple of years ago, it still has strong
>   proponents.  Also, the IRTF Namespace Research Group is actively
>   looking into topics closely related to GSE.  It is still possible
>   that GSE or a derivative of GSE will be used with IPv6 in the
>   future.
>
> - since the site local prefix is fec0::/48, global site prefixes of
>   /48 will allow sites to easily maintain a simple 1 to 1 mapping
>   between the global topology and the site local topology in the SLA
>   field.
>
> - similarly, if the 6to4 proposal is standardized, migration from a
>   6to4 prefix, which is /48 by construction, to a native IPv6 prefix
>   will be simplified if the native prefix is /48.
>
>Note that none of these reasons imply an expectation that homes,
>vehicles, etc. will intrinsically require 16 bits of subnet space.
>
>Conservation of Address Space
>
>The question naturally arises whether giving a /48 to every subscriber
>represents a profligate waste of address space.  Objective analysis
>shows that this is not the case.  A /48 prefix under the Aggregatable
>Global Unicast Address (TLA) format prefix actually contains 45
>variable bits, i.e., the number of available prefixes is 2**45 or about
>35 trillion (35,184,372,088,832).  If we take the limiting case of
>assigning one prefix per human, then the utilization of the TLA space
>appears to be limited to approximately 0.03% on reasonable
>assumptions.
>
>More precisely,
>
> - RFC 1715 defines an "H ratio" based on experience in address space
>   assignment in various networks.  Applied to a 45 bit address space,
>   and projecting a world population of 10.7 billion by 2050 (see
>   http://www.popin.org/pop1998/), the required assignment efficiency
>   is log_10(1.07*10^10) / 45 = 0.22.  This is less than the
>   efficiencies of telephone numbers and DECnetIV or IPv4 addresses
>   shown in RFC 1715, i.e., gives no grounds for concern.
>
> - We are highly confident in the validity of this analysis, based on
>   experience with IPv4 and several other address spaces, and on
>   extremely ambitious scaling goals for the Internet amounting to an
>   80 bit address space *per person*.  Even so, being acutely aware of
>   the history of under-estimating demand, we have reserved more than
>   85% of the address space (i.e., the bulk of the space not under the
>   Aggregatable Global Unicast Address (TLA) format prefix).
>   Therefore, if the analysis does one day turn out to be wrong, our
>   successors will still have the option of imposing much more
>   restrictive allocation policies on the remaining 85%.
>
> - For transient use by non-routing hosts (e.g., for stand-alone
>   dial-up users who prefer transient addresses for privacy reasons),
>   a prefix of /64 might be OK.  But a subscriber who wants "static"
>   IPv6 address space, or who has or plans to have multiple subnets,
>   ought to be provided with a /48, for the reasons given above, even
>   if it is a transiently provided /48.
>
>To summarize, we argue that although careful stewardship of IPv6
>address space is essential, this is completely compatible with the
>convenience and simplicity of a uniform prefix size for IPv6 sites of
>any size.  The numbers are such that there seems to be no objective
>risk of running out of space, giving an unfair amount of space to
>early customers, or of getting back into the over-constrained IPv4
>situation where address conservation and route aggregation damage each
>other.
>
>Multihoming Issues
>
>In the realm of multi-homed networks, the techniques used in IPv4 can
>all be applied, but they have known scaling problems.  Specifically,
>if the same prefix is advertised by multiple ISPs, the routing tables
>will grow as a function of the number of multihomed sites.  To go
>beyond this for IPv6, we only have initial proposals on the table at
>this time, and active work is under way in the IETF IPNG working
>group.  Until existing or new proposals become more fully developed,
>existing techniques known to work in IPv4 will continue to be used in
>IPv6.
>
>Key characteristics of an ideal multi-homing proposal include (at
>minimum) that it provides routing connectivity to any multi-homed
>network globally, conserves address space, produces high quality
>routes at least as well as the single-homed host case previously
>discussed via any of the network's providers, enables a multi-homed
>network to connect to multiple ISPs, does not inherently bias routing
>to use any proper subset of those networks, does not unduly damage
>route aggregation, and scales to very large numbers of multi-homed
>networks.
>
>One class of solution being considered amounts to permanent parallel
>running of two (or more) prefixes per site.  In the absence of a fixed
>prefix boundary, such a site might be required to have multiple
>different internal subnet numbering strategies, (one for each prefix
>length) or, if it only wanted one, be forced to use the most
>restrictive one as defined by the longest prefix it received from any
>of its ISPs.  In this approach, a multi-homed network would have an
>address block from each of its upstream providers.  Each host would
>either have exactly one address picked from the set of upstream
>providers, or one address per host from each of the upstream
>providers.  The first case is essentially a variant on RFC 2260, with
>known scaling limits.
>
>In the second case (multiple addresses per host), if two multi-homed
>networks communicate, having respectively m and n upstream providers,
>then the one initiating the connection will select one address pair
>from the n*m potential address pairs to connect from and to, and in so
>doing will select the providers, and therefore the applicable route,
>for the life of the connection.  Given that each path will have a
>different ambient bit rate, loss rate, and delay, if neither host is
>in possession of any routing or metric information, the initiating
>host has only a 1/(m*n) probability of selecting the optimal address
>pair.  Work on better-than-random address selection is in progress in
>the IETF, but is incomplete.
>
>An existence proof exists in the existing IPv4 Internet that a network
>whose address is distinct from and globally advertised to all upstream
>providers permits the routing network to select a reasonably good path
>within the applicable policy.  Present-day routing policies are not
>QoS policies but reachability policies, which means that they will not
>necessarily select the optimal delay, bit rate, or loss rate, but the
>route will be the best within the metrics that are indeed in use.  One
>may therefore conclude that this would work correctly for IPv6
>networks as well, apart from scaling issues.
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Fred Baker	| 519 Lado Drive
>IETF Chair	| Santa Barbara California 93111
>www.ietf.org	| Desk:   +1-408-526-4257
>		| Mobile: +1-805-886-3873
>		| FAX:	  +1-413-473-2403



From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 09:52:35 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02176
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 09:52:34 -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 HAA20756;
	Tue, 5 Sep 2000 07:52: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 GAA02828;
	Tue, 5 Sep 2000 06:52:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85DpCS26176
	for ngtrans-dist; Tue, 5 Sep 2000 06:51:12 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85Dp5H26169
	for <ngtrans@sunroof.eng.sun.com>; Tue, 5 Sep 2000 06:51:05 -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 GAA17748
	for <ngtrans@sunroof.eng.sun.com>; Tue, 5 Sep 2000 06:51:05 -0700 (PDT)
Received: from dillema.net (server.pasta.cs.UiT.No [129.242.16.119])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA04877
	for <ngtrans@sunroof.eng.sun.com>; Tue, 5 Sep 2000 06:51:04 -0700 (PDT)
Received: (from dillema@localhost)
	by dillema.net (8.9.3+3.2W/8.8.8) id PAA01874
	for ngtrans@sunroof.eng.sun.com; Tue, 5 Sep 2000 15:50:54 +0200 (CEST)
Date: Tue, 5 Sep 2000 15:50:53 +0200
From: Feico Dillema <feico@pasta.cs.uit.no>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) draft-moore-6to4-dns-00.txt
Message-ID: <20000905155053.F857@dillema.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.2i
X-Operating-System: NetBSD drifter.dillema.net 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (DRIFTER-NOCB)
X-URL: http://www.dillema.net/
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Feico Dillema <feico@pasta.cs.uit.no>

Hi,

I implemented (well, almost) support for reverse address lookup of
6to4 addresses in my DNS proxy totd, according section 3.3 of
draft-moore-6to4-dns-00.txt. I'd like to do some testing of it, and
need to know some DNS servers that serve 6to4 PTR records for that and
the zone(s) they serve. Could any of you provide me with some? I do
not have 6to4 deployed around here for testing this.

Feico Dillema.



From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 11:15:27 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04511
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 11:15:26 -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 JAA00411;
	Tue, 5 Sep 2000 09:15:22 -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 GAA09382;
	Tue, 5 Sep 2000 06:02:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85D1c926128
	for ngtrans-dist; Tue, 5 Sep 2000 06:01:38 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85D1WH26121
	for <ngtrans@sunroof.Eng.Sun.COM>; Tue, 5 Sep 2000 06:01:32 -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 GAA18403
	for <ngtrans@sunroof.Eng.Sun.COM>; Tue, 5 Sep 2000 06:01:32 -0700 (PDT)
Received: from mail-gw1.hursley.ibm.com (mail-gw1.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA00733
	for <ngtrans@sunroof.Eng.Sun.COM>; Tue, 5 Sep 2000 07:01:31 -0600 (MDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21])
	by mail-gw1.hursley.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id OAA10038;
	Tue, 5 Sep 2000 14:00:49 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id OAA30138; Tue, 5 Sep 2000 14:00:36 +0100 (BST)
Message-ID: <39B4EEB1.2C4431AB@hursley.ibm.com>
Date: Tue, 05 Sep 2000 08:01:37 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: NGTRANS List <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) draft-ietf-ngtrans-6to4-07.txt is coming
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

NGTRANS,

draft-ietf-ngtrans-6to4-07.txt will be posted shortly. This is an update following
IESG comments. Here is the change log for this version, with the major changes
marked by **:

Changes from 06 to 07 version after IESG review:

- deleted "without Explicit Tunnels" from title to avoid confusion
  with RFC 2529
**updated applicability and scaling information in the Introduction,
  with corresponding tweaks to the Abstract, emphasising interim aspect.
- strengthened text on filtering long 6to4 prefixes in section 5.2
- added "work in progress" references to multicast and scaling drafts
- noted that dynamic IPv4 addresses lead to dynamic 6to4 prefixes
**clarified terminology of sending rule
**moved sending and decapsulation rules into a separate section
- tweaked wording on multihoming
- clarified wording on multiple NATs
- clarified that default routes point to addresses, not prefixes, of relay routers
- typographical errors corrected
- removed change list
- inserted copyright and IPR notices

For those unwilling to wait, a temporary copy is at:

http://www.adtech.icair.org/brian/draft-ietf-ngtrans-6to4-07.txt

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 11:40:03 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05625
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 11:40:03 -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 JAA13726;
	Tue, 5 Sep 2000 09:39:59 -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 IAA23648;
	Tue, 5 Sep 2000 08:24:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85FNWw26305
	for ngtrans-dist; Tue, 5 Sep 2000 08:23:32 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85FNPH26298;
	Tue, 5 Sep 2000 08:23:25 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA23434;
	Tue, 5 Sep 2000 08:23:25 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA24797;
	Tue, 5 Sep 2000 08:23:25 -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 JAA27104;
	Tue, 5 Sep 2000 09:23:24 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200009051523.JAA27104@hunkular.glarp.com>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) v4 mapped multicast addresses
In-Reply-To: Your message of "Fri, 01 Sep 2000 16:02:26 PDT."
             <v04220815b5d5e2f8f2e8@[10.19.130.190]> 
Date: Tue, 05 Sep 2000 09:23:24 -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>


Forgive me if this has been discussed already, but should applications
be able to use v4 mapped multicast addresses the same way they use
v6 multicast addresses?  I have been working under the assumption
that draft-ietf-ipngwg-rfc2553bis-00.txt intends just this, but
there is at least one popular implementation that doesnt support
this (yet).

And if v4 mapped multicast addresses are allowed by the basic API,
shouldn't IN6_IS_ADDR_MULTICAST() return !0 for v4 mapped multicast
addresses?


thanx,
brad


From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 12:23:14 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07482
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 12:23:13 -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 KAA05108;
	Tue, 5 Sep 2000 10:23:01 -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 JAA08841;
	Tue, 5 Sep 2000 09:22:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85GLhp26414
	for ngtrans-dist; Tue, 5 Sep 2000 09:21:43 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85GLaH26407;
	Tue, 5 Sep 2000 09:21:36 -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 JAA08528;
	Tue, 5 Sep 2000 09:21:36 -0700 (PDT)
Received: from ups.cisco.com (ups.cisco.com [171.69.18.21])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA16951;
	Tue, 5 Sep 2000 09:21:35 -0700 (PDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188])
	by ups.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id JAA14215;
	Tue, 5 Sep 2000 09:20:58 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@ups
Message-Id: <v04220804b5daccb49c8d@[10.19.130.188]>
In-Reply-To: <200009051523.JAA27104@hunkular.glarp.com>
References: <200009051523.JAA27104@hunkular.glarp.com>
Date: Tue, 5 Sep 2000 09:21:21 -0700
To: Brad Huntting <huntting@hunkular.glarp.com>
From: Steve Deering <deering@cisco.com>
Subject: (ngtrans) Re: v4 mapped multicast addresses
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 9:23 AM -0600 9/5/00, Brad Huntting wrote:
>Forgive me if this has been discussed already, but should applications
>be able to use v4 mapped multicast addresses the same way they use
>v6 multicast addresses?

I think we did discuss this is the past and concluded that the v4-mapped
v6 addresses were only meaningful when carrying IPv4 non-loopback, unicast
addresses.  Thus, the IPv6 node should not have to do multiple, different
prefix checks to determine if an address is a multicast address or a
loopback address.

Steve



From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 19:59:19 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15646
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 19:59:18 -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 RAA29868;
	Tue, 5 Sep 2000 17:59:12 -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 QAA18466;
	Tue, 5 Sep 2000 16:58:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85NvVR26835
	for ngtrans-dist; Tue, 5 Sep 2000 16:57:31 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85NvMH26828;
	Tue, 5 Sep 2000 16:57:22 -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 QAA13554;
	Tue, 5 Sep 2000 16:57:22 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA29049;
	Tue, 5 Sep 2000 17:57:20 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id IAA25173;
	Wed, 6 Sep 2000 08:57:11 +0900 (JST)
To: Brad Huntting <huntting@hunkular.glarp.com>
cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
In-reply-to: huntting's message of Tue, 05 Sep 2000 17:40:04 CST.
      <200009052340.RAA01550@hunkular.glarp.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: (ngtrans) Re: v4 mapped multicast addresses 
From: itojun@iijlab.net
Date: Wed, 06 Sep 2000 08:57:11 +0900
Message-ID: <25171.968198231@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

	i agree with steve, also i admit 2553bis should be more explicit about
	what is supposed to work (i.e. should tell people that multicast does
	not work with IPv4 mapped address).

>> I think we did discuss this is the past and concluded that the
>> v4-mapped v6 addresses were only meaningful when carrying IPv4
>> non-loopback, unicast addresses.  Thus, the IPv6 node should not
>> have to do multiple, different prefix checks to determine if an
>> address is a multicast address or a loopback address.
>Well, then I would like to beg and plead for a reconsideration.
>As someone writing a multicast app, I look at the unicast API with
>envy...   Three simple function calls and I'm ready to move data
>with either v4 or v6 hosts.
>	gethostinfo()
>	socket()
>	[bind()]
>	connect()

	getaddrinfo(3) is the way to go.  it will present you with
	necessary info (address family, whatever) together with the
	address you have.  the following code should do the right thing.
	if you hardcode AF_INET6 (or AF_INET), you lose in the future.

	please take a look at the following paper, it gives you a great detail
	about AF independent programming:
.%A Craig Metz
.%T Protocol Independence Using the Sockets API
.%B "Proceedings of the freenix track: 2000 USENIX annual technical conference"
.%D June 2000

itojun


---
main()
{
	i = 0;
	/* initialize hints */
	getaddrinfo(mcastaddr, port, &hints, &res0);
	for (res = res0; res; res = res->ai_next) {
		switch (res->ai_family) {
		case AF_INET6:
		case AF_INET:
			break;
		default:
			exit(1);	/* unknown address family */
		}

		s[i] = socket(res->ai_familiy, res->ai_socktype, res->ai_protocol);
		if (s[i] < 0)
			continue;

		/* do it if necessary */
		if (bind(s[i], res->ai_addr, res->ai_addrlen) < 0) {
			close(s[i]);
			continue;
		}

		switch (res->ai_family) {
		case AF_INET6:
			/* IPV6_MULTICAST_IF, IPV6_JOIN_GROUP */
			break;
		case AF_INET6:
			/* IP_MULTICAST_IF */
			break;
		}

		i++;
		continue;
	}
	if (i == 0);
		exit(1);	/*no listening socket */
	/* select loop on s[0] to s[i - 1] */
}


From owner-ngtrans@sunroof.eng.sun.com  Tue Sep  5 21:37:03 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18117
	for <ngtrans-archive@odin.ietf.org>; Tue, 5 Sep 2000 21:37:02 -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 RAA23030;
	Tue, 5 Sep 2000 17:41:44 -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 QAA19639;
	Tue, 5 Sep 2000 16:41:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e85NeCm26769
	for ngtrans-dist; Tue, 5 Sep 2000 16:40:12 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e85Ne6H26762;
	Tue, 5 Sep 2000 16:40:06 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA17795;
	Tue, 5 Sep 2000 16:40:05 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA03528;
	Tue, 5 Sep 2000 16:40:05 -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 RAA01550;
	Tue, 5 Sep 2000 17:40:04 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200009052340.RAA01550@hunkular.glarp.com>
To: Steve Deering <deering@cisco.com>
cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Re: v4 mapped multicast addresses 
In-Reply-To: Your message of "Tue, 05 Sep 2000 09:21:21 PDT."
             <v04220804b5daccb49c8d@[10.19.130.188]> 
Date: Tue, 05 Sep 2000 17:40:04 -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>


> I think we did discuss this is the past and concluded that the
> v4-mapped v6 addresses were only meaningful when carrying IPv4
> non-loopback, unicast addresses.  Thus, the IPv6 node should not
> have to do multiple, different prefix checks to determine if an
> address is a multicast address or a loopback address.

Well, then I would like to beg and plead for a reconsideration.

As someone writing a multicast app, I look at the unicast API with
envy...   Three simple function calls and I'm ready to move data
with either v4 or v6 hosts.

	gethostinfo()
	socket()
	[bind()]
	connect()

But with multicast I have to have duplicate code.  In fact the same
duplicate code that every other multicast app has to have.

	gethostinfo()
	socket()
	if (sa_family==AF_INET6){
		setsockopt()'s for v6
		[bind()]
		[connect()]
	} else if (sa_family==AF_INET){
		setsockopt()'s for v4
		[bind()]
		[connect()]
	}

And every time I have to handle an group address (group address,
local address, or a remote address) I have to write two sections
of code, one for v6 and one for v4.

And this same duplication of effort goes into every v6 multicast
application (because every one of them will want to be v4 compatible).
And all this duplication could be avoided if applications could
simply use v4mapped multicast addresses with the basic v6 api.

At the very least you should change section 2 paragraph 6 which
currently reads:

	Because of the importance of providing IPv4 compatibility
	in the API, these extensions are explicitly designed to
	operate on machines that provide complete support for both
	IPv4 and IPv6....

If the setsockopt() options IPV6_MULTICAST_IF IPV6_MULTICAST_HOPS
IPV6_JOIN_GROUP and IPV6_LEAVE_GROUP cant be used on v4 multicast
sockets (whether AF_INET or mapped AF_INET6), then the above
paragraph is not being honest and language should be added to
indicate that v4 multicast is not in any way supported by this API.
If these socket options are to be supported for v4 multicast sockets,
then language should be added to make it clear what the basic API
should support.


brad


From owner-ngtrans@sunroof.eng.sun.com  Wed Sep  6 03:40:04 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05236
	for <ngtrans-archive@odin.ietf.org>; Wed, 6 Sep 2000 03:40:03 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA17854;
	Wed, 6 Sep 2000 01:39:53 -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 AAA24711;
	Wed, 6 Sep 2000 00:39:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e867cYv27072
	for ngtrans-dist; Wed, 6 Sep 2000 00:38:34 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e867cMH27065;
	Wed, 6 Sep 2000 00:38:23 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id AAA14452;
	Wed, 6 Sep 2000 00:38:20 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA10692;
	Wed, 6 Sep 2000 00:38:19 -0700 (PDT)
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 e867bi616624;
	Wed, 6 Sep 2000 09:37:44 +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 JAA02096;
	Wed, 6 Sep 2000 09:37:42 +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 JAA54271;
	Wed, 6 Sep 2000 09:37:43 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009060737.JAA54271@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Brad Huntting <huntting@hunkular.glarp.com>
cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) v4 mapped multicast addresses 
In-reply-to: Your message of Tue, 05 Sep 2000 09:23:24 MDT.
             <200009051523.JAA27104@hunkular.glarp.com> 
Date: Wed, 06 Sep 2000 09:37:43 +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:
   
   Forgive me if this has been discussed already, but should applications
   be able to use v4 mapped multicast addresses the same way they use
   v6 multicast addresses?

=> this was never specified in API specs but perhaps it is not
very reasonable because multicast APIs are too different (no scope
in IPv4 for instance).

   I have been working under the assumption
   that draft-ietf-ipngwg-rfc2553bis-00.txt intends just this,

=> obviously it is not the case for everybody.

   but there is at least one popular implementation that doesnt
   support this (yet).

=> in the scope ID usage for multicast discussion one suggested
to retrofit IPv6 multicast API goodies into the IPv4 multicast API.
I have no strong opinion about this (it is a good idea if it is easy
to implement *and* to explain to common programmers) but we have
the IPv4 multicast API designer in the list then I'd like to
get other's opinion....
   
   And if v4 mapped multicast addresses are allowed by the basic API,
   shouldn't IN6_IS_ADDR_MULTICAST() return !0 for v4 mapped multicast
   addresses?
   
=> I disagree. IN6_IS_ADDR_MULTICAST() is for real IPv6 addresses only,
for IPv4 mapped multicast one should use IN6_IS_ADDR_V4MAPPED() then
the common but not standardized macro to extract the IPv4 address and
finally IN_MULTICAST() (with the good endian :-).

Regards

Francis.Dupont@enst-bretagne.fr

PS: until a too well known router vender provides IPv6 multicast routing,
this discussion has a little interest because IPv6 multicast is not
available in the real world (or we'll come back to Mbone nightmares).


From owner-ngtrans@sunroof.eng.sun.com  Wed Sep  6 06:47:09 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07070
	for <ngtrans-archive@odin.ietf.org>; Wed, 6 Sep 2000 06:47:08 -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 EAA17413;
	Wed, 6 Sep 2000 04:47:00 -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 DAA29193;
	Wed, 6 Sep 2000 03:46:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e86Aj6927230
	for ngtrans-dist; Wed, 6 Sep 2000 03:45:06 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e86AivH27223
	for <ngtrans@sunroof.eng.sun.com>; Wed, 6 Sep 2000 03:44:57 -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 DAA20370
	for <ngtrans@sunroof.eng.sun.com>; Wed, 6 Sep 2000 03:44:56 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA14703
	for <ngtrans@sunroof.eng.sun.com>; Wed, 6 Sep 2000 03:44:55 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06945;
	Wed, 6 Sep 2000 06:44:55 -0400 (EDT)
Message-Id: <200009061044.GAA06945@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-6to4-07.txt
Date: Wed, 06 Sep 2000 06:44:54 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Connection of IPv6 Domains via IPv4 Clouds 	  
        Author(s)	: B. Carpenter, K. Moore
	Filename	: draft-ietf-ngtrans-6to4-07.txt
	Pages		: 24
	Date		: 05-Sep-00
	
This memo specifies an optional interim mechanism for IPv6 sites to
communicate with each other over the IPv4 network without explicit
tunnel setup, and for them to communicate with native IPv6 domains
via relay routers.  Effectively it treats the wide area IPv4 network
as a unicast point-to-point link layer. The mechanism is intended as
a start-up transition tool used during the period of co-existence of
IPv4 and IPv6. It is not intended as a permanent solution.

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-6to4-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-6to4-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-6to4-07.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Sep  6 08:27:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09875
	for <ngtrans-archive@odin.ietf.org>; Wed, 6 Sep 2000 08:27:42 -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 GAA20067;
	Wed, 6 Sep 2000 06:27: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 FAA09896;
	Wed, 6 Sep 2000 05:27:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e86CPtr27309
	for ngtrans-dist; Wed, 6 Sep 2000 05:25:55 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e86COJH27293;
	Wed, 6 Sep 2000 05:24:20 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA15477;
	Wed, 6 Sep 2000 05:24:18 -0700 (PDT)
Received: from smtp2.libero.it (smtp2.libero.it [193.70.192.52])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA29955;
	Wed, 6 Sep 2000 05:24:16 -0700 (PDT)
Received: from trantor.ferrara.linux.it (151.20.151.247) by smtp2.libero.it; 6 Sep 2000 14:24:14 +0200
Received: by trantor.ferrara.linux.it (Postfix, from userid 501)
	id 0927C4D25D; Wed,  6 Sep 2000 13:49:27 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by trantor.ferrara.linux.it (Postfix) with ESMTP
	id 052964C9B5; Wed,  6 Sep 2000 13:49:27 +0200 (CEST)
Date: Wed, 6 Sep 2000 13:49:26 +0200 (CEST)
From: Mauro Tortonesi <mauro@ferrara.linux.it>
To: itojun@iijlab.net
Cc: Brad Huntting <huntting@hunkular.glarp.com>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Re: v4 mapped multicast addresses 
In-Reply-To: <25171.968198231@coconut.itojun.org>
Message-ID: <Pine.LNX.4.21.0009061348320.4526-100000@trantor.ferrara.linux.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Mauro Tortonesi <mauro@ferrara.linux.it>

On Wed, 6 Sep 2000 itojun@iijlab.net wrote:

> 	please take a look at the following paper, it gives you a great detail
> 	about AF independent programming:
> .%A Craig Metz
> .%T Protocol Independence Using the Sockets API
> .%B "Proceedings of the freenix track: 2000 USENIX annual technical conference"
> .%D June 2000

where can i get this? can you point me to an URL? thanks.

-- 
Aequam memento rebus in arduis servare mentem...

Mauro Tortonesi			mauro@ferrara.linux.it
Ferrara Linux User Group	http://www.ferrara.linux.it
Project6 - IPv6 for Linux	http://project6.ferrara.linux.it



From owner-ngtrans@sunroof.eng.sun.com  Wed Sep  6 08:29:10 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09928
	for <ngtrans-archive@odin.ietf.org>; Wed, 6 Sep 2000 08:29:10 -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 GAA20704;
	Wed, 6 Sep 2000 06:29:05 -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 FAA22628;
	Wed, 6 Sep 2000 05:28:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e86CRju27354
	for ngtrans-dist; Wed, 6 Sep 2000 05:27:45 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e86CPxH27311;
	Wed, 6 Sep 2000 05:26:00 -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 FAA22043;
	Wed, 6 Sep 2000 05:25:59 -0700 (PDT)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA02404;
	Wed, 6 Sep 2000 05:25:59 -0700 (PDT)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 6D9021831; Wed,  6 Sep 2000 08:25:58 -0400 (EDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id 303A119B5; Wed,  6 Sep 2000 08:25:58 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id IAA0000596392; Wed, 6 Sep 2000 08:23:23 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200009061223.IAA0000596392@anw.zk3.dec.com>
To: itojun@iijlab.net
Cc: Brad Huntting <huntting@hunkular.glarp.com>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, bound@zk3.dec.com
Subject: Re: (ngtrans) Re: v4 mapped multicast addresses 
In-reply-to: Your message of "Wed, 06 Sep 2000 08:57:11 +0900."
             <25171.968198231@coconut.itojun.org> 
Date: Wed, 06 Sep 2000 08:23:23 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Itojun,

	i agree with steve, also i admit 2553bis should be more explicit about
	what is supposed to work (i.e. should tell people that multicast does
	not work with IPv4 mapped address).

This is simply not true.  IPv4-Mapped is a representation of an IPv4
address that is all.  If you strip out the leading bits for IPv6 you
have left an IPv4 address whether its multicast or not.  

What does have to be responded to is the mappings for IPv6 Multicast to
IPv4 if an applications listens and sends to IPv4-Mapped and that
discussion is in process as part of the update to the api now.

/jim


From owner-ngtrans@sunroof.eng.sun.com  Wed Sep  6 09:02:40 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10993
	for <ngtrans-archive@odin.ietf.org>; Wed, 6 Sep 2000 09:02:39 -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 HAA04710;
	Wed, 6 Sep 2000 07:02:35 -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 GAA22382;
	Wed, 6 Sep 2000 06:01:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e86D0jc27491
	for ngtrans-dist; Wed, 6 Sep 2000 06:00:45 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e86D0aH27484;
	Wed, 6 Sep 2000 06:00:36 -0700 (PDT)
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 GAA10613;
	Wed, 6 Sep 2000 06:00:36 -0700 (PDT)
Received: from itojun.org (dialup0.itojun.org [210.160.95.108])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA12083;
	Wed, 6 Sep 2000 06:00:33 -0700 (PDT)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.10.0/3.7W) with ESMTP id e86CujK00754;
	Wed, 6 Sep 2000 21:56:45 +0900 (JST)
Message-Id: <200009061256.e86CujK00754@itojun.org>
To: Mauro Tortonesi <mauro@ferrara.linux.it>
cc: Brad Huntting <huntting@hunkular.glarp.com>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com
In-reply-to: mauro's message of Wed, 06 Sep 2000 13:49:26 +0200.
      <Pine.LNX.4.21.0009061348320.4526-100000@trantor.ferrara.linux.it> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) Re: v4 mapped multicast addresses 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Wed, 06 Sep 2000 21:56:45 +0900
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>> .%A Craig Metz
>> .%T Protocol Independence Using the Sockets API
>> .%B "Proceedings of the freenix track: 2000 USENIX annual technical conference"
>> .%D June 2000
>where can i get this? can you point me to an URL? thanks.

http://www.usenix.org/publications/library/proceedings/usenix2000/freenix/metzprotocol.html

	you need to be a usenix member to get this, until June 2001.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep  7 01:09:03 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00375
	for <ngtrans-archive@odin.ietf.org>; Thu, 7 Sep 2000 01:09:02 -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 XAA19864;
	Wed, 6 Sep 2000 23:08:57 -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 WAA08807;
	Wed, 6 Sep 2000 22:08:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8757cU28070
	for ngtrans-dist; Wed, 6 Sep 2000 22:07:38 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.85.31] (may be forged))
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8757OH28063;
	Wed, 6 Sep 2000 22:07:25 -0700 (PDT)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with SMTP id e8757Lk256965;
	Wed, 6 Sep 2000 22:07:22 -0700 (PDT)
Date: Wed, 6 Sep 2000 22:07:18 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: (ngtrans) Re: v4 mapped multicast addresses
To: Steve Deering <deering@cisco.com>
Cc: Brad Huntting <huntting@hunkular.glarp.com>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <v04220804b5daccb49c8d@[10.19.130.188]>
Message-ID: <Roam.SIMC.2.0.6.968303238.18240.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>


> I think we did discuss this is the past and concluded that the v4-mapped
> v6 addresses were only meaningful when carrying IPv4 non-loopback, unicast
> addresses.  Thus, the IPv6 node should not have to do multiple, different
> prefix checks to determine if an address is a multicast address or a
> loopback address.

I thought that discussion was for IPv4-compatible addresses.
Did we have the discussion for IPv4-mapped addresses as well?

  Erik




From owner-ngtrans@sunroof.eng.sun.com  Thu Sep  7 01:09:34 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00374
	for <ngtrans-archive@odin.ietf.org>; Thu, 7 Sep 2000 01:09:02 -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 XAA19859;
	Wed, 6 Sep 2000 23:08:55 -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 WAA08736;
	Wed, 6 Sep 2000 22:07:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8756Ii28046
	for ngtrans-dist; Wed, 6 Sep 2000 22:06:18 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.82.166] (may be forged))
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e87568H28036;
	Wed, 6 Sep 2000 22:06:08 -0700 (PDT)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with SMTP id e87566k256866;
	Wed, 6 Sep 2000 22:06:06 -0700 (PDT)
Date: Wed, 6 Sep 2000 22:06:03 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: (ngtrans) Re: v4 mapped multicast addresses
To: Brad Huntting <huntting@hunkular.glarp.com>
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <200009051523.JAA27104@hunkular.glarp.com>
Message-ID: <Roam.SIMC.2.0.6.968303163.4682.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>


> Forgive me if this has been discussed already, but should applications
> be able to use v4 mapped multicast addresses the same way they use
> v6 multicast addresses?  I have been working under the assumption
> that draft-ietf-ipngwg-rfc2553bis-00.txt intends just this, but
> there is at least one popular implementation that doesnt support
> this (yet).

I don't think this has been discussed much on the mailing list.
We did agree that for IPv4-compatible addresses it didn't make sense
at all to allow IPv4 multicast addresses.

Initially I didn't see the need for multicast addresses in the IPv4-mapped
space, but when folks did an implementation of the java.net classes that
transparently did IPv6 and IPv4 it was a real pain to make the multicast
class work without being able to 
	always open an AF_INET6 socket
	issue IPV6_JOINGROUP socket options with either a native IPv6
	multicast address or an IPv4-mapped multicast address.
The alternative would have been to allow the IP_ADD_MEMBERSHIP socket
option on AF_INET6 sockets.

I don't think this is necessary for real applications since they
presumably know whether they are using to use IPv6 or IPv4 multicast
before creating the socket.

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Thu Sep  7 09:44:06 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16114
	for <ngtrans-archive@odin.ietf.org>; Thu, 7 Sep 2000 09:44:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA16052;
	Thu, 7 Sep 2000 07:43:53 -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 GAA14282;
	Thu, 7 Sep 2000 06:43:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e87DeTU28364
	for ngtrans-dist; Thu, 7 Sep 2000 06:40:29 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e87DeLH28357;
	Thu, 7 Sep 2000 06:40:22 -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 GAA18334;
	Thu, 7 Sep 2000 06:40:20 -0700 (PDT)
Received: from popcorn.cisco.com (popcorn.cisco.com [171.69.18.32])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA13738;
	Thu, 7 Sep 2000 06:40:21 -0700 (PDT)
Received: from [192.87.117.47] (ssh.cisco.com [171.69.10.34])
	by popcorn.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id GAA04643;
	Thu, 7 Sep 2000 06:39:14 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@127.0.0.1
Message-Id: <v04220800b5dd4aeb3bad@[192.87.117.47]>
In-Reply-To: <Roam.SIMC.2.0.6.968303238.18240.nordmark@jurassic>
References: <Roam.SIMC.2.0.6.968303238.18240.nordmark@jurassic>
Date: Thu, 7 Sep 2000 06:40:23 -0700
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
From: Steve Deering <deering@cisco.com>
Subject: (ngtrans) Re: v4 mapped multicast addresses
Cc: Brad Huntting <huntting@hunkular.glarp.com>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 10:07 PM -0700 9/6/00, Erik Nordmark wrote:
>I thought that discussion was for IPv4-compatible addresses.
>Did we have the discussion for IPv4-mapped addresses as well?

You are right.  I confused one with the other.

Steve



From owner-ngtrans@sunroof.eng.sun.com  Thu Sep  7 12:40:44 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20372
	for <ngtrans-archive@odin.ietf.org>; Thu, 7 Sep 2000 12:40:44 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA22423;
	Thu, 7 Sep 2000 10:40:38 -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 JAA23412;
	Thu, 7 Sep 2000 09:39:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e87Gcn128519
	for ngtrans-dist; Thu, 7 Sep 2000 09:38:49 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e87Gb3H28504;
	Thu, 7 Sep 2000 09:37:03 -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 JAA25185;
	Thu, 7 Sep 2000 09:37:02 -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 JAA20319;
	Thu, 7 Sep 2000 09:37:01 -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);
	 Thu, 7 Sep 2000 09:19:32 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 07 Sep 2000 09:20:04 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Thu, 7 Sep 2000 09:20:04 -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_01C018E7.48F6F9D2"
Subject: RE: (ngtrans) Re: v4 mapped multicast addresses
Date: Thu, 7 Sep 2000 09:18:40 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A5690C6F7B60@SIT.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) Re: v4 mapped multicast addresses
Thread-Index: AcAYiZM9904zrqI5S1Ko9oYZ3C1E2AAXNa/A
From: "Dave Thaler" <dthaler@Exchange.Microsoft.com>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>,
        "Brad Huntting" <huntting@hunkular.glarp.com>
Cc: <ipng@sunroof.eng.sun.com>, <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 07 Sep 2000 16:20:04.0346 (UTC) FILETIME=[7AD1DDA0:01C018E7]
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_01C018E7.48F6F9D2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Erik Nordmark writes:
> I don't think this is necessary for real applications since they
> presumably know whether they are using to use IPv6 or IPv4 multicast
> before creating the socket.

This is only partially true.  A protocol-independent application
would likely get the address from either getaddrinfo(), or from
parsing an SDP description.  Both of these methods can generate
a sockaddr in either AF_INET or AF_INET6, or in AF_INET6 with v4-
mapped addresses.  In the getaddrinfo case, the app doesn't "know"=20
unless you add code to check.
In the SDP case, there's no standard library that I'm aware of,
but some libraries may exist that work similarly to getaddrinfo().

-Dave

------_=_NextPart_001_01C018E7.48F6F9D2
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.4417.0">
<TITLE>RE: (ngtrans) Re: v4 mapped multicast addresses</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Erik Nordmark writes:</FONT>

<BR><FONT SIZE=3D2>&gt; I don't think this is necessary for real =
applications since they</FONT>

<BR><FONT SIZE=3D2>&gt; presumably know whether they are using to use =
IPv6 or IPv4 multicast</FONT>

<BR><FONT SIZE=3D2>&gt; before creating the socket.</FONT>
</P>

<P><FONT SIZE=3D2>This is only partially true.&nbsp; A =
protocol-independent application</FONT>

<BR><FONT SIZE=3D2>would likely get the address from either =
getaddrinfo(), or from</FONT>

<BR><FONT SIZE=3D2>parsing an SDP description.&nbsp; Both of these =
methods can generate</FONT>

<BR><FONT SIZE=3D2>a sockaddr in either AF_INET or AF_INET6, or in =
AF_INET6 with v4-</FONT>

<BR><FONT SIZE=3D2>mapped addresses.&nbsp; In the getaddrinfo case, the =
app doesn't &quot;know&quot; </FONT>

<BR><FONT SIZE=3D2>unless you add code to check.</FONT>

<BR><FONT SIZE=3D2>In the SDP case, there's no standard library that I'm =
aware of,</FONT>

<BR><FONT SIZE=3D2>but some libraries may exist that work similarly to =
getaddrinfo().</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C018E7.48F6F9D2--


From owner-ngtrans@sunroof.eng.sun.com  Sat Sep  9 02:20: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 CAA19782
	for <ngtrans-archive@odin.ietf.org>; Sat, 9 Sep 2000 02:20:47 -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 AAA20615;
	Sat, 9 Sep 2000 00:20:42 -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 XAA04703;
	Fri, 8 Sep 2000 23:19:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e896ILC29647
	for ngtrans-dist; Fri, 8 Sep 2000 23:18:21 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e896IEH29640;
	Fri, 8 Sep 2000 23:18:15 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id XAA00121;
	Fri, 8 Sep 2000 23:18:10 -0700 (PDT)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA07933;
	Fri, 8 Sep 2000 23:18:09 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id PAA11753;
	Sat, 9 Sep 2000 15:18:08 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id PAA01174; Sat, 9 Sep 2000 15:18:08 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id PAA29168; Sat, 9 Sep 2000 15:18:07 +0900 (JST)
Date: Sat, 09 Sep 2000 15:18:53 +0900 (JST)
Message-Id: <20000909.151853.74665794.kazu@Mew.org>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, 6bone@ISI.EDU
Subject: (ngtrans) The Global IPv6 Summit in Japan
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.95b57 on Emacs 20.7 / Mule 4.0 (HANANOEN)
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: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
Content-Transfer-Encoding: 7bit

# This is the third try since the previously posted message have not
# delivered. Sorry if you receive duplicated messages.

Hello IPv6 folks,

"The Global IPv6 Summit in Japan" will be held in the next week of
IETF San Diego at Osaka city, Japan. Most presentations/panels are
spoken in Japanese but we prepare translators between Japanese and
English. So, we would like to call for your participation.

Also you have a chance to appeal your IPv6 business in a session. We
would also like to call for your presentations.

// Steering Group of the Global IPv6 Summit in Japan

----
	Call for participation and presentations for
	"the Global IPv6 Summit in Japan"

<<Abstract>>

The Global IPv6 Summit, under the organization of the IPv6 Forum, is
held regularly around the world to accelerate the deployment of
IPv6. We are happy to announce that this conference will be held in
Japan, one of the leading countries in the areas of IPv6 development
and deployment.

The Internet is built on the foundations of the Internet Protocol
(IP). The current version of IP is named IPv4 after its version
number. The total number of devices that IPv4 can identify is limited
to about 4.3 billion. It's hard to see the Internet becoming the
foundation of a true, universal communications infrastructure when
this number is compared to the human population.

In fact, it is expected that the entire address space of IPv4 will be
exhausted by around 2008. So, address assignment/allocation is
currently being carried out under a very restrictive policy. NAT
(Network Address Translator) was introduced as a temporary solution,
resulting in the loss of some of the original functionality of the
Internet.

The principles of the Internet are end-to-end and bidirectional
communication. This means every node can communicate with every other
freely without any restrictions caused by intermediate nodes. Since
NAT broke these principles, it became difficult for unexpected novel
applications to appear in the current environment of the Internet.

To resolve the exhaustion of IP addresses, extending its address space
is a straightforward solution. IPv6, the next generation of IP,
provides a huge number of IP addresses and makes NAT obsolete allowing
the Internet to recover its original principles.

IPv6 is a paradigm recovery for applications. After deploying IPv6 and
recovering end-to-end/bidirectional communication, we cannot imagine
what kind of applications will appear.

This conference will introduce the current deployment status of IPv6
throughout the world. Also, panel discussions are planned, both on
"How IPv6 will Change Business" and on "Case Studies: Making the
Change to IPv6".

Getting Internet people together, including those who are involved in
IPv6 activities and IPv4 business and management, we intend to discuss
the future of Internet business and the direction of engineering.
This conference will be beneficial for everyone including, but not
limited to, engineers, researchers, network managers and business
people. We would like to invite each of you to participate.

<<The Host>>

	Steering Group of the Global IPv6 Summit in Japan
	(Contact: info@jp.ipv6forum.com)

<<Logistics>>

	Date:
		December 18 - 19, 2000
		(As a part of Internet Week 2000)
	Venue: 
		Grand Cube Osaka (Osaka International Convention Center)
		5-3-51, Nakanoshima, Kita-ku, Osaka 530-0005, JAPAN
		Phone: +81-6-4803-5555
		Fax:   +81-6-4803-5620
		E-mail: soumu@gco.co.jp
		http://www.gco.co.jp/index.html
		(The same place as Internet Week 2000)

<<Registration Fee>>

	<Conference Fee>

			Early registration	Regular/
			discount		On-site registration
			(until Oct 31)
	Non-student	10,000 JPY		15,000 JPY
	Student		 2,000 JPY		 2,000 JPY

	<Reception Fee>

	Non-student	 5,000 JPY
	Student		 3,000 JPY


<<Program>>

	December 18 (Mon)

		Keynote Speech 1: Dr. Jun Murai, WIDE Project
		Session 1: Business report on IPv6 in Japan
		Session 2: Status report from Asian countries
		Session 3: Panel on how IPv6 will change business

		Reception

	December 19 (Tue)

		Keynote Speech 2: Dr. Steve Deering, Cisco Systems
		Session 4: Business report on IPv6 around the world
		Session 5: Case Studies: Making the Change to IPv6

<<Participation>>

This conference will be held as a part of Internet Week 2000. Please
refer to the following page for registration:

	http://www.jp.ipv6forum.com/

<<Presentation Proposals>>

The program committee calls for presentation proposal for "Session 4:
Business report of IPv6 around the world". Candidates are sTLA holders
and IPv6 vendors. Please propose a "10 minutes" presentation on your
IPv6 business.

If you would like to give a presentation, please send an e-mail
message in the following form. Please note that we may not accept all
proposals due to the time limitations of the program.

Format:			See below
Deadline:		September 30, 2000
Notification date:	October 6, 2000

	To: cfp@jp.ipv6forum.com
	Subject: presentation proposal

	Name		:
	Title		:
	Email		:
	Telephone number:
	Organization	:
	Department	:

	Your proposal in plain text (no more than 250 words)
	explaining as concretely as possible your point of view and
	what kind of presentation can be expected.
----


From owner-ngtrans@sunroof.eng.sun.com  Mon Sep 11 13:07: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 NAA06599
	for <ngtrans-archive@odin.ietf.org>; Mon, 11 Sep 2000 13:07:58 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA10006;
	Mon, 11 Sep 2000 11:07:52 -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 JAA26955;
	Mon, 11 Sep 2000 09:55:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8BGrwr01127
	for ngtrans-dist; Mon, 11 Sep 2000 09:53:58 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8BGrsH01120
	for <ngtrans@sunroof.eng.sun.com>; Mon, 11 Sep 2000 09:53:54 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.10.2+Sun/8.10.2) id e8BGrUx02350
	for ngtrans@sunroof.eng.sun.com; Mon, 11 Sep 2000 09:53:30 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e871kOH27987;
	Wed, 6 Sep 2000 18:46:25 -0700 (PDT)
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 SAA20889;
	Wed, 6 Sep 2000 18:46:24 -0700 (PDT)
From: cfp@jp.ipv6forum.com
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA08805;
	Wed, 6 Sep 2000 18:46:23 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id KAA17726;
	Thu, 7 Sep 2000 10:46:21 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id KAA14905; Thu, 7 Sep 2000 10:46:20 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id KAA12382; Thu, 7 Sep 2000 10:46:19 +0900 (JST)
Date: Thu, 07 Sep 2000 10:47:01 +0900 (JST)
Message-Id: <20000907.104701.71162403.kazu@Mew.org>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) The Global IPv6 Summit in Japan
X-Mailer: Mew version 1.95b57 on Emacs 20.7 / Mule 4.0 (HANANOEN)
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: cfp@jp.ipv6forum.com
Content-Transfer-Encoding: 7bit

Hello folks,

"The Global IPv6 Summit in Japan" will be held in the next week of
IETF San-Diego. Presentations/Panels are spoken in Japanese but we
will prepare translators between Japanese and English.

We would like to call for your participation. 

We prepare a session called "Business report on IPv6 around the
world". This would be a good chance for your company to appeal your
business strategy on IPv6. We would also like to call for your
presentation.

See you in Osaka.

// Global IPv6 Summit in Japan Steering Group

----
	Call for participations and presentations for
	"The Global IPv6 Summit in Japan"

<<Abstract>>

The Global IPv6 Summit, under the organization of the IPv6 Forum, is
held regularly around the world to accelerate the deployment of
IPv6. We are happy to announce that this conference will be held in
Japan, one of the leading countries in the areas of IPv6 development
and deployment.

The Internet is built on the foundations of the Internet Protocol
(IP). The current version of IP is named IPv4 after its version
number. The total number of devices that IPv4 can identify is limited
to about 4.3 billion. It's hard to see the Internet becoming the
foundation of a true, universal communications infrastructure when
this number is compared to the human population.

In fact, it is expected that the entire address space of IPv4 will be
exhausted by around 2008. So, address assignment/allocation is
currently being carried out under a very restrictive policy. NAT
(Network Address Translator) was introduced as a temporary solution,
resulting in the loss of some of the original functionality of the
Internet.

The principles of the Internet are end-to-end and bidirectional
communication. This means every node can communicate with every other
freely without any restrictions caused by intermediate nodes. Since
NAT broke these principles, it became difficult for unexpected novel
applications to appear in the current environment of the Internet.

To resolve the exhaustion of IP addresses, extending its address space
is a straightforward solution. IPv6, the next generation of IP,
provides a huge number of IP addresses and makes NAT obsolete allowing
the Internet to recover its original principles.

IPv6 is a paradigm recovery for applications. After deploying IPv6 and
recovering end-to-end/bidirectional communication, we cannot imagine
what kind of applications will appear.

This conference will introduce the current deployment status of IPv6
throughout the world. Also, panel discussions are planned, both on
"How IPv6 will Change Business" and on "Case Studies: Making the
Change to IPv6".

Getting Internet people together, including those who are involved in
IPv6 activities and IPv4 business and management, we intend to discuss
the future of Internet business and the direction of engineering.
This conference will be beneficial for everyone including, but not
limited to, engineers, researchers, network managers and business
people. We would like to invite each of you to participate.

<<The Host>>

	Global IPv6 Summit in Japan Steering Group
	(Contact: info@jp.ipv6forum.com)

<<Logistics>>

	Date:
		December 18 - 19, 2000
		(As a part of Internet Week 2000)
	Venue: 
		Grand Cube Osaka (Osaka International Convention Center)
		5-3-51, Nakanoshima, Kita-ku, Osaka 530-0005, JAPAN
		Phone: +81-6-4803-5555
		Fax:   +81-6-4803-5620
		E-mail: soumu@gco.co.jp
		http://www.gco.co.jp/index.html
		(The same place as Internet Week 2000)

<<Registration Fee>>

	<Conference Fee>

			Early registration	Regular/
			discount		On-site registration
			(until Oct 31)
	Non-student	10,000 JPY		15,000 JPY
	Student		 2,000 JPY		 2,000 JPY

	<Reception Free>

	Non-student	 5,000 JPY
	Student		 3,000 JPY


<<Program>>

	December 18 (Mon)

		Keynote Speech 1: Dr. Jun Murai, WIDE Project
		Session 1: Business report on IPv6 in Japan
		Session 2: Status report from Asian countries
		Session 3: Panel on how IPv6 will change business

		Reception

	December 19 (Tue)

		Keynote Speech 2: Dr. Steve Deering, Cisco Systems
		Session 4: Business report on IPv6 around the world
		Session 5: Case Studies: Making the Change to IPv6

<<Participation>>

This conference will be held as a part of Internet Week 2000. Please
refer to the following page for registration:

	http://www.jp.ipv6forum.com/

<<Presentation Proposal>>

The program committee calls for presentation proposal for "Session 4:
Business report of IPv6 in foreign contrives". Candidates are sTLA
holders and IPv6 vendors. Please propose a "10 minutes" presentation
on your IPv6 business.

If you would like to give a presentation, please send an e-mail
message in the following form. Please note that we may not accept all
proposal due to the time limitations of the program.

Format:			See below
Deadline:		September 30, 2000
Notification date:	October 6, 2000

	To: cfp@jp.ipv6forum.com
	Subject: presentation proposal

	Name		:
	Title		:
	Email		:
	Telephone number:
	Organization	:
	Department	:

	Your proposal in plain text (no more than 250 words)
	explaining as concretely as possible your point of view and
	what kind of presentation can be expected.
----




From owner-ngtrans@sunroof.eng.sun.com  Tue Sep 12 18:55: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 SAA14984
	for <ngtrans-archive@odin.ietf.org>; Tue, 12 Sep 2000 18:55:08 -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 QAA22950;
	Tue, 12 Sep 2000 16:54:59 -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 PAA03990;
	Tue, 12 Sep 2000 15:54:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8CMrC102832
	for ngtrans-dist; Tue, 12 Sep 2000 15:53:12 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8CMr5H02825
	for <ngtrans@sunroof.eng.sun.com>; Tue, 12 Sep 2000 15:53:05 -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 PAA03730
	for <ngtrans@sunroof.eng.sun.com>; Tue, 12 Sep 2000 15:53:05 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA26950
	for <ngtrans@sunroof.eng.sun.com>; Tue, 12 Sep 2000 15:53:05 -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);
	 Tue, 12 Sep 2000 15:49:17 -0700
Received: from 172.30.236.11 by df-virus2.platinum.corp.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 12 Sep 2000 15:49:50 -0700 (Pacific Daylight Time)
Received: from speak.platinum.corp.microsoft.com ([172.30.236.197]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Tue, 12 Sep 2000 15:43:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: (ngtrans) FW: Notes from Pittsburgh
Date: Tue, 12 Sep 2000 15:43:41 -0700
Message-ID: <CC2E64D4B3BAB646A87B5A3AE97090420D5F071A@speak.platinum.corp.microsoft.com>
Thread-Topic: Notes from Pittsburgh
Thread-Index: AcAOJA3k2abdiIOlQiiodnp8xhUIhAO3QZkw
From: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
To: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 12 Sep 2000 22:43:41.0688 (UTC) FILETIME=[E64A4780:01C01D0A]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e8CMr6H02826
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
Content-Transfer-Encoding: 8bit

These are still the raw notes from Pittsburgh. If details are wrong or
incomplete for the key issues please speak up.

Tony

>  -----Original Message-----
> From: 	Tony Hain  
> Sent:	Thursday, August 24, 2000 4:36 PM
> To:	'Bob Fink'; 'Alain Durand'
> Subject:	Notes from Pittsburgh
> 
> Sorry these have taken so long to get out... I am not sure how to best
> clean them up without ending up back at simply the agenda. Thoughts?
> 
> NGtrans Minutes 8/2/00
> 
> With a single 2-hour time slot and 18 topics to discuss, each topic
> had a strict time limit, resulting in very little discussion. Without
> a volunteer to take notes, the timekeeper was doing double duty. The
> presentation series resulted in 3 new documents being sent to the list
> for becoming working group items, and one moving to working group last
> call. The primary focus of the series was 6to4, with the various
> translators adding refinements. The group will change its name to
> match the IPNG change, and become IPv6transition.
> 
> Agenda Bash						2 min Chairs
> Overview document					5 min Chairs 
> 
> N+I							2 min Jinmei
> Tatuya
> 		routers from hitaci & cisco
> 
> DSTM 							10 min Jim Bound
> 		new co-authors
> 		removed all optional processing
> 		applicability statement added
> 		desire for manual config : details in mail
> 		dns components will be started as a new additional draft
> 
> SIIT evolution 						10 min
> Eric Nordmark
> 		inbound routing to v6 only box
> 		discovery of the mapping to tunnel
> 		tunneling to mobile node : results in 3 headers per
> packet
> 		open issues : getting addresses from visited site vs.
> home
> 		pdf of slides in the mail
> 
> 6to4 multicast 						10 min
> Dave Thaler
> 		goal is to make multicast work over nbma link
> 		scale : state per receiver
> 		ask list to move to wg draft
> 
> 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)
> 
> Tunnels end point in DNS   				5 min Alain
> Durand
> 		ask list to move to wg draft (possibly combined with
> 6to4scale)
> 
> 6to4 addresses rvs DNS   				10 min Keith
> Moore
> 		map out possible solutions
> 		2 methods : if existing ipv4 zone look there : assume
> well known addr
> 		only assume delegation point, not record
> 		dos attack concerns raised
> 
> Broker							5 min
> Guardini Ivano
> 		framework doc 
> 
> Mime type 						5 min Alain
> Durand
> 		ask list to move to wg draft
> 
> v6v4compat 						5 min 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
> 
> Hometun 						10 min 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 
> 
> Multicast Translator 					5 min Kazuaki
> Tsuchiya
> 		take to list for further discussion : chairs to discuss
> experimental vs. std
> 
> Abuse against IPv6 transition				2 min Itojun
> 		open relays as attack point
> 		is this an ipv6 or ngtrans issue?
> 		is this an implementation or spec issue?
> 		seem to be setting up mechanisms that make ddos easier
> 
> Transport relay translator 				2 min Itojun
> 		no extra config : trying to increase scale
> 		no major changes - want to go to wg last call
> 		wants wg last call
> 
> SOCKS update 	 					2 min Hiroshi
> Kitamura
> 		comments addressed : unnecessary parts removed
> 		looking for WG last call
> 
> Introduction to transition  				2 min Alain
> Durand
> 		scenarios are next
> 		update on dstm to match new draft
> 		expect -05 soon : last call in SD
> 
> WG Name change					2 min Chairs
> 
> 		linked to ipng group so we should to change to ipv6 as
> well
> 		will revisit charter at the same time
> 
> 


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 07:02:46 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 HAA08414
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 07:02: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 FAA07397;
	Thu, 14 Sep 2000 05:02:25 -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 DAA17565;
	Thu, 14 Sep 2000 03:59:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EAwIY04435
	for ngtrans-dist; Thu, 14 Sep 2000 03:58:18 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EAw9H04428
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 03:58:09 -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 DAA25902
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 03:58:08 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA09268
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 03:58:07 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08366;
	Thu, 14 Sep 2000 06:58:06 -0400 (EDT)
Message-Id: <200009141058.GAA08366@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-broker-04.txt
Date: Thu, 14 Sep 2000 06:58:06 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: IPv6 Tunnel Broker
	Author(s)	: A. Durand, P. Fasano, I. Guardini, D. Lento
	Filename	: draft-ietf-ngtrans-broker-04.txt
	Pages		: 10
	Date		: 13-Sep-00
	
The IPv6 global Internet as of today is mostly built using tunnels over
the existing IPv4 infrastructure. Those tunnels are difficult to
configure and maintain in a large scale environment. The 6bone has
proven that large sites and ISPs can do it, but this process is too
complex for the isolated end user who already has an IPv4 connection and
would like to enter the IPv6 world. The motivation for the development
of the tunnel broker model is to help early IPv6 adopters to hook up
to an existing IPv6 network (e.g. the 6bone) and to get stable,
permanent IPv6 addresses and DNS names. The concept of the tunnel broker
was first presented at Orlando's IETF in December 1998. Two
implementations were demonstrated during the Grenoble IPng & NGtrans
interim meeting.

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-broker-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-broker-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 09:15:35 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 JAA10868
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 09:15:35 -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 HAA17736;
	Thu, 14 Sep 2000 07:15:30 -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 GAA05005;
	Thu, 14 Sep 2000 06:14:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EDCxY04482
	for ngtrans-dist; Thu, 14 Sep 2000 06:12:59 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EDCqH04475
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:12:52 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA26122
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:12:52 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA20620
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:12:51 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id XAA05557;
	Thu, 14 Sep 2000 23:10:47 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id AAA06611;
	Fri, 15 Sep 2000 00:12:43 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58YNZ6>; Fri, 15 Sep 2000 00:12:45 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB24F@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) DSTM addressing 
Date: Fri, 15 Sep 2000 00:12:45 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E4D.78A83AE0"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E4D.78A83AE0
Content-Type: text/plain;
	charset="iso-8859-1"

Hello George and DSTM authors, 

Thanks for the comments on the draft and sorry for the very
late reply. 

I do believe it is important to come up with a solution / 
recommendation for handling the IPv4 address assignment
based on IPv4 hosts' DNS lookups. Jim mentioned that there
will be a draft ready for San Diego, would it be possible
to have something there to address this problem ?

Erik and myself discussed it briefly and we thought that 
one way to do it may be to allocate IPv4 addresses for a 
"short" time, and let the IPv6 host request the time extension 
if it sees that it still needs it (ie. if it is actually 
a legidimate communication with an IPv4 host). 

Of course the length of time for the initial allocation 
would depend on how many IPv4 addresses are in the pool
amongst other factors, and perhaps it should be configurable
in the AIIH server. 

I don't know how feasible this is but it would be good to 
hear people's opinions. 

Cheers,
Hesham




------_=_NextPart_001_01C01E4D.78A83AE0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>DSTM addressing </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hello George and DSTM authors, </FONT>
</P>

<P><FONT SIZE=2>Thanks for the comments on the draft and sorry for the very</FONT>
<BR><FONT SIZE=2>late reply. </FONT>
</P>

<P><FONT SIZE=2>I do believe it is important to come up with a solution / </FONT>
<BR><FONT SIZE=2>recommendation for handling the IPv4 address assignment</FONT>
<BR><FONT SIZE=2>based on IPv4 hosts' DNS lookups. Jim mentioned that there</FONT>
<BR><FONT SIZE=2>will be a draft ready for San Diego, would it be possible</FONT>
<BR><FONT SIZE=2>to have something there to address this problem ?</FONT>
</P>

<P><FONT SIZE=2>Erik and myself discussed it briefly and we thought that </FONT>
<BR><FONT SIZE=2>one way to do it may be to allocate IPv4 addresses for a </FONT>
<BR><FONT SIZE=2>&quot;short&quot; time, and let the IPv6 host request the time extension </FONT>
<BR><FONT SIZE=2>if it sees that it still needs it (ie. if it is actually </FONT>
<BR><FONT SIZE=2>a legidimate communication with an IPv4 host). </FONT>
</P>

<P><FONT SIZE=2>Of course the length of time for the initial allocation </FONT>
<BR><FONT SIZE=2>would depend on how many IPv4 addresses are in the pool</FONT>
<BR><FONT SIZE=2>amongst other factors, and perhaps it should be configurable</FONT>
<BR><FONT SIZE=2>in the AIIH server. </FONT>
</P>

<P><FONT SIZE=2>I don't know how feasible this is but it would be good to </FONT>
<BR><FONT SIZE=2>hear people's opinions. </FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Hesham</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C01E4D.78A83AE0--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 09:22: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 JAA11061
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 09:22:58 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA20721;
	Thu, 14 Sep 2000 07:22:50 -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 GAA05433;
	Thu, 14 Sep 2000 06:21:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EDKTm04538
	for ngtrans-dist; Thu, 14 Sep 2000 06:20:29 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EDKMH04531
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:20:23 -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 GAA26601
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:20:23 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA19642
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:20:20 -0600 (MDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id XAA05751;
	Thu, 14 Sep 2000 23:17:40 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id AAA07039;
	Fri, 15 Sep 2000 00:19:38 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58YN7K>; Fri, 15 Sep 2000 00:19:40 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB250@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Date: Fri, 15 Sep 2000 00:19:41 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E4E.709A59E0"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E4E.709A59E0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi George, Alan and Scott

I have a couple of questions on draft-tsirtsis-v4-over-mipv6-00.txt, 
How does an IPv6 MN inform its HA that it should intercept
any IPv4 packets coming to its IPv4 "home" subnet ?

I understand you are not using MIPv4 of course, so I guess
something needs to be done to trigger the HA to send proxy
ARP so it can receive packets destined to that (IPv6 MN's)
IPv4 address and map them to the MN's IPv6 home address. 

Also do you allow the IPv6 MN to acquire addresses from the 
foreign domain ? If you do then of course you would get better
route optimisation, but I know there are complications because
we have a similar problem to solve in our draft. 

Cheers,
Hesham

------_=_NextPart_001_01C01E4E.709A59E0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi George, Alan and Scott</FONT>
</P>

<P><FONT SIZE=2>I have a couple of questions on draft-tsirtsis-v4-over-mipv6-00.txt, </FONT>
<BR><FONT SIZE=2>How does an IPv6 MN inform its HA that it should intercept</FONT>
<BR><FONT SIZE=2>any IPv4 packets coming to its IPv4 &quot;home&quot; subnet ?</FONT>
</P>

<P><FONT SIZE=2>I understand you are not using MIPv4 of course, so I guess</FONT>
<BR><FONT SIZE=2>something needs to be done to trigger the HA to send proxy</FONT>
<BR><FONT SIZE=2>ARP so it can receive packets destined to that (IPv6 MN's)</FONT>
<BR><FONT SIZE=2>IPv4 address and map them to the MN's IPv6 home address. </FONT>
</P>

<P><FONT SIZE=2>Also do you allow the IPv6 MN to acquire addresses from the </FONT>
<BR><FONT SIZE=2>foreign domain ? If you do then of course you would get better</FONT>
<BR><FONT SIZE=2>route optimisation, but I know there are complications because</FONT>
<BR><FONT SIZE=2>we have a similar problem to solve in our draft. </FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Hesham</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01E4E.709A59E0--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 09:37: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 JAA11641
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 09:37:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA26827;
	Thu, 14 Sep 2000 07:37:50 -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 GAA03358;
	Thu, 14 Sep 2000 06:36:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EDZIr04589
	for ngtrans-dist; Thu, 14 Sep 2000 06:35:18 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EDZBH04582
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:35:11 -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 GAA28034
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:35:11 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA05363
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:35:10 -0700 (PDT)
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 e8EDYku29774;
	Thu, 14 Sep 2000 15:34:47 +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 PAA05241;
	Thu, 14 Sep 2000 15:34:46 +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 PAA93402;
	Thu, 14 Sep 2000 15:36:03 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141336.PAA93402@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) DSTM addressing 
In-reply-to: Your message of Fri, 15 Sep 2000 00:12:45 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB24F@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 15:36:03 +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:

   I do believe it is important to come up with a solution / 
   recommendation for handling the IPv4 address assignment
   based on IPv4 hosts' DNS lookups.

=> I believe this is about the removed scenario 2 aka AIIH.

   Jim mentioned that there
   will be a draft ready for San Diego, would it be possible
   to have something there to address this problem ?
   
=> it was in previous DSTM drafts (then it is still available,
if you can't get previous drafts, I can send them to you).

   Erik and myself discussed it briefly and we thought that 
   one way to do it may be to allocate IPv4 addresses for a 
   "short" time, and let the IPv6 host request the time extension 
   if it sees that it still needs it (ie. if it is actually 
   a legitimate communication with an IPv4 host). 
   
=> there are many possible policies but the only real problem is
that there is a bit easy to consume the whole IPv4 address pool,
even with a short time, ie. there is a possible denial of service attack.

   Of course the length of time for the initial allocation 
   would depend on how many IPv4 addresses are in the pool
   amongst other factors, and perhaps it should be configurable
   in the AIIH server. 
   
=> if this can't avoid the DOS, it has a little interest.

   I don't know how feasible this is

=> just need a processor which can handle basic arithmetic operations (:-).

   but it would be good to hear people's opinions. 
   
=> now you know mine... This is a problem shared by any scheme where
allocations can be triggered by an action "from the outside".

Regards

Francis.Dupont@enst-bretagne.fr

PS: the scenario 1 without DHCPv6 is already implemented and works well.


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 09:45:35 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 JAA11925
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 09:45:35 -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 HAA00048;
	Thu, 14 Sep 2000 07:45:30 -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 GAA09850;
	Thu, 14 Sep 2000 06:44:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EDh9j04628
	for ngtrans-dist; Thu, 14 Sep 2000 06:43:09 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EDh2H04621
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:43:02 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA28630
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:43:02 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA27849
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 06:43:01 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id XAA06267;
	Thu, 14 Sep 2000 23:40:22 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id AAA08379;
	Fri, 15 Sep 2000 00:42:19 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58Y3D0>; Fri, 15 Sep 2000 00:42:22 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB252@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) DSTM addressing 
Date: Fri, 15 Sep 2000 00:42:22 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E51.9BC69180"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E51.9BC69180
Content-Type: text/plain;
	charset="iso-8859-1"



 In your previous mail you wrote:

   I do believe it is important to come up with a solution / 
   recommendation for handling the IPv4 address assignment
   based on IPv4 hosts' DNS lookups.

=> I believe this is about the removed scenario 2 aka AIIH.

That's correct.


   Jim mentioned that there
   will be a draft ready for San Diego, would it be possible
   to have something there to address this problem ?
   
=> it was in previous DSTM drafts (then it is still available,
if you can't get previous drafts, I can send them to you).

yes I know, but I meant there will be a new draft that includes 
the removed option form the old DSTM draft. Or that was my 
understanding from what Jim said earlier.


   Of course the length of time for the initial allocation 
   would depend on how many IPv4 addresses are in the pool
   amongst other factors, and perhaps it should be configurable
   in the AIIH server. 
   
=> if this can't avoid the DOS, it has a little interest.

I guess that's why I brought it up, because we're trying to 
avoid DOS. So are you saying that even if that time is made very 
short (2-5 seconds ?) then it still wouldn't work ?


------_=_NextPart_001_01C01E51.9BC69180
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) DSTM addressing </TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&nbsp;In your previous mail you wrote:</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; I do believe it is important to come up with a solution / </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; recommendation for handling the IPv4 address assignment</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; based on IPv4 hosts' DNS lookups.</FONT>
</P>

<P><FONT SIZE=2>=&gt; I believe this is about the removed scenario 2 aka AIIH.</FONT>
</P>

<P><FONT SIZE=2>That's correct.</FONT>
</P>
<BR>

<P><FONT SIZE=2>&nbsp;&nbsp; Jim mentioned that there</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; will be a draft ready for San Diego, would it be possible</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; to have something there to address this problem ?</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=2>=&gt; it was in previous DSTM drafts (then it is still available,</FONT>
<BR><FONT SIZE=2>if you can't get previous drafts, I can send them to you).</FONT>
</P>

<P><FONT SIZE=2>yes I know, but I meant there will be a new draft that includes </FONT>
<BR><FONT SIZE=2>the removed option form the old DSTM draft. Or that was my </FONT>
<BR><FONT SIZE=2>understanding from what Jim said earlier.</FONT>
</P>
<BR>

<P><FONT SIZE=2>&nbsp;&nbsp; Of course the length of time for the initial allocation </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; would depend on how many IPv4 addresses are in the pool</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; amongst other factors, and perhaps it should be configurable</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; in the AIIH server. </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=2>=&gt; if this can't avoid the DOS, it has a little interest.</FONT>
</P>

<P><FONT SIZE=2>I guess that's why I brought it up, because we're trying to </FONT>
<BR><FONT SIZE=2>avoid DOS. So are you saying that even if that time is made very </FONT>
<BR><FONT SIZE=2>short (2-5 seconds ?) then it still wouldn't work ?</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01E51.9BC69180--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 10:03:36 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 KAA12265
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 10:03:36 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA07568;
	Thu, 14 Sep 2000 08:03:31 -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 HAA08952;
	Thu, 14 Sep 2000 07:02:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EE1KR04669
	for ngtrans-dist; Thu, 14 Sep 2000 07:01:20 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EE1DH04662
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:01:13 -0700 (PDT)
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 HAA11711
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:01:13 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA14875
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:01:12 -0700 (PDT)
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 e8EE0vu18761;
	Thu, 14 Sep 2000 16:00:57 +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 QAA05525;
	Thu, 14 Sep 2000 16:00:54 +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 QAA93506;
	Thu, 14 Sep 2000 16:02:11 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141402.QAA93506@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
In-reply-to: Your message of Fri, 15 Sep 2000 00:19:41 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB250@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 16:02:11 +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:

   I have a couple of questions on draft-tsirtsis-v4-over-mipv6-00.txt, 
   How does an IPv6 MN inform its HA that it should intercept
   any IPv4 packets coming to its IPv4 "home" subnet ?
   
=> it doesn't need to do this and there is no IPv4 home subnet.
The IPv4 traffic goes to the Tunnel End Point and is encapsulated &
(directly) routed to the Mobile Node. The IPv6 mobility layer
knows *nothing* about IPv4 and the IPv4 layer knows *nothing* about
mobility, the only interaction between them is the TEP should be
a correspondent and routing from the TEP to the MN should be optimized.

   I understand you are not using MIPv4 of course, so I guess
   something needs to be done to trigger the HA to send proxy
   ARP so it can receive packets destined to that (IPv6 MN's)
   IPv4 address and map them to the MN's IPv6 home address. 
   
=> nothing is needed. TEP and HA functions can be done by one or
two boxes (same box is more complex and a bit more efficient).
I think you don't understand how the TEP gets IPv4 traffic:
it is the router for the IPv4 prefix. The HA is different, it is
a router attached to the link where is the prefix, if there is another
router on the link then the traffic can come through it (here again
you can make this impossible and get a small avantage with more
operational complexity).

   Also do you allow the IPv6 MN to acquire addresses from the 
   foreign domain ?

=> split functions -> full freedom (I can say the foreign domain is
an IPv6 notion which is not known by IPv4 too :-).

   If you do then of course you would get better
   route optimisation, but I know there are complications because
   we have a similar problem to solve in our draft. 
   
=> I believe this is easier in George's draft because the IPv4/TEP
selection is done by DSTM/DHCPv6 which can use or ignore mobile
IPv6 issues. (Current proposal doesn't provide a way for the DSTM
client to give the IPv4 address of its future IPv4 peer, it is an
issue or just a feature?)

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 10:19:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12802
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 10:19:00 -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 IAA15431;
	Thu, 14 Sep 2000 08:18: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 HAA13241;
	Thu, 14 Sep 2000 07:17:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EEE6r04768
	for ngtrans-dist; Thu, 14 Sep 2000 07:14:06 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EEDxH04761
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:13:59 -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 HAA09565
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:13:56 -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 IAA12908
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:13:55 -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 e8EEDku21252;
	Thu, 14 Sep 2000 16:13:46 +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 QAA05707;
	Thu, 14 Sep 2000 16:13:46 +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 QAA93595;
	Thu, 14 Sep 2000 16:15:04 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141415.QAA93595@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) DSTM addressing 
In-reply-to: Your message of Fri, 15 Sep 2000 00:42:22 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB252@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 16:15:03 +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:

=> can you send *only* the text version (no HTML please)?
   
      Jim mentioned that there
      will be a draft ready for San Diego, would it be possible
      to have something there to address this problem ?
      
   => it was in previous DSTM drafts (then it is still available,
   if you can't get previous drafts, I can send them to you).
   
   yes I know, but I meant there will be a new draft that includes 
   the removed option form the old DSTM draft. Or that was my 
   understanding from what Jim said earlier.
   
=> of course the removal is a tactical one, our idea was/is to get a
simpler document without known issue, to do a last call and to publish it,
then to come back to AIIH/scenario 2 after. As you can see we still are
at the first step (:-).
   
      Of course the length of time for the initial allocation 
      would depend on how many IPv4 addresses are in the pool
      amongst other factors, and perhaps it should be configurable
      in the AIIH server. 
      
   => if this can't avoid the DOS, it has a little interest.
   
   I guess that's why I brought it up, because we're trying to 
   avoid DOS. So are you saying that even if that time is made very 
   short (2-5 seconds ?) then it still wouldn't work ?

=> I am saying that. It is very hard to avoid DOS attacks... Perhaps
it is not possible in this case? (for me the problem is open)

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 10:21:54 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 KAA12855
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 10:21:54 -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 IAA16945;
	Thu, 14 Sep 2000 08:21:50 -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 HAA14057;
	Thu, 14 Sep 2000 07:20:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EEHEY04777
	for ngtrans-dist; Thu, 14 Sep 2000 07:17:14 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EEH6H04770
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:17:06 -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 HAA02096
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:17:06 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA22670
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:17:00 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id AAA07115;
	Fri, 15 Sep 2000 00:14:21 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id BAA11088;
	Fri, 15 Sep 2000 01:16:19 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58Y3PF>; Fri, 15 Sep 2000 01:16:22 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB254@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>,
        "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
Cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 01:16:21 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E56.5B626650"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E56.5B626650
Content-Type: text/plain;
	charset="iso-8859-1"

Francis,

Thanks for the reply, please see my comments below. 

 In your previous mail you wrote:

   I have a couple of questions on draft-tsirtsis-v4-over-mipv6-00.txt, 
   How does an IPv6 MN inform its HA that it should intercept
   any IPv4 packets coming to its IPv4 "home" subnet ?
   
=> it doesn't need to do this and there is no IPv4 home subnet.
The IPv4 traffic goes to the Tunnel End Point and is encapsulated &
(directly) routed to the Mobile Node. The IPv6 mobility layer
knows *nothing* about IPv4 and the IPv4 layer knows *nothing* about
mobility, the only interaction between them is the TEP should be
a correspondent and routing from the TEP to the MN should be optimized.

   I understand you are not using MIPv4 of course, so I guess
   something needs to be done to trigger the HA to send proxy
   ARP so it can receive packets destined to that (IPv6 MN's)
   IPv4 address and map them to the MN's IPv6 home address. 
   
=> nothing is needed. TEP and HA functions can be done by one or
two boxes (same box is more complex and a bit more efficient).
I think you don't understand how the TEP gets IPv4 traffic:
it is the router for the IPv4 prefix. The HA is different, it is
a router attached to the link where is the prefix, if there is another
router on the link then the traffic can come through it (here again
you can make this impossible and get a small avantage with more
operational complexity).


Ok, let me explain properly what I meant. My question
is: If an IPv6 MN is in a foreign domain. can it request
an IPv4 address from it's home domain ? ie. Home AIIH ?
If the answer is yes, then how do IPv4 packets addressed to
that IPv4 address get routed to the IPv6 MN's subnet in the 
foreign domain ?
So I'm talking about incoming packets. Have I missed something ? 

------_=_NextPart_001_01C01E56.5B626650
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Francis,</FONT>
</P>

<P><FONT SIZE=2>Thanks for the reply, please see my comments below. </FONT>
</P>

<P><FONT SIZE=2>&nbsp;In your previous mail you wrote:</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; I have a couple of questions on draft-tsirtsis-v4-over-mipv6-00.txt, </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; How does an IPv6 MN inform its HA that it should intercept</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; any IPv4 packets coming to its IPv4 &quot;home&quot; subnet ?</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=2>=&gt; it doesn't need to do this and there is no IPv4 home subnet.</FONT>
<BR><FONT SIZE=2>The IPv4 traffic goes to the Tunnel End Point and is encapsulated &amp;</FONT>
<BR><FONT SIZE=2>(directly) routed to the Mobile Node. The IPv6 mobility layer</FONT>
<BR><FONT SIZE=2>knows *nothing* about IPv4 and the IPv4 layer knows *nothing* about</FONT>
<BR><FONT SIZE=2>mobility, the only interaction between them is the TEP should be</FONT>
<BR><FONT SIZE=2>a correspondent and routing from the TEP to the MN should be optimized.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; I understand you are not using MIPv4 of course, so I guess</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; something needs to be done to trigger the HA to send proxy</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; ARP so it can receive packets destined to that (IPv6 MN's)</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; IPv4 address and map them to the MN's IPv6 home address. </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=2>=&gt; nothing is needed. TEP and HA functions can be done by one or</FONT>
<BR><FONT SIZE=2>two boxes (same box is more complex and a bit more efficient).</FONT>
<BR><FONT SIZE=2>I think you don't understand how the TEP gets IPv4 traffic:</FONT>
<BR><FONT SIZE=2>it is the router for the IPv4 prefix. The HA is different, it is</FONT>
<BR><FONT SIZE=2>a router attached to the link where is the prefix, if there is another</FONT>
<BR><FONT SIZE=2>router on the link then the traffic can come through it (here again</FONT>
<BR><FONT SIZE=2>you can make this impossible and get a small avantage with more</FONT>
<BR><FONT SIZE=2>operational complexity).</FONT>
</P>
<BR>

<P><FONT SIZE=2>Ok, let me explain properly what I meant. My question</FONT>
<BR><FONT SIZE=2>is: If an IPv6 MN is in a foreign domain. can it request</FONT>
<BR><FONT SIZE=2>an IPv4 address from it's home domain ? ie. Home AIIH ?</FONT>
<BR><FONT SIZE=2>If the answer is yes, then how do IPv4 packets addressed to</FONT>
<BR><FONT SIZE=2>that IPv4 address get routed to the IPv6 MN's subnet in the </FONT>
<BR><FONT SIZE=2>foreign domain ?</FONT>
<BR><FONT SIZE=2>So I'm talking about incoming packets. Have I missed something ? </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01E56.5B626650--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 10:28: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 KAA12987
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 10:28: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 IAA20099;
	Thu, 14 Sep 2000 08:28:52 -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 HAA16333;
	Thu, 14 Sep 2000 07:28:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EEQhu04845
	for ngtrans-dist; Thu, 14 Sep 2000 07:26:43 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EEQaH04838
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:26:36 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA03040
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:26:36 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA10618
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:26:35 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id AAA07349;
	Fri, 15 Sep 2000 00:23:56 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id BAA11657;
	Fri, 15 Sep 2000 01:25:54 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58Y3S2>; Fri, 15 Sep 2000 01:25:56 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB255@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) DSTM addressing 
Date: Fri, 15 Sep 2000 01:25:55 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E57.B18B0540"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E57.B18B0540
Content-Type: text/plain;
	charset="iso-8859-1"


 In your previous mail you wrote:

=> can you send *only* the text version (no HTML please)?

Sorry, forgot that. I hope this is working now.

=> I am saying that. It is very hard to avoid DOS attacks... Perhaps
it is not possible in this case? (for me the problem is open)

Yes I agree with you but I'm trying to improve the current situation. 
I think a 50 % fix is better than 0. 
Of course a complete solution would be ideal.

Cheers,
Hesham 

------_=_NextPart_001_01C01E57.B18B0540
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) DSTM addressing </TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>&nbsp;In your previous mail you wrote:</FONT>
</P>

<P><FONT SIZE=2>=&gt; can you send *only* the text version (no HTML please)?</FONT>
</P>

<P><FONT SIZE=2>Sorry, forgot that. I hope this is working now.</FONT>
</P>

<P><FONT SIZE=2>=&gt; I am saying that. It is very hard to avoid DOS attacks... Perhaps</FONT>
<BR><FONT SIZE=2>it is not possible in this case? (for me the problem is open)</FONT>
</P>

<P><FONT SIZE=2>Yes I agree with you but I'm trying to improve the current situation. </FONT>
<BR><FONT SIZE=2>I think a 50 % fix is better than 0. </FONT>
<BR><FONT SIZE=2>Of course a complete solution would be ideal.</FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Hesham </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01E57.B18B0540--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 12:58: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 MAA18955
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 12:58:22 -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 KAA07876;
	Thu, 14 Sep 2000 10:58:15 -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 JAA08160;
	Thu, 14 Sep 2000 09:16:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EGEme05025
	for ngtrans-dist; Thu, 14 Sep 2000 09:14:48 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EGEfH05018
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:14:41 -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 JAA04235
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:14:41 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA13858
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:14:38 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id CAA10336;
	Fri, 15 Sep 2000 02:11:58 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id DAA18443;
	Fri, 15 Sep 2000 03:13:56 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58YPYA>; Fri, 15 Sep 2000 03:13:58 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB258@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 03:13:58 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E66.C9844440"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E66.C9844440
Content-Type: text/plain;
	charset="iso-8859-1"

Hi George,

>
> => they are routed according to IPv4 routing to the TEP, then
> they are IPv6 routed to the MN through the HA (if not optimized) or
> directly with a source-route (if optimized, I don't see a good
> reason to be and stay not optimized). If the TEP and the HA
> are colocated then you have twice the code on the box but the
> IPv6 routing is garanteed to be optimized (in fact as good as it can be).
>
        Francis covered the case in which the Home Network also runs DSTM.
In this case the MN will get an IPv4 address back and then it will have to
use IPv4 over IPv6(tep) over MIPv6 in order to send the packet to the Home
Agent or IPv4 over IPv6(tep) if the home TEP is directly reachable.

        The other case is when the Home Network DOES NOT run DSTM but it
does run DHCPv4. Is that what you are thinking? In this case the MN needs to
send a DHCPv4 packet over a MIPv6 reverse tunnel and get an IPv4 address.
This addressed will need to be relayed to the MN by the HA, which will also
now have to run proxy ARP for the IPv4 address of the MN in order to capture
incoming IPv4 packets. I think that one might be able to implement something
like a Home Agent that supports Mobile IPv4 and Mobile IPv6 but tunnels
everything over MIPv6 in order to accommodate the above case but I tried to
avoid this case in the draft since I was aiming for something simple.

=> Yes that is one of the cases I had in mind but not all.
Unfortunately, I think we might need some complexity here ;)
That's why I was wondering about the HA, because I understood
that you didn't want to run MIPv4 at all. Doing a proxy ARP
needs to be triggered by something. In MIPv4 that is a home
registration of course. That's what I'm missing.

This scenario made me think more about how TEP in general
maps IPv4 and IPv6 addresses.

Even in the other case where there is DSTM at home, If the
IPv6 node is in the foreign domain, does it not still need
to reverse tunnel through the Home TEP ? Otherwise how does 
the home TEP do the mapping ?
If it sends packets directly in its foriegn domain, the incoming
IPv4 packets ( coming into the home domain) will be received by
the TEP and it will have no idea how to map them.
This is a similar problem to what we try to address in our
proposal for combining SIIT and DSTM.
Maybe the TEP needs to have a similar client to be able to
request this mapping information from the AIIH server.

Do you agree ?

Cheers,
Hesham

------_=_NextPart_001_01C01E66.C9844440
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) RE: </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi George,</FONT>
</P>

<P><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; =&gt; they are routed according to IPv4 routing to the TEP, then</FONT>
<BR><FONT SIZE=2>&gt; they are IPv6 routed to the MN through the HA (if not optimized) or</FONT>
<BR><FONT SIZE=2>&gt; directly with a source-route (if optimized, I don't see a good</FONT>
<BR><FONT SIZE=2>&gt; reason to be and stay not optimized). If the TEP and the HA</FONT>
<BR><FONT SIZE=2>&gt; are colocated then you have twice the code on the box but the</FONT>
<BR><FONT SIZE=2>&gt; IPv6 routing is garanteed to be optimized (in fact as good as it can be).</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Francis covered the case in which the Home Network also runs DSTM.</FONT>
<BR><FONT SIZE=2>In this case the MN will get an IPv4 address back and then it will have to</FONT>
<BR><FONT SIZE=2>use IPv4 over IPv6(tep) over MIPv6 in order to send the packet to the Home</FONT>
<BR><FONT SIZE=2>Agent or IPv4 over IPv6(tep) if the home TEP is directly reachable.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The other case is when the Home Network DOES NOT run DSTM but it</FONT>
<BR><FONT SIZE=2>does run DHCPv4. Is that what you are thinking? In this case the MN needs to</FONT>
<BR><FONT SIZE=2>send a DHCPv4 packet over a MIPv6 reverse tunnel and get an IPv4 address.</FONT>
<BR><FONT SIZE=2>This addressed will need to be relayed to the MN by the HA, which will also</FONT>
<BR><FONT SIZE=2>now have to run proxy ARP for the IPv4 address of the MN in order to capture</FONT>
<BR><FONT SIZE=2>incoming IPv4 packets. I think that one might be able to implement something</FONT>
<BR><FONT SIZE=2>like a Home Agent that supports Mobile IPv4 and Mobile IPv6 but tunnels</FONT>
<BR><FONT SIZE=2>everything over MIPv6 in order to accommodate the above case but I tried to</FONT>
<BR><FONT SIZE=2>avoid this case in the draft since I was aiming for something simple.</FONT>
</P>

<P><FONT SIZE=2>=&gt; Yes that is one of the cases I had in mind but not all.</FONT>
<BR><FONT SIZE=2>Unfortunately, I think we might need some complexity here ;)</FONT>
<BR><FONT SIZE=2>That's why I was wondering about the HA, because I understood</FONT>
<BR><FONT SIZE=2>that you didn't want to run MIPv4 at all. Doing a proxy ARP</FONT>
<BR><FONT SIZE=2>needs to be triggered by something. In MIPv4 that is a home</FONT>
<BR><FONT SIZE=2>registration of course. That's what I'm missing.</FONT>
</P>

<P><FONT SIZE=2>This scenario made me think more about how TEP in general</FONT>
<BR><FONT SIZE=2>maps IPv4 and IPv6 addresses.</FONT>
</P>

<P><FONT SIZE=2>Even in the other case where there is DSTM at home, If the</FONT>
<BR><FONT SIZE=2>IPv6 node is in the foreign domain, does it not still need</FONT>
<BR><FONT SIZE=2>to reverse tunnel through the Home TEP ? Otherwise how does </FONT>
<BR><FONT SIZE=2>the home TEP do the mapping ?</FONT>
<BR><FONT SIZE=2>If it sends packets directly in its foriegn domain, the incoming</FONT>
<BR><FONT SIZE=2>IPv4 packets ( coming into the home domain) will be received by</FONT>
<BR><FONT SIZE=2>the TEP and it will have no idea how to map them.</FONT>
<BR><FONT SIZE=2>This is a similar problem to what we try to address in our</FONT>
<BR><FONT SIZE=2>proposal for combining SIIT and DSTM.</FONT>
<BR><FONT SIZE=2>Maybe the TEP needs to have a similar client to be able to</FONT>
<BR><FONT SIZE=2>request this mapping information from the AIIH server.</FONT>
</P>

<P><FONT SIZE=2>Do you agree ?</FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Hesham</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01E66.C9844440--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 12:58: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 MAA18967
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 12:58:56 -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 KAA08205;
	Thu, 14 Sep 2000 10:58:50 -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 HAA13678;
	Thu, 14 Sep 2000 07:54:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EErQd04907
	for ngtrans-dist; Thu, 14 Sep 2000 07:53:26 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EErJH04900
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:53:20 -0700 (PDT)
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 HAA13598
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:53:20 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA06524
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 07:53:18 -0700 (PDT)
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 e8EEr4u24249;
	Thu, 14 Sep 2000 16:53:05 +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 QAA06207;
	Thu, 14 Sep 2000 16:52:58 +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 QAA93782;
	Thu, 14 Sep 2000 16:54:16 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141454.QAA93782@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) RE: 
In-reply-to: Your message of Fri, 15 Sep 2000 01:16:21 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB254@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 16:54:16 +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:

   Ok, let me explain properly what I meant. My question
   is: If an IPv6 MN is in a foreign domain. can it request
   an IPv4 address from it's home domain ? ie. Home AIIH ?

=> it can do what it wants. I think there are three policies:
 - local (ie. foreign domain). Simple but perhaps too simple.
 - home (ie. home domain/AIIH). Not hard, this can be a good
   or a bad choice...
 - close to the peer. Harder but the best if there is only one peer.
   (of course the knowledge of what/where the peer is is needed).

   If the answer is yes, then how do IPv4 packets addressed to
   that IPv4 address get routed to the IPv6 MN's subnet in the 
   foreign domain ?

=> they are routed according to IPv4 routing to the TEP, then
they are IPv6 routed to the MN through the HA (if not optimized) or
directly with a source-route (if optimized, I don't see a good
reason to be and stay not optimized). If the TEP and the HA
are colocated then you have twice the code on the box but the
IPv6 routing is garanteed to be optimized (in fact as good as it can be).

   So I'm talking about incoming packets.

=> for outcoming packets no IPv6 routing optimization is possible
(it is already optimal :-).

   Have I missed something ?

=> no but there are other points:
 - route optimization is not good because it is faster, this gives
   a greater MTU too.
 - you can play with IPv4 routing too (the position of the TEP is important)
 - there are possible gains on the security side, MN-HA critical
   communications are already secure, MN-TEP can/could/should be secure too.
   This has a cost in the setup phase (again colocation is more complex
   but has a clear benefit).

Regards

Francis.Dupont@enst-bretagne.fr

PS: the key is independence. You can put things (HA, TEP, AIIH server, ...)
where you'd like and you can optimize some particular cases as you'd like.
I believe we need concrete examples of deployments (ie. first operational
experience) in order to go further (ie. play and win with the different
service locations). George? your turn!


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 13:05:21 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 NAA19034
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 13:05:21 -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 LAA11921;
	Thu, 14 Sep 2000 11:05:15 -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 JAA07148;
	Thu, 14 Sep 2000 09:46:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EGk7i05087
	for ngtrans-dist; Thu, 14 Sep 2000 09:46:07 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EGk0H05080
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:46:01 -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 JAA11556
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:46:00 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gandalf.axion.bt.co.uk (gandalf.axion.bt.co.uk [132.146.17.29])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA25419
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:45:59 -0700 (PDT)
Received: from cbtlipnt01.btlabs.bt.co.uk by gandalf (local) with ESMTP;
          Thu, 14 Sep 2000 17:45:02 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2652.35) id <S5ZDNBNC>;
          Thu, 14 Sep 2000 17:45:16 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5B0B@mbtlipnt02.btlabs.bt.co.uk>
To: Hesham.Soliman@ericsson.com.au, george.tsirtsis@bt.com
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) RE: 
Date: Thu, 14 Sep 2000 17:41:20 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

 

-----Original Message-----
From: Hesham Soliman (EPA)
To: 'george.tsirtsis@bt.com'
Cc: ngtrans@sunroof.eng.sun.com
Sent: 14/9/2000 5:13 ii
Subject: RE: (ngtrans) RE: 

Hi George, 
...
=> Yes that is one of the cases I had in mind but not all. 
Unfortunately, I think we might need some complexity here ;) 
That's why I was wondering about the HA, because I understood 
that you didn't want to run MIPv4 at all. Doing a proxy ARP 
needs to be triggered by something. In MIPv4 that is a home 
registration of course. That's what I'm missing. 

GT> Yes that it the case.

This scenario made me think more about how TEP in general 
maps IPv4 and IPv6 addresses. 

Even in the other case where there is DSTM at home, If the 
IPv6 node is in the foreign domain, does it not still need 
to reverse tunnel through the Home TEP ? Otherwise how does 
the home TEP do the mapping ? 

GT> It needs to send a DHCPv6 packet to its Home Net requesting a DHCPv4
address. The TEP tunnel at the MN's side terminates on the MN's Home IPv6
address. So I do not see a problem there...

If it sends packets directly in its foriegn domain, the incoming 
IPv4 packets ( coming into the home domain) will be received by 
the TEP and it will have no idea how to map them. 

GT> The TEP knows the Home IPv6 Address of the MN (from the first outgoing
packet), yes? So incoming v4 packets are encapsulated by the TEP and
forwarded to MN's Home IPv6 address, they are then, picked up by the HA and
forwarded to MN's current location using MIPv6. The MN can even send a BU to
the TEP so packets go straight to it... 

I do not see the problem?? but I might be missing the point...

George




From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 13:11: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 NAA19103
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 13:11:50 -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 LAA15226;
	Thu, 14 Sep 2000 11:11:42 -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 IAA22364;
	Thu, 14 Sep 2000 08:10:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EF9gX04938
	for ngtrans-dist; Thu, 14 Sep 2000 08:09:42 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EF9ZH04931
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:09:35 -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 IAA25413
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:09:35 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA23814
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:09:34 -0700 (PDT)
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 e8EF9Gu21421;
	Thu, 14 Sep 2000 17:09:17 +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 RAA06430;
	Thu, 14 Sep 2000 17:09:16 +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 RAA93868;
	Thu, 14 Sep 2000 17:10:30 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141510.RAA93868@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) DSTM addressing 
In-reply-to: Your message of Fri, 15 Sep 2000 01:25:55 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB255@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 17:10:30 +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:

    In your previous mail you wrote:
   
   => can you send *only* the text version (no HTML please)?
   
   Sorry, forgot that. I hope this is working now.
   
=> not yet...

   => I am saying that. It is very hard to avoid DOS attacks... Perhaps
   it is not possible in this case? (for me the problem is open)
   
   Yes I agree with you but I'm trying to improve the current situation. 
   I think a 50 % fix is better than 0. 

=> I am afraid that for DOS attacks a 50% known (*) fix is not enough.

   Of course a complete solution would be ideal.
   
=> the only solution I know is to restrict the scenario 2 but this makes
it far less useful then we temporary discarded it.

Regards

Francis.Dupont@enst-bretagne.fr

PS *: known by attackers of course. They can for instance:
 - flood the AIIH server by requests (if legitimate requests can't be
   quicky recognized you are dead).
 - simulate long term connections in order to get a long lifetime
   (ie. you need to use something like IPsec in order to kill junk
    connections and to provide some feedback to the AIIH server).
PPS: I'd like to get George's ideas about scenario 2 deployment. For instance
if the requests may come only from an internal node and/or through an AAA
machinery then DOS problems can be controlled. I know mobile phone
operators like/need AAA (for the last A, sorry :-).


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 13:56: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 NAA19672
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 13:56:27 -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 LAA09178;
	Thu, 14 Sep 2000 11:56:22 -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 IAA24467;
	Thu, 14 Sep 2000 08:55:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EFsln04997
	for ngtrans-dist; Thu, 14 Sep 2000 08:54:47 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EFsfH04990
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:54:41 -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 IAA24202
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:54:41 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gollum.axion.bt.co.uk (gollum.axion.bt.co.uk [132.146.17.41])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA03319
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:54:39 -0600 (MDT)
Received: from cbtlipnt02.btlabs.bt.co.uk by gollum (local) with ESMTP;
          Thu, 14 Sep 2000 16:54:34 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2652.35) id <SWLKC4YZ>;
          Thu, 14 Sep 2000 16:53:15 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5B09@mbtlipnt02.btlabs.bt.co.uk>
To: Hesham.Soliman@ericsson.com.au
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) RE: 
Date: Thu, 14 Sep 2000 16:49:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

Hi Hesham,

I think Francis (thanks!) has made most of the points but see below some
more.

> -----Original Message-----
> From:	Francis Dupont [SMTP:Francis.Dupont@enst-bretagne.fr]
> Sent:	Thursday, September 14, 2000 3:54 PM
> To:	Hesham Soliman (EPA)
> Cc:	'george.tsirtsis@bt.com'; 'ngtrans@sunroof.eng.sun.com'
> Subject:	Re: (ngtrans) RE: 
> 
>  In your previous mail you wrote:
> 
>    Ok, let me explain properly what I meant. My question
>    is: If an IPv6 MN is in a foreign domain. can it request
>    an IPv4 address from it's home domain ? ie. Home AIIH ?
> 
> => it can do what it wants. I think there are three policies:
>  - local (ie. foreign domain). Simple but perhaps too simple.
>  - home (ie. home domain/AIIH). Not hard, this can be a good
>    or a bad choice...
>  - close to the peer. Harder but the best if there is only one peer.
>    (of course the knowledge of what/where the peer is is needed).
> 
	Yes, the MN can decide to send a DHCPv6 over MIPv6 packet to its
home network. I guess you may need reverse tunneling but in principle yes.


>    If the answer is yes, then how do IPv4 packets addressed to
>    that IPv4 address get routed to the IPv6 MN's subnet in the 
>    foreign domain ?
> 
> => they are routed according to IPv4 routing to the TEP, then
> they are IPv6 routed to the MN through the HA (if not optimized) or
> directly with a source-route (if optimized, I don't see a good
> reason to be and stay not optimized). If the TEP and the HA
> are colocated then you have twice the code on the box but the
> IPv6 routing is garanteed to be optimized (in fact as good as it can be).
> 
	Francis covered the case in which the Home Network also runs DSTM.
In this case the MN will get an IPv4 address back and then it will have to
use IPv4 over IPv6(tep) over MIPv6 in order to send the packet to the Home
Agent or IPv4 over IPv6(tep) if the home TEP is directly reachable.

	The other case is when the Home Network DOES NOT run DSTM but it
does run DHCPv4. Is that what you are thinking? In this case the MN needs to
send a DHCPv4 packet over a MIPv6 reverse tunnel and get an IPv4 address.
This addressed will need to be relayed to the MN by the HA, which will also
now have to run proxy ARP for the IPv4 address of the MN in order to capture
incoming IPv4 packets. I think that one might be able to implement something
like a Home Agent that supports Mobile IPv4 and Mobile IPv6 but tunnels
everything over MIPv6 in order to accommodate the above case but I tried to
avoid this case in the draft since I was aiming for something simple.

	Was that you point?

	Regards
	George


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 14:18: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 OAA19960
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 14:18: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 MAA21846;
	Thu, 14 Sep 2000 12:18:49 -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 KAA05886;
	Thu, 14 Sep 2000 10:16:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EHFKF05214
	for ngtrans-dist; Thu, 14 Sep 2000 10:15:20 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EHFDH05207
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 10:15:13 -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 KAA05506
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 10:15:12 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA07396
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 10:15:11 -0700 (PDT)
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 e8EHEvu17529;
	Thu, 14 Sep 2000 19:14:57 +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 TAA07921;
	Thu, 14 Sep 2000 19:14:56 +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 TAA94449;
	Thu, 14 Sep 2000 19:16:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009141716.TAA94449@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) RE: 
In-reply-to: Your message of Fri, 15 Sep 2000 02:37:46 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB256@eaubrnt018.epa.ericsson.se> 
Date: Thu, 14 Sep 2000 19:16:14 +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:

   If there is HTML again then please don't shoot me !

=> there is... Should try a BSD (:-)!
   
   Ok here is exactly what I'm asking about. How do they get routed
   through the HA ?

=> the TEP knows the MN IPv6 address then follows the common rules
for sending a packet to a IPv6 destination (lookup binding cache,
looup destination cache, ...). There is nothing special but the
TEP is likely to be detected/known as a correspondent then routing
is likely to be optimized (ie. the binding cache lookup will succeed).

   Does the Border router or TEP know that this IPv4
   address should be routed to subnet X where the MN's HA is ? 

=> Ah! You should reread the DSTM draft. The TEP encapsulates
IPv4 traffic to the MN into IPv6. The communication between the MN and
the TEP is done by a IPv4 over IPv6 tunnel.

   Because the DSTM draft does not really say how the IPv6-IPv4
   mapping should be done.

=> there is no mapping nor translation. All nodes have a global IPv6
address (at least). A global IPv4 address and a TEP is allocated to
an IPv6 node which needs to communicate with an IPv4 only node.
There is *no* relationship between addresses, the IPv4 address
is just pick up from a pool (this pool can (and will) be smaller
than the number of nodes then scenario 2 has a DOS attack).

   If it only maps it to the COA of the IPv6 node which is what will
   be seen in outgoing packets then it is not very reliable.

=> the IPv4 layer has no knowledge of mobility. The TEP uses the
Home Address of the MN. The COA is only in the binding cache and
is optional (known -> optimized, unknown -> not optimized, ie.
triangular routing via the HA).
I said to George his idea is trivial, should I have said it is too simple (:-)?

   Also in the scenario I mentioned earlier you would
   have to force the IPv6 MN in the foreign domain to reverse tunnel
   through the "home" TEP so that the home TEP would know the mapping.
    
=> no reverse tunnel...

   There is very little in the draft about that.

=> there is very little because there is nothing to explain.

   So that's why I think there are some open issues here

=> there is no issue, only freedom.

   and they depend on two things:
   
   - How does the IPv6 MN acquire the address in a foreign domain
   (Home AIIH vs Foreign AIIH)
   
=> it MAY use a home AIIH or it MAY use a foreign AIIH. The second
one is easier because the proposed tool is DHCPv6 which is a local tool.
The second is a bit harder because current DHCPv6 doesn't work but
you can imagine another way to do it (use AAA for instance).

   - How does the TEP maps the IPv4 and IPv6 addresses.

=> I don't understand your question. The word "map" has too many meanings.

   This has to be done in a reliable way. I don't think it should be
   "guessed" based on the source address in the IPv6 packet.

=> if your problem is the tunnel parameters at the TEP side then there are
two main ways to do it:
 - the TEP is configured by the AIIH server (this is needed in some cases)
 - the TEP gets the addresses from incoming packets from the tunnel (cheap
   because the TEP has to decapsulated them but there is a security issue
   if this is done blindly. I have to add something in the current draft).
The second case is the standard one for scenario 1 with an external
destination (internal destination is special: the TEP is the destination).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 14:39: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 OAA20292
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 14:39:08 -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 MAA03079;
	Thu, 14 Sep 2000 12:39:03 -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 IAA21287;
	Thu, 14 Sep 2000 08:39:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EFca504970
	for ngtrans-dist; Thu, 14 Sep 2000 08:38:36 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EFcTH04963
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:38:29 -0700 (PDT)
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 IAA01044
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:38:28 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA25696
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 08:38:27 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id BAA09337;
	Fri, 15 Sep 2000 01:35:48 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id CAA16217;
	Fri, 15 Sep 2000 02:37:45 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58YPLT>; Fri, 15 Sep 2000 02:37:47 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB256@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>,
        "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
Cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: RE: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 02:37:46 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01E61.BB41DA50"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01E61.BB41DA50
Content-Type: text/plain;
	charset="iso-8859-1"

If there is HTML again then please don't shoot me !
I'm working on it, I'm using a certain product that
works sometimes !!! No naming :)

   Ok, let me explain properly what I meant. My question
   is: If an IPv6 MN is in a foreign domain. can it request
   an IPv4 address from it's home domain ? ie. Home AIIH ?

=> it can do what it wants. I think there are three policies:
 - local (ie. foreign domain). Simple but perhaps too simple.
 - home (ie. home domain/AIIH). Not hard, this can be a good
   or a bad choice...
 - close to the peer. Harder but the best if there is only one peer.
   (of course the knowledge of what/where the peer is is needed).

Yes I agree with all that. But my question is below:

   If the answer is yes, then how do IPv4 packets addressed to
   that IPv4 address get routed to the IPv6 MN's subnet in the 
   foreign domain ?

=> they are routed according to IPv4 routing to the TEP, then
they are IPv6 routed to the MN through the HA (if not optimized) 

Ok here is exactly what I'm asking about. How do they get routed
through the HA ? Does the Border router or TEP know that this IPv4
address should be routed to subnet X where the MN's HA is ? 
Because the DSTM draft does not really say how the IPv6-IPv4
mapping should be done. If it only maps it to the COA of the IPv6
node which is what will be seen in outgoing packets then it is not
very reliable. Also in the scenario I mentioned earlier you would
have to force the IPv6 MN in the foreign domain to reverse tunnel
through the "home" TEP so that the home TEP would know the mapping.
 
There is very little in the draft about that. So that's why I think 
there are some open issues here and they depend on two things:

- How does the IPv6 MN acquire the address in a foreign domain
(Home AIIH vs Foreign AIIH)

- How does the TEP maps the IPv4 and IPv6 addresses. This has
to be done in a reliable way. I don't think it should be "guessed"
based on the source address in the IPv6 packet.



------_=_NextPart_001_01C01E61.BB41DA50
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) RE: </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>If there is HTML again then please don't shoot me !</FONT>
<BR><FONT SIZE=2>I'm working on it, I'm using a certain product that</FONT>
<BR><FONT SIZE=2>works sometimes !!! No naming :)</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; Ok, let me explain properly what I meant. My question</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; is: If an IPv6 MN is in a foreign domain. can it request</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; an IPv4 address from it's home domain ? ie. Home AIIH ?</FONT>
</P>

<P><FONT SIZE=2>=&gt; it can do what it wants. I think there are three policies:</FONT>
<BR><FONT SIZE=2>&nbsp;- local (ie. foreign domain). Simple but perhaps too simple.</FONT>
<BR><FONT SIZE=2>&nbsp;- home (ie. home domain/AIIH). Not hard, this can be a good</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; or a bad choice...</FONT>
<BR><FONT SIZE=2>&nbsp;- close to the peer. Harder but the best if there is only one peer.</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; (of course the knowledge of what/where the peer is is needed).</FONT>
</P>

<P><FONT SIZE=2>Yes I agree with all that. But my question is below:</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; If the answer is yes, then how do IPv4 packets addressed to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; that IPv4 address get routed to the IPv6 MN's subnet in the </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; foreign domain ?</FONT>
</P>

<P><FONT SIZE=2>=&gt; they are routed according to IPv4 routing to the TEP, then</FONT>
<BR><FONT SIZE=2>they are IPv6 routed to the MN through the HA (if not optimized) </FONT>
</P>

<P><FONT SIZE=2>Ok here is exactly what I'm asking about. How do they get routed</FONT>
<BR><FONT SIZE=2>through the HA ? Does the Border router or TEP know that this IPv4</FONT>
<BR><FONT SIZE=2>address should be routed to subnet X where the MN's HA is ? </FONT>
<BR><FONT SIZE=2>Because the DSTM draft does not really say how the IPv6-IPv4</FONT>
<BR><FONT SIZE=2>mapping should be done. If it only maps it to the COA of the IPv6</FONT>
<BR><FONT SIZE=2>node which is what will be seen in outgoing packets then it is not</FONT>
<BR><FONT SIZE=2>very reliable. Also in the scenario I mentioned earlier you would</FONT>
<BR><FONT SIZE=2>have to force the IPv6 MN in the foreign domain to reverse tunnel</FONT>
<BR><FONT SIZE=2>through the &quot;home&quot; TEP so that the home TEP would know the mapping.</FONT>
<BR><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>There is very little in the draft about that. So that's why I think </FONT>
<BR><FONT SIZE=2>there are some open issues here and they depend on two things:</FONT>
</P>

<P><FONT SIZE=2>- How does the IPv6 MN acquire the address in a foreign domain</FONT>
<BR><FONT SIZE=2>(Home AIIH vs Foreign AIIH)</FONT>
</P>

<P><FONT SIZE=2>- How does the TEP maps the IPv4 and IPv6 addresses. This has</FONT>
<BR><FONT SIZE=2>to be done in a reliable way. I don't think it should be &quot;guessed&quot;</FONT>
<BR><FONT SIZE=2>based on the source address in the IPv6 packet.</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C01E61.BB41DA50--


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 14:45:52 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 OAA20405
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 14:45:52 -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 MAA07148;
	Thu, 14 Sep 2000 12:45:44 -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 JAA25513;
	Thu, 14 Sep 2000 09:34:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8EGXrQ05052
	for ngtrans-dist; Thu, 14 Sep 2000 09:33:53 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8EGXlH05045
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:33:47 -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 JAA25386
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:33:46 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from gollum.axion.bt.co.uk (gollum.axion.bt.co.uk [132.146.17.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA20359
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 09:33:46 -0700 (PDT)
Received: from cbtlipnt02.btlabs.bt.co.uk by gollum (local) with ESMTP;
          Thu, 14 Sep 2000 17:34:24 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2652.35) id <SWLKCWQL>;
          Thu, 14 Sep 2000 17:33:06 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5B0A@mbtlipnt02.btlabs.bt.co.uk>
To: Hesham.Soliman@ericsson.com.au, Francis.Dupont@enst-bretagne.fr
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) DSTM addressing 
Date: Thu, 14 Sep 2000 17:29:12 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

 

-----Original Message-----
From: Hesham Soliman (EPA)
To: 'Francis Dupont'
Cc: ngtrans@sunroof.eng.sun.com
Sent: 14/9/2000 3:25 ii
Subject: RE: (ngtrans) DSTM addressing 

...
=> I am saying that. It is very hard to avoid DOS attacks... Perhaps 
it is not possible in this case? (for me the problem is open) 

Yes I agree with you but I'm trying to improve the current situation. 
I think a 50 % fix is better than 0. 
Of course a complete solution would be ideal. 

I think what you suggest (limit initial lifetime of address) is a good idea
and it will help but only up to a point as you also recognise. Even if you
assign an address for say 1 sec you actually need to wait for more than that
(X Sec) before you can reassign it. This is because if the external node
delays session initiation and you re-assign the address to someone else too
fast, the external node might communicate with the wrong internal node. An
attacker can also send you rotating DNS packets matching your assignment
lifetimes...the timing  here is critical and difficult to define...

The trick that DSTM is using for incoming connections is very similar to the
one that NAT-PT uses. It might worth having a look at RFC2766 to see how
that works. The DOS attack problem is not easy to solve here. There are a
few things you can do (in addition to your suggestion) in order to minimise
its effects but nothing I know of will completely remove the problem:

- In DNS set caching time to 0, so external nodes use the assigned address
for a single session and DNS servers do not cache it
- Limit the number of addresses you allow to by assigned for incoming
connections so you can protect outgoing traffic.
- Keep track of external nodes that make requests if possible (you might be
able to identify attackers but not easy...)


Regards
George


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 14 20:32:23 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27879
	for <ngtrans-archive@odin.ietf.org>; Thu, 14 Sep 2000 20:32:22 -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 SAA22421;
	Thu, 14 Sep 2000 18:32:11 -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 RAA13070;
	Thu, 14 Sep 2000 17:31:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) id e8F0UBA05558
	for ngtrans-dist; Thu, 14 Sep 2000 17:30:11 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta0+Sun/8.11.1.Beta0) with ESMTP id e8F0U2H05551
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 17:30:03 -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 RAA04391
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 17:30:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA19010
	for <ngtrans@sunroof.eng.sun.com>; Thu, 14 Sep 2000 17:30:01 -0700 (PDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA24842;
	Thu, 14 Sep 2000 17:29:55 -0700 (PDT)
Message-Id: <200009150029.RAA24842@boreas.isi.edu>
To: IETF-Announce: ;
Subject: (ngtrans) RFC 2921 on 6BONE pTLA and pNLA Formats
Cc: rfc-ed@ISI.EDU, ngtrans@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 14 Sep 2000 17:29:55 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: RFC Editor <rfc-ed@ISI.EDU>


--NextPart


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


        RFC 2921

        Title:	    6BONE pTLA and pNLA Formats (pTLA)
        Author(s):  B. Fink
        Status:     Informational
	Date:       September 2000
        Mailbox:    fink@es.net
        Pages:      7
        Characters: 14218
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-ngtrans-6bone-ptla-00.txt

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


This memo defines how the 6bone uses the 3FFE::/16 IPv6 address
prefix, allocated in RFC 2471, "IPv6 Testing Address Allocation",
to create pseudo Top-Level Aggregation Identifiers (pTLA's) and pseudo
Next-Level Aggregation Identifiers (pNLA's).  

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

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

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

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

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

        help: ways_to_get_rfcs

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


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

...

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

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

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

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

RETRIEVE: rfc
DOC-ID: rfc2921

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

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

--OtherAccess--
--NextPart--


From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 05:15:35 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 FAA16700
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 05:15:34 -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 DAA27121;
	Fri, 15 Sep 2000 03:15:24 -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 CAA01871;
	Fri, 15 Sep 2000 02:15:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8F9EFd05916
	for ngtrans-dist; Fri, 15 Sep 2000 02:14:15 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8F9E9r05909
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 02:14:09 -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 CAA13976
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 02:14:08 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA06109
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 02:14:07 -0700 (PDT)
Received: from cbtlipnt01.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Fri, 15 Sep 2000 10:13:39 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2652.35) id <S5ZDNN3C>;
          Fri, 15 Sep 2000 10:13:38 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A5B11@mbtlipnt02.btlabs.bt.co.uk>
To: Hesham.Soliman@ericsson.com.au
Cc: Francis.Dupont@enst-bretagne.fr, ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 10:09:43 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.35)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

Hesham,

Am I right to say that your issue is generally about incoming connections in
DSTM rather than the DSTM-SIIT and DSTM-MIPv6 drafts?

	....
	You say:
>    Does the Border router or TEP know that this IPv4
>    address should be routed to subnet X where the MN's HA is ? 
> 
	You are talking about incoming sessions yes?
	Here is the diagram from DSTMv1 that described incoming sessions in
detail (removed in v2)

	   DNSv4  AIIH   Y4          Z4
	   DNSv6         Y6
	    |      <. . . . . . . . . |   - ask for the IPv4 address of X
	    |            |            |   - this request arrives to the AIIH
Server
	    |            |            |
	    |            |            |   - if node X does not have already
a
	    |            |            |     temporary IPv4 address assigned
then the
	    |            |            |     AIIH allocates an IPv4 address
and
	    |<=====      |            |     registers it in the DNS.
	    |      . . . . . . . . . >|   - AIIH returns the IPv4 address to
node Z4
	    |            |            |
	    |            |<-----------|   - Z4 sends an IPv4 packet which
arrives at Y4
	    |      <=====|            |   - Y4 asks the AIIH server for the
IPv6 address
	    |            |            |     corresponding to X4.
	    |      =====>|            |   - AIIH server responds
	    |<++++++++++ |            |   - The packet is tunneled to node
X6


	I think you are worried about the part that says: "Y4 asks the AIIH
server for the IPv6 address corresponding to X4"

	I think the intention there was for the TEP to use DNS to get the
IPv4 address (now assigned) of the IPv6 destination. Another way would be to
use the mechanisms you have in DSTM/SIIT draft to proactively update all the
TEPs of the site with the mappings?

	Cheers
	George


From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 07:23: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 HAA17561
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 07:23: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 FAA00190;
	Fri, 15 Sep 2000 05:23:38 -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 EAA04263;
	Fri, 15 Sep 2000 04:23:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8FBMFq05994
	for ngtrans-dist; Fri, 15 Sep 2000 04:22:15 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8FBM9r05987
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 04:22:09 -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 EAA09758
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 04:22:08 -0700 (PDT)
From: geir.egeland@telenor.com
Received: from bdr-osl-25-005.oslo.telenor.no (BDR-OSL-25-005.telenor.no [134.47.108.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id EAA23324
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 04:22:07 -0700 (PDT)
Received: from 134.47.108.96 by bdr-osl-25-005.oslo.telenor.no (InterScan E-Mail VirusWall NT); Fri, 15 Sep 2000 13:23:00 +0200 (W. Europe Daylight Time)
Received: by BDR-OSL-24-201.telenor.no with Internet Mail Service (5.5.2650.21)
	id <S7NRVRLW>; Fri, 15 Sep 2000 13:22:59 +0200
Message-ID: <7923615E38B1D21187EE0008C70DA9C80119BDC0@fou-kj-21-001.nta.no>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Questions about DSTM
Date: Fri, 15 Sep 2000 13:21:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: geir.egeland@telenor.com

Hi,

I have two questions about the example in chapter 4.1 of the DSTM draft.

1. If host X6 is running an application compiled for IPv6, wouldn't you
need a header translator for the packets from host Z4 to the IPv6
application 
in host X6?

2. What if the IPv6 application running on host X6 has embedded IPv6
addresses in the payload, 
wouldn't you need some sort of ALG?

Thanks,

Geir Egeland



From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 08:07: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 IAA18228
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 08:07:53 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA11119;
	Fri, 15 Sep 2000 06:07:41 -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 FAA28181;
	Fri, 15 Sep 2000 05:07:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8FC6Kk06033
	for ngtrans-dist; Fri, 15 Sep 2000 05:06:20 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8FC6Dr06026
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 05:06:13 -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 FAA12522
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 05:06:11 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA10678
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 06:06:09 -0600 (MDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id WAA07302;
	Fri, 15 Sep 2000 22:03:28 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id XAA02623;
	Fri, 15 Sep 2000 23:05:25 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58Z18D>; Fri, 15 Sep 2000 23:05:27 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB25A@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
Cc: Francis.Dupont@enst-bretagne.fr, ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 23:05:25 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01F0D.3B1B88B0"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01F0D.3B1B88B0
Content-Type: text/plain;
	charset="iso-8859-1"

George, 

Am I right to say that your issue is generally about incoming connections in
DSTM rather than the DSTM-SIIT and DSTM-MIPv6 drafts?

=> You're half right :)
There is the case of requesting an IPv4 address from the home 
DHCPv4 server, which doesn't affect DSTM but affects your 
proposal. I'm not saying you have to solve it but just mention
it as an issue if you don't want to address it. 

The other case which you mention below only affects DSTM and 
not your draft.

	....
	You say:
>    Does the Border router or TEP know that this IPv4
>    address should be routed to subnet X where the MN's HA is ? 
> 
	You are talking about incoming sessions yes?
	Here is the diagram from DSTMv1 that described incoming sessions in
detail (removed in v2)

	   DNSv4  AIIH   Y4          Z4
	   DNSv6         Y6
	    |      <. . . . . . . . . |   - ask for the IPv4 address of X
	    |            |            |   - this request arrives to the AIIH
Server
	    |            |            |
	    |            |            |   - if node X does not have already
a
	    |            |            |     temporary IPv4 address assigned
then the
	    |            |            |     AIIH allocates an IPv4 address
and
	    |<=====      |            |     registers it in the DNS.
	    |      . . . . . . . . . >|   - AIIH returns the IPv4 address to
node Z4
	    |            |            |
	    |            |<-----------|   - Z4 sends an IPv4 packet which
arrives at Y4
	    |      <=====|            |   - Y4 asks the AIIH server for the
IPv6 address
	    |            |            |     corresponding to X4.
	    |      =====>|            |   - AIIH server responds
	    |<++++++++++ |            |   - The packet is tunneled to node
X6


	I think you are worried about the part that says: "Y4 asks the AIIH
server for the IPv6 address corresponding to X4"

=> Yes, thank you !

	I think the intention there was for the TEP to use DNS to get the
IPv4 address (now assigned) of the IPv6 destination. Another way would be to
use the mechanisms you have in DSTM/SIIT draft to proactively update all the
TEPs of the site with the mappings?

=> Exactly my point ! I don't think the DNS is enough nor is it 
a good idea when delays need to be minimised.


------_=_NextPart_001_01C01F0D.3B1B88B0
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 =
5.5.2652.35">
<TITLE>RE: (ngtrans) RE: </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>George, </FONT>
</P>

<P><FONT SIZE=3D2>Am I right to say that your issue is generally about =
incoming connections in</FONT>
<BR><FONT SIZE=3D2>DSTM rather than the DSTM-SIIT and DSTM-MIPv6 =
drafts?</FONT>
</P>

<P><FONT SIZE=3D2>=3D&gt; You're half right :)</FONT>
<BR><FONT SIZE=3D2>There is the case of requesting an IPv4 address from =
the home </FONT>
<BR><FONT SIZE=3D2>DHCPv4 server, which doesn't affect DSTM but affects =
your </FONT>
<BR><FONT SIZE=3D2>proposal. I'm not saying you have to solve it but =
just mention</FONT>
<BR><FONT SIZE=3D2>it as an issue if you don't want to address it. =
</FONT>
</P>

<P><FONT SIZE=3D2>The other case which you mention below only affects =
DSTM and </FONT>
<BR><FONT SIZE=3D2>not your draft.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>....</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>You =
say:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; Does the Border router or TEP =
know that this IPv4</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; address should be routed to =
subnet X where the MN's HA is ? </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>You are =
talking about incoming sessions yes?</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Here is =
the diagram from DSTMv1 that described incoming sessions in</FONT>
<BR><FONT SIZE=3D2>detail (removed in v2)</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; DNSv4&nbsp; AIIH&nbsp;&nbsp; =
Y4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Z4</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp; =
DNSv6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Y6</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;. . . . =
. . . . . |&nbsp;&nbsp; - ask for the IPv4 address of X</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; - this request arrives to the AIIH</FONT>
<BR><FONT SIZE=3D2>Server</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; - if node X does not have already</FONT>
<BR><FONT SIZE=3D2>a</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp; temporary IPv4 address assigned</FONT>
<BR><FONT SIZE=3D2>then the</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp; AIIH allocates an IPv4 address</FONT>
<BR><FONT SIZE=3D2>and</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&lt;=3D=3D=3D=3D=3D&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp; registers it in the DNS.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; . . . . . . =
. . . &gt;|&nbsp;&nbsp; - AIIH returns the IPv4 address to</FONT>
<BR><FONT SIZE=3D2>node Z4</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&lt;-----------|&nbsp;&nbsp; - Z4 sends an IPv4 packet which</FONT>
<BR><FONT SIZE=3D2>arrives at Y4</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;=3D=3D=3D=3D=3D|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp; - Y4 asks the AIIH server for the</FONT>
<BR><FONT SIZE=3D2>IPv6 address</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp; corresponding to X4.</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
=3D=3D=3D=3D=3D&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; |&nbsp;&nbsp; - AIIH server responds</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp; |&lt;++++++++++ =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp; - The packet is tunneled to node</FONT>
<BR><FONT SIZE=3D2>X6</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>I think =
you are worried about the part that says: &quot;Y4 asks the AIIH</FONT>
<BR><FONT SIZE=3D2>server for the IPv6 address corresponding to =
X4&quot;</FONT>
</P>

<P><FONT SIZE=3D2>=3D&gt; Yes, thank you !</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>I think =
the intention there was for the TEP to use DNS to get the</FONT>
<BR><FONT SIZE=3D2>IPv4 address (now assigned) of the IPv6 destination. =
Another way would be to</FONT>
<BR><FONT SIZE=3D2>use the mechanisms you have in DSTM/SIIT draft to =
proactively update all the</FONT>
<BR><FONT SIZE=3D2>TEPs of the site with the mappings?</FONT>
</P>

<P><FONT SIZE=3D2>=3D&gt; Exactly my point ! I don't think the DNS is =
enough nor is it </FONT>
<BR><FONT SIZE=3D2>a good idea when delays need to be minimised.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01F0D.3B1B88B0--


From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 08:12:06 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 IAA18292
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 08:12:05 -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 GAA12243;
	Fri, 15 Sep 2000 06:11:55 -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 FAA28454;
	Fri, 15 Sep 2000 05:11:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8FCAxO06055
	for ngtrans-dist; Fri, 15 Sep 2000 05:10:59 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8FCAqr06048
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 05:10:52 -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 FAA23641
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 05:10:51 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA11975
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 06:10:48 -0600 (MDT)
Received: from brsi02.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id WAA07365;
	Fri, 15 Sep 2000 22:08:07 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id XAA02823;
	Fri, 15 Sep 2000 23:10:06 +1100 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <SZ58Z19C>; Fri, 15 Sep 2000 23:10:08 +1100
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB25B@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>,
        "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
Cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: RE: (ngtrans) RE: 
Date: Fri, 15 Sep 2000 23:10:08 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C01F0D.E3BB9050"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C01F0D.E3BB9050
Content-Type: text/plain;
	charset="iso-8859-1"



   Does the Border router or TEP know that this IPv4
   address should be routed to subnet X where the MN's HA is ? 

=> Ah! You should reread the DSTM draft. The TEP encapsulates
IPv4 traffic to the MN into IPv6. The communication between the MN and
the TEP is done by a IPv4 over IPv6 tunnel.

   Because the DSTM draft does not really say how the IPv6-IPv4
   mapping should be done.

=> there is no mapping nor translation. All nodes have a global IPv6
address (at least). A global IPv4 address and a TEP is allocated to
an IPv6 node which needs to communicate with an IPv4 only node.
There is *no* relationship between addresses, the IPv4 address
is just pick up from a pool (this pool can (and will) be smaller
than the number of nodes then scenario 2 has a DOS attack).


I think either I didn't explain my question properly or you're 
answering the wrong question. But please refer to George's
email I think he understood what I meant. Sorry if I wasn't
clear  !

Cheers,
Hesham

------_=_NextPart_001_01C01F0D.E3BB9050
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) RE: </TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=2>&nbsp;&nbsp; Does the Border router or TEP know that this IPv4</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; address should be routed to subnet X where the MN's HA is ? </FONT>
</P>

<P><FONT SIZE=2>=&gt; Ah! You should reread the DSTM draft. The TEP encapsulates</FONT>
<BR><FONT SIZE=2>IPv4 traffic to the MN into IPv6. The communication between the MN and</FONT>
<BR><FONT SIZE=2>the TEP is done by a IPv4 over IPv6 tunnel.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; Because the DSTM draft does not really say how the IPv6-IPv4</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; mapping should be done.</FONT>
</P>

<P><FONT SIZE=2>=&gt; there is no mapping nor translation. All nodes have a global IPv6</FONT>
<BR><FONT SIZE=2>address (at least). A global IPv4 address and a TEP is allocated to</FONT>
<BR><FONT SIZE=2>an IPv6 node which needs to communicate with an IPv4 only node.</FONT>
<BR><FONT SIZE=2>There is *no* relationship between addresses, the IPv4 address</FONT>
<BR><FONT SIZE=2>is just pick up from a pool (this pool can (and will) be smaller</FONT>
<BR><FONT SIZE=2>than the number of nodes then scenario 2 has a DOS attack).</FONT>
</P>
<BR>

<P><FONT SIZE=2>I think either I didn't explain my question properly or you're </FONT>
<BR><FONT SIZE=2>answering the wrong question. But please refer to George's</FONT>
<BR><FONT SIZE=2>email I think he understood what I meant. Sorry if I wasn't</FONT>
<BR><FONT SIZE=2>clear&nbsp; !</FONT>
</P>

<P><FONT SIZE=2>Cheers,</FONT>
<BR><FONT SIZE=2>Hesham</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C01F0D.E3BB9050--


From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 14:07:15 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 OAA23263
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 14:07:14 -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 MAA20754;
	Fri, 15 Sep 2000 12:07:05 -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 LAA26864;
	Fri, 15 Sep 2000 11:06:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8FI4sn06375
	for ngtrans-dist; Fri, 15 Sep 2000 11:04:54 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8FI4jr06368
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:04:46 -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 LAA15024
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:04:44 -0700 (PDT)
Received: from ztxmail02.ztx.compaq.com (ztxmail02.ztx.compaq.com [161.114.1.206])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA19495
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:04:44 -0700 (PDT)
Received: by ztxmail02.ztx.compaq.com (Postfix, from userid 12345)
	id 4498D1102; Fri, 15 Sep 2000 13:04:44 -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 940F7137F; Fri, 15 Sep 2000 13:04:43 -0500 (CDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id OAA0000779631; Fri, 15 Sep 2000 14:03:26 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200009151803.OAA0000779631@anw.zk3.dec.com>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
Cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        ngtrans@sunroof.eng.sun.com, bound@zk3.dec.com
Subject: Re: (ngtrans) RE: 
In-reply-to: Your message of "Fri, 15 Sep 2000 03:13:58 +1100."
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB258@eaubrnt018.epa.ericsson.se> 
Date: Fri, 15 Sep 2000 14:03:26 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Hesham,

I am catching up on all this DSTM mail.  Nice to see it.  Right now I am
spending most of my IETF cycles on the Base API and DHCPv6 and have to
do that as author and editor for those specs.

Let me put your mind at ease.  I have solutions for the DOS issues and
routing issues you and Erik will be able to use.  And Georges MIP spec
too.

I will ressurect the AIIH parts taken out of DSTM and I am not clear if
Francis and my other co-authors will be part of that or not.  AIIH will
exist for IPv6 (parts taken out of DSTM) as it solves many problems as
you know for real IPv6 deployment we must have.

If we can't do this in the IETF we just implement it and do
informational RFC with any health warnings or take it to 3GPP or
elsewhere for their processes via ITU and ETSI.  The other option is we
build a private vendor consortia and provide public domain code base as
reference base.  But I agree with you if we can solve most of the
problem with AIIH we should do so as proper product engineering for IPv6
transition.  What we can't do is spend another two years discussing this
in IETF meetings and mail lists.  I know I am not alone and many vendors
are down right sick of it as IPv6 customers are showing up at our door
now in Europe and Asia.   The U.S. will move slower but our Education
and U.S. Military entities in the U.S. are taking IPv6 deployment very
seriously, and some of our large Corporate enterprises that want their
global addresses back for network computing for their businesses as NAT
is breaking too much stuff and they need total end-to-end computing.
Which IPv6 can support.

But I can't even think about sending out any text till late October. I
am just to busy and I think my prirority to work on the Base API and
DHCPv6 is correct and for this community too.

regards,
/jim



From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 15 14:21: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 OAA23548
	for <ngtrans-archive@odin.ietf.org>; Fri, 15 Sep 2000 14:21:41 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA28296;
	Fri, 15 Sep 2000 12:21:30 -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 LAA29888;
	Fri, 15 Sep 2000 11:19:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8FII6806460
	for ngtrans-dist; Fri, 15 Sep 2000 11:18:06 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8FIHxr06453
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:17:59 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA29565
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:17:58 -0700 (PDT)
Received: from DF-INET-1.dogfoodinternet.com (df-inet1.exchange.microsoft.com [131.107.8.8])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA29120
	for <ngtrans@sunroof.eng.sun.com>; Fri, 15 Sep 2000 11:17:58 -0700 (PDT)
Received: from yuri.dns.microsoft.com ([172.30.236.11]) by DF-INET-1.dogfoodinternet.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Fri, 15 Sep 2000 11:16:53 -0700
Received: from speak.platinum.corp.microsoft.com ([172.30.236.197]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Fri, 15 Sep 2000 11:17:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: (ngtrans) RE: Notes from Pittsburgh
Date: Fri, 15 Sep 2000 11:17:26 -0700
Message-ID: <CC2E64D4B3BAB646A87B5A3AE97090420D9E6675@speak.platinum.corp.microsoft.com>
Thread-Topic: Notes from Pittsburgh
Thread-Index: AcAOJA3k2abdiIOlQiiodnp8xhUIhAO3QZkwAJACBTA=
From: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
To: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 15 Sep 2000 18:17:26.0733 (UTC) FILETIME=[33B6D7D0:01C01F41]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e8FII0r06454
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
Content-Transfer-Encoding: 8bit

2nd try

>  -----Original Message-----
> From: 	Tony Hain  
> Sent:	Tuesday, September 12, 2000 3:44 PM
> To:	'ngtrans@sunroof.eng.sun.com'
> Subject:	FW: Notes from Pittsburgh
> 
> These are still the raw notes from Pittsburgh. If details are wrong or
> incomplete for the key issues please speak up.
> 
> Tony
> 
>  -----Original Message-----
> From: 	Tony Hain  
> Sent:	Thursday, August 24, 2000 4:36 PM
> To:	'Bob Fink'; 'Alain Durand'
> Subject:	Notes from Pittsburgh
> 
> Sorry these have taken so long to get out... I am not sure how to best
> clean them up without ending up back at simply the agenda. Thoughts?
> 
> NGtrans Minutes 8/2/00
> 
> With a single 2-hour time slot and 18 topics to discuss, each topic
> had a strict time limit, resulting in very little discussion. Without
> a volunteer to take notes, the timekeeper was doing double duty. The
> presentation series resulted in 3 new documents being sent to the list
> for becoming working group items, and one moving to working group last
> call. The primary focus of the series was 6to4, with the various
> translators adding refinements. The group will change its name to
> match the IPNG change, and become IPv6transition.
> 
> Agenda Bash						2 min Chairs
> Overview document					5 min Chairs 
> 
> N+I							2 min Jinmei
> Tatuya
> 		routers from hitaci & cisco
> 
> DSTM 							10 min Jim Bound
> 		new co-authors
> 		removed all optional processing
> 		applicability statement added
> 		desire for manual config : details in mail
> 		dns components will be started as a new additional draft
> 
> SIIT evolution 						10 min
> Eric Nordmark
> 		inbound routing to v6 only box
> 		discovery of the mapping to tunnel
> 		tunneling to mobile node : results in 3 headers per
> packet
> 		open issues : getting addresses from visited site vs.
> home
> 		pdf of slides in the mail
> 
> 6to4 multicast 						10 min
> Dave Thaler
> 		goal is to make multicast work over nbma link
> 		scale : state per receiver
> 		ask list to move to wg draft
> 
> 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)
> 
> Tunnels end point in DNS   				5 min Alain
> Durand
> 		ask list to move to wg draft (possibly combined with
> 6to4scale)
> 
> 6to4 addresses rvs DNS   				10 min Keith
> Moore
> 		map out possible solutions
> 		2 methods : if existing ipv4 zone look there : assume
> well known addr
> 		only assume delegation point, not record
> 		dos attack concerns raised
> 
> Broker							5 min
> Guardini Ivano
> 		framework doc 
> 
> Mime type 						5 min Alain
> Durand
> 		ask list to move to wg draft
> 
> v6v4compat 						5 min 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
> 
> Hometun 						10 min 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 
> 
> Multicast Translator 					5 min Kazuaki
> Tsuchiya
> 		take to list for further discussion : chairs to discuss
> experimental vs. std
> 
> Abuse against IPv6 transition				2 min Itojun
> 		open relays as attack point
> 		is this an ipv6 or ngtrans issue?
> 		is this an implementation or spec issue?
> 		seem to be setting up mechanisms that make ddos easier
> 
> Transport relay translator 				2 min Itojun
> 		no extra config : trying to increase scale
> 		no major changes - want to go to wg last call
> 		wants wg last call
> 
> SOCKS update 	 					2 min Hiroshi
> Kitamura
> 		comments addressed : unnecessary parts removed
> 		looking for WG last call
> 
> Introduction to transition  				2 min Alain
> Durand
> 		scenarios are next
> 		update on dstm to match new draft
> 		expect -05 soon : last call in SD
> 
> WG Name change					2 min Chairs
> 
> 		linked to ipng group so we should to change to ipv6 as
> well
> 		will revisit charter at the same time
> 
> 


From owner-ngtrans@sunroof.eng.sun.com  Sat Sep 16 07:07: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 HAA14045
	for <ngtrans-archive@odin.ietf.org>; Sat, 16 Sep 2000 07:07: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 FAA17151;
	Sat, 16 Sep 2000 05:06:59 -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 EAA07965;
	Sat, 16 Sep 2000 04:06:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8GB5oO06927
	for ngtrans-dist; Sat, 16 Sep 2000 04:05:50 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8GB5hr06919
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:05:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id EAA24382
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:05:40 -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 FAA16960
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 05:05:39 -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 e8GB5Ru25462;
	Sat, 16 Sep 2000 13:05:29 +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 NAA26976;
	Sat, 16 Sep 2000 13:05:27 +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 NAA04869;
	Sat, 16 Sep 2000 13:06:55 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009161106.NAA04869@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) RE: 
In-reply-to: Your message of Fri, 15 Sep 2000 03:13:58 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB258@eaubrnt018.epa.ericsson.se> 
Date: Sat, 16 Sep 2000 13:06:55 +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:

   This scenario made me think more about how TEP in general
   maps IPv4 and IPv6 addresses.
   
=> I still don't understand what is this IPv4/IPv6 mapping.

   Even in the other case where there is DSTM at home, If the
   IPv6 node is in the foreign domain, does it not still need
   to reverse tunnel through the Home TEP ?

=> this is no reverse tunnel but the TEP-MN IPv4 over IPv6 tunnel is
bidirectional (it is a key point of DSTM, the infrastructure doesn't
need to know how to route IPv4 packets).

   If it sends packets directly in its foreign domain, the incoming
   IPv4 packets ( coming into the home domain) will be received by
   the TEP and it will have no idea how to map them.

=> the packets are sent through the tunnel to the TEP then the TEP
can look at them and discover/manage tunnel parameters (including
MN IPv4 and (home) IPv6 addresses). This is needed by scenario 1
if the AIIH server doesn't configure the TEP (and this is the option
we've implemented).

   This is a similar problem to what we try to address in our
   proposal for combining SIIT and DSTM.
   Maybe the TEP needs to have a similar client to be able to
   request this mapping information from the AIIH server.
   
=> the best solution in your case should to have the AIIH server
configuring both the TEP and the MN. It will be needed by the scenario 2 too.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Sat Sep 16 07:32: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 HAA14196
	for <ngtrans-archive@odin.ietf.org>; Sat, 16 Sep 2000 07:32:55 -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 FAA20139;
	Sat, 16 Sep 2000 05:32:43 -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 EAA09469;
	Sat, 16 Sep 2000 04:31:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8GBUW506966
	for ngtrans-dist; Sat, 16 Sep 2000 04:30:32 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8GBUQr06959
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:30:26 -0700 (PDT)
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 EAA25877
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:30:23 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA01487
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:30:22 -0700 (PDT)
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 e8GBUHu26350;
	Sat, 16 Sep 2000 13:30:17 +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 NAA27142;
	Sat, 16 Sep 2000 13:30:16 +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 NAA04943;
	Sat, 16 Sep 2000 13:31:44 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009161131.NAA04943@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: geir.egeland@telenor.com
cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Questions about DSTM 
In-reply-to: Your message of Fri, 15 Sep 2000 13:21:25 +0200.
             <7923615E38B1D21187EE0008C70DA9C80119BDC0@fou-kj-21-001.nta.no> 
Date: Sat, 16 Sep 2000 13:31:44 +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:

   I have two questions about the example in chapter 4.1 of the DSTM draft.
   
   1. If host X6 is running an application compiled for IPv6,

=> the node X is dual-stack and is running application for IPv6+IPv4
(standard applications) and for IPv4-only (legacy applications).
For these applications DSTM works.

   wouldn't you need a header translator for the packets from host Z4
   to the IPv6 application in host X6?

=> I think an IPv6-only application will use IPv6 specific tricks (which one?
I don't know good examples...) then the communication with the node Z4
(4 for IPv4 only) will never work, with or without a header translator:
such applications are by definition out of the scope of a transition
mechanism (it is transition from IPv4 to IPv6).
   
   2. What if the IPv6 application running on host X6 has embedded IPv6
   addresses in the payload, 

=> an IPv6+IPv4 application which uses embedded IPv6 addresses when it
communicates with an IPv4 node is broken.

   wouldn't you need some sort of ALG?
   
=> you can use ALGs but you should not need them. In the real life
a combination of DSTM and ALGs will be used and the ALGs will be for
some protocols where a proxy or a relay is natural (ie. a part of
the architecture), for instance SMTP (the side MTA will be an ALG).

Regards

Francis.Dupont@enst-bretagne.fr

PS: you should reread the definition of a dual-stack node (RFC 2893 *).
DSTM is based on it and extends its application to cases where there
are not enough IPv4 addresses (lack of address space: the main reason
to go to IPv6) and/or the infrastructure supports only IPv6 (lack of
network/system engineers: the main reason to give up NATs).
PPS *: is it a better text? RFC 2893 is more about IPv6 over IPv4
(the opposite of DSTM).


From owner-ngtrans@sunroof.eng.sun.com  Sat Sep 16 07:57:36 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 HAA14307
	for <ngtrans-archive@odin.ietf.org>; Sat, 16 Sep 2000 07:57:35 -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 FAA22458;
	Sat, 16 Sep 2000 05:57:24 -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 EAA10556;
	Sat, 16 Sep 2000 04:56:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8GBtCR06994
	for ngtrans-dist; Sat, 16 Sep 2000 04:55:12 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8GBt5r06987
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:55:05 -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 EAA10510
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:55:02 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA24248
	for <ngtrans@sunroof.eng.sun.com>; Sat, 16 Sep 2000 04:55:01 -0700 (PDT)
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 e8GBsnu28499;
	Sat, 16 Sep 2000 13:54:49 +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 NAA27283;
	Sat, 16 Sep 2000 13:54:48 +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 NAA05053;
	Sat, 16 Sep 2000 13:56:16 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200009161156.NAA05053@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
cc: "'george.tsirtsis@bt.com'" <george.tsirtsis@bt.com>,
        ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) RE: 
In-reply-to: Your message of Fri, 15 Sep 2000 23:05:25 +1100.
             <4B6BC00CD15FD2119E5F0008C7A419A5089EB25A@eaubrnt018.epa.ericsson.se> 
Date: Sat, 16 Sep 2000 13:56:16 +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:

    Am I right to say that your issue is generally about incoming
    connections in DSTM rather than the DSTM-SIIT and DSTM-MIPv6 drafts?

    => You're half right :)
    There is the case of requesting an IPv4 address from the home 
    DHCPv4 server, which doesn't affect DSTM but affects your 
    proposal. I'm not saying you have to solve it but just mention
    it as an issue if you don't want to address it. 

=> I believe DSTM will be used with IPv6-only infrastructure because
it removes the need of a dual infrastructure. Then DHCPv4 will not be
used and only DHCPv6 should be "augmented" (ie. KISS principle was applied).

    The other case which you mention below only affects DSTM and 
    not your draft.

=> this other case is scenario 2 then is not described in the last DSTM
draft.

	I think you are worried about the part that says: "Y4 asks the AIIH
    server for the IPv6 address corresponding to X4"

    => Yes, thank you !

=> I prefer the proactive way to do this (AIIH server configures Y (the TEP)
and X (the MN)). Why? It is simpler and faster.

	I think the intention there was for the TEP to use DNS

=> even it is possible to use the DNS in a reactive way it is a bad solution
(I don't explain why: you already know :-).

    to get the IPv4 address (now assigned) of the IPv6
    destination. Another way would be to use the mechanisms you have in
    DSTM/SIIT draft to proactively update all the TEPs of the site with
    the mappings?

=> you need only one TEP (KISS again).

    => Exactly my point ! I don't think the DNS is enough nor is it 
    a good idea when delays need to be minimised.

=> I agree. In fact the DNS is enough but it is far too slow (just not
designed for this task). The DNS is used in DSTM only:
 - to trigger AIIH mechanism in scenario 2
 - to optimize the scenario 2 when there is more than one "Z" node
   (registers X4 in the DNS: subsequent request for X4 will be
    immediately served)
This is not very new, some NATs do exactly the same thing (RFC 2694 & co).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Wed Sep 20 09:08: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 JAA21708
	for <ngtrans-archive@odin.ietf.org>; Wed, 20 Sep 2000 09:08:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA28098;
	Wed, 20 Sep 2000 07:08:05 -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 GAA24228;
	Wed, 20 Sep 2000 06:07:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8KD6Uw11697
	for ngtrans-dist; Wed, 20 Sep 2000 06:06:30 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8KD6Lr11690
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 06:06:21 -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 GAA10467
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 06:06:21 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA27447
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 07:06:20 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21602;
	Wed, 20 Sep 2000 09:06:11 -0400 (EDT)
Message-Id: <200009201306.JAA21602@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, IANA <iana@iana.org>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ngtrans@sunroof.eng.sun.com
From: The IESG <iesg-secretary@ietf.org>
Subject: (ngtrans) Protocol Action: Connection of IPv6 Domains via IPv4 Clouds
	 without Explicit Tunnels to Proposed Standard
Date: Wed, 20 Sep 2000 09:06:11 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>



The IESG has approved the Internet-Draft 'Connection of IPv6 Domains
via IPv4 Clouds without Explicit Tunnels'
<draft-ietf-ngtrans-6to4-07.txt> as a Proposed Standard.  This document
is the product of the Next Generation Transition Working Group.  The
IESG contact persons are Bert Wijnen and Randy Bush.


 
Technical Summary


 The motivation for this method is to allow isolated IPv6 domains or
 hosts, attached to an 
 IPv4 network with no native IPv6 support, to communicate with other
 IPv6 domains or hosts with minimal manual configuration.  It also
 automatically provides a globally unique IPv6 address prefix to any
 site with at least one globally unique IPv4 address, even if combined
 with an IPv4 Network Address Translator (NAT).

 It does so by specifying a mechanism for assigning a unique IPv6
 address prefix to any site that currently has at least one globally
 unique IPv4 address, and this document describes scenarios for using
 such a prefix during the co-existence phase of IPv4 to IPv6 transition.
 Effectively it treats the IPv4 network as a unicast link layer.  Note
 that this is not considered to be a long term solution and that sites
 should migrate in due course to native IPv6 prefixes.

Working Group Summary

 The working group reached consensus on this document.  There were no
 objections during any last calls.

Protocol Quality

 This document was reviewed for the IESG by Randy Bush.  Test
 implementations are available on BSD platforms, but not from major
 router vendors.


From owner-ngtrans@sunroof.eng.sun.com  Wed Sep 20 14:56: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 OAA02071
	for <ngtrans-archive@odin.ietf.org>; Wed, 20 Sep 2000 14:56:27 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA17693;
	Wed, 20 Sep 2000 12:56:13 -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 JAA07452;
	Wed, 20 Sep 2000 09:54:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8KGrGf11842
	for ngtrans-dist; Wed, 20 Sep 2000 09:53:16 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8KGr9r11835
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 09:53:10 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.11.0+Sun/8.11.0) id e8KGr2403784
	for ngtrans@sunroof.eng.sun.com; Wed, 20 Sep 2000 09:53:02 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8KFUhr11795
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 08:30:44 -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 IAA10456
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 08:30:43 -0700 (PDT)
Received: from scallop.baynetworks.com (ns5.baynetworks.com [194.133.90.101])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA28315
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 08:30:42 -0700 (PDT)
Received: from mailhost.BayNetworks.COM (h8754.s84f5.BayNetworks.COM [132.245.135.84])
	by scallop.baynetworks.com (8.9.1/8.9.1) with ESMTP id RAA06704
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 17:36:22 +0200 (MET DST)
Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id LAA19255;
	Wed, 20 Sep 2000 11:30:37 -0400 (EDT)
Received: from kozi.engeast (kozi [192.32.150.115])
	by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with SMTP
	id LAA16692; Wed, 20 Sep 2000 11:30:37 -0400
	for 
Received: from baynetworks.com by kozi.engeast (SMI-8.6/SMI-SVR4)
	id LAA09064; Wed, 20 Sep 2000 11:30:37 -0400
Message-ID: <39C8D81D.1943EF1C@baynetworks.com>
Date: Wed, 20 Sep 2000 11:30:37 -0400
From: Okoziem Allen <okallen@nortelnetworks.com>
X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
CC: okallen@nortelnetworks.com
Subject: (ngtrans) Applications in IPv6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Okoziem Allen <okallen@nortelnetworks.com>
Content-Transfer-Encoding: 7bit

Hi ,

I am curious to know if there is any work currently being done with
applications (TFTP, Telnet, FTP,  Ping, Traceroute, etc )
with regards IPv6? Are there any white papers available?
I found some information in RFC 1545 - FTP Over Big Address.  Any
information will be greatly appreciated!

Thanks,

---Kozi






From owner-ngtrans@sunroof.eng.sun.com  Wed Sep 20 23:13: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 XAA15610
	for <ngtrans-archive@odin.ietf.org>; Wed, 20 Sep 2000 23:13:37 -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 VAA18857;
	Wed, 20 Sep 2000 21:13:30 -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 UAA28584;
	Wed, 20 Sep 2000 20:12:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8L3Bhd12909
	for ngtrans-dist; Wed, 20 Sep 2000 20:11:43 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8L3BYr12902
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 20:11:34 -0700 (PDT)
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 UAA00942
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 20:11:33 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA16344
	for <ngtrans@sunroof.eng.sun.com>; Wed, 20 Sep 2000 20:11:32 -0700 (PDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id MAA08096;
	Thu, 21 Sep 2000 12:11:25 +0900 (JST)
To: Okoziem Allen <okallen@nortelnetworks.com>
cc: ngtrans@sunroof.eng.sun.com
In-reply-to: okallen's message of Wed, 20 Sep 2000 11:30:37 -0400.
      <39C8D81D.1943EF1C@baynetworks.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) Applications in IPv6
From: itojun@iijlab.net
Date: Thu, 21 Sep 2000 12:11:25 +0900
Message-ID: <8094.969505885@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>I am curious to know if there is any work currently being done with
>applications (TFTP, Telnet, FTP,  Ping, Traceroute, etc )
>with regards IPv6? Are there any white papers available?
>I found some information in RFC 1545 - FTP Over Big Address.  Any
>information will be greatly appreciated!

	FTP: RFC2428.  RFC1545 is practically obsolete, don't look at it.
	HTTP: not very big issue there.  you may want to look at RFC2732.
	ping/traceroute: RFC2463.
	telnet: no issue.  just port it.
	tftp: no issue.  just port it.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 21 12:35: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 MAA09485
	for <ngtrans-archive@odin.ietf.org>; Thu, 21 Sep 2000 12:35:53 -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 KAA04734;
	Thu, 21 Sep 2000 10:35:40 -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 HAA27961;
	Thu, 21 Sep 2000 07:35:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8LEXbU13769
	for ngtrans-dist; Thu, 21 Sep 2000 07:33:37 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8LEXUr13762
	for <ngtrans@sunroof.eng.sun.com>; Thu, 21 Sep 2000 07:33:30 -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 HAA13000
	for <ngtrans@sunroof.eng.sun.com>; Thu, 21 Sep 2000 07:33:29 -0700 (PDT)
Received: from mailgate2.austin.ibm.com (mg02.austin.ibm.com [192.35.232.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01863
	for <ngtrans@sunroof.eng.sun.com>; Thu, 21 Sep 2000 08:33:29 -0600 (MDT)
Received: from netmail2.austin.ibm.com (netmail2.austin.ibm.com [9.53.250.97])
	by mailgate2.austin.ibm.com (AIX4.3/8.9.3/8.9.3) with ESMTP id JAA15654
	for <ngtrans@sunroof.eng.sun.com>; Thu, 21 Sep 2000 09:33:53 -0500
Received: from mojave.austin.ibm.com (mojave.austin.ibm.com [9.53.239.7])
        by netmail2.austin.ibm.com (8.8.5/8.8.5) with ESMTP id JAA03632;
        Thu, 21 Sep 2000 09:33:27 -0500
Received: (from marquard@localhost) by mojave.austin.ibm.com (AIX4.3/8.9.3/8.7-client1.01) id JAA40884; Thu, 21 Sep 2000 09:33:26 -0500
To: Okoziem Allen <okallen@nortelnetworks.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Applications in IPv6
References: <39C8D81D.1943EF1C@baynetworks.com>
From: Dave Marquardt <marquard@austin.ibm.com>
Date: 21 Sep 2000 09:33:25 -0500
In-Reply-To: Okoziem Allen's message of "Wed, 20 Sep 2000 11:30:37 -0400"
Message-ID: <v5twvg5stl6.fsf@mojave.austin.ibm.com>
Lines: 11
X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Dave Marquardt <marquard@austin.ibm.com>

Okoziem Allen <okallen@nortelnetworks.com> writes:
> I am curious to know if there is any work currently being done with
> applications (TFTP, Telnet, FTP,  Ping, Traceroute, etc )
> with regards IPv6? Are there any white papers available?
> I found some information in RFC 1545 - FTP Over Big Address.  Any
> information will be greatly appreciated!

AIX has had IPv6 capable telnet, FTP, and ping since 1997, when we
released IPv6 with AIX 4.3.0.

-Dave


From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 22 06:48:49 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 GAA05167
	for <ngtrans-archive@odin.ietf.org>; Fri, 22 Sep 2000 06:48:48 -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 EAA13577;
	Fri, 22 Sep 2000 04:48:40 -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 DAA28124;
	Fri, 22 Sep 2000 03:47:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8MAkgY14846
	for ngtrans-dist; Fri, 22 Sep 2000 03:46:42 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8MAkXr14839
	for <ngtrans@sunroof.eng.sun.com>; Fri, 22 Sep 2000 03:46:34 -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 DAA28030
	for <ngtrans@sunroof.eng.sun.com>; Fri, 22 Sep 2000 03:46:32 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA20867
	for <ngtrans@sunroof.eng.sun.com>; Fri, 22 Sep 2000 03:46:31 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05071;
	Fri, 22 Sep 2000 06:46:29 -0400 (EDT)
Message-Id: <200009221046.GAA05071@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-broker-05.txt
Date: Fri, 22 Sep 2000 06:46:29 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: IPv6 Tunnel Broker
	Author(s)	: A. Durand, P. Fasano, I. Guardini, D. Lento
	Filename	: draft-ietf-ngtrans-broker-05.txt
	Pages		: 10
	Date		: 21-Sep-00
	
The IPv6 global Internet as of today is mostly built using tunnels over
the existing IPv4 infrastructure. Those tunnels are difficult to
configure and maintain in a large scale environment. The 6bone has
proven that large sites and ISPs can do it, but this process is too
complex for the isolated end user who already has an IPv4 connection and
would like to enter the IPv6 world. The motivation for the development
of the tunnel broker model is to help early IPv6 adopters to hook up
to an existing IPv6 network (e.g. the 6bone) and to get stable,
permanent IPv6 addresses and DNS names. The concept of the tunnel broker
was first presented at Orlando's IETF in December 1998. Two
implementations were demonstrated during the Grenoble IPng & NGtrans
interim meeting.

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-broker-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-broker-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Sep 28 01:33: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 BAA04790
	for <ngtrans-archive@odin.ietf.org>; Thu, 28 Sep 2000 01:33:54 -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 XAA21795;
	Wed, 27 Sep 2000 23:33:12 -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 WAA05095;
	Wed, 27 Sep 2000 22:32:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) id e8S5VXO19919
	for ngtrans-dist; Wed, 27 Sep 2000 22:31:33 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8S5VOr19912
	for <ngtrans@sunroof.eng.sun.com>; Wed, 27 Sep 2000 22:31:25 -0700 (PDT)
Received: from rouget.sun.com (dsl197-48.Eng.Sun.COM [129.146.197.48])
	by jurassic.eng.sun.com (8.11.1.Beta1+Sun/8.11.1.Beta1) with ESMTP id e8S5VNe403879
	for <ngtrans@sunroof.eng.sun.com>; Wed, 27 Sep 2000 22:31:23 -0700 (PDT)
Message-Id: <5.0.0.25.0.20000927222556.0292dd50@jurassic>
X-Sender: durand@jurassic
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Wed, 27 Sep 2000 22:36:37 -0700
To: ngtrans@sunroof.eng.sun.com
From: Alain Durand <Alain.Durand@sun.com>
Subject: (ngtrans) Last call: tunnel broker (rev. 5)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@sun.com>

NGtrans folks,

A new revision of the tunnel broker draft has been issued:
draft-ietf-ngtrans-broker-05.txt

This revision answer comments received during the previous last call.
Changes are:
	- relax rules on prefix length a broker can serve.
            (any prefix length is valid, /48, /64 and /128 are
             now just the most common cases)
	- clarify some security consideration in the dialog
             broker/client or broker/server

We will enter now a 2 weeks WG last call, ending October 12th.
Please send substantive comments to the mailing list and editorial comments 
to the authors.

This draft is candidate to be published as Informational RFC.

	- Alain.



From owner-ngtrans@sunroof.eng.sun.com  Fri Sep 29 03:34: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 DAA24674
	for <ngtrans-archive@odin.ietf.org>; Fri, 29 Sep 2000 03:34:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA17358;
	Fri, 29 Sep 2000 01: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 AAA20372;
	Fri, 29 Sep 2000 00:33:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e8T7Wh120784
	for ngtrans-dist; Fri, 29 Sep 2000 00:32:43 -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 e8T7Uw320769;
	Fri, 29 Sep 2000 00:30:58 -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 AAA20113;
	Fri, 29 Sep 2000 00:30:58 -0700 (PDT)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA00092;
	Fri, 29 Sep 2000 00:30:57 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id QAA28155;
	Fri, 29 Sep 2000 16:30:56 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA20973; Fri, 29 Sep 2000 16:30:55 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id QAA04846; Fri, 29 Sep 2000 16:30:55 +0900 (JST)
Date: Fri, 29 Sep 2000 16:29:11 +0900 (JST)
Message-Id: <20000929.162911.18619584.kazu@Mew.org>
To: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Cc: pc@jp.ipv6forum.com
Subject: (ngtrans) Global IPv6 Summit in Japan
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.95b64 on Emacs 20.7 / Mule 4.1 (AOI)
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: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
Content-Transfer-Encoding: 7bit

Hi all,

I would like to remind you that the deadline of Call For Presentation
for the Summit is tomorrow. If you have not applied yet, please fill
the following application form and post it to cfp@jp.ipv6forum.com.

--Kazu

	Call for participation and presentations for
	"the Global IPv6 Summit in Japan"

<<Abstract>>

The Global IPv6 Summit, under the organization of the IPv6 Forum, is
held regularly around the world to accelerate the deployment of
IPv6. We are happy to announce that this conference will be held in
Japan, one of the leading countries in the areas of IPv6 development
and deployment.

The Internet is built on the foundations of the Internet Protocol
(IP). The current version of IP is named IPv4 after its version
number. The total number of devices that IPv4 can identify is limited
to about 4.3 billion. It's hard to see the Internet becoming the
foundation of a true, universal communications infrastructure when
this number is compared to the human population.

In fact, it is expected that the entire address space of IPv4 will be
exhausted by around 2008. So, address assignment/allocation is
currently being carried out under a very restrictive policy. NAT
(Network Address Translator) was introduced as a temporary solution,
resulting in the loss of some of the original functionality of the
Internet.

The principles of the Internet are end-to-end and bidirectional
communication. This means every node can communicate with every other
freely without any restrictions caused by intermediate nodes. Since
NAT broke these principles, it became difficult for unexpected novel
applications to appear in the current environment of the Internet.

To resolve the exhaustion of IP addresses, extending its address space
is a straightforward solution. IPv6, the next generation of IP,
provides a huge number of IP addresses and makes NAT obsolete allowing
the Internet to recover its original principles.

IPv6 is a paradigm recovery for applications. After deploying IPv6 and
recovering end-to-end/bidirectional communication, we cannot imagine
what kind of applications will appear.

This conference will introduce the current deployment status of IPv6
throughout the world. Also, panel discussions are planned, both on
"How IPv6 will Change Business" and on "Case Studies: Making the
Change to IPv6".

Getting Internet people together, including those who are involved in
IPv6 activities and IPv4 business and management, we intend to discuss
the future of Internet business and the direction of engineering.
This conference will be beneficial for everyone including, but not
limited to, engineers, researchers, network managers and business
people. We would like to invite each of you to participate.

<<The Host>>

	Steering Group of the Global IPv6 Summit in Japan
	(Contact: info@jp.ipv6forum.com)

<<Logistics>>

	Date:
		December 18 - 19, 2000
		(As a part of Internet Week 2000)
	Venue: 
		Grand Cube Osaka (Osaka International Convention Center)
		5-3-51, Nakanoshima, Kita-ku, Osaka 530-0005, JAPAN
		Phone: +81-6-4803-5555
		Fax:   +81-6-4803-5620
		E-mail: soumu@gco.co.jp
		http://www.gco.co.jp/index.html
		(The same place as Internet Week 2000)

<<Registration Fee>>

	<Conference Fee>

			Early registration	Regular/
			discount		On-site registration
			(until Oct 31)
	Non-student	10,000 JPY		15,000 JPY
	Student		 2,000 JPY		 2,000 JPY

	<Reception Fee>

	Non-student	 5,000 JPY
	Student		 3,000 JPY


<<Program>>

	December 18 (Mon)

		Keynote Speech 1: Dr. Jun Murai, WIDE Project
		Session 1: Business report on IPv6 in Japan
		Session 2: Status report from Asian countries
		Session 3: Panel on how IPv6 will change business

		Reception

	December 19 (Tue)

		Keynote Speech 2: Dr. Steve Deering, Cisco Systems
		Session 4: Business report on IPv6 around the world
		Session 5: Case Studies: Making the Change to IPv6

<<Participation>>

This conference will be held as a part of Internet Week 2000. Please
refer to the following page for registration:

	http://www.jp.ipv6forum.com/

<<Presentation Proposals>>

The program committee calls for presentation proposal for "Session 4:
Business report of IPv6 around the world". Candidates are sTLA holders
and IPv6 vendors. Please propose a "10 minutes" presentation on your
IPv6 business.

If you would like to give a presentation, please send an e-mail
message in the following form. Please note that we may not accept all
proposals due to the time limitations of the program.

Format:			See below
Deadline:		September 30, 2000
Notification date:	October 6, 2000

	To: cfp@jp.ipv6forum.com
	Subject: presentation proposal

	Name		:
	Title		:
	Email		:
	Telephone number:
	Organization	:
	Department	:

	Your proposal in plain text (no more than 250 words)
	explaining as concretely as possible your point of view and
	what kind of presentation can be expected.



