From v4v6interim-bounces@ietf.org  Wed Oct  1 06:31:40 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACCCA28C1A8;
	Wed,  1 Oct 2008 06:31:40 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 240DF3A681A;
	Wed,  1 Oct 2008 06:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iH+mZAjeobjo; Wed,  1 Oct 2008 06:31:38 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 2DF6928C196;
	Wed,  1 Oct 2008 06:31:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,343,1220227200"; d="scan'208";a="85316877"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 01 Oct 2008 13:31:45 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m91DVi3g032472; 
	Wed, 1 Oct 2008 06:31:44 -0700
Received: from [192.168.3.108] (sjc-vpn5-1095.cisco.com [10.21.92.71])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91DVgZW008260;
	Wed, 1 Oct 2008 13:31:43 GMT
Message-Id: <D1E05F99-E189-40A0-AE4D-36628B978297@cisco.com>
From: Cullen Jennings <fluffy@cisco.com>
To: "Stark, Barbara" <bs7652@att.com>
In-Reply-To: <7582BC68E4994F4ABF0BD4723975C3FA0AF5DD30@crexc41p>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 09:31:47 -0400
References: <48CEE763.8030502@cisco.com><2A9F30EB-9A1E-46B8-AF83-03B729F8DFF5@lilacglade.org>
	<48D13E0D.8060002@cisco.com>
	<BE82361A0E26874DBC2ED1BA244866B92758ED8D@NALASEXMB08.na.qualcomm.com>
	<013201c922f2$82025230$c2f0200a@cisco.com>
	<7582BC68E4994F4ABF0BD4723975C3FA0AF5DD30@crexc41p>
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4881; t=1222867904;
	x=1223731904; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20v4v6interim@ietf.org=20Mailing=20list
	|Sender:=20; bh=Hn2fx1hoB3sBfD7xnqv0de46EBKRUhwar7hXwLVly7A=;
	b=t/TGsYJ4TBmDn/mJGPNDmnhqJ05JZOcZIoit4kvjOGu0Z+L49gJoJRKkNw
	yIg+Lh9UjeyuHWSZa8Rb+iMSOIhSPLf+5j0LQphVGYDAqwA3oiagKFG1pLp/
	7CWSMKentP;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: Internet Area <int-area@ietf.org>, "Narayanan, Vidya" <vidyan@qualcomm.com>,
	ipv6@ietf.org, softwires@ietf.org,
	IPv6 Operations <v6ops@ops.ietf.org>, v4v6interim@ietf.org,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] v4v6interim@ietf.org Mailing list
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


Sorry - the correct name should be

v4v6coexistence

I just updated the wiki

On Oct 1, 2008, at 9:23 , Stark, Barbara wrote:

> Could someone confirm the name of the jabber room? My client tells  =

> me that "v4v6existence" doesn't exist.
> Barbara
>
> -----Original Message-----
> From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On  =

> Behalf Of Dan Wing
> Sent: Tuesday, September 30, 2008 7:49 AM
> To: 'Narayanan, Vidya'; 'Mark Townsley'; 'Margaret Wasserman'
> Cc: 'Brian Haberman'; 'Internet Area'; softwires@ietf.org; 'IPv6  =

> Operations'; ipv6@ietf.org; 'Behave WG'; v4v6interim@ietf.org
> Subject: RE: v4v6interim@ietf.org Mailing list
>
> See the "Remote Participation" section at:
> http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim
>
> Please register for remote participation, so we have a feeling of  =

> how many
> people are supposed to be in the jabber room and on the conference  =

> bridge.
>
> -d
>
>
>> -----Original Message-----
>> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
>> Sent: Tuesday, September 30, 2008 12:04 AM
>> To: Mark Townsley; Margaret Wasserman
>> Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan
>> Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
>> Subject: RE: v4v6interim@ietf.org Mailing list
>>
>> Mark,
>> Please share the remote particpation info (jabber room, audio
>> link, etc.) when you have it.
>>
>> Thanks,
>> vidya
>>
>>> -----Original Message-----
>>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
>>> Behalf Of Mark Townsley
>>> Sent: Wednesday, September 17, 2008 10:28 AM
>>> To: Margaret Wasserman
>>> Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan
>>> Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
>>> Subject: Re: v4v6interim@ietf.org Mailing list
>>>
>>>
>>> We are discussing the situation with the host, and any
>>> volunteers we can muster up.
>>>
>>> Our goal is to have streaming audio and video for the
>>> presentations, with the ability to ask questions or make
>>> statements to the speaker remotely over jabber (via a local
>>> moderator, speaking on the remote participants behalf). I'm
>>> afraid we probably will not have the right infrastructure for
>>> effective real-time, multipoint, participation among remote
>>> and local participants.
>>>
>>> It looks like there will be a good bit of alpha code running
>>> no matter what we do, so don't bet that there will be no
>>> problems. We'll make the experience as good as we can for
>>> remote folks based on what we have though.
>>>
>>> - Mark
>>>
>>> Margaret Wasserman wrote:
>>>>
>>>> Has there been any resolution on how/if it will be possible
>>> to attend
>>>> this meeting remotely (conference bridge, web conference,
>>> jabber room,
>>>> etc.)?
>>>>
>>>> I will not be able to travel to Montreal, but would like to
>>> attend all
>>>> or part of the meeting remotely, if possible.
>>>>
>>>> Thanks,
>>>> Margaret
>>>>
>>>> On Sep 15, 2008, at 6:53 PM, Mark Townsley wrote:
>>>>
>>>>>
>>>>> We have setup an email list for discussion leading up to
>>> the interim
>>>>> v4v6 coexistence meeting on October 1-2, 2008 in Montr=E9al,
>>> Canada. If
>>>>> you are registered to attend the meeting, you should
>> already be on
>>>>> the list.
>>>>>
>>>>> The list is open, please subscribe and begin using it for
>>> all interim
>>>>> meeting related discussion (technical as well as
>>>>> administrative/logistical). For now, please consider this a
>>>>> short-lived list focused on agenda items for discussion at this
>>>>> interim meeting alone. We should know better after the
>>> meeting how to
>>>>> best divide discussion back among the individual WG lists,
>>> or whether
>>>>> a long-lived list of this nature is warranted.
>>>>>
>>>>> If you are attending and haven't registered, please do:
>>>>>
>>>>>
>>>
>> http://trac.tools.ietf.org/area/int/trac/wiki/RegistrationForv4v6inte
>>>>> rim
>>>>>
>>>>> Tentative agenda, etc. can be found here:
>>>>>
>>>>> http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Mark, Jari, Dan and Brian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>
>>> --------------------------------------------------------------------
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>
>
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 09:13:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BADFC3A6A4E;
	Wed,  1 Oct 2008 09:13:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8682C3A6837
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 09:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.179
X-Spam-Level: 
X-Spam-Status: No, score=-106.179 tagged_above=-999 required=5
	tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ChfrmPxaPW4D for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 09:12:58 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 4E85C3A67A7
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 09:12:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="166698581"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 16:13:05 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91GD5e9008055
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 09:13:05 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m91GD5CC028612
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 16:13:05 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 09:13:05 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 09:13:04 -0700
Message-Id: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
From: Fred Baker <fred@cisco.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 12:13:03 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 16:13:05.0116 (UTC)
	FILETIME=[95E3F1C0:01C923E0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5236; t=1222877585;
	x=1223741585; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20=22IPv4->IPv6=20is=20hard=22 |Sender:=20;
	bh=myVKPAtWZGXX/UBg/fHfmVPedkV6auP+aQWFynPkRvk=;
	b=Zm6tZaPnKRsfxSRSjxwp/s6Qmq6HxbSA23veJQXJa7xRi1FQIB1wWAJJem
	yys7f2AlqTBTew+lPJDbB+A7qYjUz9RY2QtVOcmPPcXRWY1we1VSFjnKgEAp
	8hip0zq5ch;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I'm fairly disturbed by Mark's dismissal of IPv4->IPv6 translation as  
"hard". I'll take this note to say why. I am obviously a proponent of  
a particular class of solution, IVI, which is specifically targeted at  
solving this problem, so let me declare bias up front. But I do not  
consider the issue hard if correctly analyzed and approached.

In this analysis, I am going to leave out the dual stack case, which I  
frankly consider the strongly preferable deployment model. Wherever it  
is used, matters get simplified. I am expressly looking at the more  
difficult IPv4-only/IPv6-only case.

Mark's dismissal - I call it that because he spent an hour talking  
about CGN solutions and then spent less than a minute charging through  
two slides that discussed actually deploying IPv6 and declaring them  
both "hard" and therefore not worthy of consideration - is based on  
the observation that mapping 2^128 addresses into 2^32 bits is hard. I  
will agree with him that making it possible for every IPv6 address to  
be mapped into IPv4 in a scalable manner has issues. The question that  
I will ask is: is that the real requirement? I don't think it is.

While the addressing issue resolves to hosts, the connectivity problem  
is about applications. I think that today's applications can largely  
be broken down into two broad categories, and speakers in those  
applications into three. These are: the clients of client/server  
applications, the servers in client/server applications, and the peer  
in peer-to-peer applications. In an IPv4-only/IPv6-only gateway, we  
have actually only our session initiation problems to solve:

     IPv6 client->IPv4 server
     IPv4 client->IPv6 server
     IPv6 peer -> IPv4 peer
     IPv4 peer -> IPv6 peer

Once a session is initiated, we can obviously continue the conversation.

IPv6 client->IPv4 server is pretty simple. The DNS ALG advertises IPv4  
addresses as mapped IPv6 addresses, and the gateway keeps 1:n overlaid  
mappings in a manner not all that different from current IPv4/IPv4  
NATs. On the IPv6 side of the gateway, we simply use the mapped  
address; on the IPv4 side, we use IPv4 address+port overlay as we do  
in IPv4/IPv4 NATs.

An IPv4 client accessing an IPv6 server is equally simple given a 1:1  
mapping such as NAT64 or IVI describes. One maps the headers and the  
addresses.

IPv6 peer->IPv4 peer is simple enough; it is essentially the same  
problem as IPv6 client->IPv4 server, and is solved the same way.

Initiating a session from an IPv4 peer to an IPv6 peer with an  
unmapped address is "hard"; that winds up calling for complex  
machinery like NAT-PT proposes. However, it is unnecessary to solve  
the case. p2p technologies open TCP connections between systems, leave  
them open long periods of time, and use them to transport data. They  
are in effect overlay networks. If one IPv6 peer opens a session to an  
IPv4 peer, connectivity is established between IPv4-only and IPv6-only  
p2p networks and the problem is solved.

So to my mind, the requirement is that the gateway provide three  
services:
   - a DNS algorithm that maps IPv4 addresses to a subset of IPv6
     addresses.
   - a 1:1 NAT algorithm that statelessly supports the common case of
     IPv4 clients accessing IPv6 servers, which will be used by a
     relatively small set of hosts in the IPv6-only domain.
   - 1 1:n NAT algorithm that statefully maps general IPv6 to IPv4
     address plus port, which might be used by an arbitrarily large
     number of hosts in the IPv6-only domain, but unlikely to be all
     at the same time and diminishing as IPv6 deployment grows.

None of those models is "hard" in light of our present experience with  
SIIT and IPv4/IPv4 NAT.

Now, here is my issue with NAT64/SIIT's addressing model, which we  
deployed and then deprecated in RFC 4291. There are two. First, it is  
a lot like a default route, and limits the network administration's  
options in route management; to fix that, we need to have a prefix  
appropriate to the gateway as opposed to a flat "must be zero" style  
prefix. Second, th addressing architecture is essentially that of CIDR  
and therefore allows routing prefixes to be as long or as short as  
needed, but we have given clear guidance that router vendors should  
think about host routes or prefixes of /64 or shorter, not normally  
prefixes in the 65..127 length range. If we believe that - and RFC  
4291 clearly does - then enabling the gateway to support routing to  
multiple sites within the IPv6 domain using a single IPv4 prefix  
advertised in the IPv4 domain (as opposed to doing host routing to  
IPv4-mapped addresses in the IPv6-only domain) is important for  
scaling. IVI moves the address around to put IPv4-mapped prefixes  
within the /64 length rule.

So the fundamental argument for IVI is that it works well with  
routing, and makes interchange of both p2p and client/server  
applications across the IPv4/IPv6 gateway simple.

IPv4 access to the IPv6 network is most definitely *not* hard if the  
problem is correctly parsed and addressed.

No pun intended.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 09:13:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D54743A6837;
	Wed,  1 Oct 2008 09:13:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 329B83A6837
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 09:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VSh2fox5fmGj for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 09:13:12 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id 19C183A67A7
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 09:13:11 -0700 (PDT)
Received: from ([128.244.96.97])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.117253158;
	Wed, 01 Oct 2008 12:12:59 -0400
Message-ID: <48E3A18B.7010307@innovationslab.net>
Date: Wed, 01 Oct 2008 12:12:59 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: v4v6interim@ietf.org
Subject: [v4v6interim] A+P paper
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

All,
      The A+P paper is available on-line at 
http://mice.cs.columbia.edu/getTechreport.php?techreportID=560

Regards,
Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 09:23:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A9433A6C54;
	Wed,  1 Oct 2008 09:23:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDDF93A6C54
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 09:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Gn2+g48olcNx for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 09:23:41 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id BBD053A6C48
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 09:23:40 -0700 (PDT)
Received: from c0226.aw.cl.cam.ac.uk (c0226.aw.cl.cam.ac.uk [128.232.100.226])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m91GNrsK065503
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 18:23:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 17:24:00 +0100
X-Mailer: Apple Mail (2.929.2)
Subject: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

There are several advantages of having a well known prefix for NAT-PT/ 
NAT64 or even DS-lite. For the former, synthetic AAAA records are no  
longer necessary and can be ignored by updated hosts, for the latter  
there is no longer any need have a configuration mechanism. Upgraded  
IPv6 hosts can simply start sending packets to IPv4 destinations to  
the translator when they detect that they don't have actual IPv4  
connectivity, rather than depend on external entities to provide  
configuration information, in AAAA records or explicitly. An  
additional benefit would be that NAT64 could even support IPv4  
applications this way.

On the other hand, there are operational benefits to having a  
configurable prefix: this makes it possible to direct traffic that is  
to be translated to a specific translator without routing contortions.

What I suggest is that we do both. We present a well known prefix of a  
combined NAT-PT/NAT64/DS-lite translator to transport protocols and  
applications, but we allow packets destined for that prefix to have  
their destination address rewritten into a specific prefix. Because  
the packets are translated later anyway, this causes no problems.  
Also, if we allow longest match first rules for the well known to  
specific prefix translation table, this makes it very easy to support  
private translators for RFC 1918 destinations along with global  
translators for global IPv4 destinations.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 09:29:46 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 222E03A6C3A;
	Wed,  1 Oct 2008 09:29:46 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2F8E3A6A4E
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 09:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sN+iJ16Pj6mK for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 09:29:42 -0700 (PDT)
Received: from unobtainium.braintrust.co.nz (unobtainium.braintrust.co.nz
	[60.234.76.2]) by core3.amsl.com (Postfix) with ESMTP id 915003A6C3A
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 09:29:42 -0700 (PDT)
Received: from [192.168.0.51] (ip-118-90-75-60.xdsl.xnet.co.nz [118.90.75.60])
	by unobtainium.braintrust.co.nz (Postfix) with ESMTP id 63CDF27519; 
	Thu,  2 Oct 2008 05:29:44 +1300 (NZDT)
Message-Id: <5B412ACF-E024-482E-9679-867F305DA4B9@daork.net>
From: Nathan Ward <v6ops@daork.net>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 05:29:43 +1300
X-Mailer: Apple Mail (2.929.2)
Subject: [v4v6interim] Scenarios feedback
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I was hoping to get some of this stuff across earlier, but remote  
feedback is a bit difficult. This is a bit rushed to get it to the  
meeting in time, please talk to me on Jabber for clarification, I am  
also listening on the conference bridge and can see the camera.

Slide 2, the one with the graph showing the "reality" of the lack of  
IP adoption:
I disagree with this "reality". I believe the curve to be much closer  
(in angle) to the "size of the Internet", and perhaps it is even  
steeper.
- Vista has IPv6 support, Teredo, 6to4. New Internet users are likely  
to be on Vista vs. XP
- XPSP2 has IPv6 support for anyone who has turned it on. Peer to peer  
is encouraging people to do this. The most popular peer to peer app  
(uTorrent) even has a "Turn IPv6 on" button in its preferences now.
- Some CPE devices (Airport Extreme, Linksys Business whatever) have  
IPv6 support, and 6to4. These devices are getting OS X hosts online.
- Linux has Teredo and 6to4, there appears to be many Linux Teredo  
users, especially in the peer to peer population.

What is left? XP prior to SP2, OS X users without a 6to4 router or  
native connectivity, Linux users who haven't configured IPv6, and  
embedded devices. I'll go over each below:
- XP Prior to SP2. My assertion is that 99% users in this situation do  
not have a need for end-to-end IPv4. CGN will work fine for them.
- OS X users without a 6to4 router or native connectivity. This is a  
problem. Perhaps Apple will write a Teredo stack? Again, OS X users  
who don't upgrade to the latest OS are unlikely to have a need for end- 
to-end IPv4. There is a solution here already though, and that  
solution is Teredo.
- Linux users without IPv6. Tell them to configure it. It's 20  
commands at most.
- Embedded devices. These are built to work in many situations, so  
relying on non-NATed IPv4 or NAT-PMP or whatever is unlikely.


Comments on Scenarios 1, 2 and 3 collectively:
- We are caring about IPv4 right now because of the perceived need for  
end-to-end IPv4, or more specifically, the ability for end users to  
have ports open to the public Internet, either by "port  
forwarding"/"pin holing" or whatever.
- Applications that require this are, for the most part peer to peer  
applications. Bit torrent, Skype, etc.
- Bit torrent has IPv6 support, and combined with my previous comments  
about IPv6 "reality" we see that bit torrent will not be adversely  
affected.[1]
- Skype already gets around NAT, using non-NATed nodes. Skype could do  
IPv6 easily, and as per bit torrent get wide adoption.
- The non-peer to peer case, ie. home users running servers - If they  
must, they can buy a premium service from their ISP to get a non-NATed  
address. If the ISP doesn't offer this, they lose some customers[2],  
so it's up to them.
- Users of peer to peer applications are likely to upgrade their apps  
and OSes in the next year or so, they are "power users".
- CPE/GW boxes are for a large part not upgradable. Many providers  
around the world do not provide their customers with CPEs, and forcing  
the customer to purchase new hardware so that it keeps working is a  
hard sell. "Buy this so your Internet keeps working" is the same as  
saying "Deploy IPv6 so your Internet keeps working" to ISPs - except  
ISPs understand the problem and have still not done it.
- Dual stack operational overhead is lower than developing, deploying,  
and maintaining a 4 over 6 solution, especially when such a solution  
has a lifetime of only a few years. We can do dual stack *today*.


Scenario 4: IPv6 hosts reaching IPv4 servers.
This is not hard, but we need some standardisation around it.

Scenario 5: IPv4 hosts reaching IPv6 servers.
Until IPv6 is widely deployed, anyone wanting to run a server can buy  
a premium service from their ISP and get IPv4 addresses.
Port agility (in the application) is not an option here. The reason  
this scenario exists is because of legacy operating systems and  
applications.


Summary (please read aloud, but refer to the email for further  
thoughts/background):
- Let's not try and develop a complicated super-solution for IPv4.  
IPv6 is hard enough for ISPs to understand+train etc. as it is.
- We care about IPv4 for end to end/peer to peer.
- IPv6 is in wide deployment in peer to peer already, peer to peer  
users regularly upgrade. The solution to IPv4 peer to peer is IPv6,  
and it is already deployed.
- Therefore IPv4 end to end is not a problem.
- We should not focus on solutions that require CPE/GW upgrades  
because many providers do not provide CPE/GWs.
- Scenario 4 is solveable with NAT-PT.
- Often cited NAT-PT scalability problems (in the v6 -> v4 direction)  
are the same as IPv4 NAT scalability problems, and we have to solve  
IPv4 NAT scalability so let's do both.
- If we can't do NAT-PT in v6->v4 direction, dualstack exists.
- Apart from scenario 5, these problems are either all non-issues (in  
my view), or are solved already with existing protocols that vendors  
aren't doing yet, or aren't doing well enough.
- How do we solve scenario 5?
    o We cannot do port agility. The reason this scenario exists is  
because of legacy operating systems and applications, and we want to  
support those users who have not upgraded. Port agility requires  
application modification.
    o Servers have to have IPv4 until IPv6 is widely enough deployed?  
Seems feasible, as we're all doing CGN there is lots of IPv4 space  
free for servers now, provided RIRs reclaim it.


--
Nathan Ward

[1] See my talk from APNIC26 RE bit torrent IPv6 usage. With uTorrent  
supporting IPv6 (since then) this problem really does not exist anymore.
[2] Note that most customers who want to run home servers are the  
"high usage" customers, so most ISPs would be happy to get rid of  
them :-)


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 10:27:08 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DEA53A6909;
	Wed,  1 Oct 2008 10:27:08 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A39533A6909
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 10:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.428
X-Spam-Level: 
X-Spam-Status: No, score=-106.428 tagged_above=-999 required=5
	tests=[AWL=0.171, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0TLk1OGhZbQ7 for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 10:27:05 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id BA4DE3A67A6
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 10:27:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; 
	d="jpg'145?scan'145,208,145";a="85447948"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 01 Oct 2008 17:26:53 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m91HQrlb022134; 
	Wed, 1 Oct 2008 10:26:53 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91HQrwP011927;
	Wed, 1 Oct 2008 17:26:53 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:26:53 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:26:50 -0700
Message-Id: <04A198C2-EBF1-4259-957E-09A76D29969B@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/mixed; boundary=Apple-Mail-19--238326440
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 13:26:49 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 17:26:51.0082 (UTC)
	FILETIME=[E3F8C2A0:01C923EA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=98186; t=1222882013;
	x=1223746013; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20The=20Walled=20Garden=20at=20Carton=20House.
	|Sender:=20; bh=5boL6+wTEAJskb9JRYLWMk/cWwxfIMNpP5v1P5RN7LU=;
	b=ipYzycwGnBV2aqiEo1DaeBaFfbUEnYHsRnN78T6Soqf1+PXEZx3PLo7ME7
	uB0HYC5iC9dutANqNszpetCi1D4SSlR3GmzxBAMuV+knfB38mEwoaPfAHCAR
	YCncREzTN0;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: [v4v6interim] The Walled Garden at Carton House.
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


--Apple-Mail-19--238326440
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

You said that you were looking for a picture of a Walled Garden. This  
is the Walled Garden at Carton House, just outside Dublin Ireland - I  
have a many-more-pixel copy if you want it. I took the photo, and I  
give you (and anyone else) full license to use it for any purpose  
including commercial as long as you're saying bad things about walled  
gardens.

The important things to notice depend entirely on one's perspective.  
When the Duke of Leinster built this, he was no doubt very satisfied  
that he could control what grew in it. My observation, and if I  
understand your point at all, yours, is that the real growth is found  
outside the wall.




--Apple-Mail-19--238326440
Content-Disposition: inline;
	filename=IMG_0163.jpg
Content-Type: image/jpeg;
	x-unix-mode=0644;
	x-mac-type=4A504547;
	name="IMG_0163.jpg"
Content-Transfer-Encoding: base64

/9j/4RkYRXhpZgAATU0AKgAAAAgADAEPAAIAAAAGAAAAngEQAAIAAAATAAAApAESAAMAAAABAAEA
AAESAAMAAAABAAEAAAEaAAUAAAABAAAAuAEbAAUAAAABAAAAwAEoAAMAAAABAAIAAAExAAIAAAAQ
AAAAyAEyAAIAAAAUAAAA2AE8AAIAAAAQAAAA7AITAAMAAAABAAEAAIdpAAQAAAABAAAA/AAADTZD
YW5vbgBDYW5vbiBQb3dlclNob3QgRzcAAAC0AAAAAQAAALQAAAABAABRdWlja1RpbWUgNy41LjUA
MjAwODoxMDowMSAxMzoyMjozOQBNYWMgT1MgWCAxMC41LjUAAB6CmgAFAAAAAQAAAmqCnQAFAAAA
AQAAAnKQAAAHAAAABDAyMjCQAwACAAAAFAAAAnqQBAACAAAAFAAAAo6RAQAHAAAABAECAwCRAgAF
AAAAAQAAAqKSAQAKAAAAAQAAAqqSAgAFAAAAAQAAArKSBAAKAAAAAQAAArqSBQAFAAAAAQAAAsKS
BwADAAAAAQAFAACSCQADAAAAAQAYAACSCgAFAAAAAQAAAsqSfAAHAAAJRAAAAtKShgAHAAABCAAA
DBagAAAHAAAABDAxMDCgAQADAAAAAQABAACgAgADAAAAAQ5AAACgAwADAAAAAQqwAACiDgAFAAAA
AQAADR6iDwAFAAAAAQAADSaiEAADAAAAAQACAACiFwADAAAAAQACAACjAAAHAAAAAQMAAACkAQAD
AAAAAQAAAACkAgADAAAAAQAAAACkAwADAAAAAQAAAACkBAAFAAAAAQAADS6kBgADAAAAAQAAAAAA
AAAAAAAAAQAAAGQAAAAjAAAACjIwMDc6MDM6MTcgMDA6MDE6NDQAMjAwNzowMzoxNyAwMDowMTo0
NAAAAAADAAAAAQAAANUAAAAgAAAAdAAAACAAAAAAAAAAAwAAAGsAAAAgAAApsQAAA+gaAAEAAwAu
AAAA5AMAAAIAAwAEAAAAQAQAAAMAAwAEAAAASAQAAAQAAwAiAAAAUAQAAAAAAwAGAAAAlAQAAAYA
AgAWAAAAoAQAAAcAAgAWAAAAwAQAAAgABAABAAAA40IPAAkAAgAgAAAA2AQAAA0ABACUAAAA+AQA
ABAABAABAAAAAACYAQAAAwATAAAASAcAACYAAwAwAAAAbgcAABMAAwAEAAAAzgcAABgAAQAAAQAA
1gcAABkAAwABAAAAAQAAABwAAwABAAAAAAAAAB0AAwAQAAAA1ggAAB4ABAABAAAAAAkAAR8AAwBF
AAAA9ggAACIAAwDQAAAAgAkAACMABAACAAAAIAsAACQAAwBOAAAAKAsAACUAAQAOAAAAxAsAACcA
AwACAAAABAAAACgAAQAQAAAA0gsAAAAAAABcAAIAAAADAAUAAAAAAAQA//8BAAAAAAAAAAAAAAAA
AA8AAwABAAFAAAD/f///cK3oHOgDawDdAAAAAAAAAAAAAAAAAAEAAABADkAOAAAAAP//AAD/f/9/
AAAAAAIAsSkmAd0AAAAAAAAAAABEAPP/oADUAHQA1QAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAB
AJkZAAB3ANQAAAAAAAMA+gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAElNRzpQb3dlclNob3Qg
RzcgSlBFRwAAAAAAAAAAAAAARmlybXdhcmUgVmVyc2lvbiAxLjAwAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAByAQAAmwEAAAAAAAAAAAAAAAAAAGYBAAB+AgAA1////wAAAAAAAAAA
AAAAAAAAAABBAgAAowIAAOX///8AAAAAAAAAAAYAAAAKAAAAAAAAABsAAAAKAAAAAAAAAAAAAAAZ
AAAACgAAAHwCAAByAgAAdwIAAGYBAABDAwAApP///wAAAAAAAAAAcgIAAHcCAAAAAAAAAAAAAAUA
AAAADAAAAAwAAAAMAAAADAAAAAwAAAD0//8A9P//APT//wD0//8A9P//AAAAAAD0//8GAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFEAAAAABAAAAAQAAGP+///hAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAvAEAAAAAAABj/v//5AAAAAAAAAAAAAAAgDgFAHw4BQAA
AAAAAAAAAFUEAAAJBAAASwQAAF0FAAAAAAAAZv7//+MAAAD8////wQMAAEsIAACiBQAAwQMAAAEA
AACKAwAAMAEAAHwCAACTAgAApP////////8AAAAA/wEAAAAAAAAAAAAAAAAAAAAAAAAgAwAABQAA
AAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAJIDAAAAAAAAAAAAAAAAAAD/AQAAAAAAAHCt//8EAAAA
CQAAABgDAAAUAwAAFgMAABUDAAAUAwAAFAMAABYDAAAWAwAAEwMAAP//AADABAAA5AAAABcBAAA0
AAAA2wAAACkAAAAAAAAAAAAAAAMAAAADAAAAFgAAAAkAAAB9gYv3AAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAABgAAQACQAJAEAOsArABOQA2wDbANsA2wDbANsA2wDbANsAKQAp
ACkAKQApACkAKQApACkAJf8AANsAJf8AANsAJf8AANsA1//X/9f/AAAAAAAAKQApACkAMgAAAAAA
BAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAEAAAACAAIAAgACAAAAAAAA
AAAAAAAAAAAAAAAAAIoAAQAAAAQACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKABAAAAABAACAABAAEAgALgAQAA
AAAAAAAAAAAIAIABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAAA
AAAAAACcACMAAABADrAKAQABABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOIwAAAAAAAAAA
AAAAAPTETMYGzM/RYyezhYtOXxZJSSoApgIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAA3qgAAAAEfACm/gAAAANcAAA5AAAAOQAAHAQMAAwAAAAEABgAAARoABQAAAAEAAA2Q
ARsABQAAAAEAAA2YASgAAwAAAAEAAgAAAgEABAAAAAEAAA2gAgIABAAAAAEAAAtwAhMAAwAAAAEA
AQAAAAAAAAC0AAAAAQAAALQAAAABAAD/2P/gABBKRklGAAEBAQBIAEgAAP/+AAxBcHBsZU1hcmsK
/9sAhAAHBQUGBQUHBgYGCAcHCAoRCwoJCQoUDw8MERgVGRkXFRcXGh0lIBocIxwXFyEsISMnKCoq
KhkfLjEtKTElKSooAQcICAoJChMLCxMoGxcbKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgo
KCgoKCgoKCgoKCgoKCgoKCgoKCj/xAGiAAABBQEBAQEBAQAAAAAAAAAAAQIDBAUGBwgJCgsBAAMB
AQEBAQEBAQEAAAAAAAABAgMEBQYHCAkKCxAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1Fh
ByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZ
WmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXG
x8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6EQACAQIEBAMEBwUEBAABAncAAQIDEQQF
ITEGEkFRB2FxEyIygQgUQpGhscEJIzNS8BVictEKFiQ04SXxFxgZGiYnKCkqNTY3ODk6Q0RFRkdI
SUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqCg4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1
tre4ubrCw8TFxsfIycrS09TV1tfY2dri4+Tl5ufo6ery8/T19vf4+fr/wAARCABLAGQDASIAAhEB
AxEB/9oADAMBAAIRAxEAPwDhdGUXVwkKKg8pPkjwcMTzhvbgn3zW9d31ta7o7e0WFWj2EAdQBgjn
sfTtWBZ2F9omp3cN2sVrIIcgy/OFUjIIwcHI757VGZx+8f7QjsfvbOh/znNc97ItHY2+plbNw8bN
O5iG4YUqSQRjt0/rXoWh6+UuImmeJpWAVAjbnYn1Y88DHpXio81RG5Ysxx8p/h4//VXTeGdTfTtT
R0BlkDhRu6gZ6Y7VcalmNxufSVuTLGrY6iriLiszTdUhvbVZYmU44baeAR1FUdS8c+HtJYpdarCZ
R/yxhzK/5LmtncyOkorhU+KWnXE3k2Wl6jOSCQ8iLEpx/vHP6VL/AMLClz/yApce1wmam6GdrRXE
N8UtLtpFjv8AT9QtSRncIhIoH1Uk/pWmvxA8Ny2T3cGorOE4MSKRJn02kAj8aa12A6SuV8QeOrPS
w0Nltu7kcEg/u0Pue/0FcjrfjO/1yKRIs2trnHlo3zMP9o/0HFcpNIkSM8jKiDqWOAK0UO5Dl2L1
94g1TULlri4vpi54ARiqgegAqv8A2ne/8/tx/wB/T/jVWN0njWWL543GVZTwR6inbf8AYb860siL
nNeKvCupaxqS6hDFHGhtoi9sWyRtGOD0PXNc5dQG1t5o7iGaKaRWALjb0wevfp9Olek215Cb23gc
F90CyAd8EnHPbv8AlUlykc18umzIk1u0e5lbB5zjH868pzs9UdvKmeUW94xQSAknaOv8P1rQs7sh
w5fcSc55rode8N6NYXq+WskcEq7mVXJAwcccE1ly+HJrNZpTdIVjPC7SCR/kVdrq5Ozseq/DXxXa
R2stpqKSiELtEqqWUZ7YArEksY7KBYrBXDK+PN8vlh0BJYd+KyvA82bS7HUB1wfwqbSb97i3vC5k
IjdV+dy2CDz1rWEr2uRNb2NW31qxjmVZ7mGGSJSr+Y6jnAqj/b7b8f2vHjP96P8AwrnpH0jUZpZJ
44eHxudgN3T1qa20jRprmEeVAYinJBGDgHNbKMVdozbezOwa/hu1VoZI5vlwzqwbkDPasbVtc03T
Ytk1ygkznyk+Zz+ArI8URR29lbwabM1tbhnEiW52hiB3I9xXFGI296xRdyjJ9+xqFNRWiKtzPU29
Q+I9wBLb6XaiMgj97cc/kBWHd3FxqW2S8u5r13JyhJCp6EAcVCbG61O/uJbSNDGpDykkLtB74q/p
9hdiYW8U0MbycLJgtjj3HXpSc2+o+Wx6HpCGPSrJANoWBBtPUcVc+b1FQaba/ZtPtYHIdo4lVmPc
gcnmrWxf7o/KupbGBympySR6taSBXH+hxtIASMYOCD+JrLTVJ4LpZEkYNJGzHnPPUnP41f8AEEh/
tGyG7YWtkYkY7ngn3+WslLf5Ioy52Kpy4OMjHP8AKvInbmOhux0uvzgnTBO4HmRbmweDkjiqsk8k
qTwSuyoAx5HUk+v4mqE2ow6oYRHcKr2ybIhMCB/30OM8dTis+4uryAkTo7F/uuv3WznoRwenrVe0
93lSDn966Or8KFbOzm3uFJOfmOKjhb7DJOkMkH2eW4zIdwzt9ua4y9sdQe0LTSPD5+xgBzjAP485
q3pOg3ipITes7ygHJUqqkEHJLY/zmtIt72Jbe1jSey01jMibJnWQ7dxBIFQeH7D7Pqu5o2Ay+0t/
uHpXTWMUtxvZL6CVQcyJ5AB578VoCNokZN2UYYIzj+tdKblH4bEdbsyNdTfbRDoPMf8ArXM3MJa5
Yj5UXI5PXiuj1e5iCxRMxVg7bWYD0/LvWXcwSytkXPynOBsGMZqGnZKxXNZ3MrQ2VLi7AkwGRBnP
UZpLO5JvYkdxtVyueOnP+FV3tJVkvXjOVgZd+1cZHNY/2IqSGleMPIPvgjse5qUminK57PbO7W8R
LAkoOcVLlvb8qo6XMqaZaKz7iIUBYnOeOue9W/tCf3q7VsYM5t9Ia/uVkknKRxxoAVBycDpzT75N
Ps7SaMAAsjAySnJ6fp+FdppXhqa+Csw8m3P8bLy30FdNDoGjwoLaPToJ3HJMsYc59STXHGmnqdDd
j5h0lJmdvJywPBbqPqK7HRNITSIHv7h3RWHyxZOZ27ZH92vV9T+G2i3Mz3MkksLykARW+1E6YwBi
uS1bwJrlrDLfTTwSW9vH/qlkJfavAA45OP51LptO4R5UcvBONRux9qjXezD5o8qfyIx+ldlrEQtL
aR4LGGTa4jUSqGXG3pj8a57RbEy6tHG1pNFEdxBZCMYUnBJAHau11bRIp4guZwh5ba/OccU6cRy0
sjkbJNStZT9qtFVZFCjeo/vLyPettoUW6kjMQCIg4OTzz/8AWqsugAP8rycdN7dOfaryWMkDbmZn
bHJ9R/KtdjN6mTqmiR3yZVfLYcggf0rj9Qt7zSm2yJ+7zww5X/61d3ePEhyZWjHUZDHP4CqLy28s
TrcZOeAqwtz/ADptXGpWOGhvoovMwmxpSNzfeB/A1YuAtzt8tEfrkYHH4cGtS98LC6T7Rp6yREcm
N4zg/SuefTr+GbY1ncI47CJiPw/+tWbUkaLlkehWC7LC2U4G2JRgfQVYz71m2MV2thaAxz58hM5Q
5zipvLuv+ec3/fB/wrrWxynTDxHqYHF6f++F/wAKcviDVSci9474Rf8ACuYW5lMSsWGSP7oqpPe3
AfiTHA7CvOdZLc3bR2LeIdUPDXp/75X/AApp8RanwRen/vlf8K5J7242E+Zzkfwiqx1K73keb/46
P8KX1lLuK6O0bxFqeObxzj1C/wCFN/4SHUz/AMvj/kv+Fckt7cZUeacbR2FK15OFbEmMHjgU/rCH
dHVHxBqi8C9kAz2A/wAKafEWqjGNQk+nH+FcXPqN2qsRMR82Ogqqup3hUZnJz7CpeKiu5LkjuG8Q
6uf+X+T8x/hUTa7quf8Aj+lx/vD/AArlPt9z5THzOfXAqpNqF0GBExzx2FDxcV3DmR2Lazqv/P8A
T5/36hfWdSPXULn/AL+GuP8A7UvTn/SG/IVnXupXjHm5kH0bFH1peZPPHsdw2q6jn/kIXX/f00n9
qaj/ANBG6/7+muHtdUvVix9oc85+bB/nU39rX3/Pc/8AfI/wqvrKDnXY/9n//gAMQXBwbGVNYXJr
Cv/bAIQABwUFBgUFBwYGBggHBwgKEQsKCQkKFA8PDBEYFRkZFxUXFxodJSAaHCMcFxchLCEjJygq
KioZHy4xLSkxJSkqKAEHCAgKCQoTCwsTKBsXGygoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgo
KCgoKCgoKCgoKCgoKCgoKCgoKCgo/8QBogAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoLAQAD
AQEBAQEBAQEBAAAAAAAAAQIDBAUGBwgJCgsQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNR
YQcicRQygZGhCCNCscEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldY
WVpjZGVmZ2hpanN0dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TF
xsfIycrS09TV1tfY2drh4uPk5ebn6Onq8fLz9PX29/j5+hEAAgECBAQDBAcFBAQAAQJ3AAECAxEE
BSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZH
SElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0
tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/8AAEQgB4AKAAwEiAAIR
AQMRAf/iBShJQ0NfUFJPRklMRQABAQAABRhhcHBsAiAAAHNjbnJSR0IgWFlaIAfTAAcAAQAAAAAA
AGFjc3BBUFBMAAAAAGFwcGwAAAAAAAAAAAAAAAAAAAAAAAD21gABAAAAANMtYXBwbAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC3JYWVoAAAEIAAAAFGdYWVoA
AAEcAAAAFGJYWVoAAAEwAAAAFHd0cHQAAAFEAAAAFGNoYWQAAAFYAAAALHJUUkMAAAGEAAAADmdU
UkMAAAGEAAAADmJUUkMAAAGEAAAADmRlc2MAAAGUAAAAPWNwcnQAAATUAAAAQWRzY20AAAHUAAAC
/lhZWiAAAAAAAAB0SwAAPh0AAAPLWFlaIAAAAAAAAFpzAACspgAAFyZYWVogAAAAAAAAKBgAABVX
AAC4M1hZWiAAAAAAAADzUgABAAAAARbPc2YzMgAAAAAAAQxCAAAF3v//8yYAAAeSAAD9kf//+6L/
//2jAAAD3AAAwGxjdXJ2AAAAAAAAAAECMwAAZGVzYwAAAAAAAAATQ2FtZXJhIFJHQiBQcm9maWxl
AAAAAAAAAAAAAAATQ2FtZXJhIFJHQiBQcm9maWxlAAAAAG1sdWMAAAAAAAAADwAAAAxlblVTAAAA
JAAAAp5lc0VTAAAALAAAAUxkYURLAAAANAAAAdpkZURFAAAALAAAAZhmaUZJAAAAKAAAAMRmckZV
AAAAPAAAAsJpdElUAAAALAAAAnJubE5MAAAAJAAAAg5ub05PAAAAIAAAAXhwdEJSAAAAKAAAAkpz
dlNFAAAAKgAAAOxqYUpQAAAAHAAAARZrb0tSAAAAGAAAAjJ6aFRXAAAAGgAAATJ6aENOAAAAFgAA
AcQASwBhAG0AZQByAGEAbgAgAFIARwBCAC0AcAByAG8AZgBpAGkAbABpAFIARwBCAC0AcAByAG8A
ZgBpAGwAIABmAPYAcgAgAEsAYQBtAGUAcgBhMKsw4TDpACAAUgBHAEIAIDDXMO0w1TChMKQw62V4
T012+GpfACAAUgBHAEIAIIJyX2ljz4/wAFAAZQByAGYAaQBsACAAUgBHAEIAIABwAGEAcgBhACAA
QwDhAG0AYQByAGEAUgBHAEIALQBrAGEAbQBlAHIAYQBwAHIAbwBmAGkAbABSAEcAQgAtAFAAcgBv
AGYAaQBsACAAZgD8AHIAIABLAGEAbQBlAHIAYQBzdvhnOgAgAFIARwBCACBjz4/wZYdO9gBSAEcA
QgAtAGIAZQBzAGsAcgBpAHYAZQBsAHMAZQAgAHQAaQBsACAASwBhAG0AZQByAGEAUgBHAEIALQBw
AHIAbwBmAGkAZQBsACAAQwBhAG0AZQByAGHOdLpUt3wAIABSAEcAQgAg1QS4XNMMx3wAUABlAHIA
ZgBpAGwAIABSAEcAQgAgAGQAZQAgAEMA4gBtAGUAcgBhAFAAcgBvAGYAaQBsAG8AIABSAEcAQgAg
AEYAbwB0AG8AYwBhAG0AZQByAGEAQwBhAG0AZQByAGEAIABSAEcAQgAgAFAAcgBvAGYAaQBsAGUA
UAByAG8AZgBpAGwAIABSAFYAQgAgAGQAZQAgAGwgGQBhAHAAcABhAHIAZQBpAGwALQBwAGgAbwB0
AG8AAHRleHQAAAAAQ29weXJpZ2h0IDIwMDMgQXBwbGUgQ29tcHV0ZXIgSW5jLiwgYWxsIHJpZ2h0
cyByZXNlcnZlZC4AAAAA/9oADAMBAAIRAxEAPwDySxa5uEmjgZ3MmPMhVclgDke/UD8q6HSktZbW
S3kjVLgMHlaZtrIozkKOueh9eKn8IRxafHJJcTzWjNIEleNRkp3yf7vsPSo5JobnUrm61KNryC4l
LI6yAMB2bAH93txWLa7lJDdannublZrppHCxiOKV02mRBwDjt/8AWpNHlNhc/bAQ3lKWVVYDJ9O/
8q2PHNrZ2y6Nc6RlYbqB2Fu8pcIMr05OMkt+XSuPaSWVQ0OQehH9zFQ002NM1re6ls9SS588Ca5D
SyMByGJLbv51oww6zr0l9FpsF7LaXTq07Abi2Ohcgdzk4+npWPp+j3dzBcX0RBFmokaRz1weg9f8
M16V4G8TQaTYtaQ3S+QjrIDhcbW6gjrlSD36EVcEk/eBqx59baFdHX9Q0yxkkaS3GdpU5K4B+b8D
wR7VsxhLy2tdPlMkX2dnQQhACrnk545JIAz6Vv8Aw2vraXxPrWrzZjS7ZoVkUYUAnK8fQAfzro/F
uhnVYbjWNOVWkt1CkR43OgP8H+0OoPbkdCark926Ffozzu30O7+0SSL9pKAFVZMBtvqR6VpXvhXV
BpBvbWM3tsVaRwZdzK3c5AxngZB69qjtLq4S2t4VYSec6TxEgDzOemex+8Oa3NRvUVN9qzWfnw7p
oNpMZzwrYHQ9Rk4z3pRUbDZS8Ja4k8sttdlWcR7I4TCQWGOS3XGAMGpPFtlPcWf2iWJknhj2yK0g
OAPQY6ex454rL1iwTS9QglkupHnBH+lI+McDDcdO/HII9afrWs3UsE4ubqC5E4Cq8DgN6fOuTwQM
U3L3XFhbW6OfdLtdMjVfMSyll8woV+UuuRkN64JyK9K8bwWY8IwSrEqXE6xJGMck5GfrwD+NYNx5
V18PVihVGa0mM0hHG0btuG9T8+R9KybS9vNfXT9Ot5BP9hVpf9IfAByON3pgY59aNk497A9WbV5b
S6Po0LNexSwzwiN8whvKcHkAjnJUdefugVN4ZsNTju01dopPtb5EMRXAVTzlj2Y4/EH3rL1DWl1u
5Bup0tbS1Y3G1vvSv8oYKRwehx68+ta8fibVNT04tbW50+ygYu9yFy+dvUg8DPqcnpVxabuJ3LVg
1vfXl/Ld3KWoW7ZZJpvl24JGEBzlsKvOOPesS91eG08Qs+mmSaWS18qB4yxzIWPzNknIxkn+Vege
GfBulQ6TbfaBHJqjxiV7pl3kuecfN064469a5LX9WFv8REnST7ObaxMLSFQTDkNnHYsc4X3YVcla
1xK17DtPvbTSvFE94NR3n7Koefb88krdcAjjoOgwBXf2Op3U1sn/ABJ52WM7lllkEYQY645bpx92
vG5IQupPbxpcT6k5R5JFQOyOR8y+nXjPt711zaHcrHYz3Vu22QoqWst4ZhKcE5ckjb06LgYBJz0q
YtjaOq1HxHd3F29tZwWd2VZUnzO3loRzgyFQB6YHP5Vdisrm6vVvbjxDHG3leWsNucKmTyFcnJPT
J746Uzw9bz6bFHazWIhlU7NtvDlAuP73bjqWx0qXXvECacsVpDj7VO2EXy9zIvO58DPA7Z4zWm2p
FuiKUHhzRr/VpUlU36WzAE3Nw8zzSlckAk4CqCOg6n2rdk02yjuEkht0W6IwnHm4A9dxP6YrJm17
TNHtxby3ECB2wjBy0gY8szg8kn198VL4YjvdVSe8lnnsoJCvkrgJI6jnJHUDnHvz7UJhqdVBdTRQ
otyFErdFUdR9O1WvNkJwI8AdSxrK+yJatGfNEikgNICQ/HTnP+c1dtxuO8szBugZs4pkltCMU6kA
x0ooGLS02loAdS02nCkIUU6kApwFRcoKcKAKUCkMUUoFAFLQAUUUUAFFFFABRRRQAUUUUAFFFFAB
RRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFF
Fcx4h8c2Gih4YCLu7APyKflQ/wC0f6Ci1wOhu7u3sYGuLqZIYl6u5wK878RfEaWbdbaODEnQ3DD5
j/ujtXJarr+oa5N517MW/uxjhE+grOAOev1rRQ7kOXY8pkupBEhwSpX05HbINNkk8u3aVJVwGAMY
PzDjg/SnW2ZrOFRMFZGypJHvVy8tba90uUCOOPUogZFKnHmrnke5AGa4etjZ9ypeai9xBZwtKxSB
THGCOQGJOPzzzTrGFZp4bdG2l5FjDDnBJxms+xjLW+ZCM7go9uv+Fdn4I0OHUdWaOdPkaFjlMsRw
QCPfJFUlrYZpRTGLRL3S0sf9IjWYPLu2KwDBcqOrc8EGsLUri3TyoYLIQOykIXYNkHgnPGPmAx6Z
ar8+vWzaFbafZ2yT37BnEuzLxsXznI5Y4yMelU7CxknvLtrmIz6kZgJrZztZO78dDwDgDviqeojr
PDNx/wAI9CdM1bSpU8weYJA4XknAJJIGMjhv8npP7ZijWYf2dcReTGxkEEiSJwP4V3AY5B/xrkYm
/tCxlgnuJZDbHy0jkUbygB2HDcgYI4/GqSTXunQSGKZzbvHh+hZByMc9en6VXM1p0Bq4tyws7e1t
mB+xugmjd42BDEruwTjPOSPTJqW3ube1huXuXjlgkdTJ5hzJgkfcPsScimqWu44LR7sqFmJAkiCq
hI+9j1H9KzJGld5IpcOqEx5jIPQ44B7d/wARWV7O6KsbV3ew36JbkiX7MsiF3JJZdwK4HfjP5n0r
M1G2gsdKa2eBFu7efb5wjwZEIyDnuCMHmoIpDcoiIq7oyw3g/M3fnvj0+pqC/Yy+WzShlZVBVech
emT3POOKfNdBboamntPHod9GCrQTxHzEByG5288fKQxUj14rL8P2V3I9xHDO1uHTa7Ln94uQGXp0
9fb60+e7K6Vbx25EMhMqSyDq6nGAeeQMH86k0OaZmeKxlkW5nG1An3Qp+8ead9UFtzqH0w61HHaa
dCZIdOBCZVV86Ynld3oF564B9hUD3sMmlXD+eu2d5CYsDdGpcbtw455IGOwqsmuyWWn2tqkcsbQu
QXQgox7k9wfbvVrw34dudes5rn7VDb29xO7OoVTKw74PbpwK0vd2RPqdh4f8QnDo32h4omJaaR9y
upztGB83A61yPjKUjxFeXIuoWP8AZ8U0TKmFypVgo5OT8o/OrA+z6bqMsUErmOJQx2v8zEAcHoOT
9Tz3rnfESl7iKTylInBCbcAMA3v+NOUtBJa3Ol0yQ+HoURJDd6nqMSX/AFyZGJJ2ccgDHJOO9a0M
+keHLbzNRWLUNQEheaWRdyh2BbAzkADgcc4rgtHuoYYpr2Se6yjLGxgwBg/w7jz0z0H8qs28F7qc
gleylYOpliaWORkVcn5gBnJJHJPU0KXYdtTr28UC9S4/snS70eY+6S6jaRIlPCjCqfujtkj6dqPP
ktJ5E/tX7M7x4kmO55Z24ALO6gEBTwFAGB171UsptUikRn1y2BCfvIzK0B25yUHy+3UY60y/1MX9
7aO1lcC3h8xZJd7PGTj5AGHTOGz7Zqr6Csb+gXFjLdz3l5bo7zuY472ScSEqF4wWJIzyR+ldha3U
0MIezaS9hC/M4HK+2cc/0rEsbfTltCXis70XBWQz7IwrNtAwuewx2q3ZoJC0ml77a3VtiwkssZIH
PA7f/XxVolmje6pFb2kjzRGWdmXbFEpLEnGAMVq2dxcSl5ZIPJ9FYglR+HH61yNnel9TlvLqSOKK
1Iii8uU7FyvzkE/ey2V46bSK6aHUYmQGKQzyTKdqIME4789AM9aomxsxFgm52znmkMmzBbGT271W
gS6dFM0yjnOIh1P1OasJaoH3sGd8YBds4/pSAlUkgHbj8afQBS0AFOFIBThUtjFFOFIKcBUjFFKK
KUCgBaKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACi
iigAooooAKKKKACiiigAooooAKKKRmCgsxAA5JPagBap6lq1lpFuZ7ydYl7DqzewHeuZ8Q+P7ex3
W2mAXM+D+9P+rX6f3v5V53fX91qMpuLqZ5pW6lj09h6CqUbibsdB4g8d3uq74LPdaWp44PzuPc9v
oK5R1yjk+hpwHakfiNv901qlYzbuV0HAz1xSgAAA0KM4PSlyM0yTyGyVv7P81VGFb5jnnB9Ks29+
lzHKPMAMKkhW6/hUdhaXEunskQ3rG29gMHA9agvYrW3HLhJuRx3A9fxrzna+p1EtvEFdk2gYmDqP
UEH/AOtXa+FNSg0+21tmnEV01oUgbjqSOPr3/WvOrASzzb2kKZUBW6kgVvXVskdrCYXCGN9rg9WG
M5Prz/Onsw3Rp+Ema08yZLGW5k+WKKaLnyzkFifqNwrppIpE11dSs7Y+fHKH32cyzMf3Y3AgnB+6
SR7modCifTNLtJpnWJZlNzE9vzJu3BccdeGIx7+1PtGkuNeWXVGVbWbDfM3zAHIUvtIB4PIz0PPS
tUtkDItW8Q6e+sf2lZCO4eUMs8MqmI4zweuAR7+45rDTXIy0u+wlmldSX+UMo46jbwOvNdF4htLX
T7y6RQsCbRInl58p8HBx6cH8KhtbuRrG5jZ/JiQSGJmiDEjGQAeCPTPPX8am12C20MF71WKrMpiA
AYDBGR659Caaqh7yGW32cAMGfhCB/Cw9avy3ME7tEFjjuQ6CFk6KQGJbPcliOD6+1Z1+iWtzOcx/
uQJCjqAGB6lR6HPSsnHW5VxJBJKvntswHxLsG3nP3fr34p906CGOJhE5JDeapwwGD8p7VBbb5wFd
SiyN85QfMSeVI9ufyNJeRBH8vexRDhfMBU/XHagaIYovOjleTcRFgFSuQCTjt+dbmgQARTGOZkYj
a2YwyleOMH8+OmKzFdBpruXO9plUL2xgnP14H5103h2CZoo0snWO5wzor8FsZ5X8ByDxVQWo3sZO
o3DhPsxlRiVw67SowMnnofQVoWsy21hEJ7u4traGFWZY2XaznqQc9dpxWXqUVy1pPfXCYikk8mN8
jdkdceoz+HFT21ut4IDeMQ8wCRPIBswcKSB3IHU9elNbk2JreS51S9V7RJ0WV2MEt1gso9z1bjHp
j6Vk67Hc6bdxxTyNcTrmKRWyNoHAAz2Nd3qUtnE1lJI6kBngHlYI2r8oIHrnkEdgK4nU72WbV0ur
uVnmVEG5eWP93HPHbinKyEanh/RJNajnuLhUQWUMcaR5Eakjhc+rEZ645P4V1un6wbH7RE2pWyvt
8tolDZKgsMDJ+UduR74rB0sX00FzeyXEKcm6liaPeXYHaM8gnucDj14q94dvk025uLm4aORPMVQN
gxkjduxjAHOPrVp2sDR2UmvG2tYJmhkeZxndEm4Nlvu5bGeKotPPPeQhpys0lwxCQP8AMF2HqewB
OMe9VrnXLG8aKCNVRVYrJI7HaqkHpz16c5A/Cs3R7i6utRd7eSQGRVUTyKM4UkHYfc9SfQ1fNqSk
dLawQLd3Myv9nltd3CgBdxG7ew/3Tg/hVS7v7z+z2uYr+JTOskiRsmZGOOCcYAJ3dMenpWJ/a/8A
aF7cCedUspWVHfeBuCDBHX7vU4HXjntVSfVDNqE9xY2kl5a2zg+dIzCMsMY+bnIBXgDv9BS5gsdn
axWVrBJpt1a3d5qkeAbZbg7nwBt2qvyqgAHJx09a6HQdLuJIxJqLCafCmWQscqw6op7qP8etc9oX
2wCY2t7aXst6RJNMscjNCTwoLZIIXtnGBziutje+QNaoba5KhVxEzD5e+c8A49TVolmzHFFD5flh
m3dNzE/zqUTNkgDcc4GD1qlbRiKNZ70SCTG3YxyFGemBnJ6c1oQhWGURU+i84piJEDYG7Gfan4oA
pwFTcBAKcBS4pRSGAFOoooAWlFNpaAFooooAKKKKACiiigAooooAKKKKACiiigAooooAKKOtFABR
RRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRTJp4raJpppFjjQZZ2OABXBeIfiCz
MbXRxtBzm5Yc/wDAR/U00rgdXrPiLT9Djzcy7piMrCnLt/gPc15zrfirUNbYozeRbdoYzwfqe9Yc
1xJNIXmkMkjHJZzkn8akTYfunnua0UbEOXYryjEgz/dpGHFPnI80AHPy1GTxVkDc4pr8o30NISec
0mfkf6H+VAEY6AUYA/8Ar0xSTjPTFPLZoA8khR7C6kt2MgRSVcEgMV644/Co9UubdmK+SsZZcbVz
19cmo2XytzyPKgHCDqSewNROu7z7lgS6/LEOvP8AjXnnQP06XbiM5BjGOT1Oa0ZWa4lMZHKRsxPu
efxrHsYCrl2wCPmJPQVt6JYXN5Z6jqO1fJt1XzCTzhmwMUNPcDrNC07VdIjGpBVmk8gO0RDKyRMp
+YHGB0Iz0/OpRfQ3urSSTIyvEqCWC44dcEgZ45xwM+nNaum6mL/S4dN1aKYtErR200T4YqRgRkcZ
XsRnkGsTUreXT9QtZZ7eV2g+aUQyZ8636HB6/LjGOueavTpsV1IdRS5uBcrIqz21n8wePkRqSCMt
3x0BOemOtZlvq87l4dkku5vkBbGMjHI6Z6Vp3dzHfSXLQqEjdIw0jvkkZAH6n3rMszabJZWbLtIX
kZzsDYwCuehHvis2BWmmeWSNwAJW5KFCc47/AMqfbeZqNw9/IZrgx4KckgY7E9QPSqbO6RuGUieX
ADCTOxRnI989KvadqK6dbeVC+5peJAR8uM8BuxHQ0tguWljjRxPDJsS4d2SFgQVYHIB/A8fjRrss
W+GWOKPa4zuUEeZwDkg5x1qjHfSRubYugUblXgORxyPTr3qUs89jgD/UOMMw9QOn5Gm9horE7cBB
wG3E10setM+jx6fFAjuwCRkDDrySxz64J/OudhWN8fMQCcbUHJP48dKuQmTynmUBU4VQ3J98VKbR
Vi1qVy161vZOsoht4zI6r0XAIXHtknP1NJPdx3FyjWFn5S28SghRkO4X5nPYfhWc08jyySIzKSAu
SB9zGOtRnUEhBRMu75G6N+Cp7Yqua7Fsakl0/wBnSVsORhTIW5HGB+FZt3L9ovvNkOxiQ3QnAHIH
5gCoWnkLATQSZzwuRitTS47SOZvPjE5CkAycqWPr/Sktxl3Rke5hmd9RFqofzHgC7sgDOSTxkemD
UcFst5OfKuZS8Um5fm42n73A75A/Sq9jFCu4tb+csbjdhSSw7ipL37NbK0thJIiYb5ZozuUcEEHt
VdEJmxY6VaW1/EJHYQHcwMjdHX+AnoGPb0pk+qgWjW0ODIE8uJ1cBR8xyeOvHQ+5NYc2sSzWSWsi
B8P5ivuJ2n6evX86ZClxdTBY4m2KAGQEjcMdCfwov0QrdzYa0bU42ultRDZQDyYsfMWkwOgPUnjn
3rpdH065e903TtZ83ywFWOIvtjGOehyCTj05NZfhyEJNFPJMyBJW2GMlgrEHAVT3yMepxXTWetyN
cSy6gnnzWysW2qY2TsueOpzWkbAzqLPSJ5bvNnJ9lEBbzbhCFcnsDjIbjHB4/pv6bo0loQWuJWZz
vaU7S7MerY21znhm8uzI4mmaSTdv3qvz88BT6ADpnHfg12tjI7MzyOD0UHP6dBWyMmXYLdIQCAS+
PmdurH3qbjriheQCO9LikxCgU4UlLSGKKdTQcUZoAdRSZpM0AOozTM0ZoAfmjNMzS0AOzS5plKM0
AOzS02lFAC0UUUAFFFFABRRRQAUUUUAIhDKCOhpaan3BTqACiiigAooooAKKQd6WgAooooAKKKKA
CiiigAooooAKKKrX2oWumwGe7mWKMdz1PsB3NAFmsDX/ABfp2hK0Zb7RddoIzyP949v51yuveOrq
+L2+nbrWDoZP+WjD+lcPGN5BYkkk5PXNWodyXI19W8Raj4hlLXUm2FTlIU4Rf8T7mstid4P8WD+A
qVY/LUrjqaZIuJF78HpWtrGb1GA/LuPJNOWRhwKiZjwvTFOU8ZpiFc5bOeQKGPFB4K+pH9aSSkMi
3jkUNnY/+6f5U1VC/iae3+rk/wB0/wAqYEaDKUvAyMU5MFAKa6Hr2pCPJL6ZzYzJcJtmK7gQMbST
nGB0/wDr1TjnDWS5X7wyVP15qzqlq1q8tuCGWMhS27IYevuP8apX8f2dLZwfvJgivPS7nQVvPKDy
oFLGU4I9a9E8NTvb+D9XtVgaRJoi8skUYO044DHsBjP5159a2u53mBOVBIqezuLuDcPMeON8BkB+
8PQ1V7B0PQ9R8QW6RwC7UMsaqAu5QSQMHhTn06jsKxNQ8YwTNBNamZbuIMrTbBllJ4PXkgAfnTP+
Feaqxt7qaWBFvCHgKtv3bskAnsTSf8I4+nXf2a9s081lDFrjdhQeNxA5460O/UerKdtrUMEKYt/M
jT5dsgzuwc59QT0OKfLqCHTbK1CMJ1LNNKOMgnj68iornSTaW5aNAUklVYsKczbsgFfb5TUs9hcW
9w8Elq4uIQfMjPJU4zg46dealoZF5iSR72BGzK/KO2Mg0sEUl5b+XBbo5Vs7269OgGec/ias6a1v
DHI7lfNY7lTZmMDuPyOK049SYmQ42OI0RPL+UBlzg8enWkrIZibLqF2LOiSch0HQnBx9K0PtGrSY
EkMdwfKVQQOQoUYx64Bx/wDqqpqN0RcTeY/nSk8uOQ3c5x357Ve0j7ZLbXEtncsq+X84A5Uc5UHH
TH06UkMzklckudyrkfd6j3qxNGVRFiunySGYAYGf61WZmEriTBwcgH+f0qS2IuSIIEMj5+UDGMHt
U2GmJHpokKyzXqLG5I2EEFMY5OO1Wo7QW5lULErmJWyuD1AI/mB7VcfSjCjMBMJEGJIsqF6ckcnp
jNZV3FOxGJJA7gcSLtGAPbHHFXsBo3kMmnyp55R5DGrg+YGDA9Pc4NQ29y8kTpHG8m0hgFGOR39a
hRyqgyQpkMu54xg8DoM96WyuEIlwVKgABSx5bPP6cfjSuBNBfSwgKsnk7m+YZ52+vHrT/tC4nIjM
itkKiMSQOvzHHIqGO5MaSWKqAJJB5jhfmAHYdxzXQJpkFlaPcwzLLDI2ASMN+Az0zx1zTWoaGVam
ONld12h14fAyo6jA+tWra6b7PLZxxIzPIHDuRujGOcHsSMU+a7WWxiMnmStBHtBdBj7wGF9qq2Mg
EjMYzJIezcDn8P8AOKWtxnVaPbRQ3j3vngWtuoMiAfMhbIBxtI6quTjvV20Vr+Qv5MlvavPJJcSu
ikD5h8ox97AHT1+mK5xhHLdyRxH7Om0bl8wEbQMkZ5BzUiateWsNtaQyR+XEfMypxvzg4OBng9fx
rRS7ktdjvLS7t9PubSCGZ5JHIkLSyYyMdyo4IJC49a73Sbjfb+Zvi2DP8ZJbueSK8X0qe6+2x3Nw
Vj8xiGkbJ2+rYxx147V6Zp2q2drpnkI7BUbjawJI+v06mtIO5Ekd5C6tGpXvzUmax9JuRLAJCwye
cA5rUD5GauxBLuo3VHuo3UWGS7qTdUe6jdRYRJupM03NLRYBc0opKd0pDFFFJRQAtOFNpwoAWlFJ
S0AKKKY0iRjLsqj1Y4qtJrGmw/6y/tl+sq/40CuXKKyZPFOhx/e1KE/7pLfyqufGugj/AJfc/SNv
8KfK+wcyN6iudbx3oS/8vEh+kTUz/hP9C/56zf8Afo0+V9hcyOlormh4+0H/AJ7yj/tkaevjrQHH
/H4y/wC9E3+FHK+wcyOgj+4v0p2awovF+gsij+0YwcfxKw/pVyLX9Im+5qVqfrKB/OlZjujRoqKO
7t5v9XcRP/uuDUtIYUUUUAIPvNS00f6w/Qf1p1ABRRRQAUUUUAFFFFABQSACScAd6y9a8RafoMO+
7m/eEfJCnLv9B/U15nr3jHUNczGGNtaHpCh6j/aPf6dKai2JtI7DxD4/tNODwaaFvLkcF/8Almh+
v8X4fnXDXd/d6pMbi8maVz0z0HsB2rIPQ8VpkhUBJrVRSM27jGRc574qlDywJ6DNXJScZFUTuyAO
MZqhD3lbO0HHPWnfelTHoah5GM81IDlx9DTEQzDD4Hehac338kimjrSAcxPmIP8AZNDntRP8si46
7TxUfLcsevagYg68dac4/dOT/dNACge9K/MT/QigQi42r64peOlIvQY9KUgHBzyKAPFJJbyUeXM7
Hcw5LcH86k1Yxr9lhDZZVAKkfrX0NZ+CtA8SaBAmoWSNIAyLPEdrqNx7j+teQ+O/AF54VuGIulvL
aIgxO3EgQ8AMP8K4G7Ox1NaHMW0LMrLjAAzWtpdi1xb6rOLNZRHaHa+RiPod3J6gA9Kz7V9kMjYP
UK3rz71raPNLCs9tEVLXETqQRnPGKXUR2lrZ28fhaxmudSeOKaBZNgdQ2VbGRkndtwOBjFYunRx6
xq9jJf8AmS6cQ0eC5/fFRk+4Xnp/jVbQWXUrKOa8gNxBp0exI1IHJJJLA/hTZ7tbC8ik6RowlKjI
I3D5h+GP1q21e413JfE1q0/iG1sLDMgt08wKXJCKvTknoMMcCs6B7iK7unN15shyGndsl89Tz3Iq
XQpLCbTtQvry4IuZHUrvI+ZVYZwfXn8qz2vrPyJPLf51lZ97j+EkYyfXn8KiTErGkthbXMEl1KTB
vY+U6jk8+nQj/HiqCSzQyvDKuwltrLGcBscHHpVu61JLm0slt2j2QnbHHkk7hgs5/Ss6fVGuLZbK
ztTM4lLvMq5OTwAMUnZ7FG5Y6fAulyakhTi4UxorkMI1+8cdeRzWN9tltbq6WyleOGZyFYDGVzxm
rEE88kAgluHhtWI86PGACD09foKrTwqk0sawPuRiAGPKj0PvQ3oMquoDs8nzMy58w9PyrUs7XEKS
S5COhCM4IBJPGD7en1rNXfKVKxYJO0qx9f6V0Kxy3FsqzXai1jAXyouQdv3gSxyDyB6cmhK4wkvZ
JoZGVXCqhPPI5x09O/rTDazyaYty4LxxhVQsc7M+3p7e9RYlt7ee3lJSNovMTbjBBxtGfWrGoapG
lhFbW7gkqolUKDkjofr29xR6gRFEf7MUi/f5JIckq3t0+v51iSFGkLx/u2DnJX17flWzdXgtFgKM
E2AMFAPGerHnvgflVGzsDteXYzPG2QV6E9+T7UgLWnRSwy+bLKFmUYC+Vk9PqMVpvFdzGOYW4+d1
H3gQTgYOOPf/ABrNI3TP5mCSent2qdhOsLg+bHCDtK9Of8/lmkgFmf8AcpCFQDzDkqcsTnv7VIq+
XcWxQbyFBOCQSc1QZlc5be0inGHX7o61bhWRZk+ccng+h/pSuMvM0S3jxxABWG1hIg4YjBA9PWrE
Vktvpy6gzmRidmCR6kfXoKz3+W5LQhdyKWLbup55+vNWLGzOoSQRl/n2kDB5459e54qlroBqWF9O
0keE43Hy1ZsZyRj+Vdj4f0AahPumupCkbAyOMKsj4ywAGOBn/OK4W1udsojYNlH2Lt9fX9TXoGhz
yKsNq9ubVEbLs55XvyxGOa2p6kS8jvIWhs0S3QHCqM+p/GtO3cFB82a46a+NyGYKWYzFMHggbeCc
ehP61ZtNdha6WztXlmdSFdlUn68/WtzI67dRmoYmJUZXH41Lmiwh2aUGmZpQaAJM0oNMzUc93b2i
b7ieOFfV2ApDLINLmuZvfHGk2uRC0l0w/wCea4X8zXIaz8WGtiVSS1sx7nzH/L/61PkZPOj1bNUb
vXdKsci5v4I2H8O8E/kOa8A1T4oz3pKia8vPbdsT8v8A61c9L4m1i6J+zwxW4PfG4/rUtwW7C8ns
j6HuviFo0GRCJ7k/7KbR+Zrn774spASEt7aAes82T+QxXh0kesX3+vvZyD2DbR+QpY/DZY5fLH1P
NT7SC2Q+WT3Z6bffGaXkDUok9reHJ/Mg1zt38WbqYnFxqU4P+3sH86wYvDiDqtWRoUaj7lL20uiH
7NdWTWnjLU9aungt7LLKu4tPMW4zjtV4DxFJ0NrH9Iif5mjwrpyQatKQuMwEf+PCuyEKjtU+1m+o
/Zx7HHfYdfk+9qOz/chUfzFH9jaweurXH4BR/Suy8oelL5Q9KXPLuVyx7HGf2Bqbfe1W7/CTFJ/w
juof9BS8/wC/prtPLHpR5Ypc0u4Wj2OL/wCEe1Htql5/38pp0PVl+7qtz+OD/Su28selJ5Q9KOeX
cOVdjiTpuup93U3P+9Eh/pSeX4ii/wCXiCX/AH4cfyIrtzCPSmmBT2FP2k11Dlj2OK+269D1tLZ/
90sv+NWU8Z6zpsbSPbXkKIMs0FzkAD24rqTaof4RVHVtPjfTbtdo5hcfoar2s+4vZxfQo2PxnmXH
/EzuF9p4g3+NdRp/xiMmA01jcfUmNv5/0ryRfD6FR8tQS+HB/CuPpxT9t3RPs+zPoK0+JVlNKsk9
nKg2kExSBx9e1b1p4x0O8wFvkiY/wzAp/PivlgaXeWp3QTyxkf3WqzHrOvWfBmE6jtIuaaqU3voH
LNH1vFPFOu+GVJF/vIwI/Sn18r2Pj28spA0lvLAw/jt3IrtNH+MNwu1W1BJR/cu05/76H+NWlF7M
m7W6PdKK4TTPihZ3Kj7XasgP/LSBg6/l/wDrrU1Dx9o9pZie2lN3I33YkBBz/tZ6UOLQ1JM6SaaK
3iaaaRY40GWdzgAfWuB8Q/EYDfbaKMkcG6ccf8BH9T+VcnrXiHUdel3XcuIgcpCnCL+Hc+5rI4BI
96pR7icuxJPPNdTPNPI8srcs7nJNNi+ZV+lNPy5PNOQkAD2qyCT+E/pitDbkDPTFZozz3rUUfKKY
EbY21Tc8D6n+dXZBx+NUmHye+T/OgBrjpzzSnhgfXpQUwaQcSrnnrTEViT5hz+tTIuW/GmSr8+al
iB3Z6YpDHThRIuePlP8ASoFYdB0pLpiZFHYg5x+FICFP4UALnrTmP7psf3TUQPJJ4A7noKy9S8S6
dYxuolE8mCAsfIz7npQ2kBq7/lFRvKFYZPJ7DkmkEUsoUyNtBA+VP8aspAsYG1QKBGp4EuLweHIW
kfZc73UYAw2DkZFYnxVvIpvDV1d3EO29EsMcbo5KMAef5fzrY8Ezl9Et0L7zHI4GRg/55rlvGkvm
+G9YXacPKi4Pb94tebJ+8zslsedWeyazZ2JHQn860YLuS0hg8j93LFKZUmGdynGMfQjqPb2rm7O/
S2tZY3QuTwAOgOavRx3d1ZtczSmKEcKpzzz+lNqxnc3bTXl8P2UixSMrsQTGFBDkH5gfbhfyrl7n
VLvV7rJJSHOQgPGPeoDOzb1ZQ6L/AH+tXNPgjkxN5TKi8su77w7/AE4p37i3IrOCaS6LW0Us+7KF
UGVxg8E9BkZqzLpdzBO8TRFI/LbBZwSOARn8cCtyylENk1rCVhhL7hEMDd6c9TgE81HqM6SrtWR5
yNu5zkM2MgD8BgcVMpLoXZHNlJV3NJuiwcOP/wBVbFprNtFGotYQjRKVVCeC3Ziw+91/QVZSCT7I
IrnCAtndt+bPUjP+e1Q/2OL5o3stkTOiuCeOpA+btnkfSnvsFrEkmn3kWl/b5YSsDttWVziNm6kZ
9f8A9VZ9nMCVbzDvPzFcgdeePWuy0XxZHoEN7ofiHT0uNkWwRyKGGeo74I5yD3rmtevfteovI1mt
mzgSRxqu3d1O4fXPbihoEyLz1E8YMhXLAs+CCo/x9DXUyCECF7GExWdyXCvIqkdT93I5IA5PqPWu
PtgAwMr4Qkc54HPpW9dTvaSy20KfaUTcq/NkoepK/kaFoUQ3Fri3hnMjtET8pZjnqcHH4fpV/U7u
EWMcFvCJJ1UeZIAMZ64Hp1xWWyXTaezgwCN8YwWJAHT25z9aLSR48xEIVkUBtrdQe3ND0EWLixt7
Ozgw/mz3JDMzEYXjpj2NWI28qN4gw2bdxVV6nPPJ6dOtZbss8scRZ4/LPIOWGf8A9Va0ptYY2Ky7
mlUFXRuCSeVP6/mKmT6jI7COSS5VhGrMI93lsvoPwx61tWxjvLdYgrrvRkcM4UF15XgDnjPXP1rH
gnQ3UkpAK4BAkbBY8DjHt/KrF5Pa+eggWWOHqyttLfmPpx9TTjZIChu5duSTwfftSxbXlG5iy4zm
o43DgblGAWYuev8A9ep7N4gzPIqsAMAj1zwahFEjxAPtGAMZG2tKxYR7p1fkAIoIznjJOKzZ7h7i
VpCh5GAQMZHQU5PMQhFi+XoNjbieKq9mPc6Tw5a2ck7395cukcUhVWQ8gH+I+nUc/Wull8SWVtEs
IQzxuw2tI/zFV5I49Tx9K8+juLi2iKC3I3Md3zZzzjp0FWGe4SUS3KSCQkqwYYCnOSv+fWtFOysi
Gr7nWQ32o67q00MF1/rv3kjgFVUYA4HU9gPpXeeFLSG0gC27FhjG8MMsQeScdK890CxklaTzrkxP
L1EagEnjAJ7AZAwPeu08NXiwqER4GLnanlKckDvj061tDuyJI7Yz7HUEgDvk1LHMsn3TXM3eoi7v
rWOI723lXA4UgDOM9zx2966CztvK3uzbmc5zjA+g9BWhnYtCsvxHrTaHpv2pI1dmkEa7zgAnPX8q
1gK5b4l2RvfBGqqoy0Mazr7bGBP6ZobsBy114x1q5JH2ryVPaFQv69a891Xxxf3FzJFb2rPJG5Uz
XDliSDjgVj6bquqtKLaC6bBHRxuxj0zW9baXv+dxudjljjqe5pTq6WjoRGGt5GHLLreqf8fF5IEP
8EfyD9Kfb+HFzuYZPcnmush01R/DVyOyAHSudtvdmySWxzcGhRr/AAVoQ6Sq9EFbiWwHaplgA7VI
zJTTlH8NWEsVHatJYhT1jFFwM8WijtSSWwA6Vp7AKhmXikMpaNGE1Jz/ANMj/MV0OKxNLGNRb/rm
f5it3A9aEAlGKP5UUwDFGKKM0DDFGKM0UABFGBR25pc0ANIFQXq5tJx6xt/KrPFQ3XNvL/uH+VAH
NxWg2jilayU9q0IU+UVKYhQBhvYA9qqy6Yp/hFdGYR6VG0APagDkptGRv4Kz5fDgnbakeWNdsYUb
/wCtRDCMHAwM1pGk3qyHOxg6F4XXT5TK80jyAfcDEIP8a6GdNsOT2I/nU0QCyMPYUlyR5Lk+38xX
UkkrIxbuUhkk1E5+dvqKlJ5qF+SfwpiHE7gcU5R8qn/ZpoP3vpT14Vf92mAA4FamTtGPSskt2rWU
kqpHoKAGuDgnNVl+Yc/3j/Orb/dOapxdyf7xoAVkye/NNkG2RMVIfr3zVa4kETLI7hVGcknAHFAD
JAzycZFSRjaCT1NYeoeLNOsiQjGeT0Tp+f8AhXM6h4xv7oEREW8f+zwfz61LmkPlZ21/fWdlKjXM
6IAp4zknp2rndS8awJlbCDcw/wCWkh/pXB3WqozHfIZn6nvVF7ueX7oEa/rWbqFqB0Oo+ILy7ybq
5IU/wA4H5CsOTU1LYiQv7npVQQNIcnc5q5BYEjLnavoKzcmXZI9vTIjQ98CpCcgZpi/cHsBThwua
6uhznUeDtCg1Dw/DdDfHMGYMwODx7VwXxIRLHRLtGIaQyRxvjhgS4IJ9funmu48FeIY4NMVJIpGS
VzIk0I3KASOCOvY15/48vI7m21c7VkWWMEO3WNg6suPzI/GvPkrzZ1yeh5K0XlaiIWxtfDc9ORmt
bV7xItJaMH97I4XA6Y7/ANKzNaZluIbgYIAAyKbfLNdyqQo2kZQZ7Hmh6mY7S9PluyFAyFIyD/GT
2FbE17HBF5ESoXIwR3wD3NZNnLemT7PbMV6rlOvua1rLToxaySyH50PALZ7dfp2pPUpBb2V5OqP5
wjiZuZD0Hoo9z/UVLIXtpng8wzbP4jhcZIwP8mpLF0lEwk8wJnKc/cznoPwH5UyK03AllwJ3GCx6
84yM1NkVbsWINTigk26jbNLEQdhV8KWK4Vs+x5ot7tk0hYIbiJroyeTFCke6WXLFt3sPujJ9MVds
YpUmlSaCGaViIgWb92gA5x6nt/8ArqSztINA1+a2inDRyhGjuOhTOTjj6H8D+NaICR/h/eaxG99f
X/m3gUPKsW7cy4+7uIxuGAoA4GRXIana3WleXHPHMIZE8y3MgwSM9R2rvri/FqJ/tsk1vKSHhQuS
WY9WOScHA4+mOa5bxL9nkkKwXD3tnbthZXGD8wyfxH5U3ZksxYrpJUQtHtTOML61sqx8kDlADnIO
SR0zn6YrLSBJbeIrsUNz15JB/nV6FGVzCRsyuSw559f1rKVikKzk7FXGwbt/PB9CfSpYpw7or7li
QFz8nt60xCxjmSQAEnaT656GmSCS1tZslcPkL7UDLFnMWeWYgBiu1WH8Wf8ACrAghPk4Ai3YDsAP
lJBI47/dzUUIVLKFHOTg7jj+WKtaibeO8UwlWRBk7fu556Z7dqNx7EEN3NBK4BAV8hZFGAefTt9O
lOu52dn+0MAx7HA/QVT+14BjRRJnHyp35pxQJD+/AUgZD43bDk8H2paiHREGLahYkt3wFP4mp4gq
oVcBRjBP+elVFkMLFWYSkgsCOhOO3rU8UU0cJmkDGEjBcMOOg/LpQNMtoQWRVcKpIBZySBV2ENFN
ExkPl/M5GeBgf1/kaotco8iFnBAAUL3GPb/PWhJt7AOjHb8uP8/zoTsUaNvG0wM0gEcbOOB3yTn+
Rq5NIYrtIgVAXDk54HocmsxLookcmFTaTjByT6D680+Ar/r7gb3PJQn6YAqk1YR0M9+53Ss6rlMB
sfeIHX15OR+Fbel30ksEcMQZIvLy2GJlmPTAA+6vTqRwK4+zkWW5WWdyiJ8y7VzhgPl+vSuw0Gex
mvg1xcyCMD5XYH5EGOfqa0i9SWtDtbWCexezkZ4hdyII4bdY87Bn5sHoT6kcYH59nbQSCMGRstjn
iuS0XUrS+vZGiaSSK3PkwncCTkAsxP1wPwNdnZsZByAuP4e/41unoZNB5dV72zS+s7i0kGUuImiY
ezAj+taXl0eWKLisfJXhy0kj8RC2kGDGJEcEdwK7+O1C9qp6xpS6Z8UdTiVdqPI0yj/fj3fzJrcC
VhIpFdYgO1LMDHDI6ruKoWA9SB0qxtxTZ1zBJ/uH+VSM5FfFOpYB/suH/v8An/CnDxZqIHOlRf8A
f8//ABNKYBsBxR5AKqMdDXb7GBy+0kLH4tvmljRtKjAd1UkT5xk4z92uuxg1xpgCyRHH/LRf512h
61z1YKNrG1OTktRhFQTDirJqCfoaxNStpg/4mDf9cz/MVtVi6cf+Jgf+uZ/mK2uKEBBfTyW1jcTR
BWkjjLKG6E+9cmfFerqcG2tOP97/ABrq7/Bs5xxyhFcrc2yhzgDGBW1OCluROTQn/CXasCf9CtSA
Mn5mpP8AhNNS72Nt/wB9tTVgXMox1Wontl2nj+KtXSiRzstN4v1NNu7T7YbhkfvG/wAKRfGOpMcL
p9sT/wBdG/woa3V3iBA4UfzFRJAqTfd7Gn7KN7C53YtL4s1Fv+Yfb/hK3+FXtN8QXt3fxW09jFGk
mcukhJGBnpis2G3BZOOwrUtYRHqduQOzfyqJU4pXKjJtm7Uc4/cSf7pqXio5/wDUSf7prmNihCvy
ipttMQhU3McDHU1Un1HnZEv/AAI1UYuWxLaRaldIlLMfwFVDK0y7vug9hTo0JUF+SeuahQ4TFdUa
aiZOTY6JcRqcckU9elKgHlL64pAK0JHR43MfYU25wYH5yMD+dLF1YUy5AFu/bj+tAimSASPeo5M7
j68U4feHOe9NY/OfXAoAVDknPfmn7vkU+1RrxyfSn8FFGe1MBuecnmtSBx5KfQVlsURCzEKo6knG
Kz77xnpmnxBUc3Em37sfQfjSbSBI6WRxgj1rJudXsdOjY3NwkZBJ29W/KvP9X+IV9dKywHyIx2hG
W/OuRn1kXBYtvdieS3HNQ59i1Fno+o/EKNAUsIdx/wCekn+H/wCuuO1TxJd3z5ubtjjoqnpWAJGu
GxvA9lHNW4NKlk24jI3HALdT+FZObZSikRNfSPnywR/tMajEc9y2C7yH+6ua0k0v9+IiCz9weMVs
WdsbKRHKpG6nG1kypHTP4cVO4722OastP82+ktrib7KsalnLLyMdQB6+1defD2iJaPJaTmdBhRPK
eS2M8DoB/wDXrEnlS01y5uh5c6owZcjKue3SnS3kmou1xKApck7VHAoukhtO4xwqAxqvfseD70wl
gqhMZY+vFamoaQYNOgugCd4zkH16fyP61PpGiy3MAn3oiyEooYcHH+T+VKzuS3oelLwo9xTn+6KU
KFAHtTGOSF9K7DExvA15dW1miwzNhYnJUDoecDFdFr2kaELCSfUQxhkjUSIGwGIxzkdxkfpXP+G9
E1TT7O1ujC6xyJsk4yQvTJrZaSK6guEvImk3biqyJ8o9vyHSuKo9bnWloee3vw3OobrnQdYt7635
xHIcSR+zf48VlHwpq2nWs7Xlo0LLHncVyOD1DDg8Z6V6OdGskiWa1t5YrkylozC4DqAegJ9gTiru
lz63JdG1EtrfROuRHOhicnGSCRkZ9TisueMlbYfKeSWtoLGIAELPMuWP91T/AI1NAJs7IsO8jDEZ
HDYPt39K9M1rw7ot5OPtFtJpd243bsgRt24YZXPtwfauaufBep2UzXNk63qJ8yhPlkHp8vf8DzTs
wtY5/e0MsiXAeKZvmMbZB/X86cszOsIYhfKYdBnAyTn9aS62tPLLfJIC0bDDL8wcDj6cgD2qlF9o
EhzIoDfjgY96QkdZpMtvDeyHyVmuUlXyxI54OQWJx16H061na9dJd6qbm3EotpFysrg8svLEeg5O
PXGayLSaeSS4U3C/PkszDGfyqS+1GaXyoHtlg8tSFC/Mp4POOx5qr6WA07947ZWV3aaaZAzFmy3c
5J/EHnuKoz27y6K8jxRqYD3ZiZSzfextweh5zUdpdx3Cc4a4jPzMzfM6gBQq/T0q+z2/9i3Q/esz
AqFLYAPGGwOvTvnrST1A51ZENnIoxsRtwVscdjj86lhmkBRgwIBOCOo/+tWSu/dIMkFgRj3xVqzm
OxHYYVcc+vrTa0EmbAyQO6ycg579PwqpekyQiOQ+Ud3U9DnNTxyhVBTBLYJT1+n4VI5S4TAw6D5R
u7Z7H3rJaFDpHMMKRS4AjhHAHLMf/rVDlMMQ2AoAz680y/eW7uNsJ9PvLjt/SlVQyKeMA8nPU9DV
gOBOV8pvKZQegwCfepWWYxpGWKtnhj/EOtMt2SS4G/aybtxyalnlV5XSLCx7dyE84PvSAelu5iDq
6jcpIiYcHA6j+7/WntdK1sttHbt5hOXJ6KPT/wCvSRysxQMwjkVSpHXcDnn6YpUiLSKxYllyQrcj
3zjoPpSsAp82GR43i2SKvzE9TnvVuxR9vmMjNxjIbAU/5zVSR/38gyXIOFRjyAO2f89qlWSRYXwB
gnBIJBPtil1Giwqgsu4s2D8oPQH3qWc/MhZi+7qM88VWF0zxLEnzEdOMbT9aUsXwdu0gYyCT9eaZ
RcEyxQKTMFbdkKMfnWhbXnl20mJOHOAQeRx0rLXckUeFUEnjLdakklMh3ODnJ55wT9aaEdfoGqRW
k8WZzCi8cLyxznJ55OfavUNC8R4k0uKRgEvS6BsdHChgMnrnJH5V4naC0Vkka+thgAlSGJH6cGt7
UNftpoLFLWeOGS0cSI25m+YYx29q6YLuZTa6H0ASxHDkfgKNzf3v0rgoPi3oJhQz+eJCo3BI8gHH
OPbNS/8AC2vDe4KWuee/l8fzqiLnP/EGwMHjqwvccXVoV3Y7puz+hWqfP979Kl8Y+M9F1660ya0n
K/ZGl3+YuCQygDH5Vi/2/p+P+PlaiS1Hc1fmz979KbMT5MnzfwHt7Vmf8JBp4BzcA/QGo5fENiUZ
BLncvUCpUWFyluQxj517d6UFe7L+dU0a3eMH7VEPYtg1at7RrlN8UiSKDgspyM46V3ppnLysa7KG
T5lJ3rjn3rc1LUBbjyTu3SAkEDoMjPNYh02dZFJA4cHv0zmrGsTK0sT7gF+6M8ZJIwKynHmkjSDt
Fmj/AGlAeCjCppFTbkAVgAh/lPQ8Vu8LEAOgFZVYKOxpCTe4ywA+2ngfcP8AMVrKq+g/Ksewb/TT
/uH+YrWV6wNRt2o+zScD7tYN0oznA+6P61uXbA2soyPu1hXeDjp93/Gt6WxlMjQfO3T/ACaZKoAb
6mnxAbmH+etRzAfMPRjW7MkTlAGUZz8i/wBKgZcTkAdmqcKCR7AfzFRyDF1jHUNz+Ao6gtiSJfmT
jsKvRqDeQ8dv6VSgUb04/hFXIv8Aj+hx7/yrOexcdy/jHA9KZcErG/U8Edal7n6VHNgoR71zR1Zs
ygQ2cMTjHAJqLgYPfJzViTrx6VXIya7FoYMuxnMS/SqqH5T2q3GP3S/Sqg4WmInT7gPtRn+dJGf3
Y+lNzkmgZJEMM2e4ptzzbvn0ojYIxHtVe+u4orWRndUUfxMcCgCAcEelNZh5jfQVg3/i7T7RSsT/
AGhx/dOF/OuZvvFOo327yD5UZ67PlX8WNQ5pDUWzt7vVLWy/186qQPu5yfyrnNS8dpAoitIfmxgM
5yfwArkZJTIf3tw8pPVYuB/30f6VS1C9nsoQ1pEkBLYLbdzH8TWbq3dkaKk7XNi81LVNR+eeVkj6
5mbao+grLlurCL/WzNdv/dX5V/xNc/cXFxcqjzSu5brk1pQWigAIB0zk1L8wJ5dQnuEMUECQxHsB
iqklqywtIWyT2AwK0cLGoVWDZ45/WmHMkci9lH9am41uFjCqHKgB/wC8OSTxxWvHIHYyAEk/eOef
8+9ZcWUlK4AGcg4rSX7m4sNzHk+tK4i3ZsUjmmbO9vlVx1+lbEVqXtt05YB1BZsj5cHgjjisISgO
qYbnBYH1rZiv7VB++lIUqRtzkt9fSmmJnMXiKLu4wxkUbfmPVqdC4jUbQAcnkik1DYskxQELhMeu
OaZbuPLGUB9KnoXLcuG6m8oq07mNvvL2z6ii21y8t4zAkvyk8A/w5649KqyMXAUcVMlg6ISQpYEE
nP8AKhXIZ7AMED6UzGHpw4x9KX8K7jE2/A909z4etJmZ5Y2jJbIzk7jVi+gsRM0sEQSdFBxjGQe+
O9YPhfUZ9E0S3tbaaGWIKxQSoQTyTgke5q5f3jajcC+ji8oPbMhAbcqurdeMZ615U9Wz0HpYqXVs
bmcpFJLBskD5iwCD6jse+RUcF1LaanavgS7pdrSRdYyBghh6HH51WnkuEVftE/k7hvDJ8xI7DB/G
i3eVog+xLks581k+UlSMh8HuDnpWC0Wg+p2N4I/szrJEJBhvlYZBGO9cY+nJGoksJ7iwlyWEaHMW
O4AOeKujU7za9sWBDY2Mr/MxIGR+tPuIIptu98iMskao5+bJPJ/75o53ugepi6pBcu5XW9Kt9QiC
5S7tztcj0PT+f4VkW3hjRdYlI0W8e0uwD/oV+pHPqO5/WuutJ5zM8MhBXcwySMMME/4UjQQ3lwrT
GFxIfu+UDyMAjJ6dO3rWiraWkiXA8/ufCes6XLIX09pY1O7zImBH8uPxrHku/Pu47naYXQjap47k
H68Yr1iCHVIGf+zdQMsiscwXWXCqPf7wH40mpeD7fUc3GoaKEldd32ixkBz7lTj+R/Gt001oTY8h
mtYJGEwXEytkyZ+916j8qtC9/wBAktSoDKN27v2OP0rp7zwHN/rNHu1ugOTA52SHnp6Z+uK5nUNO
u9PkkS7he3ZeMSjHH9frSd1uKxz80Llcqu5hn2NSQW6m3l/hyNwDcYY9asvGQGC9eh/xFJHAPKkB
benByOvpVXJsNl8yG8hbpu5HHXirEU+y4mtmXYNgIHbiodR8wXEEhUMgHzY65BqJ5CztJsJydvuf
Sla4GoF2Fipbc2SPX/8AVUZWIkNtJ2nlQeuasR4Qu0jYVozjdz82OlQSvmdmjHlkrkY6VKLIrq5W
2ulePaEZQenTjFQyTCNWlVgxkbJXHp2plzCZJFDfIMY/H0pwthuiDDdub5gD/Kr0Idy9IrTYIAj+
RQDt+bpmliknj5UgueAamnuFFxuXBAJXKjtjH9KiikBb5Ttzn8v8/wAqgokWKaNmVSrOwJJI9qbE
snmBZZd2M9uKcjMtxncOmck9qepCBQWXdv6Y6cevekwLBkIAXYpB45GCPx9aXzAFyDjnpmoWdpDs
B3Ae2Digs+35gSq/Tj60kUmWgxPzEKdp6sOBSx28W0lgTkHK5NJFtmxtAY8cZ61Ix52ocSdOO1MZ
2ugWsEmlxOEB5Yc/WtMWcQ/gH5VR8MAjSIgeoZv51r4qjNkH2SLH3B+VH2OL+4PyqzjiigRV+yxf
3F/KnCzh/uL+VT8GnDAoAr/Y4R/yzX8qX7HD/cX8qnyKXrQBSuIooImfy14HpTdMuIxFJkhT5nTH
sKkvuYG+lZ9o5AkAHVv6CunD7syqbGnJcRjJ3DArnfEl9ELaMI42tMoZ+0a55Y+wq/NK4BHBFYeo
WxuEaM42sCCK65bGKKh1PTtpzrkHT+FanHiOxUADXI9vGcQj/wCJrlLjQjExCgYzVJtOIyNveud3
e6NV5M7iHxNp0DmUa5h8Y4gBGP8AvirX/CY6Xtz/AG64bB3Yth+H8FedNZEHBX9aieycnO2pt5D+
Z6IPGemujJNrsvORxbDp/wB+6ifxHoLqx/tq4yOB+47f98V521qyHlelSxQmZtoXHGaadtkFr9Tv
R4k0IEn+2bgcf88D/wDEUf8ACQ6CVZjrFy3X/ljjn/viuGFg/wDdphtGIwFp8zCyO8HiXRSP+Q3c
KfeD/wCwpP8AhIdGaTedel44/wBSB/7JXAtaODgg037I5z8tHMw5UeiQ+I9JDZ/t/B7AwD/4iph4
g0/zPNHiOLjI+aBccj/dFebizkDcin/Z2DY2n86TbYWsenL4qtQPl8Q2DDphoQP6irNnryX06RJq
dhPuP3Ikw547fMf5V5XBplzdTCK3tpJpD/CgzXXeGvDi6dqkEt3dILtCSttD85XKn77DhfpU+6mr
j1tudvJ1H0qInBIHSpn5P4VC3DH61uZlyE/ItU2OePeny31vZwh7iZIk9WbFcrfeNbO33C2QzHP3
m+VaG0gtc61DiMfSs2816w0/f59wu4H7i8mvPb/xZqGoKwF7HBCv3sEr+QHJrDluUI3qkt2395vl
X8v8azdTsVydztNQ8dyySMmnQHOMbmGT/gK5e91O7vXzd3ZJ/uqd5H9BVEyzFM3AKrnAjT7oqW3V
Jd4wUIwEwOCfQ1g5yexvGEUrtjOpykfP96T5j/gKWOGW5YZLyE9CelaEduqxMP4wcN3NPtYmdkjQ
5+QDP92o1bszRtKKcUZ8sUlqw8wALnnHWquqqj2ysgON/f6V09/pLrZ7prgOw6KOcCudvY2W0AcY
Ic/yptWJjJyepgtFiCA+uf6VqxqwUKDx3qnIuLe1/H+laLKyqVGRtbBzVsxZWyA2OhPU1PD8yTAD
gJ19eRTTEoAOPzqa3UCKfA/g/qKQ47ke/ZduACQMnH41OC0mcAoBzj61Gny3MpyOp/nU+8K2M7s9
cc0mBIqEHPmMwwOnf2ph5OAuFByfeljYEgc5J6e1TNGJHCrlAffIpWASWPfKyBCxZIwBjrxUo06S
PAMUh5Iwi5JI68Urxj7S6s7qAicq+09PWrotZLZYp7B5SWJRQZN24jk4z61SWg5vUpNay/aEItJU
XO4jacj3xW3cPaTxxxRRzvdDBSLy9p/H2qWxtNWupGLW04Mnys8hACAegB9+9RatqNno4+y20Zkv
AdskzOen9a0SSMmd8vJFKeoqqL2IAbW3nH8IJ/lSmaV/uQsPdiBXSZkELQ/2Xa+Ux2+WwGDjGQMf
59q6W01CJYtPZwoTzHSaRsZZucE46ZGDWDYeHwllaWljqYkgQEBXxkA5IyfzqbS1t9Ml1JJJv34k
VIYyc5yTyP8AgK/lXmvaR3btBcbLXWoZrREuVlXy0DyEoAQCVwM+/Si6CabZm3k2xXjHcJB0Zepw
P0z7VWt47carc3EhMiKcx8E7RuK7h7dvarN1MsskHnoS2xslcbmU4yM+3+Ncm2paRYgsCsKXitF5
aqFBCYbdnG7NDQSCx2yMkOyUBZfViSeg6gnINPtrqO/to3h/dRncAH4wQRkZ6YyO/rW9DoVpf2iG
7hbg/IucYxzn86uy6B6nKvDDagrK0azs4ATPGSBnB4Jx/KrkcsNxBEmzYY8qzIevUE468/0ofTUt
rxZZJCxP7lkYAlCDkYz16/rTIbG4JQqEllBkZ9y7QwXHcdDz2pJAyzeqrQlRMI7ooPLbk7kyOPXn
iphraoYrNwdq71DLk7CexrGeT7VbxlorhDayeW+QMbww+UHPTB/lVa+1ULKyEOrJIQ6PhSwA6Z6H
qOlObstBdS5dpaakr3DQu6x7YxKmVkz1Yggg9Tjmo72xv4WS2luUv4GVlEd9DvII4wXHb360aTzb
ROI0gkb94oAIY5zWw7GW6jkcuqI2AW55z04/DrUxnK247K553f8Ahy0vYmkFnc6VcJkOjKZYDg8k
EfMBx6d65m80S+sOUVbiHBBkgO5VP+13H417oiwyxSIzqoR1Lj/ZIIz+Yp17o9ldaQ889vC07YUz
KPnUDGMEc9K6FPuQ4o+fbpipTc21+QMjIbHWrdtApL/dBCjDA9+M8V2useBhqRLb45xGheMOCki4
5Kh1GD0/iBrn20R1eK2WSS0mYcLcpgNjriRcj8wKpNPYmzRk78lot28DgN6GkC7ZCAwZwMYHYetb
T+DLgNubUbCBDgDMz9ff5frV0/DnU5HjVNR07cygp+/Y7h/3zRysDk1RygaU7yjnHqP8/wBKs6a8
YvF3qGMHz+oIwf8A61dJJ4E1cQxEXenTYJJKXI+YEY6kCubEBs724ST9y0UZRkfjn0/lQAwOobae
TRtVFGMlgcAiq/npI21EckHGccUscr78SJsHIBzxnmiwrlyJhH8wGcD8gaXeuMhcHuT3NV1lU4jD
7u7HqMY6VYDFVyFJXsAOn41LKJkkC5kVsP0wBwfWrLFYgAeQy9c5FUow3C4Lbu3fNTSEuFyRk4PH
ahgTxBSQfu46nOKkyGYY4OcAe1QI2xgVAzUoHJdsn8efrSKuegeGs/2THuGDvbI/GtasbwqSdGhJ
67m/ma2RVmb3F602bIhkwcHYcH04p4psv+rf/dNAjz9Dq2B/xNrvPf8AeU5Tq23I1W764/1lXo1G
Cc9DinJtMYPbNd3LDsc15GbI+rKpP9q3YI/6aV6Cmdi/QVxN1IoJUdScD867ZPuL9BWFVJWsawv1
K98f9Hb6VlW2358nHzevsK1L7/j3f6Vl2uSkmB/F1/AVWH3FU2CcLsOCfzqlMoIwD+taW7YoBGSP
SoZT8w+Tjk9a7TA5x9LF3cOTJIAoGAshA7+hpreHo8HJkP8A20b/ABrZWUefLhQPlHX8alkkwp+X
NYStc0V7HIR6D5rviWQbWIHzUT6E0KBjPJg/7VdJZR7i59XzSX8WYVHvTshXOeXw6zxhvPkwRnGa
bbaGFuzG0j8KejYrqoIv9HX/AHarQxf8TFj/ALJosFygPD8e378n/fZrLfT1guJoxIcLtwGb2rt/
KwtYUsQN/cZQt9309KSWo29DE+yRtgnr9akttHS5n2eY6jGSFatrbGv/ACyOPwqXTlX7YpSHc2Dh
WOATx1Iq2klclNlD/hFfNGYmndh7jj9KbB4ZtUlfzbqe8kBGLe2I2/8AApMYH4c11hsJbkYu5d8f
/PGMbI/yHX8c1bS3jiUKiBVHQAYrilVb+E6FG25kW+mzmIw5WytmOTb2vG7/AHn6mtK3s4LNAsUa
xqPQYq0FpHUFSCOMVnHWSuN7GLrXiOz0SNXnEjBhhRGucn3NcRqXxDlnYi0AgU+i5b8zXT+LbZZo
I0YZ4NeYX9gFu0UDAwa7JtmUUmWJNSvdTdm3lj3diWNVLRDdEmZmbHauj0exhFnJvjBxjrWdpsMS
SkSJlee3vXPLQ0i9BZrOFbGZQqhmTK+tVLJcIyMeRwBW7LBbmKYoBnYaxEjASckncH4OelQPoOlT
FmzYz85/pTbRi6hVUAL8xOeT/wDqqZ1/4lgz6j+QqlCT5qoG+Xrn0pxKlsjciRi5JUAYIB9fel08
MTtiZhIWyAMYOPWrEDBoEXC7tvJxz09fSotPnNqC6Dc2elJfGxy/ho6aNf8ARrhrlFikdSgcoCDx
9eK47X4DbxiMkNg8MO4x1raj1vzFdWEKfLgAKcH2HNY2tv5kKE7D82Pk6dKqfQVLc5yYYt7T6f4V
ePOCWOOuc1VuB/o9r/u/4VLdqWnjEXyqUyBnIpksWaXOAo6VPaZMU+T/AMs+PzFVnwAQxxgD8al0
87vtB/6Z8D/gQo6CW4sn+vkB9T0puxRgg08ANcyFgTyeBU4YeWRgcDgH2P8A9egBlq3luHwCDwRW
jG/nbREoG7Jzngdaq2UkYt23lQ+4gg5zipLSPzlba7dCNi9Cfr+tOwi/b2TXl/JAsqIdinzGPAx3
/wA+tbdo0FosbfY/NJO9UQqdvOMDmsCSY2t1I24L8qqT+dQXfiC5WLyoyuAW5UEE59eaaaSCe5te
IPEJjjCpZxIcYId8t0/2TjPNcSrzXd0u1WZmYcAk45qSXzplMkrDJ/vNk0+xLxzCMSKqSMobjOeR
Re+5J7YkSrjin4FPK8kU0DFdRmR6DAEscTk7mBDe/pWxaxaXeoZjIPtkcuzAAAY4H5cMKwtFS5v7
AyWtxHc+Wu8l0wOOOT69qdJpOp2GoLeNzayyB2jXna20Ln9P1rzqlru52roZmkyvbeIdT0++3xMC
zQlmJDDkj9KsaW11PeKZHQAKSrAj5DjkH8R+op95qUMNzLeRjdOw2EuoyF2tg9c+/wCFUtB1JUdZ
57eIFCzyIrHMrHB545Jzn9O1cbjzMtSSOm0q3CaRhyG/0x0yOvPOf/rVqLqU9mRCsazLHwmWwVA/
nWFpV+s9rHcEsGE5G48q2AcA4646fh1rQmvEK7ogSSeRjOz/ABzkniqs9x3uSRypqE0nm7o9il96
fwkYxj16/pTbnTIkkijSZ4dh2nJxndxkH8f5VCI3lkCJsIdhtyuNxzxyOh9alvbe4to0bh0R8E7i
WGDnj8sYqrqwrGRqemXFjHJMlw863ErLJGwyXZeCQR0+VQc965TTb+8kuladyY0kPkoOQpBAGB36
fXgGu1luXtnkSU+bCimQcHduwQR2B6nivM7K8kGon7FI8TeaSdxJJPsD696cttCHe56BcXKzyoyx
LACQUcncWUdR6qRV2CUtOUSQLiMHyvu85HOe5HT8qr2VzBHcwiVMTy5ZwDkL2ypxzkfzqzkzzOEj
aOMOQrA9P/rcVFupotS5uacOZQGG4gEpggj8cnmpXLohtwQyKm4hvTGB+tSxY8jEkaOqYDJjBzzn
8cZP41HcB3VMYVTuAVR823hQT+NaW1uLyGRyyIpQt5YCn5SOU6DB556j8jXJ+My0txZKZAeGwBxg
9j9D6V11ys7wTM2MoMM54A5GGH+etcH40WU6lbSNMEXJ3ybjlicHkfUVcF71zOT0K58xY8yDezEb
WQ5IHc47U1J72HBh8zapyMgdP8algs2u4d0l0o2HA2gZIwD1NWLaGyMaLPPLE5/iOME1t7xGhetJ
Jp7SI+YWjJAwgG5BmuU8Y2obxNfSvbv8hWNRIvDYUDI9RXRWgjiuDCBuG75JMdBng8dK3da3RrJc
QzTLKJlDmMlsgsB8oPGeTiny3C9jyNbZzglHHzYGVIqOcASfMQAc7QR15r0V5Z2QxTR3wDfKhdRl
mOSen1H50aXauJjHc3l0F2kiK5ti4wp4IIweh9enWlysL3ODjiXy2LZ5GRSB1c/M3PHBFeqaN+6i
kMtn5gbkSSAEYGRkDIIB549hTLq1tLnVRALdQrWrsVkjBG7a2GGPTA6elRKLjHmZSabseexRRSKz
IxDKhPy565HXPtnpUJDrFkDt17GrUbFCzR8BgRnHP40jiNQEABJ5xnGD7VN9CrFcl1C4RunJPFNl
uduGfADdT6mrbeX5qnI7E9/zqreRYc4UBCAAKSBo9B8ISGTQoW4Hzv0Oe9bgbmue8FII9AhTGPnc
4H+9XQgDtVkMdnnrTZSfLYexpwxUVzKkcZLsqgjvQhHIG4t+zlST/d70xLmNIlUueD94Lj61mvDL
AzszRk5yBu6jPSqr3WeG+6pBO33710ObJUEakskUzGTzDkHgbfeu8jlDIuOmK81jilnTeGRFz8oJ
wT7CvQrB0lto3yDlQKzk7oq1h18f9Hb6VmWpOxwGwN39BWlf/wCof6Vl2xjw4b+96e1a4fcyqbD3
yFJL1SvLoQjl+uenWrdwY2jOMYPTArmdSuN0hTvyAOh/zkVvUnykQjcvidTcN8wA2/yqzE4dWPOD
muZglka5C7toLcBfbvXQwZjhHPr3681gpczNXGxascKD/vUXah0UegzVeOdoSpUdW5zTpZhKkZxg
kcit09bGNtC3FtEA5HT1qCED7aWzng1Kh2wj/dqOJlS8BYZyT0ouKxpMAAen51imIve3LKwxlRjG
e1askmZGXacZ4NYsmPtU4Gc7h60Reo3sWTbjuAfwqxYQBLtCMYPtis0lgehI981d0lh9pXnJzjnP
rVz+Fkrc6PHSgjpS9hSCvLOsKa/3SfanetNk+4aqPxIT2Oe8RrkRAdwa8/1ODF5GcdVNeh68NzRD
2P8ASuL1ZcXkPH8JxXbLYxjuWNMTFo4I7isrTkP2phx0P481rwyJBaOzuFHHWsm1IS+9MqefxrCp
uXD4WX5bcFJGIxhSP0rnmi2faXLHG7gV00koaMqByQawpTzMNpxmskX0IJSDpLt6OP5Csy3nK5wp
KkYbI6+1bDR/8Sx12Y/edB34FZ0FkQcliRjIpplSWxp6NIzu5ZicJ3p9oqyyEO+1BnknvRpcTRNL
uP8AB0HSolcRK2QsnO7Y/Skn7zKkv3aNldNlJaW2IdVxkLyD64rM1yRniiZ12tk5Hr70mnXxsJA8
LBi3BXnj369aNbmW6CSKWO4kndjr+FOVrBSXvGDdcW9t/u/0FMkuiwBH31XBJ7nnp+GKlvB/o9t/
uf0FQ/ZWDiQ/MOmBVmbKr3O3C5yx6mtTSpA8dwO+wc/8CFZosJ5ZyIreWQL/AHUJ/lWxpen3Nuly
88EkS+WAN64ydwpvYUdyA3L21zI4Qkb+1Kt6ryjYWXOTnqcY6dq6ZtBtY7ZLjzJWeU85KgDP4f5x
T5PDOllC8srhwD91xjNSpJ7A1Y5ZZytu2H+beep5P0psdxIgBR9mT261vRaDbKkk8UE0yoSBtcAH
05Pv7VFBYW6l2ktYwFz8rSlunXpTEM1ANKoy3LrH8x+h5rOjsZZSNsby89EQ8/jW+6hrlwFG1VTA
zx3rX06FbloQZ1QsuWQbic9gcdM0uhUtzlDoGoTY2Wuz3kcCpoNCu45Y0muoYo/MUlVOcnNd9Loc
Tbh5EjquckFhnvnkmm2umWMTl4bVd0QJJxkrzgc/Wp5tQ5UdMx+Y1HTieppoPTFd5zmT4HmZoJbT
LAHLf7JAxx+v6V2E0Yl0C8lb5XiikZcDrgHnPsRXLeFbWW2jjZVDssr7lRgOqYXP4mugt71F0e8h
llXevnAxMw3fxDH8vzrgm02zq6Hk13qMqTIFke4ZFAyOcnHIyOSOv54ra0K3DrBPvkI24Ftszl9w
IXP0xjPpXHqBFqt2WuihG8+Wg25AwcZ7ZH8q7exjaJ7W9gikKKNwLSgLjaOD6cD9T7VxyVgia907
3tsr2zhoVcYWFdhViOhA/PPvWrZWxuraSNss6wFiWOCG7Y981n22orB9ot0EZbGQqgKWJwQcHkd6
v2N5HdM9wkYQRQtI0bAjrg8e/H609omq3NjTxaxQwmRcbJ34HbDsc/rS3kSy2HXDBt3y9Dk8fpVK
31aG4huXELGbYV8stjvycf4etYN1rkZ8yL95by7v3QIwdvr9f8PelPRaj5rFzWvNWxbh8kYTHOGx
zn2rjfDbRxNf3KEeYcB4m+bexyDg4468Y9TXTX+pbrOFJGSUyKdpAOd3Xn06GuT0E+RfRlmjErPg
TcP5QH+zjrx+tTGVtBSavdHZ3l1a2V+ts0DbZEPlSIpJOWxn16547VYsfLmt1+SSXyCSCc7mAXv3
7kVDbahJc6mdQEqyyxRBoi2PnTpgY4zuGe/U1Ys5zDECuZcgqr8KOevB78H8606gtjbItltC5doy
QZSGzuY4GPpkZqlJNLJb+TaxMhJbDEkkrkHPT61Jd3ZuLDy5ZY0uFiKvs/hyuR/UVnx3L2twCJRP
GnD+qdM5z+NUlYL3NAM10xlBCsAwLKMkgDOPcZri/FUMQ8tbllkHmHBLYJIB/wDr11cU8Zt48Mok
lDbWzxjeSR+RFcv8QrdV8peVDtuyBkA9hirgRMwrJmEbJGQBjsTUut6g8Edr5T4c/edQMcgHH0pm
nWBJwyGfYFZfLOB9DyKNZCwynyrPbGFBeNsE/Uc1qtCNzHtNYvJb+KV7jf8AOMhuhGa7rWI7GLVJ
Lq5spXiEcYkLxOFDge3fGK5DS47OaWOYW0K4lTIY5J5rvdUvb2KR9Pu9Qt0iGUkJjGVwNwOc/QVS
WobIyvP0m1uZJG065+yyAbcpIVV8+/Ocf1qS/vNJkjt47JWhl8wKzCJo/lweMnt0/Kpbq9LCBW1Z
NkzHcyFV24AIx1HJqrrVype0lg1Pe6bgCrAkHGM5Ax61duhJaXT9ea3R7C8tEt2+ZVdsuOuTnHSk
05NSTVj/AGk6uzW77NgwAuxscYp+kyxRWcYubuVWHJHAAOeDyKq6ZJcXOtyO0ocLHKsbqNuVCNjI
rGsvcNKfxGDMEjjEjLDjB6H5u2KybhELDBDHccZGB/nmrhKmPDswcfw4NVJZGCyEgH+8XAOPTms0
W1Yiik4GMnJyoHf3NNupnO1do9yOMGhGYFAoUf7RHWrKrG0f76BiH5yj7aaWodDt/BTl9EQ46Owz
+NdEDiuZ8GzINNaKONkRZG27jnOa6QGqZmx2c8VVv0R7dlmUOAMjcODVkVHcFfKJbkfTNIRwt+9s
C2xVzjtjH5VhBQZCvDM5yeoxg9P5V0mptbzB0d/Nwfk52lfqOK5yVkh+ylmK4yH9CMimUdBYWwmA
VVEmDwz9CPauy06FYLaNRg8dR0/CuO0u4jILk+YDgcsOPX69a7KyKmFNpBAGBxxQDFvz+4b6Vjwn
h+n3u/0rXvj+4b6VjwrE6yh8k7vX2FdFDfQwqGdqd59n+XBBIz1/Kufurn7U/YMW59jVjW5vNuEI
lkITorJ/XvWOxKyAhjuXoAc4rOo25G8ElEs2bFLkhRuPTIBzXS2aSFB8ru3I4Q8Vyls8qu5jkJ6V
Yk8R6vaLshnEYHG0Ipx+lKDVyZrQ6tLe4+UmGUYI6xml+xXJZT5EhCjHCHmuKfxf4iA/4/v/ACGv
+FQnxn4lBP8Apxx/uL/hXTzK9zns7WO+SzvgoUwynjH3TSR2V2syg28xJJPEZx+dcDJ418TAZ/tF
x/wBf8KsW2t+M7sKw1cwIeQW2k/lii6Hqeg/ZbwA/wCjTZz/AHapJp98ss0j2kwDNkEr2rn7XV9W
gcPe+Irm4I6ooVV/QZ/WrE2uvdH97PJJ/vHihNIT1NYllbayHI9Oauae2LhAydSMHPSuaGrMF+U7
RjNWNJ1JZNYtYml3M0gwN3tRKd0wVrnebsAGkDDvxWdrpkbS5xDK8UmBh0OCOax/A3nPpVwZ5ZJm
+1N80jbjwB61wnQaep+JNK0qQxXl2scqjPlgEn9K0DMHtRMuSGUMPcGuF8cWSzXfmEc5UZ/Cu4gU
CyhX0jUfoKqG6B7GJrEjlosRkjB6muR1dmN7B8mDtPGetdlq3Eq/SuT1hf8ATrb/AHTXdLYwjuMk
G+zYMhxjtg1StwBfx7yAnc+nrWlNj7ESegIz+dUoUhe6IYvu7bQOeawqblQ+Flu52NMxUbQp+Vfa
sJ3H74js1bhEb+YY952/3vSstS2JykUWc90B/nWRotiDfnTWYjnf/SqcTg8YK59O9acm4WZ4UMH7
KB29Kro8oIYldx4+4ox+lJdTRvYsWO7dIuCPkBqlcWcqwtMUba54YjgVoW24SuWA/wBWOlPv2zpo
TmM7A/zZAfGOB2NSnqy38C+ZjwRqjfOFLk884qa7GIEGMYY8fhUCmMgEMMnngdKkmJ+zr3+Y/wAq
bFTWpnXn+ptv9z+grqPD5k1AGNmSNYlyPLQc/UmuYvB+6tv9z/Ct7w0XW5IHHI+909s/jVszO3i0
VXAja8ujjkqm1QPbgVjeILC0stOlETO83mhSzMWyM+9dPHFutEd3VnZRhc4AGaxfFsezTMEjcJQC
N2fpWabbKRm3hMekJxkjnGDzxVGLU7xzhNKlYf7P/wCqrl8H/slXXA2kcAD0qOxu55ot+5Iuvykk
nr3xTpbsmpsisTLLMsU6JCJnwwK4K9+9TXdrbQKXW4hBXlQUX5vy61QuXmuLoo6xyHzB8x7+3XpV
6S1SCaJhZ25BwmMHqeOa2MijcsyTygMAQFGegPWtjTVfZGVkZ9qEtgY4H41jXIK3VyPLVugwegra
01oY4MPaAcl1+UkkY4A9qnoXL4jft5LqFSqRyYORgyk+h6f0p8N7IFLSRiETHZk9jnOeO3FGmX1o
NPWB3YOxyRsIPOen44q46abPaQQw2kiOzr5jCPB6Hv8AWpAvUuBjNIOR+NGcYrvOcoaFJi1buDIM
+vQVa1uaNItxt4UZIy3mlPmbAHU+nUVU8NNBeQSJDKGKvu4HbFX9Xs47+zZC4Y7G2fL2HUZPrzXn
VbHWtjyu/u7C51mVI3jKuQolUHLNnpgnj0/CtzTNdt5rSa3bZlMkY43HlRgjgevP1rCS3yLiU2MZ
aT5U2jaFOT8wPYjAI9avmG2n0eaaZN1zsHmGOTBOFwOD3Pc+ua5WtLohX1Zs2EiNdw3EH+tnDI8o
fpyx6+wrTtdTwyaYkIEs8rvuX5yW65x16dB9K5jSZxHaeRZ/vv3isGcFSCcgZ46EHnniti0s7vT4
Z75EijktsGOLJBfDZbaPTaCO2alu25cNWbGp6o2lrJO0wU43lHQ7gRgDn0yBXGvrdxfXs13Kiqyp
5iuEHJzwPbg1qeNdZ+03FsojEnmwBs9t3cY/CoNIgtHgwEbZKmc5wM54z/ntTlsDd2XIrsyQqZoR
btjzN+3BIx6fj+JNZejxr9tgmuVOFw+3IZ+T1z6Hjt/So5PtdjbQsRvMu4De27HPHX2x37VVTWIr
RJIEjVnk52Mn3CRgnj61nGMlsS3Z6nYak1tG6NZQLGyYXGCF2kjrk8HntW1Ld29vBGZJfMQEsoRR
y2CADk/T8a48zrCUtGchZFDlyNwZBk4wcAkY/oM0/VNQuPsdvcxKQkxZVXGOgHI4zgdvoK1u1uXf
Q66CUXNsChR5DhC54z0OD7/N+Rqc5lmLboTJJt+YEgOPX9a57RVxZWyM8jO58xwrfMpJAz+YrUu4
RAiOrkowxuBzlcd/cEfpVpl7o3JIIPs0BiR+MmXc3IOOTj/PSuT8ZbbuVGlkLxlgQFHIAOP6H866
XTwLm3RGDBWYEBm5K7fx61zGvoojiEQIVnGFJxxmtIO7JkilbS2pdisUqJwGYkj8ePx61Vv47S4u
lFu0vEeOjMc98/hisu90mRmXF4sUOPuliQOc9qXTCunWtyYJS8zHhtpAUdPx610JXVzFvUjtLF7K
+hlj+dEkUn5xuGD6V3mv6rqUEcUdn5JW4hcvFKnXOAACf96uQs7y5u54JCImfzFCholJPzY/z+Fb
njSaK7uEtBDdmWIK++LaFY7cEcnt/Sm1qh9CPSfE6vdWttdafsmYhXzbqoZs4AwD0ye47VsatFJF
fW9/CkdlbxIwkRAAWTuMge3NcpZxWrtaXliwg1CKQM4aJtqEHof59a3p9UvL2J4XvbECYFSW6bcd
eD14/SgDZuHvkhUmeVIyjSqochsADj6jP8qyNDMkl+0kzl3aGRyxHUlDzVObU9Vs3SCXU7aSFoij
eQRjsCSSOpyeh7VNo0gF+6xFSFgk25K/3G/qK56zujWnozn3KyDc8jZC8Nms+dY5UuOFRgRjJyel
SiRpPncY3DBA+6KpyLvDlV+Ucn5ulTFmk0NGY5ASBhgSM9Ku2YSVGJfZtHykdTis5Y1JRFkyRxtH
NXbGGGUAyNwF4wcc44z+NWtyOh2vh6QGzQgsc92GCa3VbjrWD4fCixjwoXr0Oa2lNN7mRZDDHWor
tTJbSIv3ipxj1o6g/wAqQEMGGCMUgOCu9PuFwHjKEHq2B+Oaw3RhMu8DB3AgfjXc63bwmF3XDYGT
knOO/NcXdhROlvGDtVyytj1Gatyb3GkX7ONpGVIgqg9ADwBXo9qI1hQKQMAZx0ri9Ct7lwrLArLn
O4HjHpXYxosaAlcUm7oGrBf48hsc8Vjw4w5I/i6/hWlfyKLZyeOPWs6xhEiSsSQN/QfQVvQ3ZjU2
Oc16SVyoAVcH/WoRkj0NYbkCRVchwQRkDGK6jXrGMIzPJtQHOcn8sY61yErqVUDht3bpipqrU1pv
QniOWOGZQTxg8/WmXGmySLvzz296l06BZJZC/wAoXGT07VuLaKVUjkEdAKKUbsU3Y5J9KmHIU/8A
fVSQae0SHzUJJ5HfiusaxBXnI/ConswFxnjHcV0cqRz8zZzT2a4zsOKoXDTRkKHfaB0zXTz25+6D
x9Kxb63IkHPb0qGikzHeaYMf3j9PWrVs8rOMs/XsfaoZIW8xhn8a0LOBi45qbAxoQlTu3n5e5rR8
MwP/AMJFZSKDsEoz+Roht9ytkjhfStnw/bbdVt29JQelNrRkp6nbakM2Tj1x/Os/wmoSwnAGP9Je
tHUObVvqKo+GRiymH/Tw/wDOuI6uhleKl3SHj/lotdVH/wAe0f8AuD+Vc14mGTx/z0Wukj/490z/
AHB/Kqh8QpbGPqwy6fSuV1kf6dbeymuq1XJkjx6GuX1n/j9tvoa75bGEdxJQPsbZ6ZGfzqlbxltQ
GPugEkdKvygm0PpkfzqgkRa+LKeRnIz05rCp8RUPhZoJFlblgDjB6cd+tUooGeKVvvfTH8q0Yt/2
eUbsDB/4EM1mNiOOVMFjnnIrNF9BkgVIhhs/N82OMcVntK3m/dAjPerkyhbXngFgcE57VRWQFsZU
AcdOlLozXt6F6CTeOuQkeB9PSp7khtHOJFVgvzDByRj1ziqlo4bzQB26+tWdSSGPSF2ZUuihsnO7
n9KzW7Lfwr5mTbpH5Kls5A55pbohokIzgE9fpUIKqCFzj+VSytutlPHU9PpVPcdMz70furb/AK5j
+lauiy+W7MshQrgjjP8AKsu9IMdtj/nmP6VraGubhQAfL7kqCePStGYM721u2FtJtaNvl5Zhnj2J
/wD11meJJvN0xclS24EAAggH1qZJykAlEzLbKGY4C7iBk4/lWTqV819YSHIKCXjBzzx3rNblIs3S
Z0pj6BTj8KydOY52+TC2Dg5jyT+Nat2T/ZDMcE4Genp9awIL2a1z5Owu5GN4HB6evvUUtJMc/hRo
X8O8Ki28QmJBIC4KrnqD60+//s6zhR3hdXzzuZv0/OohcXqy/aZ0hbKhQN/TmoNUmk1BYY5xFEiM
SXDcmukxIrkBri4OQF+U8+latukQdFjiaQr1IQY2n0rLuXEU854IAAGea0YLuTcFWWPIQD5cnOan
oVLc0YElWdAI5FiPJIwgwPXGcV0ejrZLZO8r+fIHOAZjwQflIBxXPW090HCKsY3jH7zP4fzqS3s5
oVVftEEhaYEjoWzip6gdZ2xS9abnJNGcV3nMVfAV84ndkBVBCyugPy7sjBx64zVy/ube7WRpGWJ1
UjDD5RkEf0P5Gsr4doGF5FHtDK6lj36d62tVsbY6dNGVEk8ySIH3cR4JOPXkmvPq6PQ61seVXMBu
LsQ2nFuGwrA4R/Yf7R5A+lTaT9kktSkrs1wJn3wqCCQD91uCDz/KqOoRDy4UfzLRfOH2hHctsbqO
mM8c/jU+kWUSOiRX6C6AadMLlz3HPrwRj8a5tlqRfcsxtaxzjCTRJK5kjWEEdc5GTjgcY+tdVpsg
lhMPnAXLxhgpYncDx6/r1Fc7byyG1MRMSv5odEYZKrkknB4xlenuK0NLaPIvLYPDER8mQMxgMQAN
uOfm/Gs2VDcz9VsbWa/W089gYiyHc24s349+3/660bhGtop7TbIk0SbQWAKtgA8n8h+PHSucklaO
+uJ5nSWbKktL3bp34z3rSDy3VtdPNOf3MYZXOGGeMg/Tj609lYSaZXF1Lcb4XSNVgGd7qNoOOmcZ
I9vesZdOZZOLdXO7OVYgc9Dk8cc/1raS3t7/AO0y20yIrYG0/MScYJH15xjnis+81RoIUidIWcRm
NZF+YAFjksOhPP4URb5rRB9zYt52RIVmuGaHYyhickcHjp3wR71Yv78xT28KSbo4gDFHJ/CrdgMc
5wfzrKKSRyRpJOqYQb0Y8A4BAHrnJ6etWtRgMtwy4kQpEoSN2HygkkAA9ufzotqHQv291slja3eO
2wdzpIcEYJx1wT0+vNatgbu4PkvKSy7mMpYlRz0Hr1/yK5SJTd3G18x7OwAG/kYBOeM5H513emae
n2SS4H2jzoyGCseCO/P6etJK7NIPQ3I45E/dsrADayFTwc9PwHeuW8UMRGRIWXDdCP6d66e1DG3I
Yl1D8Mzkk4BG0VyfjLyQ8nmTMUdh86jnt+ldMN7BMwvO82PlzlwPlHHr6/T9amgXz8okfmxMcBiC
MnrgntWbGsE0ZKhpXQdDjLflVuC5FpEkSQvmN/M27z82O/TmtzMvy21rbW0N3BGwKzplC5GDnkcU
7xXLDFr8zmXErhJQM42nHQeuDTp79Jo4ZfJJtyVcrnBBDDj0q94lieHUZpY7lwMoVgz64GMnj9Kd
7yC1kUpfJQSSmZWlkO0kEMHXBI7euPzqRptGW3iUT7Sqqow75Ujkjrx+IrNNpf2DNNBaPgBy5Mi9
Ov8AIUllcSy+ZdpYTS28wOBGRknPOarcRTMU5lkjhdpVdt+M5UjPBIz1710fh+zjt70zHJdYJc7C
wA+Q/hWbDcJdXLCGONAkf3SwJya6LQVU3J3ooYwydgR9w9TXLVfRG8Dm5oT5aMVZE5zsAAYEcZFZ
+pRBGiCABGgyQvGfnPbtWq25IljUlc8N85b9c8VT1VJIzayqzFDEyFmYHJBz/SnFLmHJ+4Zul2cU
19Gs2/yCZACD6Djp9aswpBAsOZDh40fb5YI5681DE8xdRARu3SMGY5BwQOvetm3naysbYtG0yyRr
tCEjaNqn+dbJGF2bmh7TYRFcYOcYGO9a68Vi6ENthHndkkn5uvWtlGqHuMkZgFJJx71WaTewIlKI
QTx/F2qyeRxVbJV3JA4zjn6VIGVfwzXD/JIvloclSPvEHp9K57WoLeHUE8jYgdBIcYwDhlNdrJE3
kMowGOelcbqNt9v1i1tlfb5kJTcOejHJxUy2C5etNXeIiGCWKW2iXB+XDM5Ix9eaju9V1Bb0nzMs
RiKMeh5P8qfLafYNYhZFJjkwZCR8ox3+tTXMbzPI8TbCZN5I4bavYfXpVgcxq2sahNJHBNeuCnzF
UG1W9h9OldrpbF4XypPz9QPYVyF2v9rebdzIrMqMpVf4WDcD8ua67SJzHC67c/MP/QRXTQ3MahJc
WEMwPmRswPUHODWHrlhbx28BhjVMTouEGOCa6Z7gSKVC9R61i6zxBASOBcxE/wDfQronFcrM4t3K
NpaRDWbuENuRY0dTjODWj5Kr1yT3PNUrEka3fOR95QAPpj/GtKRwUbjk9OazhazKbZXkC7hnpg56
1SkZFJBGfcCrDyEZHXNVZGYZOBVklV9ndT+tZt2ibhtBGR3FaTyE87f1qjdbnYZXGKhoaZjyxgSt
9PSrlqqbxkH/ACKhnU7z9KtW5KuAR/nFTYGTRbAG4ONvvWxoBDalCRx8461kROcOMfw+ta+gEnUo
eP8AloKp7MS3OzvubZvwrO8MBl0+QMcnz3yfxrRvf+PZvqKoeHP+PKX/AK7v/OuA6+hQ8SqWZSO0
i/yroQT5C4xnaOtYHiP/ANqLW7HzAn+4P5VUPiQpbGTqplDx4Cng965rVRIbmHcqhtpxg11Op8uv
sK5rVgftcH+6a7pbHPHcWFWeII4XBxmqVoEF/IzMgCq33h78VoxruiHODkVDZl0uC4K7TuyCDzzW
M/iKh8LLSMn2KYAANkjI9M5/rWLMpKysqgr+tbG8tFdjacBs5/KsEnYkwLZBbnNZxRfQWSTdGhlj
Dr5i5X1GKpNHGJndFCqxIC7uQPxq06GSFUB2lpAASOlINNk38OCO+eppxS1Kk9EJZoEjkYbSCcD1
6VZvrSKTTbYrGAzsoLj9c01YJIEbzMHPTB9qnlH/ABLEmKnEW1seoBGf61m/idjS/uIzI7dS4Ubj
zzgACm3yGOIKRtPPH4VaBw2VZiCehOf61Vv/APVjAHfpUmkdzKvBhLb/AK5itjTreWRlSN8g/wAG
0dc/Wsi++7bf9cxW1pXnNL+6B+QAgg4IOe9aswZ1cxeK3gBIUbcOCAA3tWbqsQTTgywiNNwA2jCn
v9atznf5EWB1/vE84Oe1M18MmnRozEkMOOcCso6svYiu1WXR3jO49OcnniuPkgeF8x9MdQM13M/l
jSNuwZ2g5C9q5ObjdwoAHc1MG7sJbIbYiAKFuZeSTgE1Zb7OZWWKUbXADHI9P/rVVSQSIRDbszFf
vLjApkbTtugjgO5T84BHFdJgS6uoLyAYPTj8DV/ThDhQ0rgEA9SMGs/UgRJL85Qgjp346VoWUbTS
jCtIoXO18gUuhUtzct9m4ZfapA3nr2Pr+FFxcWzLF9kaLzvMXO4e44yOhpYfs8EZElrGzAY+8XB/
DGKsx27J5MRRI4shwI14HPfNStwN0POW/wBWnX+8f8KeXnGP3Uf/AH2f8Kee5HWkBJNdxzmX8NEa
wlvZJg/73Aywxlse9dFOrmNlMbpI7PnIBBz0IPcGs6CzeOymZ0ODsZWB6ZB7568VJJJPcWKk3RVr
dWEaEgeZxnbXnVH7x2JaHlHiuQrKZICr4ZSy7fuMvB570uhaTc3NyWjgfznCMnP8ZPqOeM9K1PGK
JJZQzGDyiWGEHfnODj/PFXPBDzQWlwilEDyqyPIxOHIIUfiGx7Vm/hItdiX9qYprSWSMlrqQRvkY
IIUAknpyTjPenWVp9kv3wIvMknCoGkxtUHqR7fpVvV28qZPOjiwilzEzH7/ccHIHAqldW7zxR6ib
oNMzFXQDa0b55PB6D196xbtoh6JGXM5bVbuR1UwsFRlZAQMdD9cZ/nWtFpkkOjSoLsbCrEKwxj5c
fiePwrJ8Q3sdprDQMiXUaoEDKf8AZzkY69c5rV0qYXFgkSkzmbJllc8jOexPBPOe1VrZXJTRDorJ
FCkv2TDYGAqABjnoD39a5W61GGKa8RIYZEeZx+83ZBJz69ufxre0Bjp10UuI2McUg3qGz82SRx9D
WJrNiq61eo+1dzCRSnO4Ng/1p00ru7E721LlpIskME/lZAk8vzGJI3HBxkjGRz9M1rayYYLiGaEb
SYxCnmkjaMEEgdODnn6fjXSO3sI4CsUvkCZkIYBlBOPmHTnHY9xUuuXD3wtEtLffAgYtlRlcgZzj
3paXGtEW7G2kQl44reQyADdIpbcc4LY7/wAR/wCA13Nl9vkkgjlntlWRB5iqSV288kHvwK4TTJxJ
cRrJKEeIEIIjuAX73rwOntnNdhobys5aRI4gzblQR5ZsYyCfTBP86m+ptCx02oi3SOFbJkMSQKSy
kAZIB/M5rz/xkkkEDOxBkBB3hjjORxxXbbny8zBAs2D5Q/hI9B3OP5VxfjVpTGm+PnlsM3BFbp21
YpHM6bNcM4IdWl7DrgfjV8pqZYO7SK2OMMMAe/NVLbAUvE4RgmSAnf0rJ/4Sq/clSw9BlRW9pN6G
d0tzq1dbm1+yT3UWDOhdt4BVhjjn19K0PFdtAdbmYygy7lBjcKxVdvUDr7/jXMxaJDLdpO9zKFmY
MVVOhyP5V2GstAutOC8LtNChH2gpg8Acggn3p2sw3RzUssVrOjMxuEZ+IiAoYEY6+ntVhmimgltr
awkTcp2NE2ApwDnrj/Jq49jFbxQmEjE0pjby5lbAOechQRTPsJs2YfaQSMsWEnC+nOPTj360cyir
sLXMksbaNYFt4wGjO50DFvY4J5z7V1/hbdbrlolBW3kdgrHP3DnvXPJcifzHmMyOqlI5Y33DJPQj
HI4NbGkTQIZslhMttIFZnzuJRsdq56kk9max03MB7tHK5JBb5gGGP5VNeJI1taIgG8+YAM55981V
sdJe5VWkIiZuCN2SPw7Vae1C28EBnAZXZlZeOoII/Ws1UjGV2x1Jx5bIyLRJYY0laIBiJVJEgAyH
GevTFbdpqSWtvaLiVy1uhKg8dMVDb2NoIhbySSvjzAp4+YMcnPpyKn+1nT4ooiiNDFAF8wnI7/5z
WkcRC5zto3NOl82ASgY35OCc4rSjJrndM1OIjaNwBG8K3Jxz3/CtFdWgVlDZUHucCrV5aofMjVPT
2qBgfPX5TtIyfwrGvfESwX8ECM2JVOFwCD759qjvPEsEV0qwkSPt4zx1PT9KTdtw5kdE5XaSeBjr
XJrGF8V2+BhCjsPpz/UGrA8TLOp8xFWMuUKnuORnmsebUoYdUWWQSkqPkb6kk59hWbkrBzI6nVgq
xCVQC0eTtzgt7VNa2sTJ5xXJdcc+lYE2vG4EoeJSQRheRkcc8/WrkviW3jiChgnVSzdveqU03ZBz
IbdWltG0qbBEsR8wuRhTn/JFSWMi7ZCOPm9evArJn1eyu45T58k2cKPlA59cVFaa2kbMpcInQbh3
x1+nFdFKpGD1InrsdKZFA4Jzj1rI12cLaxZYtm4j/nn+lUovEVslw3nzMEPC/L8o71k6lq4vFaIN
uTzhIuTyMZ/SuidWLi7MzjF3NRLrZqkjoQVaRwTnsSvP6Vofa4XbYsql8Z2g9q5uLU0imlnZSV+Y
jjrk5H8qZDrMC7pSCm9cHH3hz/Ks4TSKcTpZCB0bJ+tJGiSBt2Tz61kRa9A8itlucDGzJFagmLrl
VPX0rZSTJ5WI1vGSR0H1qjdRIGwrEjFXGZ+6MfwpfsLXRXY8aHHRztqboLM5yeP9536VctokaQbj
/nFakvhPVHfesaMhHUNSjQr2ErmHnP0pXQNMoRQJh88/L61o6IAuqRAf3x/KqhtbqEP5lvIvy91q
9oisL+I7SPnHb2ok1ZiSdzrb8/6M31FZ/hts2Eh/6bv/ADq7e/8AHs31FUfDX/Hi/wD12f8AnXCd
fQreI+g/66rW7FxCn+4P5VjeINs+n212i4/0gwygdnU8H8VI/EGtmP8A1Sf7o/lVx0khS2M3UuJF
x6Vzmqn/AEqH/dNdJqQzItc1qgxdRf7prtlsc8dx6AvCADtyQM0yxMRlkMm8bemOlK4xbAjI5XpT
ITLkpt/dkHBB5zWM/iKh8JMwU/bGXheMA9e1ZCW7SRyuGjXJxkg8VrKBi6yMEY/pWacLBIOHyee2
KzRfQr+WVdE3bsSD5h34q+n3qQ2aRCMRpLndklsYHFM3st5HD1DqzZxyMY/xql1CT2FvP9X+dTFv
+JO0RHWBiST7cVWnkDSeSdwI/i28c+vNOfUFt7d7Rvmbytm7tgioa1ZopWikZAdUjQ5U5HYUy7bz
IFPbJFRgqFC7gcfhSsytB5eV3AltoPaoasawaZS1Dpb/APXMVs6OSDnO0Ef3uTWPfjP2fPaMVZ0t
w0xGV6YOT0rQxZ2BbzPJ5I2ncTnOSah1kyG0+fj5gACD601ZAseEJHGRk8Y9KpXd1JNFJFJkbSrD
P5VmtGVc2p5N+kluFG0AAnr+tcVchlnLLGjZ9BxXTxXqXOjSiSPJU7Qdx4x+PQ1y0t3EspRlGcfd
Umoho2KTVkSxRtG7TGDcMfdGVA9+tJJKhGFhEbMfmZeTTTdnaB1IPTJ4p6uqvhOARk/McitudGRJ
qRUyy7pAnIwSParmnvtWNkuflVQMk4xmqGqkCWQkZBPrjtVjT75Ug+WFCFx156j3p81kVPc6WEX0
4bFwrx8g4CgDnH9asRSSpcwi5nUgLtBCFt3I49vrWNZavCfMWW2VFxjcAMe9aumTpdTK0SHy2Kru
EZwecnkD0qU0K+h1Sc5BpQoFMjPzZqQn+fFd5gR6Xpeo38MrGWNBcspU7uBtBHP1zVLW0m0nUIrW
RgQYhLhTnoSGGfwqz4ek83THJyzQynysMRk4HT9av3h0vUoJGuJZXaLcu0YGxXIBIP8AEBnPNefJ
Wlc7L3WhwfjDcdKRUAwsgO3oDz0rM0K68t5ZFLkKxJkJA2tgcA4x1/pWn4n1QyWflOgaNXyrFAGA
HGT9SCfxrC025EbNKyNI1wylopMlGPsQcg7en5Vg9UQ2rlzV7o3VzuWPzX2mNjtIbcehB/iB/nmt
myudOg8p3jyJR+9kljHmHHPJ/Dp34rH1K7ih07cJN727YWby++Pl79yD9KsDV4dS0+afCskaZjgY
fMCRyC3VuRwKx95q6Ju76GFqkqXbsyhGRnzCzkZT5emfTJ6Vr6dNcC0jXymiilVTHPInygDg/r3F
c5fBjebZLeRBI5d1jILZ5IwfpXT6e6to/wAi+ZGDt2OxUICQSWzkZ+nc1q9Y6krzH6TAxZhMqyRz
S5R8lmD5wfrgfpWVPcLNql0EmjcWsgSNAmHG0kDDfiRz6Cr+hXNu2rsZrRrfYxkwWOFyMYA9cE/h
VXU9Lit9aaZDsS5fMMkTfNu79ev/ANeoi7N36l7q5bXUYTtuJLfKTupxs4UDqBjn60PKtu0wedbd
W4YoD5gLMOAM4BGB69fY1mrNbpbRQzFztYq20Y3Lg/jxn+VPvbNNRlhRZVh+YRx3GABnoA3p0P8A
Omoq+oWYiXqNqBkjkJMo2uUxhecc9uqgivSdIle0sYzsMLOoy7PuPA7Dpnk/lXnFlDIVl8yBFlAV
mLApkqc4B6HOQfeu10a6s5bJ5Lmd47cHdkjhN3p9SR054qrK5UdDpYZ4liO/e7IBIsgGSODwfrXH
+OJ0+zLufcEdRuC5xk4IINdjY6ppVvK6pdK6RNskk+6GyuARn6V594nhjlJtoZXmYTMC8i5yA/GP
UAVd4palSdjnrO/gs5HlXzHSRtihRgKPXnr1q48Nnc3Uj2cUTW5YAgD7vH+PvT7DTIYnZLjdI5yR
E0fbr2NX00+1tnkETvH3KZ46enr70lWjHRambkmSabcxxXscbvFKN69XPAz6VravMj6iJ4HhmcRR
n5kzyM9z+FYTbIAB5bSSByqmRgMjrxj9M1BJeKBAGjkKyKTgcH6Z/wA9qiVaT1iQ56WLs0LXd0JX
uViKoQ4ic7Wwe46g1IIYoi0sk3nIF4cEHHrn1rHZZ4yzmZUBU7ju3Z+o+gq1FbRRW72wcAgqyFcN
z/kfpWUqsnq2LmZaEqBzCrMVRcM45A+nqKlSWK7iljDr5ijAG3jHQ/nWYZNpjSWISM0QLkfL8wP8
ug/CmWzC3bzjCTMM7lHBK9iaysxXLN3cCG2EhdnEfyNs788D1xTYbmJ8NLmLdGDhc8E+36VBdRzX
SK4ILgB2yx3AZ5x/n6VS1KYWkyeXKGMoChcHKgnv+X600r6CNSedVaKNUEXAIAY4JHt/WszUp2lt
HgjDbt4KryCQTj/Hirf7mSBG3gMcszheR+HU/hWJrt+kPlbRH5hBkWRc5+lVTheWgzX0O4aKaJ5U
LwrJ5blzgqc9Pyz0rY8Q3BjCR20CsoKyiVeVI7Dn73euR0nVPPYAykfMC2VyTjvWt4k16BjCsJZW
iXaCeAR0II/I12JtPlHdGLcaqV1E4fbsBKqRnb7D260yHUTPLloguTwy8ZIHesgXETSPnq6YOf8A
PHNNlnKZ2bQQ5yq9AKrluI6uK78qCQiTCcBDgEgk5/KqFzdPIsRMqZP3lI5U5/z+VZX2+QRKpK5Z
uh7eppLubIVWkUjy92V+vSkoagakGoyG8G4FkB55JH0rrbS4srezglubdbh53OWcbhgfyrz5bhDC
hWM7vunJ61chvbiSSOLDMrfKq8/KPoKHG2wLQ9B1JNOa0UR28ETEgnZGB3wfx4rmrK9BvSWBdULY
B6egB/z2q9cuINOZCJHnX5lMmMMen8v5VipeJJLJI8flBynyKuP94Y+orPmUldMbkmeoabBpt1EJ
ZbMp3VzFkHt0zx0FQa94fttRsTFZMkcu4MvyhBn3P0zWVpPiJFlkl8tmMY8sAY4/zitH/hKIs5ME
v4H/AOvV+3prSTHzxW7KWhWUcepmG8h2FYpXKlOuZfl/SujfTLVlDQqM9NrKAP51hf8ACSW63Jul
tZPPKBN+7kr1x9KsDxoVwDDIPyprEUv5g9pDuXpLFY22mNB9DUL2i88DHap4teW/jIilye6kAH9R
SfMOo/WuhSTV0WrMptaq3bHPpUbWyjpgYq27AHnP4CmFlPPQ45pgRQXFxaEmCZ4vYNx+VacXia4Q
Bbq2iuF7n7p/wqjFLbA/vrcv/tBiD+VW40sLr5Ykyf7uSCKBNGhFquiXIxJvs2PXI4/MZqWW0sni
e4trm3n2jd8uCw/Kst9Og7Qn8SRUX9l26EOsWxh0ZWIIptOxNlclvD+4b8Kp+HFZdPO4EbpWYZ9D
SXEF8Y2SO5VwegmTJ/MYqPSnl063MN3EwO8kPGCy44/EflWPI0aXJLdFvIbjTn63MjGH/rshJT8x
uX/gVai58lMcHaK5S7ujE0EsTYeO5aRTzwQSQfzxXZ3mHdJ1ACXCiUAdAT94fgwI/Khbob2MTUDI
ZFA2njvXOaoW+1w5AztNdNfD94v0rntVT/TYR/sGut7GC3ZFJ5n2YALn5hwOau6YocFigJyecU2G
4Wzj8xlLcYxgVBZas9s3khMgZOd2K56soxlqEZJR1J5hiW+UDA2qadbJm3yCQcDoKS51FZopFEIV
pB8z55NVo9aeOAp5IO3jlutZKpG17lcytctzoxm++B8vJJrOuIt+o2gLAjZJ0/4DVCednn3kdR03
VFHdPDeQyIFBCuOufSkquuxDma8trGpZkDbmGDnpVGbTTNJM7NtwFHy/SnTancsOWC/gKrw6nOkk
hyDnHb2p+1iPnVinJpLKm7fk5xjI71Untfst08eTnyQefqa3f7Wkbrt/BRWPfTNcagzMR/qQOmO5
pqaeiLpyvIpXwOYP+uYp2mQS+Y7FNybuxxTb9txh9oxWpotzarHIsplU7zjFW2luVJpblu/vWitF
WPlV5wT0PSqEE4uWuZgCCwTI9Dmp9Zkg25hk3Db0YGs/R3WSG6wMEbMn15rONm9ATuyzJq3k2PlZ
BwMMCB0yawXl85y8alQeprZfRWvdMklVw0zMWVQeMDtXLsJYZTG67SOKajqxO5ZknbOASakSYtt+
fB71UBIOWAJoSQF89DnoKqxB0euEAue4b+lZazui/IccetX/ABESoYngl/6ViRtlVye1FjSe5oJc
SNk5J4I9q67wzqqw2kNtIXWVZ0VVWX5TkgbiD9cVxDTFUbBPQ9Ku6JqSvqmnxxx7VM8ae5ywyTQk
Rc9sjTGcU4daRPu0p4rtMip4OsrpLG6WaF2QyBolkOBkKQf1watwabOjXclzGqRkMP3Z3khu4Aqj
ory7mbdK25wrA859Px61bjlu7e7vHyyBWjBOOvyLxXn1L33OyOxw2u30N/aQQ/Zt/mI4JDlMnkAH
0xweetYmkzy215KZElntWVZGWRSAGB4GQcDHt2Na8Oowuzh0823Ej+YhB3gtxwR1ByfyrCUBtTnV
H22kvDJGSwJz2z71jFLVGSs2bU0FvdxW800KSFEYBUbIC5yF98AVLaWltCHBX7IzOXbau4Y3EY4A
4wwHGeSKW3bTpIZNPnZk8lvMCx8H7n0zx71BpWk3uFkWbeCwIgTnKDDdO/T9KnTqUjD1yC9mvXlt
wX8gZ5+Rs4zn/ex2FdBpTQzWMlytuS10HE0LMTtBA59TgjHPtSa9pa214Wknle58sYcnCnaeAw69
O49D+E/h7T4oorweaqtNEXJEuQrZPpzx/WmmmrEK1zN0r7SbydLKTykdxFsuDuJ9Mdsgcc1Y8Ro8
gEEEaxlG80JP1QYAJB/Km6dZrLO8kF5FIUkZ3ZkwA24DHPp8o6kc0wTMt2qXIM6g8nOSU/i3YHPA
PtUO6dynsV3/ANIe2uWjeH938/mZwG6dffaD+NWrSC8uLsJpEEk7SSEiKWQFWYDJJPHHQgk8c+lV
ZirzFZbgkI3mRgAKHQjcpwDjv0/Cuh0eVb2z1JrF2WZUKCU8bjuxxnp1rSCvLUF1sS2Pw11+WNHh
k0+5lXO+1trtGkXI64yAenbmnyQ3mjRtbX8E9qy48xHhZXbAHPPDAZFc/b293ZKJhfSpPv4duAcE
5Byc9P5V1unePNZEC2955OqWDAgR3qCQN7AEZFJypvZ2Kukc5FqkaN/pBDkHGVj25BHWrEjvJGzo
q+WOvzZ2++f1Nb0i+A9cbypYp9AuyPvW7+bCOf7rcgZ7A0k3w91byUl0q7tteiTgC2kw+3nOUJBH
bgZrCdGTXMtfxI5Wcr9vdl8holQkFcgH5jx059eagLPZ3wnlA8kgRlse+en4Vcu4LmHUpl1DTpIR
EhBjI2MOw69Oaq3U0DLKDuCRkJC6AksT1GDweM1CeuxnsNn1zZL5dxGz+Y37tVXHfnH4gcVR1C+m
EkVtLbgOQGQuhBQYGPr+NTuLu1nh3+Z8wzG7rggHrS31jF/aNtKiDy5B882/Iz/Q/pWkbKwiKKZH
inzlJNy/OqFQDxkfn/nmn+e0kSsjMpQ8Ak4JHc+nGKSJPLkXzJFYsdxDe/GGA7n/ADiq95ElvJCw
JO9s5ifqPTn8KLpuwGutilwiTLM3lquCJSNyt+dRMs0QXzJVRw/DsMEjv25H19qigkR180FZJJO0
WRx/Q579OKqfbGy6NNw0hX5cgHDcZz/nkVEVJ3A05bnzZnaUviJlUhs55Pb68Vj61cNNdpGUTYpw
JB95s/5NXWum3hSN+z5jt+Y8cD/PrXP3RkhuHBm3vvJDZzjqBj2xW1OGpVjorSViFCyKFC5EZPLY
PP6VyV9FJeXk0sQ3BARtPRAP8f61raXqUFp5ckrFphxgJnHP1/zmtCy1S1iS4aRGVXk3grEpJPQ8
E/lVWnTbcVcOWXQxtHhE0rI2V3xj5ducHt/jWz4m0xrmGOS3+aQEbz0zx1xUP9q2cN4ZoYXwU25Z
QufwBOKtNr6FcLbScdmIwf0rKpGs5qcVsDhPocU1nKsypn5z8vPbPY0yWCe3laORSj5IPHNdQmqQ
fbmnNq+QgCrxw3P+NUtUuLe8JaO3l3FgW3Y4x6H0xn9K7IyqX1Q+WRjAxQqvUyLxkH1ot7Oe6maG
EFm2k4HoOTW5dw6W1vD9liu45FUAlggB457/AORWpotxpGn253JercuWLERqeMnHOfTFVKUlFuK1
Hyy6HKLFLhYlUhlbAI9a6rw7pbxyNd3aE7gNi7sH61JCbOfVpJpYriOxIOCAu8nA5x07dvWtuKbS
JgzC5vIz0CPGAcf1/Cueqqs42jZEyhNrQgvohcwMip8/VdzE81zMhEc+Zo/LkVvmXGcnPWutM+jG
Uoz6hk9tqrgVTul0aW4WUR3jxBSGDAZ3ZGOfSsqNGpDR2FGnJEemEPG7lPL3knBPfNWmCdC2QfQm
tvR7HwzfW779RmtTG2wrKpJbjqMVc/sDwsx415uOuY3/AMKmWDqylzKxEqbvucxhMdufUmopBG4x
nH+7kV1f/CNeGmXYNdYn1CPn+VPXw1oCkldZU+hkSQ/pihYGqL2b7nJoxSRZFbDp0IJrVttZZl2X
JKnorLwPxrYbwxoLDC6xnd/0yk45+npSnw54cCFDqhIPqkuf5VtTw9em9GVGMo7MEYSqCDuyMjmg
KR3P481ZttO0azh8q31YBR/eSQ4/MVPt0xOBqkW4fxeTJ/hXeoy6m10ZxUnkE/lUezkndyPatTGm
sRnVouf+mEn+FNeDTs4/teM5/wCmD/4VXKwuipBfXVs3LLKhHCOuSPxrQj1WKTAkHkk92HH51A1v
YKDnVoyPQQv/AIVH9lsixJ1WMZ4/1L0WYXRp4DruV1YeqnNQOr5AQ5/4Capizso23R6usbf7MbjN
WormCMDztTglx/0wcH9KdmLQoW0LSWpUrlS78Fcj7xp0ck8RitvMfZGzSYY5yG2jHPIHGafFqFpa
QKrTxsxdv4TjkkjqPeh3D3hO1QPJ/hP+1SsA275kX6Vg6qf+JhD/ALh/nW7dEeYv+7XP6owN/H/1
z/qa0exCEu1ZrbCLuOegrNEbi6LbCVx1xW7bRwygiSQIAuQcZpmnNb8+ZK4bn5QmR+eawqU+ZiST
iZm7JweKpbsrJgZOfSulvfsXkSbDIZQON0YA/PNUYrbSTEvmebuP3tsIPP8A31WHsHawcum5hSpK
W4jY8f3arnfHPGWVl4YcjHpXTyXUaSBUtodgXALA5P61BNJBLc25ktUKjcdsYCEnA6mrWHJaRiPL
kHmq6SYZjnHT+VdM81uvKWGOO8v+ApkcllvctYHjbjEme1L6u+4NKxzplA71WkObpj/0xH8zXY/6
EelkPxY/41zessp1FtkKxAQAAKSc8tzQqLhqXRS5zKvR/qv+uYp9i2Efp940l+MND/1zFa+jQaWY
XaeyvJm3nlCAOtOcHNWRpPVGXdhmiO0frSaHnbeBhg4T+ZrW1STTrWLdDYy8nGJs/wBDVTT5klin
ZLdYQAo4JOefepjTcNGKCIo5fs7Ax7gQePmOPyrK1G1aeYzoACeoArUkLDG3TQwzy3mHJ/DNNYHk
pYt9Gcj+tJU5p3TJs+5hRW8kjbQp570x7ZoJtrKRzW3Bb3EDM4tgd38JJ4/I0XENzcbR9jRcHrkk
n9a19647C+IzuJ4yC5H6Vl29pLNGSq52jmtjXIpJJGWNclXPH4VTghvI41AiOMdMUa20LnuNg0mW
6BjQHJyMY6dq2tM8LtYXmny7t0izxll6Y+YVmRLeQnKK6/QGtTR7+/TUbSN2LK86A7xnuKavcjoe
rIwZfxoJ5xVWJm80jPy9ask4xXYZGf4Y0nVczzPqUS7gMrsyUPQd+OtdVeaLbxpcySX11dPOgDqH
2pkLjPHPQetcX4OlnzcoknmSlUKHO7dye3bpXZatqaQ2880MbFYg3mAjbxg5Az1NeTOTZ32stDxB
LqGNopbNEUbeN8ZJGPm5Pc9R9KfcNdXMMUMaqJEk82QRPtUZx0HU5yOfWotPura13QIw8xysnmfe
CgDJI64wccU65kmfy7qKJ2+Qxgx84IHX2/8Armi1mjmWj1J44YrfWYrho4ZGkYK6OGABwMkA8g8c
/pXULdJJBFvljtp4RIzLnG0EgcAHOMgHv+IrnJ/EK3xtpPszSysR5kkjD5iOcgdv/wBfrV3WFgni
juFkVpd65jZPlUEZyPbII/xrKSd9SlcJ72K6hla7hjllh2rDKzkDgnIBzgqeQRS21s9jE80FskeR
tDwy4YnAIz7ZwfwNQG6t8G2vQsNqPkjmCBlDEHg917n2pLN7i5tzaeX5iMvylW+XPZjx2z/nFSuY
aY+GF1jWaWeJXKkyQqSNzudxJIHHY49qZAzSvIJ4i2Bn7pZSuDz09uDjvVrzbiOcLPZSOyoG84Do
wH06Z6ZqC+vryGE3WySG6kcRKACpY+hBH6U022S3fYbZ2OlBWge3l84n7wOV79R6dPxIrZ0q1gtL
fUo4YvLVoeecg/MMHjt/9es8Q3M77jag3TpvPkttKLkE54+Vge/uasWcs0Npqi3AfcIyvln5SBuH
fpz6iqg3zb9/yDmb0KckPlzMXjR+zhn5yR09yOv41TklKXDuTKjBeMrycDnjHb86qNcb5CzgK27g
N/D+NVp7glSXZGwTkkferGMX1IbLyLGDcFcSSsV8p93c9Rj60221q/0+4VbWaSGaPJYwvuXAOOlZ
ouP3QUN5Qyf3u3J/EfjWharEt20iwAttCDAGeOpGDjOOfWtEnDULneWfxL1BrJRrlvaatZBc5uQr
Mo47/eB59a0AfBWv26La3E2gTuD5YdfNizxyM4YfXmvN4A9xeR7FVpdxKZxjdknBHf1pTNK08clw
HMhXau75sHJ5I7Hijnv8aT/MfN3Oz1j4f66lnPPp/la1DtBV7FhKRj/Z+8PyrjNs/nrbSwtDdldz
McoRtzxg1r2OvX9teq9ldtAVTcSjbRn0A7V0EnxLS5lNn4m0m31aNDtWaWPEpB7qww36mnGMJaR0
fmFos4CTy/MiRGLuoBORzJznHuar3qrDEWdCSq70cNt6kjBH4Yx2r0j/AIR/wL4hl87S9Tl0i+Jz
5d2PMQH0yMMB9Qa5fxN8MPE2nRiS3sRq1hu3tdWBEw4PAIHzL+IFaKEk9Q5WYmiSTNbxhJxGyE53
J0IGeT6ZIqttcshlkKuzMr59Ccmn2Spaw3ImUxvGDkk9wOcfT8e9VIbh7g7lG0b8eZ3XJ5/QUlH3
m0FtS99s8u5byWDdMHGNuD17/nVf+yWlmW5eWPaRyhJBz+XFXtPt44p4/MJDyHPmqPMAH0/z1q2b
aMSfPOfKLnkZz+A6d6pNRehtGCW5EmnPPs8lIE5+XDDJ56c96vaP4aOp3phffECPmZhgqP7xHv0H
vV/StOGoy+THEyOGyZM4G08ZPX34ro7ua20QtEhkLSKGMmcFjknJPaqim9ehcpW0Rzd1Hp1pqEll
FZKREdofys4AAGScev8AOsK7LRkK20bW4YJjAz/+rk10Fxbo801w0rg3BLbeeQe3vVC8WK2gWZnK
nhPmjHQnvzk9vwpur0MLIrvqn2SVTLbR4Zfu7FOT65pTrwLuFggjHBRiAd30GOaZfGK9j+w3ckMb
J+8UwoVcDtxj0qqPDcaKJrW7BUnJVWyRx2FUqjtqwVM6mG8tnRWxEufYVOlzGy5VBj6CuSj0p0A3
TXLK/AEUOdpB6ZJq0bO6IU7roleMrExAP5ZrZVX2J9lLudnYQpepPtYCSJNypj71c9J4niWdY1YO
NwXKtml0GS7stRguZRcqhyjebGQCD656Y4/Kl1TwJe3GoXEtncJAJJfMEUkTfIOuQcY6n1oc5N+6
N09C9aaktxCsqsvTnac4qnZa2brVJrYykYU7UHbHeui8NajdeELd7C+trO9SVt6PMQNhPXLY9q3o
/GFkMM2jaRvGeVniOR+VNyk0rIaprqzlhOAVLShCemTVxbuIAf6XIfpisjXNYgv/ABHPeR2EEcbW
6II42UqCOpBAxVf7fCetjGfy/wAKFJlOKOnsr6y3yi5uptoxt2RqxPr3GKtvNo8yfLLfEev2dcf+
hVxv2+2z/wAeKfmP8K3PCes21jo88b6KL1pLp2yJVQqDgYGfSrVRpEuCZq50kf8ALzfD6W6//FUh
/sjJHn3ufQ24/wDiqmtLnTbtHdrO6hIYrs8+M46d6g1SXT4oSYYrgXB5Xe6sOvtWvNpcz5dbAo0r
5g1xdBgSCBCpH86jaPSMg/aLwf8AbFP/AIqmx3umJGqi2vSQOTjqfXpT2u9KGCbS+P4j/CjpqITZ
pJOTPet/2yX/ABpkkemMRh704PP7tf8AGpft2kxjLWWoEdtpH/xNINT0Y/8ALlqI+v8A+zQBGRpO
Ot7+MS/401k0w/xXuP8Armv+NS/b9KbIFjfD/ebH/stK17pn/Pldf9/R/hQBVYaYeN99/wB+l/xp
hOm9N159fLX/ABqwbzTCMiwuT/22H+FRm703/nwuR/22/wDrUgMy/ttOuIgFmuvkYOA0QxkHPUGm
x3EV1c20sDlo3PUHGeuf1q9PPpkiFRZXa57rMM/yrM09IIZkggR1jiYgBzzyc9vrSYx2t36Wk6Rz
TGNWGVdRkj61QKR337zf5xAwHhb5gP8AdP8ATNP8Vg+fC3zhQmCyqGA9mFc6iPG3mxN5YB/1kPK/
iOorCTdzeKVjfELkFUmEuB90/Kw/CpbRraP93cxyrJ2w20H9KzI9WmCj7XAl1GOkickf1FXYtSgl
X9zNvXvFONwH49fzzQpMTgi5d/ZhbSGKCQNjhjICB+GKiiNr5Sk205bHJEgwf0pCbOVCsvnWwYcM
g3x/5/KrVvaSxqDC0N5H22tgn8P8KtMhxsiB7iRXykSBQOmwZ/PFRSXTtPCZYlkUbsKwwOntipZr
29WUqjiJRxt28ioHu7kSxGQrNjOA68dKq5k1cdLdcfLaQLx6E/1pkdypeQtZQnp0yO1LLeTyAbVi
T6KKSG8nV3zFA545K+1NCa0Jjcgji1iHtjNcxrcjS6izFEQC36IMd2rqBqEn/PGL/vgf4VzGtzvN
qMjOFXFuAAox3apqfCXR+IzL47mh/wCua10OiTQLaurWTOd7fMJyvf6Vzt2QZIf9wV1Xh66RICps
IX+dvmYnnk+9THcuexDfWNpdfObaZMdB9oyP1FZduscS3MKAjaVzk571273kTLhtNtiP90/41z+q
tCYyYrGC1JIyYgRu5705LqKD1sclFess/wB84Jwc9DVi7vPKA2nk1FYQGSVohHGfM7yLnb3rQbRS
eph+gU1KbtoDSvqZQ1SZG55HXirceph1BVgG44YUknh4k5zCv+7uFSRaLsZf9SRkdc5FC5kFl3Jd
TmEVzISOrmmWt2JiFVGbj+Fc1FrhPmsR/fNV7QvEgeBxu9N+00lexckuY3VjlbpDJ/3wau6baXH2
+2Y28gUSqSxjOBzWTD4h1OzAP2qRR6Ft4rV0zxbf3t7bW0kkQWWVUOIiCQT69qSTuJpWO7h4lYEd
s5qQHJIz0qqImQ5SV/xOf500efHIWDK4PY8V2GBb8IeIoVs7pLOKMvuGGjiClcg45PWm39zdXNvN
50pYtvQ7uSSyDn865/wFDPFZ3222aR2cMGzxx35+tbWtx3MGmanObfzAqLLH8wGCFAK89eRmvMn8
TXQ7X8J52i6fHMUkdo5JGaGRG/5ZgY4I9C3X8Kvbbq1ljR8CKIt8qHqpwOh9D19aybSFGtrZopXe
5aQbxcr+7IJA9Pr61fS7RLmezm2hWBOVGRG3Q5XngdfQjp2rne9jBNoMxsyss2+YHa29ASfxHTjF
WbSWwuSgaBQYhkqQV2gnIPoev6mso6hFDexCOeOWHHmyxKgDN16kDqB/+qtlN6r519agxBQWkXBU
qevQ8t/9aplo9gb1uWrqC3jiZZYoyuSRuGDuxkEDpjp+vvUUKxywqNjC4QMdq/KZPRlHoeM+vtio
rS7hubW5tINyrFukhzNt2IB05Pfp7VRk/tBDbysgSVGbEkOTlc5XGew5wfpQk3oVyuWiOiuWkb5o
ligcouEkABA4+7g/Qdc+lZH9oTjcEIuY2IQ8hkJ6H7wx6du1S2djJcybpEuCJSSd/UHORj0Oefwr
oLPw9b2oPyYlB7scGtIUW9ylTS3OetYtSu3K2+NrIFZRwCO5OO/Jq7dI62l4zyCZjCAT64cdTXSw
IYiPLhTafQkH61jalGsk97CMqZEUtgc5Zxn+VbKmlsDS6Hnl3MYZJw2yQ8HIzxnBx/n0qtdXDPGr
jcGYHAb0HoaNVGJrooNi+bg5z2J9az5hOZbTn5XO1QTwRnnj8aIxWhiaEF8YZCpG3KgbtoIHc49D
zU41S2klkllgV7c/dhLMMHsf8+9ZMk32iQksT82xQB0APH/16swJ5lwRuHkxsA8eeWHfAx1olCO7
A6GxSCW0f94oZeHQfKU9CPXH608XtzBLFa3Sfao9u6KRVG7ae/5jkGs61m8tWhFuzqz4yyZbGc9R
yD2/GtiaVWSKLynRFywK5JGe2Pbj8K5Jqz9RBNJIQWYCNlBbg/L0yV9yD+WKyNWuGjkiy485SQq9
flbng9cYx1Jq8xMrx2yKTNADvy2Nz/y6etYl3IFvpJJHkmeIEZPQH0AqqS94ETG4WFJZXkAbOCFY
B8AdR/KrmiePvEGiyNc21+6RqOF3Hr2HrWFLZyyKoYEgtuIA68cZ/WrlnZLAnlynhyGK+WTwPrXZ
G0Uaxiz0q1+JGmeJ4gPFPh22vSVANwqbJRnj/WJg/nmnHwN4P1sibw9rh06Vh/x7X4yhHoJF5A+q
1xUSG1CupK44A6ZXof5elTxITI0sL5CDaCBkqT78fhS5lfVG6izo9Z8Ba/pFuty1gstsvH2mzcSq
PfK9PqcfhWRp9s91crDbgzSTLt2EYCnHJPoBya6DStc1vT7m3h0uWbznXjY7Zcjrwe3vkiuzj1zc
xbVNHsr2WRdslxbL5UxwRkbgBu59RzSjFS2BytuZNtBZ6RB9kiZRIy+Y7YwZCBjP09BXL6rqb3Fw
dqlWX5P3n8R9R7V0Ov8Ah2w8UXiXGi+IV0+4iUKbLUFKcjPSVcgHB7isS88Na/4cWWe70eV4f4Lh
SJoSMjkMmQPoaKnNayWhkk27spLLLuQnYB90DeM5/wD11Vv0juIH+fzF3AFo3Gc/T1H6VmyXlpKz
/areORXceaXHzEegA5zxVi1ntnurgW00MZGdoRcI4wenoeaxdyF8Qk/2OeRlBe4UAKJQoBPHHqR+
falsUMSMhRf3nzAnKkGr2nW0KeUkMJVYmLs6HPzY7nHP596sTgttQAo3G1gmSQOOT1qk9Dq0WqNW
0TbBDauFPyBiq9Pm+YfoRWpIjwkI3GVyKsQ+Fo7ia4vDeywtGwCAYCDYoGfXqKWTyL6GOWR3i+Xg
oM4PcH9a7IzSsjmlC92Zt0FMDg4Pyng/So9NuZHhyssn3VHDH0rZm03TXs52S+mDrGxVXUDJweOl
JoelPJDJbxSoEgEY5bBO6NW9OeSapyV7kqLtZnLam802pBJnd4MxfK5JTOTng8dKpeKIrRbSH7Os
KN5mD5YAOMe1egWfhGy1vU7qyur+VJbcJIqIqkMCOefxq3dfCPSJPkW5nRgchtikmpc1qilB6HnV
pp1vNbQzMu12QZ2cDjjpU50yD1b8619c0lNB1aDRreVnVbfzDI6/N16Yzj/9dVWtnUA+cCD/ALH/
ANepuirGc2k27HLFvzqxYaXpyXMH2m28+FGJZQBuYHt7+2am+zybsNIuOxC//XoEEik7Z9rYOCE/
+vTTQrF/w7f2Fnp7o9ten9+5XyXAAXPA/CnXuq2U2pWa+VffZVy0kLycs2Dgj6Vp+CNDbVNFNwt4
8JWZkMSqGDcA7ue5z+lWdY8CXEskV1Z3gaVMhgyAHHt159qr2i2FyPczW1PRRjFhff8Afwf4Uh1X
SOn9n3vTg+YP8KgfwzqecC8XPfgf4Uw6Ffx8SX0an1Zf/rVrzIy5WTrqukHO6wvsg9mz/Sj+09JY
/LYX34kD+lNi0C5YZOoKf91BTbzTWso1d7rzCTgAKBmjnQcrJZb7TVH/AB5XZz6OD/Sq/wDamlZA
On3xz0+b/wCtSWtqb+UxhtioNzNj8h/n0q3/AGQB/wAtgefSpUu43HsUv7Q04cDTrwf8DFJ9t09j
/wAg+85776vHSYDy0svH904ph0u1U8POf+B//Wp8wrGfcX+mqMGyuufR/wD61ZkF3ai+jMEU0YlY
jEpycgDn6YFb7aZYEHck+fZ+azbnRrQSpJHJcRmNiy5IPPvSbGkZ/iKRknhkWR4vkxvUZA9mHpWI
wQnzZV8pm6XFvyp+orY1oOXifeyBVx5m3KH2YVksFjbJ/wBFdv4l+aJ/8Kxlubx2I2jaMGXAkQ/8
t7Y8/ivQ1HshlYk/Px/rIhhl+q/4VMymFvMfNs56Sxcxt9aa4ViHuE2E8rcQdPxxSKFilvLUb4JR
PH7HkVZtdQhlfDbreXOflO3J+nQ1UkEkWJCd6npPD1P1HQ05ZoZk/fxrKn/PSMcj6jtTFZGx+/yZ
IpS/qycn8VP9Pyqu13c7t7MJlT/Z6fUdR+NU4oJQBJY3IkUfwk8ipP7S/eBL6AqQOJM7WB9mFClY
Thcsrf3GcDyx/wABFA1G4V34iJOOSgpgjhnOYZ0kb+7J8j/mPlP5VXktfKcCUMn/AF0G3P0PQ/nV
cyM3Bot/2rdg/ei/74FYOsTyXN9K8hUkW/G0Y7mtHYikrJGw+vGaxNblKXaGFAI3hCk/iaHqgjo7
le5H7yH/AHBXU6FqDwW21bS3f5zy4Oep965O8ciSErj7oFdPolvbNCDKHzk8jkdTTWhMtTdOr3BH
y2toD/uVjareTXcA85IU2sMCJMdx1rYjj0+MZOxvZz/SsvW3tfJQW6Rr83zbPqKbaYRTTM02kaPH
cJEkZzg7M46HtUhbityJNOkhUOtsT6nFNMGlIeTb/TC000tiWrmAW560sZG4c8ZreaTSoz0gH4Co
XurFjgG3x7MQf0FLnDlOR1oZlbqfnP8ASqdtaSXQ2x4yPU11Fi8CX8vnbcFuN1GsSQ/aIvs6oMlc
hcDPX0rNM1luzn7izmhjwyk9en0q14dZf7Ysgx2kzpgHvzWjdxT/AGVc20IXB5xkng0aFEv9r25Z
EVvMUjDd6aepL2PRR7Um3+dGMGg55966zEp+G9XH9mXm0LC6JvTaQccc9PoKzGMmoRuZJC5cFRu7
ip9AsRDb3aROJXEDLhCDyc4qqdN154J47HTZZbhIhIEyo7fWuFtJs6tWjJtfPk0tUlmgjZY02bmz
vyMAHjr1pW1RZbN/NhmhljAG44ZflGAuDyeMd+9ZGn2dw1vbzyM8sIjV9pAYAjtjOf8A9dblppyS
Swp9nZMLlpHcHJ9Bz19zzXL7PVhGn1ZjtZ3TESsChXDEBQpH+NXm0u5kXykkKRFuRgrkdmK/4V08
eibW86VECbuAGP4E+tadvboscZIZmQlh3Ofz/StVBvcu6Obs/Dl1AjrKisGCgF4xnHfr2/Kt+102
CBnVgJGwCFbAC+uMCr/2pQCBG7FRjDDjNN+0NJltq/LjNaqKRLYiDbGrPw2O7ZxTVnEagBwxGc+/
4VGJwWP7ske1RSFvvLsGecH/AApiJzNuAIcAg4OR+lZGpt5Jlndy22NWOOcASDpVp3dCS4Dc9QTx
VO8BkWYMw5RBkjp+8FAjgPEqw+c8lq0Tic78e/zdj3rEit0Elu4JJXL4xgj5fTPrW14js4rKaS3X
CsgLI47+n0rGEmxCX2ZIAxzjFZpmb3Jre2tbeIecS0i/MrLyOR9O39Kg8iYOyJHITu2qxU5Jz3/S
p4naOZZWJCLj3U/hVt50mwWleQqfuuMbR1P64qW2mImtbt55QMmIRpkyY+bjn86uQz3DKszPLKwP
ykL1HvjNYgnc7wpBaUZz/dq/BcvHAFUgykkO54wD9KiUNNAtfYie7cublHcTSA/czwM/4H+VMWJ3
+WXq5P7zdncfT65zWlBFATlmDl14Ydjgd+3vUkSKwB3MTyThuCemSO3WqjZG8IdxIozkkIwcDG0j
HYf4EVIsc3mOqPENvOH6/TnripZrX9xGw88bWOTuIUdMf41NPBbxOylZPMOCzAgh+uCc98gGkb2G
WhQRtHdQ+Wd3mFSvPTGRzzwatQadJdBY7F5JnlClIjHw369Mf1pLJJ9U2wrZCa4baFKNwx55x1x+
I616Bo2jxaJCcMJbqUASSD+Ef3FPoPXvThBtkOSgiPS9Ii0aNAuDeTcTOp+UAD7i+3r61n6nq8No
5ghuIzIkbeYwO5o3LDAx64z+OK3NRlWztlusb2VTtQdXY9ABXlepS3K3pKQss7yZd1IOSTng/nmt
Jy5VaJjq/eZpSafNHcNcRXB8pPmjwDukX3HRTW1pOv65pDqbDULjBwSrcAD3Hf8AWuLSS/kwsdnK
6Mw2yFiSPy7d6hvpbnToZpT5ke9gQGHfP8LDpz29K54uXRmaeuh6U/iHRNSuAfEvhe3+1EZN1bKI
ZCPUlflb8RUMvgnQNXcT+H9cihkY5NvqH7psHqA4yD+lcRb6jezRwGZC6ggSHYF4+o4z6ir8UV88
WwOiBMHeWJ3Z9MZx0zirT7o6YaotXvhXxN4cdEubWWKBztE6ZMJBP/PRcj8am0W3Z9Zt4pGSYCXL
lGJACnJPv0q7o/iDxJou0afqO9GbDROcq3t3H4EV0VnrWmaz5802l21nqsAK+fapsSQE4IK9M+49
ferUU3dDvbc6TTog0Clm5YZI+vNYeoRPZ6pPHE8cbkCeIO2Ac9f/AB4H863LcyKgG4cVzfit86rY
EkE+TIP1FWloZ31NTyzd2glmyGeD5ok4UkjkZOfpmlsLWGBpv3XlBtvLkODhVHGBx6fhnvUbXgTw
/wCSH62mwDH+zjFVtJ1S3VZXbc6SODygwSEVeP8AvmtNCTP1q5udL1OS8sxcRkoAbmJgEAx2XqPS
ooPGV1E4dvE0smQUCurHBzWL4o/f6611Gm2FwMAdsKB/MVR8QXUNybRx8rRQRRcdyDzSsgTaLOr6
5d6jqq3b3TSSCMx+YwIJA+tQDUbs/wDLdqpSMWkhYtzs7/QU4jP8dOyC7LZ1C5HWduaa2pXA/wCW
7c1Vx0+bpUbjOfmFFgudl4QvtRg0graXrRIspJUA9SBzUl14g1K9umhi8RTQyQB/MSNDzt5Jzntg
1R8HXDW8UqiQqCFIGeKzbZ0Os6lKepW4/UN/jQ0uwKUu51Ok3rT2ayzXgubl2bLycvjPGfStNLhw
nOwj3T/61YWhxINJt7iNc3EbPlRxvG48fX0rbaaV4VeJJDuGcM5Uj61V0tCXdjTIpOUmVW9h/wDX
rGvWluLhxJLbokZIU+Z1HqeTg1rxwRgF5CEmJ/h5wPxrkNScC6u9pyDI3PrzQ2gRvaXthgWY5Yyk
thOcjoM/z/GtFbqPGNjj/e5J/WqVkt0trDuSMqI1xtPOMVYbefuow/KmIlM8fY4HvTTMhyA4zUG2
XHIP5UhhlJ5jY++KYiRnAx8ykfSoZGU5/ecfSkELE4ZSvuaabY/3lH1oAry7QDllOfVc1h3emRks
9uyRE9Y9v7tvw7fUV0LW+RyUP0qJrYAfwD8KB3OLaGS2fy4x5LN/yxk+aN/90/8A6jUcJKyskai3
kPWCTlJPp/nNdZcWfmo0bohU9QVHNYWoaJIF/d5njH/LNj8y/wC6T1+hqHEtSKIjRpGVGNlOesbn
5H/pVWeHy5P3yNbS9pE+6f8ACl3Sx5SVDcxDgo/Dp+f9adFcuFIhYXMA6wyfeX6dx/Ks9Ua3TK7e
ZC4kkBHpNDwT9fWrC6rJjEsa3cOOXUYYfUUqpDPn7DIY3PLW0v8AT1/Cq0kERkPnk2cvQHopP1ov
3FZrYsxx2V4T9juPIl6+W3Q/gaf9r1HTvlkUvH32/Mp/A1nXNnJHhpoRMnaSPg/WnW19cxkrBOJl
HWGfr/jRvsV6mnDqFjcDbsMB7mE5X8UNWYLdFk8+22TuF274W2vj3RuD+lYrXVlcYF7am0kPSROV
/PtStZ3UIEtrOtxH25z+RFK7QcqZsSQ6XfOEubURzj+KL9zJ/wB8EbW/CpIdInhJXTb1Zv8ApjKv
lOfoG4P4GsddcljHlXsQZe6zruH51dW4tpkAhkkhz0TcJIj+DHj8KpSZDgiS6e9iOy8jkhftvTH6
4qjduxiUMwYbhj8xWn/aF/bW728sMv2aQYLQEOoHqFOdv4ZqqtjZ6iuLa7wynJXuPqOop8yJUGSW
c1pJEqzWhB7sASKS4ig3ZggDD02GmxWupacDtJmT1Q5/SpE1PecSAZHXjBFO6M3ForhCxz9mx/2z
zUoiTvbsD6iOrv2oYBSYH2cf1qN7gfxIv1XmgRiLv+1vsXJ3f3QaXUDPvhMsaINy9BjvTYnlF05i
2k7ucmrFxHJdMokiYAYPsaEVLdli6mtxZKDKm7B4D5/hNO0GaH+04cMMsU289+Kzp7U+XsSML7gU
uhRSR61YrgkCUZ46U0tSXselHPWk6kUdABQK6jIh0yf7FqNxbQMiKihgnlgE5ByCfy/A0st2qXb+
YPOQ2RMjHoFJyR+RqjaX7RSid3VdzBmeQ7igwRgY55NaPiSCZdDurvTrYOfsbKEYhSQenHrgnivP
na2h1q5zvgZEu9AtVeFSFVgrAjJ+Y/liumijWNDGmwIvGAo6+/61yvgzT3g0KKO7tnjlWRiEZQDj
IxnPIrpQZWwp38dzWj3EWATHGx3d+M4Ax3xTDcpGflBzkH5BxTGTDgSFQeAoI/zmlwQWwqk5yQRj
igQ4Xq4yzSF+oIGKYb3KeWMgeuKZI4VTkjB6ECqbFxHgbc4wCR1qbjJ5LgYfHyn/AGh1HFRPcEqF
4HH8I/KoHIPO/BHXFQuwB4JPtSuwsTS3MrbQX2hR0HSqsspa2u2J6ImP++xSSuMn5+R2NQtKi6ff
yyEqiIpYnsN49KeojC8ShJlQhBlhs3lc45B/lmuYuAjqEuOPLOBgYzjtWxqesxXcUkcC5i7SPwf+
AisGUhyznOX5pWJaEkfzJfMZidpKqOmasiU7TG2AinDsBhmz9KpROqt8ysFj4+mavWEUd3PkI+1R
1BzkUNISV3YltrRLgbIXjQk7R5hIHXg1ds7d9PRSTE/PD56/WrENku4mH5WKjJII/D/PrUtvaNsQ
MkZjXqXWovdG8YpER2pDkks5OVQZIbnsPXkVowW8kRZHlgYbAVaXkgnPHHt2PTFOt7G1TBZnnIXz
NkeQM9xggZ+v86UhY2AjckjJC7GG0HsTjr9Kh9jVaMrO6eWYo3EwXG4bhsDdTn6djW3pti17Itvb
WbF5sM7s+AuBxn1X61X0q0a7EVrFAXkLbW3JheP4iSP8iu/t7eHS7bybfByB5kmP9YR39h7VUYts
mc7EVjplrpEbeUN08gCyTY5PsPReOnepjKEjaVm2qorPlujCTG0gCY3eY55XPasbVNUza8AKseCR
uxuGRnNbOSirIws27szNZ1u71H51wqZKr6RqO2fU1WjvYirR3U8TMNpVc8r2zx3zmrMNws8+yHzI
5/KV9vBDe2T0JNZF4BLNHJ5HnxtITLE6Bdi8EkY71yttvUl77Gjb3DtuxGCEPJHYc8kdqjgMU7tC
yvt+8OfvEdPXFQ2k9zvMtrA0kS7x5chOduRwcHt6VVgzFdGcyMoJ3gOMbR1wfT0qUtSYxu7o1JLW
AxyKY5Y1mwMxvu5x6Yzj+VW4kNpxGBIFG4sFyfTgishZZWR1QtcpuHl8YZSScnr/AJFK/nIVUQyR
FZDk7dxAOe3p071aVjsSsb0M32Yxul8InfkoUBC+gyRx/wDXq1Zxk2lzflt7XG/YwGMgbcnHuWP5
VgwXRTG+OK4TaQEC54/3e3QV1MrpFp9vB08u1II27cEkE8Hkck9a1huZyfQ7ZBcLHgw8/WuT1+Yz
atZySRgRwxu7KGzkDqOK7ILITL58sZtiBsCoQy+uSTg/kKwfEUFvHej92q/8S+cgYxzjitTMjj1d
Tbo8dr8jKCMY4qvLqLSdYNo+vNbthaf8S20AtVK+QhyT1+Uc9KbdWESpvForN0woNVYVziNYniJE
IDbnXcTxgEHpWK1nbCWHz5A67kY/KcDJ5HvgVv8AiGHy9RgUwrFmBjgZ9TzzVe7tENzaoY8BkhyP
XOc0COfnH71EXJIXoBnAwKbiUcbX/wC+TXT2Wl293bLJIm5unA9qkfQIT/q4jn3zQByoMno//fJp
CXAOVYD/AHDXWxeHYFb97bt+JxS6lplvbabcyRxkFIyRlh/hQBS8Mqzo5RPMGByATiqdrFvv7wle
guCeOnAre8JyPEJShTBVchzj1rIspCt/qP3fmW5ByfUigDW0FLsWcZSRVhJbHyjPU+prSubi9twj
pLvjB/eZjGQPUYqDw/cGKwhR0BTLYKrkj5j1rfG11yr9e2KQXZTBZ7cStdxkMP7mf5EVympeXdx3
Dho0eGQqMAguB3/Gt25jFhMsDtvsp3wgOP3Tnt7Ke1Yn2eF7bUGEaZSR9pL8gdsDvTVmF2bFols9
vFiZSNg/jAOcehqwiRFCnmPns46j8qrWulQiOMv5KgoD1yTxUwSyi+65GOOI6Yh/kAHBvXyO20Z/
WlaMImBcuze/FQTzQybQZ3IXkfKBiq/2mVj+7jDr/eJxTAtNvx/x8ufaosc/Nlx7nOKF804JUVOq
o65ww9c0CIBIgHGQPpUbsCPlqyYod2SfwzSeXB1zg/WgCk4yP8ageI9xitIpD3qNo1I4waAMK702
K55ZTuA4cHBH41zmoaPJAd7A8dJ4h0+o7fhXdtEg7VXliXk4osNM87lOAFuhuX+GaMfzpJZZjGoc
/bIB0bPI/H/Guq1DQ4pwzQARSHk/3W+o/wAK5i602ewkDgmBj0I5Rv8APvUNGikRWzurf6DcEHvB
J/gf6VI8tldHZfQm0l/56IMof6ioGlhkwL2HymzxMg4z/SnOk6JuG29g7Nnn86hotMme1vII8wvH
eWx6And+tUo50gl3QyS6fN3B5Q/XtSwY35srhrebvGxwT/Q1bfUE/wBTq9ln/ptD1/Ef4GlqVoPG
qMVC6haCWM/8toOQfw/wqM6dZXh8zTrnBHPynBH1FCaYkimbSLwFT1QHp9Qf61mzLJDOXurd0cDA
kgBUj3xS0HdrfUvLcanprc7nUdSv+HSrK6tZagVW5hXzB0cfK6/TvVa21S6C8NHqEQ6q3yyD/PvT
pG0rUvkINvMT9yUbTn2PenqPR7GxB9ujXdZXyXaj/ljOcOPo3+IqR9RtpCItUs3t36bpVwPwccfr
WD/Z+o2B3QS+ag6B+fyNW4vE0qgRXsWF6ESjKn8f8aLiafU2G0iB132t2QDyFk+YH6EVTmjvLVSZ
EfaP4ozkUkEdjN+8srmTT5D/AAoQYz+HSrwn1CzjLTxC8Ts9ocN9Sh6/gaaZDimcqZHaTdEeQx5B
rSW8mRAJAx4rRjfSNTcqnlibuhHlyA+4NOk0hl4hlIP92QVSZnKD6GQWa4b5W2Z9WNaei2M6alay
NKCqvkjPWoZftVmQs0TKOzKMqfxq1pFz5uo24yp+ft16Va3MmmkdkevSjb+tHYUuea6TMyxaRhWj
bayH7y7eTVtMqqKrFdq7QAScVEsUuflbOT35xVm3tbidtiuC46KWVc/nXCdYoyQC7ucH8/XNHmYK
svBwc8flRLDNbzGKWQOQPuxEsQfcgYH61Jsfbh4xlfX1+vemITdvJZ1ZWOePT8aY5RRgR8eg6U8K
WyVVgPpUcikAsEOPrj8aYiEzLuBCl1zjOOR61FNdxxoWb7o5JPaniwknXL/KuMoVO7PuTxStp77c
yMhO3gDvRYCoxUHkDk5BFVWvCxxHEQc4woySK6nR/B91qaiWV/s8JP3iOSP9kf1rov8AhA9JETRL
blQ67XYOwZvxB/SqUWyW0jxi91cwSyKtsJXGSGdwBgfTkgfhTdLmub3QdaadsuwGMHgDOcDHSvX2
+Gnh54/LexJGMH94/P61HB8NdHtIri3tlaK3uBh4skgj6k5o5JD5kfOclnLkqImbB4PPP4GpILKZ
QBhWc9gccHtX0L/wqzwx8oNlM5Xpm4kOP14qT/hWvhWAKXsWHcKJn/xo5JCujwOz0hJQPMcBC3Pf
n6Vpw2iW6qYV3ZO0sRgfjXQ+NrfT9O12SxtFEMYjRljzkjPUgms6MQRb0EaZ4KsSSTx6mud3uax8
hgQmIgwnaFLZCk4P4cCnxzwGVpbe1lSLyjkBMA4IPr1xkVYuJpjKoCGRDwqqD29/T/ClS9uYZXSF
eXG3bjcTnqOnU1DRotdCEXEbRNC0yxqMMoKdGxjH1+vpV+zN000drB/pGSAnyHAOeAccc9O/X8az
orZpRIUiCRr+8DMQBu67a2PBd60+ryeW+wC3bcinpyoz+R/nTUL6Cbsjs7e1Wwt2XcJJ3x5suc5P
XAPpn9ap3t3HDEGlb5ShYD1xjj9RU93dJBE0jkLGgJYk4FcTqWpfbdQfzTGIEGFxyASRjPvxWzai
rIyScndmhcXsl0ASuzAwNo4Hb8ehrLvxFJHFbuAc5BAPDgkDP6VZMsjBYo5Y84O5cDJHb8Kr3Aln
kjHlFYo0B8zqcevp7VlqWQTaTDOH3iVhLIu9s8AL3/8A1VLPBFAwa0dt6nKqsW7cewPpT5L8cy/K
YlCkgHp1GPcn+h4qkPtQMsnlqwEmDIHAxngcE55FQ0wsx8szTYN1CY7p12o0eNoA747dO9RyyRz5
jM6sCoRQxyrcf4/zp7LceY813OduBsUR4UHnODU8FhHPeWsUSj5iT5pxnA6nGf5UlEcYW1ZWtWns
mCpIoKkktGuSMDBA6AU+SWZIwJGMDliQCCCQep989uKnNrIAqyOkLRtg7CUIHf6jPvmlcRRSbbjD
qhJaVnZpHzzuPTB4H/16G09irqXulq0y4VLiQjLj54yVPvzj0rZvlzZed2YMBzzxt/qTVLSP390W
di6W8Ty7iwYHjGBx0+Yc4q5fOf7NijK7dsTH8SQa1pRa1MpKzsd6YlmgeOSUncepwf0xisHxAQ1y
SrbsafNznNWRfYHI/SsXVb+MXgMoyjWzpsHViTjFdFiDp7B5f7PtAblcCFOCD/dHvRdyO4XyrhkK
nnaxGaw4r5lt41AC7VAAz7VHLqLnj5eKYjK8TsRrVsrTvK32VySxzj5jxS3jxDUdPyWIItQct/vZ
qpqY8+6W8kY7o0KADpgmsrUNRRJ4nOXZPL2qOpIzQB12haxpVhZRpcXawz5yymTbkdq0m8T6OT8u
oRMP+ug/xrhftU42hBYFSoOJ3AYcU4XNxnlNL/7+j/CizC6O4j8TaUjE/wBoRFSOPnHFU9d8QaXe
aNeW0F1HJK8RCKr5JNcuLuUDmPTP+/lJLeS7cqumgj+62TRZhdG54PngVXaQcsFCkduuax9LmU6h
qzHOClzj8WXFR6RcNbQlQec44Oarsf7PlkYRl47gMGfOSrMf5UAdvocqjRYFDFW+Y/8AjxrQMwPc
1yOm3uy0jUHpn+Zq4t7yeoz3osI27mKO5jMcoLKeoJrmI7lorDUbZiQDJJsJx8/OD+PT860ftbYy
DmsS9uFS3mt7iPZljJDIvRj6H3/nSsB0kNxK9vGHt45lCjnB9KsRPE21mglTsVAz/Ks+x1RJIFVk
2PHhXTdwOOv0NWPPhflYw59FGf6UIB9w5eQbbdvKHp1P506J0iOEtXAPXJGP51Dvy+SjKAMAMpGK
GljGMlR9eKpAWWuokba6MoPQ4yKR3iYDaPyqtvU/ddckevFVTqMaH5gc+gBNMRpExYGSpamkxgfc
U/iKzWvklHCZH+0QKT7UP+eY+oegDQMiD+AD8jUZkVhnC4rPN8iv8yEA/wB05/SrPmEoDjj06UWA
STDHKjb/ACqLAPUqKeNwwQM57Go2JBzsA7HFFgGPGvr+lVJrSKZGWRQynqCKuFzgDFNbB7ACnYDm
L3w4pBa2IA/55yH5fwPaufmtLmynIiL20p6xkcN/Q16BJHu6H8aoXFmLhCkiLIp6gjNS4lKVjiWl
gmOzUIPIbtKoyp/wqR4Lu3QNE63lv2DHPHsa173SpEViq+fEB9xvvD6Hv+P51jJbSQsz6fMyEH54
XH81P86yasaqVyFFtJ5AYpHs7kdAx2/ke9Wm1DUbYiO9gW8i6ZxhwPXNKl1YXn7jUoBaSngSYzGf
8KfNb3WiDfBJHd27jiN/mBHse1TYsrm207UG32crQz/882+Vh/j+FQzQ3VuMXkAuo/72MN+dSKNM
1VggP2O5P8Ehxk+zdKsg6vpPyzx/a7b0k649jQMrWVzJEdunXpHrbXPT8P8A6xq82p20v7rVLRrV
j/y0A3Rn8e341CIdK1gkRt9nuP8AnlL8pz7HvUFxa6lpw2kGeEfwSc/rS33GrrYtyaGCvnaXc7s8
jy2yD/Sq0Wr6npT7ZomwP4o/6iqUM8Al3W8sum3B9DhT/StMaxcwrt1K0W7i/wCe0I5/KnYLp7lh
tX0/WkC3kKOw6Ogw4/qKuWyXcaAadqwuEH/LC6G7A9M9RWX/AGbpesDfZTr5v93O1h+HWqklrqml
tkfvkH97g/gaNhOPVanTpr32Y+XqEElof74/eRH8RyPxFX9Ot7C4uobu3EbMGyJIW46d8Vy1p4lT
aIrsYPQpcDI/76/xpumavp//AAktqlpYeTI0pVmim4b5T/DjBFXG9yJ25WemZ4FIfuk1AJ0cY3YP
oeDTnkKxt3+U12HGTC2hZQGLAe/BH5Uscax5Cr16HJJ981LHuDH92AvYhsk/hinbVYYKtnPWuA6h
oZI1yqHA5wKUOpOQSAeuTSFMHG47cUFVIPHencByvEybFbHoApxQdqKuOWxg8/401Ymblgwwex/w
rb03wpNeYlkC28Z5BK7nP4dqau9hOyMq2tLi6nWK2hLnHK9APx9K6zSvC8FptmuAks46DHyr9PWt
uzsYLKERRRqg74HU+tWeB2rVRtuQ3fYhWMDryfenHB4yB+NPwD2o2gdqu5NhgQY6/rTtv93BNOCA
9cVVuLpYgVjxx1bHT6e9JsLD5p0thkkF/Ssp5GuWaSRjtHT3/wABUrI2UeTuSdp/rSC3NwcFSIyD
kg4oA8h8TSfa/EN5KCFgQCPeqgkEDBPPXmqMcNvPD5JKuwXgE7SemfmPHvXtsWiaUi7Rp1tjqcxA
/wA6kGj6YOmnWv8A34X/AArL2TZamkeAyaUUc7ZgykgeWXBAGO59PxoNlduXKyRxof4EyoVc8cem
a+g/sVmoA+yQAD/pkv8AhUcelaci7UsbcDngRL3/AApexfcr2vkfPk8LpAoIKMyn52PX3UjH61d8
BWxtdYvFaMqxtycsOT8y17yLHTraMv8AZbdQBgARL+XSvMvE988Pii6aOOOJU0oFAFAAJkIAHtnF
ChydROfMZPiTUm4tocYQ4kY9Px9q5iFmjfzBlxjYCWKnbgjIJ6kZNSLDPdAx3Upjlzu5yFkyc/5+
tOaGVQ7GRl2joIznkZ5GcgEA1g9WbqyVirZXTGTynuCrKcqzjOAR0z6fyq7MpIExlPlSsCCiFgQD
jj3rJOnkyu6s7qrANtOz+dbEM4UGGVATkAK7ck44+v1ptiURqW8c7tFGJAkf+rVQcE+546nOatQW
bzW5yHJzhccZbv65HPFO0fy3hlUSBnTJAk+Qflg+tdLpmo3qQwxDTdNbbkZlhGSPXgZ9etCg5Dck
jj1tWjU+Ys7b/n3yLk9cYwe1W4NsYQq84jDNiJuN30z2x71q6/qCmeOUW9is8aBhEqAZU57Ec9Pw
rDe+aCMl4ncv/q0QkYznJwe3Hak00NNNCxJbzq0c0VxAF5jBBZnPTGeeParw0cL5r+Y6W5KJuMik
INw55yTgj0qhdajCBLFcxFty4ZEUgkjoOuMcevNOWWTzN+9h8oLBjncAPugYHb0xSW+oehs6FbxR
Wd9bJeiWSRhEqbiTtLcn27cf/WrS1u28m0Vh0ZGHTH92pfCsMbRRTJbeRG7tIcrjeQMcZ5wNw6k1
oeLiTZwcD+PGB/u1vEwluXhZxnqmDVafSrSSZZfIjaVR8pJ6V1PnEHGAv1Bqu4JfzCFPsK1IOZex
VuCmGHX5qy7wCFseRI2TjdjgV28iFhhdpPuKxL6S9s3+ZVkjI4YoAM+nFFxHIXqK8JXBUnjKv3/K
qL21nHOhkgZpNvDbs121iyX8xjmt4s4yMRg1Zn0Wzzg20f8A3ximI883WyrtlsUkbP3jNj+lN8+x
Bx/ZY/Cf/wCtXdyaHY44tkz7Ln+dVZNKsU4eGHPYeV/9ai4HIG7sY+f7NH/f7P8ASpBe25ICaauD
yMy//WropbeztmIOnMwHdYARUUtxpiDcsCt2b92AR+dDYGda23m75TGkKnGEDbsVLJaLJHtOQrcE
jA/LrV6K401iCLb65jH+NNmNk5zHGyN/sqAKQyksX2WIKkO8L3Zxn9KYL0bTi2Ofrxmr6Q5/1W/6
HFTJFMODwPY0AV7aYFU3Q5B+9gnitH7JaXKbQEI/ulv8aj8jH8RH1NNhh+07sqqMhxk5/pQAzVdI
cotxbAiSMfMoP+sX0+tW7K5nWFdhSeMAfd+UinRW8iAiSbeOw24qmIzpd3vSNDbXDAPk48tugI9A
anbURotq0SHbLHLGfcUhFnqA4k3j0DYxUz2s7cLBHjuSQ36cUw24QZePaPUQjH6VQyr9htIj8jFS
PRqjeKHO4OSR3zV0IEIKBSp6YUYNRy56kIv/AAEUAUvlHCsT+H/1qge3Rm3Mu7/exipZTHyFl5Jz
xUBtbp+VkOD0/d0AMChCfLAx/s1Ol2FHzQI/6GmDTL1h/reR2AH+NV3tLpCQ5Ye+ygRqpdWjoOEQ
+hpwNueVaL9K5+S3uPqfWoCt4hGNvHvTuB048ljwYj7DFV5oEPKMoPpmsaF7oMG2KGz/AA1sW4up
SGlijC9yRhqdwKjI5yNpP0FRshH3latZoMHOAT7mq8gZDyvHrimIypIN3ADZNZ15pCXH+siO8dHX
hh9CK6LCtnAph+XoADSGcLeaRdRq3mwNcQj+JV+cD3Hf8KxPKntm32E+5P4ozyo9iD0r06QE/j6V
g6r4divmM8bvb3IHEqAc/UY5FQ49i1LuciZ7K8/dXsP2WU/xfwH8e1WoptU0ZcRSC7tD/wAspTuX
Hse1Nv4JbIiLVrcBTwtzEMqfqOoqNLW5sohNp9wssDc+WTuRv8KzsbJ3LW7R9bbaP9Buz/yyl+6T
7Hp/KlK6xoh2OPtUHTZJzx7N1FUXksL/APd3Uf2KfsT9w/j/AI1YiuNX0ZdiP9rtMf6qXkY9j1FK
wybzdH1j93J/odx/dl4BPselVp9IvtNJNvIWj/u9VP4VIP7J1n5N32S6P/LObgH6HoaYYtW0RtsM
heIf8s5PmX8Kke5QaW3dx9qga3kHSWPOAf5ita21HUbaMFXj1O29GPzj8f8AGmDUNOv8JdRG0mPH
zfcP41HNoc9qfPtJCmeQ0Z4NO4JdUXRPomqny5CbSfvHMMH8D0NVdPsbLTvE+npGytK0vQfwjB/W
qcl3vHl6lZrKB0ljGCD9Kdon2MeI7DyNzkycM3bg1cVqRUk+VpnqRRWBBANQTBkhfa38J4bntVkD
IzUFyMQSk/3D/Kus40bZAUnZ+YpTul+8SF6HPFRjBOAxYk9uKesRYqqBnY9FHU1wnWJLEMkKVY9C
B/jU9np73hKRRlgh5YHAH41r6f4bZ9sl0GVTz5ajn8TXS21pDAoCrsA4AAxVqF9yXIpaXo9pYKrO
plmx95hwPoK1d6Z+VDn60g2g9Tn6UuQfX8q2VjNi7xjG0ilD896ZkDgAn6igbs4CnFMRIH7DNDSR
xKXkcKo7moJ7qO1Xc557L3NZUk0uoy8ABFP4L/iaTAvXF4ZV2xZCsOPVv8BUUUQTlyHYH8BxTkiW
EADr3J6mrVra5cySfxHIX0oGC2vnsruCFXkL61bEIKgjIz6DBqVVA5zSlgO9MQnlgdh+VNMfoBT9
xNBNMCLaD1QflQwSNC7KAo6k1IMAFm4ArEv7t72YQRcRK3zH2pMBsrG8laQDbCvAHrXm/i/Tp9T8
QTG2hklVYEik8tC2CGLAcfUV6gkQbESjAxg47VcihEa7UwPeplHmVhp2dzxWLwxrEsQSPSroqGyN
1vjnp3xj+tOTwj4hV1D6RIUySWRVRvUc9/8A69e1YPqMe1OKjuahUV3K9ozw2bwtrts0jNpc7wOT
uDJyc9MFeRg4NV4vCOuZ2LpF0i5yrtBgtxzkjk89695AA9KcgxlulL2K7h7WR87azpup6dIHvI7u
0dl2DG5DIR3z0PqapxwPJEGk1G9IPJ23LHPqBiu/+KeqMbzTHAYoJHVCvbG3n8a4SOVJpWXzFKDO
VRev0/KsXeDtc0T5tWW5GzDFG7idFQbS7ZcLwQcnrz688GqV3YG9i8uCykuWLkuFDMUHcDtjNLBd
RgMjQuxU42oSTuzkE+xBqMXUwm/0e6ns2J2tg4OB7d/51L3LRMtqLeJI5kUPLwxkTo3fj8e9WDdO
xEcpjCxrgeblwfwzuxVDzbmZpM3TTykcNKc7x3xn0qvdzOLdt0jR4yrqMjcPXPPrnFC1Bs9S8KXM
cthBJKyNtiYbgp6mRscHPO1VqXxhLC9lbhM5BfP5Ck8H2KPocBXKghcKB0+Uf40vjG2MNpbggjJc
cjGeBXQlYwbOrW5tcYIOO+VqmVAkcxt8rHIGMY9qma2RdoLsCxwvyk5NNMQVigYnHXPFaCIZN0YB
kbAPvWdNdWlwzQNucockN0FaphX/AAyKpz6ck53/ACq4/iQYP/16BGas1hE29ImBU/eA/wDr05tZ
syT88hb2BqZ9PtAcSSDPdS4FR/Y9OHCiDI9SKQFG41lV5jSRj6u2KhTXFPDxMD6hs/zrV/s6zcY2
Rn6H/wCvUE2mWCNjaOmc7sUAV21W3dc4cn04FVjPZStlrTLnuVHNXBYWAGWIH1kpFtdPXJ81fbL9
KYFWKC3mXfFYZBPUHH9akktG2Yjstp7MDkiryLYI7OjRDdyQGzTvNhDZVwAfTNAGbHBNuANsw9yK
tFY3Xa5I9gD/AIVY86EZbcxP+ypNKrxORvlMYIBHmLikBR+zpHnbJx6PHu/pTTOy5H2iIY6jYQa1
TbxOuRKrA9waY1lCSC/lnH94UwM8STFfuq30DD+lHNwjRzRMFYYIYggirixwO5CXCnHQVL9lXjE6
GgDN07UXtLr+zrtyQwLW8p/iUdQT6itNtQteVQmVh/cBP61UvtKF1bmIsA3VHA+6fWsrTrh4g9o5
2XcJxJCOc+jD2P1qdgL880jbjHaFN3JO7kn6VVcPMpaU7Qv8O3NTmS8x9yID3NVZBOW3NMi+oApg
WIfNkj/cICPULgfqaVrTUSOGUD8BVWOf7Lny5Tj0pX8QNF94g+5WmIn+z6sOksXtwM/yqKaPVduG
njX6YBqq/ik44Cn04pn9sfakyJBjuNoypoAJJNQtfmacMvocGpodRZ3AkjibPQ46/nVFpITkkkn3
NR/aogMbcj3oA6VFLgABUz/s1JHYhs7p1T0+U81y6ak0PCSOoHYGnHWZmOftD/nTuB0Elmc5Dmq0
lswP3j+VYUmrTnOJ5Pzqq+rXi5KzuV7jJ4p3A3p3ltgGVAyg/NnjApYpUul3JIjZHYdK5l9Smm4k
ZmH1NJHdeWwaLKEdCtIR1DQsBhahaJxkE5FZ1vq0hYCaVyvsBWrGyyKdsvmD1BBxTAz7ixabO4Rk
A5GUzWDd+FERmn0+Y2kxOWjAzE/1WutZD68fWqcsU65Ifcv05oa7jTOAvoVRvI1S3+zSHhZBzG/0
Pb8arCC+03/j2k82H/nk/K/h6fhXcXFsbmNklTzYyMFWAxXOXGjXOnktpzfJ3tpTlD/untWbh2NF
PuZG6w1L91Kv2Wc/wv0J9jUsdxqui/IpF1bf88pecfQ9RRItnfMbeeJrS6HBil4z9D0NRY1HSvlX
9/B/zzk5wPY9qzsa3vqW0uNJ1fCY+x3B6pJwCfY9Kj+yX+kufs0rKnXYeUP4VAsdhq3yIfJnP/LJ
+D+HrTlfVNIO0Zng/wCecnP5HqKmxRaXU7O7xHfwfZpDx5q8p/8AWosobG18Q6fHA4nkaT76ngcH
pT7e40nVfkc/ZLg/wS8An2PSmWmn22meIrCMyB7hpfur0UYPWnHcmesWekI3AqC8/wCPeb/cP8qm
XgD6VDeN/o8xz/ARXacR0Wm6TNqMg8pSsYPMjDgf412OnaPbaeNyDfJ3kYc/h6VciijiXCAADoBx
ipcqOuKwjBI2cmxMgd6UjNHXoM/hS7GPUCqEIFx2FKM+1PEZHVgKUIB/H+lAhoUnrVS8v47UbF+a
T09PrVwrkY3N09aqf2XaE8oSc55Y80agY7K90/myMdv8/p7VoRYVAqJjsqirhsrfGOfzp0cMSHcv
XpzQA2CBs75ME5yParQUjGMfiaZ5nof0pd7dSf0pgTgHHOPwpOnaofNcnIb5cdMUod+7UXAkyT0x
TlGTk1Fvb14oZtylTnBHOKAM7U9REjmzt2XdjJ57f4VVjTy0CR/Mx6k9/U1oLpllFK8qQ4kcAMxY
nIHSnGOCM/KnzHikAkDrGgAyT3NTifj/AOtUOMHjFPxj2qkIeSrcn+VI2zuf0pFXPvSYGeCKLhYc
rruwOfwqDVbvyrcxw8zScKKmA25IxUbQxSSb2QM3TJpMZ5x4s0u/1S+t7eytfPSFMuzAbQSR6/TN
Y0Xw/wBZV2c28IB/gWVQtexC2t/7q04xQgEBVNZumm7spTa0R4vJ4D18yPi2h2EfJiVRg9/6kU24
+GuoSFXjsQWUc7pwGJ9c5x/k17OEiHSMCgxxk/d/Sl7GI/aSPHLT4da2ysJYo1LDCv5q7x7Ej+dU
fE/gTUtFsI725uom/eCJUVizcgncSR1GO1e5gRg/dH5VBe6fZajGIry2iuYwdwWVAwB9eaPZRWwu
ds5Pw3iDTYgNxG4nn64qr40lEltZAbvvuMEf7NdrFp9nEoSOCJUHRVUACkn06zuAomtYpQpyu9Ac
fSqUWK5AZYkUKWAyP4jzVJym9iJAwJzz2rZ+yQEYKRj8KU2UGAQin6AVVhXMLd6fN9Ka2RlWUjFb
v2eNf+WYx/u0vkxkcxr+VFgOXvtItpdryjDMMhkPNVBpEajAuBj3QV2ZigzzGh9iopDb2/8ADDEP
oopWGcHJZW7OVa8VSD3iIpWsVlRNgik2gjcvH867praHHMSf9803yIf+eUf/AHzRyhc4GSyEOCU4
9lz/ACFNWIgrg5z0wp/wr0GAW/2hoDAm7YHB2jkZx/n61a8i3H/LCP8A75FFgPO1Up14x2IOT9Kk
RyOnA+mK9A8iButvH+Kim/ZLU/8ALrB/37FFgODa7ij4klCfUGp4biCdAFlRx7V232W0H/LtAP8A
tmP8KPIgH3YYh9EFFgOEl0+1YlgoyfTNVJNLRmBWQr+tejeTH/zyj/75FL5cQ/5ZoP8AgIp2A84T
SgCAHDH6YoNkg5G3Prk16PtjH/LNP++RRsj/ALi/98iiwHm0RvIpCDKfKHvn+dVtaDOFvbMbb2EY
G9eJF7qT/KvU9keP9Wn/AHyKTy0/uJ+VJxuB5dHdxXNotx0zwwGeD3FVLieFSQWJPqATXrghj7Ig
/wCAigwxnsv5CjlYHiU9zbg4y/4IahkshcRLLG4ZGyMgHg+hr3AxR/3F/IUCKMfwqPoBTsI8Ak02
RTw36UQ2U8b748kj/ZODXvxjjH8AP4U1oUYfKdpHQ0WEeHm3kcZEMwPcBCeaQ2U7Di3myP8Apma9
q3EMUbhhRlvenygeLf2bct/y63Gf+uRpj6ZfKCV0+6fHZYW/wr2wMfX9aCxo5QueILp2puONIvfx
hb/Cpk0rUyc/2VdjHrE3+Fe05NNLEc5GKfKK540uiakz/LpFz7/umA/lV+28PXq487TJCD32tkV6
qfWmsx9fzo5QuecJosqkbdKkyP8AYNTrpmpRt8mluAeuErvGPrTAxU5HSnYDiDpWqt002QfhTDou
sE/8g5vzH+Nd+k4bg8H0p2adguebyeHNYkB/0Aj2yOf1qrJ4Q1mRg32NxjtvXB+vNepZ9v0pDRyi
ueQan8PNR1SExS6YMj7r+YuV+nNY0fw88aWLiOOzS+tfSSdFdR9Sa92+YZypxSVLgmUptbHht18K
9cuVDCxSNzzgzJkH8DT7PwD40t8RTWtvdwf9NLlQy/Q/417axHrTC2OppeyRXtZHjl58KtVul3Jb
xRuexlHFQaZ8KNfs9Utr1xCVikyQZhwMGvaDJ7j86YZUz94fnQqSQnUctzkx4a1HgbYv++6iuPCu
oyQun7oFhgfP/wDWrrzPGOsi/wDfQpDcRc/vU/76FaWMyNPGeluN224A6cpipF8Y6YuAIrk+n7sf
41xoOQewzjpimmIEgnd16Z6CuX2j7HTyo7UeNtNZgohuyT6Rjj6804eNNM6CO5J/3B/jXE7VBwCV
x39abBAcsSRJz0VQpo9oxcqOzHjfTj/yxuv++F/xp3/CZ6d/FFcD2KLn+dcakIDZBIUnHTmnkLhi
rA84BI5+lHtGHKjsB4007H+ouiPXYMfzpD420zg+Rdc8/dX/ABrjXZgvykDIwT3NLgCIMw5zjbzk
j8qftGHKjsR41008iC5I9lH+NL/wmmnHgW919dgx/OuKUAMOOQcjd+opjAIzyMzddpIzg/40e0Yu
VHbjxnpxJIiuWP8Aur/8VR/wmtgTgW10f+Ar/jXFRw5jJyxbrxwetSiFtxywYkcAtk5zS9ox8qOw
/wCE309cZt7gZ9do/rTR45sHGVtLgj1+X/GuUaBcFSmMdieme9NYJ0GAAcZX09arnYuVHWt45tEO
PsVwcehX/GmL46tnOBYXOOecr/jXJvjzPLiQu2fvKOMfWpCVBUFTzwRnPNLndw5UdTJ41hTG7Trh
fXc6jFMTxpasSfsU28HGwOufr9K5mZxLgOm3vjP6c1GdqFf3e3pg46A9v0pOch8qOpbxtD1XTrgg
/wDTRKP+E4QcDTZs9/3i1zRkjAAL/MCBwn9afhYgTktz1AIp+0YcqOg/4TtM/wDIKueen7xRSL42
V2ONNkU+jSrnNYCuqqcKWBIyvXNL50f8Q2heDge1HOw5Ubo8bh+mmyHtxL/9alHjM4ZvsBXb1zLy
f0rmzewKwAG7aDvzgVF9ojdggwM9cHJ/IdvejnYuVHWf8JjgD/QXf1xJ0H5VC/jdh8v2BgcZ/wBb
/wDY1gPIVGFRimDnjBpscoLbhy237gPTn8OaOeQcqOgj8cPJytjx7zY/9lpf+E0m3Y/s7tnmbp/4
7WHGMnP7sjGeTx7U0li20MMDv0FPnYcqOgHjOdiw/s5RjnLT8fypv/CaStHv+wJt55Epx/6DXPoA
SWAyRkH0pqgeWPlJUn7vXpRzsOVHRL40mA3f2em3Gf8AWn/Ck/4TS6ZgP7PiTPfzTx/47WDgMQrR
Mpbpnj9acRblX3kR5x1PJOe/86OZhZG2/jW7BINhECOP9af8Kanjm9/58IwM/wDPQkfyrELW0q/u
5F24GGQZyPWo3ZDGVB2tj5uff0/OjmYWRvt44vGJCWEJx1/eH/CmjxtenpZwD38w/wCFYJa3BGJQ
CegIBI9aD5XILcZwcClzsfKjdbxnd54s4D9XINOj8a3RZf8AQYcN33sawY4/LYHaQCvQjj86b5cY
BZ2PPbt/npRzMVkdA/jO9/584R1xy1IfFt6SALWE5HXLVihVC7mfaR0B5H41GwijydxHOOO/40+Z
hZG8fFl6oDxwW4OOQSxP0xmmt4y1Hr5FtjoeGJ/nWA0hU7o9hccjrkH359akEikZ2hQc9ADz/wDr
pczCxtt4w1EAHyrfp2Vsfzpp8Y6kpXMVt8x6YP8AjXO7i6FSQpA4IODmnGPaMiV3B54UNgen1xRz
MdkdAfGGp9RHb+/yt/jTT4x1PdgR2/sNjZ/9CrFBwqqd5J7FcH8P8aiQlyfToC39KOZisjfPi/Vg
R8tsM+qN/wDFUn/CY6o2P+PcH/rmef8Ax6sfZPGnygyggN69OetR723AxjGOCQP8KfMwsjb/AOEw
1XqRAMekZ/8AiqG8X6uBkG3z6GIj+tYrB/LJJG4AZOBj86arNKCC4XOMA449aOZhZG0fGGsjHNuc
+kfT9aQ+MNYYgCaBc9zDgD9ay225IUbyBhcjk5/zmmYOdwXGOOBxn8KOZhZGqPF+skf66368ARg/
1ph8Ya4vPnW4we8XX9aypblYlAkwpHUkD9cmog3mfOOhHO4jk96OZhY2pPGerrCJHuIQScBEt8n6
nmk/4S7WWAK3MLAj/nhgg++ayVdQwIRTxhSRnPvTcyKSp+XHP/1qOZhZGr/wlOvsOLqEegMApg8V
eICpLXMHXjEI5rOyR1YZ6YPpTVcg8BVwO3+f1o5mFkah8Uay4BaaIY5BEIzTZPFesKFP2uPBPP7k
dKzWdjk43cYGW/OjcD2IOeg6UczHZGhL4u1GGPzJLxUX+8Y14pI/FmpSx71vFZT/ABKq4P6VnTxR
uuHTeCOBgHNAWKJBtjWOM8gKCAKOZisjSPiHV3OBenB6cKP6VGde1bI/058e2P8ACqIbABUDAOAR
/Sk6AnAAzjgmjmfcdkWn17VFDFtQnGOhBH+FVx4nvpPmW/udmccnDMfpimBweBuAz8xJ7UN5ZBYj
A9uaOZ9xWRZTWdRkjDi+uMHvuOaDqupFSRqExI7GSqzPHtBK8j1poUuASPqB0/OjmfcLInbU78hl
N/cc8AiQimf2heMB/p9yMnkec2ag2gZznnrnij7w+cDGOKOZ9wsiU3t63H2u4Pf/AFrc0hurs8/a
pm/7atUBIG7nJz1p+wAgnpnOT2FHM+4WQ1ri4Ix505OM58xsfzpjSTPlfPlBbOcSN+nNPZW3HGce
tOyw4IGMcFqOZhZFYRyKm3zZZOfvNIc07yMDmVvrvOalyUPJBPUikLZbH3QO4Io5mFiExElj5kjA
9MNTJI2ZuSRntVrC7eoPPIzimmSI5BHP5ii7CxRaOMcEP79xTATt2kdunXH0NXcBzg5UY796YYjn
5GVs8YNF2B0scYjQA58peN7c8/jzTUnh/wBWp3ux4x1p/Bj5B24OMnikMkYQERqGGMbeh+tZFkmV
QbnwM9gvSmn5RuwWHGc/z/WgBmJbBYjB29dtNBIO7DEkZBzypFMQwMxDBuQG6YwaaY0xwpAPYEc+
1SSFmT5tpbOSSvtTAWT5kHGOhFKwx4jDEtwp9DSFCGG1xg8Hk5z/AJ9alVmZQSvIHTHU06PJTc0S
RbjjaCR/LFFgK+2Q7mCEqTgM3PPvSKsu4BguO20kA/jUzzyqGxyoGQQc5H0pYFaQdNp6/MMc07CG
SW/mN80ZTGcyb+PxpkdgsTqfOc9sk5x7/SnFGZd2xlxwBn7wNWEQqu9hnKjBbH+RRa+oEciEF1Ln
cTlnA/zj6UzzA7BdpBBydq9u+DUkkLS5UpuG7DDptppREj5i2gZUkkYPpijUCGQmPdlWky3ygY6+
1WDvkUMIjFhRw2CW+uCah84hcENx1IXsOlCEAqwOADk57c0wJFjkx8oQLnPP88Ujq7/NvwBgHI4A
/pTAWJYFvu85/wD1dalRmbcrSDdyCADgDNICJoypcgsMcgA8UmyVDvUFlOAVGCR+NWZYyo++vAOP
f2qFXeMmIAncDgj+X0pgO8lky2FJHJBbFOkQqFSTaSV5AIFV1l28AH0xkjafX69Kk82Rh5fJOMkg
D6/rxT0ERGONX2rBgdRzjmkjjVW+RCTjJAwD/wDqq28iyP5ZU4HOG4x/n+lQFWYZigVcZGTzu4pA
NWGN2G5WLfXOc+v+e1OaOONy5dQAvzHaeKfuALMAwP3cZABHqKQsSAp25J4z1zmgYxNhwxd15x0w
P1p77dwG3IJxn1/wqNoWDpKiBWYH24pvluoDk44IwR+vWmIsRKckJI0oPRfQ+lQmRBgGfYQDkYya
b5buqrvJPXHtUgwGC7A27sw/GkMh3PKoxI+DzwMYzUawzO5c+XgH7xOM+xqy+7zAJFCKeSAPaolc
AEpy3P8AFjGfWmIIo1hyqIWYt0LDA/zzUuUP3EYsByFIOf8A9VRgBSCARgd2puTkgrnnp6+9K4yU
xiRf3kYBIznIBIpWQQjORjtuIP15qMlArA5H0GaUbVG5Mr79R+VADlc+WvIyMg4GP89Kjw00hOdg
blUB3Y9s/lTcoFwBlSTxThGJCFbacj7npTETeU6rvDBB/tdxxxUB2KRzu6ktkkE1KskkYIHynHHu
Pc0xAuwloznPVcHNACYV/nC44wVwR+XPelI34zGSccAEHA9+9IGCPlA4GDle1P3qTwpBI2nNAEaw
GR/9VnB6U8O0bABACM/Me9RMCGGCM9QQBn6U7fJyC+XB+72oAkPDNIy7nAIBBzjOPX+VNViWYhSS
PTofcCojwNyEZHOOgxUiKc5LkFuSe49qAHITHym4Pw/yg8H8KjLx5JdmJzllzyf8KeJm3FVc9ex/
wpx9WwSBkJ1x+NAEcmx125JB6/1qHyBENyRbVA6d6mGFQKmBuPJJzt9Ka7EsNkilNp3A56+o596G
gI8FSXKkBvl6HHNKzhSBnPUAD+dObd93JbjgkU1Ud2DMR7A9/wD61AFYR4A6sCc5/PHX8qkKYA3F
eBlSQe9SsHJ4QjJwTng0m9kOZDg9R/k0hjN4Vtwl+76L0+tBnIHmRuCemNmN2e//ANepm6jf1I6K
PypiK52qXBb6YzTuIr/aJPkd4WVmOGVmwR2z6HpUgkUbk2vgHIYeh7Zp5h3MxHQcHn360oHJII3Z
7etFwIzh1IVCp5z/AFpgkMYwICc92bj8amKjbjYCe2OlN8skk7uvQZ5NAFeaW8RCFtojx94uf896
USTFRvig92XJI/OpjH2ZsY/hA5/OmhAQeeAegbrQAwtKpVsRuinJTa3P4g0oVxuIPJHZcY/zmpFi
djlQNoGM9PwpuHySDz+dAxrB8FRlQeTn0zTF8xW25yvK5Hf61I0iFxEGQMecHrjFG0bjwCTwcUAM
AdT+8xgj5Rjp+tO3sWyucYAzjrSkbSSGI9RikYKU4BYnnkUCGk8fe6nPTkf5zRubPGM9OF5pGHQK
SQQMk9aH2/6xSyt7HpRcBQ25uGA9sdf1pQ6Drhyf1pkbHHDcHPahnwwG3GOwNAAXDNnHuaUDoo4H
b60Yzjjt680O+4jcMN2IFMBu7+FkB46CldC5BA2j2Hf0pHZN4A7jvwP8aQSHO1Wzg5DY5oAUpjnk
k+1M2beARxyR2pwnJU85IPPPNNEismDheuTmi4hNhK4I7/w9R9KRvLCkEg5GAMdKXcD0JyDwfSmt
heeMD0FAzbDM7AOoRTwRmkDk5LNnnpj7tK2OUK/kKaiqI/lLZHG08nFZXKHs4ZSWByF5OO1R73ZQ
gJ69egpTgkglgMcnqTT5G5OCp5wcnpTAk3goPmDg9RtpnnYcPtBbONoOKiL4jAXAPXHpSpyTsIHc
4HOaAJiZC3Rgc4x/ntTgZE25+UHt1z9KjEY3kbBvOMvnmkUKhL4Y7sdD+tAFmJ1lcqRyOmQP89qa
GV2Pmp8oPG3IzUCM0jgc4PoR/Wmi7RJNzPubOT8+V9PX6UxFtZgmIssjE8HJ9KHYgZ3c56Adfzqq
9wpfK/MM53Y44qViko8ws5XBOCP8PencCyvHziRtw656fn/npTFuViOJJkkBb7qk4FRNOodY5EYo
w5J/h/rVee2jRkNsvy8ktggZ6fXkdqBF85DYDHIORzkD6fnUUitt2gDnPHcVRWebdgliDzhASenG
PpUgXYSd0u7uM57d6BhGtwJC0rLvz1Q8HipwxOGIZs8AZ4P+cVGrxn7wG4kYJbBx/U0NIsrsuEyF
HTOQR3PqTS2AXfLGTvCscZOegB7/AJU6O7jL7SPmUfwtn8x/h6VDl1Uk9OcEKOQfrSAbCAgU8DnA
JH407gPe7COAY2bORlVzT5ZXk4kR49y9Qf15oRGkBBkAHJzznp/+qmyNtyoGQBgnPU+n6UgBZVOA
GLqByT049aFJYfL29P1qEuAd4Vl5IwR93OOT7U4OCu4ErjO7aePfg0XAeZxkn5FJ6hBzUg5QnecM
OcjB4qMFSPvLk8jcvT6ig7SGJdcDof64oAkGz5izFsDp+FRkpgNvzt+8M8UnlgYchcd8cCjy1Vt5
cAKvOTwPwoAkVl2p/Fn0Of0pfNjj/wCWhJ6fewfeoY03MSCGHQYXrzSsrKSzAMMjA9qBiFdxyzn1
yW5owqkgy4XuD0OKY0aFvnfI6YPP6il/doMBiMZySOhoESeapyEOEPYH/PpTGfjdll5wcVAJ1Rdw
eMLjrgcj2OamRxgFSApHGO1AA7ER5DZH5U8htu7LZz2oJdgMqQT1baMdfY01pI0VpJGVB9QPwP40
AEkTMgBbbn5iwxhqcDnq2Sw5PJz79aacMFw3UAjGMGnZXkEHI9//AK1MByFjGN77iM4AwCP1p20J
huAQCAOnHr61CC7v82A2OTjilxlT8o46npRcB29pDjOeMjp0/GkOARkducN1NNXbzuPOM59KaDAW
I3Akngk0ALtDABcsO5BHX2puwxtjZ16NnoKGKowxktkdOxzwKkypULuZccgDkfjQIcsgYsGO4joK
iXGSDlQOAMHn1pu8ZYHDKB/d5FNDbSNpJU8kMM4oGTcgLyxz/CeR9KXcoBbkgdFPqfpUTF2/jAxx
wMf5FV5Yt6kPucHrg5/D60wLnnqw25TAGODzn096jBG4gnAz/Ec/jUCxKojjEQXjAKjn3/yaeUAf
AkU5HUDj8jQIndPLPY4OMAHLD/PNBA28EFgMscjA9qqLM0SYdtg6c/l+Apd+/eBIM5wQO1GgFlGR
V+YkZJ5HpSCQY/dt5nYnNQuxiyXZdo+UfMOeP8KYCiFCuX529e/uaALA3gks2cDHBHFMZ8gYB3j3
6VE8iqvEnXk9/Xn8qdGwZl3ZOcjIOfzFIZLuAYkgDPGB+tMLsM5GecimEFWBYruY9DkY9qmyFUI8
YA65xyMfSgBrSoFAZeBzx3FNVXYjYfp3z7intErM23JB+6V5/nULAhQrDY2dylOD+NAEkodULkZc
DjPT602NyoXKgHGSQc/hUbXB3bdrM2eoBII9KYbxImy0bDaOAUx+poAsLIDIcHBI6E0pIcEF9oB6
Edari7jlfY52OOcN1I/P6VIGwDlsDaDx096AJpEQgOGBzxk8ikWAY3A4K9c9B7VHnGMdM/r71IwW
RWDqBxyRxz+FACMpGWEm056kZppQMC3LZGVPTpTUXAPDHA4J4xTgrtjKhAemG6fjQAg25IXGMfWm
YJYZBIPoKVkbacqucc80u7ywQH3EHGQelMQhVwfnQqPQimkRjvz0Ix/nilaXKjzG5IycGljX5jyO
pyW6UARndG2wNtbJPNAzkcZ45oILYJJ/HpQ2XOGIGOxOKAI2RgeQcdKUgKAMHngHHA+tNdlU84Zu
dobpQZUT7xQcgcNQAjKRtxnA67e/NNC7m4BXtnnke1Okmjkk74KgZGP50EP5ZUBoztwSOMCgQYJz
ub5T6elMBClt5xgnKn0+tRiUo4UbSBx6ZPvmptynHAA4+XJA5o3C5tpcBgrSMoY8naacxQkMMcHA
JNcV/ac8cix797pwWzwtalrq7bgN8ZwMY61wxxMGCmmdE5X5A3lqVJHGBu5qNtpbJ5zxjiuf/tUh
XaQBmyCuTwfrTH1bJ8zPzHsOh7fhTeJpoOdHS4QlcueT26fmKjR4hn5eAuSOOT9a5wa7KuY2UgA5
GG6CmTaweGyTtOSOw+n+e1T9bh0Fzo6eSaLCgoMZGDuzmgNGih3LqCMfKuR+Vcp/aczb9owM5FEu
tXBt/LAPzLjO44pfXIC5zp76+EOGSBmzjcYznIxnHWqsep20xUl5Yi2cqQOK56O/ndSxOcgEg/yx
Tri+ZsqV24GR34x0qfri7D5zelW2Vo5YtwCsF81QRlvfFPafE2ftSFW+fYuSD7HPHpXPS3UixJGr
AkgZOf8APaq8O9mw0jRuue/BGc1LxttkJyd7HYefau6LGiAnoSM/jUyXEMp27iR2x0zXI/aJFlUB
8lfl3ZwTUn2h13HJKjsp/wA+n61Sxq6oFM6mSdf3oV2Az0z0GaBcQcnzM56jdnkd/wBa5IX0m8ku
WYnGXNSQTzQ5aQqUXjGc89qX11X1Qc50rtHnJcAnn5eSabPdKo2ls8dB1AHY1iS6hKCjMu043ovb
Hb+VZ3nuwkDyNuI4YDinLGx6IOc6lHjjYLvZlb5V4zg9ePqKlju0JYNuUq38I/z61yMWo3CqNxL4
7tSpeSxoyhixYlW3DqMUfXF2D2iOpfUIQQxbYW54bt9D9D3przh3BDiMnBwADz/nNcksV20LHzAQ
3TPXPrSGW42s7HkLtG3PzD/Gl9bYc+h2kV0jyGNZFdsH73Jzxz78mozd25X5QBvbgqcbv/1Vw1vP
cxSjeW5GFC+h5qwZ7gqB5h2r94D3oeLa6C59DrXv4ni8zHI4C5Oen86W4nyQU28jglj/ACrlFnkA
LAkjAOAPSka6uGyx3F8Z3DuKlYzTVD5zq4LifahLBkYnkDp6jjnvVh7jYnzDIOST1B+n61y0OoP5
QQLtwPTr7/yprXl0qhQWKqd2T1q1jIpWsPmOna4j87aFDDb1xgZz+nalaQJIyn5mAGRnpnpXHSz3
jRFsgBBjH41JHeXWI5c/vE4O0Y4p/W12BSOtW6RAvK4HY9CD16UsjK7kKyjIJKjng9v/AK9cu96d
n90HIPqMigXkj7fLIyBk80vrq7BzHTLHDDtRdqKTx8uMDHSkec4AjRWZuhyM8fXrXNXOqM2CAQM9
Ryen8qa19M6blIDpzu74z/LpVfW49g5zqjcKcAPsYHg5+vp9KCSzbsBhjk5AzXJJf3cRY+4Iz147
1PDqkix7VcllG3nv3PNP63Hqhc6OmNwsa/eA5ORnPX2qOS8RojtPYfcHf/PrXKtqVwz4XCru5xxj
/OKc+oP5cihcFht3Zznmk8YuiDnudWs6lWkVuNwHOBtz2P8AntVee4SNyWlGDgAMMcjj09eetcoL
6V0YIAXB4B79qmnuLi4hXzGZWU4yfSh4xW2F7Q6SPVUKqwOQRz+dStIv+sMnyDDcnGPcVxplaJAV
fgHknnpU7XtyYNjPnJDYHXj0qVjO6JVQ6hroMqENtXpgCom1KNVPzcHB+g65rkJL2eQAhmUDA+UY
9s03zJXDnLFc4XP+fah4t9EHtDr31aHHy7cgZz0yP8mof7Zgk3sZMANjGBzXLvNK5D5OQCuBxxTF
VlCjDZxySal4qfQXtDqG1WFXIZyN7cYPQYx0q6uoRiOTDcx7gSe2O4rjmbEnTJA+8BS+dKGX587j
8wPTFTHFTQe0Z1K6xE7FCwAOBu49j9KdJqsJwA4OCSx469K5DzCSAMZbjGaeVaeJmQckjvgD2prF
T6gqjOsTVIZPkc7gpweOv0/AU9L+KPGFRD3B7egrkWZ2IbJ2n14Oacr+WcliVYYz6UfW5IPaHVSX
9vkv5iscZVPz/wAKWSeJgEaTyQqknaMnoT/k1zDFWbdntjp0FNMs5ct5hYAjJzjgCq+uMfOdeyqW
U4RlK5BVjkDjJpj3KDEO/wCYdCTXKHUJ4QqpIeTkEU6K9lchvMxuG0DsKpYzug9odO8kLAKj5VOe
Rw3PrVNL5JXjjJwcAHPv0FYrXUoQFHyMbeBj/PSqkbtGQSMsOM561LxcnsgdQ6kaiI52QKPkXOFP
Ge386WW+UbmySo+VlI71z/mEuS5IdyFyaSQBFy0hIPOAe/NZfW6lw9ozcfU4o2AUDDblGP5g0g1J
JFYM25gOCefb09a5wtkjDkYHI/8ArUjyMrsrSHJPHFWsVMn2hvS6lER5hQLwDzxj6H8e9WotWtGL
He6Lt+Vh39jXJuWdWJJ25zmgHarc7AOgHemsTPcftDrP7WgSIYyiuSu4EHI//XVca1ECqliAy7sg
9/TpXMNI4jA3HGcimlnXBY/Tim8RNi9qzqk1WBSVZjGRkgjB55454px12JcIW4/iLcEHtxXK+azK
qHJIyR+NSMed20hmGDjtSeJmP2jOoTV4slZOp5yB09aYdTiQD5gDt4yQa5qRhg7eoOAfrTmjHDPJ
jPJH9KX1qYvaM6I66m5kGMA5BApsmtqYg7HIAzXOMTwU+X6d+O9VmkdDuJ+mDmrWImw9ozpf7XRV
ch/mLYwT6/Ss+XW2kcEqcjhs9x1/pWSHz1AbGM+howHYscgBe/Y0nVmxObZfutZkbbtPKtwR6YqK
71eRo0C8/IAW78d6oAbR8wDnnA9KTYTgK2R0x6UueXVk8zLX9qXSIPmYN13Z7dafL4gkZkbc53Jt
IJ6mqLZ2qDgEck1GkcbsruW2hugOM1UZ9ylJGhDqshbKuxTIyM9MVtadrazLsncrtXg9mOa5qVII
pMxHAYlsZzye1MBzk78DHHHWnzuLvEHKz0P/2Q==

--Apple-Mail-19--238326440
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--Apple-Mail-19--238326440--


From v4v6interim-bounces@ietf.org  Wed Oct  1 10:42:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D9663A6909;
	Wed,  1 Oct 2008 10:42:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54F3E3A6909
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 10:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5
	tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WPBBgaqNCiiu for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 10:42:36 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 5ED873A67B3
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 10:42:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="166765400"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 17:42:14 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91HgEo9023319; 
	Wed, 1 Oct 2008 10:42:14 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91HgEnt001798;
	Wed, 1 Oct 2008 17:42:14 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:42:14 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:42:13 -0700
Message-Id: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Bill Manning <bmanning@karoshi.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 13:42:11 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 17:42:13.0726 (UTC)
	FILETIME=[09E90FE0:01C923ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1335; t=1222882934;
	x=1223746934; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Single=20namespace |Sender:=20;
	bh=YBx2S3HvPWtrcPXZI6cneKf6wlH8OFc9FRPgV69hU3A=;
	b=tYp9wubyp20daBOnjAhpi6ec7Lyy8ly16s+a2VN+gTGeJ7RurhzG0vL+JL
	cWB9SIV3UK4lzaOGc6QhITRJ0fxX6I+w+F9t35Ftmdz/GMZ14qz8ELh7M4Sa
	SXXjO1psZW;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

picking up from the discussion in the chat room, and passing along a  
question that jabber wasn't able to deliver in the chat room.

Not sure we're disagreeing on whether there should be a single name  
space. The real question is what you say about a name when you're  
asked to translate it into a name.

Let's imagine that the name oatwillie.example.com has two A records,  
pointing respectively to 1.2.3.4 and 192.168.0.1. The question is not  
whether the name is different in different namespaces; the question is  
whether the translation is different in different domains.

The way we usually implement this kind of thing is to have multiple  
name servers, one of which is accessible from outside and the other is  
accessible from inside. That gives us one name space, but different  
responses to that translation request depending on the source of the  
request. DNS64 does largely the same thing, but commits the gross and  
indecent act of saying out loud that it does so.

The difference in the domains in DNS64 is between an IPv4 (IPv4-only  
or IPv4+IPv6) domain and an IPv6-only domain and referencing a name  
that has an A record but not an AAAA record.

So now I will repeat my question. You said that you didn't care for  
DNS64. I'm asking what, specifically, you would prefer to use.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 10:44:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E910E3A6C40;
	Wed,  1 Oct 2008 10:44:48 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C9523A6C40
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 10:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.466
X-Spam-Level: 
X-Spam-Status: No, score=-106.466 tagged_above=-999 required=5
	tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fLrz2ohNfh94 for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 10:44:46 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 9B85B3A6C3C
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 10:44:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="166766752"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 17:44:34 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m91HiYQI000502; 
	Wed, 1 Oct 2008 10:44:34 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91HiYj6002635;
	Wed, 1 Oct 2008 17:44:34 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:44:34 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 10:44:33 -0700
Message-Id: <F4CDAF13-FCE4-436E-B4EB-0253DA58983C@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Bill Manning <bmanning@karoshi.com>
In-Reply-To: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 13:44:32 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 17:44:33.0803 (UTC)
	FILETIME=[5D671DB0:01C923ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=291; t=1222883074; x=1223747074;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Single=20namespace
	|Sender:=20; bh=llkteCk9v/iPK2xUQTTaghqxMIEV2uKnlGc6JV/KD/k=;
	b=ISRLtZ3KyZEirABv41mks9G2HpFFGXxHHEfF6jBBzTKzcrixYMeXOiNnC1
	0QpIZYSgMMR0vsSmZc2vdYNNZK+pfZlpayPC10tdcpy3BzpQpydxR+m+SDkA
	XUzJjNZ30i;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 1:42 PM, Fred Baker wrote:

> Not sure we're disagreeing on whether there should be a single name  
> space. The real question is what you say about a name when you're  
> asked to translate it into a name.

arg: s/into a name/into a record reporting an address/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 10:58:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C21413A6856;
	Wed,  1 Oct 2008 10:58:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7203F3A6856
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 10:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id omUadDStfCUc for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 10:57:58 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net
	[207.173.203.159])
	by core3.amsl.com (Postfix) with ESMTP id 5FEC43A6405
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 10:57:58 -0700 (PDT)
Received: from commandprompt.com (traingw.ericsson.ca [192.75.88.176])
	(authenticated bits=0)
	by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m91I1A11002570
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:01:13 -0700
Date: Wed, 1 Oct 2008 13:57:26 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081001175725.GI33079@commandprompt.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(lists.commandprompt.com [207.173.203.159]);
	Wed, 01 Oct 2008 11:01:13 -0700 (PDT)
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Wed, Oct 01, 2008 at 01:42:11PM -0400, Fred Baker wrote:

> Let's imagine that the name oatwillie.example.com has two A records, 
> pointing respectively to 1.2.3.4 and 192.168.0.1. The question is not 
> whether the name is different in different namespaces; the question is 
> whether the translation is different in different domains.
>
> The way we usually implement this kind of thing is to have multiple name 
> servers, one of which is accessible from outside and the other is 
> accessible from inside. That gives us one name space, but different 
> responses to that translation request depending on the source of the 
> request. DNS64 does largely the same thing, but commits the gross and 
> indecent act of saying out loud that it does so.

I think that in the scenario with one RFC1918 address and one public
address, one of the answers comes with a local context and the other
comes with a global context.  The local context is determinable by the
querying host on the basis of the host's own IP address, because you
know that if you have an RFC1918 address, you're in a local-only
context.  In the case of DNS64, however, the whole point is that the
host doesn't need to know that it's living in a special place.  So
there's nothing about the state of the host that tells you what the
context is.  Instead, you need to know what the state of its relation
to other hosts on the Internet is in order to know what the "right"
context is.  Something about that makes me uneasy, but I can't yet put
my finger on what.

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:03:52 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DA0428C148;
	Wed,  1 Oct 2008 11:03:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9F6D3A67A7
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.479
X-Spam-Level: 
X-Spam-Status: No, score=-106.479 tagged_above=-999 required=5
	tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8vKnyz5++RU8 for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:03:50 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id AE1D828C148
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:03:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="85468936"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 01 Oct 2008 18:03:37 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91I3b2v009484; 
	Wed, 1 Oct 2008 11:03:37 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m91I3bGt006335;
	Wed, 1 Oct 2008 18:03:37 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:03:36 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:03:36 -0700
Message-Id: <7F44852E-9BE5-4866-B024-B82B5A791599@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Andrew Sullivan <ajs@commandprompt.com>
In-Reply-To: <20081001175725.GI33079@commandprompt.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 14:03:35 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<20081001175725.GI33079@commandprompt.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 18:03:36.0675 (UTC)
	FILETIME=[069B8B30:01C923F0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2617; t=1222884217;
	x=1223748217; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Single=20namespace
	|Sender:=20; bh=+/pBCe1L8B726epuR8amWTRP0IQKGtxgQi2ydoFFWVk=;
	b=LNY53YYB7cfeqFjYoa/BgoPwpgO69i7YqNrwo6Uhc+cX/i557e+lySd4FM
	5NMnr8SWFAB3VU+pNzCJPSlW3OReMziYw6iIHQKhLn7aKcawf9AWpksPI2ay
	IzgUiT+qpG;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

fine. I'll argue that the IPv4 host in my example doesn't know  
anything about public or private addresses; it knows what server it  
has been instructed to use.

In the DNS64/IVI case, it knows little more. It knows that it has no  
IPv4 DNS server and no IPv4 router or address, and that it has all of  
those in IPv6. So it asks for a AAAA record for any name it needs  
translated into an address, and it believes the translation. The  
translation is scoped - the DNS64 server advertises AAAA records  
derived from A records when it has no other AAAA record to present,  
and it does so in the domain in which it resides. But the host knows  
nothing of the scoping.

On Oct 1, 2008, at 1:57 PM, Andrew Sullivan wrote:

> On Wed, Oct 01, 2008 at 01:42:11PM -0400, Fred Baker wrote:
>
>> Let's imagine that the name oatwillie.example.com has two A records,
>> pointing respectively to 1.2.3.4 and 192.168.0.1. The question is not
>> whether the name is different in different namespaces; the question  
>> is
>> whether the translation is different in different domains.
>>
>> The way we usually implement this kind of thing is to have multiple  
>> name
>> servers, one of which is accessible from outside and the other is
>> accessible from inside. That gives us one name space, but different
>> responses to that translation request depending on the source of the
>> request. DNS64 does largely the same thing, but commits the gross and
>> indecent act of saying out loud that it does so.
>
> I think that in the scenario with one RFC1918 address and one public
> address, one of the answers comes with a local context and the other
> comes with a global context.  The local context is determinable by the
> querying host on the basis of the host's own IP address, because you
> know that if you have an RFC1918 address, you're in a local-only
> context.  In the case of DNS64, however, the whole point is that the
> host doesn't need to know that it's living in a special place.  So
> there's nothing about the state of the host that tells you what the
> context is.  Instead, you need to know what the state of its relation
> to other hosts on the Internet is in order to know what the "right"
> context is.  Something about that makes me uneasy, but I can't yet put
> my finger on what.
>
> A
>
> -- 
> Andrew Sullivan
> ajs@commandprompt.com
> +1 503 667 4564 x104
> http://www.commandprompt.com/
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:08:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B44F93A6A4E;
	Wed,  1 Oct 2008 11:08:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC88C3A6A4E;
	Wed,  1 Oct 2008 11:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.904
X-Spam-Level: 
X-Spam-Status: No, score=0.904 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,
	RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F6Rsgeb31xgt; Wed,  1 Oct 2008 11:08:27 -0700 (PDT)
Received: from zns001-0m9001.yokogawa.co.jp (zns001-0m9001.yokogawa.co.jp
	[203.174.79.138])
	by core3.amsl.com (Postfix) with ESMTP id C87EE3A699C;
	Wed,  1 Oct 2008 11:08:26 -0700 (PDT)
Received: from zns001-0m9001.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m91I8EW5004748; Thu, 2 Oct 2008 03:08:14 +0900 (JST)
Received: from zex001-0m9026.jp.ykgw.net (zex001-0m9026.jp.ykgw.net
	[10.0.11.45])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	m91I8EeB004745; Thu, 2 Oct 2008 03:08:14 +0900 (JST)
Received: from EXMAIL03.jp.ykgw.net ([10.0.11.29]) by
	zex001-0m9026.jp.ykgw.net ([10.0.11.45]) with mapi;
	Thu, 2 Oct 2008 03:08:13 +0900
From: <Masahito.Endou@jp.yokogawa.com>
To: <v4v6interim@ietf.org>
Date: Thu, 2 Oct 2008 03:08:13 +0900
Thread-Topic: New Version Notification for draft-endo-v6ops-dnsproxy-01 
Thread-Index: Ackj72CMqx4Z/ZwPRa6edRtUIdwjZQAAFfrw
Message-ID: <B76F972AA81DDB4F8E4BA80DEDE43983D32C922AA1@EXMAIL03.jp.ykgw.net>
References: <20081001175831.9E8943A6801@core3.amsl.com>
In-Reply-To: <20081001175831.9E8943A6801@core3.amsl.com>
Accept-Language: ja-JP
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: ja-JP
MIME-Version: 1.0
Cc: behave@ietf.org
Subject: [v4v6interim] FW: New Version Notification for
	draft-endo-v6ops-dnsproxy-01
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Hi

I revised my draft [draft-endo-dnsproxy].
I defined the new EDNS option to support verifing synthesized records.
I think that it is a discussion item, because NAT64 also proposes alternate solution.

best regards,

// masaxmasa

A new version of I-D, draft-endo-v6ops-dnsproxy-01.txt has been successfuly submitted by Masahito Endo and posted to the IETF repository.

Filename:        draft-endo-v6ops-dnsproxy
Revision:        01
Title:           Translator Friendly DNS Proxy
Creation_date:   2008-10-01
WG ID:           Independent Submission
Number_of_pages: 27

Abstract:
This document describes the DNS Proxy that is separated from NAT-PT
[RFC2766].  NAT-PT was designed to work with DNS Application Level
Gateway.  However [RFC4966] pointed out DNS related issues, and
[RFC2766] was changed to historical state.  This document attempts to
DNS Proxy specification, removing dependency on NAT-PT as well as
resolving problems pointed in [RFC4966].



The IETF Secretariat.


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:16:26 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B75528C0FC;
	Wed,  1 Oct 2008 11:16:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B85693A676A
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.49
X-Spam-Level: 
X-Spam-Status: No, score=-106.49 tagged_above=-999 required=5
	tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2Ah8ynuihBWI for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:16:23 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id B51BC3A6856
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:16:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="105843852"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 01 Oct 2008 18:16:14 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91IGDZ5013284; 
	Wed, 1 Oct 2008 11:16:13 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91IGD8X013355;
	Wed, 1 Oct 2008 18:16:13 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:16:13 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:16:12 -0700
Message-Id: <4AEC856D-6418-44A7-84E7-79A64913A1A2@cisco.com>
From: Fred Baker <fred@cisco.com>
To: bmanning@vacation.karoshi.com
In-Reply-To: <20081001180949.GA4282@vacation.karoshi.com.>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 14:16:11 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<20081001180949.GA4282@vacation.karoshi.com.>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 18:16:12.0498 (UTC)
	FILETIME=[C91CFB20:01C923F1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2329; t=1222884973;
	x=1223748973; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Single=20namespace |Sender:=20;
	bh=LvFb/yrwLxNxEYIEQ99wwOz/xkItkuZHhBgBjePOcac=;
	b=qmXpa5o9DgByBVs4+3xsBToGdv9ejoZ16XIs0tASCBMbHJCePG4IF+MixH
	3IBBpsWBSfyAwAnci1cBjRUgfA6gIvV+g2cVfdnhM7kTWGUV5YI57vph2ano
	cunapIEWMpIfzakcGAboMJ67FpHHP8L+M0ASfewBkcasvoFElAnaM=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 2:09 PM, bmanning@vacation.karoshi.com wrote:
> that said, DNS64 is asserted to provide a different answer depending  
> on
> where the question originates.  Some folks do this today w/ a bind  
> construct
> called "views".  if  DNS64 "constructs" synthetic addresses on the fly
> (algorithmically generated addressess) as proposed,  is this based  
> on the
> DNS64 application intercepting a DNS reply - (here is the A rr) and  
> fabricating
> a lie (here is the AAAA rr) to pass to the querier? where the AAAA  
> is the address
> of the translation device?

It doesn't intercept anything.

It gets a AAAA request from some host, sends a request for an A record  
(perhaps o itself), gets the A record response, generates a AAAA  
record from it, and sends that as a reply to the original request.

> If this is a plausable explaination, then I would posit that the  
> creation of
> DNS64 is injecting a MITM vector that is unreasonable.

Any form of translation is a MITM vector. If you find translation  
unreasonable, then yes you will find that vector unreasonable. If you  
find translation necessary, I don't think you can avoid the  
possibility that the translator is a MITM vector.

> depending on the deployment model, i think that properly placed DNS  
> caches, running
> dual stack, would work just fine.

several problems there. First, what if a name exists and is  
translatable but doesn't happen to be in the cache at the moment? Do  
you populate the cache? Second, what if the cache is poisoned?

Your complaining about MITM attacks?

> back to the oatwillie.example.com case...
> presume the node has a single NIC  ::   2001:478:6::cafe
> and and IVI box with               ::   2001:478:6::254
> 	                           ::   198.32.6.251
>
> with a dual-stack DNS server       ::   2001:478:6::11
>                                   ::   198.32.6.11
>
> inside the DNS server, I might make the following mapping for  
> oatwillie:
>
> oatwillie	in aaaa 2001:478:6::cafe
> 		in a    198.32.6.251
>
>
> would that work for you?

Maybe. If the server directly knows the translation already, it's  
great. I don't think it is a very general solution, though, as there  
is no way to populate the cache in the first place.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:23:40 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C08603A6A33;
	Wed,  1 Oct 2008 11:23:40 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D6F03A6A33
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.773
X-Spam-Level: 
X-Spam-Status: No, score=-5.773 tagged_above=-999 required=5 tests=[AWL=0.226, 
	BAYES_00=-2.599, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9955vHK-biyS for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:23:38 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 526AD3A69DF
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:23:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="105845863"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 01 Oct 2008 18:23:41 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91INfL7030559
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:23:41 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91INese020222
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 18:23:41 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 14:23:41 -0400
Received: from Townsley-MacBook.local ([10.82.245.147]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 14:23:40 -0400
Message-ID: <48E3BFE8.5030103@cisco.com>
Date: Wed, 01 Oct 2008 14:22:32 -0400
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
In-Reply-To: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
X-OriginalArrivalTime: 01 Oct 2008 18:23:40.0621 (UTC)
	FILETIME=[D4371FD0:01C923F2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6670; t=1222885421;
	x=1223749421; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=rBVfIKduBuRbAZyMbbMaIPmeuubn0OGj/2ofxOB2XHo=;
	b=DYl6UYC9tiH9SuKtE7LRRR3yFCREzp6ZcdmGDNOhdoeb3xOxNAMDnry5yx
	jmJ4AGx/YfFou6pNULIsNQ3aG/LWCfeD4wrc1baTI0FE6JRE8Fbk3DDhaNzv
	D7S9FOOdNIsrvMCqX2Rvu6NRqPlcTir1gqwl4OA/O3/C3HMOFb8bQ=;
Authentication-Results: sj-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


Fred,

By "hard" I didn't intend to predispose whether the solution itself 
would be hard or easy to code, scale, or otherwise make work for some 
scoped definition of the problem. The statement that this is "hard" made 
it's way into the slide based on discussions at the last ietf, on list, 
etc. where I found less understanding in the community on exactly how 
IPv4 -> IPv6 translation could be made to work in a scalable or useful 
manner. As you say, one needs to approach and analyze the problem in a 
specific manner in order to make it seem less "hard."

Hopefully by the end of the meeting we will all be approaching and 
analyzing the problem correctly. Then, it won't seem so hard and I will 
happily erase the bullet from the slide deck.

- Mark

PS. Apologies that I didn't spend more time on this topic, it was 
scenario #5 of 5 - we were running out of time during the slot, and 
frankly I ran out of time making the slides leading up to the meeting as 
well so perhaps did not give this full billing. I had no intention of 
implying one scenario more important than the other based on slide count.


Fred Baker wrote:
> I'm fairly disturbed by Mark's dismissal of IPv4->IPv6 translation as 
> "hard". I'll take this note to say why. I am obviously a proponent of 
> a particular class of solution, IVI, which is specifically targeted at 
> solving this problem, so let me declare bias up front. But I do not 
> consider the issue hard if correctly analyzed and approached.
>
> In this analysis, I am going to leave out the dual stack case, which I 
> frankly consider the strongly preferable deployment model. Wherever it 
> is used, matters get simplified. I am expressly looking at the more 
> difficult IPv4-only/IPv6-only case.
>
> Mark's dismissal - I call it that because he spent an hour talking 
> about CGN solutions and then spent less than a minute charging through 
> two slides that discussed actually deploying IPv6 and declaring them 
> both "hard" and therefore not worthy of consideration - is based on 
> the observation that mapping 2^128 addresses into 2^32 bits is hard. I 
> will agree with him that making it possible for every IPv6 address to 
> be mapped into IPv4 in a scalable manner has issues. The question that 
> I will ask is: is that the real requirement? I don't think it is.
>
> While the addressing issue resolves to hosts, the connectivity problem 
> is about applications. I think that today's applications can largely 
> be broken down into two broad categories, and speakers in those 
> applications into three. These are: the clients of client/server 
> applications, the servers in client/server applications, and the peer 
> in peer-to-peer applications. In an IPv4-only/IPv6-only gateway, we 
> have actually only our session initiation problems to solve:
>
>     IPv6 client->IPv4 server
>     IPv4 client->IPv6 server
>     IPv6 peer -> IPv4 peer
>     IPv4 peer -> IPv6 peer
>
> Once a session is initiated, we can obviously continue the conversation.
>
> IPv6 client->IPv4 server is pretty simple. The DNS ALG advertises IPv4 
> addresses as mapped IPv6 addresses, and the gateway keeps 1:n overlaid 
> mappings in a manner not all that different from current IPv4/IPv4 
> NATs. On the IPv6 side of the gateway, we simply use the mapped 
> address; on the IPv4 side, we use IPv4 address+port overlay as we do 
> in IPv4/IPv4 NATs.
>
> An IPv4 client accessing an IPv6 server is equally simple given a 1:1 
> mapping such as NAT64 or IVI describes. One maps the headers and the 
> addresses.
>
> IPv6 peer->IPv4 peer is simple enough; it is essentially the same 
> problem as IPv6 client->IPv4 server, and is solved the same way.
>
> Initiating a session from an IPv4 peer to an IPv6 peer with an 
> unmapped address is "hard"; that winds up calling for complex 
> machinery like NAT-PT proposes. However, it is unnecessary to solve 
> the case. p2p technologies open TCP connections between systems, leave 
> them open long periods of time, and use them to transport data. They 
> are in effect overlay networks. If one IPv6 peer opens a session to an 
> IPv4 peer, connectivity is established between IPv4-only and IPv6-only 
> p2p networks and the problem is solved.
>
> So to my mind, the requirement is that the gateway provide three 
> services:
>   - a DNS algorithm that maps IPv4 addresses to a subset of IPv6
>     addresses.
>   - a 1:1 NAT algorithm that statelessly supports the common case of
>     IPv4 clients accessing IPv6 servers, which will be used by a
>     relatively small set of hosts in the IPv6-only domain.
>   - 1 1:n NAT algorithm that statefully maps general IPv6 to IPv4
>     address plus port, which might be used by an arbitrarily large
>     number of hosts in the IPv6-only domain, but unlikely to be all
>     at the same time and diminishing as IPv6 deployment grows.
>
> None of those models is "hard" in light of our present experience with 
> SIIT and IPv4/IPv4 NAT.
>
> Now, here is my issue with NAT64/SIIT's addressing model, which we 
> deployed and then deprecated in RFC 4291. There are two. First, it is 
> a lot like a default route, and limits the network administration's 
> options in route management; to fix that, we need to have a prefix 
> appropriate to the gateway as opposed to a flat "must be zero" style 
> prefix. Second, th addressing architecture is essentially that of CIDR 
> and therefore allows routing prefixes to be as long or as short as 
> needed, but we have given clear guidance that router vendors should 
> think about host routes or prefixes of /64 or shorter, not normally 
> prefixes in the 65..127 length range. If we believe that - and RFC 
> 4291 clearly does - then enabling the gateway to support routing to 
> multiple sites within the IPv6 domain using a single IPv4 prefix 
> advertised in the IPv4 domain (as opposed to doing host routing to 
> IPv4-mapped addresses in the IPv6-only domain) is important for 
> scaling. IVI moves the address around to put IPv4-mapped prefixes 
> within the /64 length rule.
>
> So the fundamental argument for IVI is that it works well with 
> routing, and makes interchange of both p2p and client/server 
> applications across the IPv4/IPv6 gateway simple.
>
> IPv4 access to the IPv6 network is most definitely *not* hard if the 
> problem is correctly parsed and addressed.
>
> No pun intended.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:26:54 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2110B3A6AEC;
	Wed,  1 Oct 2008 11:26:54 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA7123A681F
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.199
X-Spam-Level: 
X-Spam-Status: No, score=-106.199 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i-0cpZomoRLm for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:26:51 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id D9B583A676A
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:26:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="105846680"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 01 Oct 2008 18:26:56 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m91IQtiO012120
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:26:55 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m91IQtqS002762
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 18:26:55 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:26:54 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:26:54 -0700
Message-Id: <95D16B70-4462-4BBB-9782-E3DA4B7A1A1B@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <48E3BFE8.5030103@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 14:26:53 -0400
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<48E3BFE8.5030103@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 18:26:54.0494 (UTC)
	FILETIME=[47C5CBE0:01C923F3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7246; t=1222885615;
	x=1223749615; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=KOcJ0gv7zvYQQfG9xGL/fOSZER6y5cqTi6OAIxbxYms=;
	b=NsBf1h8uCraP3Tt1lkY76WRMIx5I1/zCgo/yJTkR+Q+jrKVQXOF1gJ6nML
	awh2D/z/D+EtIVPC59WZfWNLOFGgK3qaH4VAiaeQdEV9ff3lujxAEZLA0hQx
	9UWuasRkxo;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

ack. I think SIIT, NAT64, and IVI have each addressed placing IPv4- 
accessible systems within an IPv6 network in a scalable fashion (at  
least as scalable as addressing itself). I obviously have a preference  
among those, but I think it is both possible and straightforward.

On Oct 1, 2008, at 2:22 PM, Mark Townsley wrote:

>
> Fred,
>
> By "hard" I didn't intend to predispose whether the solution itself  
> would be hard or easy to code, scale, or otherwise make work for  
> some scoped definition of the problem. The statement that this is  
> "hard" made it's way into the slide based on discussions at the last  
> ietf, on list, etc. where I found less understanding in the  
> community on exactly how IPv4 -> IPv6 translation could be made to  
> work in a scalable or useful manner. As you say, one needs to  
> approach and analyze the problem in a specific manner in order to  
> make it seem less "hard."
>
> Hopefully by the end of the meeting we will all be approaching and  
> analyzing the problem correctly. Then, it won't seem so hard and I  
> will happily erase the bullet from the slide deck.
>
> - Mark
>
> PS. Apologies that I didn't spend more time on this topic, it was  
> scenario #5 of 5 - we were running out of time during the slot, and  
> frankly I ran out of time making the slides leading up to the  
> meeting as well so perhaps did not give this full billing. I had no  
> intention of implying one scenario more important than the other  
> based on slide count.
>
>
> Fred Baker wrote:
>> I'm fairly disturbed by Mark's dismissal of IPv4->IPv6 translation  
>> as "hard". I'll take this note to say why. I am obviously a  
>> proponent of a particular class of solution, IVI, which is  
>> specifically targeted at solving this problem, so let me declare  
>> bias up front. But I do not consider the issue hard if correctly  
>> analyzed and approached.
>>
>> In this analysis, I am going to leave out the dual stack case,  
>> which I frankly consider the strongly preferable deployment model.  
>> Wherever it is used, matters get simplified. I am expressly looking  
>> at the more difficult IPv4-only/IPv6-only case.
>>
>> Mark's dismissal - I call it that because he spent an hour talking  
>> about CGN solutions and then spent less than a minute charging  
>> through two slides that discussed actually deploying IPv6 and  
>> declaring them both "hard" and therefore not worthy of  
>> consideration - is based on the observation that mapping 2^128  
>> addresses into 2^32 bits is hard. I will agree with him that making  
>> it possible for every IPv6 address to be mapped into IPv4 in a  
>> scalable manner has issues. The question that I will ask is: is  
>> that the real requirement? I don't think it is.
>>
>> While the addressing issue resolves to hosts, the connectivity  
>> problem is about applications. I think that today's applications  
>> can largely be broken down into two broad categories, and speakers  
>> in those applications into three. These are: the clients of client/ 
>> server applications, the servers in client/server applications, and  
>> the peer in peer-to-peer applications. In an IPv4-only/IPv6-only  
>> gateway, we have actually only our session initiation problems to  
>> solve:
>>
>>    IPv6 client->IPv4 server
>>    IPv4 client->IPv6 server
>>    IPv6 peer -> IPv4 peer
>>    IPv4 peer -> IPv6 peer
>>
>> Once a session is initiated, we can obviously continue the  
>> conversation.
>>
>> IPv6 client->IPv4 server is pretty simple. The DNS ALG advertises  
>> IPv4 addresses as mapped IPv6 addresses, and the gateway keeps 1:n  
>> overlaid mappings in a manner not all that different from current  
>> IPv4/IPv4 NATs. On the IPv6 side of the gateway, we simply use the  
>> mapped address; on the IPv4 side, we use IPv4 address+port overlay  
>> as we do in IPv4/IPv4 NATs.
>>
>> An IPv4 client accessing an IPv6 server is equally simple given a  
>> 1:1 mapping such as NAT64 or IVI describes. One maps the headers  
>> and the addresses.
>>
>> IPv6 peer->IPv4 peer is simple enough; it is essentially the same  
>> problem as IPv6 client->IPv4 server, and is solved the same way.
>>
>> Initiating a session from an IPv4 peer to an IPv6 peer with an  
>> unmapped address is "hard"; that winds up calling for complex  
>> machinery like NAT-PT proposes. However, it is unnecessary to solve  
>> the case. p2p technologies open TCP connections between systems,  
>> leave them open long periods of time, and use them to transport  
>> data. They are in effect overlay networks. If one IPv6 peer opens a  
>> session to an IPv4 peer, connectivity is established between IPv4- 
>> only and IPv6-only p2p networks and the problem is solved.
>>
>> So to my mind, the requirement is that the gateway provide three  
>> services:
>>  - a DNS algorithm that maps IPv4 addresses to a subset of IPv6
>>    addresses.
>>  - a 1:1 NAT algorithm that statelessly supports the common case of
>>    IPv4 clients accessing IPv6 servers, which will be used by a
>>    relatively small set of hosts in the IPv6-only domain.
>>  - 1 1:n NAT algorithm that statefully maps general IPv6 to IPv4
>>    address plus port, which might be used by an arbitrarily large
>>    number of hosts in the IPv6-only domain, but unlikely to be all
>>    at the same time and diminishing as IPv6 deployment grows.
>>
>> None of those models is "hard" in light of our present experience  
>> with SIIT and IPv4/IPv4 NAT.
>>
>> Now, here is my issue with NAT64/SIIT's addressing model, which we  
>> deployed and then deprecated in RFC 4291. There are two. First, it  
>> is a lot like a default route, and limits the network  
>> administration's options in route management; to fix that, we need  
>> to have a prefix appropriate to the gateway as opposed to a flat  
>> "must be zero" style prefix. Second, th addressing architecture is  
>> essentially that of CIDR and therefore allows routing prefixes to  
>> be as long or as short as needed, but we have given clear guidance  
>> that router vendors should think about host routes or prefixes of / 
>> 64 or shorter, not normally prefixes in the 65..127 length range.  
>> If we believe that - and RFC 4291 clearly does - then enabling the  
>> gateway to support routing to multiple sites within the IPv6 domain  
>> using a single IPv4 prefix advertised in the IPv4 domain (as  
>> opposed to doing host routing to IPv4-mapped addresses in the IPv6- 
>> only domain) is important for scaling. IVI moves the address around  
>> to put IPv4-mapped prefixes within the /64 length rule.
>>
>> So the fundamental argument for IVI is that it works well with  
>> routing, and makes interchange of both p2p and client/server  
>> applications across the IPv4/IPv6 gateway simple.
>>
>> IPv4 access to the IPv6 network is most definitely *not* hard if  
>> the problem is correctly parsed and addressed.
>>
>> No pun intended.
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:35:07 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 319413A69DF;
	Wed,  1 Oct 2008 11:35:07 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 393773A69DF
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lfjJtSz35xNU for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:35:05 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23])
	by core3.amsl.com (Postfix) with ESMTP id 78E563A67A7
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:35:05 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29])
	by mail-out4.apple.com (Postfix) with ESMTP id 0015B3FAC5BA
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:34:30 -0700 (PDT)
Received: from relay13.apple.com (unknown [127.0.0.1])
	by relay13.apple.com (Symantec Mail Security) with ESMTP id DB7792808C
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:34:30 -0700 (PDT)
X-AuditID: 1180711d-ac911bb000000ede-ce-48e3c2b6afcb
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com
	[17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay13.apple.com (Apple SCV relay) with ESMTP id B7B722807D
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:34:30 -0700 (PDT)
Message-Id: <090C6392-9082-4660-AE68-FA384B788C03@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 11:34:30 -0700
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 1, 2008, at 10:42, Fred Baker wrote:
>
> The way we usually implement this kind of thing is to have multiple  
> name servers, one of which is accessible from outside and the other  
> is accessible from inside.

The reason I've been having a hard time following this discussion is  
that you're using the word "domain" where I've always seen the word  
"horizon" in order to distinguish the concept from the meaning of the  
word "domain" in Domain Name System.

> That gives us one name space, but different responses to that  
> translation request depending on the source of the request. DNS64  
> does largely the same thing, but commits the gross and indecent act  
> of saying out loud that it does so.

The "gross indecency" here is, apparently, admitting in public that we  
cannot escape the need to amend the DNS standards to recognize, for  
the first time, that we need more than one public horizon, i.e. the  
V4V6COEX public horizon and the IPv6 public horizon.

I do not see how we can escape that problem except by deprecating IPv4- 
only operation.  You want to talk to IPv6 nodes?  Then get yourself an  
IPv6 stack and a default route. Otherwise, have a coke and a smile,  
and shut the frell up.  I'm assuming that rough consensus is still  
leaning away from that, so can we please face up to the reality that  
multiple public DNS horizons are the way out of this?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:42:11 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF1303A6AE8;
	Wed,  1 Oct 2008 11:42:11 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 702D23A6AEC
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3MghfdZ04+-M for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:42:09 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id B0A5A3A69DF
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:42:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208,217";a="22458079"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 01 Oct 2008 18:42:14 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m91IgEiT006643
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 11:42:14 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91IgDtp012762
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 18:42:14 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 14:42:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Oct 2008 14:42:13 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42378@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A+P work
Thread-Index: Ackj9WudI2pglmPpSdC1PmAV8LwaJw==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <v4v6interim@ietf.org>
X-OriginalArrivalTime: 01 Oct 2008 18:42:13.0735 (UTC)
	FILETIME=[6BAED770:01C923F5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1939; t=1222886534;
	x=1223750534; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20A+P=20work |Sender:=20;
	bh=BJrYD7vzAOvKVa4eHbeMiwLdW5pGFIR+Hq2LfAhOZo8=;
	b=HrgeksOJTGKOVM+YE6MLBNTPDUfNW+VS033wY/5Mx3/GxicTx2DXKMS2N2
	FYtBKMk2FJqhuTvqtXoJR6qS3CcghXeT/8q37VfqfBJuQMwars6Y+Sk/Vkyh
	X+n4nSLIwu;
Authentication-Results: sj-dkim-4; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [v4v6interim] A+P work
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1462932805=="
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1462932805==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C923F5.6B819CCF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C923F5.6B819CCF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

If an Internet-draft is written that describes A+P in more detail that
would be very helpful.  Maybe such a draft already exists in which case,
please point it to me.  We need more details like showing some sample
packet flows and address assignments between the home CPE Router and the
BR, or things like, is using port in the synthetic IPv6 address just an
optimization or is use of port totally necessary.=20
=20
Thanks.
=20
Hemant

------_=_NextPart_001_01C923F5.6B819CCF
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D827223818-01102008><FONT face=3DArial size=3D2>If an =
Internet-draft=20
is written that describes A+P in more detail that would be very =
helpful.&nbsp;=20
Maybe such a draft already exists in which case, please point it to =
me.&nbsp; We=20
need more details like showing some sample packet flows and address =
assignments=20
between the home CPE Router and the BR, or things like, is using port in =
the=20
synthetic IPv6 address just an optimization or is use of port totally=20
necessary.&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D827223818-01102008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D827223818-01102008><FONT face=3DArial=20
size=3D2>Thanks.</FONT></SPAN></DIV>
<DIV><SPAN class=3D827223818-01102008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D827223818-01102008><FONT face=3DArial=20
size=3D2>Hemant</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C923F5.6B819CCF--

--===============1462932805==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--===============1462932805==--


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:49:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 424C23A6909;
	Wed,  1 Oct 2008 11:49:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E21528C14B
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=0.210, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e8ZWHJcDwdRZ for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:49:16 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id 6D3C43A6405
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:49:16 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m91Ilvpe020834;
	Thu, 2 Oct 2008 03:47:57 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m91IljjN045292; Thu, 2 Oct 2008 03:47:48 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <59DA04E5-CE06-43EB-9DDA-54FF3CE82166@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 2 Oct 2008 03:47:44 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Good point!

I also stated similar same in my latest version of snatpt.

http://www.ietf.org/internet-drafts/draft-miyata-v6ops-snatpt-02.txt


...miyata



On 2008/10/02, at 1:24, Iljitsch van Beijnum wrote:

> There are several advantages of having a well known prefix for NAT- 
> PT/NAT64 or even DS-lite. For the former, synthetic AAAA records are  
> no longer necessary and can be ignored by updated hosts, for the  
> latter there is no longer any need have a configuration mechanism.  
> Upgraded IPv6 hosts can simply start sending packets to IPv4  
> destinations to the translator when they detect that they don't have  
> actual IPv4 connectivity, rather than depend on external entities to  
> provide configuration information, in AAAA records or explicitly. An  
> additional benefit would be that NAT64 could even support IPv4  
> applications this way.
>
> On the other hand, there are operational benefits to having a  
> configurable prefix: this makes it possible to direct traffic that  
> is to be translated to a specific translator without routing  
> contortions.
>
> What I suggest is that we do both. We present a well known prefix of  
> a combined NAT-PT/NAT64/DS-lite translator to transport protocols  
> and applications, but we allow packets destined for that prefix to  
> have their destination address rewritten into a specific prefix.  
> Because the packets are translated later anyway, this causes no  
> problems. Also, if we allow longest match first rules for the well  
> known to specific prefix translation table, this makes it very easy  
> to support private translators for RFC 1918 destinations along with  
> global translators for global IPv4 destinations.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 11:56:22 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D16DC3A6813;
	Wed,  1 Oct 2008 11:56:22 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5D9453A6813
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 11:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zprnD165sB+D for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 11:56:19 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id 878EA3A6405
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 11:56:19 -0700 (PDT)
Received: from ([128.244.96.97])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.117288064;
	Wed, 01 Oct 2008 14:56:23 -0400
Message-ID: <48E3C7D4.3040408@innovationslab.net>
Date: Wed, 01 Oct 2008 14:56:20 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42378@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42378@xmb-rtp-20e.amer.cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] A+P work
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Hemant,
      The following link was posted to the mailing list:
http://mice.cs.columbia.edu/getTechreport.php?techreportID=560

It is the current definition of A+P.

Regards,
Brian

Hemant Singh (shemant) wrote:
> If an Internet-draft is written that describes A+P in more detail that 
> would be very helpful.  Maybe such a draft already exists in which case, 
> please point it to me.  We need more details like showing some sample 
> packet flows and address assignments between the home CPE Router and the 
> BR, or things like, is using port in the synthetic IPv6 address just an 
> optimization or is use of port totally necessary. 
>  
> Thanks.
>  
> Hemant
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 12:02:24 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BAB128C1E0;
	Wed,  1 Oct 2008 12:02:24 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8DA1B28C1E0
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 12:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id of3VHNgr6PdC for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 12:02:22 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 8F05D3A680B
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 12:00:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="22908386"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 01 Oct 2008 19:00:49 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91J0naG014407; 
	Wed, 1 Oct 2008 15:00:49 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91J0nqH014298;
	Wed, 1 Oct 2008 19:00:49 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 15:00:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Oct 2008 15:00:48 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4237A@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <48E3C7D4.3040408@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] A+P work
Thread-Index: Ackj93FZkLcarWibR6CMzKFzHNelnQAAA4Zw
References: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42378@xmb-rtp-20e.amer.cisco.com>
	<48E3C7D4.3040408@innovationslab.net>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Brian Haberman" <brian@innovationslab.net>
X-OriginalArrivalTime: 01 Oct 2008 19:00:49.0352 (UTC)
	FILETIME=[04A47C80:01C923F8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1607; t=1222887649;
	x=1223751649; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20RE=3A=20[v4v6interim]=20A+P=20work |Sender:=20
	|To:=20=22Brian=20Haberman=22=20<brian@innovationslab.net>;
	bh=6T5MF/NcRRcYXR/g3IvKHjYQY+XisPP1M4PsADt7CRg=;
	b=XBZ3RBFQkENGKcDdlb2TsV+OwnJfAcsP70kqc06JXBLiRmadKPgshBvwKR
	YwI9ndB85DWk+SOrazARf0gOEieXQDAsoXYkX59MYjKI9ElnjdVVRNs4ZlM5
	OA8AGxxyD7;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] A+P work
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Brian,

Yes, I know of this link but IMHO the details in this paper are not
sufficient for such work to be accepted as a solution by IETF.  The
authors need to provide more details like what I asked for.  Either the
paper gets updated or a new I-D should be written.  I'd be happy to work
with the authors to give them a list of what all needs more details
besides just two items I listed below.

Thanks.

Hemant 

-----Original Message-----
From: Brian Haberman [mailto:brian@innovationslab.net] 
Sent: Wednesday, October 01, 2008 2:56 PM
To: Hemant Singh (shemant)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] A+P work

Hemant,
      The following link was posted to the mailing list:
http://mice.cs.columbia.edu/getTechreport.php?techreportID=560

It is the current definition of A+P.

Regards,
Brian

Hemant Singh (shemant) wrote:
> If an Internet-draft is written that describes A+P in more detail that

> would be very helpful.  Maybe such a draft already exists in which 
> case, please point it to me.  We need more details like showing some 
> sample packet flows and address assignments between the home CPE 
> Router and the BR, or things like, is using port in the synthetic IPv6

> address just an optimization or is use of port totally necessary.
>  
> Thanks.
>  
> Hemant
> 
> 
> ----------------------------------------------------------------------
> --
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 12:03:47 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D1FE28C1BC;
	Wed,  1 Oct 2008 12:03:47 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E7173A67B3
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 12:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2iQV7Ige0rT6 for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 12:03:45 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36])
	by core3.amsl.com (Postfix) with ESMTP id 5701F28C1BC
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 12:03:32 -0700 (PDT)
Received: from traingw.ericsson.ca ([192.75.88.176] helo=rmac.psg.com)
	by ran.psg.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1Kl6zI-00041Y-0Z; Wed, 01 Oct 2008 19:03:52 +0000
Message-ID: <48E3C997.4060703@psg.com>
Date: Wed, 01 Oct 2008 15:03:51 -0400
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42378@xmb-rtp-20e.amer.cisco.com>
	<48E3C7D4.3040408@innovationslab.net>
In-Reply-To: <48E3C7D4.3040408@innovationslab.net>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] A+P work
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> http://mice.cs.columbia.edu/getTechreport.php?techreportID=560
>> If an Internet-draft is written that describes A+P in more detail that
>> would be very helpful.

two of the authors are ex-ietfers who have written more than their share
of internet drafts and have taken vows of not writing any more.  the
other two of the authors have never written i-ds and are aghast at
internet drafts.  :)

so, if someone wants to work with us to author a draft, i imagine we
would be amenable.

randy
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 12:18:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 285273A67A6;
	Wed,  1 Oct 2008 12:18:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 392513A68D3
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 12:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.484
X-Spam-Level: 
X-Spam-Status: No, score=-106.484 tagged_above=-999 required=5
	tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p0dMK8fQElYW for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 12:18:26 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 717433A67A6
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 12:18:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="91444921"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 01 Oct 2008 19:18:50 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91JIo4N021986; 
	Wed, 1 Oct 2008 12:18:50 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m91JIobI026401;
	Wed, 1 Oct 2008 19:18:50 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:18:50 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:18:49 -0700
Message-Id: <0C04CA90-BA84-42A3-829F-C313359DB0A4@cisco.com>
From: Fred Baker <fred@cisco.com>
To: bmanning@vacation.karoshi.com
In-Reply-To: <20081001183005.GA4659@vacation.karoshi.com.>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 15:18:48 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<20081001180949.GA4282@vacation.karoshi.com.>
	<4AEC856D-6418-44A7-84E7-79A64913A1A2@cisco.com>
	<20081001183005.GA4659@vacation.karoshi.com.>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 19:18:49.0490 (UTC)
	FILETIME=[88747720:01C923FA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1354; t=1222888731;
	x=1223752731; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Single=20namespace |Sender:=20;
	bh=K+dHLUSOS7K/HafUwriNdCZCJo7Eh51zM61X7T3XUNo=;
	b=WTed/DzmalDWljL50m+HEF8S0NhC4FhAYj24/sLJaGecq5RZ4To+TP4qWd
	SHo6ZP0Mb1BrPSDcc9DTQDdWCcNUtRR32pWPau2puIAJgUqZCCFtRchoOYjb
	t5ZR/Q9GpF5F7EM3Xq4F9PFUGbx+vYyZ+bgdfNCRqM5I3r2BZumZk=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 2:30 PM, bmanning@vacation.karoshi.com wrote:
>> It gets a AAAA request from some host, sends a request for an A  
>> record
>> (perhaps o itself), gets the A record response, generates a AAAA
>> record from it, and sends that as a reply to the original request.
>
> 	so the DNS64 app is configured in the endsystems as the
> 	caching nameserver for the domain.  in that case, there is
> 	an operational question or  two.

not sure how that works in a real domain. IVI and NAT64 configure it  
in the common server.

>>> If this is a plausable explaination, then I would posit that the
>>> creation of
>>> DNS64 is injecting a MITM vector that is unreasonable.
>>
>> Any form of translation is a MITM vector. If you find translation
>> unreasonable, then yes you will find that vector unreasonable. If you
>> find translation necessary, I don't think you can avoid the
>> possibility that the translator is a MITM vector.
>
> 	right - but keeping the translation at the network layer instead
> 	of the application layer reduces complexity.

arg.

you're doing DNS name translation at the network layer?

You sound like my marketing people.

> 	translateable is not an artifact of the DNS, thats properly the
> 	perview of a NAT.

and you found this in a document that described a NAT.

I'm lost.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 12:21:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E9A053A6AEC;
	Wed,  1 Oct 2008 12:21:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CE8E3A6A8F
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 12:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6Srp5Ij9diUt for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 12:21:36 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25])
	by core3.amsl.com (Postfix) with ESMTP id 24BD33A6909
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 12:21:35 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by mail.nttv6.net (8.14.3/8.14.3) with ESMTP id m91JLvNt066768;
	Thu, 2 Oct 2008 04:21:58 +0900 (JST)
	(envelope-from arifumi@nttv6.net)
Message-Id: <7BC3C85A-2EB2-4123-A9BE-C2E71D3224FF@nttv6.net>
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 04:22:37 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0
	(mail.nttv6.net [127.0.0.1]); Thu, 02 Oct 2008 04:21:58 +0900 (JST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Another point.

If we have a well-known prefix for translation, we can implement  
address selection policy simply. If the to-be-translated prefix is  
defined to be 3000::/16, we can configure client host's policy table  
so that to-be-translated prefix have less priority than IPv6 and  
possibly IPv4.

Moreover, if we put this rule in the *default* policy table, we can  
control a client host's address selection behavior in the following way.

If a server administrator put a 6->4 translater in front of his  
server, and he uses 3000::/16 prefix for the DNS AAAA record as well  
as a normal A record, IPv4 traffic won't decrease so much. This is  
because those client hosts with IPv6 address only connect to the  
server through the IPv6 network and the translator.
If he uses non-3000::/16 prefix for the DNS AAAA record and uses a  
normal A record, the server will have much traffic through IPv6, as  
far as most of the client hosts don't loose IPv4 address.

Even if we put a translator on client-side, we can make use of this  
address selection policy by deciding which prefix to use for the dummy  
prefix.

Kindest Regards.

On 2008/10/02, at 1:24, Iljitsch van Beijnum wrote:

> There are several advantages of having a well known prefix for NAT- 
> PT/NAT64 or even DS-lite. For the former, synthetic AAAA records are  
> no longer necessary and can be ignored by updated hosts, for the  
> latter there is no longer any need have a configuration mechanism.  
> Upgraded IPv6 hosts can simply start sending packets to IPv4  
> destinations to the translator when they detect that they don't have  
> actual IPv4 connectivity, rather than depend on external entities to  
> provide configuration information, in AAAA records or explicitly. An  
> additional benefit would be that NAT64 could even support IPv4  
> applications this way.
>
> On the other hand, there are operational benefits to having a  
> configurable prefix: this makes it possible to direct traffic that  
> is to be translated to a specific translator without routing  
> contortions.
>
> What I suggest is that we do both. We present a well known prefix of  
> a combined NAT-PT/NAT64/DS-lite translator to transport protocols  
> and applications, but we allow packets destined for that prefix to  
> have their destination address rewritten into a specific prefix.  
> Because the packets are translated later anyway, this causes no  
> problems. Also, if we allow longest match first rules for the well  
> known to specific prefix translation table, this makes it very easy  
> to support private translators for RFC 1918 destinations along with  
> global translators for global IPv4 destinations.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 12:22:19 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 146F43A6909;
	Wed,  1 Oct 2008 12:22:19 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2AF63A6909
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 12:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.492
X-Spam-Level: 
X-Spam-Status: No, score=-106.492 tagged_above=-999 required=5
	tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ttI5JrRwjfek for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 12:22:17 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 029DB3A68D3
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 12:22:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="166832098"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 19:22:33 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m91JMXMa006097; 
	Wed, 1 Oct 2008 12:22:33 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91JMXma027918;
	Wed, 1 Oct 2008 19:22:33 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:22:33 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:22:29 -0700
Message-Id: <9E00EDE2-A4D2-445B-8932-ADE14C5574CD@cisco.com>
From: Fred Baker <fred@cisco.com>
To: james woodyatt <jhw@apple.com>
In-Reply-To: <090C6392-9082-4660-AE68-FA384B788C03@apple.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 15:22:26 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 19:22:29.0878 (UTC)
	FILETIME=[0BD10160:01C923FB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1636; t=1222888953;
	x=1223752953; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Single=20namespace
	|Sender:=20; bh=r99XwGdBtCyukTD+SdAv23prYWTbXdp++5UR93H7y2E=;
	b=BccqEdlY6G3xCw1Y3v3lwKIa4T8vmgB9ikJyoyX3LysZMosUzlVr2rOyIM
	fc6pOsGBSnseIqF8K8ma/enouUfmM8elXXAiV/qu2vFIoNDqbO6J/lYs0szT
	s+6WQ1Q5tN;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 2:34 PM, james woodyatt wrote:

> On Oct 1, 2008, at 10:42, Fred Baker wrote:
>>
>> The way we usually implement this kind of thing is to have multiple  
>> name servers, one of which is accessible from outside and the other  
>> is accessible from inside.
>
> The reason I've been having a hard time following this discussion is  
> that you're using the word "domain" where I've always seen the word  
> "horizon" in order to distinguish the concept from the meaning of  
> the word "domain" in Domain Name System.

The horizon is the edge of the routing domain.

>> That gives us one name space, but different responses to that  
>> translation request depending on the source of the request. DNS64  
>> does largely the same thing, but commits the gross and indecent act  
>> of saying out loud that it does so.
>
> The "gross indecency" here is, apparently, admitting in public that  
> we cannot escape the need to amend the DNS standards to recognize,  
> for the first time, that we need more than one public horizon, i.e.  
> the V4V6COEX public horizon and the IPv6 public horizon.

perhaps. I find such things a little idiotic. It's one thing to say  
you don't want to do it; there are a lot of things I don't like to do  
and want guidance when I am forced to do them. Pretending it doesn't  
exist and going bats when someone points out the elephant in the room  
isn't very productive.

> I do not see how we can escape that problem except by deprecating  
> IPv4-only operation.

You get my vote. Talk with the network operators. Do you happen to  
know any? :-)
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:08:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA49E3A6AB3;
	Wed,  1 Oct 2008 13:08:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD8393A6A8F
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5
	tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f3CmBogy4G6E for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:08:25 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id DFDB93A67B3
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:08:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,345,1220227200"; d="scan'208";a="166861733"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 01 Oct 2008 20:08:00 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m91K80LZ019924; 
	Wed, 1 Oct 2008 13:08:00 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m91K7xBv007968;
	Wed, 1 Oct 2008 20:08:00 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 13:07:57 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 13:07:56 -0700
Message-Id: <3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 16:07:55 -0400
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 20:07:56.0671 (UTC)
	FILETIME=[651C98F0:01C92401]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=432; t=1222891680; x=1223755680;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20The=20NAT64=20prefix
	|Sender:=20; bh=SKBMR+C8WQu30yM16RyWJ2huY5/Uaehw8uxQxbQKno0=;
	b=Pl6f1sfq5pLDsMGbTPlMEJDH06h7TpMYtGchF6QUox/JgzeMKdzLR+/9Sq
	2bFalOr0Vm4X+ZdaTgtJE/689ycErW0jcbY2cdjRkWgwj5e33ebJQIQxyiAB
	ktGIx47qFU;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 12:24 PM, Iljitsch van Beijnum wrote:

> There are several advantages of having a well known prefix for NAT- 
> PT/NAT64 or even DS-lite.

Maybe I'm missing something.

If there exists a AAAA record for a name, there is no reason to  
translate an A record to create one. Regardless of the host type, if a  
native AAAA record exists, a translated record will never be presented.

What's the issue?
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:28:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DED83A6C57;
	Wed,  1 Oct 2008 13:28:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F25063A6C57
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UY5nuUvvBvwK for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:28:54 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net
	[207.173.203.159])
	by core3.amsl.com (Postfix) with ESMTP id 2F3513A6AF8
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:28:54 -0700 (PDT)
Received: from commandprompt.com (traingw.ericsson.ca [192.75.88.176])
	(authenticated bits=0)
	by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m91KX0Cr015592
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 13:33:02 -0700
Date: Wed, 1 Oct 2008 16:29:15 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081001202914.GA34476@commandprompt.com>
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(lists.commandprompt.com [207.173.203.159]);
	Wed, 01 Oct 2008 13:33:03 -0700 (PDT)
Subject: [v4v6interim] "No DNS changes" in
	draft-wing-nat-pt-replacement-comparison-01
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I think I understand now what my problem was that I was trying to
state (incompetently, I think) at the mic.

In the overview of the items we were to discuss this afternoon, and in
draft-wing-nat-pt-replacement-comparison-01 table 2, we have this
claim:

   +--------------+-----------------+------------+---------------------+
   |   Proposal   |  ISP's Internal | DNS Impact |  Carrier Grade NAT  |
   |              |     Network     |            |                     |
   +--------------+-----------------+------------+---------------------+
   |    A+P-v4    |       IPv4      |  no change |     (no CGN, if     |
   |              |   destination   |            |   subscriber's NAT  |
   |              |   port routing  |            |   support A+P NAT)  |
   +--------------+-----------------+------------+---------------------+
   |    A+P-v6    |    IPv4/IPv6    |  no change |     (no CGN, if     |
   |              |      tunnel     |            |   subscriber's NAT  |
   |              |                 |            |   support A+P NAT)  |
   +--------------+-----------------+------------+---------------------+

I'm confused by the DNS Impact claim of "no change" here, if the
suggestion is that A+P is going to help v6-only clients talk to the
target hosts.  Is it instead the case that A+P is just not going to
help v6-only hosts?  That is, unless I'm misunderstanding badly (and
it wouldn't be the first time), a v6-only host can't talk to a v4-only
host using A+P without getting some way of talking to v4 networks,
period.  So maybe the DNS Impact in that table should be like NAT444?

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:44:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17BC23A69DF;
	Wed,  1 Oct 2008 13:44:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B50DE3A69DF
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:44:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.175, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DW4y2+OxRgUH for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:44:26 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id B78E43A6918
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:44:25 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m91KhWov027145;
	Thu, 2 Oct 2008 05:43:32 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m91KhMsm053574; Thu, 2 Oct 2008 05:43:23 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <71C69E1E-C339-4DD6-AFED-4EAE1DDD1040@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 2 Oct 2008 05:43:22 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred,

You are right when we use currently proposed DNS rewriting.
But, we may have some exception.

e.g., When the administrator place Translator box in front of
Dual stack server, the administrator may register both
native IPv6 address and synthesized address as AAAA RR.

Thanks,

....miyata


On 2008/10/02, at 5:07, Fred Baker wrote:

>
> On Oct 1, 2008, at 12:24 PM, Iljitsch van Beijnum wrote:
>
>> There are several advantages of having a well known prefix for NAT- 
>> PT/NAT64 or even DS-lite.
>
> Maybe I'm missing something.
>
> If there exists a AAAA record for a name, there is no reason to  
> translate an A record to create one. Regardless of the host type, if  
> a native AAAA record exists, a translated record will never be  
> presented.
>
> What's the issue?
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:47:51 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F29F3A6C8D;
	Wed,  1 Oct 2008 13:47:51 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E6323A6890
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.505
X-Spam-Level: 
X-Spam-Status: No, score=-106.505 tagged_above=-999 required=5
	tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IJ+7DZQwUBrO for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:47:49 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 183983A6C57
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:46:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,345,1220227200"; d="scan'208";a="85555910"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 01 Oct 2008 20:46:21 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91KkLap023506; 
	Wed, 1 Oct 2008 13:46:21 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91KkL2O013455;
	Wed, 1 Oct 2008 20:46:21 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 13:45:31 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 13:45:30 -0700
Message-Id: <80275B0D-CA53-4805-B9BA-2309871CF19B@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Hiroshi MIYATA <miyata@tahi.org>
In-Reply-To: <71C69E1E-C339-4DD6-AFED-4EAE1DDD1040@tahi.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 16:45:29 -0400
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
	<71C69E1E-C339-4DD6-AFED-4EAE1DDD1040@tahi.org>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 20:45:30.0665 (UTC)
	FILETIME=[A498C990:01C92406]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=218; t=1222893981; x=1223757981;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20The=20NAT64=20prefix
	|Sender:=20; bh=nbWFEkUR7GUjd4CbCGZAla8C5ElFsESViNt2cfltDOc=;
	b=eukac+ldILr6y73xamg+vqcweu23QGB7q7SODbzxL2KBnwN4bTBrunbX98
	FqkB9r+rcFNZkA1Oopd6rwCN1sV2yInbtzW5v8EVI08/6bky8RoacpwxGx0k
	jLwmrNhiZaiqA18Cv76SiL4uJ4XUcdYRkDPOR9qzfm4eJ6C1zzMl0=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 1, 2008, at 4:43 PM, Hiroshi MIYATA wrote:

> the administrator may register both
> native IPv6 address and synthesized address as AAAA RR.

that's his choice. we can recommend he choose differently :-)
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:48:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41E493A6C57;
	Wed,  1 Oct 2008 13:48:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 175053A69DF
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 41Ml0bp6mHXB for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:48:25 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25])
	by core3.amsl.com (Postfix) with ESMTP id 6A5463A6C7F
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:48:10 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by mail.nttv6.net (8.14.3/8.14.3) with ESMTP id m91KmEF1067139;
	Thu, 2 Oct 2008 05:48:15 +0900 (JST)
	(envelope-from arifumi@nttv6.net)
Message-Id: <311C944E-1EE0-4CDF-AED9-E1A51E42EAFB@nttv6.net>
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 05:48:55 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0
	(mail.nttv6.net [127.0.0.1]); Thu, 02 Oct 2008 05:48:16 +0900 (JST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On 2008/10/02, at 5:07, Fred Baker wrote:

>
> On Oct 1, 2008, at 12:24 PM, Iljitsch van Beijnum wrote:
>
>> There are several advantages of having a well known prefix for NAT- 
>> PT/NAT64 or even DS-lite.
>
> Maybe I'm missing something.
>
> If there exists a AAAA record for a name, there is no reason to  
> translate an A record to create one. Regardless of the host type, if  
> a native AAAA record exists, a translated record will never be  
> presented.
>
> What's the issue?

I believe this is about well-known prefix to make a synthetic IPv6  
address from IPv4 address. On client-side translation, you can use  
this prefix to send a packet which is translated into an IPv4 packet  
somewhere in the network.

I mentioned in my previous e-mail server-side translation case. In  
that case, IPv4 only server can serve to IPv6 clients through the  
translator. Here, a server administrator can use the well-known prefix  
to make AAAA record.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:53:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C3F83A694D;
	Wed,  1 Oct 2008 13:53:53 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33FC13A6918
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0xSPHhZCIbxz for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:53:51 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id 4AEFC3A6767
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:53:51 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m91KqLvj027718;
	Thu, 2 Oct 2008 05:52:21 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m91KqBAV054348; Thu, 2 Oct 2008 05:52:12 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <586D1A61-4F16-4070-BD3F-8E41A3A1F2CB@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <80275B0D-CA53-4805-B9BA-2309871CF19B@cisco.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 2 Oct 2008 05:52:11 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
	<71C69E1E-C339-4DD6-AFED-4EAE1DDD1040@tahi.org>
	<80275B0D-CA53-4805-B9BA-2309871CF19B@cisco.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On 2008/10/02, at 5:45, Fred Baker wrote:

>
> On Oct 1, 2008, at 4:43 PM, Hiroshi MIYATA wrote:
>
>> the administrator may register both
>> native IPv6 address and synthesized address as AAAA RR.
>
> that's his choice. we can recommend he choose differently :-)

If he can know the client address, it is possible.
But if he choose one from his assigned prefix, both are very close.
So, longest match/shortest match depends on the client side.
Thus, very different prefix is preferable. ;-)

...miyata
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 13:59:08 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 874B93A6836;
	Wed,  1 Oct 2008 13:59:08 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 40FA33A6836
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 13:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level: 
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.132, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WDw+2pm1Oxyw for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 13:59:06 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id 51E813A6767
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 13:59:06 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m91Kw8Dg027871;
	Thu, 2 Oct 2008 05:58:08 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m91Kvw77054579; Thu, 2 Oct 2008 05:57:59 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <2BA4694D-0F3F-421D-8F53-ABCD7CB14816@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Hiroshi MIYATA <miyata@tahi.org>
In-Reply-To: <586D1A61-4F16-4070-BD3F-8E41A3A1F2CB@tahi.org>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 2 Oct 2008 05:57:46 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
	<71C69E1E-C339-4DD6-AFED-4EAE1DDD1040@tahi.org>
	<80275B0D-CA53-4805-B9BA-2309871CF19B@cisco.com>
	<586D1A61-4F16-4070-BD3F-8E41A3A1F2CB@tahi.org>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Mind you, it does not mean I recommend to use well-known address in  
public. ;-)

....miyata


On 2008/10/02, at 5:52, Hiroshi MIYATA wrote:

>
> On 2008/10/02, at 5:45, Fred Baker wrote:
>
>>
>> On Oct 1, 2008, at 4:43 PM, Hiroshi MIYATA wrote:
>>
>>> the administrator may register both
>>> native IPv6 address and synthesized address as AAAA RR.
>>
>> that's his choice. we can recommend he choose differently :-)
>
> If he can know the client address, it is possible.
> But if he choose one from his assigned prefix, both are very close.
> So, longest match/shortest match depends on the client side.
> Thus, very different prefix is preferable. ;-)
>
> ...miyata
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 14:08:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D7FA03A68A1;
	Wed,  1 Oct 2008 14:08:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EE673A6767
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 14:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X2Q8NM+ZAmAV for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 14:08:12 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by core3.amsl.com (Postfix) with ESMTP id A6F183A68E6
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 14:08:12 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so376647wag.5
	for <v4v6interim@ietf.org>; Wed, 01 Oct 2008 14:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=UErRPPMAibzogxwUHdrxnRZhmv3SCLTJII28eTSKaX8=;
	b=d0zgonKMugqLAQLq7Zv8HW7Wqo1+v+yWPBLe8ODhKhx0DGTFE4RfUAnHC1gFGZQNCV
	UNIU0Ef87KJtEmeBuj8WvctjnjxDa8+GX2uRyX5mvztMw4XbkeIcdaROZ0TFPv+67Wje
	//Q4pqK7Tx47m9yVWVJCz/wxblfH6cQOFqmEg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=uiWKuXwwlR+V9+CslKtLWQecf6DmgnxgtAqCJVcFo5dZrHLZ0o6nyYQAoPvANK4l6E
	ZLkpJNizNhw79twzL6R5ImE1tSiM99sqPPNkg2QdEXBJPsT3IRsGlchzahHSznm4ssIF
	6Uigcv6/sGD4A+og1iVVb+kaRyCZbckCeKk+I=
Received: by 10.114.182.1 with SMTP id e1mr9856765waf.143.1222895316320;
	Wed, 01 Oct 2008 14:08:36 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l37sm1748563waf.23.2008.10.01.14.08.33
	(version=SSLv3 cipher=RC4-MD5); Wed, 01 Oct 2008 14:08:35 -0700 (PDT)
Message-ID: <48E3E6D0.2050100@gmail.com>
Date: Thu, 02 Oct 2008 10:08:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
In-Reply-To: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Iljitsch,

On 2008-10-02 05:24, Iljitsch van Beijnum wrote:
> There are several advantages of having a well known prefix for
> NAT-PT/NAT64 or even DS-lite. For the former, synthetic AAAA records are
> no longer necessary and can be ignored by updated hosts, for the latter
> there is no longer any need have a configuration mechanism. Upgraded
> IPv6 hosts can simply start sending packets to IPv4 destinations to the
> translator when they detect that they don't have actual IPv4
> connectivity, rather than depend on external entities to provide
> configuration information, in AAAA records or explicitly. An additional
> benefit would be that NAT64 could even support IPv4 applications this way.
> 
> On the other hand, there are operational benefits to having a
> configurable prefix: this makes it possible to direct traffic that is to
> be translated to a specific translator without routing contortions.
> 
> What I suggest is that we do both. We present a well known prefix of a
> combined NAT-PT/NAT64/DS-lite translator to transport protocols and
> applications, but we allow packets destined for that prefix to have
> their destination address rewritten into a specific prefix. Because the
> packets are translated later anyway, this causes no problems. Also, if
> we allow longest match first rules for the well known to specific prefix
> translation table, this makes it very easy to support private
> translators for RFC 1918 destinations along with global translators for
> global IPv4 destinations.

I agree with all that, but it's important to add a very strong set of
operational recommendations on how the two prefixes are advertised in
both internal and external routing. Exactly as with 6to4 and Teredo relays,
if the prefixes are announced outside the appropriate scope, all sorts
of undesirable traffic patterns (and black holes) will result.

   Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 14:21:10 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E80228C1E2;
	Wed,  1 Oct 2008 14:21:10 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F0E9C28C1E2
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 14:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d7ncy5Zh3Gmt for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 14:21:08 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
	by core3.amsl.com (Postfix) with ESMTP id 197B73A68D3
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 14:20:05 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so772804wfd.31
	for <v4v6interim@ietf.org>; Wed, 01 Oct 2008 14:20:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=uv4PlwauvFGDickZ5n6iFPEGDlwZDUdi9YeHS/8LiU0=;
	b=w3lrOgqhl43IaP52lu2uk68bDo0LNqjdUlBbUfB+0XKAyiB30nyw/ZXAcDnmTLQx26
	TKN+CxiyV7XCligJVlG97uEM6/jpQ9vLE9URA73EMtapvrXhTgZUm/I8QGpA4AHgYrf2
	vSoy6P9xBg3vV8/voWDTGsJ7oocPGAwGgNHnk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=JRZ+0/8akgerxPCNfWVlDjDazRA6uVRHKjMwDFKROoHCfqFwZtDsKUFIKrjP3B6Il2
	ofiDmQjClomyNS41nxs5yy9H484xA3lFp5aESMi7qkMgGHN6H6dukqua1LGQHeWcl9ky
	c+kAmJtZbj9azDBJbJUD5UQXvamK5DtqQ8Rws=
Received: by 10.114.25.3 with SMTP id 3mr9924748way.22.1222896028954;
	Wed, 01 Oct 2008 14:20:28 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id m17sm1791383waf.35.2008.10.01.14.20.26
	(version=SSLv3 cipher=RC4-MD5); Wed, 01 Oct 2008 14:20:28 -0700 (PDT)
Message-ID: <48E3E998.3020909@gmail.com>
Date: Thu, 02 Oct 2008 10:20:24 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<9E00EDE2-A4D2-445B-8932-ADE14C5574CD@cisco.com>
In-Reply-To: <9E00EDE2-A4D2-445B-8932-ADE14C5574CD@cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

The fact of life is that we already have an untold number
of DNS namespaces. Offering different views of the
namespace inside and outside corporate networks is standard
practice. Now this offends the computer science view of the
DNS as creating a single, formal, unique namespace but it hasn't
been that way for at least ten years.

Although DNS64 is even more offensive to the computer science
view, I can't see any realistic solution to the v4only/v6 only
interworking problem that doesn't *require* different views
of the namespace on the two sides, created dynamically to
match the translation state.

   Brian
   Dept of Computer Science
   Univ of Auckland


On 2008-10-02 08:22, Fred Baker wrote:
> 
> On Oct 1, 2008, at 2:34 PM, james woodyatt wrote:
> 
>> On Oct 1, 2008, at 10:42, Fred Baker wrote:
>>>
>>> The way we usually implement this kind of thing is to have multiple
>>> name servers, one of which is accessible from outside and the other
>>> is accessible from inside.
>>
>> The reason I've been having a hard time following this discussion is
>> that you're using the word "domain" where I've always seen the word
>> "horizon" in order to distinguish the concept from the meaning of the
>> word "domain" in Domain Name System.
> 
> The horizon is the edge of the routing domain.
> 
>>> That gives us one name space, but different responses to that
>>> translation request depending on the source of the request. DNS64
>>> does largely the same thing, but commits the gross and indecent act
>>> of saying out loud that it does so.
>>
>> The "gross indecency" here is, apparently, admitting in public that we
>> cannot escape the need to amend the DNS standards to recognize, for
>> the first time, that we need more than one public horizon, i.e. the
>> V4V6COEX public horizon and the IPv6 public horizon.
> 
> perhaps. I find such things a little idiotic. It's one thing to say you
> don't want to do it; there are a lot of things I don't like to do and
> want guidance when I am forced to do them. Pretending it doesn't exist
> and going bats when someone points out the elephant in the room isn't
> very productive.
> 
>> I do not see how we can escape that problem except by deprecating
>> IPv4-only operation.
> 
> You get my vote. Talk with the network operators. Do you happen to know
> any? :-)
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 14:24:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 506F83A6912;
	Wed,  1 Oct 2008 14:24:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EC943A67A6
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 14:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.117, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jAQL3nhXC5zg for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 14:24:25 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id 26A6A3A6912
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 14:24:25 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m91LNWPI028360;
	Thu, 2 Oct 2008 06:23:32 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m91LNL5D054989; Thu, 2 Oct 2008 06:23:22 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <84C4341F-368E-4FDE-8421-BD28474AB1CB@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <48E3E6D0.2050100@gmail.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Thu, 2 Oct 2008 06:23:21 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<48E3E6D0.2050100@gmail.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Indeed!

...miyata

On 2008/10/02, at 6:08, Brian E Carpenter wrote:

> it's important to add a very strong set of
> operational recommendations on how the two prefixes are advertised in
> both internal and external routing.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 14:37:22 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C46D3A6BE3;
	Wed,  1 Oct 2008 14:37:22 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82B743A6BE3
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 14:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.511
X-Spam-Level: 
X-Spam-Status: No, score=-106.511 tagged_above=-999 required=5
	tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X-7b1p51luKj for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 14:37:20 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 1DB7C3A6846
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 14:37:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,346,1220227200"; 
	d="txt'?scan'208";a="105912358"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 01 Oct 2008 21:37:37 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m91LbbAm028099; 
	Wed, 1 Oct 2008 14:37:37 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m91Lbb5a003019;
	Wed, 1 Oct 2008 21:37:37 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 14:37:37 -0700
Received: from [192.168.3.103] ([10.21.89.125]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 14:37:36 -0700
Message-Id: <CFB435D2-1213-4920-9A3A-A7BB48D94F58@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Dan Wing <dwing@cisco.com>, Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/mixed; boundary=Apple-Mail-661--223279751
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 17:37:36 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 01 Oct 2008 21:37:36.0832 (UTC)
	FILETIME=[EBF00400:01C9240D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8602; t=1222897057;
	x=1223761057; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Notes=20from=20day=201 |Sender:=20;
	bh=elmu66R8lLbxpgk0U3gO9bFOxVtc7bmt31y4esHfqSI=;
	b=psdt9aS5xHVIa0sEkxky7qDOl2c3cWrQGhgelW5qW4XOdlbHLRij8HMSaS
	xNZyv/WKWTc17xo2N5TjlJ29Wph5kMB5q23Sx5PX1aJbHcvrSHmjlpatHQeH
	bEVr89scQzdsDdPfacZTCh6/cIcg7YPtRs05AtrB+0eEcc67X9Rcc=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: [v4v6interim] Notes from day 1
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


--Apple-Mail-661--223279751
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I am posting this to the list so that people can correct/expand where  
appropriate.


--Apple-Mail-661--223279751
Content-Disposition: attachment;
	filename=v4v6interim-1-fjb.txt
Content-Type: text/plain;
	x-mac-creator=21526368;
	x-unix-mode=0644;
	x-mac-type=54455854;
	name="v4v6interim-1-fjb.txt"
Content-Transfer-Encoding: 7bit

Agenda:

08:30-9:00   breakfast                 (0:30)
09:00-9:15   practical arrangements    (0:15, Jari)
09:15-9:25   goals for the meeting     (0:10, Jari)
09:25-9:35   agenda bash               (0:10, chairs)
09:35-11:00  scenarios I               (1:50, Mark)
11:00-11:30  email break               (0:30)
11:30-12:00  lunch                     (0:30)
12:00-13:00  scenarios II              (1:00, Mark)
13:00-13:30  Address Plus Port (A+P)   (0:30, Randy)
13:30-14:00  Stateless Address Mapping (0:30, Remi)
14:00-14:15  break                     (0:15)
14:15-14:45  DS-Lite                   (0:30, Alain)
14:45-15:15  email break               (0:30)
15:15-15:45  comparison                (0:30, Dan)
15:45-17:00  discussion                (1:15, all)
                  - IPv6 prefix
                  - P-MTU & Fragmentation
                  - End-point discovery
                  - encaps/decaps location?
                  - Tunneling protocol

19:00-        social event at [http://www.gibbys.com/ Gibby's]

Discussion:

Mark Townsley gave an overview of the planned IPv6 deployment using dual stack technology. Reality is that IPv6 did not deploy, and we are facing some issues in the IPv4 address space. We want to look at scenarios (http://tools.ietf.org/id/draft-arkko-townsley-coexistence) sorting out the coexistence phase of deployment.

Mar showed five scenarios:
(1) IPv4 sites reaching global internet

In this scenario, the Internet is kept going by making trade-offs that may prevent edge network deployment of services.

(2) service providers running out of private IPv4 space

This provides balkanization of the Internet in which service providers don't necessarily provide access to the global IPv4 Internet.

(3) Enterprise "greenfield" IPv6-only networks

These are networks that run IPv6-only and are built from the ground p to do so. They consider the operational overhead of dual stack networks to be high. These use IPv6 internally and require access to IPv4-supported content.

(3a) Wireless "greenfield" IPv6-only networks"

Same scenario, but wireless (Cellular Radio) access network. The perception is that the cellular operator has the ability to specify equipment and operations in more detail than in generalized networks.

(4) IPv6 hosts reaching private IPv4-only servers

This combines a dual stack network providing access to servers in a private IPv4-only space managed by the ISP. This presumes that IPv6-only connectivity is required globally, but not IPv4-access.

Randy Bush pointed out that this scenario is much like the expected future scenario in which there are legacy IPv4 servers in an mostly-IPv6 world. This is deemed largely different from that in scale - the IPv4 part is relatively small, not relatively large.

(5) IPv4-only hosts reaching IPv6-only servers

Mark thinks this is "hard", because he can't map 2^128 addresses into 2^32 in a 1:1 fashion.


Design space issues:

Dual NAT (CGN) is new territory for some applications; the approach is likely to break some applications and introduce management complexity when servers are deployed between the CGN and the CPE Gateway. Specifically, Port Forwarding as implemented in UPnP will be compromised. Applications can generally continue to work if servers or peer/peer connectivity continues through the global IPv4 space; with modifications, most applications are likely to work. There is significant management complexity in all cases however.

If I am able to touch both the CGN and the CPE Gateway, then I can turn off NAT in the CPE Gateway and simply route from the home. If we use point to point connectivity (tunnel/DSL/PPP etc) then I have a large number of options due to total control. A network in Italy does the p2p scenario using 802.1d bridging in the CPE Gateway. One option here would be to use IPv6 in the ISP around a point to point network scenario connecting the CPE GW to the CGN. This lends itself to scenarios in which "port leasing" or "fractional addressing" are real options.

Remi Denis-Courmont raised concerns with the ability of the ISP to prevent DOS attacks and such. Complexity and statistical efficiency trade off here; Randy Bush and Mark Townsley argued in favor of simplicity over efficiency.

One issue raised here is the statistical behavior of port mapping. Current applications may use many (O(100)) ports while displaying a single web page, which due to issues of multiplexing means multiple hundreds of ports in use per user across a NAT due to mapping lifetime issues. There is support in research for the notion that changing transports to SCTP can dramatically change that while improving the application behavior, so one could expect applications to adapt to the environment. 

There is also room to consider mapping IPv4 addresses and ports into IPv6 addresses and routing in IPv6, and using that to connect private networks to the CGN in the distribution network.

The point was made that we have now spent an hour on various ramifications of the 4-4-4 solution and solutions like it. Within a relatively short period - one business contract cycle, on the order of three years or less - we can expect routers and hosts to all support IPv6. So this is a lot of time spent on how to add incredible complexity to keep IPv4 going for a couple more years. In the chat room, Nathan Ward notes that "the customers on OSes without IPv6 support are unlikely to need inbound Ipv4 connections". So IPv4 translation to access IPv6 servers can support legacy equipment."

Enterprise greenfield IPv6-only networks.

There are various ways to enable IPv6-only networks to access IPv4 content: NAT64, NAT-PT, or application gateways are options.

There was a pretty convoluted discussion of IPv6 networks connecting to dual stack networks containing IPv4-only content.  This appears to call for some form of translation.


We then went on to ask what scenarios we have missed, and Mark Townsley made it clear that the only scenarios he was interested in were areas in which the IETF needs to charter new work. Ron Bonica went on to look at the combinatorics of the solution space, which can be come quite large.

13:00-13:30  Address Plus Port (A+P)   (0:30, Randy)
http://mice.cs.columbia.edu/getTechreport.php?techreportID=560

Randy Bush then gave a talk on A+P: basically, he would like to insert IPv4 address and port into the IPv6 address and provide NAT between those things. He would like the ISPs to simply deploy IPv6. For details of the solution, read the document. His fundamental concern, he said, is that control should be as close to the user as possible and his model provides for that.

13:30-14:00  Stateless Address Mapping (0:30, Remi)
http://tools.ietf.org/html/draft-despres-sam

Remi gave an overview of the SAM technology.

14:15-14:45  DS-Lite                   (0:30, Alain)
http://tools.ietf.org/html/draft-durand-softwire-dual-stack-lite

Alain gave an overview of DS-Lite.

15:15-15:45  comparison                (0:30, Dan)
http://tools.ietf.org/html/draft-wing-nat-pt-replacement-comparison

Dan Wing reviewed the comparison document, in a set of slides that tried to capture the significant differences between various proposals. 

There was a long and wide-ranging discussion here with many people at the mike. To be honest, I couldn't make sense out of what needed to be minuted beyond "read the slides", although there was a lot of discussion.

Brian Haberman then ran a "how are we doing" session. In the jabber room, it was pretty clearly asked what the point of scenario 4 was (translation between IPv4 and IPv6, with the IPv4 being a private network) and why that excluded global addresses. Mark Townsley explained that scenario 4 was supposed to be the legacy IPv4 systems in a mostly-converted IPv6 network, while scenario 5 is an interchange between public or potentially-public networks.
--Apple-Mail-661--223279751
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit



--Apple-Mail-661--223279751
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--Apple-Mail-661--223279751--


From v4v6interim-bounces@ietf.org  Wed Oct  1 21:52:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD2BC28C0CF;
	Wed,  1 Oct 2008 21:52:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 272913A6835
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 21:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 17v6qQFvzSZT for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 21:52:03 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net
	[207.173.203.159])
	by core3.amsl.com (Postfix) with ESMTP id 4CF7C3A6803
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 21:52:03 -0700 (PDT)
Received: from commandprompt.com ([206.172.31.194]) (authenticated bits=0)
	by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m924u72V019000
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <v4v6interim@ietf.org>; Wed, 1 Oct 2008 21:56:12 -0700
Date: Thu, 2 Oct 2008 00:52:21 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081002045221.GA36568@commandprompt.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <090C6392-9082-4660-AE68-FA384B788C03@apple.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(lists.commandprompt.com [207.173.203.159]);
	Wed, 01 Oct 2008 21:56:13 -0700 (PDT)
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Wed, Oct 01, 2008 at 11:34:30AM -0700, james woodyatt wrote:

> The "gross indecency" here is, apparently, admitting in public that we 
> cannot escape the need to amend the DNS standards to recognize, for the 
> first time, that we need more than one public horizon, i.e. the V4V6COEX 
> public horizon and the IPv6 public horizon.

While I understand that suggestion, and even have a certain amount of
sympathy with it, I note that there's a practical reason that many
DNS-heads don't like multiple versions of the namespace: they tend to
leak into other contexts.  Since we have experience with this
already, it would be prudent to plan that such leaks will be part of
any future deployment of "split-brain" approaches.

This is bad enough in the context of corporate NATs with RFC 1918
addresses inside, but at least one has a hope of spotting this (by
virtue of the 1918 address itself).  I appreciate what Fred said
earlier, that applications don't always care about the distinction
between 1918 and non-1918 address spaces; but the distinction is an
old one, and applications (or just help desk workers) that need to
deal with these cases can use that distinction to help them.  Since by
definition, in this case, what we're trying to address are
applications that can't learn new things (or they'd use IPv6
natively), I'm pretty worried that we'll create new modes of failure
that will be very hard to troubleshoot, because we'll have inserted a
new device in the network whose whole purpose is to intercept DNS
packets and change them into something else.

To be clear, I'm not saying, "Disaster! Bad! Evil! No! DNS purity!"
I'm just raising a caution that there seems to be a boom on for
split-brain DNS answers, and such answers come not only with DNSSEC
problems, but other issues as well.

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 22:40:11 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B9A73A68D3;
	Wed,  1 Oct 2008 22:40:11 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B2F43A6C41;
	Wed,  1 Oct 2008 06:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZLmG62Pu14Rl; Wed,  1 Oct 2008 06:23:15 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com
	[216.82.245.115])
	by core3.amsl.com (Postfix) with ESMTP id 140873A680A;
	Wed,  1 Oct 2008 06:23:15 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-6.tower-121.messagelabs.com!1222867397!21279017!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.53]
Received: (qmail 32061 invoked from network); 1 Oct 2008 13:23:17 -0000
Received: from sbcsmtp6.sbc.com (HELO mlph073.enaf.sfdc.sbc.com)
	(144.160.20.53)
	by server-6.tower-121.messagelabs.com with AES256-SHA encrypted SMTP;
	1 Oct 2008 13:23:17 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlph073.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m91DNGHG013573; Wed, 1 Oct 2008 09:23:17 -0400
Received: from 01GAF5142010624.AD.BLS.COM ([139.76.131.91])
	by mlph073.enaf.sfdc.sbc.com (8.14.0/8.14.0) with SMTP id
	m91DNDQh013541; Wed, 1 Oct 2008 09:23:13 -0400
Received: from 01NC27689010625.AD.BLS.COM ([90.144.44.200]) by
	01GAF5142010624.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.2499); 
	Wed, 1 Oct 2008 09:23:12 -0400
Received: from 01NC27689010641.AD.BLS.COM ([90.144.44.103]) by
	01NC27689010625.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.2499); 
	Wed, 1 Oct 2008 09:23:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 1 Oct 2008 09:23:08 -0400
Message-ID: <7582BC68E4994F4ABF0BD4723975C3FA0AF5DD30@crexc41p>
In-Reply-To: <013201c922f2$82025230$c2f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: v4v6interim@ietf.org Mailing list
Thread-Index: AckY6uKeN8eY2PYZS82b7Wp6/WSgKwJ35irgAAn2vLAANZYJYA==
References: <48CEE763.8030502@cisco.com><2A9F30EB-9A1E-46B8-AF83-03B729F8DFF5@lilacglade.org>
	<48D13E0D.8060002@cisco.com>
	<BE82361A0E26874DBC2ED1BA244866B92758ED8D@NALASEXMB08.na.qualcomm.com>
	<013201c922f2$82025230$c2f0200a@cisco.com>
From: "Stark, Barbara" <bs7652@att.com>
To: "Dan Wing" <dwing@cisco.com>, "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Mark Townsley" <townsley@cisco.com>,
	"Margaret Wasserman" <mrw@lilacglade.org>
X-OriginalArrivalTime: 01 Oct 2008 13:23:12.0350 (UTC)
	FILETIME=[DA8747E0:01C923C8]
X-Mailman-Approved-At: Wed, 01 Oct 2008 22:40:10 -0700
Cc: Internet Area <int-area@ietf.org>, v4v6interim@ietf.org, ipv6@ietf.org,
	IPv6 Operations <v6ops@ops.ietf.org>, softwires@ietf.org,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] v4v6interim@ietf.org Mailing list
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Could someone confirm the name of the jabber room? My client tells me that =
"v4v6existence" doesn't exist.
Barbara

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf =
Of Dan Wing
Sent: Tuesday, September 30, 2008 7:49 AM
To: 'Narayanan, Vidya'; 'Mark Townsley'; 'Margaret Wasserman'
Cc: 'Brian Haberman'; 'Internet Area'; softwires@ietf.org; 'IPv6 Operations=
'; ipv6@ietf.org; 'Behave WG'; v4v6interim@ietf.org
Subject: RE: v4v6interim@ietf.org Mailing list

See the "Remote Participation" section at:
http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim

Please register for remote participation, so we have a feeling of how many
people are supposed to be in the jabber room and on the conference bridge.

-d
 =


> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com] =

> Sent: Tuesday, September 30, 2008 12:04 AM
> To: Mark Townsley; Margaret Wasserman
> Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan =

> Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
> Subject: RE: v4v6interim@ietf.org Mailing list
> =

> Mark,
> Please share the remote particpation info (jabber room, audio =

> link, etc.) when you have it.
> =

> Thanks,
> vidya
> =

> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
> > Behalf Of Mark Townsley
> > Sent: Wednesday, September 17, 2008 10:28 AM
> > To: Margaret Wasserman
> > Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan
> > Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
> > Subject: Re: v4v6interim@ietf.org Mailing list
> >
> >
> > We are discussing the situation with the host, and any
> > volunteers we can muster up.
> >
> > Our goal is to have streaming audio and video for the
> > presentations, with the ability to ask questions or make
> > statements to the speaker remotely over jabber (via a local
> > moderator, speaking on the remote participants behalf). I'm
> > afraid we probably will not have the right infrastructure for
> > effective real-time, multipoint, participation among remote
> > and local participants.
> >
> > It looks like there will be a good bit of alpha code running
> > no matter what we do, so don't bet that there will be no
> > problems. We'll make the experience as good as we can for
> > remote folks based on what we have though.
> >
> > - Mark
> >
> > Margaret Wasserman wrote:
> > >
> > > Has there been any resolution on how/if it will be possible
> > to attend
> > > this meeting remotely (conference bridge, web conference,
> > jabber room,
> > > etc.)?
> > >
> > > I will not be able to travel to Montreal, but would like to
> > attend all
> > > or part of the meeting remotely, if possible.
> > >
> > > Thanks,
> > > Margaret
> > >
> > > On Sep 15, 2008, at 6:53 PM, Mark Townsley wrote:
> > >
> > >>
> > >> We have setup an email list for discussion leading up to
> > the interim
> > >> v4v6 coexistence meeting on October 1-2, 2008 in Montr=E9al,
> > Canada. If
> > >> you are registered to attend the meeting, you should =

> already be on
> > >> the list.
> > >>
> > >> The list is open, please subscribe and begin using it for
> > all interim
> > >> meeting related discussion (technical as well as
> > >> administrative/logistical). For now, please consider this a
> > >> short-lived list focused on agenda items for discussion at this
> > >> interim meeting alone. We should know better after the
> > meeting how to
> > >> best divide discussion back among the individual WG lists,
> > or whether
> > >> a long-lived list of this nature is warranted.
> > >>
> > >> If you are attending and haven't registered, please do:
> > >>
> > >>
> > =

> http://trac.tools.ietf.org/area/int/trac/wiki/RegistrationForv4v6inte
> > >> rim
> > >>
> > >> Tentative agenda, etc. can be found here:
> > >>
> > >> http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim
> > >>
> > >> Thanks,
> > >>
> > >> - Mark, Jari, Dan and Brian
> > >>
> > >>
> > >>
> > >>
> > >>
> > --------------------------------------------------------------------
> > >> IETF IPv6 working group mailing list
> > >> ipv6@ietf.org
> > >> Administrative Requests: =

> https://www.ietf.org/mailman/listinfo/ipv6
> > >>
> > --------------------------------------------------------------------
> > >
> > >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 22:40:11 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AA1F3A6A19;
	Wed,  1 Oct 2008 22:40:11 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B69023A681D
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 22:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UVZaxSquyO7y for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 22:32:05 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id A74EE3A67B2
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 22:32:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,348,1220227200"; d="scan'208";a="167144812"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 05:32:31 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m925WVA8017442; 
	Wed, 1 Oct 2008 22:32:31 -0700
Received: from dwingwxp01 (sjc-vpn7-519.cisco.com [10.21.146.7])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m925WOGN015252;
	Thu, 2 Oct 2008 05:32:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Andrew Sullivan'" <ajs@commandprompt.com>, <v4v6interim@ietf.org>
References: <20081001202914.GA34476@commandprompt.com>
Date: Thu, 2 Oct 2008 01:32:24 -0400
Message-ID: <065801c92450$4444e840$0792150a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20081001202914.GA34476@commandprompt.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AckkBYC7RLThim+4QsCu7PQA7zzrOQASjRsg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2880; t=1222925551;
	x=1223789551; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20=22No=20DNS=20changes=2
	2=20indraft-wing-nat-pt-replacement-comparison-01 |Sender:=20;
	bh=QP5UvJV+OAugVG6Xv85LS2WytxnZlLvUUGGEuyb+yMc=;
	b=c2+3+cWH8w1/q4cj8fYX4iHCXQZFb8fr0PHNN8GiYoNe5HQ+ccKhCNBgns
	V4DEiRGO5jdgUBfZJ/hboo9FDdTJfXejayuu/VNpCANUgQM9Uysv7zl+ySee
	MaF1KAbtta;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Mailman-Approved-At: Wed, 01 Oct 2008 22:40:10 -0700
Subject: Re: [v4v6interim] "No DNS changes"
	indraft-wing-nat-pt-replacement-comparison-01
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 

> -----Original Message-----
> From: v4v6interim-bounces@ietf.org 
> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Andrew Sullivan
> Sent: Wednesday, October 01, 2008 4:29 PM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] "No DNS changes" 
> indraft-wing-nat-pt-replacement-comparison-01
> 
> I think I understand now what my problem was that I was trying to
> state (incompetently, I think) at the mic.
> 
> In the overview of the items we were to discuss this afternoon, and in
> draft-wing-nat-pt-replacement-comparison-01 table 2, we have this
> claim:
> 
>    
> +--------------+-----------------+------------+---------------------+
>    |   Proposal   |  ISP's Internal | DNS Impact |  Carrier 
> Grade NAT  |
>    |              |     Network     |            |            
>          |
>    
> +--------------+-----------------+------------+---------------------+
>    |    A+P-v4    |       IPv4      |  no change |     (no 
> CGN, if     |
>    |              |   destination   |            |   
> subscriber's NAT  |
>    |              |   port routing  |            |   support 
> A+P NAT)  |
>    
> +--------------+-----------------+------------+---------------------+
>    |    A+P-v6    |    IPv4/IPv6    |  no change |     (no 
> CGN, if     |
>    |              |      tunnel     |            |   
> subscriber's NAT  |
>    |              |                 |            |   support 
> A+P NAT)  |
>    
> +--------------+-----------------+------------+---------------------+
> 
> I'm confused by the DNS Impact claim of "no change" here, if the
> suggestion is that A+P is going to help v6-only clients talk to the
> target hosts.  Is it instead the case that A+P is just not going to
> help v6-only hosts?  That is, unless I'm misunderstanding badly (and
> it wouldn't be the first time), a v6-only host can't talk to a v4-only
> host using A+P without getting some way of talking to v4 networks,
> period.  So maybe the DNS Impact in that table should be like NAT444?

A+P is all about IPv4 or a dual-stack host.  In either case, it would
access the IPv4 Internet using IPv4.  Also, in either case, the host does an A
record query and the host can process that A record query.  In that sense, I
agree it is like NAT444.

Table 2 probably tries to say too many things, as Table 2 is about IPv6 hosts
yet Table 2 includes NAT444, which doesn't support IPv6.  A+P (and Dual-Stack
Lite and SAM, for that matter) only support IPv6 subscriber hosts as a
side-effect; they do not intrinsically support IPv6.

-d
 

> A
> 
> -- 
> Andrew Sullivan
> ajs@commandprompt.com
> +1 503 667 4564 x104
> http://www.commandprompt.com/
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 22:42:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D27113A690D;
	Wed,  1 Oct 2008 22:42:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 120DB3A690D;
	Wed,  1 Oct 2008 22:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oatrvb7Ig1fc; Wed,  1 Oct 2008 22:42:35 -0700 (PDT)
Received: from unobtainium.braintrust.co.nz (unobtainium.braintrust.co.nz
	[60.234.76.2]) by core3.amsl.com (Postfix) with ESMTP id BC3183A68BA;
	Wed,  1 Oct 2008 22:42:34 -0700 (PDT)
Received: from [192.168.0.51] (ip-118-90-75-60.xdsl.xnet.co.nz [118.90.75.60])
	by unobtainium.braintrust.co.nz (Postfix) with ESMTP id 8FD3827874; 
	Thu,  2 Oct 2008 18:41:46 +1300 (NZDT)
Message-Id: <594873B7-9476-4836-97F4-16EBA2A0815D@daork.net>
From: Nathan Ward <v6ops@daork.net>
To: "Stark, Barbara" <bs7652@att.com>
In-Reply-To: <7582BC68E4994F4ABF0BD4723975C3FA0AF5DD30@crexc41p>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 18:41:44 +1300
References: <48CEE763.8030502@cisco.com><2A9F30EB-9A1E-46B8-AF83-03B729F8DFF5@lilacglade.org>
	<48D13E0D.8060002@cisco.com>
	<BE82361A0E26874DBC2ED1BA244866B92758ED8D@NALASEXMB08.na.qualcomm.com>
	<013201c922f2$82025230$c2f0200a@cisco.com>
	<7582BC68E4994F4ABF0BD4723975C3FA0AF5DD30@crexc41p>
X-Mailer: Apple Mail (2.929.2)
Cc: Internet Area <int-area@ietf.org>, softwires@ietf.org, "Narayanan,
	Vidya" <vidyan@qualcomm.com>, ipv6@ietf.org,
	IPv6 Operations <v6ops@ops.ietf.org>, v4v6interim@ietf.org,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] v4v6interim@ietf.org Mailing list
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

v4v6coexistence

On 2/10/2008, at 2:23 AM, Stark, Barbara wrote:

> Could someone confirm the name of the jabber room? My client tells  =

> me that "v4v6existence" doesn't exist.
> Barbara
>
> -----Original Message-----
> From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On  =

> Behalf Of Dan Wing
> Sent: Tuesday, September 30, 2008 7:49 AM
> To: 'Narayanan, Vidya'; 'Mark Townsley'; 'Margaret Wasserman'
> Cc: 'Brian Haberman'; 'Internet Area'; softwires@ietf.org; 'IPv6  =

> Operations'; ipv6@ietf.org; 'Behave WG'; v4v6interim@ietf.org
> Subject: RE: v4v6interim@ietf.org Mailing list
>
> See the "Remote Participation" section at:
> http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim
>
> Please register for remote participation, so we have a feeling of  =

> how many
> people are supposed to be in the jabber room and on the conference  =

> bridge.
>
> -d
>
>
>> -----Original Message-----
>> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
>> Sent: Tuesday, September 30, 2008 12:04 AM
>> To: Mark Townsley; Margaret Wasserman
>> Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan
>> Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
>> Subject: RE: v4v6interim@ietf.org Mailing list
>>
>> Mark,
>> Please share the remote particpation info (jabber room, audio
>> link, etc.) when you have it.
>>
>> Thanks,
>> vidya
>>
>>> -----Original Message-----
>>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
>>> Behalf Of Mark Townsley
>>> Sent: Wednesday, September 17, 2008 10:28 AM
>>> To: Margaret Wasserman
>>> Cc: Brian Haberman; Internet Area; softwires@ietf.org; Dan
>>> Wing; 'IPv6 Operations'; ipv6@ietf.org; Behave WG
>>> Subject: Re: v4v6interim@ietf.org Mailing list
>>>
>>>
>>> We are discussing the situation with the host, and any
>>> volunteers we can muster up.
>>>
>>> Our goal is to have streaming audio and video for the
>>> presentations, with the ability to ask questions or make
>>> statements to the speaker remotely over jabber (via a local
>>> moderator, speaking on the remote participants behalf). I'm
>>> afraid we probably will not have the right infrastructure for
>>> effective real-time, multipoint, participation among remote
>>> and local participants.
>>>
>>> It looks like there will be a good bit of alpha code running
>>> no matter what we do, so don't bet that there will be no
>>> problems. We'll make the experience as good as we can for
>>> remote folks based on what we have though.
>>>
>>> - Mark
>>>
>>> Margaret Wasserman wrote:
>>>>
>>>> Has there been any resolution on how/if it will be possible
>>> to attend
>>>> this meeting remotely (conference bridge, web conference,
>>> jabber room,
>>>> etc.)?
>>>>
>>>> I will not be able to travel to Montreal, but would like to
>>> attend all
>>>> or part of the meeting remotely, if possible.
>>>>
>>>> Thanks,
>>>> Margaret
>>>>
>>>> On Sep 15, 2008, at 6:53 PM, Mark Townsley wrote:
>>>>
>>>>>
>>>>> We have setup an email list for discussion leading up to
>>> the interim
>>>>> v4v6 coexistence meeting on October 1-2, 2008 in Montr=E9al,
>>> Canada. If
>>>>> you are registered to attend the meeting, you should
>> already be on
>>>>> the list.
>>>>>
>>>>> The list is open, please subscribe and begin using it for
>>> all interim
>>>>> meeting related discussion (technical as well as
>>>>> administrative/logistical). For now, please consider this a
>>>>> short-lived list focused on agenda items for discussion at this
>>>>> interim meeting alone. We should know better after the
>>> meeting how to
>>>>> best divide discussion back among the individual WG lists,
>>> or whether
>>>>> a long-lived list of this nature is warranted.
>>>>>
>>>>> If you are attending and haven't registered, please do:
>>>>>
>>>>>
>>>
>> http://trac.tools.ietf.org/area/int/trac/wiki/RegistrationForv4v6inte
>>>>> rim
>>>>>
>>>>> Tentative agenda, etc. can be found here:
>>>>>
>>>>> http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Mark, Jari, Dan and Brian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org
>>>>> Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>
>>> --------------------------------------------------------------------
>>>>
>>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>
> !DSPAM:22,48e45edb202913425321090!
>
>

--
Nathan Ward




_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 23:36:17 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 116D93A69CF;
	Wed,  1 Oct 2008 23:36:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB2D73A69CF
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 23:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FYOGPaIuGSf8 for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 23:36:15 -0700 (PDT)
Received: from mint.apnic.net (mint.apnic.net [202.12.29.58])
	by core3.amsl.com (Postfix) with ESMTP id CD7E13A67B6
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 23:36:14 -0700 (PDT)
Received: from dhcp19.potaroo.net (dhcp19.potaroo.net [203.10.60.19])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 4871AD5F2D;
	Thu,  2 Oct 2008 16:35:50 +1000 (EST)
Message-Id: <AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
From: Geoff Huston <gih@apnic.net>
To: Andrew Sullivan <ajs@commandprompt.com>
In-Reply-To: <20081002045221.GA36568@commandprompt.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 16:35:47 +1000
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On 02/10/2008, at 2:52 PM, Andrew Sullivan wrote:

>
> To be clear, I'm not saying, "Disaster! Bad! Evil! No! DNS purity!"
> I'm just raising a caution that there seems to be a boom on for
> split-brain DNS answers, and such answers come not only with DNSSEC
> problems, but other issues as well.

Oh that it were different. Would that we have completed this  
transition while there was plentiful IPv4 addresses left in the pool.  
Would that the dial stack transition were undertaken while we weren't  
being forced to assume unnatural configurations due to IPv4 address  
exhaustion. That way we would not be attempting to shoehorn a size 128  
Internet into a size 32 shoe for the next decade or more.

But we are where we are and now we have to explore notions that  
decouple the previously strict concepts of the equivalence of names  
and addresses. And if an IPv4 only host wants to initiate a  
conversation with an IPv6 only host, then the initial part of the  
conventional rendezvous, the DNS lookup, has to creatively lie in its  
response. Yeah, its crap, and yeah, its going to cause grief. Stuff  
will leak inappropriately and debugging problems will be tougher. And  
the DNS gets broken in strange ways as a consequence.

But we all knew this Andrew, didn't we? So I for one am not sure what  
point you are making here that wasn't part and parcel of any of these  
hybrid translation approaches. Am I missing something here in your  
post that advances something that was not well understood already?


Geoff


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  1 23:55:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF23B3A69CF;
	Wed,  1 Oct 2008 23:55:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67FD13A67B6
	for <v4v6interim@core3.amsl.com>; Wed,  1 Oct 2008 23:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1RJwILL5cOGY for <v4v6interim@core3.amsl.com>;
	Wed,  1 Oct 2008 23:55:12 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net
	[207.173.203.159])
	by core3.amsl.com (Postfix) with ESMTP id B3B753A69CF
	for <v4v6interim@ietf.org>; Wed,  1 Oct 2008 23:55:12 -0700 (PDT)
Received: from commandprompt.com ([206.172.31.194]) (authenticated bits=0)
	by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m926w6ok026844
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 1 Oct 2008 23:58:09 -0700
Date: Thu, 2 Oct 2008 02:54:21 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: Dan Wing <dwing@cisco.com>
Message-ID: <20081002065420.GA37587@commandprompt.com>
References: <20081001202914.GA34476@commandprompt.com>
	<065801c92450$4444e840$0792150a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <065801c92450$4444e840$0792150a@cisco.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(lists.commandprompt.com [207.173.203.159]);
	Wed, 01 Oct 2008 23:58:10 -0700 (PDT)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "No DNS
	changes"	indraft-wing-nat-pt-replacement-comparison-01
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thu, Oct 02, 2008 at 01:32:24AM -0400, Dan Wing wrote:
> 
> Table 2 probably tries to say too many things, as Table 2 is about IPv6 hosts
> yet Table 2 includes NAT444, which doesn't support IPv6.  A+P (and Dual-Stack
> Lite and SAM, for that matter) only support IPv6 subscriber hosts as a
> side-effect; they do not intrinsically support IPv6.

Yes, that was my impression.  I suggest leaving out cases where it's a
side effect from that table.  It's confusing otherwise (or at least,
it was to me).

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 02:39:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D37E13A6848;
	Thu,  2 Oct 2008 02:39:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9178D3A6848
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 02:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SyQErO3MV5EE for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 02:39:40 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 435A23A6811
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 02:39:40 -0700 (PDT)
Received: from c0248.aw.cl.cam.ac.uk (c0248.aw.cl.cam.ac.uk [128.232.100.248])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m929dN8I082570
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 2 Oct 2008 11:39:24 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 10:39:30 +0100
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 1 okt 2008, at 21:07, Fred Baker wrote:

> On Oct 1, 2008, at 12:24 PM, Iljitsch van Beijnum wrote:

>> There are several advantages of having a well known prefix for NAT- 
>> PT/NAT64 or even DS-lite.

> Maybe I'm missing something.

> If there exists a AAAA record for a name, there is no reason to  
> translate an A record to create one. Regardless of the host type, if  
> a native AAAA record exists, a translated record will never be  
> presented.

> What's the issue?

I don't see how you get from what I said to what you said...

But now that you bring it up: the reason to make sure fake AAAA  
records aren't generated when real AAAA records exist is that we don't  
want to have the situation where a host uses translated connectivity  
if there's also native connectivity.

However, if the address selection rules work well enough it MAY be  
useful to present both a native address and an address that will go  
through a translator to the application so that if the native address  
doesn't work the app can try the translated address. However, we know  
there are hosts out there today that don't implement RFC 3484 fully  
(at all?) (i.e., Macs) so generating fake AAAA records where real ones  
exist in a DNS64 (-like) box is a very bad idea.

To get back to a less academic issue: what we need is for the  
addresses that are translated to be less preferred than real IPv4  
addresses. Currently, the default RFC 3484 policy table puts IPv4  
below ANY type of IPv6, so we don't have this property today.  
Obviously this is a trivial change to make to the default policy table  
if the prefix is well known, but again, external boxes that generate  
fake AAAA records can't know whether the host in question has been  
upgraded.

So let me present a path from where we are today to where we want to  
be in the future.

Today, we have NAT-PT implementations, deprecated as they may be.

The next step would be to implement some of the stuff in the NAT64  
draft, such as not using a DNS ALG but an explicit DNS64 and the EDNS0  
SAS option to indicate that synthetic AAAA records were created. Note  
that this mostly works with existing NAT-PT translators, although  
those should be upgraded to work according to the latest BEHAVE  
insights as referenced in the NAT64 draft.

At the same time, we can ask IANA to allocate a well known prefix for  
NAT64/DS-lite use. The specifications for the NAT64 translator and DS- 
lite CGN should be merged at this point, so a single translator can  
address both use cases, making deployment for either easier and  
reducing risk on the part of vendors. Because (old) hosts using DS- 
lite may need ALG support to work but ALGs get in the way of modern  
hosts/applications, IPv4 ALGs are deployed when using DS-lite, but no  
ALGs are used when the host uses NAT64.

New NAT64/DS-lite implementations should use the well known prefix and  
existing implementations should migrate to the well known prefix.

Host OSes are upgraded to prefer native IPv4 over the well known  
translated prefix, and, if desired, they are upgraded to create  
synthetic AAAA responses locally whenever there is no IPv4  
connectivity in the system.

(Alternatively, hosts implement a mechanism such that A lookups are  
also done in the absense of IPv4 connectivity and the ::ffff:0:0/96  
prefix that is used in the API is rewritten into the well known  
translator prefix as (IPv6) packets are generated so that applications  
using IPv4 through the IPv6 socket API or even the IPv4 socket API can  
send packets to IPv4 destinations even though there is no IPv4  
connectivity.)

Middlebox / DSLAM / CPE / home gateway etc vendors implement a DHCPv6  
option to obtain rewrite rules for the well known prefix, so that  
packets addressed to the well known prefix can have their destination  
address rewritten so that the packets flow towards a specific  
translator (and the return packets are translated back).

When we reach this point we should be in very good shape and be ready  
to use IPv6-to-IPv4 translation for a good number of years without  
major problems.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 02:42:25 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DD0E3A6B15;
	Thu,  2 Oct 2008 02:42:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03B223A6B1A
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 02:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id l5iyqHfA0+91 for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 02:42:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 486923A6811
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 02:42:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9435620ED6; Thu,  2 Oct 2008 11:42:44 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-65-48e4979497c9
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	31AF720C67; Thu,  2 Oct 2008 11:42:44 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 11:42:05 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 11:42:05 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 2DF8A2469;
	Thu,  2 Oct 2008 12:42:05 +0300 (EEST)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4CB1F4DAC2;
	Thu,  2 Oct 2008 12:42:01 +0300 (EEST)
Message-Id: <65137CB2-F5E9-48F2-8084-11BF17B34291@ericsson.com>
From: Christian Vogt <christian.vogt@ericsson.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 05:41:59 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 09:42:05.0133 (UTC)
	FILETIME=[21105FD0:01C92473]
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] Translation-based IPv4/IPv6 interworking for IPv4
	networks
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Dear all,

Alain and I have worked on a translation-based IPv4/IPv6 interworking
method that we would like to share with you.  This method is for
deployment in IPv4-only networks, and in this regard differs from many
of the existing translation-based interworking methods that are for
deployment in IPv6 networks.  The main advantage of IPv4-side deployment
is that no extra, globally unique IPv4 addresses are required.

You find Alain's and my proposal here:
http://users.piuha.net/chvogt/pub/2008/virtual-ip6-connectivity.txt

In the early days of IPv6 introduction, the responsibility for IPv4/IPv6
interworking must clearly be on the side of the new IPv6 networks, for
incentives reasons.  But interworking will become increasingly important
also for IPv4 networks as IPv6 gets more prevalent.  IPv4-side
interworking methods will then be useful.  Furthermore, IPv4-side
interworking can already today solve some of the key problem scenarios,
namely those involving IPv6 clients and IPv4 servers in the absence of a
unique global IPv4 addresses for each server.

We realize we are submitting this very late -- and I could myself not
even participate in the discussion around tunneling-based interworking
yesterday.  I wish that had been different.  But perhaps our document
can still provide a bit of valuable input for today's discussion.

- Christian, for Alain and Christian


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 02:48:12 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEE503A6C00;
	Thu,  2 Oct 2008 02:48:12 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76C6A3A6C00
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 02:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gwpMpL8VM1gk for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 02:48:11 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 86F2F3A6803
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 02:48:11 -0700 (PDT)
Received: from c0248.aw.cl.cam.ac.uk (c0248.aw.cl.cam.ac.uk [128.232.100.248])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m929mNjc082763
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 2 Oct 2008 11:48:23 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <839EAB12-81CD-4FD7-BCB8-7A76D9222180@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Andrew Sullivan <ajs@commandprompt.com>
In-Reply-To: <20081002045221.GA36568@commandprompt.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 10:48:30 +0100
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2 okt 2008, at 5:52, Andrew Sullivan wrote:

> there's a practical reason that many
> DNS-heads don't like multiple versions of the namespace: they tend to
> leak into other contexts.  Since we have experience with this
> already, it would be prudent to plan that such leaks will be part of
> any future deployment of "split-brain" approaches.

> This is bad enough in the context of corporate NATs with RFC 1918
> addresses inside, but at least one has a hope of spotting this (by
> virtue of the 1918 address itself).

If we use a well known prefix for the translator then the problem is  
no worse than in the RFC 1918 case.

> I'm pretty worried that we'll create new modes of failure
> that will be very hard to troubleshoot, because we'll have inserted a
> new device in the network whose whole purpose is to intercept DNS
> packets and change them into something else.

Nobody wants to put a device in the network that _intercepts_ DNS  
packets.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 05:12:40 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 686AA3A6CB8;
	Thu,  2 Oct 2008 05:12:40 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 585C43A6CB8
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 05:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ubn5XdYVo82W for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 05:12:38 -0700 (PDT)
Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25])
	by core3.amsl.com (Postfix) with ESMTP id 30A3A3A659B
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 05:12:37 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by mail.nttv6.net (8.14.3/8.14.3) with ESMTP id m92CCt73072333;
	Thu, 2 Oct 2008 21:12:56 +0900 (JST)
	(envelope-from arifumi@nttv6.net)
Message-Id: <9F3FB3C0-6776-4F0E-9372-BC190A74755B@nttv6.net>
From: Arifumi Matsumoto <arifumi@nttv6.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 21:13:35 +0900
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
	<9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0
	(mail.nttv6.net [127.0.0.1]); Thu, 02 Oct 2008 21:12:56 +0900 (JST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

>>
> I don't see how you get from what I said to what you said...
>
> But now that you bring it up: the reason to make sure fake AAAA  
> records aren't generated when real AAAA records exist is that we  
> don't want to have the situation where a host uses translated  
> connectivity if there's also native connectivity.
>
> However, if the address selection rules work well enough it MAY be  
> useful to present both a native address and an address that will go  
> through a translator to the application so that if the native  
> address doesn't work the app can try the translated address.  
> However, we know there are hosts out there today that don't  
> implement RFC 3484 fully (at all?) (i.e., Macs) so generating fake  
> AAAA records where real ones exist in a DNS64 (-like) box is a very  
> bad idea.

I agree with you most of the parts, but let me comment on this point.

Regardless of the existence of RFC 3484 non-compatible hosts, replying  
a synthesis AAAA with a genuine AAAA should be an operator's choice ?  
As far as there is some benefit, such as fault-tolerance, to have  
these two AAAA records, and we don't have strong motivation to  
prohibit it universally, it's better to leave this decision up to an  
operator of the site or the translator box.


Kindest regards.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 06:06:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1FC83A6B45;
	Thu,  2 Oct 2008 06:06:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B68E83A6B45
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 06:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.516
X-Spam-Level: 
X-Spam-Status: No, score=-106.516 tagged_above=-999 required=5
	tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nGVQPDKBaRnf for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 06:06:50 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 75BAA3A6CDA
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 06:06:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,351,1220227200"; d="scan'208";a="167342866"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 13:06:43 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m92D6hpj007784; 
	Thu, 2 Oct 2008 06:06:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92D6g00024120;
	Thu, 2 Oct 2008 13:06:42 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 06:06:42 -0700
Received: from [192.168.3.109] ([10.21.75.252]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 06:06:42 -0700
Message-Id: <0950B3A4-B6E0-467E-95EE-40280D0BDA80@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 09:03:35 -0400
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>
	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>
	<9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 13:06:42.0477 (UTC)
	FILETIME=[B6EE65D0:01C9248F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1577; t=1222952803;
	x=1223816803; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20The=20NAT64=20prefix
	|Sender:=20; bh=nlJCRr9MktcTIK0Wu2EBKORg9WPmVm6HztoKKLJJg+0=;
	b=NMtAjzjNNynj+oa2p1GPFdRP1Fh0DnByTy5PDbiwJe5ngB0M6hY6XA8ehF
	Boe1BjgvaRT2pcPtfYfTtb34UgNc1J62zphlzwvVbxUVwh/BxYjf7hmBO/bN
	V3+c7AyI9b;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 2, 2008, at 5:39 AM, Iljitsch van Beijnum wrote:

> To get back to a less academic issue: what we need is for the  
> addresses that are translated to be less preferred than real IPv4  
> addresses.

picking one comment out of your longer note (which I might have more  
of a response to later), I'm not sure I agree, at least in the IVI case.

The big issue is what happens when a system with a general IPv6  
address sends a datagram to a system that has a translated address. If  
the result is that the message goes through the translator, we have a  
problem.

In the IVI case and I believe in the NAT64 case, they don't go through  
the translator. What happens is that the translator announces a  
default route (whatever prefix the LIR assigned, at that length) into  
the IPv6 domain, and either the servers or the routers in front of  
them announce more specific routes appropriate to the locations of  
those servers in the network. This is necessary for datagrams from the  
translator to get to their target servers. By the same logic that  
datagrams get from the translator to the servers, traffic from other  
IPv6 devices will go directly to the same servers - traffic will  
follow longest-match-first standard routing and go nowhere near the  
translator.

I will agree philosophically that it would be preferable that clients  
and peers in the IPv6 domain used the more general IPv6 address, but I  
honestly don't see anything that breaks, or even a change of route, if  
they happen to use the translated address.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 06:06:59 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1750E28C1B6;
	Thu,  2 Oct 2008 06:06:59 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3DC083A6CDE
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 06:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.52
X-Spam-Level: 
X-Spam-Status: No, score=-106.52 tagged_above=-999 required=5
	tests=[AWL=0.079, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pnER4+3b7uXA for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 06:06:57 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id BA8073A6CE1
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 06:06:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,351,1220227200"; d="scan'208";a="167343087"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 13:07:01 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m92D71ss000864; 
	Thu, 2 Oct 2008 06:07:01 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m92D6xGN004557;
	Thu, 2 Oct 2008 13:07:01 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 06:06:42 -0700
Received: from [192.168.3.109] ([10.21.75.252]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 06:06:41 -0700
Message-Id: <F698EDA9-1121-4324-93C3-D259A02125F7@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Andrew Sullivan <ajs@commandprompt.com>
In-Reply-To: <20081002045221.GA36568@commandprompt.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 08:55:49 -0400
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 13:06:41.0945 (UTC)
	FILETIME=[B69D3890:01C9248F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=516; t=1222952822; x=1223816822;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Single=20namespace
	|Sender:=20; bh=aXJgpHkg6evUJlrvrcazxhRe0kha76yd1g0cwIonOZk=;
	b=mC6kKYpPdIAXLkfoiYq6Z11GGV1Xgvqjh+fuqd4tquWctnlCqLDQ7B4dZg
	XvtHklAisVIfY/ZqwMZjcYdvXNe5SkSeViZP8+hSPA6fpyo3yyTh2F80EWFz
	rmsAo7CG6o;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 2, 2008, at 12:52 AM, Andrew Sullivan wrote:

> While I understand that suggestion, and even have a certain amount of
> sympathy with it, I note that there's a practical reason that many
> DNS-heads don't like multiple versions of the namespace: they tend to
> leak into other contexts.

no doubt. When we pretend something doesn't exist, it's pretty easy  
for it to get screwed up.

I'll argue that recognizing the issue and designing a solution will  
work better than whistling in the dark.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 06:22:59 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AED833A6C14;
	Thu,  2 Oct 2008 06:22:59 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D8AF3A697D
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 06:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id laQ3ehHh65Wa for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 06:22:58 -0700 (PDT)
Received: from lists.commandprompt.com (host-159.commandprompt.net
	[207.173.203.159])
	by core3.amsl.com (Postfix) with ESMTP id 2EBE43A6887
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 06:22:58 -0700 (PDT)
Received: from commandprompt.com (traingw.ericsson.ca [192.75.88.176])
	(authenticated bits=0)
	by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m92DQbRF022175
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 06:26:40 -0700
Date: Thu, 2 Oct 2008 09:22:52 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: v4v6interim@ietf.org
Message-ID: <20081002132252.GC38182@commandprompt.com>
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
	<AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(lists.commandprompt.com [207.173.203.159]);
	Thu, 02 Oct 2008 06:26:41 -0700 (PDT)
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thu, Oct 02, 2008 at 04:35:47PM +1000, Geoff Huston wrote:
> But we all knew this Andrew, didn't we? So I for one am not sure what point 
> you are making here that wasn't part and parcel of any of these hybrid 
> translation approaches. Am I missing something here in your post that 
> advances something that was not well understood already?

I don't think I'm advancing something that was not understood, but I
am arguing that it is not plain the benefits are worth the cost.  I am
pretty sure there are going to be DNS protocol enthusiasts who think
it's _not_ worth the cost.  Certainly we're going to have to have a
better argument than "We know we're introducing this breakage, so it's
ok."

I can imagine someone arguing, for instance, that if you're an
IPv4-only operator and you want people on v6 networks to be able to
use your services, put a AAAA record for a v4-compatible (or some new,
improved v4-compatible) address in the DNS.  If the response is, "But
v4-only operators might not do that, and v6 users will suffer," then
we're begging the question, because what we're debating is whether
altering DNS answers for some users is ok given the benefit thereby
achieved.  Such a person might also argue that supporting v4 users'
use of v6-only systems is just not a practical goal given the costs,
and if they want to use those services, that will give them an
excellent incentive to add IPv6 support; so for practical reasons, we
shouldn't try to solve that scenario.

Note that there's an important disanalogy between the current
proposals and the corporate network, split-brain case.  If I run a
split-brain DNS installation, I am taking the risk of leaks &c.  It's
my network, and if I want to do funky things inside it, that's
arguably my privilege.  But unless I'm missing something important,
most of the current proposals will change the DNS answers without the
operator of the source DNS answer needing to know anything about it.
The potential for increases in support costs and surprising results is
real, and that will cause people to object.

A

-- 
Andrew Sullivan
ajs@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 06:23:17 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE36D3A6CCB;
	Thu,  2 Oct 2008 06:23:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E62063A6960
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 06:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VY-XebAk2OHu for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 06:23:16 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 025153A6CCD
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 06:23:15 -0700 (PDT)
Received: from zrtphxm1.corp.nortel.com (zrtphxm1.corp.nortel.com
	[47.140.202.50])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m92DMd121797; Thu, 2 Oct 2008 13:22:39 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 09:22:37 -0400
Message-ID: <4B7DAC3FEFD35D4A96BDD011699050141B4864EA@zrtphxm1.corp.nortel.com>
In-Reply-To: <F698EDA9-1121-4324-93C3-D259A02125F7@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Single namespace
Thread-Index: Ackkj+PrJPybTzS1R+Gvp8wLwEv3pgAAdANw
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
	<F698EDA9-1121-4324-93C3-D259A02125F7@cisco.com>
From: "Ed Koehler Jr" <ekoehler@nortel.com>
To: "Fred Baker" <fred@cisco.com>, "Andrew Sullivan" <ajs@commandprompt.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

If that is the case then it would make sense to get this documented as a
common practice. We have to determine between idealized and realizable. 

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Fred Baker
Sent: Thursday, October 02, 2008 8:56 AM
To: Andrew Sullivan
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace


On Oct 2, 2008, at 12:52 AM, Andrew Sullivan wrote:

> While I understand that suggestion, and even have a certain amount of 
> sympathy with it, I note that there's a practical reason that many 
> DNS-heads don't like multiple versions of the namespace: they tend to 
> leak into other contexts.

no doubt. When we pretend something doesn't exist, it's pretty easy for
it to get screwed up.

I'll argue that recognizing the issue and designing a solution will work
better than whistling in the dark.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 06:41:39 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA9E13A685B;
	Thu,  2 Oct 2008 06:41:39 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DBB53A685B
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 06:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.604
X-Spam-Level: *
X-Spam-Status: No, score=1.604 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768,
	HOST_EQ_MODEMCABLE=1.368, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JaknOVmdcPjP for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 06:41:37 -0700 (PDT)
Received: from paoakoavas10.cable.comcast.com (paoakoavas10.cable.comcast.com
	[208.17.35.59]) by core3.amsl.com (Postfix) with ESMTP id 58A093A659B
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 06:41:02 -0700 (PDT)
Received: from ([10.52.116.30])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.51369361;
	Thu, 02 Oct 2008 09:40:16 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 2 Oct 2008 09:40:16 -0400
Received: from 192.75.88.176 ([192.75.88.176]) by
	PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) via Exchange
	Front-End Server webmail.comcast.com ([24.40.8.152]) with
	Microsoft Exchange Server HTTP-DAV ; Thu,  2 Oct 2008 13:40:15 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 02 Oct 2008 09:40:14 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Fred Baker <fred@cisco.com>
Message-ID: <C50A477E.1B4C4%alain_durand@cable.comcast.com>
Thread-Topic: [v4v6interim] Single namespace
Thread-Index: AckkC8rp6YGdhOyNRAG6f4MIRvojEAAiJr7x
In-Reply-To: <48E3E998.3020909@gmail.com>
Mime-version: 1.0
X-OriginalArrivalTime: 02 Oct 2008 13:40:16.0664 (UTC)
	FILETIME=[677AF180:01C92494]
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org




On 10/1/08 5:20 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:

> Although DNS64 is even more offensive to the computer science
> view, I can't see any realistic solution to the v4only/v6 only
> interworking problem that doesn't *require* different views
> of the namespace on the two sides, created dynamically to
> match the translation state.

In the case of v6->v4, there is actually a solution that *does*not*require*
creating different views of the namespace. The v6 host can use its IPv4
stack with Dual-stack lite, and the problem goes away entirely.

  - Alain.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 10:08:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 059413A69DA;
	Thu,  2 Oct 2008 10:08:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C56E03A69DA
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 10:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b1t1e36hcBJz for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 10:08:43 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
	by core3.amsl.com (Postfix) with ESMTP id D790F3A69CD
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:08:43 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29])
	by mail-out3.apple.com (Postfix) with ESMTP id 9004F3E07642
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:08:00 -0700 (PDT)
Received: from relay13.apple.com (unknown [127.0.0.1])
	by relay13.apple.com (Symantec Mail Security) with ESMTP id 7824428096
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:08:00 -0700 (PDT)
X-AuditID: 1180711d-a990bbb000000ede-cc-48e4fff0209f
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com
	[17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay13.apple.com (Apple SCV relay) with ESMTP id 583A928083
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:08:00 -0700 (PDT)
Message-Id: <EC6C96C1-E0F4-4172-9F2D-4FCAB92BD46F@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <20081002132252.GC38182@commandprompt.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 10:07:58 -0700
References: <BD0BD783-9F12-4415-85B3-9593584BB12D@cisco.com>
	<090C6392-9082-4660-AE68-FA384B788C03@apple.com>
	<20081002045221.GA36568@commandprompt.com>
	<AC9D9C70-5E07-4909-871D-A17E3D7F456D@apnic.net>
	<20081002132252.GC38182@commandprompt.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 2, 2008, at 06:22, Andrew Sullivan wrote:
>
> Such a person might also argue that supporting v4 users' use of v6- 
> only systems is just not a practical goal given the costs, and if  
> they want to use those services, that will give them an
> excellent incentive to add IPv6 support; so for practical reasons,  
> we shouldn't try to solve that scenario.

The corollary is a better argument: if application service operators  
would like to be reachable and available to IPv4-only clients, and  
making such services IPv6-only is just not a practical goal given the  
costs, then that will give such operators an excellent incentive to  
run a dual-stack site.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 10:31:16 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFC8328C172;
	Thu,  2 Oct 2008 10:31:16 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EF0C28C0ED
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 10:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.528
X-Spam-Level: 
X-Spam-Status: No, score=-106.528 tagged_above=-999 required=5
	tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M6IJa+uJVwkY for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 10:31:15 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by core3.amsl.com (Postfix) with ESMTP id 3430E28C172
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:31:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,352,1220227200"; d="scan'208";a="22496750"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 02 Oct 2008 17:31:23 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m92HVNKj011250
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 10:31:23 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92HVMQl024370
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 17:31:23 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 10:31:21 -0700
Received: from [192.168.3.109] ([10.21.75.252]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 10:31:20 -0700
Message-Id: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 13:31:19 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 17:31:20.0902 (UTC)
	FILETIME=[AF35C660:01C924B4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=854; t=1222968683; x=1223832683;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Potential=20interoperability=20issue |Sender:=20;
	bh=773c8CSJj5XltZfbMv15StOexeUbZg9ew/K3yPEo5yQ=;
	b=B9Qvc70pjws7UD9EydbIrSt5lFejMATZl6R4B+WttoCA6rk/0p38KpeQMM
	9g6J2pImHUQ9nlvfeOHxyx3x/FT5CmZ6Y19HPlJJb8bp1axhPjT+jxY9G0YT
	H9aY0BXdBI;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Sitting in your discussion of applications that may have issues  
through a translator. In the chat room, I asked:

> Dumb question from personal ignorance. SMTP opens with a HELO or  
> EHLO that has the IP address of the MTA in it. Does SMTP treat that  
> as a character string, or does it interpret the address? If it  
> interprets the address, it may have the same issue as FTP in a 6to4  
> environment


and James Woodyatt replied

> Some things interpret it as an address, e.g. rule processing engines  
> for deciding whether to require TLS.
> Or authentication.

That either calls for an ALG or appropriate code in the servers that  
can deal with an <> address even when the server doesn't have such an  
address. The simplest resolution might be to have the MTA have a leg  
in the IPv6 world and one in the IPv4 world. 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 10:51:26 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B3E53A6A0C;
	Thu,  2 Oct 2008 10:51:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB8503A6A77
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 10:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b+JSr+7JLaC6 for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 10:51:21 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23])
	by core3.amsl.com (Postfix) with ESMTP id D5A3E3A6A0C
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:51:21 -0700 (PDT)
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out4.apple.com (Postfix) with ESMTP id 2F1753FD1451
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:51:44 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 1B244464003
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:51:44 -0700 (PDT)
X-AuditID: 11807135-ab983bb000000d0e-1e-48e50a2fec6b
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com
	[17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay12.apple.com (Apple SCV relay) with ESMTP id EA15B420003
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 10:51:43 -0700 (PDT)
Message-Id: <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 10:51:43 -0700
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 2, 2008, at 10:31, Fred Baker wrote:
>
> Sitting in your discussion of applications that may have issues  
> through a translator. In the chat room, I asked:
>
>> Dumb question from personal ignorance. SMTP opens with a HELO or  
>> EHLO that has the IP address of the MTA in it. Does SMTP treat that  
>> as a character string, or does it interpret the address? If it  
>> interprets the address, it may have the same issue as FTP in a 6to4  
>> environment
>
> and James Woodyatt replied
>
>> Some things interpret it as an address, e.g. rule processing  
>> engines for deciding whether to require TLS. Or authentication.

The EHLO message has a domain name.  In SMTP, the Domain grammar  
production includes a special case allowing for an IP address literal  
instead of a FQDN.  This domain name in the EHLO message is sometimes  
used to make decisions about TLS and AUTH requirements.  So, too, can  
the IP address of the connecting client be used for such decisions.

Whether an ALG is required to cope with this is a question I'm not  
prepared to answer.

> That either calls for an ALG or appropriate code in the servers that  
> can deal with an <> address even when the server doesn't have such  
> an address. The simplest resolution might be to have the MTA have a  
> leg in the IPv6 world and one in the IPv4 world.

I would agree that this is the simplest way to handle SMTP servers.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 12:37:31 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33DC328C134;
	Thu,  2 Oct 2008 12:37:31 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7B8F28C0F6
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 12:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y5WYm4BiU2n6 for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 12:37:29 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
	by core3.amsl.com (Postfix) with ESMTP id CC9AA28C0F4
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 12:37:29 -0700 (PDT)
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out3.apple.com (Postfix) with ESMTP id 9E7A43E0C642
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 12:37:50 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 8BCD8464002
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 12:37:50 -0700 (PDT)
X-AuditID: 11807135-a897dbb000000d0e-ec-48e5230e2560
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com
	[17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay12.apple.com (Apple SCV relay) with ESMTP id 5291C420006
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 12:37:50 -0700 (PDT)
Message-Id: <31D693EF-453A-4120-A7E4-ADC86C0D42DE@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
In-Reply-To: <C50A477E.1B4C4%alain_durand@cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 12:37:50 -0700
References: <C50A477E.1B4C4%alain_durand@cable.comcast.com>
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 2, 2008, at 06:40, Alain Durand wrote:
> On 10/1/08 5:20 PM, "Brian E Carpenter"  =

> <brian.e.carpenter@gmail.com> wrote:
>>
>> Although DNS64 is even more offensive to the computer science
>> view, I can't see any realistic solution to the v4only/v6 only
>> interworking problem that doesn't *require* different views
>> of the namespace on the two sides, created dynamically to
>> match the translation state.
>
> In the case of v6->v4, there is actually a solution that  =

> *does*not*require*
> creating different views of the namespace. The v6 host can use its  =

> IPv4
> stack with Dual-stack lite, and the problem goes away entirely.

Except, the v6->v4 case is only half the picture.  The problem is  =

entirely in the other half.  It does not go away.  You have simply  =

chosen not to see it.

IPv6 hosts running DS-Lite can initiate flows to IPv4 endpoints, but  =

they do not have public IPv4 addresses and they can't make their  =

services available to IPv4-only hosts without help from the service  =

provider.  From the perspective of IPv4-only clients, DS-Lite servers  =

are in a walled garden.

Brief digression: if you want to make any kind of services available  =

to IPv4-only clients, then you have two basic choices:

   + Make your services available over IPv4 at publicly assigned
     and routed addresses.  Advertise DNS content normally.

   + Make your services available through an IPv4 translator.
     Advertise DNS content with addresses translated into the
     public IPv4 realm.

In the second case, from the perspective of IPv4-only clients, it does  =

not matter whether the server is in a private IPv4 realm or in the  =

public IPv6 realm.  If you'd like your IPv6 services to be available  =

to IPv4-only hosts, you have only two choices: A) run full dual-stack  =

servers (not DS-Lite), or B) deploy a translator with a DNS gateway to  =

the public IPv4 horizon.

As it happens, here at Apple, we have a service called Back To My Mac=99  =

(part of our MobileMe=99) service that basically does option B) today,  =

because our customers often don't full native IPv4 service, i.e. they  =

have private networks.  (Interestingly, we avoided the whole IPv4  =

address realm conflict problem by tunneling IPv6 over ESP/UDP/IPv4  =

through NAT with NAT-PMP and using DNS-SD tricks to manage the  =

equivalent problem to what is under discussion here, but that's a side- =

track for now.)

Please take note of the problem if you try to make Back To My Mac=99  =

work by tunneling inside ESP transport mode IPv6 in addition to ESP  =

IPv4/NAT-T.  The additional mode would be a simplification of the  =

current mode, actually, because NAT-PMP wouldn't be required (though,  =

ALD might be, depending...).  However, it would only be good for IPv6- =

capable clients-- IPv4-only clients would still have no recourse if  =

the SP NAT does not help with the IPv4 autotunnel.  You might imagine  =

deploying something like IVI or NAT64, so that IPv6 servers register  =

their tunnels in the DNS through a DNS64 gateway that knows about the  =

NAT64 point where ESP/UDP/IPv4 is translated into ESP/IPv6, but that  =

would be not-at-all anything like what you see in the DS-Lite draft.   =

It *also* doesn't look like the current NAT6/NAT64/IVI/what-have-you  =

proposals because nothing in those drafts talks much about DNS-SD (or  =

its moral equivalent).  They seem to just hand-wave over that problem.

Summarizing, these are the sorts of problems that have me convinced  =

that trying to make IPv6-only services reachable from IPv4-only  =

clients is a losing game in the long run.  We should concentrate our  =

coexistence effort on the following problems:

   A) Ensuring that *all* kinds of dual-stack clients see IPv6 servers,

   B) Ensuring that IPv4-only clients see dual-stack servers,

   ...and finally...

   C) Ensuring that dual-stack servers can register equivalently in  =

the DNS for
      both IPv4-only clients and dual-stack clients,

   ...while...

   D) Bearing mind that Teredo hosts and nodes in 6to4 sites may be  =

dual-stack,
      and they may be either/both clients and/or servers.  (No, I  =

don't care
      about ISATAP today.  I'm not going to care until ISATAP  =

deployments are
      numerous enough to matter.)

At this point, I view everything else as a dangerous distraction from  =

our basic coexistence problem set, and it should be deferred until the  =

happy eventuality that they become a more pressing problem than they  =

are today.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 13:59:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C59453A67F6;
	Thu,  2 Oct 2008 13:59:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF1023A67F6
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 13:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5Q6o0O7gDeGm for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 13:59:00 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22])
	by core3.amsl.com (Postfix) with ESMTP id 3E8893A67AD
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 13:59:00 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52])
	by mail-out3.apple.com (Postfix) with ESMTP id 7F9703E0EFE4
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 13:59:27 -0700 (PDT)
Received: from relay14.apple.com (unknown [127.0.0.1])
	by relay14.apple.com (Symantec Mail Security) with ESMTP id 6AFB528043
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 13:59:27 -0700 (PDT)
X-AuditID: 11807134-aa930bb000000ef9-0e-48e5362ffc9d
Received: from il0602f-dhcp175.apple.com (il0602f-dhcp175.apple.com
	[17.206.50.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by relay14.apple.com (Apple SCV relay) with ESMTP id 4010A28040
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 13:59:27 -0700 (PDT)
Message-Id: <FD4E2376-A197-4D13-9CA5-D137D8EF33CF@apple.com>
From: james woodyatt <jhw@apple.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 13:59:27 -0700
X-Mailer: Apple Mail (2.929.2)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v4v6interim] questions for the group
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

everyone--

Scenario 1: IPv4 sites reaching the global IPv4 Internet?

	Q) do you have to cope today?
	A) Yes.  NAT444 is already a call-driver for me.

	Q) do you think you may have to cope in the future?
	A) Yes.  Every day in some new way.

	Q) are you making any plans for coping?
	A) I have a bug debt you wouldn't believe.

Scenario 2: Providers running out of private IPv4 space?

	Q) do you have to cope today?
	A) Not a provider.

	Q) do you think you may have to cope in the future?
	A) If DS-Lite deploys, it will mean work for me.

	Q) are you making any plans for coping?
	A) Trying to adapt to ISP plans in this regard.

Scenario 3a: Enterprise "greenfield" IPv6-only networks?

	Q) do you have to cope today?
	A) No.

	Q) do you think you may have to cope in the future?
	A) I'm actively trying to keep my organization from
	worrying about this.  I think other organizations
	that worry about this are wrong to do so.

	Q) are you making any plans for coping?
	A) I'm actively stomping down efforts in this direction.

Scenario 3b: Wireless "greenfield" IPv6-only networks?

	Q) do you have to cope today?
	A) No.

	Q) do you think you may have to cope in the future?
	A) I see no real reason to think so.

	Q) are you making any plans for coping?
	A) No.

Scenario 4: IPv6 hosts reaching private IPv4-only servers?

	Q) do you have to cope today?
	A) No.

	Q) do you think you may have to cope in the future?
	A) No.

	Q) are you making any plans for coping?
	A) No.

Scenaio 5: IPv4-only hosts reaching IPv6-only servers?

	Q) do you have to cope today?
	A) No.

	Q) do you think you may have to cope in the future?
	A) No.

	Q) are you making any plans for coping?
	A) No.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 14:08:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C87273A67F6;
	Thu,  2 Oct 2008 14:08:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D34813A67F6
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 14:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hxJLj14duzJd for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 14:08:04 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168])
	by core3.amsl.com (Postfix) with ESMTP id 349C43A67F5
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 14:08:04 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1318750wfd.31
	for <v4v6interim@ietf.org>; Thu, 02 Oct 2008 14:08:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:subject:content-type
	:content-transfer-encoding;
	bh=N4tmXPmFoPf4nXCDJeCYpQMNWOw+QQkCmMEZQK0Mum4=;
	b=eDnYm/2IAB5O2zcyAG+0DybXkRXnS1Ix1uLL+rQblHvH83rcyC/qPZ16uWQITZytqU
	OLt5SJzImlsFxNzx2UrU6Eqd1A7Ajrxeodt3UsxWxAasqKx7JXeMVV4abqE3Q/QhYAV5
	H3hYJuXBE9G4NgNd2bUtxEDzwEE53yjuAeO3M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to
	:subject:content-type:content-transfer-encoding;
	b=uwFHgu8s4sYGqAMZK6PVzwhex9hM4qjl6beIUYXECX/tjfM+m25u5UjfZUSBalrk26
	SzFik+G2Kx4pXVikqwcxyIEl+SegUwKnEYSqcyFWqk/6FUSbDfw0YNSzcEl3+61eHwbC
	qcfBISbGWlQvG7M+QoumCyhHgSBYVYkku/+KI=
Received: by 10.142.180.19 with SMTP id c19mr36226wff.263.1222981705360;
	Thu, 02 Oct 2008 14:08:25 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 22sm3044808wfg.13.2008.10.02.14.08.23
	(version=SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 14:08:24 -0700 (PDT)
Message-ID: <48E5383F.4080108@gmail.com>
Date: Fri, 03 Oct 2008 10:08:15 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: v4v6interim@ietf.org
Subject: [v4v6interim] Half a hum for IPv6 Hosts Reaching Private IPv4-Only
	Servers
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

The reason I was lukewarm on this is because it just seems wrong
to encourage people to run *servers* in private space. Although
global IPv4 space is getting scarce, putting servers in private
space isn't the right thing to encourage. Like NAT444 it
doesn't incent migration to v6. But I'm afraid it's probably
unavoidable anyway, thus +0.5 of a hum.

   Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 14:14:13 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0888E3A690A;
	Thu,  2 Oct 2008 14:14:13 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 39EDD3A68AB
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 14:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.531
X-Spam-Level: 
X-Spam-Status: No, score=-106.531 tagged_above=-999 required=5
	tests=[AWL=0.068, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qyVN3RmW9hPE for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 14:14:10 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 9ABB83A67F6
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 14:14:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,353,1220227200"; d="scan'208";a="167647791"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 21:13:51 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m92LDpAj032524
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 14:13:51 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m92LDpxN007410
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 21:13:51 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 14:13:51 -0700
Received: from [192.168.4.124] ([10.21.68.197]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 14:13:51 -0700
Message-Id: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
From: Fred Baker <fred@cisco.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 17:13:50 -0400
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 02 Oct 2008 21:13:51.0349 (UTC)
	FILETIME=[C4B25250:01C924D3]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=523; t=1222982031; x=1223846031;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20BOF=20discussions |Sender:=20;
	bh=V+4k6YJ+csfEWyMOIbvFbSvMEYLSczyqMnuCsVGwq8A=;
	b=Zu9Q5+fdhp/72gfIYGTD5fpHFtj4LWjtjmSC5SDjDxcfDNyX9/ghnZchCf
	IBG3GeZ3YFw4CayrDPXYjPWLytqp0kDliuR+1DPe0p/Lvp0zfds5fvVickve
	Zw0LMAIyzi;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

So various folks are going to be doing a lot of work in email and such  
in the next few weeks. May I suggest that the ADs schedule a BOF for  
the translation solution and one for the tunneling solution (and one  
for the 4-4-4 solution?) separate from WGs, to enable the doc authors  
to sit down together and discuss?

I would also suggest that you set of mailing lists for these BOFs,  
perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them  
to this forum and let people sign up the usual way.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 14:53:48 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97D2428C0D9;
	Thu,  2 Oct 2008 14:53:48 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AFC73A6818
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 14:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.91
X-Spam-Level: *
X-Spam-Status: No, score=1.91 tagged_above=-999 required=5 tests=[AWL=-1.814, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6,
	MIME_QP_LONG_LINE=1.396, ROUND_THE_WORLD_LOCAL=2.696,
	SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9jI4xxjxp7U4 for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 14:21:00 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 7A7723A68E5
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 14:20:52 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m92LL7mN025376
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 16:21:07 -0500 (CDT)
Received: from mail.net.alcatel.com.hk (h202-65-2-130.alcatel.com
	[202.65.2.130])
	by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id m92LL3Ds020032
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 16:21:03 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com
	[135.254.109.35])
	by mail.net.alcatel.com.hk (8.13.7/8.13.7/Alcanet1.0) with ESMTP id
	m92L1x4e028027
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 05:02:03 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.25]) by
	sgsinsbhs02.ad4.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 3 Oct 2008 05:20:57 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 05:20:51 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D01FB1007@SGSINSMBS02.ad4.ad.alcatel.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Meeting Minutes Thursday
Thread-Index: Ackk1L61WNitc9AyS1ubqU+jnQKPZw==
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: <v4v6interim@ietf.org>
X-OriginalArrivalTime: 02 Oct 2008 21:20:57.0220 (UTC)
	FILETIME=[C2891440:01C924D4]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.57 on 135.1.218.53
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
X-Mailman-Approved-At: Thu, 02 Oct 2008 14:53:48 -0700
Subject: [v4v6interim] Meeting Minutes Thursday
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0376426952=="
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

This is a multipart message in MIME format.

--===============0376426952==
Content-class: urn:content-classes:message
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_0049_01C92528.90A6F470"

This is a multipart message in MIME format.

------=_NextPart_000_0049_01C92528.90A6F470
Content-Type: multipart/mixed;
	boundary="----=_NextPart_001_004A_01C92528.90A93E60"


------=_NextPart_001_004A_01C92528.90A93E60
Content-Type: multipart/alternative;
	boundary="----=_NextPart_002_004B_01C92528.90A93E60"


------=_NextPart_002_004B_01C92528.90A93E60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

For everyone's review and comment.

 

Cheers!

 

David Miles

Alcatel-Lucent

Senior Architect

IP Division

Level 3, 215 Spring Street

Melbourne VIC 3000, Australia

Email: david.miles@alcatel-lucent.com.au

Phone: +61 3 9664 3308

Mobile: +61 417 684 617

 


------=_NextPart_002_004B_01C92528.90A93E60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>For everyone&#8217;s review and =
comment.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Cheers!<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'>David =
Miles<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Alcatel-Lucent<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Senior Architect<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'>IP =
Division<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.5pt'>Level =
3, 215
Spring Street<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Melbourne VIC
3000, Australia<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Email: <a
href=3D"mailto:david.miles@alcatel-lucent.com.au">david.miles@alcatel-luc=
ent.com.au</a><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Phone: +61 3 9664
3308<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.5pt'>Mobile: +61 417
684 617<o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_002_004B_01C92528.90A93E60--

------=_NextPart_001_004A_01C92528.90A93E60
Content-Type: text/plain;
	name="minutes.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="minutes.txt"

=0A=
=0A=
--------=0A=
Thursday=0A=
=0A=
IVI:=0A=
----=0A=
CERNET exists in two halves, the IPv4 and IPv6 half (CNGI-CERNET2). IVI =
gateways are located between the two networks. CERNET2 is single-stack =
IPv6.=0A=
Because of low internet penetration in China, major operators (fixed and =
mobile) are interested in IVI.=0A=
Lessons learnt:=0A=
- The only viable option for future Internet is IPv6=0A=
- Building a new IPv6 network is more cost effective than a dual-stack =
network (especially for un-wired networks)=0A=
- Stateless is very important (vs stateful)=0A=
=0A=
The IVI model leverages IPv6 address planning in order to make a 1:1 =
mapping between IPv4 and IPv6. You do not randomly select IPv6 =
addresses. =0A=
Marcello: I don't understand. If you want communications from IPv4 to =
IPv6 you need to make that choice - you need to select a few addresses =
that need static mapping. If you want communications from IPv6 to IPv4 =
you don't need that static mapping.=0A=
Xing: Correct. But we do both ways.=0A=
Dave: The hosts in the IVI network. This is still connecting global IPv4 =
address space. These consume just as much address space as if they were =
in the global IPv4 Internet. What about IPv4 exhaustion. This technique =
will become less useful over time.=0A=
Alain: I agree with what Dave said. IVI is an optimisation to allow a v4 =
over v6 tunnel to be sent directly to the machine.=0A=
Fred: Responding to Dave's point re IPv4 availability. The comparison is =
to dual-stack mode where you address every system in the IPv6 domain. In =
the latter you need to put IPv4 addresses on everything, but in IVI you =
don't need IPv4 addresses on clients. =0A=
=0A=
Addresses IPv4 to IPv6 IVI (SIIT extension, stateless)=0A=
IPv6 IVI to IPv4 (SIIT, stateless)=0A=
=0A=
Address format:=0A=
LIR prefix (ie, /40)=0A=
Embedded IPv4 address from bits 40-to-72!=0A=
=0A=
Dave: Is the 40 bit boundary fixed, or completely under control of the =
LIR?=0A=
Xing: It is not fixed=0A=
Dave: So the 72-bit boundary isnt fixed either? =0A=
Xing: No=0A=
Dave: SIIT does not use v4 compatible space, uses v4 translatable space=0A=
Remi: You mentioned port multiplexing like A+P and SAM. Is this an idea =
or something you have?=0A=
Xing: Today I only focused on 1:1 stateless.=0A=
Marcello: I understood we have this address fromat because you want to =
keep routing on the highest /64 prefix, you dont want to route on the =
more specifics that go beyond the /64 boundary. If you want to reach =
different parts of the v4 internet you inject routes that are shorter =
than 64 bits. Do we have a problem if we route on more specific than =
/64? Do we have a problem with routers?=0A=
Dave: I dont think there is a routing problem. There are some problems =
with putting it at the end that may depend on implementation. Because =
your using LIR prefix it does not start with binary 000, and hence hosts =
do not know this. You now have a problem with the address space =
definition at 64-bits Interface Id boundary. You may have =
implementations with embedded assumptions around 64-bit boundaries.=0A=
Fred: I believe the NAT64 draft has an option for LIR prefix - here =
(IVI) we have an LIR prefix. The argument for using a LIR prefix is that =
its easier for the network admin to manage routes. They can choose an =
exist gateway instead of just hoping when there are more than one =
gateway. They can manage routing more clearly=0A=
X: Yes there will be impact to routing scalability. There will be very =
specific prefixes in the global routing table. This in to a problem =
specific to this proposal, its general, perhaps it should not stop us =
from doing this.=0A=
Randy: Everyone will route it probably, but its one more memory fetch =
down the tree. [Comment that there is no statement about ensuring no =
fixed 64-bit boundary]=0A=
=0A=
Dave: Interesting routing question: Since a single IPv4 address has =
multiple IPv6 addresses. The state we want is most hosts are IPv6. We =
have apps that are v6 and start doing referrals. If we are in one ISP =
and refer the address to another customer in another ISP - is he still =
able to reach it? How will the routing policy be configured?=0A=
Fred: It is a routing policy problem=0A=
Dave: If this were deployed by multiple ISP would they do it right?=0A=
Fred: They would only advertise this space within their domain=0A=
Dave: In which case referrals might not work. So we cant assume =
referrals will work with this=0A=
Alain: If you use NAT64 with a special prefix that represents the IPv4 =
internet and do referral then youre going to have a problem - its not =
just IVI. You cant expect a routing policy is put into place. Any time =
you use a prefix of your own choosing you will have the same problem.=0A=
=0A=
Routing in IVI networks=0A=
=0A=
One IVI gateway, or many=0A=
=0A=
Fred: One comment on this magic vs LIR prefix. If you want to talk about =
routing policy and what SP are likely to do. I expect a magic prefix =
(000) are more likely to not be advertised outside a domain vs a domain =
specific prefix. These are specific to a service (translation) here the =
LIR prefix are just LIR prefix. If you want to use policy as a way of =
saying this is a bad idea, the policy argues against the 000 type of =
prefix. I would be more interested in using LIR prefixes not special use=0A=
Marcello: I thought that too, but, suppose I am in two different ISP but =
I am using unique prefixes for mapping. If a referral passes the =
application data from one ISP to another one. Referrals work not because =
it is routed, but because they have the same meaning and are translated. =
You dont need this to be advertised (000 prefixes) for this to work. It =
can be directly translated. I assume you have IVI/NATPT - not that you =
have v4 host connectivity, but have access to a NAT-PT service.=0A=
Fred: If we are talking about translated networks.  If you are going =
through translators, how are you going to manage the routing? If policy =
is going to get in the way of one proposal, what will happen - its going =
to be for LIR prefixes and against special use prefixes. The IPv4 doesnt =
come into it=0A=
Marcello: But we are talking about referrals. If a well-known prefix is =
used referrals will work - im not saying this means this is a better =
solution, just thta referrals work=0A=
Alain: There are two prefixes. The address prefix represents the v4 =
Internet when you are on a v6 site. The two prefixes dont have to be the =
same. When i configure my IVI host they can have 2002 prefix. When i =
want to get a packet back to IPv6 this matters, when I want to send my =
packet to an IPv4 world you have a better chance using a well known =
prefix=0A=
Randy: ISP routing policies are not a roulette game. ISP will route it =
if they need to.=0A=
Remi: This discussion is similar to the case of comparison between 6to4 =
and 6RD? Referring IPv6 to customers has worked, youre differing on the =
LIR prefix as it is not a generalised tool. There is a strong argument =
for ISP independance.=0A=
Eric: There is a lot of 6to4 out there!=0A=
Remi: Yes, have they any guarantee that the v6 packets they send will =
return? There is no guaratee.=0A=
Eric: 70% that hit ipv6.google.com have 6to4 addresses=0A=
Remi: How they do it I dont know. =0A=
=0A=
Prefix Announcement in IVI=0A=
=0A=
Lots of routing policy discussion. Here is an example (routing policy) =
that has been working for 2 years. =0A=
=0A=
DNS is similar to other solutions. There will be A to quad A record =
synthesis. =0A=
=0A=
Marcello: When you say you support multiple IVI gateways, this not the =
case for IPv6-initiated communications?=0A=
Xing: No=0A=
=0A=
Stateless operation=0A=
=0A=
There is stateless operation/stateless mode. There is a SIIT extension =
(prefix-specific address). The transformation of addresses is automatic =
and requires no state.=0A=
=0A=
Stateful (NAT-PT replacement)=0A=
Address format is the same as the stateless mode. The address and port =
are mapped to IPv6 addresses in a stateless manner=0A=
=0A=
Operation of gateway:=0A=
=0A=
Stateless is preferable due to end-to-end principle and simplicity=0A=
In summary IVI reachability:=0A=
=0A=
IPv6 initiated (1:1 mode).=0A=
=0A=
Alain: When you do DNS you synthesise records so you have the same =
DNSSEC issues?=0A=
Marcello: These are not the same issues as NAT-PT as i understand. =
NAT-PT intercepts packets. If you place the DNS ALG on the local DNS =
server or in the resolver in the host then this perfectly matches DNSSEC =
trust models. You validate and then synthesise. So this works. NAT-PT =
intercepts and does it on the fly. As this case is implemented in the =
DNS server this can be solved.=0A=
Alain: Key work, can be solved=0A=
Marcello: The point is that there are 2 trust models in DNSSEC - =
validating server or validating resolver. Here you place the =
functionality of the syntheses in the place you validate - you have to =
do it right after you validate. If you want to do it is the resolver =
you'd need to put the synthesis there.=0A=
Dave: Diagrams are a bit confusing. Back to the LIR discussion when you =
have v6 initiated communication. In going from global v6 to global v4 =
the other thing you can get for free - youre mapping entire v4 address =
space. Youre also mapping any RFC 1918 space. With the LIR prefix, and =
as they are different for each ISP, you can get a different prefix for =
each RFC 1918 space.=0A=
Andrew: Where you are going to do validation in DNSSEC. There are two =
directions here, but the overall consensus is that it would be better to =
have validation as close to the end as possible. If you assume a stub =
resolver on the client it becomes too appealing as an attack target. It =
means everyone will need a validator or DNSSEC may not work. Brians =
suggestion is that if you have a standardised prefix (and can learn what =
it is in a secure fashion) you can strip it off, validate, then put it =
back on. The hard part is learning what that prefix is.=0A=
Marcello: In any case you need to learn that prefix and it is not =
specific to this mechanism.=0A=
Laurent: mobile are important. I dont see how this works with existing =
IETF-defined mechanisms (such as PMIP) - how would this work in a PMIP =
environment. This mechanism much work in a mobile environment.=0A=
Marcello: I dont see any problem from a MIP perspective. =0A=
x: The reason is once you get a new IP address we initiate another =
instance of this protocol. =0A=
=0A=
Choices: Get no IPv6 jsut do IPv4 - no way=0A=
Get ipv4 and use them for NAT - state and complexity=0A=
Get IPv4 and deploy dual stack. =0A=
Get IPv4 dresses and use them to sell and IVI + general IPv6 service. =
This is the IVI proposal.=0A=
=0A=
Y: Do you have comment or experiance on the protocols that are carrying =
IP addresses in their payload - how does this work with IVI?=0A=
Xing: We tried SSH - but yes when addresses are embedded you do need ALG.=0A=
Y: In the path - yes you would need then an ALG. So a SIP client will =
not work through=0A=
X: In the previous slide you had a v6 adoption s-curve. The time at =
which IPv4 addresses are sufficiently expensive, you said one was to get =
IPv4 addresses and use them as IVI addresses - how does that differ to =
the way IVI works anyway - is that different?=0A=
Xing: No=0A=
Alain: Id like to follow up: Can we relate this discussion to =
yesterday's with Randy with the NAT box in the middle and how to get =
control. We looked at control at the edge yesterday. How is this =
possible in IVI=0A=
Xing: The combination of address and port can be done in stateless =
fashion. For servers you could embed port number into the IVI address=0A=
Alain: If i am a normal IPv6 node how do I know what is happening?=0A=
Xing: In the stateful case?=0A=
Alain: Yes=0A=
Xing: Like NAT-PT - the gateway (IVI) will keep the state=0A=
=0A=
Mark: If I have an ALG on the IPv6 domain - say a SIP v6 client, that =
proxy needs to have a leg on the v4 domain. Therefore these is a =
separate device that forwards packets, separate to the IVI gateway, =
right?=0A=
Xing: Yes=0A=
Fred: There is some process - but it can be in the same device or a =
different one. We do need work regardless of translation. Regardless of =
approach some apps need work. I dont think that helps us choose among =
approaches.=0A=
=0A=
=0A=
---=0A=
Marcello: Improving NAT-PT=0A=
=0A=
Will talk about what can be improved. NAT64 is not our draft - i just =
meant the functionality from IPv6 into IPv4. I am comparing the basic =
NAT-PT. Not talking about static mapping on the IVI or that kind of =
stuff - just basic NAT-PT.=0A=
=0A=
Issues with protocols embedding IP addresses. Common. Solution: v4 NAT =
is to use ICE. Recommend we follow BEHAVE requirements in any NAT we =
define (for v6-v4).=0A=
NAPT-PT Redirection: It only works for TCP and UDP, what about other =
protocols? You dont have a demux. Recommend: whatever NAT we define =
needs to support whatever protocols we want to work. If we need to do =
more protocols lets just do them.=0A=
=0A=
NAT-PT binding state decay:=0A=
State needs to be refreshed. RFC 2266 predated BEHAVE. Recommend: Follow =
BEHAVE requirements for mapping refresh timer. Hosts now know what to =
expect. Also can use ICE.=0A=
=0A=
Loss of Info:=0A=
Flow label, extension and ICMP lost.=0A=
Even RFC 4966 states this isn't really a big issue. I don't think there =
is much we can do about this, but I do not think (and they [RFC 4966 =
authors]) do not think its an issues either. There has been an issue =
around DSCP so I think we may need more work there.=0A=
=0A=
NAT-PT and frag - Alain for later=0A=
=0A=
SCPT and multihoming.=0A=
Follow the IPv4 NAT recommendation for multihoming=0A=
=0A=
NAT-PT for a proxy correspondent node for MIPv6=0A=
This is a non issue from MIPv6 experts=0A=
=0A=
NAT-PT and multicast=0A=
I dont know what this means - is something needed?=0A=
=0A=
Brian: NAT-PT and multicast - any translation approach in multicast =
needs more work. Is it needed, I'm not sure? I have heard some that say =
you do - but the arguments have not been compelling. If anyone has =
compelling ideas let me know=0A=
Marcello: I think we should at a minimum, what things do we need the NAT =
to do to prevent future problems. Issue with mulitcast routing is RPF =
checks, you have to be able to have cross-domain knowledge in the =
routing. They are topics worth identifying.=0A=
Z: I will give an example using multicast. We have received many =
requirements to support multicast. I cannot explain how they want to be =
used, but I have received many requests. =0A=
Y: There is BEHAVE document on multicast so there has been some thought=0A=
Dan: There is a draft/RFC on mulitcast in IPv4 - but not cross v4/v6. =
There has been some thought on it though=0A=
=0A=
As first conclusions, the main issue with current NAT-PT it predates =
BEHAVE work. It is missing things but they can be solved with the BEHAVE =
knowledege. Most can be solved by just working on the spec. Let's just =
write a better spec.=0A=
=0A=
The DNS ALG issues:=0A=
Network topology contraints: DNS queries and data packet must follow the =
same path. Spoofing DNS messages include synthetic records in DNS. For =
the 4-to-6 direction the DNS reply is associated with the NAT state. For =
6-to-4 the DNS function can be separated. =0A=
=0A=
Jari: Are you saying you could avoid 6-to-4 component?=0A=
Marcello: Yes=0A=
X: You were saying you need co-location - but it could be seperated and =
communicated to the transaltor=0A=
Marcello: you can solve this by sync DNS and NAT. But for multihoming =
you need sync between different NAT boxes. Here its sync between DNS and =
NAT.=0A=
=0A=
This issue is solved in 64, but harder in 4-6. Seperate NAT64 and NAT46 =
and make a spec for NAT64.=0A=
=0A=
Scalability and SPOF:=0A=
You have a SPOF doing DNS and NAT. Not true for NAT64 only NAT46. You =
can get redundancy in NAT64 because there is no state.=0A=
=0A=
When the NAT state disappears you no longer have these addresses so you =
have a problem. With NAT46 you create the state when you see the query =
by the DNS. So then you have to keep it for a long time even without =
packets. In NAT46 DNS is creating the NAT state. We can solve the easy =
part in NAT64 and look at other solutions for NAT46. Again, separate =
NAT64 and NAT46 and follow BEHAVE for NAT64.=0A=
=0A=
DoS Attacks:=0A=
You reserve the whole address on DNS, on data attack its less efficient =
because you reserve just one port. We need to separate NAT64 and NAT46 =
again, there are different problems for both.=0A=
=0A=
Most severe issues are easily solved for NAT64 but more work is needed =
for NAT46. I suggest we separate them.=0A=
There are some issues when you associated a given prefix to a given NAT =
box because you need some relationship between the DNS response and the =
NAT box to which you communicate. The DNS message must be associated =
with a specific NAT box somewhere.=0A=
Some scenarios don't need a DNS ALG. Could have a different spec, one =
for DNS64 and one for NAT64.=0A=
=0A=
Jari: I don't think the separation is useful. =0A=
Marcello: If you read this spec, NAT-PT has different components, and =
the whole NAT-PT got bashed because of one of the parts have problems. =0A=
Dave: I agree there is a need to distinguish the different cases. Where =
you put them and how many specs I don't feel strongly on. Scenario 4 is =
a subset of the NAT64 domain. The NAT64 domain is a subset of larger =
things. NAT64 is a subset of what IVI does. There are 3 levels , the =
full IVI, the NAT64 portion, and the scenario 4 portion. If you put them =
all together you get one big solution (like IVI). Im not arguing for =
either separate or combined, but if you believe they should be closer =
together in one spec, then you could argue the NAT64 and IVI should be =
combined. Or you think they should be separated to get compliance to =
individual components (ie, I support this RFC). There is also another =
one - how fast each piece can advance in the standardisation process - =
you could also want to separate based on timing. Ie, NAT64 is easy, =
NAT46 is hard - do NAT64 APAS. NAT46 as experimental, etc.=0A=
Z: I think splitting is a good idea. I would argue to keep NAT64 and =
DNS64 together. I don't think we have got much attention from DNS folk - =
and it needs that attention. This may be one reason to pull them out and =
we need the involvement of the DNS community.=0A=
=0A=
Dual stack to single stack - native connectivity or translated =
connectivity? When you have v4/v6 only hosts this can be easily solved. =
But when dual-stack communicates to a v6-only node things are harder. =
You can play with policy table. EDNS0, try to use well-known prefixes. =
None of them really achieve what we want. Its hard to do this in an =
automatic way. Recommend to use described tools.=0A=
=0A=
Dave: This is a case that can be solved without DNS64, a dual stack can =
have A and AAAA records. You don't even need a DNS64. if you collect =
these by scenario you may be able to evaluate the problems a little =
easier. =0A=
Andrew: How much are we willing to insist that the v6 hosts need to have =
some intelligence. We talk about a DNS ALG at a recursive resolver, and =
this v6 only host doesn't need anything. Other times it does need =
knowledge. We need to decide which one.=0A=
Marcello: You may prefer the translated instead of the native, and it =
still works. There are other issues with DNSSEC, but there are no =
deployed DNSSEC resolvers today anyway. So we could do DNSSEC changes =
and these changes together. Basic connectivity should be provided to all =
legacy hosts. Optimised features may require some changes.=0A=
X: If you want DNSSEC to work you do need to do it in the host. That is =
the long-term preferred solution. But for compatibility you could use =
the other solution.=0A=
Alain: you could always avoid translation in the first place and just =
use the IPv4 stack. If you do that - none of the DNSSEC issues arise. =0A=
Dave: There are 3 places to solve the problem. Authoritative DNS server. =
Only works is certain scenarios, other places: validating recursive =
resolver, or a validating stub resolver. And where we should do it =
depends on the scenario. Eventually all host should be doing it , but it =
may take a while to get there. It has to be a scenario specific thing. A =
validating resolver solution may be okay in some scenarios.=0A=
Andrew: We do have running code for stub resolvers. =0A=
=0A=
Inappropriate translation of responses to A queries.=0A=
NAT PT spoofs packets. Its a MITH in NAT-PT, so just place it in the =
right place.=0A=
=0A=
DNS-ALG and multiple addresses node=0A=
As you're not creating state in NAT64 you don't have this problem.=0A=
=0A=
Most issues don't apply to NAT64. The idea of the DNS ALG picking up =
things on the fly is a bad one, put it in DNS function or resolver. One =
way to avoid some problems with DNS synthesis could be to use a global =
prefix.=0A=
=0A=
Suresh: If I have a dual-stack node, youe're making it prefer =
translation or native IPv4 and IPv6. Its up to the node to resolve this =
issue. I do not agree you should put the onus on the node to decide =
this. If I prefer v6 over v4 you'd use the synthesised quad A. =0A=
Marcello: You could solve it in the policy table=0A=
Dan: If we had a cool secure way of learning what the prefix is, we get =
a new address. Now we know right away how to do DNSSEC and reconfigure =
our own policy table. Its not a rip out the stack, this could solve many =
issues. =0A=
Marcello: But it doesn't solve the legacy problems=0A=
Dan: If you want to do something new, do something new=0A=
=0A=
=0A=
=0A=
sNATPT=0A=
------=0A=
Not every application uses DNS to resolve addresses.=0A=
Enables a IPv6 client to connect to an IPv4 server.=0A=
Eliminate a DNS ALG. sNAT-PT is bi-directional, v4 or v6 initiated. =
Synthetic addresses may have an IDENT bit in the advanced case to help =
identify the presence of a translator.=0A=
TFDP: Resolves some DNS LAG related issues. It synthesises A/AAAA/PTR =
and can created dynamic mappings (1:1) while being separated from the =
transport of the packet.=0A=
Recycle traditional NAT-PT for the translation, remove the DNS ALG and =
create a Translator Friendly DNS Proxy separate to the NAT device. =0A=
The translation engine is separated from the configuration. We don't =
recommend to use dynamic allocation for the anonymous service. =0A=
RFC 4966 issues with multicast translation: =0A=
=0A=
Dave: MLD joints flow to the sNAT-PT. How does it decide what M4 address =
is used for an M6 address. =0A=
: The sNAT-PT is statically configured with a M4:M6 mapping table=0A=
=0A=
ICMP error translation:=0A=
=0A=
Q:: How does this differ from what is in SIIT?=0A=
A:: This is a new [ICMP] code=0A=
=0A=
I think we should not support UDP w/o checksums. SIIT didn't, NAT-PT =
tried.=0A=
=0A=
Dan: All Cisco voice gateways send UDP packets without checksums=0A=
=0A=
Reassembly resolves the fragmented packet issue, but introduces its own =
issues. We can introduce this as optional behaviour=0A=
=0A=
Q:: The approach in NAT64 was to specify if you did reassemble, but you =
could implement it differently. Are you saying you want to go beyond =
that to say you must reassemble?=0A=
A:: Must reassemble at this moment, but I am wondering=0A=
C: As a spec, you could say you need this behaviour without a need to =
actually reassemble.=0A=
=0A=
I do not think Marcellos approach is bad, I just would like to present =
alternatives. =0A=
EDNS original resource record option (a new option). If RR was =
authorised and synthesised, the DNS proxy inserts the ORR option inside =
the RR. RR verification can be done in one message.=0A=
=0A=
Q:: Why are you thinking of doing this inside the option instead of =
using the additional info option=0A=
A:: I understood end-node verification is required. So we should give =
some info to indicate this is synthesised. =0A=
C:: But you could put it in the additional information response. Why put =
it in the option instead of the additional info section?=0A=
A:: No real reason=0A=
Andrew: All your doing is translating the A to the AAAA, but all the =
other records are passed through untouched?=0A=
A:: Yes=0A=
Andrew: So the validator sees this ORR option and then queries =
specifically for the A record? Im confused=0A=
Marcello: In order for this to work, we need to change the client. If =
you need to change the client, why not just synthesise records inside =
the client? =0A=
=0A=
Marcello: You saying that a bit in the address [IDENT] will indicate it =
is synthetic?=0A=
A:: Yes.=0A=
Dave: You can use a well-known prefix, or use the IDENT bit when you =
don't have a well known prefix. If its an arbitrary prefix, how do you =
know which bit is the IDENT bit? A dummy bit is 128-bits minus 32-bits. =
IDENT is a bit-number that is always the 33rd from the right. If i =
receive this address (DNS or otherwise) how do i know whether its =
synthetic or not. Couldn't this just be a MAC address that has that bit =
set?=0A=
=0A=
Q: Do you think that having a SIP ALG is required?=0A=
A: It depends on the policy of the network [operator]=0A=
Q: Is that SIP ALG for the purpose of setting up the media path?=0A=
A: Yes=0A=
Q: The SIP WG has decided that ICE is the recommended way to go, are you =
trying to say you don't think that is the right way to go?=0A=
A: [No, this is just a description of one implementation.]=0A=
Q: There may be some confusion in what a SIP ALG means at different =
times. I wouldn't go so far to say the SIP WG says to use ICE instead of =
SBC (a type of SIP ALG). SIP and other protocols are designed for =
certain types of intermediaries - if you put new intermediaries it in =
things will break. In SIP's case, back to back interconnections.=0A=
=0A=
TFDP assigns an IPv4 address dynamically. We face problems that some =
applications cache DNS record. Some applications are not compliant to =
[DNS] TTL. If the application caches responses and it doesn't expire TTL =
it is not friendly for dynamic address assignment. TTL was not designed =
for applications, it was designed for servers. Propose that any =
implementation should [use TTL to expire any DNS cached record].=0A=
=0A=
NAT6 Issues=0A=
-------=0A=
Cullen=0A=
=0A=
Issues that come up in all the drafts that do translation. =0A=
Lots of experience with v4-to-v4 ALG. The one that comes up all the time =
is FTP ALG. All major browsers and FTP clients support PASV mode. PASV =
solves 4-to-4, EPASV solves 6-to-6 but nothing solves 4-to-6. Need to do =
some more stuff on FTP.=0A=
Many people have made SIP ALG. They are a disaster and all have bugs, =
cant work with SIP TLS. SIP WG has moved to try and avoid them. Many SIP =
clients work fine through v4 NAT using a variety of techniques. RTSP is =
getting fixed too, and ALG may not be the right way there either - not =
sure. MGCP, unlikely to see it in these environments. =0A=
All the other ALG on v4-to-v4 devices seems non-relevant, H323 may be =
important - but it is a hard thing to decide on. Are there any other =
protocols that we need to look at ALG for? If we only need an FTP ALG we =
can go and do that.=0A=
Q: Why do we need an FTP ALG for 6to4.=0A=
For 4to4 all the major browsers use PASV command. EPASV does the same =
thing for 6to6. =0A=
Dave: Would EPASV work for 4to4?=0A=
A: Yes - EPASV has a protocol family field, so it could be used for 4to4.=0A=
X: HTTP ALG: if you find an IPv4 address embedded in a URL what will we =
do.=0A=
Cullen: Good example. I have a NAT that looks in HTTP and translates it =
[URL]. This breaks all kinds of stuff. The problem with this HTTP ALG, =
for example, consider a binary file transfer that may have the exact =
4bytes of my IP address in there and it gets it changed!! =0A=
=0A=
Client Port Control=0A=
Protocols that allow devices behind the NAT to request a port - a =
particular port. Issue is around authorisation. There are protocols like =
UPnP to push up to the NAT, NAT-PMP similar to UPnP to control the NAT =
directly. Is the virus you just downloaded allowed to open up as many =
ports as it wants. Also, multi-layer NAT is common today. This issue is =
not specific to IPv6 at all. =0A=
=0A=
Alain: What is important is the difference between requesting any port, =
vs. a specific port. For example, if you want a specific port you'll =
never be able to get it in any of these solution/scenario (1/2/3). Move =
this semantic to wanting to work on any port.=0A=
Marcello: There are some things that you could do different in IPv6. =
Authorisation for example. There is a draft that shows some ideas. In =
IPv6 you can actually prove address ownership.=0A=
Cullen: Okay. The problem is not how to have a secure connection between =
host and NAT (ie, using CGA). But the problem is which clients should be =
authorised and which hosts, or applications, should not. There are =
brilliant ideas on how to solve this, but they are orthogonal.=0A=
=0A=
Fragmentation=0A=
Goal: deal with the MTU differences between IPv4 and IPv6. How to we =
match the semantics of the DNF bit in IPv4 with options in IPv6. The =
ideal solution would not rely on ICMP, but ICMP would be an =
optimisation. Didn't force you to retransmit the first packet every =
time, and one that allows the application to be involved in this =
discovery process.=0A=
Options:=0A=
v6 end hosts include Frag Header in all packets larger than about 500 =
octets. Downside requires a change in host or applications - something =
we are trying to avoid.=0A=
host sends the first packet and NAT sends ICMP error telling host to =
insert frag error - and host resends. I'm unclear on how the API work =
between stack and application to allow an application to differentiate =
between this case and the case where you really want to be un-frag. When =
a packet is more than v4 MTU and less than v6 MTU - you also need =
retransmission.=0A=
Host sends the packet that may be too big and relies on getting an IPv4 =
ICMP error - the NAT could then send back the IPv6 frag error. This wont =
work if there is something that drops ICMP on the v4 network between the =
NAT and whatever devices needs the fragmentation. =0A=
=0A=
Marcello: If this specific to the solution, or just relating to how IPv6 =
fragmentation works?=0A=
Cullen: How v6 frag works, we guarantee we get 1280B and it usually =
works. =0A=
Suresh: I don't know what's going to happen with an IPv6 host when it =
sends a 1280B packet and gets a "too big". =0A=
Cullen: Me too - but the guess is that the right thing will happen. The =
implementers never expected this.=0A=
Fred: It's supposed to work.=0A=
Cullen: I know we need testing, but I don't think it should be a serious =
concern.=0A=
Dave: the RFC requires that subsequent packets come with a fragment =
header, but they can still be 1280B. =0A=
Dave: I think C and D are the same option, its just topological case =
differences. In C the min MTU is attached to the NAT, in D its beyond =
the NAT.=0A=
Suresh: These are options not only for the sending host, but also the =
NAT implementers. =0A=
Dave: No, the only time a NAT sends ICMP sends an error today if its =
IPv4 link has an MTU link to small for the packet. That is different to =
saying if it would not have to fragment.=0A=
Cullen: What I had meant by C is that the NAT had 1500B MTU on its =
uplink. Take the case where it opportunistically sent a frag error.=0A=
Dave: The disadvantage is that the first packet after the SYN is =
dropped. =0A=
Y: There are some more interesting options. I wonder if you can forward =
a packet anyway to allow fragmentation.=0A=
Cullen: I thought about when v6 says don't frag this packet, but then =
you allow it to be fragmented in the v4 world anyway =0A=
D: Are you assuming the NAT behaviour is more or less what SIIT says =
today?=0A=
Cullen: I went through all of that and there are some differences=0A=
=0A=
Out of order fragments=0A=
Truth about v4 NAT today: they deal with out of order packets with =
varying degrees of bugginess. out of order packets do happen so what do =
we do? Trying to deal with DoS and memory attacks on a NAT with 40G line =
cards, detect, buffer and reassemble is going to be very hard. Lots of =
people just block out of order fragments - so they only need to deal =
with keeping track. This will become a judgement and taste call - we =
break things if we do this. If we don't do this we have other issues. =
Any input?=0A=
=0A=
Q: I think we should do what behave says - behave says you should handle =
out of order packets. Whether the NAT actually reassembles, or just acts =
as if it reassembles is okay.=0A=
Cullen: Yeah ,sure - but the question is whether we have to save them.=0A=
Marcello: I asked this in v6ops - the answer is that you need a slot of =
time=0A=
Dave: I agree with Marcello, be it 3 seconds or of that order. With =
fragments things are usually back-to-back. IP does not guarantee lack of =
reordering - so I do not think we should just drop them.=0A=
=0A=
IPSec AH:=0A=
Some things just don't work. AH for example.=0A=
=0A=
=0A=
Dan=0A=
---=0A=
Proposal summary:=0A=
Im going to also show all of the proposals on one slide. I tried to map =
these to the scenarios as know this morning.  Mark is working on them.=0A=
Dave: Between the three tables we are not complete. An example case not =
covered: v6 internet on top right in slide 3, and v4 intranet on bottom =
left. Connectivity inbound.=0A=
Dan: I am not trying to capture scenarios.=0A=
X: From the discussion it seems obvious that the translation based =
solutions are all pretty similar. I don't think any of us have nailed it =
correctly. Somewhere is the best way. Lets take ideas from all the =
solutions (translation). We should try and merge the various translation =
proposals.=0A=
Randy: I agree. I believe I have (as an operator) 2 problems. Problems =
with the broadband provider, or the problems the broadband provider =
causes me. =0A=
Alain: In some of those cases where you have a v6 only server  - =
scenario 4. Its not that you cant have an address, its just an =
application that doesn't work in v6 yet. Another point this morning =
discussed intranets. In these examples , using IPv6 can be quite =
compelling. Finally, giving the control of the NAT back to the user is =
something we will try to achieve. What is happening for green-field (it =
is not clear)? What we need is a roadmap - SP are running out of v4 =
space, and we need something simple right now.=0A=
Marcello: My take is that we should take input and honour the input we =
receive.=0A=
Alain: When I hear about legacy IPv6 hosts - this is too hard to =
swallow. There is very little deployment of IPv6-only networks. Yes =
devices exist with v6 capability, but when we turn off v4.......=0A=
Jari: I think we need to understand the S-curve/adoption curve. We are =
not all in the same place.=0A=
Remi: I agree with Alain that there is a host with only v6 stack. We =
have to deal with dual stack hosts that have IPv6-only addresses without =
IPv4 addresses. To deal with these hosts we don't require NAT64.=0A=
Y: There is still software that is not good at running IPv6 on these =
devices. I don't think you can have only IPv6 networks.=0A=
Alain: You make a good point. We have been confusing three things: what =
the network provides (addresses), what does the stack do, and finally =
what does the app do. If all of those three things are IPv6 then you can =
do the protocol translation and it works. If one isn't IPv6, typically =
the app, there is a lot of interest in doing the tunnel + v4 NAt =
clearly. We must look at all the hosts. The requirement of v6-only and =
then choose the solution isn't good - we need to define the "v6-only" =
definition better.=0A=
Jari: we do have people explaining they have this issue and they want to =
do these things.=0A=
=0A=
Mark:=0A=
Scenario 1: NAT 44 stuff=0A=
Scenario 2: Service providers running out of IPv4 space. V4 over v6 =
encapsulations/tunnels. This is really still about delivering IPv4 to =
the user.=0A=
Scenario 3a: Wireless Greenfield. Its still about v4 in v6 =
encapsulations. Talking about a host setting up the tunnel instead of =
the gateway. Host to gateway tunnel.=0A=
Scenario 3-5: Translation Options. one big box that translates the whole =
IPv4 Internet into the whole of the IPv6 internet both ways. Such a box =
doesn't exist. =0A=
Scenario 3: My IPv6 Network translates to the IPv4 Internet. My =
IPv6-network initiated traffic.=0A=
Scenario 4: My IPv6 network is exposed to parts of the IPv4 internet. =
Initiate from IPv4 internet to My IPv6 Network=0A=
Scenario 5: I want to expose My IPv4 Network to the entire IPv6 =
Internet. Initiate from the IPv6 Internet=0A=
Scenario 6: I want to expose My IPv4 network to the entire IPv6 =
Internet, Initiate from My IPv4 Network=0A=
=0A=
Scenario 3: Greenfield. NAT64/DNS64. =0A=
=0A=
Scenario 5: Exposing some of my v6 Internet to the Internet. IVI, NAT-PT.=0A=
=0A=
Scenario 4: IPv6 Internet to my IPv4 Network. NAT64. 1:1 stateless=0A=
=0A=
Forget about the names and numbers!=0A=
=0A=
We cannot build a translator that can translate in both directions =
simultaneously. We must scope things. Shrink things down to the network =
I care about on one side, and translate to the remaining global network.=0A=
=0A=
Alain: This last scenario (My IPv4 to IPv6 Internet) is not solved. This =
scenario is actually an endgame scenario when the world has already gone =
v6, and services may only be on v6. I have not cared about v6 for a long =
time, but not apps are only on v6. =0A=
Mark: The argument for why this is already solved is because by the time =
IPv6 only traffic exists out here, then hosts within the IPv4 network =
will be dual-stack hosts.=0A=
Dave: I agree with Alain. This is not already solved. In the translation =
category there are four possible solutions. You're not talking about =
network devices in the "network" its the apps, hosts, etc. This scenario =
is not solved by Teredo because they are IPv4 networks. There hasn't =
been much demand for this so far, but this is a real, and unsolved, =
fourth case.=0A=
Christian: This may be an important scenario in the future so IPv6 =
deployments will be high, so there will be less incentive on the IPv6 =
side to solve this problem, and more on the IPv4 side. The other =
solution is deployed on the IPv6 side, and as a consequence they need =
global IPv4 addresses. At some point in the future they will not get =
global addresses. Thus, better to have something on the side of the IPv4 =
network we don't need additional IPv4 addresses, we need more IPv6 =
global addresses. The virtual IPv6 document I have been working on =
addresses this scenario. =0A=
Phillip: I object to the existence of a tunnel in Scenario 2. It may =
well be that the IETF recommends a tunnel-based solution, but I don't =
think it should be in the description.=0A=
Mark: This is not a description of the scenario. =0A=
Phillip: It seems you are declaring a tunnel based approach is the =
correct way to solve this problem. We need to discuss why we think =
tunnel-based is the correct way, and why we think back-to-back =
translation is bad.=0A=
Jari: My recommendation is that we explain which tools fit with what =
scenarios. I don't want to entertain theoretical things.=0A=
Phillip: We are going to build equipment in scenarios 3/4/5. This will =
solve scenario 2. Ie, say that it is a bad idea to do back-to-back NAT.=0A=
Marcello: Even though that is the case for scenario 2, I'm not sure I'm =
convinced the scenario in 3a is the solution. =0A=
Mark: It's a solution. It doesn't matter because people will do what =
they want to do.=0A=
Cullen: I think that these tunnelling ones come down to v4 floated over =
6 by the CPE or by the host.=0A=
Ed: I like the definition of the translation - big problem before little =
problems. In terms of prohibiting 464, why prohibit things between =
"consenting adults".=0A=
=0A=
=0A=
=0A=
Jari: Its mostly about the question of which scenarios you actually care =
about. If you care about scenarios with hosts still. =0A=
Mark: Scenario 3a represents a host that you can change.=0A=
Remi: This could be used in an ISP network, right?=0A=
Alain: I think that Remi has a point : you cannot have a clear cut =
scenario 1/2 prolonging v4, and 4/5/6 which translate. There is overlap. =
In scenario 3 you can address it either over tunnels or translation.=0A=
Mark: I agree=0A=
X: Mobiles may possibly have IPv4-only software=0A=
=0A=
I propose that the next version of this document classifies things as =
follows:=0A=
1) Topologically we have IPv4 Networks reaching the IPv4 Internet with =
no IPv6 involved in reaching the IPv6 internet. NAT 444 or SAM with PPP =
tunnels, etc. No IPv6 introduced.=0A=
2) You are introducing an IPv6 network to help solve your IPv4 =
continuation problem. Eg: 2a: RFC1918 address space exhaustion , 2b: I =
want to run my IPv6 because I don't want to run dual stack. Listing the =
business scenarios that fit within this topological heading of IPv4 over =
IPv6.=0A=
3, 4, 5, and 6: These are the translation options. Point being that a =
[god box] for NAT is impossible. Must always think of things in the =
context of My Network. =0A=
=0A=
Christian: It is sufficient for one of the components between the =
application and the other end can make you 6-only. There are 3 parts =
that may be v6 only, the app, the host, the network. =0A=
Dave: I agree with Christian. The router and the next router and stack =
and app are IPv6 only, no - that AND should be an OR. If you are trying =
to say : for things that make an interesting translations scenario, its =
the stack and the application. If your host can only support one [stack] =
then you cannot tunnel.=0A=
Ed: The situation where the network is v6 only is covered in scenarios =
1/2. Thus this comes down to application or hosts.=0A=
Alain: All of us have been talking about networks. This is really =
relevant to the Ip stack and applications. =0A=
Mark: you can still solve it with tunnels.=0A=
Dave: No, your application can only see v6, the other end can only do =
v4. The reason might be because the app was never written to support =
another family, or it could be because its running on a host that is v6 =
or v4 only. We would really like all apps to be version agnostic, but =
they may be on a IPv6 only host.=0A=
Peter: The issue is not equipment is dual stack v4/v6. At some point you =
just will not be able to get an IPv4 address.=0A=
Dave: legacy v4 to v6 internet - looking for concensus to not solve this =
problem, asking who cares about this?=0A=
Alain: argues that it may not be high priority, but that shouldn't stop =
anyone from working on it,=0A=
Fred: again - looking for clarification - claims US military and China =
both have this requirment Ed Jenkins: IPV4 to IPV6 will eventually be =
needed and will be a long lasting requirement because of the existence =
of equipment that can never be upgraded (DOD)=0A=
=0A=
Dave: how to decide how to prioritize, 1) what scenarios need to be =
solved today, 2) for what are people currently using NAT-PT . What =0A=
problems are being solved by NAT-PT.   If we don't fix these problems =0A=
people will never move off of NAT-PT.  =0A=
=0A=
Woj:  Scenario #3:  confiused by how this has been changed - are we =
trying to address an IPv4 endpoint,=0A=
Mark: Scenarios 1 and 2 both deal with keeping v4 alive - #1 has no v6,=0A=
#2 brings in ipv6 has an infrastructure but is still about v4.  Ok now =
we move into the land of translation  - that is between ipv4 only worlds =0A=
and ipv6 worlds.    Translation land has to do with introducing new =0A=
things that (4 scenarios that are combinations of V4 to V6) that can =
perform the translation. =0A=
Woj:  hmm scenario 3 - must it be tunneled over IPv6=0A=
Mark:  could use MPLS or something , but , well this is an ipv4 ipv6 =
group so....=0A=
Woj:  isn't this more like scenario #1?=0A=
Mark: repeated his translation story -=0A=
Woj:  Does Scenario #1 include dual stack ...=0A=
Mark: This is about NEW work .. feel free to dual stack if you like...=0A=
Woj: can be done with other tunnel techniques..=0A=
... : there are other solutions in this space,=0A=
=0A=
Dave Miles: confirm view that CGN is adding something new, Mark agrees:=0A=
Dave:  clarify - is their an assumption of using RFC1918 private IP =
space between CPE and CGN?=0A=
Mark:  issue is how to deal with overlapping private IP address space, =
could pop into #2 and don't have an with overlapping IPs=0A=
Dave:  argues tunneling not the only way to resolve the issue of =
overlapping rfc 1918 ip space, there are alternatives.  CGN application=0A=
- clarify that CGN can coexist with IPv6 - so is scenario #2 really a =
subset of scenario #3.=0A=
Mark:  it's an issue of why one uses IPv6. RFC1918 exhaustion with =
scenario #2 was written as a solution - could be written differently as =
a problem statement.=0A=
Mark: continues about how #2 and #3 are different - #2 is I want to =
deploy IPv6 in my SP network and run IPv4 over it - it happens to solve =
the RFC 1918 problem=0A=
Dave: mark and Dave agree on the restatement of the problem.=0A=
Alain: doesn't like Dave's class E example - maybe PPOE would be a =
better example of how to transit the V6 portion of the net.=0A=
=0A=
Dave: is there a NAT 444 written down anywhere?=0A=
Chair: no - there is a CGN document, but no 444 doc=0A=
Dave: I'll write a draft.=0A=
=0A=
Jabber request:  can we put number of hosts on the scenarios for =
clarification.=0A=
Mark: no - because everyone's network is different.=0A=
=0A=
Woj:  when do we see IPv4 ONLY talking to IPV6 only or vice versa -=0A=
Mark: answer scenarios 3,4,5,6..=0A=
=0A=
mark: Its not about apps, the doc is about wanting to deploy a _network_.=0A=
Jari: There is an additional constraint in corp networks where you cant =
actually touch the software. you are expected to run a normal [existing] =
OS.=0A=
Dave: You're right. We are talking about an IPv4 provisioned app, and an =
IPv6 provisioned app. There is a third, the stack is dual stack, host is =
dual stack, and the app is agnostic,  but he only gets one type of =
address. We are all talking about a v4 only provisioned app and a v6 =
only provisioned app talking to each other.=0A=
Mark: Concerned we are looking at this, that, etc. We are in the trap of =
listing out every combination that you can touch. That trap is providing =
less clarity than I had hoped for.=0A=
Dave: My point is that it is not theoretical that you have v4 =
applications or v4 only OS. It is reality. It is also not theoretical =
that networks consist of heterogenous devices where you have both v4 and =
v6. I am saying we can simplify the problem because they all come out to =
the same thing=0A=
Jari: We should ensure we can deploy these things in more cases than can =
be deployed today. Lets go through the scenarios and this or that, but =
we must give people tools so they can do this in more situations than we =
can do today. It's important that we motivate people to do IPv6.=0A=
Christian: We are simplifying. We are defining what it means for =
something to be IP version X only. It means either the application, or =
the host, or the network is IP version X only. My push back on the doc =
is that it should define that in the beginning and then it makes it =
easier to describe.=0A=
Ed: I agree too. The problem statement is the application that deals =
with only one address family. The solution space is richer with =
different solutions whether it is the application or the stack. There =
are always going to be different solutions. The solutions need to =
consider those different flavours where the restricted part of the pipe =
is.=0A=
Alain: I think that doing this  between this stack and the IP address on =
the machine is helpful because of the cases where we have overlapping =
technologies, and the cases where we have no choice.=0A=
Mark: Everyone is agreeing. At the same time we have to step back. I =
hear, its not about saying I need an IPv6 only network - its about =
saying I need and IPv6 application. The drivers have been "oh wait, i =
need an IPv6 network", "i want to run a single stack network", "I want =
one network". We speak in terms of networks networks networks. Its not =
about the network, its about the applications. We need app developers in =
the room. All the applications need to turn IPv6.=0A=
Dave: I don't think the wrong people are in the room. Im not a fan of =
saying you want an app-specific solution, that's every app doing =
something or ALG. That's the method of last resort. We would like =
something to be solved in an app independent fashion. We are broadening =
transition paths.=0A=
Remi: Some hosts want IPv6 or IPv4 connectivity. The reason may be the =
application, the software, the IP stack or the networking piece. We are =
in the right room for talking about IPv6 connectivity.=0A=
Mark: So there's the walk through the scenarios. THe first two are about =
v4. The last 4 are about IPv6. I wonder if we need to call out the =
network vs. the host/application is IPv6 only.=0A=
Jari: We aren't doing scenarios because its fun, but because its =
important and we need to know what to do next. We have already decided =
tunnelling will be done, we have already started one solution in soft =
wires, so we are already doing work in that. The real question is =
whether we are going to do work on translation.=0A=
Brian: We will go thorough the questions and try and gauge a sense of =
peoples acceptance.=0A=
=0A=
--=0A=
=0A=
Brian: Im going to ask two question before asking are you interested in =
the scenario.=0A=
1) Are people interested in working on or writing tunnelling or =
translation.=0A=
Jari: May I propose : Do you believe there is a clear cut case for =
either translation or tunnelling. Ie, there are situations where we have =
to do that.=0A=
Remi: There may be solutions that combine both.=0A=
Brian: 		1: tunnelling plus NAT [vast majority raised hand]=0A=
		2: translation [vast majority raised hand]=0A=
=0A=
Brian: Currently the results were a clear decisions for both tunnelling =
and translation.=0A=
Randy: What this came to after lunch was: there are two general =
spaces:1) my broadband friends are running many many pieces that need to =
tunnel , 2) translation is when there are large chunks to be moved=0A=
Jari: We will learn what modes/scenarios we are interested in. We will =
poll soon.=0A=
Brian: The first scenario, the CGN solution. Who is actually seeing =
these types of problems today?=0A=
Jari: We go through each. We ask whether the IETF should address =
(because you have that issues now or in the future).=0A=
Fred: Cisco is working actively on CGN.=0A=
Cullen: Speechless - I bet everyone in the room has one of those NATs, =
we have BEHAVE. What are we asking here?=0A=
Jari: A carrier grade one. We are talking about the new work that the =
IETF needs to do. It is not what new work, but new work in this space. =
We are asking whether there is a need to do CGN. Etc.=0A=
Alain: I do believe that this is something that is important, there is =
good work that is done in behave. I do not behave we should try and =
expand RFC 1918 into the SP space.=0A=
Jari: you can object to specific proposals later.=0A=
Mark: There are no IPv6 tunnels, there are CGN and gateways and there =
are different ways to do it.=0A=
Dave: The question you had asked is whether we think the IETF needs work =
in this area. Then you asked whether you would contribute (to docs). =
Third, are people using or selling NAT-PT for this particular scenario.=0A=
Jari: I just want to ask one question. =0A=
Randy: This is the fourth time we have done on scenarios, when she keeps =
asking the same question again and again, I'm giving the wrong answer. =
Must ask, what answer do you want.=0A=
Shin: If we cannot change CPE we have to look at NAT444. And the =
existing v4-only devices. We have to do it. I'm not saying IPv6 is not =
needed - IPv6 is needed. CGN has lots of limitations. There are many =
limitations, ports, sessions, UPnP. Please think about that. We have to =
do this.=0A=
Remi: Does it include the case where the CGN does no NAT?=0A=
Mark: Yes, anything that has to do with IPv4 to IPv4 without =
tunnelling/encapsulation.=0A=
=0A=
Who thinks the IETF should define scenario 1: 18 or so hands. Who thinks =
we should not: 0 hands. =0A=
=0A=
Scenario 2: Who things the IETF should solve cycles solving scenario 2: =
29 for. Against: 0=0A=
=0A=
Scenario 3: My IPv6 network to the IPv4 Internet: For: 28. Against: 1=0A=
=0A=
Scenario 4: IPv6 Internet to Your IPv4 network: For:  27 Against: 2=0A=
=0A=
Scenario 5: IPv4 Internet to my IPv6 Network: For: 20. Against: 3. =0A=
=0A=
Scenario 6: My IPv4 network to IPv6 Internet. For: 20 Against: 2=0A=
=0A=
Table:=0A=
=0A=
Scenario		For		Against=0A=
--------------+----------------+-----------------=0A=
One			18		0=0A=
Two			29		0=0A=
Three			28		1=0A=
Four			27		2=0A=
Five			20		3=0A=
Six			20		2=0A=
=0A=
=0A=
=0A=
Phillip: There are a number of working groups, BEHAVE, Softwires, v6ops, =
DNSops. I'm worried because now it will be split across four working =
groups. I don't know if this is the right solution, but do we at least =
want one mailing list to talk about this issue? I am worried the people =
that are focused on tunnels will not be able to provide translations and =
vice versa. This stuff could all get lost.=0A=
Jari: We hear you. The trade offs are putting people in the same place - =
but do we have enough experts in that one place. If we put everything in =
a new working group can we get the right persons involved. I am not sure =
there is a perfect solution. Maybe with scenario 1 we could bring a =
bigger set of people into one room, including legacy v4 guys.=0A=
Phillip: Maybe we should think about keeping the v4v6interim mailing =
list alive and going. =0A=
Jari: How about we keep it alive until Minneapolis. Hopefully by =
Minneapolis we will have a way for BEHAVE to execute.=0A=
Remi: I just want to say that I don't share the concern that those =
working on tunnelled solutions would miss something related to a =
translated solution. I think there can be a clear-cut separation.=0A=
Phillip: We could bring the tunnelling stuff back into BEHAVE. It does =
in make some sense.=0A=
Mark: If you look at some of the solutions that Softwires have done, =
like mesh, that you might not end up having those that build big routers =
going to BEHAVE, and therefore may not appreciate some of the things =
that go with routing. In Softwires we have people that know about big =
routers and IPv6.=0A=
Phillip: Should BEHAVE look at NATs, and Softwire just look at how to =
plug that into the tunnelling solution?=0A=
Mark: Whenever you start carving up port spaces this way, that way, the =
other way, that is when you need BEHAVE experts. When talking about =
tunnels you need Softwires.=0A=
Jari: Time to close the meeting. We reach the conclusion that we do need =
both the solutions. I am kind of surprised, perhaps I saw we had only =
two solutions [translation and tunnelling]. Thank you all.=0A=
Dan: Today was my 40th Birthday, and I enjoyed spending it with you.=0A=
=0A=
---- Meeting Closed ----
------=_NextPart_001_004A_01C92528.90A93E60--

------=_NextPart_000_0049_01C92528.90A6F470
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPYzCCBDIw
ggMaoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0IxGzAZBgNVBAgMEkdyZWF0
ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwRQ29tb2RvIENBIExpbWl0
ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0wNDAxMDEwMDAwMDBaFw0y
ODEyMzEyMzU5NTlaMHsxCzAJBgNVBAYTAkdCMRswGQYDVQQIDBJHcmVhdGVyIE1hbmNoZXN0ZXIx
EDAOBgNVBAcMB1NhbGZvcmQxGjAYBgNVBAoMEUNvbW9kbyBDQSBMaW1pdGVkMSEwHwYDVQQDDBhB
QUEgQ2VydGlmaWNhdGUgU2VydmljZXMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+
QJ30buHqdoccTUVEjr5GyIMGncEq/hgfjuQC+vOrXVCKFjELmgbQxXAizUktVGPMtm5oRgtT6stM
JMC8ck7q8RWu9FSaEgrDerIzYOLaiVXzIljz3tzP74OGooyUT59o8piQRoQnx3a/48w1LIteB2Rl
gsBIsKiR+WGfdiBQqJHHZrXreGIDVvCKGhPqMaMeoJn9OPb2JzJYbwf1a7j7FCuvt6rM1mNfc4za
BZmoOKjLF3g2UazpnvR4Oo3PD9lC4pgMqy+fDgHe75+ZSfEt36x0TRuYtUfF5SnR+ZAYx2KcvoPH
Jns+iiXHwN2d5jVoECCdj9je0sOEnA1e6C/JAgMBAAGjgcAwgb0wHQYDVR0OBBYEFKARCiM+lvEH
7OKvKe+CpX/QMKS0MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MHsGA1UdHwR0MHIw
OKA2oDSGMmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0FBQUNlcnRpZmljYXRlU2VydmljZXMuY3Js
MDagNKAyhjBodHRwOi8vY3JsLmNvbW9kby5uZXQvQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmww
DQYJKoZIhvcNAQEFBQADggEBAAhW/ALwm+j/pPrWe8ZEgM5PxMX2AFjMpra8FEloBHbo5u5d7AIP
YNaNUBhPJk4B4+awpe6/vHRUQb/9/BK4x09a9IlgBX9gtwVK8/bxwr/EuXSGti19a8zS80bdL8bg
asPDNAMsfZbdWsIOpwqZwQWLqwwv81w6z2w3VQmH3lNAbFjv/LarZW4E9hvcPOBaFcae2fFZSDAh
ZQNs7Okhc+ybA6HgN62gFRiP+roCzqcsqRATLNTlCCarIpdg+JBedNSimlO98qlo4KJuwtdssaMP
nr/raOdW8q7y4ys4OgmBtWuF174t7T8at7Jj4vViLILUagBBUPE5g5+V6TaWmG4wggTdMIIDxaAD
AgECAhBxkvvmGV+sTRKFdHE0ohinMA0GCSqGSIb3DQEBBQUAMHsxCzAJBgNVBAYTAkdCMRswGQYD
VQQIDBJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcMB1NhbGZvcmQxGjAYBgNVBAoMEUNvbW9k
byBDQSBMaW1pdGVkMSEwHwYDVQQDDBhBQUEgQ2VydGlmaWNhdGUgU2VydmljZXMwHhcNMDQwMTAx
MDAwMDAwWhcNMjgxMjMxMjM1OTU5WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYD
VQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYD
VQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xp
ZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjMapjVTTUZuaRC5c5J4oovHnzSMQfHTrSD
ZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKTzMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1le
pS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZGzaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGo
Lhu21DEgLLyCio6kDqXXiUP8FlqvHXHXEVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0
YqoYymiTHqGFfvVHZcv4TVcodNI0/zC27vZiMBSMLOsCAwEAAaOCAScwggEjMB8GA1UdIwQYMBaA
FKARCiM+lvEH7OKvKe+CpX/QMKS0MB0GA1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNV
HQ8BAf8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH
AwQwEQYDVR0gBAowCDAGBgRVHSAAMHsGA1UdHwR0MHIwOKA2oDSGMmh0dHA6Ly9jcmwuY29tb2Rv
Y2EuY29tL0FBQUNlcnRpZmljYXRlU2VydmljZXMuY3JsMDagNKAyhjBodHRwOi8vY3JsLmNvbW9k
by5uZXQvQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwEQYJYIZIAYb4QgEBBAQDAgEGMA0GCSqG
SIb3DQEBBQUAA4IBAQCdlcs8uH6lCcQevwvCx3aOOTyUxhCqTwzJ4KuEXYlU4GU7820cfDcsJVRf
liH8N4SRnRXcFE+Bz1Qda2xFYMct+ZdRTPlmyjyggoymyPDi6dRK+ew/VsnddozDggFPbADzHhph
dARHA6nGQFeRvGUixSdnT1fbZFrZjR+6hi/0Bq6cae3p9M8pF9jgSp8aIC+XTFG7RgfEijdOIOMJ
MWjHnsSLneh+EbwyaBCWEZhE2CpRYE2I63Q630MGMsg5Vow6EVLTQaRDA/Tt7zMn2zngFE4mydj1
OeKJuJNdtykmQeqzm66D/Hd1yujKtf7iZUpjPkTE0MNeh3OpmByvfxV/MIIGSDCCBTCgAwIBAgIR
APTJFkzZLMQ+Cbtz+ZLzUM4wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVTMQswCQYDVQQI
EwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0
d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNF
UkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwNzE3MDAwMDAwWhcN
MDkwNzE3MjM1OTU5WjCB6DE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsgLSBQRVJTT05B
IE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9mIHVzZTogaHR0
cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMgQ29tb2RvIExp
bWl0ZWQxFDASBgNVBAMTC0RhdmlkIE1pbGVzMTAwLgYJKoZIhvcNAQkBFiFkYXZpZC5taWxlc0Bh
bGNhdGVsLWx1Y2VudC5jb20uYXUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCuK4tO
9IBOqTTkqqoprcZgsT+OnZwmBmOeiJXve3P7FSAgH3TbfbjRKeWH3hb0r7LJlZyyTDfbkb8du97o
ZPpfQfKKwACiyn4Z4wgqtIEtTP5OSrw5vQ1MqZHiHrM+SqVTWVPmL4mMNLykhzDo+w8waoKnmffT
427R0dx6/EQgfCE8/L0DN/P4/HMd/Gkzsq7sJ4T1dQ71/mo/vqXzZDLMxr3J5Hev18wN3MiFrzM5
Co+rrJYN47lvyfPDjglI2AHL7dYg1vIuWWn0fQ3lHbhjsc1k8CU1DGimLiNu+jUPyZJje4FAlOQu
nlZzcKPOUtAuZzul1qLMEUXTTVeidrdlAgMBAAGjggIjMIICHzAfBgNVHSMEGDAWgBSJgmd9xJ0m
cABLtFBIfN49rgRufTAdBgNVHQ4EFgQUfHJHHlEhtAYgSFN0BJ3HxOT13p0wDgYDVR0PAQH/BAQD
AgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCG
SAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1o
dHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzCBpQYDVR0fBIGdMIGaMEygSqBIhkZodHRwOi8v
Y3JsLmNvbW9kb2NhLmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1h
aWwuY3JsMEqgSKBGhkRodHRwOi8vY3JsLmNvbW9kby5uZXQvVVROLVVTRVJGaXJzdC1DbGllbnRB
dXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDBsBggrBgEFBQcBAQRgMF4wNgYIKwYBBQUHMAKGKmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL1VUTkFBQUNsaWVudENBLmNydDAkBggrBgEFBQcwAYYYaHR0
cDovL29jc3AuY29tb2RvY2EuY29tMCwGA1UdEQQlMCOBIWRhdmlkLm1pbGVzQGFsY2F0ZWwtbHVj
ZW50LmNvbS5hdTANBgkqhkiG9w0BAQUFAAOCAQEARtucjWywS3VXfHL9Lguh+jBmAzLXH5dYaI2a
mKr82Ec2dxdFMgdPBsZR6AWLfaEjDmC4JH8OxXMh/+cY9AFLXC8RAvOz647pkMc4ayY3KmmA/9wq
z1wI89lnskd0L3qJJCMXgTtFcI6QwWvuslrvZODYyuECnvBoXJLn4HMfuZdkiynZ/jqmuukCIchz
iW9wXAI2sSu4jjJ2gkVpH1Ei8AXAy7i8o5eXn70NP1OvxHNJf1C9W5Ro53Q2Wbcd/2W3GXpfM9fl
rwgwJLuBhMn+UMibvbaQrgd0cvYErGHV5ptHgvQOFau75cRa6/ARjvhWJ5w+vKuK+Z04PS87Bu5o
zzGCBGgwggRkAgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNh
bHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0
dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0
aGVudGljYXRpb24gYW5kIEVtYWlsAhEA9MkWTNksxD4Ju3P5kvNQzjAJBgUrDgMCGgUAoIICeDAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMDIyMTIwNTFaMCMG
CSqGSIb3DQEJBDEWBBTCbju4btdGXrmPxU8YU8iQG7ZPMDBnBgkqhkiG9w0BCQ8xWjBYMAoGCCqG
SIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0D
AgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEA9MkW
TNksxD4Ju3P5kvNQzjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQD0yRZM2SzEPgm7c/mS
81DOMA0GCSqGSIb3DQEBAQUABIIBAGC8E3VgsxlOu4CsJP7PtEoRWbiD3R65i+heVquV25Tq1F+c
ZUtALvc5f/wHAzbPL1x9OX7vYDXudpZ10fZmE4zdUgP2gOmU2azD4pggjS/CF5wW6Tgjyt+IxY1a
/u83lrv//dGiIOV7giktAiP2TdHvYWkXLfqPu3lxaLs3zvsjCmsP7tQ5+EwfBYU0gfJ3x0ysFI82
iR8Q9S+cc96Ylx4mM7NualdJf+yYnT/86olM5G4NvNnCYUjpbjqcI2z3nbvDv0Heoqrv0q2GvJ1R
/IrrgBRxOpWkgwQurbGzwb0PAytQfmpY+NgvTkj979QWkOUsWyC91kJeOr6/KfHoerIAAAAAAAA=

------=_NextPart_000_0049_01C92528.90A6F470--

--===============0376426952==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--===============0376426952==--


From v4v6interim-bounces@ietf.org  Thu Oct  2 15:20:13 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 596603A69A1;
	Thu,  2 Oct 2008 15:20:13 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E9143A6913
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 15:20:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dyBFo5Ui1NbR for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 15:20:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 889FD3A69A1
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 15:20:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,353,1220227200"; d="scan'208";a="167684890"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 02 Oct 2008 22:20:25 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m92MKPJC032467
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 15:20:25 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m92MKLfc010801
	for <v4v6interim@ietf.org>; Thu, 2 Oct 2008 22:20:25 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 18:20:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 18:19:27 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: Ackk0+PAWr0LzmLETv+Lq0ixo5v6IgACM+Ig
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>, <v4v6interim@ietf.org>
X-OriginalArrivalTime: 02 Oct 2008 22:20:23.0681 (UTC)
	FILETIME=[104FD710:01C924DD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1123; t=1222986025;
	x=1223850025; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20RE=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20; bh=929pi3s4TX0jwcQvmL/nJACgsI7BVDXyd+zCsyc+Ryg=;
	b=I18WXwhFvuTsM6y53ED1VCnohyDckWj183sHSEHuqWOb3dWHEkzMJ/9X2G
	ziS/BGt3NMFRZKcfnbSl/FMOCM2C3qXtj6u0SYJSYLSJxEX1Y8a8kQ7ozlIq
	UNzMqNmCKs;
Authentication-Results: sj-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred,

Good suggestion.  However, what if a BOF is needed to discuss a solution
where both xlat and tunnel are needed?  Do we discuss those in this WG
mailer or spawn a 3rd new BOF mailer?

Thanks.

Hemant 

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Fred Baker (fred)
Sent: Thursday, October 02, 2008 5:14 PM
To: v4v6interim@ietf.org
Subject: [v4v6interim] BOF discussions

So various folks are going to be doing a lot of work in email and such
in the next few weeks. May I suggest that the ADs schedule a BOF for the
translation solution and one for the tunneling solution (and one for the
4-4-4 solution?) separate from WGs, to enable the doc authors to sit
down together and discuss?

I would also suggest that you set of mailing lists for these BOFs,
perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them to
this forum and let people sign up the usual way.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 17:41:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E130B3A6A59;
	Thu,  2 Oct 2008 17:41:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A3AA3A6A59
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 17:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lsayGo9DNTJH for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 17:41:01 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168])
	by core3.amsl.com (Postfix) with ESMTP id E735B3A69D3
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 17:41:00 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1423121wfd.31
	for <v4v6interim@ietf.org>; Thu, 02 Oct 2008 17:41:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=u7wNSHtjayyA2GV4iDQKwNEHlbVLHq4X/K1INC6VfWQ=;
	b=ctr6ymUoWEwAPLemqFoDb+gs3yWarC4f+AUW9f7061H/4sO/IOZ73OpOjLbCLQgsYn
	6s8GePnFs03+cl8kZU9EwIwdMLiu45LlpX+hXOQ7xKv5RmxVzTyH9IltsmgOC/iaePsD
	SpYv7uD1CDQ+dcNJVTa5OE6P5jSDUBEqmTpVk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=aZ8NLS7aJ13XrEbZ5iWFru2dQnApYGPHgv+uMay7DzRKZXCZORjfR/hyB9RQAvzpv3
	42ebpBQmcpFj8NxKVrxHBA/QzeW4m/6DohzpTULif6hxt0zncFSkqJZCnLNKArKMBZUh
	afQ0GoFOo7UcfzijC7tiLXoKqdO03AaQUwMzg=
Received: by 10.142.140.14 with SMTP id n14mr102700wfd.247.1222994488185;
	Thu, 02 Oct 2008 17:41:28 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 24sm3390435wff.17.2008.10.02.17.41.26
	(version=SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 17:41:27 -0700 (PDT)
Message-ID: <48E56A34.5060207@gmail.com>
Date: Fri, 03 Oct 2008 13:41:24 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alain Durand <alain_durand@cable.comcast.com>
References: <C50A477E.1B4C4%alain_durand@cable.comcast.com>
In-Reply-To: <C50A477E.1B4C4%alain_durand@cable.comcast.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Single namespace
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-03 02:40, Alain Durand wrote:
> 
> 
> On 10/1/08 5:20 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com> wrote:
> 
>> Although DNS64 is even more offensive to the computer science
>> view, I can't see any realistic solution to the v4only/v6 only
>> interworking problem that doesn't *require* different views
>> of the namespace on the two sides, created dynamically to
>> match the translation state.
> 
> In the case of v6->v4, there is actually a solution that *does*not*require*
> creating different views of the namespace. The v6 host can use its IPv4
> stack with Dual-stack lite, and the problem goes away entirely.

Agreed. But if you have a true v6-only scenario in the host, that doesn't
work. I agree with those who've said we'd better document this
issue rather than pretending it isn't real.

    Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 18:14:29 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B296F3A6A7E;
	Thu,  2 Oct 2008 18:14:29 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DEE03A6A7E
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 18:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kPg+8g1yO3RE for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 18:14:27 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181])
	by core3.amsl.com (Postfix) with ESMTP id 666783A68E3
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 18:14:27 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so719165wag.5
	for <v4v6interim@ietf.org>; Thu, 02 Oct 2008 18:14:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=dgeP3lt2n3PXHo86hYwo/pJoI0d29LP9/4Xa1ETQAaQ=;
	b=N2Rx2jp9uu15nl1guGteUZI3xq5xOGDPS3yhcHlvGupbuJ+K7bQK6F45IlhG9FasVQ
	1NplbXsPnNKfMLeVaHyfZxThqRh3TMaETArKLCUef4XOdNGqTvjkJq3oBFvV5KoHZksL
	6TDCfnaOJeoVYvyDbH8o10kloJiULo1GjWYeg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=C726KoGxqvKV7PjP5EhPJiuremV9jB3Zipa5WqXpXMjm+EgzI4FbQAOwQCQs7XL+MT
	D4xcrmcDBo85EkvcDeh394PKnu0NMGiZ9xR8ENMKxSy5bHxzxrTTn1w7u74KgBySjsl7
	7aLtAzX5lgpcl3Dmj1Sz1HuEMQtuvYXw09wDg=
Received: by 10.114.196.1 with SMTP id t1mr454655waf.80.1222996490123;
	Thu, 02 Oct 2008 18:14:50 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id v39sm8363761wah.40.2008.10.02.18.14.48
	(version=SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 18:14:49 -0700 (PDT)
Message-ID: <48E57206.6060302@gmail.com>
Date: Fri, 03 Oct 2008 14:14:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Arifumi Matsumoto <arifumi@nttv6.net>
References: <E5B66B80-F4B1-49EF-BBDB-5FD3C5D1F1B3@muada.com>	<3ADB39D4-022B-4965-9972-C242524C287E@cisco.com>	<9C02F1B4-FF51-4AAC-BBDA-59B15787D2BB@muada.com>
	<9F3FB3C0-6776-4F0E-9372-BC190A74755B@nttv6.net>
In-Reply-To: <9F3FB3C0-6776-4F0E-9372-BC190A74755B@nttv6.net>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] The NAT64 prefix
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-03 01:13, Arifumi Matsumoto wrote:
>>>
>> I don't see how you get from what I said to what you said...
>>
>> But now that you bring it up: the reason to make sure fake AAAA
>> records aren't generated when real AAAA records exist is that we don't
>> want to have the situation where a host uses translated connectivity
>> if there's also native connectivity.
>>
>> However, if the address selection rules work well enough it MAY be
>> useful to present both a native address and an address that will go
>> through a translator to the application so that if the native address
>> doesn't work the app can try the translated address. However, we know
>> there are hosts out there today that don't implement RFC 3484 fully
>> (at all?) (i.e., Macs) so generating fake AAAA records where real ones
>> exist in a DNS64 (-like) box is a very bad idea.
> 
> I agree with you most of the parts, but let me comment on this point.
> 
> Regardless of the existence of RFC 3484 non-compatible hosts, replying a
> synthesis AAAA with a genuine AAAA should be an operator's choice ? As
> far as there is some benefit, such as fault-tolerance, to have these two
> AAAA records, and we don't have strong motivation to prohibit it
> universally, it's better to leave this decision up to an operator of the
> site or the translator box.

There's also the rather strange case where the genuine AAAA record leads
to a routing black hole, and the synthetic AAAA leads to a working
translator. Although that should not happen, it *will* happen during
the early years of IPv6 deployment.

    Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  2 18:39:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C5713A6AF0;
	Thu,  2 Oct 2008 18:39:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB2CC3A6AF0
	for <v4v6interim@core3.amsl.com>; Thu,  2 Oct 2008 18:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qpBYpSICuQmf for <v4v6interim@core3.amsl.com>;
	Thu,  2 Oct 2008 18:39:12 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by core3.amsl.com (Postfix) with ESMTP id 0958E3A6827
	for <v4v6interim@ietf.org>; Thu,  2 Oct 2008 18:39:12 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so723143wag.5
	for <v4v6interim@ietf.org>; Thu, 02 Oct 2008 18:39:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=b3dhK91M63GXiqTEZnNhwEgIerFLpms19D4Ub21KfBk=;
	b=KnF9Qp+yNeDaL2P1CSHe28txB+CYyO8nsMszqOwA6M3VAk0gsikwBltwaylKllQV8j
	dPy/HTFt3v6Jjn6JSfeyyYO+BTt9E/lVq4jdPXbIfOnrb0pneSSTQp8nQ5+Sp2efVTRg
	iVGGKe6zH2qlNhHQYO9Zv1QoC2jsRDEPYNrYc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=QJniq2GU39GW/5OfPaaVHRMyf/KNTPJxxGc3WYrj8DGitHB09h8lMyhajYPv/4GGaf
	o2f3/ZyPtjK+XeRKjClVCMH8LQm2Lc3JJ0CZxPwDzJ/C8bt0LMQrnzlg5Vw9rWV1CprP
	M/rvgYxvHNxx8jkTyBlWjBY7mqsCuKMXnNMak=
Received: by 10.115.49.11 with SMTP id b11mr454127wak.117.1222997957093;
	Thu, 02 Oct 2008 18:39:17 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l37sm8453458waf.23.2008.10.02.18.39.15
	(version=SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 18:39:16 -0700 (PDT)
Message-ID: <48E577C1.8000006@gmail.com>
Date: Fri, 03 Oct 2008 14:39:13 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
	<3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
In-Reply-To: <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-03 06:51, james woodyatt wrote:
> On Oct 2, 2008, at 10:31, Fred Baker wrote:
>>
>> Sitting in your discussion of applications that may have issues
>> through a translator. In the chat room, I asked:
>>
>>> Dumb question from personal ignorance. SMTP opens with a HELO or EHLO
>>> that has the IP address of the MTA in it. Does SMTP treat that as a
>>> character string, or does it interpret the address? If it interprets
>>> the address, it may have the same issue as FTP in a 6to4 environment
>>
>> and James Woodyatt replied
>>
>>> Some things interpret it as an address, e.g. rule processing engines
>>> for deciding whether to require TLS. Or authentication.
> 
> The EHLO message has a domain name.  In SMTP, the Domain grammar
> production includes a special case allowing for an IP address literal
> instead of a FQDN.  This domain name in the EHLO message is sometimes
> used to make decisions about TLS and AUTH requirements.  So, too, can
> the IP address of the connecting client be used for such decisions.
> 
> Whether an ALG is required to cope with this is a question I'm not
> prepared to answer.
> 
>> That either calls for an ALG or appropriate code in the servers that
>> can deal with an <> address even when the server doesn't have such an
>> address. The simplest resolution might be to have the MTA have a leg
>> in the IPv6 world and one in the IPv4 world.
> 
> I would agree that this is the simplest way to handle SMTP servers.
> 

Yes. Incidentally, SMTP is listed in RFC 3027 among the "Protocols that
can work with the aid of an ALG", but the discussion seems rather
brief to me.

    Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 02:33:45 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12F293A6B57;
	Fri,  3 Oct 2008 02:33:45 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2E643A6B3D
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 02:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SBw7LPy2UJzv for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 02:33:42 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id B820828C265
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 02:32:04 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m939VFKp003116
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 18:31:15 +0900 (JST)
	(envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m939V5kB036521
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 18:31:06 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Fri, 3 Oct 2008 18:31:04 +0900
X-Mailer: Apple Mail (2.928.1)
Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Jennings,


FYI.
Though it is already clearly explained by Dave, let me give you the
pointer.
The answer for your question of "Fragmentation options" is clearly
stated in RFC2765(SIIT) as end-to-end path MTU discovery.
See Section 3 and 4.

And of course RFC1981(PMTUD) is compliant with it. ;-)
Chap. 4
       Note: A node may receive a Packet Too Big message reporting a
       next-hop MTU that is less than the IPv6 minimum link MTU.  In  
that
       case, the node is not required to reduce the size of subsequent
       packets sent on the path to less than the IPv6 minimun link MTU,
       but rather must include a Fragment header in those packets [IPv6-
       SPEC].

It must work well. ;-)

Regards,

....miyata
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 06:12:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A13128C0DC;
	Fri,  3 Oct 2008 06:12:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F08913A69A6
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 06:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.717
X-Spam-Level: 
X-Spam-Status: No, score=-1.717 tagged_above=-999 required=5 tests=[AWL=0.232, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JzBUUqWEWugY for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 06:12:25 -0700 (PDT)
Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28])
	by core3.amsl.com (Postfix) with ESMTP id D2F4728C0E5
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 06:12:24 -0700 (PDT)
Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp2-g19.free.fr (Postfix) with ESMTP id B2F4212B74F;
	Fri,  3 Oct 2008 15:12:52 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 399A612B74E;
	Fri,  3 Oct 2008 15:12:50 +0200 (CEST)
Message-ID: <48E61A05.20406@free.fr>
Date: Fri, 03 Oct 2008 15:11:33 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I support Fred's suggestion of separating discussion spaces for what is 
specific to tunneling and what is specific to translation.

In my understanding:
- NAT64, NAT46, and what concerns ISP infrastructure NATs (CGNs) but not 
CPE NATs, would be in v4v6-xlat
- A+P, IVI, SAM, and tunneling aspects of DS lite  would be in v4v6-Xlat
- questions that concern interactions between the two, would remain in 
the current mailing list.

RD

Hemant Singh (shemant)   (m/j/a) 10/3/08 12:19 AM:
> Fred,
> 
> Good suggestion.  However, what if a BOF is needed to discuss a solution
> where both xlat and tunnel are needed?  Do we discuss those in this WG
> mailer or spawn a 3rd new BOF mailer?
> 
> Thanks.
> 
> Hemant 
> 
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
> On Behalf Of Fred Baker (fred)
> Sent: Thursday, October 02, 2008 5:14 PM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] BOF discussions
> 
> So various folks are going to be doing a lot of work in email and such
> in the next few weeks. May I suggest that the ADs schedule a BOF for the
> translation solution and one for the tunneling solution (and one for the
> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit
> down together and discuss?
> 
> I would also suggest that you set of mailing lists for these BOFs,
> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them to
> this forum and let people sign up the usual way.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
> 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 06:15:25 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A01293A688C;
	Fri,  3 Oct 2008 06:15:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69D1F3A67C1
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 06:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dYuzTl-IF7rT for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 06:15:23 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 5648B3A688C
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 06:15:12 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id C7EBF29E150E; Fri,  3 Oct 2008 09:15:12 -0400 (EDT)
Received: from Macintosh-7.local (unknown [24.201.245.131])
	by jazz.viagenie.ca (Postfix) with ESMTP id 9498529E14FA;
	Fri,  3 Oct 2008 09:15:12 -0400 (EDT)
Message-ID: <48E61AE0.7080200@viagenie.ca>
Date: Fri, 03 Oct 2008 09:15:12 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
	<48E61A05.20406@free.fr>
In-Reply-To: <48E61A05.20406@free.fr>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

R=E9mi Despr=E9s a =E9crit :
> I support Fred's suggestion of separating discussion spaces for what is
> specific to tunneling and what is specific to translation.
> =

> In my understanding:
> - NAT64, NAT46, and what concerns ISP infrastructure NATs (CGNs) but not
> CPE NATs, would be in v4v6-xlat
> - A+P, IVI, SAM, and tunneling aspects of DS lite  would be in v4v6-Xlat

s/v4v6-xlat/v4v6-tunnel/  right?

Marc.


> - questions that concern interactions between the two, would remain in
> the current mailing list.
> =

> RD
> =

> Hemant Singh (shemant)   (m/j/a) 10/3/08 12:19 AM:
>> Fred,
>>
>> Good suggestion.  However, what if a BOF is needed to discuss a solution
>> where both xlat and tunnel are needed?  Do we discuss those in this WG
>> mailer or spawn a 3rd new BOF mailer?
>>
>> Thanks.
>>
>> Hemant
>> -----Original Message-----
>> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
>> On Behalf Of Fred Baker (fred)
>> Sent: Thursday, October 02, 2008 5:14 PM
>> To: v4v6interim@ietf.org
>> Subject: [v4v6interim] BOF discussions
>>
>> So various folks are going to be doing a lot of work in email and such
>> in the next few weeks. May I suggest that the ADs schedule a BOF for the
>> translation solution and one for the tunneling solution (and one for the
>> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit
>> down together and discuss?
>>
>> I would also suggest that you set of mailing lists for these BOFs,
>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them to
>> this forum and let people sign up the usual way.
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
>>
> =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim


-- =

=3D=3D=3D=3D=3D=3D=3D=3D=3D
IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
Stun/Turn server: http://numb.viagenie.ca

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 07:00:51 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A7393A69A6;
	Fri,  3 Oct 2008 07:00:51 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 362303A69A6
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 07:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id q2Bbo1e40eyF for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 07:00:49 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id EF5D23A67B4
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:00:48 -0700 (PDT)
Received: from zrtphxm1.corp.nortel.com (zrtphxm1.corp.nortel.com
	[47.140.202.50])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m93E1D503692; Fri, 3 Oct 2008 14:01:14 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:00:56 -0400
Message-ID: <4B7DAC3FEFD35D4A96BDD011699050141B4D2997@zrtphxm1.corp.nortel.com>
In-Reply-To: <48E61AE0.7080200@viagenie.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: AcklWjENUqewc8c9SIGpB/DJ/24YYAABh0kg
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
	<48E61A05.20406@free.fr> <48E61AE0.7080200@viagenie.ca>
From: "Ed Koehler Jr" <ekoehler@nortel.com>
To: "Marc Blanchet" <marc.blanchet@viagenie.ca>,
	=?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

agree =


-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org] On=
 Behalf Of Marc Blanchet
Sent: Friday, October 03, 2008 9:15 AM
To: R=E9mi Despr=E9s
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions

R=E9mi Despr=E9s a =E9crit :
> I support Fred's suggestion of separating discussion spaces for what =

> is specific to tunneling and what is specific to translation.
> =

> In my understanding:
> - NAT64, NAT46, and what concerns ISP infrastructure NATs (CGNs) but =

> not CPE NATs, would be in v4v6-xlat
> - A+P, IVI, SAM, and tunneling aspects of DS lite  would be in =

> v4v6-Xlat

s/v4v6-xlat/v4v6-tunnel/  right?

Marc.


> - questions that concern interactions between the two, would remain in =

> the current mailing list.
> =

> RD
> =

> Hemant Singh (shemant)   (m/j/a) 10/3/08 12:19 AM:
>> Fred,
>>
>> Good suggestion.  However, what if a BOF is needed to discuss a =

>> solution where both xlat and tunnel are needed?  Do we discuss those =

>> in this WG mailer or spawn a 3rd new BOF mailer?
>>
>> Thanks.
>>
>> Hemant
>> -----Original Message-----
>> From: v4v6interim-bounces@ietf.org =

>> [mailto:v4v6interim-bounces@ietf.org]
>> On Behalf Of Fred Baker (fred)
>> Sent: Thursday, October 02, 2008 5:14 PM
>> To: v4v6interim@ietf.org
>> Subject: [v4v6interim] BOF discussions
>>
>> So various folks are going to be doing a lot of work in email and =

>> such in the next few weeks. May I suggest that the ADs schedule a BOF =

>> for the translation solution and one for the tunneling solution (and =

>> one for the
>> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit =

>> down together and discuss?
>>
>> I would also suggest that you set of mailing lists for these BOFs, =

>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them =

>> to this forum and let people sign up the usual way.
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
>>
> =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim


--
=3D=3D=3D=3D=3D=3D=3D=3D=3D
IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca Stun/Turn=
 server: http://numb.viagenie.ca

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 07:12:03 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 030403A693B;
	Fri,  3 Oct 2008 07:12:03 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 163383A693B
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 07:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iXOxH7l+P25S for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 07:11:58 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id D28453A6892
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:10:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,356,1220227200"; d="scan'208";a="23087034"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 03 Oct 2008 14:10:44 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m93EAiVM012555; 
	Fri, 3 Oct 2008 10:10:44 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m93EAhvo016849;
	Fri, 3 Oct 2008 14:10:44 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 10:10:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 10:10:29 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42393@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <48E61A05.20406@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: AcklWcsAdsdJX1jKSiO20vuELGTLVAAB/E3g
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
	<48E61A05.20406@free.fr>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-OriginalArrivalTime: 03 Oct 2008 14:10:43.0984 (UTC)
	FILETIME=[D30F9900:01C92561]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2192; t=1223043044;
	x=1223907044; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20RE=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20
	|To:=20=3D?iso-8859-1?Q?R=3DE9mi_Despr=3DE9s?=3D=20<remi.de
	spres@free.fr>;
	bh=qlYg4kW+5xF3VxcDGDnY3keTqg88ILEXO+Z+8BRiSOc=;
	b=ZKr1imy2rX11M8mkwUu6Qu+lhdNl6JC7X5A6N+oM9Auwla6cbc+mUJ5Shw
	TByP6I0R5HUcEPj00W9fVITM3ytvhBsS+LysezaC5s/b1ck43MTAhg2ZHNUV
	10QoGIAW18;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

OK, Remi - sounds good.

Thanks.

Hemant =


-----Original Message-----
From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr] =

Sent: Friday, October 03, 2008 9:12 AM
To: Hemant Singh (shemant)
Cc: Fred Baker (fred); v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions

I support Fred's suggestion of separating discussion spaces for what is spe=
cific to tunneling and what is specific to translation.

In my understanding:
- NAT64, NAT46, and what concerns ISP infrastructure NATs (CGNs) but not CP=
E NATs, would be in v4v6-xlat
- A+P, IVI, SAM, and tunneling aspects of DS lite  would be in v4v6-Xlat
- questions that concern interactions between the two, would remain in the =
current mailing list.

RD

Hemant Singh (shemant)   (m/j/a) 10/3/08 12:19 AM:
> Fred,
> =

> Good suggestion.  However, what if a BOF is needed to discuss a =

> solution where both xlat and tunnel are needed?  Do we discuss those =

> in this WG mailer or spawn a 3rd new BOF mailer?
> =

> Thanks.
> =

> Hemant
> =

> -----Original Message-----
> From: v4v6interim-bounces@ietf.org =

> [mailto:v4v6interim-bounces@ietf.org]
> On Behalf Of Fred Baker (fred)
> Sent: Thursday, October 02, 2008 5:14 PM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] BOF discussions
> =

> So various folks are going to be doing a lot of work in email and such =

> in the next few weeks. May I suggest that the ADs schedule a BOF for =

> the translation solution and one for the tunneling solution (and one =

> for the
> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit =

> down together and discuss?
> =

> I would also suggest that you set of mailing lists for these BOFs, =

> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them =

> to this forum and let people sign up the usual way.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

> =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 07:48:47 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94BC43A68DF;
	Fri,  3 Oct 2008 07:48:47 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A8AE3A68DF
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 07:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.186, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cpP+2iotFNYc for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 07:48:44 -0700 (PDT)
Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28])
	by core3.amsl.com (Postfix) with ESMTP id AB33A3A6AC4
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:48:44 -0700 (PDT)
Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 4AA0F12B781;
	Fri,  3 Oct 2008 16:48:41 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 38E7312B768;
	Fri,  3 Oct 2008 16:48:36 +0200 (CEST)
Message-ID: <48E63077.5070907@free.fr>
Date: Fri, 03 Oct 2008 16:47:19 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
	<48E61A05.20406@free.fr> <48E61AE0.7080200@viagenie.ca>
In-Reply-To: <48E61AE0.7080200@viagenie.ca>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

TWFyYyBCbGFuY2hldCAgIChtL2ovYSkgMTAvMy8wOCAzOjE1IFBNOgo+IFLvv71taSBEZXNwcu+/
vXMgYSDvv71jcml0IDoKPj4gSSBzdXBwb3J0IEZyZWQncyBzdWdnZXN0aW9uIG9mIHNlcGFyYXRp
bmcgZGlzY3Vzc2lvbiBzcGFjZXMgZm9yIHdoYXQgaXMKPj4gc3BlY2lmaWMgdG8gdHVubmVsaW5n
IGFuZCB3aGF0IGlzIHNwZWNpZmljIHRvIHRyYW5zbGF0aW9uLgo+Pgo+PiBJbiBteSB1bmRlcnN0
YW5kaW5nOgo+PiAtIE5BVDY0LCBOQVQ0NiwgYW5kIHdoYXQgY29uY2VybnMgSVNQIGluZnJhc3Ry
dWN0dXJlIE5BVHMgKENHTnMpIGJ1dCBub3QKPj4gQ1BFIE5BVHMsIHdvdWxkIGJlIGluIHY0djYt
eGxhdAo+PiAtIEErUCwgSVZJLCBTQU0sIGFuZCB0dW5uZWxpbmcgYXNwZWN0cyBvZiBEUyBsaXRl
ICB3b3VsZCBiZSBpbiB2NHY2LVhsYXQKPiAKPiBzL3Y0djYteGxhdC92NHY2LXR1bm5lbC8gIHJp
Z2h0PwpSaWdodCAoT29wcyEpCgpSRApfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwp2NHY2aW50ZXJpbSBtYWlsaW5nIGxpc3QKdjR2NmludGVyaW1AaWV0Zi5v
cmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2aW50ZXJpbQo=


From v4v6interim-bounces@ietf.org  Fri Oct  3 07:49:16 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B574B3A693B;
	Fri,  3 Oct 2008 07:49:16 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF7083A693B
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 07:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5 tests=[AWL=1.052, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PlYqI5x9niCY for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 07:49:15 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 7986E3A6820
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:49:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,356,1220227200"; d="scan'208";a="21573820"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Oct 2008 14:49:09 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m93En9jp017112; 
	Fri, 3 Oct 2008 16:49:09 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m93En90C002115;
	Fri, 3 Oct 2008 14:49:09 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 16:49:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 16:46:00 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE0079493AC@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Potential interoperability issue
Thread-Index: Ackkt5OsAbhCRIJoTOGjwHwnT2WrhQArrr1A
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
	<3127D92C-CADA-4A3C-8C10-5A7194F4B3CD@apple.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "james woodyatt" <jhw@apple.com>, <v4v6interim@ietf.org>
X-OriginalArrivalTime: 03 Oct 2008 14:49:08.0921 (UTC)
	FILETIME=[30E91290:01C92567]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=828; t=1223045349; x=1223909349;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20Potential=20interoperab
	ility=20issue |Sender:=20;
	bh=FMUdcxnJXLM8j972m2eHe9iyn4bOxAGKc+fjwECzom4=;
	b=psZTK4a6dLRsg4nixwCI0nDwuFURWfIIabHLLuO6UznxjziwJKUoGLap5u
	U7Ux4/OH9Gttii9w6zH9IolOAnaRIo51yEQTIIBIbNdkS0u9y1Xet1GbZCEo
	btj3NY554Z;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 =

> =

> > That either calls for an ALG or appropriate code in the =

> servers that =

> > can deal with an <> address even when the server doesn't =

> have such an =

> > address. The simplest resolution might be to have the MTA =

> have a leg =

> > in the IPv6 world and one in the IPv4 world.
> =

> I would agree that this is the simplest way to handle SMTP servers.

Agreed as well. A proxy approach is always better (predictable, traceable) =
but then you need to proxy/intercept the DNS request for the MX record and =
change it on the fly.

Moreover, AFAIK, the optional IP address in the HELO message is just 'for i=
nformation' only. It is mainly used in the Received: headers which are used=
 for debugging (and can easily be forged as they are not part of the DKIM s=
ignatire).

-=E9ric
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 07:54:44 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FE9F28C146;
	Fri,  3 Oct 2008 07:54:44 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4277C28C1FC
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 07:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.746
X-Spam-Level: 
X-Spam-Status: No, score=-5.746 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ljz6wexNuZOe for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 07:54:42 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 12AFB28C1D4
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:54:41 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 3 Oct 2008 14:47:27 -0000
X-AuditID: 80125474-ac999bb000000a40-42-48e6307f9f3d
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	6840521AF2D
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 07:47:27 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K86004IL3R2SQO2@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 03 Oct 2008 07:47:27 -0700 (PDT)
Date: Fri, 03 Oct 2008 10:47:29 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <48E63081.7070701@sri.com>
MIME-version: 1.0
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I am most interested in translation solutions and support some "divide 
and conquer" but will try to follow all the discussions.  Given the high 
degree of overlap in interest, we need to make sure the BOFs are 
scheduled for Minneapolis so that all can attend either or both.  Also 
avoid obvious conflicts with v6ops, 6man, etc.

Fred Baker wrote:
> So various folks are going to be doing a lot of work in email and such 
> in the next few weeks. May I suggest that the ADs schedule a BOF for 
> the translation solution and one for the tunneling solution (and one 
> for the 4-4-4 solution?) separate from WGs, to enable the doc authors 
> to sit down together and discuss?
>
> I would also suggest that you set of mailing lists for these BOFs, 
> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them 
> to this forum and let people sign up the usual way.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 08:06:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4881928C146;
	Fri,  3 Oct 2008 08:06:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6E7E28C12D
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 08:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.204
X-Spam-Level: **
X-Spam-Status: No, score=2.204 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768,
	HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6,
	RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H-KijmuYKN3m for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 08:06:01 -0700 (PDT)
Received: from paoakoavas09.cable.comcast.com (paoakoavas09.cable.comcast.com
	[208.17.35.58]) by core3.amsl.com (Postfix) with ESMTP id 82E1528C1FC
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 08:05:14 -0700 (PDT)
Received: from ([10.52.116.31])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-NTF18.61072462;
	Fri, 03 Oct 2008 11:04:56 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Fri, 3 Oct 2008 11:04:55 -0400
Received: from 147.191.223.149 ([147.191.223.149]) by
	PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) via Exchange
	Front-End Server webmail.comcast.com ([24.40.8.152]) with
	Microsoft Exchange Server HTTP-DAV ; Fri,  3 Oct 2008 15:04:19 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Fri, 03 Oct 2008 11:04:18 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: <v4v6interim@ietf.org>
Message-ID: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: AcklaCkFzeaG20B8QU2nsBXxNmYNSgAASW8d
In-Reply-To: <48E63081.7070701@sri.com>
Mime-version: 1.0
X-OriginalArrivalTime: 03 Oct 2008 15:04:55.0985 (UTC)
	FILETIME=[65679210:01C92569]
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Our Ads have re-chartered the Softwire wg to address the tunneling + nat44
case, so it is unclear to me why we would need a bof in that particular
space when the working group will be meeting in Minneapolis.

  - Alain. 


On 10/3/08 10:47 AM, "Ed Jankiewicz" <edward.jankiewicz@sri.com> wrote:

> I am most interested in translation solutions and support some "divide
> and conquer" but will try to follow all the discussions.  Given the high
> degree of overlap in interest, we need to make sure the BOFs are
> scheduled for Minneapolis so that all can attend either or both.  Also
> avoid obvious conflicts with v6ops, 6man, etc.
> 
> Fred Baker wrote:
>> So various folks are going to be doing a lot of work in email and such
>> in the next few weeks. May I suggest that the ADs schedule a BOF for
>> the translation solution and one for the tunneling solution (and one
>> for the 4-4-4 solution?) separate from WGs, to enable the doc authors
>> to sit down together and discuss?
>> 
>> I would also suggest that you set of mailing lists for these BOFs,
>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them
>> to this forum and let people sign up the usual way.
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>> 
> 
> --
> Ed Jankiewicz - SRI International
> Fort Monmouth Branch Office - IPv6 Research
> Supporting DISA Standards Engineering Branch
> 732-389-1003 or  ed.jankiewicz@sri.com
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 08:28:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC43128C27D;
	Fri,  3 Oct 2008 08:28:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0644528C27D
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 08:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.019
X-Spam-Level: 
X-Spam-Status: No, score=-6.019 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1NFuLFM9q8QH for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 08:28:50 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 720D828C1FC
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 08:28:50 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 3 Oct 2008 15:28:44 -0000
X-AuditID: 80125474-ab196bb000000a40-c8-48e63a2b335d
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	E525521AF2D
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 08:28:43 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K86004875NUSM58@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 03 Oct 2008 08:28:43 -0700 (PDT)
Date: Fri, 03 Oct 2008 11:28:46 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: v4v6interim@ietf.org
Message-id: <48E63A2E.6080804@sri.com>
MIME-version: 1.0
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] Questions for the group
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

due to travel constraint I ran out before the final poll.  for the 
record, here is my response to what I think the scenarios ended up 
being, and the questions on the floor.  Caveat:  while I am answering in 
the context of my understanding/interpretation of the needs of the 
organization I support, the opinions are mine, not those of my employer 
or customer.  By "core" I mean the major enterprise networks and 
backbones that US DoD will be running.   For the translation scenarios, 
"my IPv4-only network" e.g. may be a subset.  Also note, as I stated at 
the meeting, solutions space needs to consider where the constraint is - 
either the application, host or "my network" supports only 1 address 
family - and I believe the translation discussion should be centered on 
application and host-stack adaptation.  Other techniques can satisfy the 
"my network" only carries one address family.

Scenario 1: IPv4 sites reaching the global IPv4 Internet?

    Q) do you have to cope today?
    A) right now, dual-stack core adequately meets this need.

    Q) do you think you may have to cope in the future?
    A) potentially.  Several policy documents and business case for IPv6 
assume that operational cost will be incentive to turn off IPv4 routing 
in the core, so tunneling solutions will be needed

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes. 

Scenario 2: Providers running out of private IPv4 space?

    Q) do you have to cope today?
    A) no.

    Q) do you think you may have to cope in the future?
    A) no.

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes. 

Scenario 3: My IPv6-only network to Global IPv4 Internet?

    Q) do you have to cope today?
    A)  only in experimental context.  There is some irrational 
resistance to IPv6 adoption due to FUD about losing access to the IPv4 
Internet.

    Q) do you think you may have to cope in the future?
    A) potentially.  If IPv4 routing is turned off in parts of the core, 
these are equivalent to an IPv6-only network.  Also, some constituents 
are very interested in tactical networks taking advantage of new work in 
IPv6 mobility not available in IPv4; this may result in greenfield 
IPv6-only deployments.  Maintaining "access to the global IPv4 Internet" 
would be desirable.

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes. 

Scenario 4:  Global IPv6 Internet to My IPv4-only network?

    Q) do you have to cope today?
    A) Yes, in development, testing and experimental contexts.

    Q) do you think you may have to cope in the future?
    A) absolutely.  large existing base of networked equipment with long 
anticipated lifespan that is IPv4-only.

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes.  And I intend to contribute in this area.

Scenario 5: Global IPv4 Internet to My IPv6-only network?

    Q) do you have to cope today?
    A) Only in experimental context.

    Q) do you think you may have to cope in the future?
    A) potentially, see Scenario 3.

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes. 

Scenario 6: My IPv4-only network to global IPv6 Internet?

    A) Yes, in development, testing and experimental contexts.

    Q) do you think you may have to cope in the future?
    A) absolutely.  large existing base of networked equipment with long 
anticipated lifespan that is IPv4-only.

    Q) Should IETF invest cycles in defining this scenario and 
developing solutions?
    A) Yes.  And I intend to contribute in this area.

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 09:20:10 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4B1A3A698E;
	Fri,  3 Oct 2008 09:20:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A4923A698E
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 09:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.494
X-Spam-Level: 
X-Spam-Status: No, score=-1.494 tagged_above=-999 required=5
	tests=[AWL=-0.145, BAYES_00=-2.599, HELO_EQ_FR=0.35,
	J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dyqbk4sQ60HN for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 09:20:04 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id B19673A68E1
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 09:20:04 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 1BB9817802;
	Fri,  3 Oct 2008 18:20:17 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 0ECAE177EC;
	Fri,  3 Oct 2008 18:20:06 +0200 (CEST)
Message-ID: <48E645D9.9050505@free.fr>
Date: Fri, 03 Oct 2008 18:18:33 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Alain Durand <alain_durand@cable.comcast.com>
References: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
In-Reply-To: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

This seems indeed better than a BOF.
Is the new charter available?

RD

Alain Durand   (m/j/a) 10/3/08 5:04 PM:
> Our Ads have re-chartered the Softwire wg to address the tunneling + nat44
> case, so it is unclear to me why we would need a bof in that particular
> space when the working group will be meeting in Minneapolis.
> 
>   - Alain. 
> 
> 
> On 10/3/08 10:47 AM, "Ed Jankiewicz" <edward.jankiewicz@sri.com> wrote:
> 
>> I am most interested in translation solutions and support some "divide
>> and conquer" but will try to follow all the discussions.  Given the high
>> degree of overlap in interest, we need to make sure the BOFs are
>> scheduled for Minneapolis so that all can attend either or both.  Also
>> avoid obvious conflicts with v6ops, 6man, etc.
>>
>> Fred Baker wrote:
>>> So various folks are going to be doing a lot of work in email and such
>>> in the next few weeks. May I suggest that the ADs schedule a BOF for
>>> the translation solution and one for the tunneling solution (and one
>>> for the 4-4-4 solution?) separate from WGs, to enable the doc authors
>>> to sit down together and discuss?
>>>
>>> I would also suggest that you set of mailing lists for these BOFs,
>>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them
>>> to this forum and let people sign up the usual way.
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>
>> --
>> Ed Jankiewicz - SRI International
>> Fort Monmouth Branch Office - IPv6 Research
>> Supporting DISA Standards Engineering Branch
>> 732-389-1003 or  ed.jankiewicz@sri.com
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
> 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 09:24:52 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 529B43A698E;
	Fri,  3 Oct 2008 09:24:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22A923A698E
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 09:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1rzpz0J1uoMG for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 09:24:48 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 80BB33A68A7
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 09:24:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,357,1220227200"; d="scan'208";a="23140006"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 03 Oct 2008 16:25:17 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m93GPHvH023855; 
	Fri, 3 Oct 2008 12:25:17 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m93GPGSn000512;
	Fri, 3 Oct 2008 16:25:16 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 12:25:16 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 12:25:16 -0400
Message-ID: <BB56240F3A190F469C52A57138047A03011DB146@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <48E645D9.9050505@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: AckldBNQoiubjKNRR6eEu+lmXs2O6AAAH4ww
References: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
	<48E645D9.9050505@free.fr>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>,
	"Alain Durand" <alain_durand@cable.comcast.com>
X-OriginalArrivalTime: 03 Oct 2008 16:25:16.0831 (UTC)
	FILETIME=[9EDA4AF0:01C92574]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2609; t=1223051117;
	x=1223915117; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m>
	|Subject:=20RE=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20
	|To:=20=3D?iso-8859-1?Q?R=3DE9mi_Despr=3DE9s?=3D=20<remi.de
	spres@free.fr>,=0A=20=20=20=20=20=20=20=20=22Alain=20Durand=
	22=20<alain_durand@cable.comcast.com>;
	bh=FAuvgri9bt/mcpG9EQGEmzfunFCstSW1X9iibVmyoKM=;
	b=hxgqbUKwBgE5loqxUg6iKwhVsqzjDjeD5cRmJCjKlid+8WsmZKdH399HNi
	b0nKcUq9YI6viUKj+WoBuhcbRBr29Wk9RHiQFs9FnUIyQ/2eF3kkiZ/j5/eB
	L4y2OOslGT;
Authentication-Results: rtp-dkim-1; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

http://www.ietf.org/mail-archive/web/softwires/current/msg00687.html

- Wes =


-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org] On=
 Behalf Of R=E9mi Despr=E9s
Sent: Friday, October 03, 2008 12:19 PM
To: Alain Durand
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions

This seems indeed better than a BOF.
Is the new charter available?

RD

Alain Durand   (m/j/a) 10/3/08 5:04 PM:
> Our Ads have re-chartered the Softwire wg to address the tunneling + =

> nat44 case, so it is unclear to me why we would need a bof in that =

> particular space when the working group will be meeting in Minneapolis.
> =

>   - Alain. =

> =

> =

> On 10/3/08 10:47 AM, "Ed Jankiewicz" <edward.jankiewicz@sri.com> wrote:
> =

>> I am most interested in translation solutions and support some =

>> "divide and conquer" but will try to follow all the discussions.  =

>> Given the high degree of overlap in interest, we need to make sure =

>> the BOFs are scheduled for Minneapolis so that all can attend either =

>> or both.  Also avoid obvious conflicts with v6ops, 6man, etc.
>>
>> Fred Baker wrote:
>>> So various folks are going to be doing a lot of work in email and =

>>> such in the next few weeks. May I suggest that the ADs schedule a =

>>> BOF for the translation solution and one for the tunneling solution =

>>> (and one for the 4-4-4 solution?) separate from WGs, to enable the =

>>> doc authors to sit down together and discuss?
>>>
>>> I would also suggest that you set of mailing lists for these BOFs, =

>>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them =

>>> to this forum and let people sign up the usual way.
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>
>> --
>> Ed Jankiewicz - SRI International
>> Fort Monmouth Branch Office - IPv6 Research Supporting DISA Standards =

>> Engineering Branch
>> 732-389-1003 or  ed.jankiewicz@sri.com
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

> =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 10:00:09 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A59C628C0FD;
	Fri,  3 Oct 2008 10:00:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 674D528C0FD
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 10:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.128
X-Spam-Level: 
X-Spam-Status: No, score=-6.128 tagged_above=-999 required=5
	tests=[AWL=-0.429, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xtOKkx7vq0Wo for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 10:00:07 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id E6FA628C0D8
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 10:00:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,357,1220227200"; d="scan'208";a="168247523"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 03 Oct 2008 17:00:36 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93H0a21023083; 
	Fri, 3 Oct 2008 10:00:36 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m93H0XMh029944;
	Fri, 3 Oct 2008 17:00:36 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 13:00:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 12:59:54 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E423A0@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <48E645D9.9050505@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: AckldBNR02g/BV5OSiiEU/EAkq59dgABTguQ
References: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
	<48E645D9.9050505@free.fr>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>,
	"Alain Durand" <alain_durand@cable.comcast.com>
X-OriginalArrivalTime: 03 Oct 2008 17:00:35.0208 (UTC)
	FILETIME=[8D80F880:01C92579]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2712; t=1223053236;
	x=1223917236; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20RE=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20; bh=d6dgLC0Hm9GZig2M+hb1ScpCy7NaPVNgFtMzhjp0Sws=;
	b=YN/ftJA+jXWa7PrR4KumVN27dCXvdwSESI1Y7T1rCUAIxxtD4Zlvmp7YFh
	g0g916VQt8UM0+MJOvgXO7IEjvyQNPvF5W1OeVdlgdE26oNakLlX4GvxrAMG
	9VpXyjYG1s;
Authentication-Results: sj-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I agree with Alain for not having a BOF.  However, do we still keep the 3 m=
ailers or do we not spawn the two new suggested mailers for tunnels vs. xla=
te?

Thanks.

Hemant =


-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org] On=
 Behalf Of R=E9mi Despr=E9s
Sent: Friday, October 03, 2008 12:19 PM
To: Alain Durand
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions

This seems indeed better than a BOF.
Is the new charter available?

RD

Alain Durand   (m/j/a) 10/3/08 5:04 PM:
> Our Ads have re-chartered the Softwire wg to address the tunneling + =

> nat44 case, so it is unclear to me why we would need a bof in that =

> particular space when the working group will be meeting in Minneapolis.
> =

>   - Alain. =

> =

> =

> On 10/3/08 10:47 AM, "Ed Jankiewicz" <edward.jankiewicz@sri.com> wrote:
> =

>> I am most interested in translation solutions and support some =

>> "divide and conquer" but will try to follow all the discussions.  =

>> Given the high degree of overlap in interest, we need to make sure =

>> the BOFs are scheduled for Minneapolis so that all can attend either =

>> or both.  Also avoid obvious conflicts with v6ops, 6man, etc.
>>
>> Fred Baker wrote:
>>> So various folks are going to be doing a lot of work in email and =

>>> such in the next few weeks. May I suggest that the ADs schedule a =

>>> BOF for the translation solution and one for the tunneling solution =

>>> (and one for the 4-4-4 solution?) separate from WGs, to enable the =

>>> doc authors to sit down together and discuss?
>>>
>>> I would also suggest that you set of mailing lists for these BOFs, =

>>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them =

>>> to this forum and let people sign up the usual way.
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>
>> --
>> Ed Jankiewicz - SRI International
>> Fort Monmouth Branch Office - IPv6 Research Supporting DISA Standards =

>> Engineering Branch
>> 732-389-1003 or  ed.jankiewicz@sri.com
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

> =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 11:35:39 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C5C83A6A3E;
	Fri,  3 Oct 2008 11:35:39 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B628A3A6AEF
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 11:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.450, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jtdpDYVQFh7d for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 11:35:36 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 2B40D28C18C
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 11:35:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,358,1220227200"; d="scan'208";a="23121451"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 03 Oct 2008 18:36:01 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93Ia136019344; 
	Fri, 3 Oct 2008 14:36:01 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m93Ia1rr001278;
	Fri, 3 Oct 2008 18:36:01 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 14:36:01 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 14:36:00 -0400
Message-ID: <BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: AcklOzbv7AvOH9xVQyuPwJwY/JGnogAS1TLw
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "Hiroshi MIYATA" <miyata@tahi.org>, <v4v6interim@ietf.org>
X-OriginalArrivalTime: 03 Oct 2008 18:36:01.0778 (UTC)
	FILETIME=[E2CE3520:01C92586]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1359; t=1223058961;
	x=1223922961; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m>
	|Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20
	|To:=20=22Hiroshi=20MIYATA=22=20<miyata@tahi.org>,=20<v4v6i
	nterim@ietf.org>;
	bh=CtPXbYmB+ODMAm4PN2sNizs45a5Scaoo8AccUFKz3FM=;
	b=eisMoacgCZIpOShj6SlxeZmELhF2MwyQD+VjvLLn8XF/U9UHFR6Bmls/V8
	AlO0gueLw/zqPMUFdDcUISYndfa5WmjJQNFVo4wnQkQex9YohfEk19tOj4Wg
	Qs6w0+tBVB;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Some SP's may view ICMP as an attack vector and may explicitly block
ICMP messages.

In this case, the only way to get connectivity for packets that are too
large is to fragment.

- Wes 

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Hiroshi MIYATA
Sent: Friday, October 03, 2008 5:31 AM
To: v4v6interim@ietf.org
Subject: [v4v6interim] Fragmentation Options in NAT6 presentation

Jennings,


FYI.
Though it is already clearly explained by Dave, let me give you the
pointer.
The answer for your question of "Fragmentation options" is clearly
stated in RFC2765(SIIT) as end-to-end path MTU discovery.
See Section 3 and 4.

And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
       Note: A node may receive a Packet Too Big message reporting a
       next-hop MTU that is less than the IPv6 minimum link MTU.  In
that
       case, the node is not required to reduce the size of subsequent
       packets sent on the path to less than the IPv6 minimun link MTU,
       but rather must include a Fragment header in those packets [IPv6-
       SPEC].

It must work well. ;-)

Regards,

....miyata
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 12:18:35 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33F513A6A11;
	Fri,  3 Oct 2008 12:18:35 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 797243A6859
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 12:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.021
X-Spam-Level: 
X-Spam-Status: No, score=-6.021 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QIesS96DyHiS for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 12:18:33 -0700 (PDT)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM
	[128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id 8A1143A6A11
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 12:18:33 -0700 (PDT)
Received: from smssmtp-internal1.sri.com (128.18.84.115)
	by mailgate-internal3.sri.com with SMTP; 3 Oct 2008 19:19:00 -0000
X-AuditID: 80125473-ac1aabb000000a1e-6b-48e67024943c
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id
	793BB21AF2A
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 12:19:00 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K86004OAGBNSL3C@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 03 Oct 2008 12:19:00 -0700 (PDT)
Date: Fri, 03 Oct 2008 15:19:02 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: v4v6interim@ietf.org
Message-id: <48E67026.6060504@sri.com>
MIME-version: 1.0
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] revised scenarios
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I'm not sure we really got total consensus/closure on the final set of 
scenarios, at least before I left.  I assume the next draft of the 
Scenarios doc will reflect the discussion and outcome of the interim 
meeting, but I wanted to restate a couple things I said at the mic 
during the meeting and extend them:

1.  I agree with the fundamental division translation space by which 
address family is constrained, i.e. the subject is either IPv6-only or 
IPv4-only.
2.  I am not sure it is necessary to further divide the scenario by 
client/server.  Yes, solutions may/not be bi-directional, so it is 
useful to consider  "my IPv4 to global IPv6" versus "global IPv6 to my 
IPv4" to explore different mechanisms (e.g. what to do with DNS).  
Bottom line, I go along with the 4 sub-scenarios for translation.
3.  I definitely draw a distinction between a "network" constraint and 
an application or host-stack constraint, i.e. "my IPv4 network" only 
routes IPv4 internally versus "my IPv4 host/application" that only 
understands IPv4 addresses.  "My IPv4 network" may include dual-stack 
hosts/applications, but that leads to a different solution than 
IPv4-only hosts/applications needing translation.  I think dual-stack 
access through a constrained network factors out to some of the other 
areas already under discussion.

No need to argue this out, I go along with whatever leads to a sensible 
division of labor.  Definitely those with lots of IPv4 stuff needing to 
coexist with emerging IPv6 internet have different interest than those 
with new IPv6 stuff wanting to maintain access to the current IPv4 
internet. 

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 12:19:19 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4BF8F3A6986;
	Fri,  3 Oct 2008 12:19:19 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2015D3A6986
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 12:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.073
X-Spam-Level: 
X-Spam-Status: No, score=-6.073 tagged_above=-999 required=5 tests=[AWL=0.526, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ElI6Qjn9PBwl for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 12:19:17 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 9BB843A6A32
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 12:19:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,358,1220227200"; d="scan'208";a="21594529"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Oct 2008 19:19:44 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m93JJitF013059; 
	Fri, 3 Oct 2008 21:19:44 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m93JJiRT000220;
	Fri, 3 Oct 2008 19:19:44 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 21:19:43 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 3 Oct 2008 21:16:34 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE007949456@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: AcklOzbv7AvOH9xVQyuPwJwY/JGnogAS1TLwAAFUT4A=
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>,
	"Hiroshi MIYATA" <miyata@tahi.org>, <v4v6interim@ietf.org>
X-OriginalArrivalTime: 03 Oct 2008 19:19:43.0824 (UTC)
	FILETIME=[FDAAAD00:01C9258C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2770; t=1223061584;
	x=1223925584; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=zmM1rUF0w0wFy6RZBly9TyX1uL7XwhQHG96T9Ey483k=;
	b=dIKwF+wqgYAme9Hr9TpEJORbxDvqt/HxUDZr4G9glvgCUv1JsxJ0oVRIYQ
	1yITnn6eYLye3tYRgtxUqtBgYn/rvGLBRvONHnlDUh5QDHOjafKSkleF5AXR
	6t4FrD/jtU;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Or more precisely, SP won't block ICMP in transit but have NO choice but ra=
te limiting the number of ICMPv6 packet too big _generated_ by a router to =
100 pps or so... (NB: this is already the case now in IPv4 and IPv6 in orde=
r to save CPU)

Of course, if Google Map (or any other applications) has to open 50+ connec=
tions per end-user transaction, and if there are more than 2 end-users conn=
ecting to Google Maps within the same second (this is assumed to by ironica=
l -- Friday evening), then some connections will fail... (cached informatio=
n will only be available after the connection timed out I'm afraid).

Hence the importance of setting 'manually' the MTU right at the edge where =
the ICMP generation rate is probably (?) lower than in the core.

-=E9ric

> -----Original Message-----
> From: v4v6interim-bounces@ietf.org =

> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Wes Beebee =

> (wbeebee)
> Sent: vendredi 3 octobre 2008 20:36
> To: Hiroshi MIYATA; v4v6interim@ietf.org
> Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
> =

> Some SP's may view ICMP as an attack vector and may =

> explicitly block ICMP messages.
> =

> In this case, the only way to get connectivity for packets =

> that are too large is to fragment.
> =

> - Wes =

> =

> -----Original Message-----
> From: v4v6interim-bounces@ietf.org =

> [mailto:v4v6interim-bounces@ietf.org]
> On Behalf Of Hiroshi MIYATA
> Sent: Friday, October 03, 2008 5:31 AM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
> =

> Jennings,
> =

> =

> FYI.
> Though it is already clearly explained by Dave, let me give =

> you the pointer.
> The answer for your question of "Fragmentation options" is =

> clearly stated in RFC2765(SIIT) as end-to-end path MTU discovery.
> See Section 3 and 4.
> =

> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
>        Note: A node may receive a Packet Too Big message reporting a
>        next-hop MTU that is less than the IPv6 minimum link =

> MTU.  In that
>        case, the node is not required to reduce the size of subsequent
>        packets sent on the path to less than the IPv6 minimun =

> link MTU,
>        but rather must include a Fragment header in those =

> packets [IPv6-
>        SPEC].
> =

> It must work well. ;-)
> =

> Regards,
> =

> ....miyata
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 12:52:37 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 914AE3A6B59;
	Fri,  3 Oct 2008 12:52:37 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 535B63A68AF
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 12:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZhL9SEzZgOc3 for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 12:52:35 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id 3FA533A6B56
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 12:52:35 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m93JpciF022743;
	Sat, 4 Oct 2008 04:51:38 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m93JpSwu056885; Sat, 4 Oct 2008 04:51:29 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sat, 4 Oct 2008 04:51:28 +0900
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Correct!

We have met the problem, and, yes, only the way is fragmenting
the packet on the Translator.
We have developed it as a optional behavior.

It may cause the argument if we state it in document, since
it break the PMTU Discovery semantics.

But it is the fact.

Maybe it is not recommended to describe on BEHAVE documents
as a requirement.
But we should give the hint of this issue on the documents
as possible problems and solution and utilization (since
it is not recommended to use this in public service, but
possible to be used for controllable area of the administrator.)

Regards,

....miyata


On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote:

> Some SP's may view ICMP as an attack vector and may explicitly block
> ICMP messages.
>
> In this case, the only way to get connectivity for packets that are  
> too
> large is to fragment.
>
> - Wes
>
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org 
> ]
> On Behalf Of Hiroshi MIYATA
> Sent: Friday, October 03, 2008 5:31 AM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
>
> Jennings,
>
>
> FYI.
> Though it is already clearly explained by Dave, let me give you the
> pointer.
> The answer for your question of "Fragmentation options" is clearly
> stated in RFC2765(SIIT) as end-to-end path MTU discovery.
> See Section 3 and 4.
>
> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
>       Note: A node may receive a Packet Too Big message reporting a
>       next-hop MTU that is less than the IPv6 minimum link MTU.  In
> that
>       case, the node is not required to reduce the size of subsequent
>       packets sent on the path to less than the IPv6 minimun link MTU,
>       but rather must include a Fragment header in those packets  
> [IPv6-
>       SPEC].
>
> It must work well. ;-)
>
> Regards,
>
> ....miyata
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 13:02:33 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8443128C0E8;
	Fri,  3 Oct 2008 13:02:33 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B553328C0DB
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 13:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.234
X-Spam-Level: 
X-Spam-Status: No, score=-106.234 tagged_above=-999 required=5
	tests=[AWL=-0.235, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WmmZjVsxmxUW for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 13:02:31 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id F3B123A6833
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 13:02:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,358,1220227200"; d="scan'208";a="86601350"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 03 Oct 2008 20:02:22 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93K2MsJ013525
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 13:02:22 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m93K2MRc003434
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 20:02:22 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 13:02:22 -0700
Received: from [10.242.24.102] ([10.21.87.71]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 13:02:21 -0700
Message-Id: <BEBD49E2-53FA-46A9-BAAD-063753DE078A@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 13:02:18 -0700
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 03 Oct 2008 20:02:21.0751 (UTC)
	FILETIME=[F24F5C70:01C92592]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1660; t=1223064142;
	x=1223928142; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20; bh=FHNa8NmwdSRs630FzW/pc+VjhvXQiQKcaPiPTotFj8k=;
	b=p2BUMTiGly8f7ClSHpcdySIMN+8c4aEQ+8e2+CiEpAsn0b5N5e3/2bbJsW
	GaP7S8RiE+H+JYnS2ESpXRSzQd65BA1SYcMDKQH5wkm3kD+Gth1goSNT2Szw
	rWZ+mMfMgN;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

What I'm suggesting is that the folks that need to discuss translation  
- perhaps 15 of us total - sit down and talk about it, and the same  
opportunity be available to the tunneling folks. My point is to foment  
accomplishment; as Randy says, he needs this yesterday. I have no  
problem with other discussions happening too and expect still to have  
a requirements discussion in v6ops.

On Oct 2, 2008, at 3:19 PM, Hemant Singh (shemant) wrote:

> Fred,
>
> Good suggestion.  However, what if a BOF is needed to discuss a  
> solution
> where both xlat and tunnel are needed?  Do we discuss those in this WG
> mailer or spawn a 3rd new BOF mailer?
>
> Thanks.
>
> Hemant
>
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org 
> ]
> On Behalf Of Fred Baker (fred)
> Sent: Thursday, October 02, 2008 5:14 PM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] BOF discussions
>
> So various folks are going to be doing a lot of work in email and such
> in the next few weeks. May I suggest that the ADs schedule a BOF for  
> the
> translation solution and one for the tunneling solution (and one for  
> the
> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit
> down together and discuss?
>
> I would also suggest that you set of mailing lists for these BOFs,
> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them  
> to
> this forum and let people sign up the usual way.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 13:02:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1E6228C11E;
	Fri,  3 Oct 2008 13:02:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 626C33A68EA
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 13:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.224
X-Spam-Level: 
X-Spam-Status: No, score=-106.224 tagged_above=-999 required=5
	tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Wj86OujSqXt3 for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 13:02:54 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 9B6D328C0DB
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 13:02:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,358,1220227200"; d="scan'208";a="92193537"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 03 Oct 2008 20:03:02 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93K32Tl014522; 
	Fri, 3 Oct 2008 13:03:02 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m93K32OX025779;
	Fri, 3 Oct 2008 20:03:02 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 13:03:02 -0700
Received: from [10.242.24.102] ([10.21.87.71]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 13:03:01 -0700
Message-Id: <CCCF29E2-82E8-4EC9-806F-8E15D9A20324@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Alain Durand <alain_durand@cable.comcast.com>
In-Reply-To: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 13:02:58 -0700
References: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 03 Oct 2008 20:03:02.0220 (UTC)
	FILETIME=[0A6E70C0:01C92593]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2047; t=1223064182;
	x=1223928182; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20; bh=oNO9UIxYvTVkRDvk1y5zT2VvNKdM+3jYtqlmVKSYKVc=;
	b=fSxk5xG2AOPqavDXpmSUWCwQAuVPfB8G25rfyVzyP29b3g8KrVM2iA+isF
	fW0En/A8El5ioKVj1872Gbb8jjYkCFfG2S0JjYJ9EcAL/utmU8Jz+czW8CgG
	mcpjt3291Q;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I'm OK with that if you are.

On Oct 3, 2008, at 8:04 AM, Alain Durand wrote:

> Our Ads have re-chartered the Softwire wg to address the tunneling +  
> nat44
> case, so it is unclear to me why we would need a bof in that  
> particular
> space when the working group will be meeting in Minneapolis.
>
>  - Alain.
>
>
> On 10/3/08 10:47 AM, "Ed Jankiewicz" <edward.jankiewicz@sri.com>  
> wrote:
>
>> I am most interested in translation solutions and support some  
>> "divide
>> and conquer" but will try to follow all the discussions.  Given the  
>> high
>> degree of overlap in interest, we need to make sure the BOFs are
>> scheduled for Minneapolis so that all can attend either or both.   
>> Also
>> avoid obvious conflicts with v6ops, 6man, etc.
>>
>> Fred Baker wrote:
>>> So various folks are going to be doing a lot of work in email and  
>>> such
>>> in the next few weeks. May I suggest that the ADs schedule a BOF for
>>> the translation solution and one for the tunneling solution (and one
>>> for the 4-4-4 solution?) separate from WGs, to enable the doc  
>>> authors
>>> to sit down together and discuss?
>>>
>>> I would also suggest that you set of mailing lists for these BOFs,
>>> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them
>>> to this forum and let people sign up the usual way.
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>
>>
>> --
>> Ed Jankiewicz - SRI International
>> Fort Monmouth Branch Office - IPv6 Research
>> Supporting DISA Standards Engineering Branch
>> 732-389-1003 or  ed.jankiewicz@sri.com
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 16:19:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DACC3A6968;
	Fri,  3 Oct 2008 16:19:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E3913A6968
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 16:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nJLdpLRdj1EL for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 16:18:58 -0700 (PDT)
Received: from ocean.net.edu.cn (ocean.net.edu.cn [202.112.0.56])
	by core3.amsl.com (Postfix) with ESMTP id 2D3333A68EF
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 16:18:57 -0700 (PDT)
Received: from [127.0.0.1] (ocean.net.edu.cn [202.112.0.56])
	by ocean.net.edu.cn  with ESMTP id m93NJBcj015503;
	Sat, 4 Oct 2008 07:19:12 +0800 (CST)
Message-ID: <48E6A86E.30308@cernet.edu.cn>
Date: Sat, 04 Oct 2008 07:19:10 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
In-Reply-To: <48E63077.5070907@free.fr>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

UsOpbWkgRGVzcHLDqXMg5YaZ6YGTOgo+IE1hcmMgQmxhbmNoZXQgICAobS9qL2EpIDEwLzMvMDgg
MzoxNSBQTToKPj4gUu+/vW1pIERlc3By77+9cyBhIO+/vWNyaXQgOgo+Pj4gSSBzdXBwb3J0IEZy
ZWQncyBzdWdnZXN0aW9uIG9mIHNlcGFyYXRpbmcgZGlzY3Vzc2lvbiBzcGFjZXMgZm9yIHdoYXQg
aXMKPj4+IHNwZWNpZmljIHRvIHR1bm5lbGluZyBhbmQgd2hhdCBpcyBzcGVjaWZpYyB0byB0cmFu
c2xhdGlvbi4KPj4+Cj4+PiBJbiBteSB1bmRlcnN0YW5kaW5nOgo+Pj4gLSBOQVQ2NCwgTkFUNDYs
IGFuZCB3aGF0IGNvbmNlcm5zIElTUCBpbmZyYXN0cnVjdHVyZSBOQVRzIChDR05zKSBidXQgCj4+
PiBub3QKPj4+IENQRSBOQVRzLCB3b3VsZCBiZSBpbiB2NHY2LXhsYXQKPj4+IC0gQStQLCBJVkks
IFNBTSwgYW5kIHR1bm5lbGluZyBhc3BlY3RzIG9mIERTIGxpdGUgIHdvdWxkIGJlIGluIAo+Pj4g
djR2Ni1YbGF0Cj4+Cj4+IHMvdjR2Ni14bGF0L3Y0djYtdHVubmVsLyAgcmlnaHQ/CklWSSBzaG91
bGQgYmUgaW4gdjR2Ni14bGF0IGNhdC4geGluZwoKPiBSaWdodCAoT29wcyEpCj4KPiBSRAo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gdjR2NmludGVy
aW0gbWFpbGluZyBsaXN0Cj4gdjR2NmludGVyaW1AaWV0Zi5vcmcKPiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y0djZpbnRlcmltCgpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXwp2NHY2aW50ZXJpbSBtYWlsaW5nIGxpc3QKdjR2Nmlu
dGVyaW1AaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2
aW50ZXJpbQo=


From v4v6interim-bounces@ietf.org  Fri Oct  3 16:45:44 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 707D43A695E;
	Fri,  3 Oct 2008 16:45:44 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F0F03A68D1
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 16:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ugMWxNgBW6Ok for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 16:45:42 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175])
	by core3.amsl.com (Postfix) with ESMTP id 50F4F3A695E
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 16:45:42 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1935812wfd.31
	for <v4v6interim@ietf.org>; Fri, 03 Oct 2008 16:46:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=b1kio26emTXxc4qRH5V74oEl4TJ+Xuj33Kyx2RGnL9o=;
	b=k7TTlS2m6JWTKk2CBZeYmPyaCwqCh4FRSJqk81liQ85QGmLzIF8rsew00uefMl2Aja
	Z/Na4JROn5CXIpKlZKqD+tjFok1jY1yygk50WPsktWWhjlO9YnhMaFNH2TktB5liPFH4
	JXGZcVbpCHBfJqqRTPZNmtdIc60/ZznCFMCUQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=MxhdW5Ny/l9hd9Hkx8rNKxEtfVMT/OkW4tajsyyUVFtmx3s28A97OUOiRUG9/pek9a
	lPKWgzU7JVIBjjPVW98xxCy4bsDnZMvwqduc84Bo8gBieImbYPNQGqTPLVXvBnniIWWs
	BGeVk+TJVsfhKd0KwWnSQQyvjgHY2d3tgBYng=
Received: by 10.142.194.1 with SMTP id r1mr592365wff.192.1223077571601;
	Fri, 03 Oct 2008 16:46:11 -0700 (PDT)
Received: from ?10.1.1.4? (118-93-8-5.dsl.dyn.ihug.co.nz [118.93.8.5])
	by mx.google.com with ESMTPS id 30sm5749675wfd.1.2008.10.03.16.46.09
	(version=SSLv3 cipher=RC4-MD5); Fri, 03 Oct 2008 16:46:11 -0700 (PDT)
Message-ID: <48E6AEBD.9090205@gmail.com>
Date: Sat, 04 Oct 2008 12:46:05 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hiroshi MIYATA <miyata@tahi.org>
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
	<D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org>
In-Reply-To: <D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Actually the *correct* solution is to use a method of
PMTU discovery that does not depend on ICMP.
That's the point of RFC 4821.

  Brian

On 2008-10-04 08:51, Hiroshi MIYATA wrote:
> Correct!
> 
> We have met the problem, and, yes, only the way is fragmenting
> the packet on the Translator.
> We have developed it as a optional behavior.
> 
> It may cause the argument if we state it in document, since
> it break the PMTU Discovery semantics.
> 
> But it is the fact.
> 
> Maybe it is not recommended to describe on BEHAVE documents
> as a requirement.
> But we should give the hint of this issue on the documents
> as possible problems and solution and utilization (since
> it is not recommended to use this in public service, but
> possible to be used for controllable area of the administrator.)
> 
> Regards,
> 
> ....miyata
> 
> 
> On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote:
> 
>> Some SP's may view ICMP as an attack vector and may explicitly block
>> ICMP messages.
>>
>> In this case, the only way to get connectivity for packets that are too
>> large is to fragment.
>>
>> - Wes
>>
>> -----Original Message-----
>> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
>> On Behalf Of Hiroshi MIYATA
>> Sent: Friday, October 03, 2008 5:31 AM
>> To: v4v6interim@ietf.org
>> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
>>
>> Jennings,
>>
>>
>> FYI.
>> Though it is already clearly explained by Dave, let me give you the
>> pointer.
>> The answer for your question of "Fragmentation options" is clearly
>> stated in RFC2765(SIIT) as end-to-end path MTU discovery.
>> See Section 3 and 4.
>>
>> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
>>       Note: A node may receive a Packet Too Big message reporting a
>>       next-hop MTU that is less than the IPv6 minimum link MTU.  In
>> that
>>       case, the node is not required to reduce the size of subsequent
>>       packets sent on the path to less than the IPv6 minimun link MTU,
>>       but rather must include a Fragment header in those packets [IPv6-
>>       SPEC].
>>
>> It must work well. ;-)
>>
>> Regards,
>>
>> ....miyata
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 17:23:54 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26D0D3A69AA;
	Fri,  3 Oct 2008 17:23:54 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C9083A6976
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 17:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C93bd+LsYNs5 for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 17:23:51 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 564543A69AE
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 17:23:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,359,1220227200"; d="scan'208";a="23167782"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 04 Oct 2008 00:24:18 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m940OIlP016539
	for <v4v6interim@ietf.org>; Fri, 3 Oct 2008 20:24:18 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m940OI2m003115
	for <v4v6interim@ietf.org>; Sat, 4 Oct 2008 00:24:18 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 20:22:15 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 20:22:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E423B2@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <BEBD49E2-53FA-46A9-BAAD-063753DE078A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] BOF discussions
Thread-Index: Acklkvar1Jux+L1ASzq7kzElla0HmQAI2niA
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>
	<BEBD49E2-53FA-46A9-BAAD-063753DE078A@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-OriginalArrivalTime: 04 Oct 2008 00:22:15.0504 (UTC)
	FILETIME=[40E93D00:01C925B7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2758; t=1223079858;
	x=1223943858; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com> |Subject:=20RE=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20
	|To:=20=22Fred=20Baker=20(fred)=22=20<fred@cisco.com>;
	bh=F8CwzffMp4jOyMaXlRvhO7jQ9FLxu9co8A3GK1IM+BI=;
	b=TiNdskTqd9rKmGOSSVlJW3X3t+DepM/h0TB0di3RWgoV36X3wX46qo2kzc
	CtORtqtEYJH/Gx/Izr0JCxC6xsYau98Ms0KUWIj05Up66VcSX6nXHqNcL4qA
	JrW/BXf0Px;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred,

I hear ya.  Maybe BOF was a wrong choice of words since it took people
in the direction of thinking we didn't have a WG on this one.  The
interim meeting was so much more productive compared to discussing this
lot in a few hours at IETF Dublin in a few WG's when at any IETF, any WG
is competing with tons of other WG's that folks would like to go to as
well. 

Soon as we focused folks into one WG and no other distractions, we did
move forward in the interim meeting rather than staying in limbo at IETF
meetings.  That is why I do like your idea of few right folks getting
together at next IETF to hash more things out and BOF is indeed the
right term for such a getting together.  By all means, let the
v4v6coexistence WG do its session(s) at the next IETF, but I do think
more work will be needed in more focused smaller groups outside of the
WG session(s).

Hemant

-----Original Message-----
From: Fred Baker (fred) 
Sent: Friday, October 03, 2008 4:02 PM
To: Hemant Singh (shemant)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions

What I'm suggesting is that the folks that need to discuss translation
- perhaps 15 of us total - sit down and talk about it, and the same
opportunity be available to the tunneling folks. My point is to foment
accomplishment; as Randy says, he needs this yesterday. I have no
problem with other discussions happening too and expect still to have a
requirements discussion in v6ops.

On Oct 2, 2008, at 3:19 PM, Hemant Singh (shemant) wrote:

> Fred,
>
> Good suggestion.  However, what if a BOF is needed to discuss a 
> solution where both xlat and tunnel are needed?  Do we discuss those 
> in this WG mailer or spawn a 3rd new BOF mailer?
>
> Thanks.
>
> Hemant
>
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org 
> [mailto:v4v6interim-bounces@ietf.org
> ]
> On Behalf Of Fred Baker (fred)
> Sent: Thursday, October 02, 2008 5:14 PM
> To: v4v6interim@ietf.org
> Subject: [v4v6interim] BOF discussions
>
> So various folks are going to be doing a lot of work in email and such

> in the next few weeks. May I suggest that the ADs schedule a BOF for 
> the translation solution and one for the tunneling solution (and one 
> for the
> 4-4-4 solution?) separate from WGs, to enable the doc authors to sit 
> down together and discuss?
>
> I would also suggest that you set of mailing lists for these BOFs, 
> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them 
> to this forum and let people sign up the usual way.
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct  3 21:47:26 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B45B93A692C;
	Fri,  3 Oct 2008 21:47:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C86D3A6857
	for <v4v6interim@core3.amsl.com>; Fri,  3 Oct 2008 21:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.581
X-Spam-Level: 
X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4ccsaR5aEETz for <v4v6interim@core3.amsl.com>;
	Fri,  3 Oct 2008 21:47:23 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 4D5433A6891
	for <v4v6interim@ietf.org>; Fri,  3 Oct 2008 21:46:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,359,1220227200"; d="scan'208";a="21608299"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 04 Oct 2008 04:47:09 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m944l9XH017658
	for <v4v6interim@ietf.org>; Sat, 4 Oct 2008 06:47:09 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m944l9Lm004858
	for <v4v6interim@ietf.org>; Sat, 4 Oct 2008 04:47:09 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 4 Oct 2008 06:47:09 +0200
Received: from Townsley-MacBook.local ([10.61.90.35]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 4 Oct 2008 06:47:08 +0200
Message-ID: <48E6F503.8070700@cisco.com>
Date: Sat, 04 Oct 2008 06:45:55 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: v4v6interim@ietf.org
X-OriginalArrivalTime: 04 Oct 2008 04:47:08.0594 (UTC)
	FILETIME=[41EE5120:01C925DC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2094; t=1223095629;
	x=1223959629; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Interim=20meeting=20outcome |Sender:=20;
	bh=eyg3sjl0p0qiJtkiYvFYBYaCSLDmg0uiygmzQWh1xe8=;
	b=L+k4kjAD/gYfyKazWgCz/o8JXAs2uTzHvODuIKMc8zr1Mf8sdYWZY1Ms6c
	g6cZgMJSVfInK8ftnifumlJ4phkov2tf6fLVb/qgYSXMbb3AjMbhrAJZnnHs
	Jhw9dKPW+P;
Authentication-Results: ams-dkim-2; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: [v4v6interim] Interim meeting outcome
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


I am very happy with the outcome of this meeting.  We had a lot of
participants, a lot of interaction, and in the end a crystallization of
the problem space and progress on the solution space. While some open
issues remain, I believe we achieved our goals for the meeting. Thanks
to everyone for this.

As has been noted, there are two broad categories of solution spaces.

The first has two aspects: Overloading IPv4 addresses in the face of
address exhaustion (NATs, Fractional Addressing), and Tunneling (presumably
over IPv6). The second broad category of solution space has essentially four 
iterations of translation topologies, each focusing the problem space down from 
the less tractable goal of bidirectional translation between all of IPv4 and all 
of IPv6. Presented like this, I saw wide support for solving these problems, and
solutions on the table for solving each (with great potential for common 
components as well). I am much happier with this kind of strong support (either 
for *or* against) vs. the more split opinion I was seeing walking into the meeting.

When considering when to use translation between IPv4 and IPv6, I learned that
it is critical to include the capability of applications, the OS, and the 
network in the analysis. When the network is mis-matched end-to-end, tunneling 
options can come into play. When the applications or OS are mismatched 
end-to-end, translation options come into play. While we have identified some 
overlap at the edges of these two problems spaces such that tunnels or 
translators could apply, we should be able to articulate the tradeoffs between 
the two in due course.

After this meeting, I firmly believe that the IETF is ready to embark on
this work, and that at least the participants in the meeting are headed
in the same general direction. My recommendation to the IAB and IESG
will be to charter the work in this area right away, and to the
community to get to work on hammering out the solutions.

Thanks again for a productive two days, see you again in Minneapolis.

- Mark











_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct  4 00:48:41 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA92D3A6861;
	Sat,  4 Oct 2008 00:48:41 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5462D3A6861
	for <v4v6interim@core3.amsl.com>; Sat,  4 Oct 2008 00:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YHUJCxjkS-41 for <v4v6interim@core3.amsl.com>;
	Sat,  4 Oct 2008 00:48:40 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 6B3EA3A6849
	for <v4v6interim@ietf.org>; Sat,  4 Oct 2008 00:48:40 -0700 (PDT)
Received: from [10.0.1.3] (82-192-90-29.leasedsl.net [82.192.90.29] (may be
	forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m947meKN028377
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 4 Oct 2008 09:48:56 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <DD0672C2-CFE2-4806-BF24-67A3F81D9283@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 4 Oct 2008 00:37:37 +0200
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2 okt 2008, at 23:13, Fred Baker wrote:

> So various folks are going to be doing a lot of work in email and  
> such in the next few weeks. May I suggest that the ADs schedule a  
> BOF for the translation solution and one for the tunneling solution

Disagree. Like I've been saying for some time now: there is no  
semantic difference between the NAT64&co translation and DS-lite  
translation, only a syntactic difference. There should only be a  
single translation spec that covers both. So discussing the two  
solutions in separate places is likely to be suboptimal. Or make it  
three lists: translation issues / NAT64-specific issues / DS-lite  
specific issues.

> I would also suggest that you set of mailing lists for these BOFs,  
> perhaps called v4v6-xlat and v4v6-tunnel or some such. Announce them  
> to this forum and let people sign up the usual way.

subscribe *

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct  4 00:48:50 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D37C3A69D0;
	Sat,  4 Oct 2008 00:48:50 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E6123A69D0
	for <v4v6interim@core3.amsl.com>; Sat,  4 Oct 2008 00:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u7tQ+zuFyzLU for <v4v6interim@core3.amsl.com>;
	Sat,  4 Oct 2008 00:48:48 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 24B5A3A6849
	for <v4v6interim@ietf.org>; Sat,  4 Oct 2008 00:48:47 -0700 (PDT)
Received: from [10.0.1.3] (82-192-90-29.leasedsl.net [82.192.90.29] (may be
	forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m947meKK028377
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 4 Oct 2008 09:48:42 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 4 Oct 2008 00:17:38 +0200
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2 okt 2008, at 19:31, Fred Baker wrote:

>> Dumb question from personal ignorance. SMTP opens with a HELO or  
>> EHLO that has the IP address of the MTA in it.

[...]

> That either calls for an ALG or appropriate code in the servers that  
> can deal with an <> address even when the server doesn't have such  
> an address. The simplest resolution might be to have the MTA have a  
> leg in the IPv6 world and one in the IPv4 world.

Right. I don't think we should create trouble where none exists in  
practice. Running an SMTP server behind a translator is not a good  
idea; using a dual stack SMTP server as a forwarder makes much more  
sense.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct  4 01:57:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 467CA3A69FC;
	Sat,  4 Oct 2008 01:57:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFCAA3A69FC
	for <v4v6interim@core3.amsl.com>; Sat,  4 Oct 2008 01:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MTEoXh92ymCR for <v4v6interim@core3.amsl.com>;
	Sat,  4 Oct 2008 01:57:54 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16])
	by core3.amsl.com (Postfix) with ESMTP id A17F83A690E
	for <v4v6interim@ietf.org>; Sat,  4 Oct 2008 01:57:54 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3])
	by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m948uuKS044598;
	Sat, 4 Oct 2008 17:56:56 +0900 (JST) (envelope-from miyata@tahi.org)
Received: from [127.0.0.1] (fumi.64translator.com [10.21.254.6])
	by bahamas.64translator.com (8.13.6/8.13.6) with ESMTP id
	m948ubAL080852; Sat, 4 Oct 2008 17:56:38 +0900 (JST)
	(envelope-from miyata@tahi.org)
Message-Id: <ECC150A9-5846-40D7-83EE-669F3B21E050@tahi.org>
From: Hiroshi MIYATA <miyata@tahi.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <48E6AEBD.9090205@gmail.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Sat, 4 Oct 2008 17:56:35 +0900
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
	<D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org>
	<48E6AEBD.9090205@gmail.com>
X-Mailer: Apple Mail (2.928.1)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Brian,

Thanks for your input.
I will investigate it!

Cheers!

...miyata

On 2008/10/04, at 8:46, Brian E Carpenter wrote:

> Actually the *correct* solution is to use a method of
> PMTU discovery that does not depend on ICMP.
> That's the point of RFC 4821.
>
>  Brian
>
> On 2008-10-04 08:51, Hiroshi MIYATA wrote:
>> Correct!
>>
>> We have met the problem, and, yes, only the way is fragmenting
>> the packet on the Translator.
>> We have developed it as a optional behavior.
>>
>> It may cause the argument if we state it in document, since
>> it break the PMTU Discovery semantics.
>>
>> But it is the fact.
>>
>> Maybe it is not recommended to describe on BEHAVE documents
>> as a requirement.
>> But we should give the hint of this issue on the documents
>> as possible problems and solution and utilization (since
>> it is not recommended to use this in public service, but
>> possible to be used for controllable area of the administrator.)
>>
>> Regards,
>>
>> ....miyata
>>
>>
>> On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote:
>>
>>> Some SP's may view ICMP as an attack vector and may explicitly block
>>> ICMP messages.
>>>
>>> In this case, the only way to get connectivity for packets that  
>>> are too
>>> large is to fragment.
>>>
>>> - Wes
>>>
>>> -----Original Message-----
>>> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org 
>>> ]
>>> On Behalf Of Hiroshi MIYATA
>>> Sent: Friday, October 03, 2008 5:31 AM
>>> To: v4v6interim@ietf.org
>>> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
>>>
>>> Jennings,
>>>
>>>
>>> FYI.
>>> Though it is already clearly explained by Dave, let me give you the
>>> pointer.
>>> The answer for your question of "Fragmentation options" is clearly
>>> stated in RFC2765(SIIT) as end-to-end path MTU discovery.
>>> See Section 3 and 4.
>>>
>>> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
>>>      Note: A node may receive a Packet Too Big message reporting a
>>>      next-hop MTU that is less than the IPv6 minimum link MTU.  In
>>> that
>>>      case, the node is not required to reduce the size of subsequent
>>>      packets sent on the path to less than the IPv6 minimun link  
>>> MTU,
>>>      but rather must include a Fragment header in those packets  
>>> [IPv6-
>>>      SPEC].
>>>
>>> It must work well. ;-)
>>>
>>> Regards,
>>>
>>> ....miyata
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct  4 13:36:55 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E4DA3A67B3;
	Sat,  4 Oct 2008 13:36:55 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6852A3A677D
	for <v4v6interim@core3.amsl.com>; Sat,  4 Oct 2008 13:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.515
X-Spam-Level: 
X-Spam-Status: No, score=-106.515 tagged_above=-999 required=5
	tests=[AWL=0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7exWOs-dIi1P for <v4v6interim@core3.amsl.com>;
	Sat,  4 Oct 2008 13:36:52 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id A75F03A6405
	for <v4v6interim@ietf.org>; Sat,  4 Oct 2008 13:36:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,361,1220227200"; d="scan'208";a="168836766"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 04 Oct 2008 20:37:25 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m94KbORp001228; 
	Sat, 4 Oct 2008 13:37:24 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m94KbOI9003100;
	Sat, 4 Oct 2008 20:37:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 4 Oct 2008 13:37:24 -0700
Received: from stealth-10-32-244-220.cisco.com ([10.32.244.220]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 4 Oct 2008 13:37:24 -0700
Message-Id: <74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 4 Oct 2008 13:37:22 -0700
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
	<4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 04 Oct 2008 20:37:24.0100 (UTC)
	FILETIME=[01D21C40:01C92661]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=357; t=1223152644; x=1224016644;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Potential=20interoperab
	ility=20issue |Sender:=20;
	bh=UE/rmfyKXLV5mHwPk+pZ1DH2BXpqorbIcldOQHhrOUI=;
	b=AYc6ziua0UD6GRMa2kgZwDFY/6YDbAbQ8T3nQcNvMblBgSbMnBCWgwaAG0
	Pc6ngTCzkiltRjwnUdvuQ6s/IWgO5XDSO1mL72dVSXD7KObwdHTqX2VK0rPO
	lT3aEAptox;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 3, 2008, at 3:17 PM, Iljitsch van Beijnum wrote:

> using a dual stack SMTP server as a forwarder makes much more sense.

Gee, you make it sound as if I were arguing against dual stack. I'm  
merely noting that dual stack isn't being deployed at the rate one  
would hope for and that my customers are looking for a translation  
solution.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 00:15:35 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0A7228C1CE;
	Mon,  6 Oct 2008 00:15:35 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D440728C1B1
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 00:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.518
X-Spam-Level: 
X-Spam-Status: No, score=-107.518 tagged_above=-999 required=5
	tests=[AWL=1.081, BAYES_00=-2.599, GB_I_INVITATION=-2,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oAvQgCpf0Lvs for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 00:15:33 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 82ABC28C0EA
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 00:15:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,366,1220227200"; d="scan'208";a="87092758"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 06 Oct 2008 07:16:00 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m967G0n0029062
	for <v4v6interim@ietf.org>; Mon, 6 Oct 2008 00:16:00 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m967G00J011944
	for <v4v6interim@ietf.org>; Mon, 6 Oct 2008 07:16:00 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 00:16:00 -0700
Received: from stealth-10-32-244-219.cisco.com ([10.32.244.219]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 00:16:00 -0700
Message-Id: <38AB391A-FA7A-487F-91CC-BADA10B7A078@cisco.com>
From: Fred Baker <fred@cisco.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 00:15:59 -0700
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 06 Oct 2008 07:16:00.0152 (UTC)
	FILETIME=[62616980:01C92783]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=341; t=1223277360; x=1224141360;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Translation=20discussion |Sender:=20;
	bh=9eFYdqtx5/Q9GyybdcYfiVDbDW0hzhhoaUxMrRiJPm8=;
	b=Bvy/W/6rDVCCEumsrWtYgFRYDtNLBApDq2sPIVJ8iN/jRKPpUGoij4CQjS
	V1WyqEVH5JX7JZTpw/lPZOWywOxXpazzGTddqHhwHph+2XkhWHtdBw6lTxfu
	pD4lvUacyakfa+As5CIcynRpfKAo4N4bZtYPiZTO/f+LN9RGc0CR8=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: [v4v6interim] Translation discussion
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Dan Wing made a list for us, and I (using mailman's "invitation" tool)  
have invited a number of folks to join; I believe that I invited all  
who said they were interested.

In any event, if you would like to join but didn't see an invitation,  
please go to

https://www.employees.org/mailman/listinfo/46translation

and do so.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 01:35:52 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A59B3A6831;
	Mon,  6 Oct 2008 01:35:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B81403A67C1
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 01:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level: 
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.535, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vyFTs+srLILx for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 01:35:50 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id BB59F3A692F
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 01:35:49 -0700 (PDT)
Received: from nirrti.muada.com (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m968ZotJ072217
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 6 Oct 2008 10:35:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <AB3F6653-44B6-4C58-858B-04D3DCBD4F12@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 10:36:00 +0200
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
	<4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
	<74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 4 okt 2008, at 22:37, Fred Baker wrote:

>> using a dual stack SMTP server as a forwarder makes much more sense.

> Gee, you make it sound as if I were arguing against dual stack. I'm  
> merely noting that dual stack isn't being deployed at the rate one  
> would hope for and that my customers are looking for a translation  
> solution.

The thing that we have to make explicit is that it's necessary to  
deploy the right solution to a given problem, one size never fits all.

Dual stack is not a good solution for clients for two reasons: it  
requires running both IP versions throughout a network, which  
increases cost and complexity, and it uses up just as many addresses  
as just running IPv4.

But for servers, dual stack is the best possible solution, because  
it's way simpler than the alternatives as receiving incoming sessions  
through translation is a big hurdle and the address use and network  
complexity aren't as bad because the number of servers and presumably,  
the number of places they're present are limited.

In the case of SMTP it's also easy to simply put a dual stack server  
in the path if you have an IPv6 server.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 03:56:15 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 466283A6AAB;
	Mon,  6 Oct 2008 03:56:15 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CE863A67AC
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 03:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vieI-eEwhqDv for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 03:56:13 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id 487F73A6AAB
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 03:56:13 -0700 (PDT)
Received: from zrtphxm1.corp.nortel.com (zrtphxm1.corp.nortel.com
	[47.140.202.50])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m96ArcZ24363; Mon, 6 Oct 2008 10:53:38 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 06:56:10 -0400
Message-ID: <4B7DAC3FEFD35D4A96BDD011699050141B571910@zrtphxm1.corp.nortel.com>
In-Reply-To: <AB3F6653-44B6-4C58-858B-04D3DCBD4F12@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Potential interoperability issue
Thread-Index: AcknjqJA6wKZEFsnQpu84DOI4igStgAEt5Mg
References: <E0F13238-A5C2-4BEE-BE28-7FFCFEFB3FDC@cisco.com>
	<4E6509A8-CE7E-4807-ABC3-C5A705676B7C@muada.com>
	<74408D36-502A-439F-A097-8569C4B8DE06@cisco.com>
	<AB3F6653-44B6-4C58-858B-04D3DCBD4F12@muada.com>
From: "Ed Koehler Jr" <ekoehler@nortel.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>, "Fred Baker" <fred@cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

IMHO, any server based application should first be approached by dual
stack in the server if at all possible. Only then should one look to
alternatives. I have been running this way in my lab for a number of
years, there are very few server based scenarios where this does not
work. 

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Iljitsch van Beijnum
Sent: Monday, October 06, 2008 4:36 AM
To: Fred Baker
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Potential interoperability issue

On 4 okt 2008, at 22:37, Fred Baker wrote:

>> using a dual stack SMTP server as a forwarder makes much more sense.

> Gee, you make it sound as if I were arguing against dual stack. I'm 
> merely noting that dual stack isn't being deployed at the rate one 
> would hope for and that my customers are looking for a translation 
> solution.

The thing that we have to make explicit is that it's necessary to deploy
the right solution to a given problem, one size never fits all.

Dual stack is not a good solution for clients for two reasons: it
requires running both IP versions throughout a network, which increases
cost and complexity, and it uses up just as many addresses as just
running IPv4.

But for servers, dual stack is the best possible solution, because it's
way simpler than the alternatives as receiving incoming sessions through
translation is a big hurdle and the address use and network complexity
aren't as bad because the number of servers and presumably, the number
of places they're present are limited.

In the case of SMTP it's also easy to simply put a dual stack server in
the path if you have an IPv6 server.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 07:46:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C26913A6AD0;
	Mon,  6 Oct 2008 07:45:59 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2882E3A6ACF
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 07:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[AWL=0.288, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RsVWxW4l+egy for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 07:45:57 -0700 (PDT)
Received: from smtp7-g19.free.fr (smtp7-g19.free.fr [212.27.42.64])
	by core3.amsl.com (Postfix) with ESMTP id 01B4E3A6AD3
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 07:45:56 -0700 (PDT)
Received: from smtp7-g19.free.fr (localhost [127.0.0.1])
	by smtp7-g19.free.fr (Postfix) with ESMTP id D4901B01C5;
	Mon,  6 Oct 2008 16:46:27 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp7-g19.free.fr (Postfix) with ESMTP id F007EB01CE;
	Mon,  6 Oct 2008 16:46:22 +0200 (CEST)
Message-ID: <48EA246E.6040203@free.fr>
Date: Mon, 06 Oct 2008 16:45:02 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn>
In-Reply-To: <48E6A86E.30308@cernet.edu.cn>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

WGluZyBMaSAgIChtL2ovYSkgMTAvNC8wOCAxOjE5IEFNOgo+IFLDqW1pIERlc3Byw6lzIOWGmemB
kzoKPj4gTWFyYyBCbGFuY2hldCAgIChtL2ovYSkgMTAvMy8wOCAzOjE1IFBNOgo+Pj4gUu+/vW1p
IERlc3By77+9cyBhIO+/vWNyaXQgOgo+Pj4+IEkgc3VwcG9ydCBGcmVkJ3Mgc3VnZ2VzdGlvbiBv
ZiBzZXBhcmF0aW5nIGRpc2N1c3Npb24gc3BhY2VzIGZvciB3aGF0IGlzCj4+Pj4gc3BlY2lmaWMg
dG8gdHVubmVsaW5nIGFuZCB3aGF0IGlzIHNwZWNpZmljIHRvIHRyYW5zbGF0aW9uLgo+Pj4+Cj4+
Pj4gSW4gbXkgdW5kZXJzdGFuZGluZzoKPj4+PiAtIE5BVDY0LCBOQVQ0NiwgYW5kIHdoYXQgY29u
Y2VybnMgSVNQIGluZnJhc3RydWN0dXJlIE5BVHMgKENHTnMpIGJ1dCAKPj4+PiBub3QKPj4+PiBD
UEUgTkFUcywgd291bGQgYmUgaW4gdjR2Ni14bGF0Cj4+Pj4gLSBBK1AsIElWSSwgU0FNLCBhbmQg
dHVubmVsaW5nIGFzcGVjdHMgb2YgRFMgbGl0ZSAgd291bGQgYmUgaW4gCj4+Pj4gdjR2Ni1YbGF0
Cj4+Pgo+Pj4gcy92NHY2LXhsYXQvdjR2Ni10dW5uZWwvICByaWdodD8KPiBJVkkgc2hvdWxkIGJl
IGluIHY0djYteGxhdCBjYXQuIHhpbmcKClJpZ2h0OiBJVkkgaXMgaW5kZWVkIGEgdHJhbnNsYXRp
b24gc29sdXRpb24uCkFwb2xvZ2llcyBmb3IgdGhlIG1pc3Rha2UuCgpJbiBteSB1bmRlcnN0YW5k
aW5nLCAgaXMgb25seSBpZiBpdCBpcyBleHRlbmRlZCB0byBzdXBwb3J0IElQdjQKb3ZlciBJUHY2
LCBhbmQgYWxzbyBwb3J0IG11bHRpcGxleGluZyAocmVzcGVjdGl2ZWx5IHNlY3Rpb25zIDQuOCBh
bmQgNi4yIApvZiB5b3VyIGRyYWZ0LXhsaS1iZWhhdmUtaXZpLTAwKSB0aGF0IGNvbW1vbmFsaXR5
IHdpdGggYSB0dW5uZWxpbmcgCmFwcHJvYWNoIGxpa2UgU0FNIGlzIGxpa2VseSB0byBiZSBzaWdu
aWZpY2FudC4KCkJlc3QgcmVnYXJkcy4KClJECgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXwp2NHY2aW50ZXJpbSBtYWlsaW5nIGxpc3QKdjR2NmludGVyaW1A
aWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2aW50ZXJp
bQo=


From v4v6interim-bounces@ietf.org  Mon Oct  6 08:24:22 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 40E623A6A65;
	Mon,  6 Oct 2008 08:24:22 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7582E3A68DF
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 08:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.408
X-Spam-Level: 
X-Spam-Status: No, score=-106.408 tagged_above=-999 required=5
	tests=[AWL=-0.109, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MSc-msxsaKoO for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 08:24:16 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id BD6C83A6A65
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 08:24:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,368,1220227200"; d="scan'208";a="169664125"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 06 Oct 2008 15:24:50 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m96FOojp009336; 
	Mon, 6 Oct 2008 08:24:50 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m96FOo14006222;
	Mon, 6 Oct 2008 15:24:50 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:24:50 -0700
Received: from stealth-10-32-244-219.cisco.com ([10.32.244.219]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:24:49 -0700
Message-Id: <27E6F7E7-813C-43D7-85AA-24243B653921@cisco.com>
From: Fred Baker <fred@cisco.com>
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <48EA246E.6040203@free.fr>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 08:24:46 -0700
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn> <48EA246E.6040203@free.fr>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 06 Oct 2008 15:24:49.0814 (UTC)
	FILETIME=[AC38AB60:01C927C7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=369; t=1223306690; x=1224170690;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20BOF=20discussions
	|Sender:=20; bh=vO4spmGVLGq8LdMRxEtp7Qz3UYULeH9YoC5W1wyDBKE=;
	b=EHMEtOxkjrKYVf3jtpPMsGZ2fJfDvxvhrfMqr3IZGpj5iGBOb25Gmxasuq
	syC8Uj6kqHmMxI3WetkbsVu6A3Mer7scf3+M+V/ouyxYhkMQx7JFtQnkhAsz
	yl43wjho2X;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 6, 2008, at 7:45 AM, R=E9mi Despr=E9s wrote:

> In my understanding,  is only if it is extended to support IPv4
> over IPv6, and also port multiplexing (respectively sections 4.8 and  =

> 6.2 of your draft-xli-behave-ivi-00) that commonality with a  =

> tunneling approach like SAM is likely to be significant.

?

There is no "over" in IVI...
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 09:16:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E231528C1FF;
	Mon,  6 Oct 2008 09:16:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5961D28C1FF
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 09:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level: 
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[AWL=0.256, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eK1iXqR6hUHV for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 09:16:00 -0700 (PDT)
Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65])
	by core3.amsl.com (Postfix) with ESMTP id B91C928C1F7
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 09:15:59 -0700 (PDT)
Received: from smtp8-g19.free.fr (localhost [127.0.0.1])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 8B66E32AACB;
	Mon,  6 Oct 2008 18:16:35 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 03A2732AAE0;
	Mon,  6 Oct 2008 18:16:33 +0200 (CEST)
Message-ID: <48EA3992.4090807@free.fr>
Date: Mon, 06 Oct 2008 18:15:14 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
References: <C50BACB2.1B5EF%alain_durand@cable.comcast.com>
	<48E645D9.9050505@free.fr>
	<BB56240F3A190F469C52A57138047A03011DB146@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03011DB146@xmb-rtp-211.amer.cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

QWxhaW4sIGlzIHJpZ2h0IHRvIHN1cHBvc2UgdGhhdCB0aGUgU29mdHdpcmUgY2hhcnRlciBoYXMg
YmVlbiByZXZpc2VkIApBRlRFUiBNb250cmVhbD8KCi0gSWYgbm90LCBvdGhlciBnb2FscyBhbmQg
bWlsZXN0b25lcyB0aGFuICJTdWJtaXQgc29mdHdpcmVzIE1JQiB0byB0aGUgCklFU0ciIHdvdWxk
IGNsZWFybHkgYmUgbWlzc2luZy4pCgotIElmIHllcywgdGhlIHF1ZXN0aW9uIHJlbWFpbnM6IGNh
biB3ZSBzZWUgdGhlIHJldmlzZWQgY2hhcnRlciB5b3Ugc2VlbSAKdG8ga25vdywgZXZlbiBpbiBw
cm92aXNpb25hbCBmb3JtPwoKUkQKCgpXZXMgQmVlYmVlICh3YmVlYmVlKSAgIChtL2ovYSkgMTAv
My8wOCA2OjI1IFBNOgo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9zb2Z0
d2lyZXMvY3VycmVudC9tc2cwMDY4Ny5odG1sCj4gCj4gLSBXZXMgCj4gCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0KPiBGcm9tOiB2NHY2aW50ZXJpbS1ib3VuY2VzQGlldGYub3JnIFttYWls
dG86djR2NmludGVyaW0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFLDqW1pIERlc3By
w6lzCj4gU2VudDogRnJpZGF5LCBPY3RvYmVyIDAzLCAyMDA4IDEyOjE5IFBNCj4gVG86IEFsYWlu
IER1cmFuZAo+IENjOiB2NHY2aW50ZXJpbUBpZXRmLm9yZwo+IFN1YmplY3Q6IFJlOiBbdjR2Nmlu
dGVyaW1dIEJPRiBkaXNjdXNzaW9ucwo+IAo+IFRoaXMgc2VlbXMgaW5kZWVkIGJldHRlciB0aGFu
IGEgQk9GLgo+IElzIHRoZSBuZXcgY2hhcnRlciBhdmFpbGFibGU/Cj4gCj4gUkQKPiAKPiBBbGFp
biBEdXJhbmQgICAobS9qL2EpIDEwLzMvMDggNTowNCBQTToKPj4gT3VyIEFkcyBoYXZlIHJlLWNo
YXJ0ZXJlZCB0aGUgU29mdHdpcmUgd2cgdG8gYWRkcmVzcyB0aGUgdHVubmVsaW5nICsgCj4+IG5h
dDQ0IGNhc2UsIHNvIGl0IGlzIHVuY2xlYXIgdG8gbWUgd2h5IHdlIHdvdWxkIG5lZWQgYSBib2Yg
aW4gdGhhdCAKPj4gcGFydGljdWxhciBzcGFjZSB3aGVuIHRoZSB3b3JraW5nIGdyb3VwIHdpbGwg
YmUgbWVldGluZyBpbiBNaW5uZWFwb2xpcy4KPj4KPj4gICAtIEFsYWluLiAKCgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwp2NHY2aW50ZXJpbSBtYWlsaW5n
IGxpc3QKdjR2NmludGVyaW1AaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby92NHY2aW50ZXJpbQo=


From v4v6interim-bounces@ietf.org  Mon Oct  6 09:35:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEF623A6932;
	Mon,  6 Oct 2008 09:35:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D66E33A67DD
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 09:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eFIu+FyZ9xob for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 09:35:12 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 44A4D3A6932
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 09:35:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,368,1220227200"; d="scan'208";a="169706707"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 06 Oct 2008 16:34:53 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m96GYrRm026910; 
	Mon, 6 Oct 2008 09:34:53 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m96GYr9g025624;
	Mon, 6 Oct 2008 16:34:53 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 12:34:52 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 12:34:51 -0400
Message-ID: <BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <48E6AEBD.9090205@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: AcklsjnzPqZeDrtMQ5SJhp27VB9nTQCHk2ow
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
	<D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org>
	<48E6AEBD.9090205@gmail.com>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"Hiroshi MIYATA" <miyata@tahi.org>
X-OriginalArrivalTime: 06 Oct 2008 16:34:52.0629 (UTC)
	FILETIME=[754B5850:01C927D1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3188; t=1223310893;
	x=1224174893; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m>
	|Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=NNq4yyRDRDMdjgjDntW7QrtlkJ44O1xwbMXM5vvOD70=;
	b=sCz5xC+gHonAU7/jBawiVJhXr4XNieeU8hlWZV71DvoGWS3T1y/1ciPlpO
	1cEIX+Siy/GGktlamKNMw7McRPTuJGtJLgCZfk4yWmGryhSTzdnPjjRHh7O0
	QMuPRZDjJB;
Authentication-Results: sj-dkim-3; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I do agree that RFC 4821 is the right solution, and should be used in
recommendations in IETF documents.

However, how many stacks actually implement RFC 4821?

Perhaps by merely publicizing more widely its existence, we might be
able to lure more implementors... 

- Wes


-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
Sent: Friday, October 03, 2008 7:46 PM
To: Hiroshi MIYATA
Cc: Wes Beebee (wbeebee); v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation

Actually the *correct* solution is to use a method of PMTU discovery
that does not depend on ICMP.
That's the point of RFC 4821.

  Brian

On 2008-10-04 08:51, Hiroshi MIYATA wrote:
> Correct!
> 
> We have met the problem, and, yes, only the way is fragmenting the 
> packet on the Translator.
> We have developed it as a optional behavior.
> 
> It may cause the argument if we state it in document, since it break 
> the PMTU Discovery semantics.
> 
> But it is the fact.
> 
> Maybe it is not recommended to describe on BEHAVE documents as a 
> requirement.
> But we should give the hint of this issue on the documents as possible

> problems and solution and utilization (since it is not recommended to 
> use this in public service, but possible to be used for controllable 
> area of the administrator.)
> 
> Regards,
> 
> ....miyata
> 
> 
> On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote:
> 
>> Some SP's may view ICMP as an attack vector and may explicitly block 
>> ICMP messages.
>>
>> In this case, the only way to get connectivity for packets that are 
>> too large is to fragment.
>>
>> - Wes
>>
>> -----Original Message-----
>> From: v4v6interim-bounces@ietf.org 
>> [mailto:v4v6interim-bounces@ietf.org]
>> On Behalf Of Hiroshi MIYATA
>> Sent: Friday, October 03, 2008 5:31 AM
>> To: v4v6interim@ietf.org
>> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
>>
>> Jennings,
>>
>>
>> FYI.
>> Though it is already clearly explained by Dave, let me give you the 
>> pointer.
>> The answer for your question of "Fragmentation options" is clearly 
>> stated in RFC2765(SIIT) as end-to-end path MTU discovery.
>> See Section 3 and 4.
>>
>> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
>>       Note: A node may receive a Packet Too Big message reporting a
>>       next-hop MTU that is less than the IPv6 minimum link MTU.  In 
>> that
>>       case, the node is not required to reduce the size of subsequent
>>       packets sent on the path to less than the IPv6 minimun link
MTU,
>>       but rather must include a Fragment header in those packets
[IPv6-
>>       SPEC].
>>
>> It must work well. ;-)
>>
>> Regards,
>>
>> ....miyata
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 09:51:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDCB03A6A48;
	Mon,  6 Oct 2008 09:51:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 301533A6A48
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 09:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.719
X-Spam-Level: 
X-Spam-Status: No, score=-1.719 tagged_above=-999 required=5 tests=[AWL=0.231, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WKCE-3KuL48E for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 09:51:12 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id 65FA63A67DD
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 09:51:12 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 2FBF4173F8;
	Mon,  6 Oct 2008 18:51:19 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 07056AE2C;
	Mon,  6 Oct 2008 18:50:59 +0200 (CEST)
Message-ID: <48EA4193.8070909@free.fr>
Date: Mon, 06 Oct 2008 18:49:23 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn> <48EA246E.6040203@free.fr>
	<27E6F7E7-813C-43D7-85AA-24243B653921@cisco.com>
In-Reply-To: <27E6F7E7-813C-43D7-85AA-24243B653921@cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

RnJlZCBCYWtlciAgIChtL2ovYSkgMTAvNi8wOCA1OjI0IFBNOgo+IAo+IE9uIE9jdCA2LCAyMDA4
LCBhdCA3OjQ1IEFNLCBS77+9bWkgRGVzcHLvv71zIHdyb3RlOgo+IAo+PiBJbiBteSB1bmRlcnN0
YW5kaW5nLCAgaXMgb25seSBpZiBpdCBpcyBleHRlbmRlZCB0byBzdXBwb3J0IElQdjQKPj4gb3Zl
ciBJUHY2LCBhbmQgYWxzbyBwb3J0IG11bHRpcGxleGluZyAocmVzcGVjdGl2ZWx5IHNlY3Rpb25z
IDQuOCBhbmQgCj4+IDYuMiBvZiB5b3VyIGRyYWZ0LXhsaS1iZWhhdmUtaXZpLTAwKSB0aGF0IGNv
bW1vbmFsaXR5IHdpdGggYSB0dW5uZWxpbmcgCj4+IGFwcHJvYWNoIGxpa2UgU0FNIGlzIGxpa2Vs
eSB0byBiZSBzaWduaWZpY2FudC4KPiAKPiA/Cj4gCj4gVGhlcmUgaXMgbm8gIm92ZXIiIGluIElW
SS4uLgo+IApUaGUgdGl0bGUgb2Ygc2VjdGlvbiA0LjggaW4gZHJhZnQteGxpLWJlaGF2ZS1pdmkt
MDAgaXMgIklQdjQgb3ZlciBJUHY2IgoKRmlyc3Qgd29yZHMgb2YgdGhpcyBzZWN0aW9uIGFyZSAi
VGhlIElWSSBzY2hlbWUgY2FuIHN1cHBvcnQgdGhlIElQdjQgCm92ZXIgSVB2NiBzZXJ2aWNlIChO
QVQ2NDYpIi4KClRoYXQncyB3aGF0IEkgd2FzIHJlZmVycmluZyB0by4KClJECl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnY0djZpbnRlcmltIG1haWxpbmcg
bGlzdAp2NHY2aW50ZXJpbUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3Y0djZpbnRlcmltCg==


From v4v6interim-bounces@ietf.org  Mon Oct  6 13:22:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96E073A6912;
	Mon,  6 Oct 2008 13:22:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC16B3A68AF
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 13:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.561
X-Spam-Level: 
X-Spam-Status: No, score=-5.561 tagged_above=-999 required=5 tests=[AWL=1.038, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L9lbgVf2qIa0 for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 13:21:58 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 5A30A3A68DB
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 13:21:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,369,1220227200"; d="scan'208";a="21783675"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 06 Oct 2008 20:22:34 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m96KMYDR016877; 
	Mon, 6 Oct 2008 22:22:34 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m96KMXGA019907;
	Mon, 6 Oct 2008 20:22:33 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 22:22:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 22:19:18 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE0079A9B16@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: AcklsjnzPqZeDrtMQ5SJhp27VB9nTQCHk2owAAfkFsA=
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com><D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org><48E6AEBD.9090205@gmail.com>
	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>,
	"Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"Hiroshi MIYATA" <miyata@tahi.org>
X-OriginalArrivalTime: 06 Oct 2008 20:22:33.0836 (UTC)
	FILETIME=[44021AC0:01C927F1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3756; t=1223324554;
	x=1224188554; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=dYHA13bj6ZoDNut6wBqIZIzfQDymGK4fKAXIe1La/dY=;
	b=r0fWTyZw9r9sPAqmtmxRezc9czGe9uG54ENU4Lwr8lFVXq6u+wRvyYOxCq
	9Io3Q+vY16hWQ9OQx9+MwHhXOrBzAyXWZsSM2NYqWJvKkH9r0v6nDCKEkBPG
	4CCq0Azz4z;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Am I the only finding weird to assume that servers (and clients depending o=
n the application) would be upgraded to support PLPMTUd while still being u=
nable to do dual-stack?

Assuming that a server is 'important' enough to get a PLPMTUd software upgr=
ade, then we could assume as well that it can get both an IPv4 and an IPv6 =
addresses, couldn't we? =


Or am I missing something? (which is quite possible of course)

-=E9ric


> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: Friday, October 03, 2008 7:46 PM
> To: Hiroshi MIYATA
> Cc: Wes Beebee (wbeebee); v4v6interim@ietf.org
> Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
> =

> Actually the *correct* solution is to use a method of PMTU =

> discovery that does not depend on ICMP.
> That's the point of RFC 4821.
> =

>   Brian
> =

> On 2008-10-04 08:51, Hiroshi MIYATA wrote:
> > Correct!
> > =

> > We have met the problem, and, yes, only the way is fragmenting the =

> > packet on the Translator.
> > We have developed it as a optional behavior.
> > =

> > It may cause the argument if we state it in document, since =

> it break =

> > the PMTU Discovery semantics.
> > =

> > But it is the fact.
> > =

> > Maybe it is not recommended to describe on BEHAVE documents as a =

> > requirement.
> > But we should give the hint of this issue on the documents =

> as possible
> =

> > problems and solution and utilization (since it is not =

> recommended to =

> > use this in public service, but possible to be used for =

> controllable =

> > area of the administrator.)
> > =

> > Regards,
> > =

> > ....miyata
> > =

> > =

> > On 2008/10/04, at 3:36, Wes Beebee (wbeebee) wrote:
> > =

> >> Some SP's may view ICMP as an attack vector and may =

> explicitly block =

> >> ICMP messages.
> >>
> >> In this case, the only way to get connectivity for packets =

> that are =

> >> too large is to fragment.
> >>
> >> - Wes
> >>
> >> -----Original Message-----
> >> From: v4v6interim-bounces@ietf.org
> >> [mailto:v4v6interim-bounces@ietf.org]
> >> On Behalf Of Hiroshi MIYATA
> >> Sent: Friday, October 03, 2008 5:31 AM
> >> To: v4v6interim@ietf.org
> >> Subject: [v4v6interim] Fragmentation Options in NAT6 presentation
> >>
> >> Jennings,
> >>
> >>
> >> FYI.
> >> Though it is already clearly explained by Dave, let me =

> give you the =

> >> pointer.
> >> The answer for your question of "Fragmentation options" is clearly =

> >> stated in RFC2765(SIIT) as end-to-end path MTU discovery.
> >> See Section 3 and 4.
> >>
> >> And of course RFC1981(PMTUD) is compliant with it. ;-) Chap. 4
> >>       Note: A node may receive a Packet Too Big message reporting a
> >>       next-hop MTU that is less than the IPv6 minimum link =

> MTU.  In =

> >> that
> >>       case, the node is not required to reduce the size of =

> subsequent
> >>       packets sent on the path to less than the IPv6 minimun link
> MTU,
> >>       but rather must include a Fragment header in those packets
> [IPv6-
> >>       SPEC].
> >>
> >> It must work well. ;-)
> >>
> >> Regards,
> >>
> >> ....miyata
> >> _______________________________________________
> >> v4v6interim mailing list
> >> v4v6interim@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v4v6interim
> >>
> > =

> > _______________________________________________
> > v4v6interim mailing list
> > v4v6interim@ietf.org
> > https://www.ietf.org/mailman/listinfo/v4v6interim
> > =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct  6 17:28:01 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEE733A6B51;
	Mon,  6 Oct 2008 17:28:01 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8237B3A6B54
	for <v4v6interim@core3.amsl.com>; Mon,  6 Oct 2008 17:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5
	tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2Tzm9lcnM8Qd for <v4v6interim@core3.amsl.com>;
	Mon,  6 Oct 2008 17:27:59 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id BE4683A69C3
	for <v4v6interim@ietf.org>; Mon,  6 Oct 2008 17:27:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,370,1220227200"; d="scan'208";a="87534905"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 07 Oct 2008 00:28:37 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m970Sb02027573
	for <v4v6interim@ietf.org>; Mon, 6 Oct 2008 17:28:37 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m970SbXQ026595
	for <v4v6interim@ietf.org>; Tue, 7 Oct 2008 00:28:37 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 17:28:37 -0700
Received: from stealth-10-32-244-219.cisco.com ([10.32.244.219]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 17:28:36 -0700
Message-Id: <0A2B2E22-01C4-4BF2-A810-FD620748A1ED@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Eric Vyncke (evyncke) <evyncke@cisco.com>
In-Reply-To: <CE2BF2A7B1008C459FD7978065C6ECE0079A9B16@xmb-ams-33a.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 17:28:36 -0700
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com><D2FC99B8-A75A-43BE-9717-DCCE2C807AB7@tahi.org><48E6AEBD.9090205@gmail.com>
	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079A9B16@xmb-ams-33a.emea.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 07 Oct 2008 00:28:36.0936 (UTC)
	FILETIME=[A3806480:01C92813]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=843; t=1223339317; x=1224203317;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=dEvw97zHtSIbCuVGN4/6oG76CBaSNw6qYL6WUiOP1Hg=;
	b=pstUgyxD9Tiyaq+j61LnwjNmEooeqfgBcOBO3ZOVfeW0ewgLqxdl71Bbp3
	MY9HUq4CimnPq1GzROa+7QSGM5TSWWz0mokbTdDLeUv7d/aE2oQCnh8lIGSr
	hzBaSXKXEp;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 6, 2008, at 1:19 PM, Eric Vyncke (evyncke) wrote:

> Am I the only finding weird to assume that servers (and clients  
> depending on the application) would be upgraded to support PLPMTUd  
> while still being unable to do dual-stack?

I'm not sure that's an accurate statement. End system implementations  
(Mac, Linux, BSD, Solaris, Windows Vista and some earlier versions)  
generally are dual-stack-capable these days. The issue is that the  
network connecting them isn't.

That's the premise in DS-Lite; that one could use the network as  
bandwidth, eliminate all network-based services, and simply tunnel  
through it to build a next generation overlay. ISPs that think they  
are offering services besides bandwidth might eventually decide they  
don't want to be tunneled over, smell the coffee, and change.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 00:48:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 25F983A6999;
	Tue,  7 Oct 2008 00:48:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3A423A6973
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 00:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KjN4mTcoieLe for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 00:48:16 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 7F70A3A6850
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 00:48:16 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m977lWX7024526; Tue, 7 Oct 2008 10:48:06 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 7 Oct 2008 10:47:57 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 7 Oct 2008 10:47:56 +0300
Received: from esdhcp04196.research.nokia.com ([172.21.41.96]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 7 Oct 2008 10:47:56 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: v4v6interim@ietf.org
Date: Tue, 7 Oct 2008 10:47:56 +0300
User-Agent: KMail/1.9.10
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<48E6AEBD.9090205@gmail.com>
	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810071047.56810.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 07 Oct 2008 07:47:56.0568 (UTC)
	FILETIME=[03110980:01C92851]
X-Nokia-AV: Clean
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Monday 06 October 2008 19:34:51 ext Wes Beebee (wbeebee), you wrote:
> I do agree that RFC 4821 is the right solution, and should be used in
> recommendations in IETF documents.
>
> However, how many stacks actually implement RFC 4821?

There are really two separate categories:

For TCP (and SCTP), this needs to be supported by the IP stack. The widespr=
ead =

use of TCP MSS clamping makes it obvious that many if not most IP stacks do =

not support this as yet.

For UDP, this needs to be implemented directly into the application-layer, =

with some additional support from the IP stack (to allow sending too large =

packets with DF bit). As yet, Linux is the only IP stack that explicitly =

supports this via some "proprietary" socket API options. As for application=
s, =

it is difficult to gather meaningful data. But considering the lack of =

support from lower layers, it is likely that this is mostly not implemented=
. =

I empirically believe that most applications simply have a "safe" hard-code=
d =

MTU for UDP, e.g. 1400 bytes or whatever.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 03:29:08 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ECC153A6B51;
	Tue,  7 Oct 2008 03:29:08 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 178343A6B4D
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 03:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.951
X-Spam-Level: 
X-Spam-Status: No, score=-0.951 tagged_above=-999 required=5
	tests=[AWL=-1.348, BAYES_00=-2.599, FH_HAS_XAIMC=2.696,
	MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nMQX-nCts1Q2 for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 03:29:06 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66])
	by core3.amsl.com (Postfix) with SMTP id DBCA83A6B02
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 03:29:05 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0)
	with SMTP id jm548eb42eb; Tue, 07 Oct 2008 18:29:09 +0800
Message-ID: <48EB39F2.6000904@cernet.edu.cn>
Date: Tue, 07 Oct 2008 18:29:06 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn> <48EA246E.6040203@free.fr>
In-Reply-To: <48EA246E.6040203@free.fr>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: Am3oJnUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

UsOpbWkgRGVzcHLDqXMg5YaZ6YGTOgo+IFhpbmcgTGkgICAobS9qL2EpIDEwLzQvMDggMToxOSBB
TToKPj4gUsOpbWkgRGVzcHLDqXMg5YaZ6YGTOgo+Pj4gTWFyYyBCbGFuY2hldCAgIChtL2ovYSkg
MTAvMy8wOCAzOjE1IFBNOgo+Pj4+IFLvv71taSBEZXNwcu+/vXMgYSDvv71jcml0IDoKPj4+Pj4g
SSBzdXBwb3J0IEZyZWQncyBzdWdnZXN0aW9uIG9mIHNlcGFyYXRpbmcgZGlzY3Vzc2lvbiBzcGFj
ZXMgZm9yIAo+Pj4+PiB3aGF0IGlzCj4+Pj4+IHNwZWNpZmljIHRvIHR1bm5lbGluZyBhbmQgd2hh
dCBpcyBzcGVjaWZpYyB0byB0cmFuc2xhdGlvbi4KPj4+Pj4KPj4+Pj4gSW4gbXkgdW5kZXJzdGFu
ZGluZzoKPj4+Pj4gLSBOQVQ2NCwgTkFUNDYsIGFuZCB3aGF0IGNvbmNlcm5zIElTUCBpbmZyYXN0
cnVjdHVyZSBOQVRzIChDR05zKSAKPj4+Pj4gYnV0IG5vdAo+Pj4+PiBDUEUgTkFUcywgd291bGQg
YmUgaW4gdjR2Ni14bGF0Cj4+Pj4+IC0gQStQLCBJVkksIFNBTSwgYW5kIHR1bm5lbGluZyBhc3Bl
Y3RzIG9mIERTIGxpdGUgIHdvdWxkIGJlIGluIAo+Pj4+PiB2NHY2LVhsYXQKPj4+Pgo+Pj4+IHMv
djR2Ni14bGF0L3Y0djYtdHVubmVsLyAgcmlnaHQ/Cj4+IElWSSBzaG91bGQgYmUgaW4gdjR2Ni14
bGF0IGNhdC4geGluZwo+Cj4gUmlnaHQ6IElWSSBpcyBpbmRlZWQgYSB0cmFuc2xhdGlvbiBzb2x1
dGlvbi4KPiBBcG9sb2dpZXMgZm9yIHRoZSBtaXN0YWtlLgpUaGFua3MuCj4KPiBJbiBteSB1bmRl
cnN0YW5kaW5nLCAgaXMgb25seSBpZiBpdCBpcyBleHRlbmRlZCB0byBzdXBwb3J0IElQdjQKPiBv
dmVyIElQdjYsIGFuZCBhbHNvIHBvcnQgbXVsdGlwbGV4aW5nIChyZXNwZWN0aXZlbHkgc2VjdGlv
bnMgNC44IGFuZCAKPiA2LjIgb2YgeW91ciBkcmFmdC14bGktYmVoYXZlLWl2aS0wMCkgdGhhdCBj
b21tb25hbGl0eSB3aXRoIGEgdHVubmVsaW5nIAo+IGFwcHJvYWNoIGxpa2UgU0FNIGlzIGxpa2Vs
eSB0byBiZSBzaWduaWZpY2FudC4KT2guIEkgc2VlIHRoZSByZWFzb24uIEluIGRyYWZ0LXhsaS1i
ZWhhdmUtaXZpLTAwLCB3ZSBkaXNjdXNzZWQgdGhlIGNhc2UgCm9mIGRvdWJsZSBJVkkgKElQdjQt
SVB2Ni1JUHY0KS4gV2UgbWF5IGNvbXBhcmUgU0FNIGFuZCBkb3VibGUgSVZJIGluIHRoZSAKZnV0
dXJlLgoKUmVnYXJkcywKCnhpbmcKCj4KPiBCZXN0IHJlZ2FyZHMuCj4KPiBSRAo+Cj4KCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnY0djZpbnRlcmltIG1h
aWxpbmcgbGlzdAp2NHY2aW50ZXJpbUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3Y0djZpbnRlcmltCg==


From v4v6interim-bounces@ietf.org  Tue Oct  7 03:31:59 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12A0028C15C;
	Tue,  7 Oct 2008 03:31:59 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03C9E28C156
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 03:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.277
X-Spam-Level: 
X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5
	tests=[AWL=-0.674, BAYES_00=-2.599, FH_HAS_XAIMC=2.696,
	MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F3urj6c7sB85 for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 03:31:57 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66])
	by core3.amsl.com (Postfix) with SMTP id B27FA28C15C
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 03:31:56 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0)
	with SMTP id jm3348eb437d; Tue, 07 Oct 2008 18:31:35 +0800
Message-ID: <48EB3A88.3070001@cernet.edu.cn>
Date: Tue, 07 Oct 2008 18:31:36 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn> <48EA246E.6040203@free.fr>
	<27E6F7E7-813C-43D7-85AA-24243B653921@cisco.com>
	<48EA4193.8070909@free.fr>
In-Reply-To: <48EA4193.8070909@free.fr>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: AOpqJnUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

UsOpbWkgRGVzcHLDqXMg5YaZ6YGTOgo+IEZyZWQgQmFrZXIgICAobS9qL2EpIDEwLzYvMDggNToy
NCBQTToKPj4KPj4gT24gT2N0IDYsIDIwMDgsIGF0IDc6NDUgQU0sIFLvv71taSBEZXNwcu+/vXMg
d3JvdGU6Cj4+Cj4+PiBJbiBteSB1bmRlcnN0YW5kaW5nLCAgaXMgb25seSBpZiBpdCBpcyBleHRl
bmRlZCB0byBzdXBwb3J0IElQdjQKPj4+IG92ZXIgSVB2NiwgYW5kIGFsc28gcG9ydCBtdWx0aXBs
ZXhpbmcgKHJlc3BlY3RpdmVseSBzZWN0aW9ucyA0LjggYW5kIAo+Pj4gNi4yIG9mIHlvdXIgZHJh
ZnQteGxpLWJlaGF2ZS1pdmktMDApIHRoYXQgY29tbW9uYWxpdHkgd2l0aCBhIAo+Pj4gdHVubmVs
aW5nIGFwcHJvYWNoIGxpa2UgU0FNIGlzIGxpa2VseSB0byBiZSBzaWduaWZpY2FudC4KPj4KPj4g
Pwo+Pgo+PiBUaGVyZSBpcyBubyAib3ZlciIgaW4gSVZJLi4uCj4+Cj4gVGhlIHRpdGxlIG9mIHNl
Y3Rpb24gNC44IGluIGRyYWZ0LXhsaS1iZWhhdmUtaXZpLTAwIGlzICJJUHY0IG92ZXIgSVB2NiIK
Pgo+IEZpcnN0IHdvcmRzIG9mIHRoaXMgc2VjdGlvbiBhcmUgIlRoZSBJVkkgc2NoZW1lIGNhbiBz
dXBwb3J0IHRoZSBJUHY0IAo+IG92ZXIgSVB2NiBzZXJ2aWNlIChOQVQ2NDYpIi4KPgo+IFRoYXQn
cyB3aGF0IEkgd2FzIHJlZmVycmluZyB0by4KKDEpIEl0IGlzIGEgc2NoZW1lIG9mIGRvdWJsZSB0
cmFuc2xhdGlvbiAoSVB2NC1JUHY2LUlQdjQpLCBub3QgCnR1bm5lbGluZy4gV2Ugc2hvdWxkIG5v
dCBjYWxsIGl0ICJvdmVyIiwgc29ycnkuCigyKSBJdCBpcyBOQVQ0NjQsIG5vdCBOQVQ2NDYuCgp4
aW5nCj4KPiBSRAo+Cj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fCnY0djZpbnRlcmltIG1haWxpbmcgbGlzdAp2NHY2aW50ZXJpbUBpZXRmLm9yZwpodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y0djZpbnRlcmltCg==


From v4v6interim-bounces@ietf.org  Tue Oct  7 05:58:16 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A5913A6B85;
	Tue,  7 Oct 2008 05:58:16 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC1053A6B84
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 05:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level: 
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[AWL=0.282, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zq4TnJRbSRtD for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 05:58:15 -0700 (PDT)
Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28])
	by core3.amsl.com (Postfix) with ESMTP id 014743A6A00
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 05:58:14 -0700 (PDT)
Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 0321612B744;
	Tue,  7 Oct 2008 14:58:13 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 845C912B6D2;
	Tue,  7 Oct 2008 14:58:11 +0200 (CEST)
Message-ID: <48EB5C93.5000408@free.fr>
Date: Tue, 07 Oct 2008 14:56:51 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <44339B00-681B-4E63-9FE0-F65D3EA23B07@cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42389@xmb-rtp-20e.amer.cisco.com>	<48E61A05.20406@free.fr>
	<48E61AE0.7080200@viagenie.ca> <48E63077.5070907@free.fr>
	<48E6A86E.30308@cernet.edu.cn> <48EA246E.6040203@free.fr>
	<27E6F7E7-813C-43D7-85AA-24243B653921@cisco.com>
	<48EA4193.8070909@free.fr> <48EB3A88.3070001@cernet.edu.cn>
In-Reply-To: <48EB3A88.3070001@cernet.edu.cn>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] BOF discussions
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

WGluZyBMaSAgIChtL2ovYSkgMTAvNy8wOCAxMjozMSBQTToKPiBSw6ltaSBEZXNwcsOpcyDlhpnp
gZM6Cj4+IEZyZWQgQmFrZXIgICAobS9qL2EpIDEwLzYvMDggNToyNCBQTToKPj4+Cj4+PiBPbiBP
Y3QgNiwgMjAwOCwgYXQgNzo0NSBBTSwgUu+/vW1pIERlc3By77+9cyB3cm90ZToKPj4+Cj4+Pj4g
SW4gbXkgdW5kZXJzdGFuZGluZywgIGlzIG9ubHkgaWYgaXQgaXMgZXh0ZW5kZWQgdG8gc3VwcG9y
dCBJUHY0Cj4+Pj4gb3ZlciBJUHY2LCBhbmQgYWxzbyBwb3J0IG11bHRpcGxleGluZyAocmVzcGVj
dGl2ZWx5IHNlY3Rpb25zIDQuOCBhbmQgCj4+Pj4gNi4yIG9mIHlvdXIgZHJhZnQteGxpLWJlaGF2
ZS1pdmktMDApIHRoYXQgY29tbW9uYWxpdHkgd2l0aCBhIAo+Pj4+IHR1bm5lbGluZyBhcHByb2Fj
aCBsaWtlIFNBTSBpcyBsaWtlbHkgdG8gYmUgc2lnbmlmaWNhbnQuCj4+Pgo+Pj4gPwo+Pj4KPj4+
IFRoZXJlIGlzIG5vICJvdmVyIiBpbiBJVkkuLi4KPj4+Cj4+IFRoZSB0aXRsZSBvZiBzZWN0aW9u
IDQuOCBpbiBkcmFmdC14bGktYmVoYXZlLWl2aS0wMCBpcyAiSVB2NCBvdmVyIElQdjYiCj4+Cj4+
IEZpcnN0IHdvcmRzIG9mIHRoaXMgc2VjdGlvbiBhcmUgIlRoZSBJVkkgc2NoZW1lIGNhbiBzdXBw
b3J0IHRoZSBJUHY0IAo+PiBvdmVyIElQdjYgc2VydmljZSAoTkFUNjQ2KSIuCj4+Cj4+IFRoYXQn
cyB3aGF0IEkgd2FzIHJlZmVycmluZyB0by4KPiAoMSkgSXQgaXMgYSBzY2hlbWUgb2YgZG91Ymxl
IHRyYW5zbGF0aW9uIChJUHY0LUlQdjYtSVB2NCksIG5vdCAKPiB0dW5uZWxpbmcuIFdlIHNob3Vs
ZCBub3QgY2FsbCBpdCAib3ZlciIsIHNvcnJ5Lgo+ICgyKSBJdCBpcyBOQVQ0NjQsIG5vdCBOQVQ2
NDYuCgpJIHNlZS4KVGhhbmtzIGZvciB0aGUgY2xhcmlmaWNhdGlvbi4KUkQKX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdjR2NmludGVyaW0gbWFpbGluZyBs
aXN0CnY0djZpbnRlcmltQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vdjR2NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Tue Oct  7 06:46:35 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB0493A6928;
	Tue,  7 Oct 2008 06:46:35 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0AD763A6928
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 06:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P65PQkm9qnqW for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 06:46:29 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id A4E6C3A67AB
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 06:46:28 -0700 (PDT)
Received: from wifi-eduroam-034.sri.ucl.ac.be (wifi-eduroam-034.sri.ucl.ac.be
	[192.135.167.34]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m97DknCN099431
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <v4v6interim@ietf.org>; Tue, 7 Oct 2008 15:46:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: v4v6interim@ietf.org
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 7 Oct 2008 15:46:55 +0200
X-Mailer: Apple Mail (2.929.2)
Subject: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_each_other
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 08:45:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C3D53A68BD;
	Tue,  7 Oct 2008 08:45:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AC343A684F
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 08:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.023
X-Spam-Level: 
X-Spam-Status: No, score=-6.023 tagged_above=-999 required=5 tests=[AWL=0.023, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WiKHB+X7rCUn for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 08:45:44 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 523643A699C
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 08:45:31 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 7 Oct 2008 15:45:45 -0000
X-AuditID: 80125474-ac999bb000000a40-c6-48eb842947a7
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	35B2D21AF2F
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 08:45:45 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K8D004YLL48SMDF@mail.sri.com> for
	v4v6interim@ietf.org; Tue, 07 Oct 2008 08:45:45 -0700 (PDT)
Date: Tue, 07 Oct 2008 11:45:49 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-id: <48EB842D.8000206@sri.com>
MIME-version: 1.0
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I'm sure the folks on Digg will boldly go where no IETFer has gone 
before and come up with an instant solution in 25 words or 
less...immediately reviewed and dismissed...saves a lot of time and 
brainpower, and avoids the overhead of publishing the Solution X RFC 
followed by the Solution X is Evil RFC followed by the "Solution X is 
Evil RFC" is Evil RFC followed by...

my favorite - "They didn't figure that out already?"

On the other hand, you did a great job of summarizing a lot of 
discussion (over years) and a dozen drafts (currently being circulated) 
into a one-page summary in nearly layman's terms (at least network 
hobbyist level).  Thanks.

FYI, while I am an advocate for (eventually) solving the v4 client to v6 
server scenario, I agree that the priority should be on the v6 client to 
v4 Internet solution, and we don't want to hold up that solution for an 
integrated two-way translator. 

Ed J.

Iljitsch van Beijnum wrote:
> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_each_other 
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 10:27:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 854B93A6821;
	Tue,  7 Oct 2008 10:27:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A19E3A6821
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 10:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5
	tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WSR8d0y5WQZV for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 10:27:00 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 72C503A67F3
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 10:27:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,373,1220227200"; d="scan'208";a="93057308"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 07 Oct 2008 17:26:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m97HQPOQ028161; 
	Tue, 7 Oct 2008 10:26:25 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m97HQPRC004623;
	Tue, 7 Oct 2008 17:26:25 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 10:26:24 -0700
Received: from stealth-10-32-244-219.cisco.com ([10.32.244.219]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 10:26:24 -0700
Message-Id: <7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 7 Oct 2008 10:26:23 -0700
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 07 Oct 2008 17:26:24.0336 (UTC)
	FILETIME=[D2822500:01C928A1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2735; t=1223400385;
	x=1224264385; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=yYpyVXt7W0u+lVb7HUJ1smOEeka12h1QH5QhACPP8B4=;
	b=EDlh1t5t3FOz4SfBsVRgLsidJM/724AyleKnIcX+t/zUwT8psteD6szgRV
	ejsEdAstnVRHkPQlC6TyhKp0570dp2xZrzpijF9l3I18mRZ6GLp/o3bNnaTB
	UFmzjEVtVj;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 7, 2008, at 6:46 AM, Iljitsch van Beijnum wrote:
> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_each_other


Thanks. Good article. I think the title is amusing; one would think  
that there was no prior work on making IPv4 and IPv6 talk with each  
other. But as you point out, there of course has been.

Let me comment on your comments re IVI:

> Finally, there is a solution named IVI (IV and VI, get it?) which  
> updates NAT-PT but also creates a direct, SIIT-like mapping between  
> certain IPv4 and IPv6 addresses. Unfortunately, this requires some  
> un-IPv6 like configuration on the IPv6 side, so it's not obvious to  
> me how this is useful. But apparently, IVI has been in use in China  
> for two years.


What does it mean to be "IPv6-like"?

Looking through RFCs 1884 (2.4.4), 2373 (2.5.4), 3513 (2.5.5), 4291  
(2.5.5), and 2765 (2.1), and additionally looking at NAT64 (section  
5.1), the addressing architecture has always had in it some form of  
address that embeds IPv4 into an IPv6 address. None of those memos  
have discussed how that was allocated or how a host was supposed to  
get them; the one thing that has been perfectly clear throughout is  
that they were not allocated by SLACK - they would have to be manually  
assigned or automatically assign via the mechanisms we use for IPv4  
address allocation, probably using DHCP to communicate them to the  
host and either Dynamic DNS or manual DNS management to associate them  
with names.

The one point of disagreement that I have had with Marcello's  
Pref64::/96 characterization is that it does something that RFC 4291  
says to not do. If we have a prefix whose left-most bits are not 000,  
we are supposed to reserve the right-most 64 bits for host identifier  
and contain the routing prefix in the left-most 64 bits; RFC 4291  
makes that clear in section 2.5.1, 2.5.4, 2.5.6, and 2.5.7. As such,  
neglecting the question of using the 0::ffff:a.b.c.d, 0::0:a.b.c.d, or  
0::ffff:0:a.b.c.d forms, if I have a prefix assigned by the network  
operator, the address architecture says that I would have to treat all  
Pref64::a.b.c.d routes as host routes. Tell me that this is not what  
you're hoping for in an IPv6 address?

What CERNET has done is define an address that maps to RFC 4291's  
architecture, allows them to (within that architecture) subnet IPv4- 
mapped addresses in the IPv6 domain, and use the mapping effectively  
in routing. If there is anything that I would hope was IPv6-like, it  
would have those characteristics.

All you do is crab; you don't like it, but you don't give a technical  
reason to not like it. What's your point?
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 14:00:41 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77C7E3A689F;
	Tue,  7 Oct 2008 14:00:41 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 539683A6967
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 14:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5
	tests=[AWL=-0.069, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fg6yKUDy1J63 for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 14:00:39 -0700 (PDT)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28])
	by core3.amsl.com (Postfix) with ESMTP id 5D1CE3A67B3
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 14:00:22 -0700 (PDT)
Received: by yx-out-2324.google.com with SMTP id 8so609055yxg.49
	for <v4v6interim@ietf.org>; Tue, 07 Oct 2008 14:01:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=IylMzdYIJ/JuYd7Ox1adqGVl6vtT3W3nXsHbOAzAMzU=;
	b=BpSzAAPQ1f5jkm9s0E66vRVCdsv4qh50GJyyjKLSWqNY9TrtWXrP09MHTSelAkC7Lc
	P6q0xDgdPxgRhbKgnJez1cAO60X7D8qHTjZfFswnTclu5RjfMGIBDqrnArf2TRCQHDAb
	SwtjaEDkufX47uI2FXIUq7pbZmroLzRdEi+DA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=wEVLjyXRUEGHkqhJz+CudUX9pjmSqqDezdKRP5nYJYuCg1XmeA+XFf+kln4PQ0xvQd
	hY5g7RQcJGfEgo1DtJdU6FsmEqPahj8KhBcXJmCejxjFg1YgkCkXCVVOFpLOw7Lo8c3P
	JxHtwfLBE+BhJO4JzUIDUtKWc3vWAgbuL2jW0=
Received: by 10.142.141.21 with SMTP id o21mr2963956wfd.213.1223413260550;
	Tue, 07 Oct 2008 14:01:00 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 9sm18811107wfc.19.2008.10.07.14.00.57
	(version=SSLv3 cipher=RC4-MD5); Tue, 07 Oct 2008 14:00:59 -0700 (PDT)
Message-ID: <48EBCE08.4050602@gmail.com>
Date: Wed, 08 Oct 2008 10:00:56 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?=
 <remi.denis-courmont@nokia.com>
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<48E6AEBD.9090205@gmail.com>
	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
	<200810071047.56810.remi.denis-courmont@nokia.com>
In-Reply-To: <200810071047.56810.remi.denis-courmont@nokia.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

T24gMjAwOC0xMC0wNyAyMDo0NywgUsOpbWkgRGVuaXMtQ291cm1vbnQgd3JvdGU6Cj4gT24gTW9u
ZGF5IDA2IE9jdG9iZXIgMjAwOCAxOTozNDo1MSBleHQgV2VzIEJlZWJlZSAod2JlZWJlZSksIHlv
dSB3cm90ZToKPj4gSSBkbyBhZ3JlZSB0aGF0IFJGQyA0ODIxIGlzIHRoZSByaWdodCBzb2x1dGlv
biwgYW5kIHNob3VsZCBiZSB1c2VkIGluCj4+IHJlY29tbWVuZGF0aW9ucyBpbiBJRVRGIGRvY3Vt
ZW50cy4KPj4KPj4gSG93ZXZlciwgaG93IG1hbnkgc3RhY2tzIGFjdHVhbGx5IGltcGxlbWVudCBS
RkMgNDgyMT8KPiAKPiBUaGVyZSBhcmUgcmVhbGx5IHR3byBzZXBhcmF0ZSBjYXRlZ29yaWVzOgo+
IAo+IEZvciBUQ1AgKGFuZCBTQ1RQKSwgdGhpcyBuZWVkcyB0byBiZSBzdXBwb3J0ZWQgYnkgdGhl
IElQIHN0YWNrLiBUaGUgd2lkZXNwcmVhZCAKPiB1c2Ugb2YgVENQIE1TUyBjbGFtcGluZyBtYWtl
cyBpdCBvYnZpb3VzIHRoYXQgbWFueSBpZiBub3QgbW9zdCBJUCBzdGFja3MgZG8gCj4gbm90IHN1
cHBvcnQgdGhpcyBhcyB5ZXQuCj4gCj4gRm9yIFVEUCwgdGhpcyBuZWVkcyB0byBiZSBpbXBsZW1l
bnRlZCBkaXJlY3RseSBpbnRvIHRoZSBhcHBsaWNhdGlvbi1sYXllciwgCj4gd2l0aCBzb21lIGFk
ZGl0aW9uYWwgc3VwcG9ydCBmcm9tIHRoZSBJUCBzdGFjayAodG8gYWxsb3cgc2VuZGluZyB0b28g
bGFyZ2UgCj4gcGFja2V0cyB3aXRoIERGIGJpdCkuIEFzIHlldCwgTGludXggaXMgdGhlIG9ubHkg
SVAgc3RhY2sgdGhhdCBleHBsaWNpdGx5IAo+IHN1cHBvcnRzIHRoaXMgdmlhIHNvbWUgInByb3By
aWV0YXJ5IiBzb2NrZXQgQVBJIG9wdGlvbnMuIEFzIGZvciBhcHBsaWNhdGlvbnMsIAo+IGl0IGlz
IGRpZmZpY3VsdCB0byBnYXRoZXIgbWVhbmluZ2Z1bCBkYXRhLiBCdXQgY29uc2lkZXJpbmcgdGhl
IGxhY2sgb2YgCj4gc3VwcG9ydCBmcm9tIGxvd2VyIGxheWVycywgaXQgaXMgbGlrZWx5IHRoYXQg
dGhpcyBpcyBtb3N0bHkgbm90IGltcGxlbWVudGVkLiAKPiBJIGVtcGlyaWNhbGx5IGJlbGlldmUg
dGhhdCBtb3N0IGFwcGxpY2F0aW9ucyBzaW1wbHkgaGF2ZSBhICJzYWZlIiBoYXJkLWNvZGVkIAo+
IE1UVSBmb3IgVURQLCBlLmcuIDE0MDAgYnl0ZXMgb3Igd2hhdGV2ZXIuCgpJbiBhbnkgY2FzZSwg
SSBhc3N1bWUgd2UgaGF2ZSB0byB3YWl0IGF0IGxlYXN0IDUgeWVhcnMgYmVmb3JlIHRoZSBSRkM0
ODIxCmFwcHJvYWNoIGlzIHdpZGVseSBkZXBsb3llZC4gQnV0IHNpbmNlIHRoZSBwcm9ibGVtIG9m
IE1UVSBzaXplIGFuZApJQ01QIGJsb2NraW5nIGlzIHdpZGVzcHJlYWQsIEkgdGhpbmsgd2Ugc2hv
dWxkIHJlY29nbmlzZSB0aGF0IGl0IGlzbid0CnNwZWNpZmljIHRvIHRoZSBOQVQ2WzRdIHNjZW5h
cmlvcywgYW5kIHRoYXQgdGhlIHNvbHV0aW9uIG5lZWRzIHRvIGJlIGdlbmVyYWwuCgogICBCcmlh
bgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdjR2Nmlu
dGVyaW0gbWFpbGluZyBsaXN0CnY0djZpbnRlcmltQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Tue Oct  7 16:13:36 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C2A193A6889;
	Tue,  7 Oct 2008 16:13:36 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14E913A6B76
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 16:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.185
X-Spam-Level: 
X-Spam-Status: No, score=-2.185 tagged_above=-999 required=5 tests=[AWL=0.114, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id D-p4jY2RGJjP for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 16:13:35 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org
	[IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc])
	by core3.amsl.com (Postfix) with ESMTP id F3C9D3A68E1
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 16:13:34 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id m97NE817079257;
	Wed, 8 Oct 2008 10:14:09 +1100 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200810072314.m97NE817079257@drugs.dv.isc.org>
To: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Tue, 07 Oct 2008 10:47:56 +0300."
	<200810071047.56810.remi.denis-courmont@nokia.com> 
Date: Wed, 08 Oct 2008 10:14:08 +1100
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


In message <200810071047.56810.remi.denis-courmont@nokia.com>, "=?iso-8859-1?q?
R=E9mi?= Denis-Courmont" writes:
> On Monday 06 October 2008 19:34:51 ext Wes Beebee (wbeebee), you wrote:
> > I do agree that RFC 4821 is the right solution, and should be used in
> > recommendations in IETF documents.
> >
> > However, how many stacks actually implement RFC 4821?
> 
> There are really two separate categories:
> 
> For TCP (and SCTP), this needs to be supported by the IP stack. The widespr=
> ead =
> 
> use of TCP MSS clamping makes it obvious that many if not most IP stacks do =
> 
> not support this as yet.
> 
> For UDP, this needs to be implemented directly into the application-layer, =
> 
> with some additional support from the IP stack (to allow sending too large =
> 
> packets with DF bit). As yet, Linux is the only IP stack that explicitly =
> 
> supports this via some "proprietary" socket API options. As for application=
> s, =
> 
> it is difficult to gather meaningful data. But considering the lack of =
> 
> support from lower layers, it is likely that this is mostly not implemented=
> . =
> 
> I empirically believe that most applications simply have a "safe" hard-code=
> d =
> 
> MTU for UDP, e.g. 1400 bytes or whatever.

	Any IP stack which sets DF for UDP without the application
	requesting it is broken.

	If you do want to be able to set DF for UDP you also need
	to have a way to tell the IP stack to fragment the UDP
	packet into fragements no larger than a certain size.
 
	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct  7 18:45:52 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC5F928C108;
	Tue,  7 Oct 2008 18:45:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F4B83A686C
	for <v4v6interim@core3.amsl.com>; Tue,  7 Oct 2008 16:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gsvq30+CXbWB for <v4v6interim@core3.amsl.com>;
	Tue,  7 Oct 2008 16:24:03 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 636E13A67F9
	for <v4v6interim@ietf.org>; Tue,  7 Oct 2008 16:24:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,375,1220227200"; d="scan'208";a="170726164"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 07 Oct 2008 23:24:39 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m97NOd4k005763; 
	Tue, 7 Oct 2008 16:24:39 -0700
Received: from dwingwxp01 (dhcp-128-107-163-185.cisco.com [128.107.163.185])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m97NOduL021509;
	Tue, 7 Oct 2008 23:24:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Mark Andrews'" <Mark_Andrews@isc.org>, <v4v6interim@ietf.org>
References: Your message of "Tue, 07 Oct 2008 10:47:56
	+0300."<200810071047.56810.remi.denis-courmont@nokia.com>
	<200810072314.m97NE817079257@drugs.dv.isc.org>
Date: Tue, 7 Oct 2008 16:24:38 -0700
Message-ID: <015601c928d3$de512480$35666b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acko0m8puqnJruCZS6mRgIrkpjvc8QAANq7A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <200810072314.m97NE817079257@drugs.dv.isc.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=865; t=1223421879; x=1224285879;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=bzkH1ljYBxM8TvHREbYMr3nDpqQJw67rY/1VH1Z1TIY=;
	b=BtZ6D4P1C7LBNps3buW/jwAQUOHKi/umdiyXD3ijCl6DB9563kVjW2H7od
	B93CWSCalqoGBYO5Q4H4Jv86+SDQqcbk4p92bbGCd+G1KWRvjWhBqSx3DKMl
	mvz3sPJk+u;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Mailman-Approved-At: Tue, 07 Oct 2008 18:45:51 -0700
Cc: 'Marc Petit-Huguenin' <petithug@acm.org>
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

...
> 	Any IP stack which sets DF for UDP without the application
> 	requesting it is broken.
> 
> 	If you do want to be able to set DF for UDP you also need
> 	to have a way to tell the IP stack to fragment the UDP
> 	packet into fragements no larger than a certain size.

A procedure to perform UDP Path MTU Discovery is described in
http://tools.ietf.org/html/draft-petithuguenin-behave-stun-pmtud and uses the
'modern' RFC4821 technique (rather than RFC1191's technique that relies on
ICMP).  However, so far the BEHAVE working group has received few comments on
that draft.  I can only interpret the few comments to mean there is no
interest in the technique -- which frankly surprises me.  If it's interesting
or useful or it can be improved, please email the author (petithug@acm.org,
CC'd on this message) or behave@ietf.org.  Thanks!

-d

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct  8 00:14:07 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 356DF28C195;
	Wed,  8 Oct 2008 00:14:07 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3295128C1A1
	for <v4v6interim@core3.amsl.com>; Wed,  8 Oct 2008 00:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.689
X-Spam-Level: 
X-Spam-Status: No, score=-1.689 tagged_above=-999 required=5 tests=[AWL=0.260, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hRhroC6qrZby for <v4v6interim@core3.amsl.com>;
	Wed,  8 Oct 2008 00:14:05 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id 34EAF28C193
	for <v4v6interim@ietf.org>; Wed,  8 Oct 2008 00:14:05 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 7471F172D8;
	Wed,  8 Oct 2008 09:14:16 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 83FF0172D4;
	Wed,  8 Oct 2008 09:14:15 +0200 (CEST)
Message-ID: <48EC5D76.5080109@free.fr>
Date: Wed, 08 Oct 2008 09:12:54 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
In-Reply-To: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Iljitsch van Beijnum   (m/j/a) 10/7/08 3:46 PM:
> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_each_other 

Very clear article, and very nice reading :-).

It would have been more accurate, though, if the A+P and SAM approaches
would at least have been listed. (Having NAT64, DS Lite and IVI as the
complete list of solutions discussed "to make the IPv4 world talk to the
(future) IPv6 world" is missing something.)

Worth being remembered: SAM has more potential than other solutions for
IPv4-only clients to reach an IPv6 capable server that only has a shared 
IPv4 address (with a restricted port range, accessible via tunnels).

In particular, in draft-despres-SAM-v4v6coexistenceScenarios-00,
scenario C is as follows (simplified to have encapsulation in IPv6 only,
and complemented to show on it supports connections both ways).



+------+                                    +--------+   Global
| SAM  |           +---------+              |  SAM   |  Internet
| host |--site v6--| SAM CPE |-- ISP v6 ----| ISP GW |<--- v4 -->
+------+           +---------+              +--------+

   SAM <--- v4/v6 -->SAM1 SAM2<---- v4/v6 ---> SAM <----- v4 ---->
     :                    :                      :
     '- Port restricted   '- Stateless CPE       '--- Stateless GW
           socket interface


         <---- transparency to global v4 packets ----->
              (outgoing AND incoming connections)


Regards,

RD


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  9 05:44:17 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5663B3A68CD;
	Thu,  9 Oct 2008 05:44:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE6D13A68CD
	for <v4v6interim@core3.amsl.com>; Thu,  9 Oct 2008 05:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.053
X-Spam-Level: 
X-Spam-Status: No, score=-6.053 tagged_above=-999 required=5
	tests=[AWL=-0.104, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t5Qg4m0XSBwy for <v4v6interim@core3.amsl.com>;
	Thu,  9 Oct 2008 05:44:15 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id CBC043A68C3
	for <v4v6interim@ietf.org>; Thu,  9 Oct 2008 05:44:14 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AE8FF20E53; Thu,  9 Oct 2008 14:43:39 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-79-48edfc7adb28
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A00D220DF6; Thu,  9 Oct 2008 14:43:38 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 9 Oct 2008 14:43:31 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 9 Oct 2008 14:43:31 +0200
Message-ID: <48EDFC73.7080404@ericsson.com>
Date: Thu, 09 Oct 2008 14:43:31 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=
 <remi.denis-courmont@nokia.com>
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<48E6AEBD.9090205@gmail.com>	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>
	<200810071047.56810.remi.denis-courmont@nokia.com>
In-Reply-To: <200810071047.56810.remi.denis-courmont@nokia.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 09 Oct 2008 12:43:31.0331 (UTC)
	FILETIME=[A2A29D30:01C92A0C]
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

R=E9mi Denis-Courmont skrev:
> =

> For UDP, this needs to be implemented directly into the application-layer=
, =

> with some additional support from the IP stack (to allow sending too larg=
e =

> packets with DF bit). As yet, Linux is the only IP stack that explicitly =

> supports this via some "proprietary" socket API options. As for applicati=
ons, =

> it is difficult to gather meaningful data. But considering the lack of =

> support from lower layers, it is likely that this is mostly not implement=
ed. =

> I empirically believe that most applications simply have a "safe" hard-co=
ded =

> MTU for UDP, e.g. 1400 bytes or whatever.
> =


You can't make 4821 style PMTUD generic over UDP. The issue is of course
the feedback that needs to be integrated with the protocol. And that you
need to have some way of knowing exactly which packet is which.

When it comes to "safe", no value is truly safe and that is the issue.
Things starting to get really high success rates when you go down below
500 bytes, i.e. 576 - reasonable overhead. But even 1400 is to big in a
number of places for IPv4 networks. Also the tendency to make tunnels in
tunnels is one of the bigger issues about how much you should deduct.

Thus in addition to get TCP and SCTP stacks to implement 4821, have
application that uses other transport to also include solution we do
need a solution for the address family translation that support
fragmentation enabled to avoid black holes.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  9 07:26:24 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4520A3A6C20;
	Thu,  9 Oct 2008 07:26:24 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76C233A6C74
	for <v4v6interim@core3.amsl.com>; Thu,  9 Oct 2008 07:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZuLB5cqcgGwx for <v4v6interim@core3.amsl.com>;
	Thu,  9 Oct 2008 07:26:22 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id A1A8E3A6ABD
	for <v4v6interim@ietf.org>; Thu,  9 Oct 2008 07:26:22 -0700 (PDT)
Received: from ([128.244.96.104])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.118794736;
	Thu, 09 Oct 2008 10:26:43 -0400
Message-ID: <48EE14A3.2070007@innovationslab.net>
Date: Thu, 09 Oct 2008 10:26:43 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: v4v6interim@ietf.org
Subject: [v4v6interim] Minutes
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

All,
      The draft minutes are available for review on the wiki page
(http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim).  Please 
review and provide and comments, clarifications, or corrections to the 
chairs.

Regards,
Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  9 08:50:50 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3E613A698F;
	Thu,  9 Oct 2008 08:50:50 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 538833A698F
	for <v4v6interim@core3.amsl.com>; Thu,  9 Oct 2008 08:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id m+F540EC-E0Y for <v4v6interim@core3.amsl.com>;
	Thu,  9 Oct 2008 08:50:48 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id A9D7A3A68DF
	for <v4v6interim@ietf.org>; Thu,  9 Oct 2008 08:50:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,383,1220227200"; d="scan'208";a="93785704"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 09 Oct 2008 15:51:04 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m99Fp3eE030226; 
	Thu, 9 Oct 2008 08:51:03 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m99Fp3Es026417;
	Thu, 9 Oct 2008 15:51:03 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <v4v6interim@ietf.org>
References: <48EE14A3.2070007@innovationslab.net>
Date: Thu, 9 Oct 2008 08:51:04 -0700
Message-ID: <02d901c92a26$d5f29ae0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AckqGzir5HWRNL+aTxG6BPlGrslGVgAC2I3A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <48EE14A3.2070007@innovationslab.net>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=368; t=1223567463; x=1224431463;
	c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20Minutes |Sender:=20;
	bh=Tx7wjyl+GTxpKEU3faP2dFiyFsyh2aLcWHTMMOi6kOY=;
	b=Xk3jItd1dEIP5T0MMElDBXA9h5k44Kxj2SCAoODuRFf86W2TF+zI9uSN9o
	+BU06qOqDfVynCTlPhKtvohoDSpdHnHmzo9/nzbTndS+/s96S7ipaZwN7EZN
	41JL7nKLXx;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: 'David Miles' <David.Miles@alcatel-lucent.com>
Subject: Re: [v4v6interim] Minutes
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

>       The draft minutes are available for review on the wiki page
> (http://trac.tools.ietf.org/area/int/trac/wiki/v4v6interim).  Please 
> review and provide and comments, clarifications, or 
> corrections to the chairs.

And thanks to Fred Baker and David Miles for doing the minutes!  They
were excellent and used as-is with only formatting changes.

-d

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  9 13:23:24 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C1BD73A6A48;
	Thu,  9 Oct 2008 13:23:24 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAF693A6A48
	for <v4v6interim@core3.amsl.com>; Thu,  9 Oct 2008 13:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.078, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kyk75Jj3td63 for <v4v6interim@core3.amsl.com>;
	Thu,  9 Oct 2008 13:23:22 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180])
	by core3.amsl.com (Postfix) with ESMTP id 190D73A689D
	for <v4v6interim@ietf.org>; Thu,  9 Oct 2008 13:23:22 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so103309wag.5
	for <v4v6interim@ietf.org>; Thu, 09 Oct 2008 13:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=uEG29J0WtcK9niF5TQ1N81FFNeHHdALBqRfGCkWYROU=;
	b=T/GFhXOxZlntAAyseqeKg40WS0Tjs69cGh4zW6qgLZyg+/0XWFWmh3Trf58yhQImaq
	AbLqLyF0ziAhx8UMXwQWQKbUEVACSsz1II2mbFonHmUB6+Nr+04bpT8NMO20g6Z7I7gD
	8Z/VDwoQ1w1AzfG/TyJ1NeHOtU15BCO5EENFs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=Iq95P6bvHzYg6mNdCqrn87wYbg0PJziVPAErDqA+xaSQiuUoSE62sUI4ixp/eLTaCv
	idkwYJbX6iemA/N8ltwOAiERWrjU+t/EJ48y8Fr1sDNbXTZf9gIZewm+IyJKvXlm8+6b
	l9hlKDVoEe3GwtbqtBhpf1rlUJjz1U2U5enq0=
Received: by 10.114.150.1 with SMTP id x1mr848769wad.71.1223583845593;
	Thu, 09 Oct 2008 13:24:05 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l38sm823482waf.1.2008.10.09.13.24.02
	(version=SSLv3 cipher=RC4-MD5); Thu, 09 Oct 2008 13:24:04 -0700 (PDT)
Message-ID: <48EE685D.8090408@gmail.com>
Date: Fri, 10 Oct 2008 09:23:57 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>	<48E6AEBD.9090205@gmail.com>	<BB56240F3A190F469C52A57138047A03011DB57C@xmb-rtp-211.amer.cisco.com>	<200810071047.56810.remi.denis-courmont@nokia.com>
	<48EDFC73.7080404@ericsson.com>
In-Reply-To: <48EDFC73.7080404@ericsson.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

...
> When it comes to "safe", no value is truly safe and that is the issue.
> Things starting to get really high success rates when you go down below
> 500 bytes, i.e. 576 - reasonable overhead. But even 1400 is to big in a
> number of places for IPv4 networks. 

Yes, I'm just fighting a link a few hops from me that seems to have
an MTU of 1232, which transitions IPv6 into a big black hole...

   Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct  9 23:58:21 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1A2428C0E3;
	Thu,  9 Oct 2008 23:58:21 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9377528C0E3
	for <v4v6interim@core3.amsl.com>; Thu,  9 Oct 2008 23:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v0BguxyGaCN8 for <v4v6interim@core3.amsl.com>;
	Thu,  9 Oct 2008 23:58:19 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 6C6B23A6843
	for <v4v6interim@ietf.org>; Thu,  9 Oct 2008 23:58:19 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9A6wniq000832; Fri, 10 Oct 2008 09:59:02 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 09:58:58 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 09:58:57 +0300
Received: from esdhcp04051.research.nokia.com ([172.21.40.51]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 09:58:58 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Magnus Westerlund" <magnus.westerlund@ericsson.com>
Date: Fri, 10 Oct 2008 09:59:01 +0300
User-Agent: KMail/1.9.10
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<200810071047.56810.remi.denis-courmont@nokia.com>
	<48EDFC73.7080404@ericsson.com>
In-Reply-To: <48EDFC73.7080404@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810100959.02133.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 10 Oct 2008 06:58:58.0290 (UTC)
	FILETIME=[AAF4A520:01C92AA5]
X-Nokia-AV: Clean
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thursday 09 October 2008 15:43:31 ext Magnus Westerlund, you wrote:
> You can't make 4821 style PMTUD generic over UDP. The issue is of course
> the feedback that needs to be integrated with the protocol. And that you
> need to have some way of knowing exactly which packet is which.

I agree. I actually believe that this is one half one the problem: there is=
 no =

(semi-)standard way to do this with the a UDP BSDish socket.

To the best of my knowledge, Linux supports this through IP_MTU_DISCOVER, i=
n a =

awkward yet usable way. On Windows, you can set the DF bit, but that's abou=
t =

it. On BSD/OSX, you cannot even set the DF bit. I might be wrong.

> When it comes to "safe", no value is truly safe and that is the issue.
> Things starting to get really high success rates when you go down below
> 500 bytes, i.e. 576 - reasonable overhead. But even 1400 is to big in a
> number of places for IPv4 networks. Also the tendency to make tunnels in
> tunnels is one of the bigger issues about how much you should deduct.

Sure. In fact, my 3G provider sets an MTU of 1400 bytes, so sending UDP =

packets with 1400 bytes payload would be awfully bad.

> Thus in addition to get TCP and SCTP stacks to implement 4821, have
> application that uses other transport to also include solution we do
> need a solution for the address family translation that support
> fragmentation enabled to avoid black holes.

In Dublin, I thought we came to the conclusion that all significant IPv6 =

stacks supported the provision for fragmentating IPv6 even below 1280 bytes=
. =

If I understand correctly, they then send IPv6 packets with a fragment =

header, so that it is "easy" for the translation box to do its job.

As for IPv4 side, I think we have what we have and we cannot improve it muc=
h. =

If the application supports 4821, good. If not, then well, it might not wor=
k, =

with and without IPv6 translation. However, I think it would be (or have =

been) a good idea to promote an Informational socket API extension for =

RFC4821, so that apps can control the DF bit, fetch the known MTU, dequeue =

per-destination Too Big errors, etc.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 10 00:08:40 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 746A93A6AA5;
	Fri, 10 Oct 2008 00:08:40 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1C783A6800
	for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 00:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lSlaZ73q5nP8 for <v4v6interim@core3.amsl.com>;
	Fri, 10 Oct 2008 00:08:38 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168])
	by core3.amsl.com (Postfix) with ESMTP id 3A2AE3A67D8
	for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 00:08:38 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id q7so1062678uge.15
	for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=QJSF93ZcU9qNoC5oW5gtlZnj+ou17ulSTeDndxhDeAc=;
	b=BN/hhOnXUewNorfdslRCzBQXrlwNRngcpuhl/2AlBTcr4F0oL7vJ5psO/TTPFPjHue
	HEk6R0DHOzLC/7mb23aItJprtk5mPAKVRdWDu+Hb66Q+PfYbMSVpqgUss1gKjJi0at3g
	8nQ0F4ABXSocQVnuhwk8DytFChwLDQCgQBlJ8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=i4xWnSnFhLLO4OtAqk3SqCbUGRbSdf47gCnGroQpDGDTFTdL1n8E0Lv9n+3W1Kb5JQ
	EhWzOylQqibriJ87TNpEa8h+zftZd2OkP54eseZTWIc5TXly8pFMldh0weTCUgL7JGks
	iltw9F7R6CH09cqUhQVFvU/qNqyPf0XvB3THc=
Received: by 10.103.241.5 with SMTP id t5mr771384mur.72.1223622545251;
	Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
Received: by 10.103.249.10 with HTTP; Fri, 10 Oct 2008 00:09:05 -0700 (PDT)
Message-ID: <f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
Date: Fri, 10 Oct 2008 09:09:05 +0200
From: "Turchanyi Geza" <turchanyi.geza@gmail.com>
To: "=?ISO-8859-1?Q?R=E9mi_Despr=E9s?=" <remi.despres@free.fr>
In-Reply-To: <48EC5D76.5080109@free.fr>
MIME-Version: 1.0
Content-Disposition: inline
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
	<48EC5D76.5080109@free.fr>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Hello,

Well, SAM is an interesting idea.

HOWEVER: if we can implement new software (almost)everywhere, than why
not to use IPv6 everywhere?

I missed the point: what can be kept unchanged in the SAM scenario?

Thanks,

Geza

On Wed, Oct 8, 2008 at 9:12 AM, R=E9mi Despr=E9s <remi.despres@free.fr> wro=
te:
> Iljitsch van Beijnum   (m/j/a) 10/7/08 3:46 PM:
>>
>>
>> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4_talk_to_e=
ach_other
>
> Very clear article, and very nice reading :-).
>
> It would have been more accurate, though, if the A+P and SAM approaches
> would at least have been listed. (Having NAT64, DS Lite and IVI as the
> complete list of solutions discussed "to make the IPv4 world talk to the
> (future) IPv6 world" is missing something.)
>
> Worth being remembered: SAM has more potential than other solutions for
> IPv4-only clients to reach an IPv6 capable server that only has a shared
> IPv4 address (with a restricted port range, accessible via tunnels).
>
> In particular, in draft-despres-SAM-v4v6coexistenceScenarios-00,
> scenario C is as follows (simplified to have encapsulation in IPv6 only,
> and complemented to show on it supports connections both ways).
>
>
>
> +------+                                    +--------+   Global
> | SAM  |           +---------+              |  SAM   |  Internet
> | host |--site v6--| SAM CPE |-- ISP v6 ----| ISP GW |<--- v4 -->
> +------+           +---------+              +--------+
>
>  SAM <--- v4/v6 -->SAM1 SAM2<---- v4/v6 ---> SAM <----- v4 ---->
>    :                    :                      :
>    '- Port restricted   '- Stateless CPE       '--- Stateless GW
>          socket interface
>
>
>        <---- transparency to global v4 packets ----->
>             (outgoing AND incoming connections)
>
>
> Regards,
>
> RD
>
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 10 05:41:04 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B970228C156;
	Fri, 10 Oct 2008 05:41:04 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68A733A69C3
	for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 05:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.708
X-Spam-Level: 
X-Spam-Status: No, score=-1.708 tagged_above=-999 required=5 tests=[AWL=0.241, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vtwPoyGeUNpx for <v4v6interim@core3.amsl.com>;
	Fri, 10 Oct 2008 05:40:59 -0700 (PDT)
Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65])
	by core3.amsl.com (Postfix) with ESMTP id 7CD823A6947
	for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 05:40:59 -0700 (PDT)
Received: from smtp8-g19.free.fr (localhost [127.0.0.1])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 941D932A7E4;
	Fri, 10 Oct 2008 14:40:51 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 18A3C32A7CA;
	Fri, 10 Oct 2008 14:40:51 +0200 (CEST)
Message-ID: <48EF4D03.6080505@free.fr>
Date: Fri, 10 Oct 2008 14:39:31 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Turchanyi Geza <turchanyi.geza@gmail.com>, v4v6interim@ietf.org
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>	
	<48EC5D76.5080109@free.fr>
	<f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
In-Reply-To: <f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Turchanyi Geza   (m/j/a) 10/10/08 9:09 AM:
> Hello,
> 
> Well, SAM is an interesting idea.
> 
> HOWEVER: if we can implement new software (almost)everywhere, than why
> not to use IPv6 everywhere?

Two points.
- For SAM to be useful, it doesn't need at all to be available 
everywhere, or even "almost" everywhere: if an ISP has it, its clients 
that also have it can take advantage of its properties (deployment is 
incremental).
- In scenario C, although the customer site has no global IPv4 address 
reserved for it, its SAM hosts are reachable, without NAT traversal, by 
IPv4-only remote clients.

> I missed the point: what can be kept unchanged in the SAM scenario?
In scenario C below, an IPv4 datagram exchanged between the SAM host and 
any remote host that requires the connection to be IPv4 is unchanged 
end-to end. Both source and destination addresses and ports of the 
datagram, and its protocol, are received as sent (5-tuple preservation). 
The IPv4 only host ignores that encapsulation in IPv6 has taken place 
somewhere.

5-tuples being neither restricted nor modified E2E, the solution is more 
general than those that impose NAT traversal. In particular, it ensures 
compatibility with SCTP and with any other transport protocol that may 
be useful in the future.

Regards,

RD

>> Worth being remembered: SAM has more potential than other solutions for
>> IPv4-only clients to reach an IPv6 capable server that only has a shared
>> IPv4 address (with a restricted port range, accessible via tunnels).
>>
>> In particular, in draft-despres-SAM-v4v6coexistenceScenarios-00,
>> scenario C is as follows (simplified to have encapsulation in IPv6 only,
>> and complemented to show on it supports connections both ways).
>>
>>
>>
>> +------+                                    +--------+   Global
>> | SAM  |           +---------+              |  SAM   |  Internet
>> | host |--site v6--| SAM CPE |-- ISP v6 ----| ISP GW |<--- v4 -->
>> +------+           +---------+              +--------+
>>
>>  SAM <--- v4/v6 -->SAM1 SAM2<---- v4/v6 ---> SAM <----- v4 ---->
>>    :                    :                      :
>>    '- Port restricted   '- Stateless CPE       '--- Stateless GW
>>          socket interface
>>
>>
>>        <---- transparency to global v4 packets ----->
>>             (outgoing AND incoming connections)
>>
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 10 07:44:55 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4668C28C118;
	Fri, 10 Oct 2008 07:44:55 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC49828C118
	for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 07:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DKmnLqw3tCqZ for <v4v6interim@core3.amsl.com>;
	Fri, 10 Oct 2008 07:44:53 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36])
	by core3.amsl.com (Postfix) with ESMTP id 18B9828C111
	for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 07:44:53 -0700 (PDT)
Received: from ip192.186.dsl-acs2.seawa0.iinet.com ([209.20.186.192]
	helo=rmac.psg.com) by ran.psg.com with esmtpsa (SSLv3:AES256-SHA:256)
	(Exim 4.69 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1KoJFG-0008mv-48; Fri, 10 Oct 2008 14:45:34 +0000
Message-ID: <48EF6A8D.4080500@psg.com>
Date: Fri, 10 Oct 2008 07:45:33 -0700
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Turchanyi Geza <turchanyi.geza@gmail.com>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>	<48EC5D76.5080109@free.fr>
	<f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
In-Reply-To: <f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> HOWEVER: if we can implement new software (almost)everywhere

we have these pesky things called "customers."

randy
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 10 08:32:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DA9628C19A;
	Fri, 10 Oct 2008 08:32:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA17028C15C
	for <v4v6interim@core3.amsl.com>; Fri, 10 Oct 2008 08:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.387
X-Spam-Level: 
X-Spam-Status: No, score=-6.387 tagged_above=-999 required=5
	tests=[AWL=-0.088, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dSHn9X07JtZv for <v4v6interim@core3.amsl.com>;
	Fri, 10 Oct 2008 08:32:36 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id E408428C15F
	for <v4v6interim@ietf.org>; Fri, 10 Oct 2008 08:32:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,390,1220227200"; d="scan'208";a="172686414"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 10 Oct 2008 15:33:16 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9AFXGDI031541; 
	Fri, 10 Oct 2008 08:33:16 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9AFXFhZ012921;
	Fri, 10 Oct 2008 15:33:15 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Turchanyi Geza'" <turchanyi.geza@gmail.com>,
	"=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr>
	<f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
Date: Fri, 10 Oct 2008 08:33:15 -0700
Message-ID: <01d501c92aed$8385f5a0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AckqpztTFLnkViY1SYmDIVstrLrXGgARaCzg
In-Reply-To: <f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2839; t=1223652796;
	x=1224516796; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=FiK+4X4Qwb5DkLZaHOyvRkYQ9soTRn4Tvubv98/V1/k=;
	b=RLiT5F8dO6bJvijY3VG9muM7ouoWgCy9b7DgdEBwKFdngfkNgjNkrSSw0i
	yqYiw1se99j/9wYxLB/o8/iEuvlW7CXMV8dPUORm2hjE8xoXLEY5njwd+Guh
	YuZ1q1TCxq;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 =


> -----Original Message-----
> From: v4v6interim-bounces@ietf.org =

> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Turchanyi Geza
> Sent: Friday, October 10, 2008 12:09 AM
> To: R=E9mi Despr=E9s
> Cc: v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
> =

> Hello,
> =

> Well, SAM is an interesting idea.
> =

> HOWEVER: if we can implement new software (almost)everywhere, than why
> not to use IPv6 everywhere?

Because there is no content on IPv6 yet.  Visit
http://www.alexa.com/site/ds/top_sites?ts_mode=3Dglobal&lang=3Dnone and
do AAAA queries against those websites.

-d


> I missed the point: what can be kept unchanged in the SAM scenario?
> =

> Thanks,
> =

> Geza
> =

> On Wed, Oct 8, 2008 at 9:12 AM, R=E9mi Despr=E9s =

> <remi.despres@free.fr> wrote:
> > Iljitsch van Beijnum   (m/j/a) 10/7/08 3:46 PM:
> >>
> >>
> >> =

> http://digg.com/tech_news/IETF_working_on_making_IPv6_and_IPv4
> _talk_to_each_other
> >
> > Very clear article, and very nice reading :-).
> >
> > It would have been more accurate, though, if the A+P and =

> SAM approaches
> > would at least have been listed. (Having NAT64, DS Lite and =

> IVI as the
> > complete list of solutions discussed "to make the IPv4 =

> world talk to the
> > (future) IPv6 world" is missing something.)
> >
> > Worth being remembered: SAM has more potential than other =

> solutions for
> > IPv4-only clients to reach an IPv6 capable server that only =

> has a shared
> > IPv4 address (with a restricted port range, accessible via tunnels).
> >
> > In particular, in draft-despres-SAM-v4v6coexistenceScenarios-00,
> > scenario C is as follows (simplified to have encapsulation =

> in IPv6 only,
> > and complemented to show on it supports connections both ways).
> >
> >
> >
> > +------+                                    +--------+   Global
> > | SAM  |           +---------+              |  SAM   |  Internet
> > | host |--site v6--| SAM CPE |-- ISP v6 ----| ISP GW |<--- v4 -->
> > +------+           +---------+              +--------+
> >
> >  SAM <--- v4/v6 -->SAM1 SAM2<---- v4/v6 ---> SAM <----- v4 ---->
> >    :                    :                      :
> >    '- Port restricted   '- Stateless CPE       '--- Stateless GW
> >          socket interface
> >
> >
> >        <---- transparency to global v4 packets ----->
> >             (outgoing AND incoming connections)
> >
> >
> > Regards,
> >
> > RD
> >
> >
> > _______________________________________________
> > v4v6interim mailing list
> > v4v6interim@ietf.org
> > https://www.ietf.org/mailman/listinfo/v4v6interim
> >
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 01:54:26 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE80A3A6AED;
	Sat, 11 Oct 2008 01:54:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB1553A6AED
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 01:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ROvgPvj1jg-N for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 01:54:24 -0700 (PDT)
Received: from mail.fit.nokia.com (unknown [IPv6:2001:2060:40:1::123])
	by core3.amsl.com (Postfix) with ESMTP id 90C233A67EE
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 01:54:24 -0700 (PDT)
Received: from [192.168.255.2] (a88-114-157-111.elisa-laajakaista.fi
	[88.114.157.111]) (authenticated bits=0)
	by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id m9B8scQx010210
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 11 Oct 2008 11:54:38 +0300 (EEST)
	(envelope-from lars.eggert@nokia.com)
Message-Id: <3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Dan Wing <dwing@cisco.com>
In-Reply-To: <01d501c92aed$8385f5a0$c2f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 11 Oct 2008 10:54:37 +0200
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr>
	<f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
	<01d501c92aed$8385f5a0$c2f0200a@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV 0.94/8411/Sat Oct 11 05:40:28 2008 on fit.nokia.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(mail.fit.nokia.com [212.213.221.39]);
	Sat, 11 Oct 2008 11:54:45 +0300 (EEST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-10, at 17:33, ext Dan Wing wrote:
> Because there is no content on IPv6 yet.  Visit
> http://www.alexa.com/site/ds/top_sites?ts_mode=global&lang=none and
> do AAAA queries against those websites.

Or go to http://utility.nokia.net/~lars/meter/ipv6.html, which does  
this for you :-)

Lars
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 05:01:30 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CD5D3A6900;
	Sat, 11 Oct 2008 05:01:30 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E61503A683C
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 05:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.382
X-Spam-Level: 
X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[AWL=0.617, 
	BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dARkplw6jClS for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 05:01:28 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 979A13A6874
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 05:01:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,393,1220227200"; d="scan'208";a="22329039"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 11 Oct 2008 12:01:56 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9BC1tlU013314; 
	Sat, 11 Oct 2008 14:01:56 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9BC1ufg009884;
	Sat, 11 Oct 2008 12:01:56 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Oct 2008 14:01:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 11 Oct 2008 14:02:22 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] You have been dugg!
Thread-Index: AckrfxfUvN0TfeooQx+QWJ9GQ0A9bQAGX/GA
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "Dan Wing (dwing)" <dwing@cisco.com>
X-OriginalArrivalTime: 11 Oct 2008 12:01:55.0824 (UTC)
	FILETIME=[2805F700:01C92B99]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1649; t=1223726516;
	x=1224590516; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug
	g! |Sender:=20;
	bh=wOhfhCV5WLzzwt5549hxrJRLFqZ1IZE1aqMAjfyS6b4=;
	b=iMAEgRBJvDhZ2DVin+JIXIWmu+YWrfAnP0BqsSPP4xicqIIvyxZX4gaK+w
	5VWWdqliV3AcwaDakDZP1ylYGbFuuVu42AJPVGJvUAw0GB8KUoqWnTlIYDZW
	syTLNmCZMQ;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Interesting and disappointing at the same time. Is there any chance to get =
another version of the same statistics where not only www.example.com will =
be queried but also www6.example.com ipv6.example.com (this is of course a =
vastly different metric but could also be useful).

To come back to Dan's email, is there a way to get alexa statistics weigthe=
d by the %-age of global Internet traffic? I.e. if the first 10 sites were =
on IPv6, how much Internet traffic would be over IPv6? =


And if you put the web server sites IPv6 readiness (cfr Lars' email) and th=
e client IPv6 readiness (cfr discussion on v6ops -- roughly 6-10% of client=
s can access IP6 only site), this is a factual confirmation that the conten=
t site is lagging... (which is of course easier to fix than the client site=
).

Regards

-=E9ric =


> -----Original Message-----
> From: v4v6interim-bounces@ietf.org =

> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Lars Eggert
> Sent: samedi 11 octobre 2008 10:55
> To: Dan Wing (dwing)
> Cc: v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
> =

> On 2008-10-10, at 17:33, ext Dan Wing wrote:
> > Because there is no content on IPv6 yet.  Visit =

> > =

> http://www.alexa.com/site/ds/top_sites?ts_mode=3Dglobal&lang=3Dnon
> e and do =

> > AAAA queries against those websites.
> =

> Or go to http://utility.nokia.net/~lars/meter/ipv6.html, =

> which does this for you :-)
> =

> Lars
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
> =

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 08:13:16 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B5173A6781;
	Sat, 11 Oct 2008 08:13:16 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2E3E3A6830
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 08:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PcYJIRiRcSpz for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 08:13:14 -0700 (PDT)
Received: from mail.fit.nokia.com (unknown [IPv6:2001:2060:40:1::123])
	by core3.amsl.com (Postfix) with ESMTP id E51333A6774
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 08:13:13 -0700 (PDT)
Received: from [192.168.255.2] (a88-114-157-111.elisa-laajakaista.fi
	[88.114.157.111]) (authenticated bits=0)
	by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id m9BFDSY6011448
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 11 Oct 2008 18:13:29 +0300 (EEST)
	(envelope-from lars.eggert@nokia.com)
Message-Id: <0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Eric Vyncke (evyncke) <evyncke@cisco.com>
In-Reply-To: <CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 11 Oct 2008 18:13:28 +0300
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV 0.94/8412/Sat Oct 11 15:30:20 2008 on fit.nokia.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(mail.fit.nokia.com [212.213.221.39]);
	Sat, 11 Oct 2008 18:13:34 +0300 (EEST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-11, at 15:02, ext Eric Vyncke (evyncke) wrote:
> Interesting and disappointing at the same time. Is there any chance  
> to get another version of the same statistics where not only www.example.com 
>  will be queried but also www6.example.com ipv6.example.com (this is  
> of course a vastly different metric but could also be useful).

Good suggestion. I'll add that when I have a minute, I need to fix a  
bug related to DKIM tracking anyway. Any other prefixes that www6 and  
ipv6 that I should check?

(The spike you see in the history plot around August was due to a  
similar change - I started doing lookups for www.example.com in  
addition to just example.com.)

Lars
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 08:15:35 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EC1C3A6900;
	Sat, 11 Oct 2008 08:15:35 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF0233A6887
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 08:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fb+Cb+rvxL53 for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 08:15:33 -0700 (PDT)
Received: from mail.fit.nokia.com (unknown [IPv6:2001:2060:40:1::123])
	by core3.amsl.com (Postfix) with ESMTP id B47F13A68B8
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 08:15:32 -0700 (PDT)
Received: from [192.168.255.2] (a88-114-157-111.elisa-laajakaista.fi
	[88.114.157.111]) (authenticated bits=0)
	by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id m9BFElPu011452
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 11 Oct 2008 18:14:47 +0300 (EEST)
	(envelope-from lars.eggert@nokia.com)
Message-Id: <2B4CBF2E-A692-4667-84FD-22510BEA2798@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Eric Vyncke (evyncke) <evyncke@cisco.com>
In-Reply-To: <CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 11 Oct 2008 18:14:47 +0300
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV 0.94/8412/Sat Oct 11 15:30:20 2008 on fit.nokia.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(mail.fit.nokia.com [212.213.221.39]);
	Sat, 11 Oct 2008 18:14:53 +0300 (EEST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-11, at 15:02, ext Eric Vyncke (evyncke) wrote:
> To come back to Dan's email, is there a way to get alexa statistics  
> weigthed by the %-age of global Internet traffic? I.e. if the first  
> 10 sites were on IPv6, how much Internet traffic would be over IPv6?

Not through Alexa alone. If anyone has pointers to data that I could  
correlate the stats with, that'd be great.

(Or, ideally, a willing operator would share their aggregate DNS  
lookup stats & traffic loads...)

Lars
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 08:48:50 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79FA53A6A43;
	Sat, 11 Oct 2008 08:48:50 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96D793A6A43
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 08:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.536
X-Spam-Level: 
X-Spam-Status: No, score=-6.536 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6XeTwfu8cid1 for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 08:48:48 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id AD1AC3A6774
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 08:48:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,393,1220227200"; d="scan'208";a="94391790"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 11 Oct 2008 15:48:43 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9BFmhOD013004; 
	Sat, 11 Oct 2008 08:48:43 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9BFmhOL004092;
	Sat, 11 Oct 2008 15:48:43 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>,
	"'ext Eric Vyncke \(evyncke\)'" <evyncke@cisco.com>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
	<0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
Date: Sat, 11 Oct 2008 08:48:43 -0700
Message-ID: <088a01c92bb8$d6c71d40$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ackrs/4oXzRrtqbIQCGLJHVZdvYCKQABG6xg
In-Reply-To: <0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1229; t=1223740123;
	x=1224604123; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=dfMB5pNex1T4NY0afxSOWmhoqd1ZmJtmzCVAlTkMAY8=;
	b=OZTkqY42MzApFvZhtSptTmcCtfL9KrYpdnVdRaqNDhbIK7Nf2RSwuq6Sgm
	qAczlBVwg+xYJKtZA9L5kaIRszqpRK37UwffonhBM7EpRMd1Iinfnc5kT67x
	uYaA2Bi44f;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] 
> Sent: Saturday, October 11, 2008 8:13 AM
> To: ext Eric Vyncke (evyncke)
> Cc: Dan Wing (dwing); v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
> 
> On 2008-10-11, at 15:02, ext Eric Vyncke (evyncke) wrote:
> > Interesting and disappointing at the same time. Is there 
> any chance  
> > to get another version of the same statistics where not 
> only www.example.com 
> >  will be queried but also www6.example.com ipv6.example.com 
> (this is  
> > of course a vastly different metric but could also be useful).
> 
> Good suggestion. I'll add that when I have a minute, I need to fix a  
> bug related to DKIM tracking anyway. Any other prefixes that 
> www6 and ipv6 that I should check?

Are users expected to know of, and use those URLs?  They can't be 
forwarded in email or IM to someone running IPv4-only -- which 
is the ultimate 'referral' (so often talked about abstractly 
by IETFers).

-d


> (The spike you see in the history plot around August was due to a  
> similar change - I started doing lookups for www.example.com in  
> addition to just example.com.)
> 
> Lars

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 08:49:01 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A03393A6B2A;
	Sat, 11 Oct 2008 08:49:01 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 799853A6774
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 08:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hDLBMhfrhNjk for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 08:48:59 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 9409E3A6A95
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 08:48:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,393,1220227200"; d="scan'208";a="173258584"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 11 Oct 2008 15:48:59 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9BFmxbJ022595; 
	Sat, 11 Oct 2008 08:48:59 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9BFmwj4014501;
	Sat, 11 Oct 2008 15:48:59 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Lars Eggert'" <lars.eggert@nokia.com>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr>
	<f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com>
	<01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
Date: Sat, 11 Oct 2008 08:48:58 -0700
Message-ID: <088b01c92bb8$dffce700$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ackrfw+jjlv08Q65RGGALoii7gGw5AAOc4lw
In-Reply-To: <3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=622; t=1223740139; x=1224604139;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=+m5372nnYj6OdEu1A/0BAqv3QcdUpEPGNKljFoRiPCE=;
	b=ZM/UUwBM21FE5+8POHyOCmzcP1zgsznIIejxF/e2immn9RRP9IR55MvYVK
	mnX9PmxlrAbcpeU8WyY7FoiBpT4R9ESMH0VVgPP0TyD9ie+bhl9GVB18zUvo
	dHe6mm82El;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 =


> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] =

> Sent: Saturday, October 11, 2008 1:55 AM
> To: ext Dan Wing
> Cc: 'Turchanyi Geza'; "'R=E9mi Despr=E9s'"; v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
> =

> On 2008-10-10, at 17:33, ext Dan Wing wrote:
> > Because there is no content on IPv6 yet.  Visit
> > http://www.alexa.com/site/ds/top_sites?ts_mode=3Dglobal&lang=3Dnone and
> > do AAAA queries against those websites.
> =

> Or go to http://utility.nokia.net/~lars/meter/ipv6.html, which does  =

> this for you :-)

Thanks.
-d

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 08:51:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8E963A6B02;
	Sat, 11 Oct 2008 08:51:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4722C3A6A93
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 08:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.77
X-Spam-Level: 
X-Spam-Status: No, score=-5.77 tagged_above=-999 required=5 tests=[AWL=0.829, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NA6sK4i4VGCN for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 08:51:40 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0CBB13A677E
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 08:51:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,393,1220227200"; d="scan'208";a="22333479"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 11 Oct 2008 15:51:58 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9BFpwXa004944; 
	Sat, 11 Oct 2008 17:51:58 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9BFpwEn028003;
	Sat, 11 Oct 2008 15:51:58 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Oct 2008 17:51:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 11 Oct 2008 17:52:28 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE0079FEEF2@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <088a01c92bb8$d6c71d40$c2f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] You have been dugg!
Thread-Index: Ackrs/4oXzRrtqbIQCGLJHVZdvYCKQABG6xgAAArNwA=
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
	<0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
	<088a01c92bb8$d6c71d40$c2f0200a@cisco.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>, "Lars Eggert" <lars.eggert@nokia.com>
X-OriginalArrivalTime: 11 Oct 2008 15:51:58.0257 (UTC)
	FILETIME=[4AEA1A10:01C92BB9]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1068; t=1223740318;
	x=1224604318; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug
	g! |Sender:=20;
	bh=WeVxXhhrVaJWErHITzgdo8ZG1bzJPz/JbbR68uv7K5A=;
	b=SweKWj9ETee+ru7llh83zVVbU5+V7FXsB76zeMJAkYx0MnHcsxnS5rbywK
	LfRa1wlEvlJm0YqwwX6i3hXBeWPYPC576SSXsUwOrfXeHGznRMP1Gl91W7xO
	D4MVCnCsqg;
Authentication-Results: ams-dkim-2; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> > > Interesting and disappointing at the same time. Is there
> > any chance
> > > to get another version of the same statistics where not
> > only www.example.com
> > >  will be queried but also www6.example.com ipv6.example.com
> > (this is
> > > of course a vastly different metric but could also be useful).
> > =

> > Good suggestion. I'll add that when I have a minute, I need =

> to fix a =

> > bug related to DKIM tracking anyway. Any other prefixes that
> > www6 and ipv6 that I should check?
> =

> Are users expected to know of, and use those URLs?  They =

> can't be forwarded in email or IM to someone running =

> IPv4-only -- which is the ultimate 'referral' (so often =

> talked about abstractly by IETFers).

Dan,

No of course, but, I would be really nice if Lars could extend his page wit=
h both statistics for pure dual-stack www.example.com and with statistics f=
or the bare minimum www6.example.com & ipv6.example.com. This would give us=
 useful information (at least from my point of view).

Regards

-=E9ric
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 11 15:06:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B7223A68B9;
	Sat, 11 Oct 2008 15:06:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 650043A68B9
	for <v4v6interim@core3.amsl.com>; Sat, 11 Oct 2008 15:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Cu8sbahOiKUa for <v4v6interim@core3.amsl.com>;
	Sat, 11 Oct 2008 15:06:02 -0700 (PDT)
Received: from mail.fit.nokia.com (unknown [IPv6:2001:2060:40:1::123])
	by core3.amsl.com (Postfix) with ESMTP id 667C93A6808
	for <v4v6interim@ietf.org>; Sat, 11 Oct 2008 15:06:02 -0700 (PDT)
Received: from [192.168.255.2] (a88-114-157-111.elisa-laajakaista.fi
	[88.114.157.111]) (authenticated bits=0)
	by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id m9BM6XBM012742
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sun, 12 Oct 2008 01:06:36 +0300 (EEST)
	(envelope-from lars.eggert@nokia.com)
Message-Id: <0F4B8136-03EA-484E-877F-7447BE8DCE93@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: ext Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 12 Oct 2008 01:06:33 +0300
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><48EC5D76.5080109@free.fr><f1110c510810100009r51bf3553n999ef0489f4dff03@mail.gmail.com><01d501c92aed$8385f5a0$c2f0200a@cisco.com>
	<3285FCFA-047D-405F-9DF0-DA6CE637AD0E@nokia.com>
	<CE2BF2A7B1008C459FD7978065C6ECE0079FEED7@xmb-ams-33a.emea.cisco.com>
	<0053A018-9FB0-44AC-9DB0-AD87BB2A909E@nokia.com>
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV 0.94/8412/Sat Oct 11 15:30:20 2008 on fit.nokia.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0
	(mail.fit.nokia.com [212.213.221.39]);
	Sun, 12 Oct 2008 01:06:43 +0300 (EEST)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I made these changes. The new dataset will be gathered 1AM PST.

Lars

On 2008-10-11, at 18:13, ext Lars Eggert wrote:
> On 2008-10-11, at 15:02, ext Eric Vyncke (evyncke) wrote:
>> Interesting and disappointing at the same time. Is there any chance  
>> to get another version of the same statistics where not only www.example.com 
>>  will be queried but also www6.example.com ipv6.example.com (this  
>> is of course a vastly different metric but could also be useful).
>
> Good suggestion. I'll add that when I have a minute, I need to fix a  
> bug related to DKIM tracking anyway. Any other prefixes that www6  
> and ipv6 that I should check?
>
> (The spike you see in the history plot around August was due to a  
> similar change - I started doing lookups for www.example.com in  
> addition to just example.com.)
>
> Lars
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 05:41:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7A7E3A698E;
	Mon, 13 Oct 2008 05:41:53 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 210D73A6841
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 05:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RoHGqHPnPbi1 for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 05:41:51 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id EDB2F3A6883
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 05:41:50 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9DCg0h0033140
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 13 Oct 2008 14:42:00 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 14:42:16 +0200
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
	<7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 7 okt 2008, at 19:26, Fred Baker wrote:

> What does it mean to be "IPv6-like"?

That everything happens mostly automatic and is easy otherwise. For  
instance, in IPv4 you have to think about how big each subnet is. In  
IPv6 you don't.

> The one point of disagreement that I have had with Marcello's  
> Pref64::/96 characterization is that it does something that RFC 4291  
> says to not do. If we have a prefix whose left-most bits are not  
> 000, we are supposed to reserve the right-most 64 bits for host  
> identifier

Yes, I know. What I don't know is why this text was put in the RFC, so  
far nobody has been able (or willing) to tell me that.

> As such, neglecting the question of using the 0::ffff:a.b.c.d,  
> 0::0:a.b.c.d, or 0::ffff:0:a.b.c.d forms, if I have a prefix  
> assigned by the network operator, the address architecture says that  
> I would have to treat all Pref64::a.b.c.d routes as host routes.  
> Tell me that this is not what you're hoping for in an IPv6 address?

Not entirely sure what you're trying to say. But obviously we can  
specify the behavior that we want in a new specification so I don't  
know why it would matter.

> What CERNET has done is define an address that maps to RFC 4291's  
> architecture, allows them to (within that architecture) subnet IPv4- 
> mapped addresses in the IPv6 domain, and use the mapping effectively  
> in routing. If there is anything that I would hope was IPv6-like, it  
> would have those characteristics.

> All you do is crab; you don't like it, but you don't give a  
> technical reason to not like it. What's your point?

The IVI mapping means that at the very least a special subnet has to  
be created for every IPv4-reachable host. The suggestion of having  
non-/64 subnets and DHCPv6 is very problematic because DHCPv6 doesn't  
know about subnet prefix lengths.

The situation where a static mapping is set up means that the  
configuration can be limited to the translation box, this simply makes  
much more sense on every level.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:22:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A71FE3A6A5C;
	Mon, 13 Oct 2008 15:22:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D001628C0FE
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.488
X-Spam-Level: 
X-Spam-Status: No, score=-106.488 tagged_above=-999 required=5
	tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 65rBgQEAK5E8 for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:22:48 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 068D53A67A7
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:22:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="48826759"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 13 Oct 2008 22:23:28 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMNSDQ001365; 
	Mon, 13 Oct 2008 15:23:28 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMNSw2002225;
	Mon, 13 Oct 2008 22:23:28 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 15:23:28 -0700
Received: from [10.2.5.36] ([10.21.70.94]) by xfe-sjc-211.amer.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Oct 2008 15:23:27 -0700
Message-Id: <8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 15:23:26 -0700
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
	<7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>
	<290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 13 Oct 2008 22:23:28.0137 (UTC)
	FILETIME=[50CCD790:01C92D82]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1637; t=1223936608;
	x=1224800608; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=nKSVSUFJuTXEF3GqklbAktp+cPuAKMuWTHI4iOBSzSE=;
	b=MwnMjKou8a12x8N96hrmdKHb+nqLGxYZNw2vxdXAeB4Ta6uxpDh92zhcPi
	je/QswzTce0MRU6FOxZK4ruGf8W0Xl4iVZZl8MMu/Azm3L4Td+1hx4fP00rZ
	hsdxqNHhZmTFJSDRutVOoxaOviph8FevYT+t6nBYgAvlYptPPUpKQ=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 13, 2008, at 5:42 AM, Iljitsch van Beijnum wrote:

> On 7 okt 2008, at 19:26, Fred Baker wrote:
>
>> What does it mean to be "IPv6-like"?
>
> That everything happens mostly automatic and is easy otherwise. For  
> instance, in IPv4 you have to think about how big each subnet is. In  
> IPv6 you don't.

I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.  
And btw this is about a IPv4 address, like NAT64 etc are. You make  
relatively positive statements about the other options and dump on one  
that has the same strengths and weaknesses.

> The IVI mapping means that at the very least a special subnet has to  
> be created for every IPv4-reachable host. The suggestion of having  
> non-/64 subnets and DHCPv6 is very problematic because DHCPv6  
> doesn't know about subnet prefix lengths.


we have a way to assign a prefix using DHCP. You're telling me it  
doesn't know the prefix length? If so, it's broken. I haven't read  
that spec; remind me which it is?

And yes, regardless of the address format used - even SLACK, for that  
matter - one has to either inject a host route into routing or inject  
a prefix into routing. That's how routing works. The only way we can  
avoid that is to put every mapped-address host on a LAN shared with  
the translator. Bzzt. That doesn't scale.

> The situation where a static mapping is set up means that the  
> configuration can be limited to the translation box, this simply  
> makes much more sense on every level.

Actually, not so. And this differs from NAT64, which you spoke  
positively about, in what way?
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:33:52 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73CE028C17A;
	Mon, 13 Oct 2008 15:33:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B98753A69F6
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ybzkEKil6RiT for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:33:49 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id AF5AC3A67A7
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:33:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="24114229"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 13 Oct 2008 22:34:26 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMYPWu002598; 
	Mon, 13 Oct 2008 18:34:25 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMYPMm015271;
	Mon, 13 Oct 2008 22:34:26 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:34:25 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 18:33:25 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] You have been dugg!
Thread-Index: Acktgnaa4EuQcjKbQ0uBdG5VhKqXfAAANyTw
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 13 Oct 2008 22:34:25.0960 (UTC)
	FILETIME=[D8E4AA80:01C92D83]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2444; t=1223937266;
	x=1224801266; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20
	|To:=20=22Fred=20Baker=20(fred)=22=20<fred@cisco.com>,=0A=2
	0=20=20=20=20=20=20=20=22Iljitsch=20van=20Beijnum=22=20<ilji
	tsch@muada.com>;
	bh=/d4Xkwz+O+/EqmD0uuwdjlj66oKIi6bvTGy2So7SGGg=;
	b=ll9pZ540lE1u8+kiSRnawT/vyyQgZW/H62iE4Z7caJGvEyxhhqbwRZyihr
	x7YxKgJWTEo3zCCob63B2yjzw+nL/B1W/P1A9iS5w3uCl256iK4xXOYEOCcX
	z+5vnTSuSG;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I haven't had the time to catch up to these emails and get a proper
perspective.  But just a quick comment that DHCPv6 is not broken if
DHCPv6 responses from the server to the client do not include prefix
length - that's by design of the IPv6 architecture where the router on
the network is responsible for doling out the prefix length to the
clients and NOT the DHCPv6 server.

Hemant 

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Fred Baker (fred)
Sent: Monday, October 13, 2008 6:23 PM
To: Iljitsch van Beijnum
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!


On Oct 13, 2008, at 5:42 AM, Iljitsch van Beijnum wrote:

> On 7 okt 2008, at 19:26, Fred Baker wrote:
>
>> What does it mean to be "IPv6-like"?
>
> That everything happens mostly automatic and is easy otherwise. For 
> instance, in IPv4 you have to think about how big each subnet is. In
> IPv6 you don't.

I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.  
And btw this is about a IPv4 address, like NAT64 etc are. You make
relatively positive statements about the other options and dump on one
that has the same strengths and weaknesses.

> The IVI mapping means that at the very least a special subnet has to 
> be created for every IPv4-reachable host. The suggestion of having
> non-/64 subnets and DHCPv6 is very problematic because DHCPv6 doesn't 
> know about subnet prefix lengths.


we have a way to assign a prefix using DHCP. You're telling me it
doesn't know the prefix length? If so, it's broken. I haven't read that
spec; remind me which it is?

And yes, regardless of the address format used - even SLACK, for that
matter - one has to either inject a host route into routing or inject a
prefix into routing. That's how routing works. The only way we can avoid
that is to put every mapped-address host on a LAN shared with the
translator. Bzzt. That doesn't scale.

> The situation where a static mapping is set up means that the 
> configuration can be limited to the translation box, this simply makes

> much more sense on every level.

Actually, not so. And this differs from NAT64, which you spoke
positively about, in what way?
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:47:07 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31BF03A680B;
	Mon, 13 Oct 2008 15:47:07 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF8EB3A680B
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id flGA7x3Az77n for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:47:05 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id 08D133A67A7
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:47:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="48833246"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 13 Oct 2008 22:48:00 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMm0nn003424; 
	Mon, 13 Oct 2008 15:48:00 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMm06k020539;
	Mon, 13 Oct 2008 22:48:00 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 15:47:59 -0700
Received: from dhcp-128-107-98-124.cisco.com ([128.107.98.124]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 15:47:59 -0700
Message-Id: <0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 15:47:58 -0700
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 13 Oct 2008 22:47:59.0255 (UTC)
	FILETIME=[BDA7A270:01C92D85]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3004; t=1223938080;
	x=1224802080; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=j0M5HMT1iAbuaQKItrRd/AaDkwmbfItjLW+XHsnVb3A=;
	b=QgNfE9muv//sNVBknbQJFq5yQEnJlOPa44Rw3q8CBhwq8zPFkosqMJpSRT
	8Y63/0uUscRmledy5Va+UX5cJsortR6h9+BA3RACCLZaFIoANbdzq505bxfb
	fkBXA3JngyG3thJObd4dC+GunQThbDpqgCbg1re5XBH5SZqQ3iVsA=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

um, hold on. two uses.

DHCPv6 is used to assign host addresses to host interfaces. They only  
have one prefix length: /128.

DHCPv6 is also used to assign a prefix to the CPE router in a home.  
the addcon draft, in large part, is saying that these are not always  
(and perhaps should never be) /64. Please tell me that we can assign  
a /60, a /56, or a /48 to a home if we want to.

On Oct 13, 2008, at 3:33 PM, Hemant Singh (shemant) wrote:

> I haven't had the time to catch up to these emails and get a proper
> perspective.  But just a quick comment that DHCPv6 is not broken if
> DHCPv6 responses from the server to the client do not include prefix
> length - that's by design of the IPv6 architecture where the router on
> the network is responsible for doling out the prefix length to the
> clients and NOT the DHCPv6 server.
>
> Hemant
>
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org 
> ]
> On Behalf Of Fred Baker (fred)
> Sent: Monday, October 13, 2008 6:23 PM
> To: Iljitsch van Beijnum
> Cc: v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
>
>
> On Oct 13, 2008, at 5:42 AM, Iljitsch van Beijnum wrote:
>
>> On 7 okt 2008, at 19:26, Fred Baker wrote:
>>
>>> What does it mean to be "IPv6-like"?
>>
>> That everything happens mostly automatic and is easy otherwise. For
>> instance, in IPv4 you have to think about how big each subnet is. In
>> IPv6 you don't.
>
> I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.
> And btw this is about a IPv4 address, like NAT64 etc are. You make
> relatively positive statements about the other options and dump on one
> that has the same strengths and weaknesses.
>
>> The IVI mapping means that at the very least a special subnet has to
>> be created for every IPv4-reachable host. The suggestion of having
>> non-/64 subnets and DHCPv6 is very problematic because DHCPv6 doesn't
>> know about subnet prefix lengths.
>
>
> we have a way to assign a prefix using DHCP. You're telling me it
> doesn't know the prefix length? If so, it's broken. I haven't read  
> that
> spec; remind me which it is?
>
> And yes, regardless of the address format used - even SLACK, for that
> matter - one has to either inject a host route into routing or  
> inject a
> prefix into routing. That's how routing works. The only way we can  
> avoid
> that is to put every mapped-address host on a LAN shared with the
> translator. Bzzt. That doesn't scale.
>
>> The situation where a static mapping is set up means that the
>> configuration can be limited to the translation box, this simply  
>> makes
>
>> much more sense on every level.
>
> Actually, not so. And this differs from NAT64, which you spoke
> positively about, in what way?
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:54:48 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 88DFF28C194;
	Mon, 13 Oct 2008 15:54:48 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E91C3A6A6F
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level: 
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[AWL=0.080, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id k0jTumtl-wpY for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:54:46 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 8B0A53A6A4C
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:54:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="24116256"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 13 Oct 2008 22:55:33 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMtXm7012320; 
	Mon, 13 Oct 2008 18:55:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMtXY5025995;
	Mon, 13 Oct 2008 22:55:33 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:55:32 -0400
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 18:55:28 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4242D@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] You have been dugg!
Thread-Index: Ackthb6inNZEQKRFQ9KFs5uu0IyR+wAAKAXg
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
	<0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-OriginalArrivalTime: 13 Oct 2008 22:55:32.0944 (UTC)
	FILETIME=[CC131500:01C92D86]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3747; t=1223938533;
	x=1224802533; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20
	|To:=20=22Fred=20Baker=20(fred)=22=20<fred@cisco.com>;
	bh=FmKYkQ9TK3s6jbllqaGiMsdY8vltLpcgFV1/DN94fjU=;
	b=S4AI86MPDvYLxqYdGcEV3eCjmf2l0PrQZMeNYnntdBI+8dAwAPaxnm0hTC
	X/+S1/eHoIoLKV49ZafTfyFAHSwKz9tbHr5JvrpZRl2pXH7KTt3OHKeT/d1Y
	uU/clo2GOH;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

If the DHCPv6 PD option (RFC3633) is used to assign a prefix to the CPE
router in a home, then sure, since the PD option format includes a
prefix length, by all means, any ISP can assign the CPE router a prefix
of length the ISP so desires by their network design.  I was talking
about DHCPv6 without the PD option where DHCPv6 address assignment does
not include a prefix length. Doling out a PD option to a router is
different from DHCPv6 address assignment. 

Hemant 

-----Original Message-----
From: Fred Baker (fred) 
Sent: Monday, October 13, 2008 6:48 PM
To: Hemant Singh (shemant)
Cc: Iljitsch van Beijnum; v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!

um, hold on. two uses.

DHCPv6 is used to assign host addresses to host interfaces. They only
have one prefix length: /128.

DHCPv6 is also used to assign a prefix to the CPE router in a home.  
the addcon draft, in large part, is saying that these are not always
(and perhaps should never be) /64. Please tell me that we can assign a
/60, a /56, or a /48 to a home if we want to.

On Oct 13, 2008, at 3:33 PM, Hemant Singh (shemant) wrote:

> I haven't had the time to catch up to these emails and get a proper 
> perspective.  But just a quick comment that DHCPv6 is not broken if
> DHCPv6 responses from the server to the client do not include prefix 
> length - that's by design of the IPv6 architecture where the router on

> the network is responsible for doling out the prefix length to the 
> clients and NOT the DHCPv6 server.
>
> Hemant
>
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org 
> [mailto:v4v6interim-bounces@ietf.org
> ]
> On Behalf Of Fred Baker (fred)
> Sent: Monday, October 13, 2008 6:23 PM
> To: Iljitsch van Beijnum
> Cc: v4v6interim@ietf.org
> Subject: Re: [v4v6interim] You have been dugg!
>
>
> On Oct 13, 2008, at 5:42 AM, Iljitsch van Beijnum wrote:
>
>> On 7 okt 2008, at 19:26, Fred Baker wrote:
>>
>>> What does it mean to be "IPv6-like"?
>>
>> That everything happens mostly automatic and is easy otherwise. For 
>> instance, in IPv4 you have to think about how big each subnet is. In
>> IPv6 you don't.
>
> I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.
> And btw this is about a IPv4 address, like NAT64 etc are. You make 
> relatively positive statements about the other options and dump on one

> that has the same strengths and weaknesses.
>
>> The IVI mapping means that at the very least a special subnet has to 
>> be created for every IPv4-reachable host. The suggestion of having
>> non-/64 subnets and DHCPv6 is very problematic because DHCPv6 doesn't

>> know about subnet prefix lengths.
>
>
> we have a way to assign a prefix using DHCP. You're telling me it 
> doesn't know the prefix length? If so, it's broken. I haven't read 
> that spec; remind me which it is?
>
> And yes, regardless of the address format used - even SLACK, for that 
> matter - one has to either inject a host route into routing or inject 
> a prefix into routing. That's how routing works. The only way we can 
> avoid that is to put every mapped-address host on a LAN shared with 
> the translator. Bzzt. That doesn't scale.
>
>> The situation where a static mapping is set up means that the 
>> configuration can be limited to the translation box, this simply 
>> makes
>
>> much more sense on every level.
>
> Actually, not so. And this differs from NAT64, which you spoke 
> positively about, in what way?
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:55:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A58F13A69F0;
	Mon, 13 Oct 2008 15:55:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A48E23A6A65
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3UzKsIrDD8ap for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:55:03 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 705573A67A7
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:55:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="24147479"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 13 Oct 2008 22:55:57 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMtvYO011873
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 18:55:57 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMtvcK020245
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 22:55:57 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:55:57 -0400
Received: from bxb-rdroms-8711.cisco.com ([10.98.10.82]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:55:57 -0400
Message-Id: <D9F02607-D15F-48EA-97A5-BF1F218F392C@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 18:55:45 -0400
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
	<0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 13 Oct 2008 22:55:57.0511 (UTC)
	FILETIME=[DAB7B570:01C92D86]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3680; t=1223938557;
	x=1224802557; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20 |To:=20Fred=20Baker=20<fred@cisco.com>;
	bh=4Mi4XuTj6El+aAMaJfdbOuQvmnlKhtkbTnwK++wyED0=;
	b=AdkOZhraVeNMSDat7fMmEyU+VzNfmiyOE2wQW9t/Y8306CQ9rof4cVHUc4
	pnn/QwHv0yxVtmObccXLgxKviXf6btIozEi9+W9oeVTYQ/9mhZ88oop0JuIK
	AGABFRXmXm;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred - yes, PD prefixes include the prefix length.

Arguing pedantically (reverting to my previous life for a minute) with  
your first statement, IMO an address, by itself, doesn't have a prefix  
length.  The prefix it matches for, e.g., routing may have a prefix  
length, but the address doesn't have a prefix length at all...

- Ralph

On Oct 13, 2008, at Oct 13, 2008,6:47 PM, Fred Baker wrote:

> um, hold on. two uses.
>
> DHCPv6 is used to assign host addresses to host interfaces. They  
> only have one prefix length: /128.
>
> DHCPv6 is also used to assign a prefix to the CPE router in a home.  
> the addcon draft, in large part, is saying that these are not always  
> (and perhaps should never be) /64. Please tell me that we can assign  
> a /60, a /56, or a /48 to a home if we want to.
>
> On Oct 13, 2008, at 3:33 PM, Hemant Singh (shemant) wrote:
>
>> I haven't had the time to catch up to these emails and get a proper
>> perspective.  But just a quick comment that DHCPv6 is not broken if
>> DHCPv6 responses from the server to the client do not include prefix
>> length - that's by design of the IPv6 architecture where the router  
>> on
>> the network is responsible for doling out the prefix length to the
>> clients and NOT the DHCPv6 server.
>>
>> Hemant
>>
>> -----Original Message-----
>> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org 
>> ]
>> On Behalf Of Fred Baker (fred)
>> Sent: Monday, October 13, 2008 6:23 PM
>> To: Iljitsch van Beijnum
>> Cc: v4v6interim@ietf.org
>> Subject: Re: [v4v6interim] You have been dugg!
>>
>>
>> On Oct 13, 2008, at 5:42 AM, Iljitsch van Beijnum wrote:
>>
>>> On 7 okt 2008, at 19:26, Fred Baker wrote:
>>>
>>>> What does it mean to be "IPv6-like"?
>>>
>>> That everything happens mostly automatic and is easy otherwise. For
>>> instance, in IPv4 you have to think about how big each subnet is. In
>>> IPv6 you don't.
>>
>> I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.
>> And btw this is about a IPv4 address, like NAT64 etc are. You make
>> relatively positive statements about the other options and dump on  
>> one
>> that has the same strengths and weaknesses.
>>
>>> The IVI mapping means that at the very least a special subnet has to
>>> be created for every IPv4-reachable host. The suggestion of having
>>> non-/64 subnets and DHCPv6 is very problematic because DHCPv6  
>>> doesn't
>>> know about subnet prefix lengths.
>>
>>
>> we have a way to assign a prefix using DHCP. You're telling me it
>> doesn't know the prefix length? If so, it's broken. I haven't read  
>> that
>> spec; remind me which it is?
>>
>> And yes, regardless of the address format used - even SLACK, for that
>> matter - one has to either inject a host route into routing or  
>> inject a
>> prefix into routing. That's how routing works. The only way we can  
>> avoid
>> that is to put every mapped-address host on a LAN shared with the
>> translator. Bzzt. That doesn't scale.
>>
>>> The situation where a static mapping is set up means that the
>>> configuration can be limited to the translation box, this simply  
>>> makes
>>
>>> much more sense on every level.
>>
>> Actually, not so. And this differs from NAT64, which you spoke
>> positively about, in what way?
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:57:13 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C88503A68E7;
	Mon, 13 Oct 2008 15:57:13 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81F2D3A68E7
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NyoFCLxAlKGj for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:57:12 -0700 (PDT)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.232])
	by core3.amsl.com (Postfix) with ESMTP id CEAEF3A67A7
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:57:11 -0700 (PDT)
Received: by wr-out-0506.google.com with SMTP id c49so1104852wra.17
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:58:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:from:to:references
	:in-reply-to:subject:date:message-id:mime-version:content-type
	:content-transfer-encoding:x-mailer:thread-index:content-language;
	bh=5fKt4T40NUn2RlUdVfcrM4aBH9/4HtCUIPjmtPHc6zo=;
	b=j+24cof2qqIB2YVox77MQz4p7W6DTAs17JVWuNXp0HGI6Sd5vPFzaSoaugklgHrkjV
	N0PoTpf/jnrOMJ+quK9N8fS20WS4tzUnknjSDIsbyZfg4JeeppRx2cEH/C8v9niuy/BE
	siAFbOYHs411Ag1ZiRKfZQedCDCtrcB+T85EA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:to:references:in-reply-to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding:x-mailer:thread-index
	:content-language;
	b=ibKST2ks38Ner9JUnDCtBbGN7/GOfK90JQZ1wmFtqj6XbXyLCQYTw9reEwzmjN9GSM
	PKsDxQ3MlBlfFeCBvgwQy4KFaV8prMdEI84Dv8GWFcOcZ3f8ZKwf8GxQX5i2c8x2kcJR
	CKREcFcSaRLvrCqVSk4Bz113KSI5rpSnXXxdA=
Received: by 10.101.67.11 with SMTP id u11mr6594654ank.88.1223938686570;
	Mon, 13 Oct 2008 15:58:06 -0700 (PDT)
Received: from Lapci010 (pool-96-231-157-91.washdc.fios.verizon.net
	[96.231.157.91])
	by mx.google.com with ESMTPS id c29sm18618988anc.13.2008.10.13.15.58.05
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 13 Oct 2008 15:58:05 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: <v4v6interim@ietf.org>
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>	<7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>	<290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
In-Reply-To: <8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
Date: Mon, 13 Oct 2008 18:58:06 -0400
Message-ID: <003001c92d87$27fdf740$77f9e5c0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acktgl3UjxzpDdQ+QrKzYLSvFQLbuwABJfBg
Content-Language: en-us
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

>I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.

That is a discussion more about block allocation (aka prefix delegation) vs
a single subnet's size, yes?


/TJ

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 13 15:59:12 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 024F53A69F0;
	Mon, 13 Oct 2008 15:59:12 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 52ED43A68E7
	for <v4v6interim@core3.amsl.com>; Mon, 13 Oct 2008 15:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LBDpAahS7e5C for <v4v6interim@core3.amsl.com>;
	Mon, 13 Oct 2008 15:59:09 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id AB21D3A66B4
	for <v4v6interim@ietf.org>; Mon, 13 Oct 2008 15:59:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="174397714"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 13 Oct 2008 22:59:37 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMxb8G027757; 
	Mon, 13 Oct 2008 15:59:37 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMxbRT028999;
	Mon, 13 Oct 2008 22:59:37 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 15:59:37 -0700
Received: from dhcp-128-107-98-124.cisco.com ([128.107.98.124]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 15:59:36 -0700
Message-Id: <57846733-9212-43D6-9F73-20984ACE460E@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D04E4242D@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 13 Oct 2008 15:59:35 -0700
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
	<0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E4242D@xmb-rtp-20e.amer.cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 13 Oct 2008 22:59:36.0329 (UTC)
	FILETIME=[5D24AF90:01C92D87]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=196; t=1223938777; x=1224802777;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20You=20have=20been=20dug g!
	|Sender:=20; bh=mNDRUF7XnDRv0Xegtmu9foG7Yq7Fv/XYKeDdOgG48DA=;
	b=YWR0G9LpYb72twqVVBBO14Sx+8kqfIrMz7/3QE0NfIgIMC1kLHeKhmenUp
	cxPDgsm6vx6iyHUPECNth268xFeuiv1HfqP9qOs8pOrYwjosAziQ3kfjXBIJ
	6yObunnT97;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 13, 2008, at 3:55 PM, Hemant Singh (shemant) wrote:

> Doling out a PD option to a router is
> different from DHCPv6 address assignment.

I'm sure we're talking about routers here.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 14 02:04:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C545E3A6A2B;
	Tue, 14 Oct 2008 02:04:53 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FE113A6A2B
	for <v4v6interim@core3.amsl.com>; Tue, 14 Oct 2008 02:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nL46J3wHLJmV for <v4v6interim@core3.amsl.com>;
	Tue, 14 Oct 2008 02:04:51 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 5D4563A6944
	for <v4v6interim@ietf.org>; Tue, 14 Oct 2008 02:04:51 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]
	([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9E95MAO050887
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 14 Oct 2008 11:05:22 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <76C0A264-F6C3-42B1-A6DC-A52B5B3AF56A@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Eric Vyncke (evyncke) <evyncke@cisco.com>
In-Reply-To: <CE2BF2A7B1008C459FD7978065C6ECE007949456@xmb-ams-33a.emea.cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 14 Oct 2008 11:05:39 +0200
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
	<CE2BF2A7B1008C459FD7978065C6ECE007949456@xmb-ams-33a.emea.cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 3 okt 2008, at 21:16, Eric Vyncke (evyncke) wrote:

> Or more precisely, SP won't block ICMP in transit but have NO choice  
> but rate limiting the number of ICMPv6 packet too big _generated_ by  
> a router to 100 pps or so... (NB: this is already the case now in  
> IPv4 and IPv6 in order to save CPU)

Right.

> Of course, if Google Map (or any other applications) has to open 50+  
> connections per end-user transaction

Which it doesn't. In fact, when I try it I only see a single  
connection, but a bunch of stuff may be cached. AFAIK, a browser only  
sets up two sessions to the same FQDN. When there are lots of sessions  
this happens when lots of elements (ads...) need to be loaded from  
different FQDNs.

Also note that Google uses packets smaller than 1500 bytes.

> and if there are more than 2 end-users connecting to Google Maps  
> within the same second (this is assumed to by ironical -- Friday  
> evening), then some connections will fail...

Only if 100 sessions all send a large packet within a roundrip from  
the server to the router. Since the client needs to load a bunch of  
stuff before the additional sessions can be started this won't happen.

But I guess it could with 100+ different users at the same time.

> (cached information will only be available after the connection  
> timed out I'm afraid).

What do you mean timed out?

> Hence the importance of setting 'manually' the MTU right at the edge  
> where the ICMP generation rate is probably (?) lower than in the core.

You mean using large MTUs in the middle. Then you don't have trouble.  
Using small MTUs in the middle isn't a good idea.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 14 02:15:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C252E3A6ACB;
	Tue, 14 Oct 2008 02:15:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 879ED3A6827
	for <v4v6interim@core3.amsl.com>; Tue, 14 Oct 2008 02:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.873
X-Spam-Level: 
X-Spam-Status: No, score=-5.873 tagged_above=-999 required=5 tests=[AWL=0.726, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LvY2VzTFe7We for <v4v6interim@core3.amsl.com>;
	Tue, 14 Oct 2008 02:15:36 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 653DE3A6ACB
	for <v4v6interim@ietf.org>; Tue, 14 Oct 2008 02:15:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,408,1220227200"; d="scan'208";a="22535476"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 14 Oct 2008 09:15:46 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9E9FkVU002941; 
	Tue, 14 Oct 2008 11:15:46 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9E9Fk9R002557;
	Tue, 14 Oct 2008 09:15:46 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 11:15:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 11:16:11 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE007A590BF@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <76C0A264-F6C3-42B1-A6DC-A52B5B3AF56A@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Fragmentation Options in NAT6 presentation
Thread-Index: Ackt3CeSaOqjzbaZRSq/8/zHw2bGdgAATmfQ
References: <B2FE551A-5BA9-4D46-B619-EF694015D5AF@tahi.org>
	<BB56240F3A190F469C52A57138047A03011DB1F0@xmb-rtp-211.amer.cisco.com>
	<CE2BF2A7B1008C459FD7978065C6ECE007949456@xmb-ams-33a.emea.cisco.com>
	<76C0A264-F6C3-42B1-A6DC-A52B5B3AF56A@muada.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 14 Oct 2008 09:15:46.0674 (UTC)
	FILETIME=[712FA520:01C92DDD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=449; t=1223975746; x=1224839746;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20Fragmentation=20Options
	=20in=20NAT6=20presentation |Sender:=20;
	bh=mgqwPDM9DxQnAOYMp237X9em0XeZS1O4ZIxMgtxOiVU=;
	b=sznG0jy/f9d+woVEhbLEPs9s7Vn+JwpCFJDfo4IEs4/LQuVtqARX4sumHG
	DA/z26/N7Oyy5NcVRRDq/UYKmr7tl5msrkob9zRIqAwtZsI/6Eki62vBYQtw
	++jgWBGRSi;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Fragmentation Options in NAT6 presentation
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> 
> > Hence the importance of setting 'manually' the MTU right at 
> the edge 
> > where the ICMP generation rate is probably (?) lower than 
> in the core.
> 
> You mean using large MTUs in the middle. Then you don't have 
> trouble.  
> Using small MTUs in the middle isn't a good idea.

Actually, I mean two things (which have the same cause & effect):
- try to avoid small MTU in the core
- generate ICMP at the edge
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct 15 09:09:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 065323A69B2;
	Wed, 15 Oct 2008 09:09:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4FDD28C221
	for <v4v6interim@core3.amsl.com>; Wed, 15 Oct 2008 09:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.725
X-Spam-Level: 
X-Spam-Status: No, score=-2.725 tagged_above=-999 required=5
	tests=[AWL=-0.126, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YxTldsKfd6rn for <v4v6interim@core3.amsl.com>;
	Wed, 15 Oct 2008 09:09:02 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id ABFD03A692F
	for <v4v6interim@ietf.org>; Wed, 15 Oct 2008 09:09:02 -0700 (PDT)
Received: from ([128.244.206.121])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.120015421;
	Wed, 15 Oct 2008 12:08:58 -0400
Message-ID: <48F6159A.5020801@innovationslab.net>
Date: Wed, 15 Oct 2008 12:08:58 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: v4v6interim@ietf.org
Subject: [v4v6interim] Audio recording of interim meeting
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

All,
      The audio recordings from the interim meeting are now available on 
the wiki.

Regards,
Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct 15 09:41:20 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E323D28C24A;
	Wed, 15 Oct 2008 09:41:20 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA00F28C23B
	for <v4v6interim@core3.amsl.com>; Wed, 15 Oct 2008 09:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JGPxkNHGHPUs for <v4v6interim@core3.amsl.com>;
	Wed, 15 Oct 2008 09:41:19 -0700 (PDT)
Received: from QMTA10.westchester.pa.mail.comcast.net
	(qmta10.westchester.pa.mail.comcast.net [76.96.62.17])
	by core3.amsl.com (Postfix) with ESMTP id 0B1683A6C4C
	for <v4v6interim@ietf.org>; Wed, 15 Oct 2008 09:41:17 -0700 (PDT)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA10.westchester.pa.mail.comcast.net with comcast
	id T1Uq1a00716LCl05A4iGye; Wed, 15 Oct 2008 16:42:16 +0000
Received: from [10.4.0.105] ([69.33.111.74])
	by OMTA06.westchester.pa.mail.comcast.net with comcast
	id T4i01a00J1cMU3H3S4i33s; Wed, 15 Oct 2008 16:42:09 +0000
X-Authority-Analysis: v=1.0 c=1 a=Kzyr2gFXM2oA:10 a=W0f4M4Z6aokA:10
	a=48vgC7mUAAAA:8 a=S3jcjBrA6k2UD9xZRwgA:9
	a=wAYrHgmz-9ishlTBq5XKtyN-baQA:4
	a=lZB815dzVvQA:10 a=c5zHXd76wwQA:10
Message-Id: <BEF065E1-C7EC-4B15-9248-DDB8A7612931@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Brian Haberman <brian@innovationslab.net>
In-Reply-To: <48F6159A.5020801@innovationslab.net>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 12:41:59 -0400
References: <48F6159A.5020801@innovationslab.net>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Audio recording of interim meeting
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org



This is great!  Thanks to everyone who helped to make this meeting so  
accessible to those of us who couldn't attend in person.

Thanks,
Margaret

On Oct 15, 2008, at 12:08 PM, Brian Haberman wrote:

> All,
>     The audio recordings from the interim meeting are now available  
> on the wiki.
>
> Regards,
> Brian
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 16 01:16:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70AAE3A6B2E;
	Thu, 16 Oct 2008 01:16:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8025C3A6B2E
	for <v4v6interim@core3.amsl.com>; Thu, 16 Oct 2008 01:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ul20CHfsYKkK for <v4v6interim@core3.amsl.com>;
	Thu, 16 Oct 2008 01:16:25 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 45DC63A6AA9
	for <v4v6interim@ietf.org>; Thu, 16 Oct 2008 01:16:25 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.38])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9G8GoDk009115
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 16 Oct 2008 10:16:55 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <9FEB64A3-5FD4-43DC-AD55-6D7464737B16@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 10:17:03 +0200
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com>
	<7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com>
	<290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 14 okt 2008, at 0:23, Fred Baker wrote:

>> That everything happens mostly automatic and is easy otherwise. For  
>> instance, in IPv4 you have to think about how big each subnet is.  
>> In IPv6 you don't.

> I disagree. The discussion of /48 vs /56 vs /60 vs /64 comes to mind.

Which was a bad idea; one prefix length for everyone is preferable.

But it's also irrelevant to the discussion at hand, what I was talking  
about is that all IPv6 subnets are (should be) /64, while with IPv4  
you need to think about how many hosts will have to fit in a subnet  
and size it accordingly.

> we have a way to assign a prefix using DHCP. You're telling me it  
> doesn't know the prefix length? If so, it's broken. I haven't read  
> that spec; remind me which it is?

Are you saying that you want to use DHCPv6 prefix delegation to give  
out prefixes to IPv6 hosts that are reachable from the IPv4 side  
through IVI? Not sure if that makes everything easier. One of the  
issues with PD is to get the routers to know what's going on, and the  
host would still have to fill in the correct lower bits.

With DHCPv6 address assignment you just get the address, with no  
knowledge about the subnet. For the host this is probably not a big  
deal (in the IVI case with presumably no other hosts on the same  
subnet) but the routers need to know the subnet so they know how to  
send packets to the host in question.

>> The situation where a static mapping is set up means that the  
>> configuration can be limited to the translation box, this simply  
>> makes much more sense on every level.

> Actually, not so.

How does it make sense to have to touch more boxes?

Or, what benefit is there that outweighs this downside?

> And this differs from NAT64, which you spoke positively about, in  
> what way?

NAT64 doesn't impose addressing requirements on the IPv6 side.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 16 01:24:31 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A92623A6AA9;
	Thu, 16 Oct 2008 01:24:31 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7E2B3A693B
	for <v4v6interim@core3.amsl.com>; Thu, 16 Oct 2008 01:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hdQIXeuMwOr0 for <v4v6interim@core3.amsl.com>;
	Thu, 16 Oct 2008 01:24:29 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 08DDE3A6AA9
	for <v4v6interim@ietf.org>; Thu, 16 Oct 2008 01:24:28 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.38])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9G8P38j009234
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 16 Oct 2008 10:25:04 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <D3D01D2D-71B5-43E6-95D7-F79F5A760BDD@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 10:25:16 +0200
References: <732E532B-97C7-465C-BBE0-FD1B442DB21E@muada.com><7E414550-E1C7-46BB-A7AD-D4F128903046@cisco.com><290F8ED4-F51C-429F-9DD6-F904996A1CED@muada.com>
	<8094EF71-2475-48B5-8F26-F926769CBF91@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D04E42429@xmb-rtp-20e.amer.cisco.com>
	<0B53C988-0427-436E-92D2-02E5603656F3@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] You have been dugg!
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 14 okt 2008, at 0:47, Fred Baker wrote:

> DHCPv6 is also used to assign a prefix to the CPE router in a home.  
> the addcon draft, in large part, is saying that these are not always  
> (and perhaps should never be) /64. Please tell me that we can assign  
> a /60, a /56, or a /48 to a home if we want to.

Of course. Have a look at your own products, it works just fine.

>> But just a quick comment that DHCPv6 is not broken if
>> DHCPv6 responses from the server to the client do not include prefix
>> length - that's by design of the IPv6 architecture where the router  
>> on
>> the network is responsible for doling out the prefix length to the
>> clients and NOT the DHCPv6 server.

It would be great if we could classify this as a mistake (much like  
the whole business with the reverse DNS mapping for IPv6  
with .int/.arpa) and fix this, but unfortunately adding a prefix  
length will only help a little to make all of this stuff better.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 16 09:41:39 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF4D23A6A38;
	Thu, 16 Oct 2008 09:41:39 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F7393A684A
	for <v4v6interim@core3.amsl.com>; Thu, 16 Oct 2008 09:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.878
X-Spam-Level: 
X-Spam-Status: No, score=-5.878 tagged_above=-999 required=5
	tests=[AWL=-0.229, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fHxwD2pvJSdC for <v4v6interim@core3.amsl.com>;
	Thu, 16 Oct 2008 09:41:37 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id AC5F33A6A5B
	for <v4v6interim@ietf.org>; Thu, 16 Oct 2008 09:41:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6F30B20A95; Thu, 16 Oct 2008 18:42:37 +0200 (CEST)
X-AuditID: c1b4fb3c-ac8cbbb0000015b5-3c-48f76efd9adb
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2F70B206CA; Thu, 16 Oct 2008 18:42:37 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 18:42:36 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 18:42:36 +0200
Message-ID: <48F76EFC.9000703@ericsson.com>
Date: Thu, 16 Oct 2008 18:42:36 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: v4v6interim@ietf.org, 46Translation <46translation@employees.org>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/mixed; boundary="------------040400040506020403050103"
X-OriginalArrivalTime: 16 Oct 2008 16:42:36.0881 (UTC)
	FILETIME=[32241410:01C92FAE]
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] [Fwd: [BEHAVE] Proposal for new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behave WG <behave@ietf.org>
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

This is a multi-part message in MIME format.
--------------040400040506020403050103
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

The attached message was just sent to BEHAVE. Please send any comments
to BEHAVE.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Färögatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

--------------040400040506020403050103
Content-Type: message/rfc822;
 name="[BEHAVE] Proposal for new BEHAVE charter.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="[BEHAVE] Proposal for new BEHAVE charter.eml"

Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 16 Oct 2008 18:40:31 +0200
Received: from mailgw2.ericsson.se ([193.180.251.37]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 16 Oct 2008 18:40:31 +0200
Received: from mailgw2.ericsson.se (unknown [127.0.0.1])
	by mailgw2.ericsson.se (Symantec Mail Security) with ESMTP id 93BEA58C002;
	Thu, 16 Oct 2008 18:40:31 +0200 (CEST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32])
	by mailgw2.ericsson.se (Symantec Mail Security) with ESMTP id 93E90500007;
	Thu, 16 Oct 2008 18:40:30 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 78E323A6B47;
	Thu, 16 Oct 2008 09:39:27 -0700 (PDT)
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E37243A6B47
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 09:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.88
X-Spam-Level: 
X-Spam-Status: No, score=-5.88 tagged_above=-999 required=5 tests=[AWL=-0.231, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ETyatuzllA80 for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 09:39:24 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 54E3D3A684A
	for <behave@ietf.org>; Thu, 16 Oct 2008 09:39:24 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	08A9B21153
	for <behave@ietf.org>; Thu, 16 Oct 2008 18:40:25 +0200 (CEST)
X-AuditID: c1b4fb25-ab02bbb00000564a-b0-48f76e7e06e4
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	D2E0520FA5
	for <behave@ietf.org>; Thu, 16 Oct 2008 18:40:24 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 18:40:24 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 18:40:24 +0200
Message-ID: <48F76E78.6000302@ericsson.com>
Date: Thu, 16 Oct 2008 18:40:24 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 16 Oct 2008 16:40:24.0354 (UTC)
	FILETIME=[E3261020:01C92FAD]
X-Brightmail-Tracker: AAAAAgxAANIMQJYU
Subject: [BEHAVE] Proposal for new BEHAVE charter
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>,
	<mailto:behave-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org
Return-Path: behave-bounces@ietf.org

Hi,

Together with the chairs I have drafted a new BEHAVE charter that is on
the agenda for next weeks IESG telechat for decision if it should go for
formal review. However, I like to share it with you already now so that
you can comment on it early. The goal is to have this charter in place
before Minneapolis so that the Translation work can go forward.
Therefore, resolving comments early reduced the risk in hiccups in this
process.

To make this possible we have so far excluded any specific work items on
port-borrowing or other solutions to the dual stack lite problem. BEHAVE
will be home for this discussion until it has become clear on what we
really need to do here. At that point we will make a new recharter
action to where that work would fit. It is after all likely that part of
that work belongs in other WGs.

So please provide your view on the draft charter!


Draft charter proposal submitted to IESG

The behavior of NATs varies from one implementation to
another. As a result it is very difficult for applications to predict
or discover the behavior of these devices. Predicting and/or
discovering the behavior of NATs is important for designing
application protocols and NAT traversal techniques that work reliably
in existing networks. This situation is especially problematic for end-
to-end applications where one or both end-points are behind a NAT, such
as multiuser games, interactive multimedia and P2P download.

The working group documents best current practices to enable NATs to
function in as deterministic a fashion as possible. The NAT
behavior practices will be application independent. This has already
completed for UDP, TCP, DCCP, Multicast and ICMP. It continues with SCTP
and any additional protocol deemed necessary to handle. The WG has
documented approaches for characterizing and testing NAT devices.

BEHAVE will develop protocol-independent toolkits usable by application
protocols for NAT traversal. The WG has already produced an update of
the binding discovery protocol STUN. It will now produce a relay
protocol that focuses on security that is usable with both IPv4 and
IPv6, and capable of relaying between the two IP versions.

The goal of this work is to encourage migration to IPv6 and compliance
with the UNSAF [RFC 3424] considerations. To support deployments where
communicating hosts require using different address families (IPv4 or
IPv6), address family translation is needed to establish communication.
 BEHAVE will coordinate with the V6ops WG in this work.

The BEHAVE WG will design solutions for the following four translation
scenarios; other scenarios are out of scope:

1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are
   initiated from an IPv6 host towards an IPv4 host. The
   translator function is intended to service a specific
   IPv6 network of arbitary size. Port translation is necessary on
   the IPv4 side for efficient IPv4 address usage.

2. IPv6 Internet to MY IPv4, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are
   initiated from an IPv6 host towards an IPv4 host.  The translator
   function services is intended to service a specific IPv4 network
   using either private or public IPv4 addresses. Because this scenario
   has different constraints compared to (1), the WG should attempt to
   design a simpler solution with less impact on applications.

3. MY IPv4 to IPv6 Internet, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are initiated
   from an IPv4 host towards an IPv6 host. The translator function is
   intended to service a specific IPv4 network using either public or
   private IPv4 address space.

4. IPv4 Internet to MY IPv6, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are initiated
   from an IPv4 host towards an IPv6 host. The translator function is
   intended to service a specific IPv6 network where selected IPv6 hosts
   and services are to be reachable.

All translation solutions shall be capable of handling flows using TCP,
UDP, DCCP, and SCTP. The fundamental parts of ICMP are also required to
work. Additional protocols directly on top of IP may be supported.
Translation mechanisms must handle fragmentation.

The translators should support multicast traffic and its control traffic
(IGMP and MLD) across them, both Single Source Multicast (SSM) and Any
Source Multicast (ASM). However, the WG may determine that it becomes
too complex or too difficult to realize with maintained functionality,
for some or all cases of multicast functionality.

Translation mechanisms cannot transparently support protocols that embed
network addresses within their protocol messages without application
level gateways (ALGs). Because ALGs have security issues (like blocking
usage of TLS), are error prone and brittle, and hinder application
development, the usage of ALGs in the defined translators should be
avoided. Instead application developers will need to be aware and use
mechanisms that handle the address family translation. ALGs may be
considered only for the most crucial of legacy applications.

DNS is a crucial part in making a large number of applications work
across a translator. Thus the solution to the above translation cases
shall include recommendations for DNS. If additional DNS functionality
is needed, it may be developed. Any DNS extensions must be developed
together with the DNSEXT WG, including issuing a joint WG last call for
any documents.

The WG needs to determine the best method for providing address space to
a translator in the different deployment cases and documenting the pros
and cons of the suggested approaches. The WG is to seek input from the
Routing, Operations and Internet areas.

Solutions may solve more than one of the cases, however timely delivery
is more important than a unified solution.

Milestones:

Done	Submit BCP that defines unicast UDP behavioral requirements for
        NATs to IESG
Done	Submit a BCP that defines TCP behavioral requirements for NATs
        to IESG
Done	Submit a BCP that defines ICMP behavioral requirements for NATs
        to IESG
Done	Submit informational that discusses current NAT traversal
        techniques used by applications
Done	Submit BCP that defines multicast UDP
Done	Submit revision of RFC 3489 to IESG behavioral requirements for
        NATs to IESG
Done	Submit informational document for rfc3489bis test vectors
Done   	Submit experimental document that describes how an application
        can determine the type of NAT it is behind
Done	Submit BCP document for DCCP NAT behavior

Dec 08	Submit standards-track relay protocol to IESG

Dec 08	Submit BCP document for SCTP NAT behavior

Jan 09  Determine relative prioritization of the four translation cases.

Mar 09	Submit standards-track document for relaying of a TCP bytestream

Mar 09	Submit standard-track document of an IPv6 relay protocol to IESG

Mar 09  Determine what solutions(s) and components are needed to
        solve each of the four cases. Create new milestones for the
        solution(s) and the components.

Sep 09  Target for first solution to be submitted to IESG.


-- =


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


--------------040400040506020403050103
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--------------040400040506020403050103--


From v4v6interim-bounces@ietf.org  Fri Oct 17 01:57:15 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 364813A69EF;
	Fri, 17 Oct 2008 01:57:15 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7BAB3A68DC
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 01:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.874
X-Spam-Level: 
X-Spam-Status: No, score=-5.874 tagged_above=-999 required=5
	tests=[AWL=-0.225, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PUcsBeiya+tD for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 01:57:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 4F02B3A67D0
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 01:57:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E90F120D65; Fri, 17 Oct 2008 10:58:14 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-f2-48f853a637e8
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9BC4B20C67; Fri, 17 Oct 2008 10:58:14 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 10:58:05 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 10:58:05 +0200
Message-ID: <48F8539D.90608@ericsson.com>
Date: Fri, 17 Oct 2008 10:58:05 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: 46Translation <46translation@employees.org>, v4v6interim@ietf.org
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 17 Oct 2008 08:58:05.0133 (UTC)
	FILETIME=[77B297D0:01C93036]
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behave WG <behave@ietf.org>
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Resending as some have reported issues with receiving the charter email
as an attachment. Please send any comments to BEHAVE.

/Magnus

Hi,

Together with the chairs I have drafted a new BEHAVE charter that is on
the agenda for next weeks IESG telechat for decision if it should go for
formal review. However, I like to share it with you already now so that
you can comment on it early. The goal is to have this charter in place
before Minneapolis so that the Translation work can go forward.
Therefore, resolving comments early reduced the risk in hiccups in this
process.

To make this possible we have so far excluded any specific work items on
port-borrowing or other solutions to the dual stack lite problem. BEHAVE
will be home for this discussion until it has become clear on what we
really need to do here. At that point we will make a new recharter
action to where that work would fit. It is after all likely that part of
that work belongs in other WGs.

So please provide your view on the draft charter!


Draft charter proposal submitted to IESG

The behavior of NATs varies from one implementation to
another. As a result it is very difficult for applications to predict
or discover the behavior of these devices. Predicting and/or
discovering the behavior of NATs is important for designing
application protocols and NAT traversal techniques that work reliably
in existing networks. This situation is especially problematic for end-
to-end applications where one or both end-points are behind a NAT, such
as multiuser games, interactive multimedia and P2P download.

The working group documents best current practices to enable NATs to
function in as deterministic a fashion as possible. The NAT
behavior practices will be application independent. This has already
completed for UDP, TCP, DCCP, Multicast and ICMP. It continues with SCTP
and any additional protocol deemed necessary to handle. The WG has
documented approaches for characterizing and testing NAT devices.

BEHAVE will develop protocol-independent toolkits usable by application
protocols for NAT traversal. The WG has already produced an update of
the binding discovery protocol STUN. It will now produce a relay
protocol that focuses on security that is usable with both IPv4 and
IPv6, and capable of relaying between the two IP versions.

The goal of this work is to encourage migration to IPv6 and compliance
with the UNSAF [RFC 3424] considerations. To support deployments where
communicating hosts require using different address families (IPv4 or
IPv6), address family translation is needed to establish communication.
 BEHAVE will coordinate with the V6ops WG in this work.

The BEHAVE WG will design solutions for the following four translation
scenarios; other scenarios are out of scope:

1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are
   initiated from an IPv6 host towards an IPv4 host. The
   translator function is intended to service a specific
   IPv6 network of arbitary size. Port translation is necessary on
   the IPv4 side for efficient IPv4 address usage.

2. IPv6 Internet to MY IPv4, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are
   initiated from an IPv6 host towards an IPv4 host.  The translator
   function services is intended to service a specific IPv4 network
   using either private or public IPv4 addresses. Because this scenario
   has different constraints compared to (1), the WG should attempt to
   design a simpler solution with less impact on applications.

3. MY IPv4 to IPv6 Internet, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are initiated
   from an IPv4 host towards an IPv6 host. The translator function is
   intended to service a specific IPv4 network using either public or
   private IPv4 address space.

4. IPv4 Internet to MY IPv6, i.e. perform translation between IPv4 and
   IPv6 for packets in uni- or bi-directional flows that are initiated
   from an IPv4 host towards an IPv6 host. The translator function is
   intended to service a specific IPv6 network where selected IPv6 hosts
   and services are to be reachable.

All translation solutions shall be capable of handling flows using TCP,
UDP, DCCP, and SCTP. The fundamental parts of ICMP are also required to
work. Additional protocols directly on top of IP may be supported.
Translation mechanisms must handle fragmentation.

The translators should support multicast traffic and its control traffic
(IGMP and MLD) across them, both Single Source Multicast (SSM) and Any
Source Multicast (ASM). However, the WG may determine that it becomes
too complex or too difficult to realize with maintained functionality,
for some or all cases of multicast functionality.

Translation mechanisms cannot transparently support protocols that embed
network addresses within their protocol messages without application
level gateways (ALGs). Because ALGs have security issues (like blocking
usage of TLS), are error prone and brittle, and hinder application
development, the usage of ALGs in the defined translators should be
avoided. Instead application developers will need to be aware and use
mechanisms that handle the address family translation. ALGs may be
considered only for the most crucial of legacy applications.

DNS is a crucial part in making a large number of applications work
across a translator. Thus the solution to the above translation cases
shall include recommendations for DNS. If additional DNS functionality
is needed, it may be developed. Any DNS extensions must be developed
together with the DNSEXT WG, including issuing a joint WG last call for
any documents.

The WG needs to determine the best method for providing address space to
a translator in the different deployment cases and documenting the pros
and cons of the suggested approaches. The WG is to seek input from the
Routing, Operations and Internet areas.

Solutions may solve more than one of the cases, however timely delivery
is more important than a unified solution.

Milestones:

Done	Submit BCP that defines unicast UDP behavioral requirements for
        NATs to IESG
Done	Submit a BCP that defines TCP behavioral requirements for NATs
        to IESG
Done	Submit a BCP that defines ICMP behavioral requirements for NATs
        to IESG
Done	Submit informational that discusses current NAT traversal
        techniques used by applications
Done	Submit BCP that defines multicast UDP
Done	Submit revision of RFC 3489 to IESG behavioral requirements for
        NATs to IESG
Done	Submit informational document for rfc3489bis test vectors
Done   	Submit experimental document that describes how an application
        can determine the type of NAT it is behind
Done	Submit BCP document for DCCP NAT behavior

Dec 08	Submit standards-track relay protocol to IESG

Dec 08	Submit BCP document for SCTP NAT behavior

Jan 09  Determine relative prioritization of the four translation cases.

Mar 09	Submit standards-track document for relaying of a TCP bytestream

Mar 09	Submit standard-track document of an IPv6 relay protocol to IESG

Mar 09  Determine what solutions(s) and components are needed to
        solve each of the four cases. Create new milestones for the
        solution(s) and the components.

Sep 09  Target for first solution to be submitted to IESG.


-- =


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 03:40:07 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81EB53A6827;
	Fri, 17 Oct 2008 03:40:07 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1920B3A6827
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 03:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n0dTjs-LN0vz for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 03:40:05 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 1E8D93A63CB
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 03:40:04 -0700 (PDT)
Received: from [IPv6:2002:a375:547a:9:21b:63ff:fe02:3c13]
	([IPv6:2002:a375:547a:9:21b:63ff:fe02:3c13]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9HAeb4G031577
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Oct 2008 12:40:40 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 12:40:55 +0200
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

[catching up...]

On 1 okt 2008, at 18:13, Fred Baker wrote:

> An IPv4 client accessing an IPv6 server is equally simple given a  
> 1:1 mapping such as NAT64 or IVI describes. One maps the headers and  
> the addresses.

[...]

> So to my mind, the requirement is that the gateway provide three  
> services:
>  - a DNS algorithm that maps IPv4 addresses to a subset of IPv6
>    addresses.
>  - a 1:1 NAT algorithm that statelessly supports the common case of
>    IPv4 clients accessing IPv6 servers, which will be used by a
>    relatively small set of hosts in the IPv6-only domain.
>  - 1 1:n NAT algorithm that statefully maps general IPv6 to IPv4
>    address plus port, which might be used by an arbitrarily large
>    number of hosts in the IPv6-only domain, but unlikely to be all
>    at the same time and diminishing as IPv6 deployment grows.

So you _don't_ want to solve the situation where an IPv4-only host  
gets to talk to any given IPv6 host.

I think it would be fair to call _that_ scenario "hard".

However, I think there are others who are interested in solving this  
case.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 07:33:15 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4107D28C0DE;
	Fri, 17 Oct 2008 07:33:15 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 413BC3A6826
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 07:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5
	tests=[AWL=-0.550, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kO2uk37dimtK for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 07:33:13 -0700 (PDT)
Received: from QMTA04.westchester.pa.mail.comcast.net
	(qmta04.westchester.pa.mail.comcast.net [76.96.62.40])
	by core3.amsl.com (Postfix) with ESMTP id CB5033A6A4C
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 07:33:12 -0700 (PDT)
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44])
	by QMTA04.westchester.pa.mail.comcast.net with comcast
	id TmyV1a0040xGWP854qaGx5; Fri, 17 Oct 2008 14:34:16 +0000
Received: from [10.36.0.45] ([76.119.58.152])
	by OMTA12.westchester.pa.mail.comcast.net with comcast
	id TqaE1a00C3H3vh03YqaES4; Fri, 17 Oct 2008 14:34:15 +0000
X-Authority-Analysis: v=1.0 c=1 a=NhI9_mw7tIoA:10 a=_lx8axnWmiUA:10
	a=48vgC7mUAAAA:8 a=M3J8f-9-BZmqZyNF3VwA:9 a=MjqbBa290Pj0Cant6bgA:7
	a=cR7YuYViPw3_aTPOxz8gq14W_-4A:4 a=f7GxY0FH8QIA:10 a=lZB815dzVvQA:10
	a=I2EqgwFF2xUA:10
Message-Id: <E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Behave WG <behave@ietf.org>
In-Reply-To: <48F8539D.90608@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 10:34:13 -0400
References: <48F8539D.90608@ericsson.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


I support this work, and I think the behave WG is the right place to  =

do it.

I have  few comments in-line...

On Oct 17, 2008, at 4:58 AM, Magnus Westerlund wrote:
>
> Draft charter proposal submitted to IESG
>
> The behavior of NATs varies from one implementation to
> another. As a result it is very difficult for applications to predict
> or discover the behavior of these devices. Predicting and/or
> discovering the behavior of NATs is important for designing
> application protocols and NAT traversal techniques that work reliably
> in existing networks. This situation is especially problematic for  =

> end-
> to-end applications where one or both end-points are behind a NAT,  =

> such
> as multiuser games, interactive multimedia and P2P download.
>
> The working group documents best current practices to enable NATs to
> function in as deterministic a fashion as possible. The NAT
> behavior practices will be application independent. This has already
> completed for UDP, TCP, DCCP, Multicast and ICMP. It continues with  =

> SCTP
> and any additional protocol deemed necessary to handle. The WG has
> documented approaches for characterizing and testing NAT devices.
>
> BEHAVE will develop protocol-independent toolkits usable by  =

> application
> protocols for NAT traversal. The WG has already produced an update of
> the binding discovery protocol STUN. It will now produce a relay
> protocol that focuses on security that is usable with both IPv4 and
> IPv6, and capable of relaying between the two IP versions.

Is there a draft available on which this work will be based?  I'm not  =

suggesting that you mention it in the charter, I'd just like to know  =

which draft I should be reading for this item.

> The goal of this work is to encourage migration to IPv6 and compliance
> with the UNSAF [RFC 3424] considerations. To support deployments where
> communicating hosts require using different address families (IPv4 or
> IPv6), address family translation is needed to establish  =

> communication.
> BEHAVE will coordinate with the V6ops WG in this work.

I think it should be made clearer here whether the translation  =

documents will be written in the v6ops WG or behave.  I _think_ this  =

is intended to say that the documents will be written in behave, and  =

that the behave WG will get input and review regarding operational   =

requirements and deployability from the v6ops WG, but I'd like to see  =

that made clearer.

> The BEHAVE WG will design solutions for the following four translation
> scenarios; other scenarios are out of scope:
>
> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and

"MY" should be expanded or explained before it is first used.

>   IPv6 for packets in uni- or bi-directional flows that are
>   initiated from an IPv6 host towards an IPv4 host. The
>   translator function is intended to service a specific
>   IPv6 network of arbitary size. Port translation is necessary on
>   the IPv4 side for efficient IPv4 address usage.
>
> 2. IPv6 Internet to MY IPv4, i.e. perform translation between IPv4 and
>   IPv6 for packets in uni- or bi-directional flows that are
>   initiated from an IPv6 host towards an IPv4 host.  The translator
>   function services is intended to service a specific IPv4 network
>   using either private or public IPv4 addresses. Because this scenario
>   has different constraints compared to (1), the WG should attempt to
>   design a simpler solution with less impact on applications.
>
> 3. MY IPv4 to IPv6 Internet, i.e. perform translation between IPv4 and
>   IPv6 for packets in uni- or bi-directional flows that are initiated
>   from an IPv4 host towards an IPv6 host. The translator function is
>   intended to service a specific IPv4 network using either public or
>   private IPv4 address space.
>
> 4. IPv4 Internet to MY IPv6, i.e. perform translation between IPv4 and
>   IPv6 for packets in uni- or bi-directional flows that are initiated
>   from an IPv4 host towards an IPv6 host. The translator function is
>   intended to service a specific IPv6 network where selected IPv6  =

> hosts
>   and services are to be reachable.

I would also like to us write (at least) two NAT-related documents that
aren't listed here:

(1) A document that offers advice on how/when to deploy these  =

translation
mechanisms vs. other choices.  I think this document would cover topics
such as:

	- If the infrastructure will support dual stack and you are running out
           of IPv4 addresses, NAT IPv4 and leave IPv6 alone.
	- The advantages of placing NATs closer to the edges of the network

(2) An explanation of how to do IPv6 <=3D> IPv6 NAT.  It am convinced that
there are some people who will choose to do this for the same reasons  =

that
people with plenty of IPv4 addresses choose to use IPv4 <=3D> IPv4 NATs
today.  I think we could write a document that says something like:   =

IPv6
<=3D> IPv6 NATs are not really necessary, don't provide any concrete  =

advantages
that can't be obtained through less disruptive means, and are not  =

recommended
by the IETF, but if you are planning to do this anyway, please do it  =

right (don't
include port translation, use algorithmic address mapping if possible,  =

instead
of state tables, etc.).

> All translation solutions shall be capable of handling flows using  =

> TCP,

> UDP, DCCP, and SCTP. The fundamental parts of ICMP are also required  =

> to
> work. Additional protocols directly on top of IP may be supported.
> Translation mechanisms must handle fragmentation.
>
> The translators should support multicast traffic and its control  =

> traffic
> (IGMP and MLD) across them, both Single Source Multicast (SSM) and Any
> Source Multicast (ASM). However, the WG may determine that it becomes
> too complex or too difficult to realize with maintained functionality,
> for some or all cases of multicast functionality.
>
> Translation mechanisms cannot transparently support protocols that  =

> embed
> network addresses within their protocol messages without application
> level gateways (ALGs). Because ALGs have security issues (like  =

> blocking
> usage of TLS), are error prone and brittle, and hinder application
> development, the usage of ALGs in the defined translators should be
> avoided. Instead application developers will need to be aware and use
> mechanisms that handle the address family translation. ALGs may be
> considered only for the most crucial of legacy applications.
>
> DNS is a crucial part in making a large number of applications work
> across a translator. Thus the solution to the above translation cases
> shall include recommendations for DNS. If additional DNS functionality
> is needed, it may be developed. Any DNS extensions must be developed
> together with the DNSEXT WG, including issuing a joint WG last call  =

> for
> any documents.
>
> The WG needs to determine the best method for providing address  =

> space to
> a translator in the different deployment cases and documenting the  =

> pros
> and cons of the suggested approaches. The WG is to seek input from the
> Routing, Operations and Internet areas.
>
> Solutions may solve more than one of the cases, however timely  =

> delivery
> is more important than a unified solution.
>
> Milestones:
>
> Done	Submit BCP that defines unicast UDP behavioral requirements for
>        NATs to IESG
> Done	Submit a BCP that defines TCP behavioral requirements for NATs
>        to IESG
> Done	Submit a BCP that defines ICMP behavioral requirements for NATs
>        to IESG
> Done	Submit informational that discusses current NAT traversal
>        techniques used by applications
> Done	Submit BCP that defines multicast UDP
> Done	Submit revision of RFC 3489 to IESG behavioral requirements for
>        NATs to IESG
> Done	Submit informational document for rfc3489bis test vectors
> Done   	Submit experimental document that describes how an application
>        can determine the type of NAT it is behind
> Done	Submit BCP document for DCCP NAT behavior
>
> Dec 08	Submit standards-track relay protocol to IESG
>
> Dec 08	Submit BCP document for SCTP NAT behavior
>
> Jan 09  Determine relative prioritization of the four translation  =

> cases.
>
> Mar 09	Submit standards-track document for relaying of a TCP  =

> bytestream
>
> Mar 09	Submit standard-track document of an IPv6 relay protocol to  =

> IESG
>
> Mar 09  Determine what solutions(s) and components are needed to
>        solve each of the four cases. Create new milestones for the
>        solution(s) and the components.
>
> Sep 09  Target for first solution to be submitted to IESG.
>
>
> -- =

>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> F=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 08:06:30 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9EFC828B797;
	Fri, 17 Oct 2008 08:06:30 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47C3128B797
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 08:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.025
X-Spam-Level: 
X-Spam-Status: No, score=-6.025 tagged_above=-999 required=5 tests=[AWL=0.021, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AA0mICnSXG0U for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 08:06:27 -0700 (PDT)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM
	[128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id D6F7928B56A
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 08:06:27 -0700 (PDT)
Received: from smssmtp-internal1.sri.com (128.18.84.115)
	by mailgate-internal3.sri.com with SMTP; 17 Oct 2008 15:06:35 -0000
X-AuditID: 80125473-ab4e2bb000000a55-9f-48f8a9fb04d4
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id
	AEA8021AF2D
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 08:06:35 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K8W00DPN1YYO350@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 17 Oct 2008 08:06:35 -0700 (PDT)
Date: Fri, 17 Oct 2008 11:06:33 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-id: <48F8A9F9.6000505@sri.com>
MIME-version: 1.0
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org



Iljitsch van Beijnum wrote:
> [catching up...]
>
> On 1 okt 2008, at 18:13, Fred Baker wrote:
>
>> An IPv4 client accessing an IPv6 server is equally simple given a 1:1 
>> mapping such as NAT64 or IVI describes. One maps the headers and the 
>> addresses.
>
> [...]
>
>> So to my mind, the requirement is that the gateway provide three 
>> services:
>>  - a DNS algorithm that maps IPv4 addresses to a subset of IPv6
>>    addresses.
>>  - a 1:1 NAT algorithm that statelessly supports the common case of
>>    IPv4 clients accessing IPv6 servers, which will be used by a
>>    relatively small set of hosts in the IPv6-only domain.
>>  - 1 1:n NAT algorithm that statefully maps general IPv6 to IPv4
>>    address plus port, which might be used by an arbitrarily large
>>    number of hosts in the IPv6-only domain, but unlikely to be all
>>    at the same time and diminishing as IPv6 deployment grows.
>
> So you _don't_ want to solve the situation where an IPv4-only host 
> gets to talk to any given IPv6 host.
>
> I think it would be fair to call _that_ scenario "hard".
>
> However, I think there are others who are interested in solving this 
> case.
There was some discussion at the Montreal meeting.  I believe I said 
something like

"...folks I work with would like to see solutions in that space, but it 
is certainly not a high priority.  For the foreseeable future, it does 
not seem critical to enable an IPv4-only host to talk to an arbitrary 
number of IPv6-only hosts/servers/applications.  There really aren't any 
to worry about." 

The priorities as I see them are first, make sure a host "turning on" 
IPv6 doesn't lose anything (like access to the whole IPv4 Internet) and 
second, make sure an IPv4-only server is still reachable if somebody 
else (eventually everybody else) turns on IPv6 (either they are 
dual-stack and reach it via IPv4 or through a translator near the 
IPv4-only server). 

The situation where an IPv4-only legacy client keeps working in a world 
where lots of services turn off IPv4 to me seems a "maybe later" problem 
to solve.  Doesn't matter if it's hard - it is deferrable.  Of course, 
framework and other solutions should keep this scenario in mind at least 
to the level of not making it harder to do that later...


> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 08:56:17 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C9643A6A01;
	Fri, 17 Oct 2008 08:56:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7CE773A6A01
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 08:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.013
X-Spam-Level: 
X-Spam-Status: No, score=-106.013 tagged_above=-999 required=5
	tests=[AWL=-0.414, BAYES_00=-2.599, J_BACKHAIR_33=1,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TZW1Z14nwJoj for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 08:56:15 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 4C7B93A67A3
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 08:56:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,432,1220227200"; d="scan'208";a="96339990"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 17 Oct 2008 15:57:18 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9HFvIP6024614; 
	Fri, 17 Oct 2008 08:57:18 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m9HFvILj008471;
	Fri, 17 Oct 2008 15:57:18 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 08:57:18 -0700
Received: from stealth-10-32-244-220.cisco.com ([10.32.244.220]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 08:57:17 -0700
Message-Id: <0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 08:57:15 -0700
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 17 Oct 2008 15:57:17.0880 (UTC)
	FILETIME=[07E73380:01C93071]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3814; t=1224259038;
	x=1225123038; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=x1SI33k99xfNHYc3yjVSuI3SgFOcYOj5rzJ/wmyJQzM=;
	b=GkEbVSAZauwu+vVYIroLg+5nbT/vzT3h9iCP/UrLKZREl86ddc/NsK/jk6
	buQvYloGxqMJ7a383q2+Afsrb1Nz+zlt+yP+SHSjl7jrGFOCxTxbhJM7NX1d
	hnJJmqNs0K;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 17, 2008, at 3:40 AM, Iljitsch van Beijnum wrote:
> So you _don't_ want to solve the situation where an IPv4-only host  
> gets to talk to any given IPv6 host.
>
> I think it would be fair to call _that_ scenario "hard".
>
> However, I think there are others who are interested in solving this  
> case.

Correct on both points. NAT-PT tries to connect any IPv4 to any IPv6,  
and winds up with some "interesting" operational complexity as a  
result. I think that if you want to go after that problem for real,  
the solution you come up with is going to have comparable complexity  
and weaknesses. Willing to be proven wrong, but that's what it looks  
like to me.

However, using an IPv4 address mapped into an IPv6 address as SIIT  
does, we can provide access to a subset of IPv6 nodes - the ones that  
have such an address in addition to their standard IPv6 address. We  
can describe a relatively simple mechanism that will address most  
requirements for quite a while. I would far rather go for the low  
hanging fruit and let those who want to solve the bigger problem do so  
without slowing the relatively easy part down.

In my mind, it is in large part a question of requirements. Would it  
be nice to enable any IPv4 node to access any IPv6 node? of course.  
But is that really needed? I don't think so.

As I said in email during the interim, you really have two application  
cases - client/server (the web and POP/IMAP being examples, and SMTP  
when it is configured to upload mail from an application like OutLook  
to a corporate/ISP mail server), and peer-to-peer. SMTP is peer-to- 
peer between MTAs (TCP sessions are created in both directions), and  
applications like BitTorrent are obviously peer-to-peer.

Obviously you need any client to be able to access any server. Given  
that there are often several orders of magnitude more clients than  
servers in such applications, I have a relatively small translation  
requirement - I don't need any computer to any computer, I only need  
for IPv6 clients to be able to access IPv4 servers (mapped address in  
the client or stateful NATs comparable to present NAT44 will work),  
and IPv4 clients to access IPv6 servers (simply done with a mapped  
address).

For peer to peer applications like SMTP, using mapped addresses makes  
it relatively simple to support them. Since one expects them to be the  
bulk of application traffic, stateless translation has some real  
benefits there as well. Why does one expect that? Well, if one MTA  
serves 10,000 MUAs that each upload less than 100 messages a day, that  
MTA is at any given time talking with only a few of them, perhaps  
10-100. But it will be constantly chatting with the next MTA upstream  
as it sends its clients' 10,000*100 messages along.

For peer to peer applications like BitTorrent, while what would  
otherwise be called "clients" in fact open TCP-like connections willy- 
nilly, they have rules about how they open them. They tend to open a  
few connections that they leave open for a long time and use  
bidirectionally, so opening a connection in the IPv6->IPv4 direction  
works also to move content from the IPv4 domain to the IPv6 domain.  
Within each domain, connections generally work, and content can be  
moved where it needs to be. Using NAT44-like technology, IPv6 systems  
can access IPv4 systems readily. IPv4 systems won't be able to access  
IPv6-native peers, but they won't need to as the content will already  
be in their domain.

So I don't think we need any<->any access anywhere near as much as we  
need the much simpler ability to have IPv4 systems access IPv6  
*servers*, systems that have stable addresses that are generally  
assigned to them anyway.

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 09:24:10 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6ECA93A6A2B;
	Fri, 17 Oct 2008 09:24:10 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF7383A6781
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 09:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g0a8zuhxv35T for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 09:24:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36])
	by core3.amsl.com (Postfix) with ESMTP id 2DC083A6A2B
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 09:24:08 -0700 (PDT)
Received: from rmac.dhcp.nanog.merit.net ([192.35.165.20] helo=rmac.psg.com)
	by ran.psg.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1Kqs8T-000Jmc-Ea; Fri, 17 Oct 2008 16:25:09 +0000
Message-ID: <48F8BC64.10608@psg.com>
Date: Fri, 17 Oct 2008 09:25:08 -0700
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com>
In-Reply-To: <48F8A9F9.6000505@sri.com>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> "...folks I work with would like to see solutions in that space, but it
> is certainly not a high priority.  For the foreseeable future, it does
> not seem critical to enable an IPv4-only host to talk to an arbitrary
> number of IPv6-only hosts/servers/applications.  There really aren't any
> to worry about."

we hope there will be

randy

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 11:28:39 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2BE8A3A6AFA;
	Fri, 17 Oct 2008 11:28:39 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7B543A6AFA
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 11:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.026
X-Spam-Level: 
X-Spam-Status: No, score=-6.026 tagged_above=-999 required=5 tests=[AWL=0.020, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9aPLw4QmiQO3 for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 11:28:38 -0700 (PDT)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM
	[128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id DFC083A6ADF
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 11:28:37 -0700 (PDT)
Received: from smssmtp-internal1.sri.com (128.18.84.115)
	by mailgate-internal3.sri.com with SMTP; 17 Oct 2008 18:29:27 -0000
X-AuditID: 80125473-abce3bb000000a55-22-48f8d9878d6f
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id
	2183E21AF23
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 11:29:27 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K8W00DZQBD2ODD0@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 17 Oct 2008 11:29:27 -0700 (PDT)
Date: Fri, 17 Oct 2008 14:29:24 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <48F8BC64.10608@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <48F8D984.90901@sri.com>
MIME-version: 1.0
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com> <48F8BC64.10608@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

yup.  I really meant to say "right now" and even for the near future, 
don't we still expect most servers/applications to be dual-stack rather 
than IPv6-only?  My point was there are more pressing problems to solve, 
while it would be nice for all variations to work, some can be deferred.

Randy Bush wrote:
>> "...folks I work with would like to see solutions in that space, but it
>> is certainly not a high priority.  For the foreseeable future, it does
>> not seem critical to enable an IPv4-only host to talk to an arbitrary
>> number of IPv6-only hosts/servers/applications.  There really aren't any
>> to worry about."
>>     
>
> we hope there will be
>
> randy
>
>
>   

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 11:35:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CE033A6AF7;
	Fri, 17 Oct 2008 11:35:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 019E73A6AF7
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 11:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id r6VWvGkQztqx for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 11:34:59 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36])
	by core3.amsl.com (Postfix) with ESMTP id 171FA3A6AEC
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 11:34:59 -0700 (PDT)
Received: from rmac.dhcp.nanog.merit.net ([192.35.165.20] helo=rmac.psg.com)
	by ran.psg.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.69 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1KquB7-000K7a-4E; Fri, 17 Oct 2008 18:36:01 +0000
Message-ID: <48F8DB10.6000800@psg.com>
Date: Fri, 17 Oct 2008 11:36:00 -0700
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com> <48F8BC64.10608@psg.com>
	<48F8D984.90901@sri.com>
In-Reply-To: <48F8D984.90901@sri.com>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Ed Jankiewicz wrote:
> yup.  I really meant to say "right now" and even for the near future,
> don't we still expect most servers/applications to be dual-stack rather
> than IPv6-only?  My point was there are more pressing problems to solve,
> while it would be nice for all variations to work, some can be deferred.
> 
> Randy Bush wrote:
>>> "...folks I work with would like to see solutions in that space, but it
>>> is certainly not a high priority.  For the foreseeable future, it does
>>> not seem critical to enable an IPv4-only host to talk to an arbitrary
>>> number of IPv6-only hosts/servers/applications.  There really aren't any
>>> to worry about."
>>>     
>>
>> we hope there will be

i worry that, given history, services may not be able to easily get ipv4
address space before the ietf process produces useful code.

randy
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 12:18:06 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FDB63A6A55;
	Fri, 17 Oct 2008 12:18:06 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9C663A6818
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 12:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.027
X-Spam-Level: 
X-Spam-Status: No, score=-6.027 tagged_above=-999 required=5 tests=[AWL=0.019, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QFqxmsLcwcPd for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 12:18:03 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id D60BF3A6781
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 12:18:03 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 17 Oct 2008 19:19:08 -0000
X-AuditID: 80125474-ae19cbb000000a40-c1-48f8e52cbb3b
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	9BDC321AF2F
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 12:19:08 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K8W00MJ2DNVSV20@mail.sri.com> for
	v4v6interim@ietf.org; Fri, 17 Oct 2008 12:19:08 -0700 (PDT)
Date: Fri, 17 Oct 2008 15:19:06 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <48F8DB10.6000800@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <48F8E52A.3080009@sri.com>
MIME-version: 1.0
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com>
	<48F8BC64.10608@psg.com> <48F8D984.90901@sri.com>
	<48F8DB10.6000800@psg.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

one of my assumptions is that it would be more likely that servers 
already have or could get stable IPv4 addresses, or at least were more 
likely to get the addresses than clients - the asymmetry being lots of 
clients and few servers.   Several folks have suggested that the 
remaining IPv4 addresses or at least portions of that space should be 
reserved for uses that encourage IPv6.  Giving an address to a 
dual-stack server so it can still be reached by IPv4 clients seems like 
a good use.  Requiring every new IPv6 subscriber to also have a unique 
IPv4 address would not be as "cost effective".

Of course, that doesn't take p2p into account where everyone is a 
server, but there should be other ways for those folks to find each other. 

Randy Bush wrote:
> Ed Jankiewicz wrote:
>   
>> yup.  I really meant to say "right now" and even for the near future,
>> don't we still expect most servers/applications to be dual-stack rather
>> than IPv6-only?  My point was there are more pressing problems to solve,
>> while it would be nice for all variations to work, some can be deferred.
>>
>> Randy Bush wrote:
>>     
>>>> "...folks I work with would like to see solutions in that space, but it
>>>> is certainly not a high priority.  For the foreseeable future, it does
>>>> not seem critical to enable an IPv4-only host to talk to an arbitrary
>>>> number of IPv6-only hosts/servers/applications.  There really aren't any
>>>> to worry about."
>>>>     
>>>>         
>>> we hope there will be
>>>       
>
> i worry that, given history, services may not be able to easily get ipv4
> address space before the ietf process produces useful code.
>
> randy
>
>   

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 12:41:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4403A3A690A;
	Fri, 17 Oct 2008 12:41:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDB7F3A65A5
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 12:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.954
X-Spam-Level: 
X-Spam-Status: No, score=-5.954 tagged_above=-999 required=5 tests=[AWL=0.645, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jDLH57Qn4T0X for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 12:41:40 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id B6EB83A690A
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 12:41:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,434,1220227200"; d="scan'208";a="22987903"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 17 Oct 2008 19:42:33 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9HJgX1Z031186; 
	Fri, 17 Oct 2008 21:42:33 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9HJgXY8018628;
	Fri, 17 Oct 2008 19:42:33 GMT
Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 21:42:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 21:42:49 +0200
Message-ID: <CE2BF2A7B1008C459FD7978065C6ECE007AB5E01@xmb-ams-33a.emea.cisco.com>
In-Reply-To: <48F8E52A.3080009@sri.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] "IPv4->IPv6 is hard"
Thread-Index: AckwjUA61/+qeknHS4OyfKDQit6iCAAAx6kQ
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com><4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com><48F8A9F9.6000505@sri.com><48F8BC64.10608@psg.com>
	<48F8D984.90901@sri.com><48F8DB10.6000800@psg.com>
	<48F8E52A.3080009@sri.com>
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "Ed Jankiewicz" <edward.jankiewicz@sri.com>, "Randy Bush" <randy@psg.com>
X-OriginalArrivalTime: 17 Oct 2008 19:42:33.0527 (UTC)
	FILETIME=[7FDB4470:01C93090]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=473; t=1224272553; x=1225136553;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=evyncke@cisco.com;
	z=From:=20=22Eric=20Vyncke=20(evyncke)=22=20<evyncke@cisco.c
	om> |Subject:=20RE=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=rBVDDRdYu6JvXuYwSefp/YDnebaEMssPsRY9fHmiKV4=;
	b=lY59033OxvcgFr1QTmdI8Qqpd3zS0yDM6Od3GYQMUyxob5kqa7iMoSWfMt
	zdzPDrD0w2mfLNibW4WeJ1rVI7w1kxwFPhoXRFEv+oysVDqtdFTvFqm9/2af
	cgjW6kHjfW;
Authentication-Results: ams-dkim-1; header.From=evyncke@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 > -----Original Message-----
> From: v4v6interim-bounces@ietf.org 
> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Ed Jankiewicz
> 
> Of course, that doesn't take p2p into account where everyone 
> is a server, but there should be other ways for those folks 
> to find each other. 
>

And we all know that P2P applications are pretty flexible to work around
network constraints, being NAT or IPv6 (and utorrent already supports
IPv6 anyway) :-)
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 13:21:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED7483A6AD9;
	Fri, 17 Oct 2008 13:21:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB7EB3A6AD9
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 13:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.512
X-Spam-Level: 
X-Spam-Status: No, score=-106.512 tagged_above=-999 required=5
	tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p7BjzHk4bYSt for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 13:21:25 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 025FF3A6A57
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 13:21:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,434,1220227200"; d="scan'208";a="109389613"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 17 Oct 2008 20:22:30 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9HKMUCq002180; 
	Fri, 17 Oct 2008 13:22:30 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9HKMTvZ011287;
	Fri, 17 Oct 2008 20:22:29 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:22:29 -0700
Received: from stealth-10-32-244-220.cisco.com ([10.32.244.220]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:22:29 -0700
Message-Id: <B4CCC195-FD5A-4260-AF60-4B74D5532D52@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-Reply-To: <48F8E52A.3080009@sri.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 13:22:29 -0700
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com> <48F8BC64.10608@psg.com>
	<48F8D984.90901@sri.com> <48F8DB10.6000800@psg.com>
	<48F8E52A.3080009@sri.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 17 Oct 2008 20:22:29.0570 (UTC)
	FILETIME=[14026A20:01C93096]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=525; t=1224274950; x=1225138950;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=9edZGcti5X2oA4jTr71zDQWvJrzj/fsUfi1DhF/BAR0=;
	b=lJxAgRgzO6QfbYRG4ezTJsRppDFVoR8a0iJ+A4HKqNwRAN7Z+r7d/hDojS
	fP/5QMAbzDa4UYIuOxLtFGRY9bl0/G/oJiL2sC4b9M6m3ULjITTinupOXYr/
	KgI6pf5vP5;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 17, 2008, at 12:19 PM, Ed Jankiewicz wrote:

> Of course, that doesn't take p2p into account where everyone is a  
> server, but there should be other ways for those folks to find each  
> other.

I think that it isn't necessary to consider every p2p application  
instance a "server". As I noted this morning, they will naturally  
resolve a lot of that. And to the extent that they don't, that becomes  
a reason to deploy dual stack, which is what we have been recommending  
for some time now anyway.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 13:40:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D2D33A6AE8;
	Fri, 17 Oct 2008 13:40:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C4E53A6AFE
	for <v4v6interim@core3.amsl.com>; Fri, 17 Oct 2008 13:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.514
X-Spam-Level: 
X-Spam-Status: No, score=-106.514 tagged_above=-999 required=5
	tests=[AWL=0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Su1ZHMzDbF6J for <v4v6interim@core3.amsl.com>;
	Fri, 17 Oct 2008 13:40:54 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 4FA653A6AE8
	for <v4v6interim@ietf.org>; Fri, 17 Oct 2008 13:40:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,434,1220227200"; d="scan'208";a="109393242"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 17 Oct 2008 20:41:59 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9HKfxv0032318; 
	Fri, 17 Oct 2008 13:41:59 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9HKfxSI008325;
	Fri, 17 Oct 2008 20:41:59 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:41:59 -0700
Received: from stealth-10-32-244-220.cisco.com ([10.32.244.220]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:41:58 -0700
Message-Id: <0F936B42-2FB9-413B-ADDF-BE881730F95E@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-Reply-To: <48F8D984.90901@sri.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 13:41:58 -0700
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>
	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<48F8A9F9.6000505@sri.com> <48F8BC64.10608@psg.com>
	<48F8D984.90901@sri.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 17 Oct 2008 20:41:58.0837 (UTC)
	FILETIME=[CCF26650:01C93098]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1787; t=1224276119;
	x=1225140119; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=GnpAQogoIABWmWMA848kH8VpstiaN0NvuEgVVrAuUAo=;
	b=SjP8dphFu9E/1zjgSLpDEpweyOZcZehkaolho6fOFpNI9bapWtf7Kt7b2r
	2ggGGINdDitDjxF0ammfG3MTXnclXi1yodDWzJwqYZmeGfgQKeTf/P1cxTNK
	WfZYtEumBJ;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 17, 2008, at 11:29 AM, Ed Jankiewicz wrote:

> yup.  I really meant to say "right now" and even for the near  
> future, don't we still expect most servers/applications to be dual- 
> stack rather than IPv6-only?  My point was there are more pressing  
> problems to solve, while it would be nice for all variations to  
> work, some can be deferred.

One has to define "dual stack".

Everything that runs on my Mac is potentially dual stack, in the sense  
that the code is there to run both IPv4 and IPv6. Present it with an  
IPv4 network, it does so. Present it with an IPv6 network, it does so.

It the thing it needs to talk with is IPvX and it only has IPvY  
routing, however, it can't get there. From my home I can't access  
ipv6.google.com because no ISP in Santa Barbara County runs IPv6.

The DS-Lite model says that I should set up a tunnel across the IPv4  
infrastructure, whether from my host or from my router; 6to4 is  
similar, as are others.

The translation model says that the host should use the network  
available to it and something in the network should change the  
protocol when and where it must.

My personal preference is for dual stack deployment, and where  
necessary to change as little as possible, as the changes will outlive  
the need for them by decades. Asking the host to build tunnels is an  
example of such a change. Under the ISP's control or at least in  
collusion with it, I can see building tunnels. But even there, as the  
ISPs deploy IPv6 that becomes a change that will outlive the need for  
it. That's why I'm working on translation - enable the network  
administration to install what it needs to when it needs it, and  
enable it to remove it when the need goes away.

my two yen

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 17 15:41:31 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0620228C14A;
	Fri, 17 Oct 2008 15:41:31 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 625E53A6874;
	Fri, 17 Oct 2008 15:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.53
X-Spam-Level: 
X-Spam-Status: No, score=-6.53 tagged_above=-999 required=5 tests=[AWL=0.069, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7uyvFxvR8BIh; Fri, 17 Oct 2008 15:41:29 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 5AD293A6847;
	Fri, 17 Oct 2008 15:41:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,434,1220227200"; d="scan'208";a="109410835"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 17 Oct 2008 22:42:35 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9HMgYIo029682; 
	Fri, 17 Oct 2008 15:42:34 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9HMgYEm021852;
	Fri, 17 Oct 2008 22:42:34 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Margaret Wasserman'" <mrw@lilacglade.org>,
	"'Behave WG'" <behave@ietf.org>
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
Date: Fri, 17 Oct 2008 15:42:34 -0700
Message-ID: <024001c930a9$a5d00710$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
thread-index: AckwZXDa87nyt1UTQMC1l+rF0/21XQAQbiUA
In-Reply-To: <E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2901; t=1224283354;
	x=1225147354; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20[v4v6interim]=20Proposal=20f
	or=20new=20BEHAVE=20charter |Sender:=20;
	bh=p76L4Qnf0p7ex7ds7+n0KBBE52av4r4QYHdQIyOLWUQ=;
	b=Y1p2quF+c2s925oeHp3En4+rOw7ZZE7Fvm9t3fGoYiNCfG+eQRK8Pox0iy
	BP9M19zO7bAP+YFkMNQznaTEwPPAdu/vyFjSutOh7p3cNwJaUdV0NdQiXN6k
	NOLr1VVxEb;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>
Subject: Re: [v4v6interim] [BEHAVE]  Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Margaret Wasserman wrote:

...
> > BEHAVE will develop protocol-independent toolkits usable by  
> > application
> > protocols for NAT traversal. The WG has already produced an 
> > update of
> > the binding discovery protocol STUN. It will now produce a relay
> > protocol that focuses on security that is usable with both IPv4 and
> > IPv6, and capable of relaying between the two IP versions.
> 
> Is there a draft available on which this work will be based?  
> I'm not suggesting that you mention it in the charter, I'd just 
> like to know which draft I should be reading for this item.

Yes, they are:

  draft-ietf-behave-turn (nearing completion)
  draft-ietf-behave-turn-ipv6 (expired, but a new version is
                               being submitted shortly that 
                               aligns it with TURN)
  draft-ietf-behave-turn-tcp (will be discussed in Minneapolis)

...
> I would also like to us write (at least) two NAT-related 
> documents that aren't listed here:
> 
> (1) A document that offers advice on how/when to deploy these  
> translation mechanisms vs. other choices.  I think this document 
> would cover topics such as:
> 
> 	- If the infrastructure will support dual stack and you 
> are running out
>            of IPv4 addresses, NAT IPv4 and leave IPv6 alone.

Alain, Dave Thaler, Jari, and I are co-authoring a document
that will discuss when-to-translate and when-to-dual-stack-lite.

I don't know if such a document would belong in BEHAVE or
SOFTWIRES -- it spans between the two WGs.

> 	- The advantages of placing NATs closer to the edges of 
> the network

I don't believe anyone has submitted an I-D that delves into
those advantages or those disadvantages.  Certainly, there is
a lot of experience with NATs close to the edges -- those
are the NATs that Linksys/D-Link/Netgear/etc. have been 
selling for years.

> (2) An explanation of how to do IPv6 <=> IPv6 NAT.  It am 
> convinced that there are some people who will choose to do 
> this for the same reasons that people with plenty of IPv4 
> addresses choose to use IPv4 <=> IPv4 NATs today.  I think we 
> could write a document that says something like:   IPv6
> <=> IPv6 NATs are not really necessary, don't provide any concrete  
> advantages that can't be obtained through less disruptive 
> means, and are not recommended by the IETF, but if you are 
> planning to do this anyway, please do it right (don't
> include port translation, use algorithmic address mapping if 
> possible, instead of state tables, etc.).

NAT44 has been a third rail (*) in the IETF for over a decade, 
and NAT64 and NAT46 have only recently emerged as a way forward 
to help with the eventual transition to IPv6.  

NAT66 is still a third rail.  I don't want to go there.

(*) <http://en.wikipedia.org/wiki/Political_third_rail>

-d

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sun Oct 19 13:44:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C4A73A6AB5;
	Sun, 19 Oct 2008 13:44:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D9583A6AB7
	for <v4v6interim@core3.amsl.com>; Sun, 19 Oct 2008 13:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TSTI6HFKgqlV for <v4v6interim@core3.amsl.com>;
	Sun, 19 Oct 2008 13:44:12 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239])
	by core3.amsl.com (Postfix) with ESMTP id D63B63A6AB5
	for <v4v6interim@ietf.org>; Sun, 19 Oct 2008 13:44:12 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1316099rvf.49
	for <v4v6interim@ietf.org>; Sun, 19 Oct 2008 13:45:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=nZ6zAoQMq83gmSTiEaVvC9IbUqeZwgRcZ7CILIdO07k=;
	b=qJj8V3GJxC9BCaH1vYrpOwwyoUOzqROBr+9h4sC7le3Um2MAaa7NMXFEyY3XGAR6FH
	B8QQbVjZUhMBTw1h7nwsSqKJJUZ+cBBt4z8geNqWXjDTj7uD78riM8XcMehaIVP2TZl/
	MDFP0loCfB9cOE/nlM2geq6kNgTdZzBKt+SPQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=DwJq9TcNUUh/wQp4FUOO9Qyo1AexKvCp07iY1Bxb4bwtasobIhU45ucTTkKtBhCaNH
	5z527hAZGlLOr1rVKl+j3MLSwegJsO2XjNicXqy9p53tSN9u1TXmGKCB06PmyNVpHb3F
	6RvgHoiH4MqlISEjzL2Bq6GlIs064iUkmDa4Q=
Received: by 10.141.71.14 with SMTP id y14mr4302182rvk.24.1224449121696;
	Sun, 19 Oct 2008 13:45:21 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id l31sm17013600rvb.2.2008.10.19.13.45.19
	(version=SSLv3 cipher=RC4-MD5); Sun, 19 Oct 2008 13:45:21 -0700 (PDT)
Message-ID: <48FB9C5E.8070402@gmail.com>
Date: Mon, 20 Oct 2008 09:45:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<024001c930a9$a5d00710$c3f0200a@cisco.com>
In-Reply-To: <024001c930a9$a5d00710$c3f0200a@cisco.com>
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-18 11:42, Dan Wing wrote:
> Margaret Wasserman wrote:

...
>> (2) An explanation of how to do IPv6 <=> IPv6 NAT.  It am 
>> convinced that there are some people who will choose to do 
>> this for the same reasons that people with plenty of IPv4 
>> addresses choose to use IPv4 <=> IPv4 NATs today.  I think we 
>> could write a document that says something like:   IPv6
>> <=> IPv6 NATs are not really necessary, don't provide any concrete  
>> advantages that can't be obtained through less disruptive 
>> means, and are not recommended by the IETF, but if you are 
>> planning to do this anyway, please do it right (don't
>> include port translation, use algorithmic address mapping if 
>> possible, instead of state tables, etc.).
> 
> NAT44 has been a third rail (*) in the IETF for over a decade, 
> and NAT64 and NAT46 have only recently emerged as a way forward 
> to help with the eventual transition to IPv6.  
> 
> NAT66 is still a third rail.  I don't want to go there.

Yep. As Margaret well knows, RFC4864 was written to try to avoid
stepping on that rail, and includes a gap analysis of what's
needed to avoid it. I'd rather the IETF put effort into those
gaps.

    Brian
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sun Oct 19 22:20:07 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 271133A68E1;
	Sun, 19 Oct 2008 22:20:07 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9CF63A68E1
	for <v4v6interim@core3.amsl.com>; Sun, 19 Oct 2008 22:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.62
X-Spam-Level: *
X-Spam-Status: No, score=1.62 tagged_above=-999 required=5 tests=[AWL=-2.121, 
	BAYES_50=0.001, DATE_IN_PAST_03_06=0.044, FH_HAS_XAIMC=2.696,
	J_BACKHAIR_33=1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5uc8ftnmmFIH for <v4v6interim@core3.amsl.com>;
	Sun, 19 Oct 2008 22:20:04 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66])
	by core3.amsl.com (Postfix) with SMTP id 1D3003A6885
	for <v4v6interim@ietf.org>; Sun, 19 Oct 2008 22:20:03 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0)
	with SMTP id jm2348fc2c3a; Mon, 20 Oct 2008 13:21:13 +0800
Message-ID: <48FBC96D.5020207@cernet.edu.cn>
Date: Mon, 20 Oct 2008 07:57:33 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>
	<0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
In-Reply-To: <0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: jmbMnrUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

RnJlZCBCYWtlciDlhpnpgZM6Cj4KPiBPbiBPY3QgMTcsIDIwMDgsIGF0IDM6NDAgQU0sIElsaml0
c2NoIHZhbiBCZWlqbnVtIHdyb3RlOgo+PiBTbyB5b3UgX2Rvbid0XyB3YW50IHRvIHNvbHZlIHRo
ZSBzaXR1YXRpb24gd2hlcmUgYW4gSVB2NC1vbmx5IGhvc3QgCj4+IGdldHMgdG8gdGFsayB0byBh
bnkgZ2l2ZW4gSVB2NiBob3N0Lgo+Pgo+PiBJIHRoaW5rIGl0IHdvdWxkIGJlIGZhaXIgdG8gY2Fs
bCBfdGhhdF8gc2NlbmFyaW8gImhhcmQiLgo+Pgo+PiBIb3dldmVyLCBJIHRoaW5rIHRoZXJlIGFy
ZSBvdGhlcnMgd2hvIGFyZSBpbnRlcmVzdGVkIGluIHNvbHZpbmcgdGhpcyAKPj4gY2FzZS4KPgo+
IENvcnJlY3Qgb24gYm90aCBwb2ludHMuIE5BVC1QVCB0cmllcyB0byBjb25uZWN0IGFueSBJUHY0
IHRvIGFueSBJUHY2LCAKPiBhbmQgd2luZHMgdXAgd2l0aCBzb21lICJpbnRlcmVzdGluZyIgb3Bl
cmF0aW9uYWwgY29tcGxleGl0eSBhcyBhIAo+IHJlc3VsdC4gSSB0aGluayB0aGF0IGlmIHlvdSB3
YW50IHRvIGdvIGFmdGVyIHRoYXQgcHJvYmxlbSBmb3IgcmVhbCwgCj4gdGhlIHNvbHV0aW9uIHlv
dSBjb21lIHVwIHdpdGggaXMgZ29pbmcgdG8gaGF2ZSBjb21wYXJhYmxlIGNvbXBsZXhpdHkgCj4g
YW5kIHdlYWtuZXNzZXMuIFdpbGxpbmcgdG8gYmUgcHJvdmVuIHdyb25nLCBidXQgdGhhdCdzIHdo
YXQgaXQgbG9va3MgCj4gbGlrZSB0byBtZS4KPgo+IEhvd2V2ZXIsIHVzaW5nIGFuIElQdjQgYWRk
cmVzcyBtYXBwZWQgaW50byBhbiBJUHY2IGFkZHJlc3MgYXMgU0lJVCAKPiBkb2VzLCB3ZSBjYW4g
cHJvdmlkZSBhY2Nlc3MgdG8gYSBzdWJzZXQgb2YgSVB2NiBub2RlcyAtIHRoZSBvbmVzIHRoYXQg
Cj4gaGF2ZSBzdWNoIGFuIGFkZHJlc3MgaW4gYWRkaXRpb24gdG8gdGhlaXIgc3RhbmRhcmQgSVB2
NiBhZGRyZXNzLiBXZSAKPiBjYW4gZGVzY3JpYmUgYSByZWxhdGl2ZWx5IHNpbXBsZSBtZWNoYW5p
c20gdGhhdCB3aWxsIGFkZHJlc3MgbW9zdCAKPiByZXF1aXJlbWVudHMgZm9yIHF1aXRlIGEgd2hp
bGUuIEkgd291bGQgZmFyIHJhdGhlciBnbyBmb3IgdGhlIGxvdyAKPiBoYW5naW5nIGZydWl0IGFu
ZCBsZXQgdGhvc2Ugd2hvIHdhbnQgdG8gc29sdmUgdGhlIGJpZ2dlciBwcm9ibGVtIGRvIHNvIAo+
IHdpdGhvdXQgc2xvd2luZyB0aGUgcmVsYXRpdmVseSBlYXN5IHBhcnQgZG93bi4KPgo+IEluIG15
IG1pbmQsIGl0IGlzIGluIGxhcmdlIHBhcnQgYSBxdWVzdGlvbiBvZiByZXF1aXJlbWVudHMuIFdv
dWxkIGl0IAo+IGJlIG5pY2UgdG8gZW5hYmxlIGFueSBJUHY0IG5vZGUgdG8gYWNjZXNzIGFueSBJ
UHY2IG5vZGU/IG9mIGNvdXJzZS4gCj4gQnV0IGlzIHRoYXQgcmVhbGx5IG5lZWRlZD8gSSBkb24n
dCB0aGluayBzby4KPgo+IEFzIEkgc2FpZCBpbiBlbWFpbCBkdXJpbmcgdGhlIGludGVyaW0sIHlv
dSByZWFsbHkgaGF2ZSB0d28gYXBwbGljYXRpb24gCj4gY2FzZXMgLSBjbGllbnQvc2VydmVyICh0
aGUgd2ViIGFuZCBQT1AvSU1BUCBiZWluZyBleGFtcGxlcywgYW5kIFNNVFAgCj4gd2hlbiBpdCBp
cyBjb25maWd1cmVkIHRvIHVwbG9hZCBtYWlsIGZyb20gYW4gYXBwbGljYXRpb24gbGlrZSBPdXRM
b29rIAo+IHRvIGEgY29ycG9yYXRlL0lTUCBtYWlsIHNlcnZlciksIGFuZCBwZWVyLXRvLXBlZXIu
IFNNVFAgaXMgCj4gcGVlci10by1wZWVyIGJldHdlZW4gTVRBcyAoVENQIHNlc3Npb25zIGFyZSBj
cmVhdGVkIGluIGJvdGggCj4gZGlyZWN0aW9ucyksIGFuZCBhcHBsaWNhdGlvbnMgbGlrZSBCaXRU
b3JyZW50IGFyZSBvYnZpb3VzbHkgcGVlci10by1wZWVyLgo+Cj4gT2J2aW91c2x5IHlvdSBuZWVk
IGFueSBjbGllbnQgdG8gYmUgYWJsZSB0byBhY2Nlc3MgYW55IHNlcnZlci4gR2l2ZW4gCj4gdGhh
dCB0aGVyZSBhcmUgb2Z0ZW4gc2V2ZXJhbCBvcmRlcnMgb2YgbWFnbml0dWRlIG1vcmUgY2xpZW50
cyB0aGFuIAo+IHNlcnZlcnMgaW4gc3VjaCBhcHBsaWNhdGlvbnMsIEkgaGF2ZSBhIHJlbGF0aXZl
bHkgc21hbGwgdHJhbnNsYXRpb24gCj4gcmVxdWlyZW1lbnQgLSBJIGRvbid0IG5lZWQgYW55IGNv
bXB1dGVyIHRvIGFueSBjb21wdXRlciwgSSBvbmx5IG5lZWQgCj4gZm9yIElQdjYgY2xpZW50cyB0
byBiZSBhYmxlIHRvIGFjY2VzcyBJUHY0IHNlcnZlcnMgKG1hcHBlZCBhZGRyZXNzIGluIAo+IHRo
ZSBjbGllbnQgb3Igc3RhdGVmdWwgTkFUcyBjb21wYXJhYmxlIHRvIHByZXNlbnQgTkFUNDQgd2ls
bCB3b3JrKSwgCj4gYW5kIElQdjQgY2xpZW50cyB0byBhY2Nlc3MgSVB2NiBzZXJ2ZXJzIChzaW1w
bHkgZG9uZSB3aXRoIGEgbWFwcGVkIAo+IGFkZHJlc3MpLgo+Cj4gRm9yIHBlZXIgdG8gcGVlciBh
cHBsaWNhdGlvbnMgbGlrZSBTTVRQLCB1c2luZyBtYXBwZWQgYWRkcmVzc2VzIG1ha2VzIAo+IGl0
IHJlbGF0aXZlbHkgc2ltcGxlIHRvIHN1cHBvcnQgdGhlbS4gU2luY2Ugb25lIGV4cGVjdHMgdGhl
bSB0byBiZSB0aGUgCj4gYnVsayBvZiBhcHBsaWNhdGlvbiB0cmFmZmljLCBzdGF0ZWxlc3MgdHJh
bnNsYXRpb24gaGFzIHNvbWUgcmVhbCAKPiBiZW5lZml0cyB0aGVyZSBhcyB3ZWxsLiBXaHkgZG9l
cyBvbmUgZXhwZWN0IHRoYXQ/IFdlbGwsIGlmIG9uZSBNVEEgCj4gc2VydmVzIDEwLDAwMCBNVUFz
IHRoYXQgZWFjaCB1cGxvYWQgbGVzcyB0aGFuIDEwMCBtZXNzYWdlcyBhIGRheSwgdGhhdCAKPiBN
VEEgaXMgYXQgYW55IGdpdmVuIHRpbWUgdGFsa2luZyB3aXRoIG9ubHkgYSBmZXcgb2YgdGhlbSwg
cGVyaGFwcyAKPiAxMC0xMDAuIEJ1dCBpdCB3aWxsIGJlIGNvbnN0YW50bHkgY2hhdHRpbmcgd2l0
aCB0aGUgbmV4dCBNVEEgdXBzdHJlYW0gCj4gYXMgaXQgc2VuZHMgaXRzIGNsaWVudHMnIDEwLDAw
MCoxMDAgbWVzc2FnZXMgYWxvbmcuCj4KPiBGb3IgcGVlciB0byBwZWVyIGFwcGxpY2F0aW9ucyBs
aWtlIEJpdFRvcnJlbnQsIHdoaWxlIHdoYXQgd291bGQgCj4gb3RoZXJ3aXNlIGJlIGNhbGxlZCAi
Y2xpZW50cyIgaW4gZmFjdCBvcGVuIFRDUC1saWtlIGNvbm5lY3Rpb25zIAo+IHdpbGx5LW5pbGx5
LCB0aGV5IGhhdmUgcnVsZXMgYWJvdXQgaG93IHRoZXkgb3BlbiB0aGVtLiBUaGV5IHRlbmQgdG8g
Cj4gb3BlbiBhIGZldyBjb25uZWN0aW9ucyB0aGF0IHRoZXkgbGVhdmUgb3BlbiBmb3IgYSBsb25n
IHRpbWUgYW5kIHVzZSAKPiBiaWRpcmVjdGlvbmFsbHksIHNvIG9wZW5pbmcgYSBjb25uZWN0aW9u
IGluIHRoZSBJUHY2LT5JUHY0IGRpcmVjdGlvbiAKPiB3b3JrcyBhbHNvIHRvIG1vdmUgY29udGVu
dCBmcm9tIHRoZSBJUHY0IGRvbWFpbiB0byB0aGUgSVB2NiBkb21haW4uIAo+IFdpdGhpbiBlYWNo
IGRvbWFpbiwgY29ubmVjdGlvbnMgZ2VuZXJhbGx5IHdvcmssIGFuZCBjb250ZW50IGNhbiBiZSAK
PiBtb3ZlZCB3aGVyZSBpdCBuZWVkcyB0byBiZS4gVXNpbmcgTkFUNDQtbGlrZSB0ZWNobm9sb2d5
LCBJUHY2IHN5c3RlbXMgCj4gY2FuIGFjY2VzcyBJUHY0IHN5c3RlbXMgcmVhZGlseS4gSVB2NCBz
eXN0ZW1zIHdvbid0IGJlIGFibGUgdG8gYWNjZXNzIAo+IElQdjYtbmF0aXZlIHBlZXJzLCBidXQg
dGhleSB3b24ndCBuZWVkIHRvIGFzIHRoZSBjb250ZW50IHdpbGwgYWxyZWFkeSAKPiBiZSBpbiB0
aGVpciBkb21haW4uCj4KPiBTbyBJIGRvbid0IHRoaW5rIHdlIG5lZWQgYW55PC0+YW55IGFjY2Vz
cyBhbnl3aGVyZSBuZWFyIGFzIG11Y2ggYXMgd2UgCj4gbmVlZCB0aGUgbXVjaCBzaW1wbGVyIGFi
aWxpdHkgdG8gaGF2ZSBJUHY0IHN5c3RlbXMgYWNjZXNzIElQdjYgCj4gKnNlcnZlcnMqLCBzeXN0
ZW1zIHRoYXQgaGF2ZSBzdGFibGUgYWRkcmVzc2VzIHRoYXQgYXJlIGdlbmVyYWxseSAKPiBhc3Np
Z25lZCB0byB0aGVtIGFueXdheS4KClRoYW5rcyEKClNvbWUgYWRkaXRpb25hbCBub3RlcyBiYXNl
ZCBvbiBDRVJORVQgdHdvIHllYXJzIGV4cGVyaWVuY2Ugb2YgcnVubmluZyBhCnB1cmUgSVB2NiBi
YWNrYm9uZS4KCldlIGJlbGlldmUgdGhlIHNlbGVjdGlvbiBvZiB0aGUgc2NlbmFyaW9zIGNvdWxk
IGJlIGJhc2VkIG9uIHRoZQppbmNlbnRpdmUgb2YgdGhlIG93bmVyIG9mIHRoZSBJUHY2IGhvc3Rz
LgooMSkgSWYgdGhlIElQdjYgaG9zdCBuZWVkcyB0byBiZSBhbiBJUHY0LWFjY2Vzc2libGUgc2Vy
dmVyLCB0aGV5IHdpbGwKdXNlIHRoZSBJVkkgYWRkcmVzcy4gT3RoZXJ3aXNlLCBpdCB3aWxsIHVz
ZSBub24tSVZJIGFkZHJlc3MuIFRoaXMgaXMgdG8Kc2F5IHRoYXQgdGhlcmUgaXMgbm8gbmVlZCB0
byBwcm92aWRlIGEgZ2VuZXJhbCBzY2hlbWUgZm9yIGFueSBJUHY0IGhvc3QKaW5pdGlhdGVzIGNv
bW11bmljYXRpb24gd2l0aCBBTlkgSVB2NiBob3N0LCBzaW5jZSB0aGUgb3duZXIgb2YgdGhlIElQ
djYKaG9zdCBjYW4gc2VsZWN0IHRoZSBzdWl0YWJsZSBjYXRlZ29yeSBvZiB0aGUgSVB2NiBhZGRy
ZXNzZXMuCigyKSBBcyB0aGUgSVNQLCB3ZSBwcmljZSBJVkkgYWRkcmVzc2VzICgxOjEgbWFwcGlu
ZyBvZiBJUHY0IGFkZHJlc3MsCnNjYXJjZSByZXNvdXJjZSkgYW5kIG5vbi1JVkkgYWRkcmVzc2Vz
IChub24tc2NhcmNlIHJlc291cmNlKQpkaWZmZXJlbnRseS4gU28gaXQgaXMgYWxzbyBlY29ub21p
Y2FsbHkgcmVhc29uYWJsZS4KCkp1c3Qgb3VyIHR3byBjZW50cy4KCnhpbmcKPgo+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gdjR2NmludGVyaW0gbWFp
bGluZyBsaXN0Cj4gdjR2NmludGVyaW1AaWV0Zi5vcmcKPiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3Y0djZpbnRlcmltCj4KPgoKCgoKX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KdjR2NmludGVyaW0gbWFpbGluZyBsaXN0CnY0djZp
bnRlcmltQGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2
NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Sun Oct 19 23:52:44 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B05223A68F3;
	Sun, 19 Oct 2008 23:52:44 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C9A33A6833
	for <v4v6interim@core3.amsl.com>; Sun, 19 Oct 2008 23:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.383
X-Spam-Level: 
X-Spam-Status: No, score=-3.383 tagged_above=-999 required=5
	tests=[AWL=-0.621, BAYES_00=-2.599, J_BACKHAIR_33=1,
	RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y987RTWqAyGB for <v4v6interim@core3.amsl.com>;
	Sun, 19 Oct 2008 23:52:42 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 2FD3E3A68F3
	for <v4v6interim@ietf.org>; Sun, 19 Oct 2008 23:52:41 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local 
	(67.pool85-53-133.dynamic.orange.es [85.53.133.67])by smtp02.uc3m.es 
	(Postfix) with ESMTP id CA0EE5C3365;
	Mon, 20 Oct 2008 08:53:48 +0200 (CEST)
Message-ID: <48FC2AFC.60405@it.uc3m.es>
Date: Mon, 20 Oct 2008 08:53:48 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-
	4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
	<48FBC96D.5020207@cernet.edu.cn>
In-Reply-To: <48FBC96D.5020207@cernet.edu.cn>
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:N SM:2
X-imss-tmaseResult: TT:1 TS:-19.2161 TC:1F TRN:89 TV:5.5.1026(16228.004)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

WGluZyBMaSBlc2NyaWJpw7M6Cj4gRnJlZCBCYWtlciDlhpnpgZM6Cj4+Cj4+IE9uIE9jdCAxNywg
MjAwOCwgYXQgMzo0MCBBTSwgSWxqaXRzY2ggdmFuIEJlaWpudW0gd3JvdGU6Cj4+PiBTbyB5b3Ug
X2Rvbid0XyB3YW50IHRvIHNvbHZlIHRoZSBzaXR1YXRpb24gd2hlcmUgYW4gSVB2NC1vbmx5IGhv
c3QgCj4+PiBnZXRzIHRvIHRhbGsgdG8gYW55IGdpdmVuIElQdjYgaG9zdC4KPj4+Cj4+PiBJIHRo
aW5rIGl0IHdvdWxkIGJlIGZhaXIgdG8gY2FsbCBfdGhhdF8gc2NlbmFyaW8gImhhcmQiLgo+Pj4K
Pj4+IEhvd2V2ZXIsIEkgdGhpbmsgdGhlcmUgYXJlIG90aGVycyB3aG8gYXJlIGludGVyZXN0ZWQg
aW4gc29sdmluZyB0aGlzIAo+Pj4gY2FzZS4KPj4KPj4gQ29ycmVjdCBvbiBib3RoIHBvaW50cy4g
TkFULVBUIHRyaWVzIHRvIGNvbm5lY3QgYW55IElQdjQgdG8gYW55IElQdjYsIAo+PiBhbmQgd2lu
ZHMgdXAgd2l0aCBzb21lICJpbnRlcmVzdGluZyIgb3BlcmF0aW9uYWwgY29tcGxleGl0eSBhcyBh
IAo+PiByZXN1bHQuIEkgdGhpbmsgdGhhdCBpZiB5b3Ugd2FudCB0byBnbyBhZnRlciB0aGF0IHBy
b2JsZW0gZm9yIHJlYWwsIAo+PiB0aGUgc29sdXRpb24geW91IGNvbWUgdXAgd2l0aCBpcyBnb2lu
ZyB0byBoYXZlIGNvbXBhcmFibGUgY29tcGxleGl0eSAKPj4gYW5kIHdlYWtuZXNzZXMuIFdpbGxp
bmcgdG8gYmUgcHJvdmVuIHdyb25nLCBidXQgdGhhdCdzIHdoYXQgaXQgbG9va3MgCj4+IGxpa2Ug
dG8gbWUuCj4+Cj4+IEhvd2V2ZXIsIHVzaW5nIGFuIElQdjQgYWRkcmVzcyBtYXBwZWQgaW50byBh
biBJUHY2IGFkZHJlc3MgYXMgU0lJVCAKPj4gZG9lcywgd2UgY2FuIHByb3ZpZGUgYWNjZXNzIHRv
IGEgc3Vic2V0IG9mIElQdjYgbm9kZXMgLSB0aGUgb25lcyB0aGF0IAo+PiBoYXZlIHN1Y2ggYW4g
YWRkcmVzcyBpbiBhZGRpdGlvbiB0byB0aGVpciBzdGFuZGFyZCBJUHY2IGFkZHJlc3MuIFdlIAo+
PiBjYW4gZGVzY3JpYmUgYSByZWxhdGl2ZWx5IHNpbXBsZSBtZWNoYW5pc20gdGhhdCB3aWxsIGFk
ZHJlc3MgbW9zdCAKPj4gcmVxdWlyZW1lbnRzIGZvciBxdWl0ZSBhIHdoaWxlLiBJIHdvdWxkIGZh
ciByYXRoZXIgZ28gZm9yIHRoZSBsb3cgCj4+IGhhbmdpbmcgZnJ1aXQgYW5kIGxldCB0aG9zZSB3
aG8gd2FudCB0byBzb2x2ZSB0aGUgYmlnZ2VyIHByb2JsZW0gZG8gCj4+IHNvIHdpdGhvdXQgc2xv
d2luZyB0aGUgcmVsYXRpdmVseSBlYXN5IHBhcnQgZG93bi4KPj4KPj4gSW4gbXkgbWluZCwgaXQg
aXMgaW4gbGFyZ2UgcGFydCBhIHF1ZXN0aW9uIG9mIHJlcXVpcmVtZW50cy4gV291bGQgaXQgCj4+
IGJlIG5pY2UgdG8gZW5hYmxlIGFueSBJUHY0IG5vZGUgdG8gYWNjZXNzIGFueSBJUHY2IG5vZGU/
IG9mIGNvdXJzZS4gCj4+IEJ1dCBpcyB0aGF0IHJlYWxseSBuZWVkZWQ/IEkgZG9uJ3QgdGhpbmsg
c28uCj4+Cj4+IEFzIEkgc2FpZCBpbiBlbWFpbCBkdXJpbmcgdGhlIGludGVyaW0sIHlvdSByZWFs
bHkgaGF2ZSB0d28gCj4+IGFwcGxpY2F0aW9uIGNhc2VzIC0gY2xpZW50L3NlcnZlciAodGhlIHdl
YiBhbmQgUE9QL0lNQVAgYmVpbmcgCj4+IGV4YW1wbGVzLCBhbmQgU01UUCB3aGVuIGl0IGlzIGNv
bmZpZ3VyZWQgdG8gdXBsb2FkIG1haWwgZnJvbSBhbiAKPj4gYXBwbGljYXRpb24gbGlrZSBPdXRM
b29rIHRvIGEgY29ycG9yYXRlL0lTUCBtYWlsIHNlcnZlciksIGFuZCAKPj4gcGVlci10by1wZWVy
LiBTTVRQIGlzIHBlZXItdG8tcGVlciBiZXR3ZWVuIE1UQXMgKFRDUCBzZXNzaW9ucyBhcmUgCj4+
IGNyZWF0ZWQgaW4gYm90aCBkaXJlY3Rpb25zKSwgYW5kIGFwcGxpY2F0aW9ucyBsaWtlIEJpdFRv
cnJlbnQgYXJlIAo+PiBvYnZpb3VzbHkgcGVlci10by1wZWVyLgo+Pgo+PiBPYnZpb3VzbHkgeW91
IG5lZWQgYW55IGNsaWVudCB0byBiZSBhYmxlIHRvIGFjY2VzcyBhbnkgc2VydmVyLiBHaXZlbiAK
Pj4gdGhhdCB0aGVyZSBhcmUgb2Z0ZW4gc2V2ZXJhbCBvcmRlcnMgb2YgbWFnbml0dWRlIG1vcmUg
Y2xpZW50cyB0aGFuIAo+PiBzZXJ2ZXJzIGluIHN1Y2ggYXBwbGljYXRpb25zLCBJIGhhdmUgYSBy
ZWxhdGl2ZWx5IHNtYWxsIHRyYW5zbGF0aW9uIAo+PiByZXF1aXJlbWVudCAtIEkgZG9uJ3QgbmVl
ZCBhbnkgY29tcHV0ZXIgdG8gYW55IGNvbXB1dGVyLCBJIG9ubHkgbmVlZCAKPj4gZm9yIElQdjYg
Y2xpZW50cyB0byBiZSBhYmxlIHRvIGFjY2VzcyBJUHY0IHNlcnZlcnMgKG1hcHBlZCBhZGRyZXNz
IGluIAo+PiB0aGUgY2xpZW50IG9yIHN0YXRlZnVsIE5BVHMgY29tcGFyYWJsZSB0byBwcmVzZW50
IE5BVDQ0IHdpbGwgd29yayksIAo+PiBhbmQgSVB2NCBjbGllbnRzIHRvIGFjY2VzcyBJUHY2IHNl
cnZlcnMgKHNpbXBseSBkb25lIHdpdGggYSBtYXBwZWQgCj4+IGFkZHJlc3MpLgo+Pgo+PiBGb3Ig
cGVlciB0byBwZWVyIGFwcGxpY2F0aW9ucyBsaWtlIFNNVFAsIHVzaW5nIG1hcHBlZCBhZGRyZXNz
ZXMgbWFrZXMgCj4+IGl0IHJlbGF0aXZlbHkgc2ltcGxlIHRvIHN1cHBvcnQgdGhlbS4gU2luY2Ug
b25lIGV4cGVjdHMgdGhlbSB0byBiZSAKPj4gdGhlIGJ1bGsgb2YgYXBwbGljYXRpb24gdHJhZmZp
Yywgc3RhdGVsZXNzIHRyYW5zbGF0aW9uIGhhcyBzb21lIHJlYWwgCj4+IGJlbmVmaXRzIHRoZXJl
IGFzIHdlbGwuIFdoeSBkb2VzIG9uZSBleHBlY3QgdGhhdD8gV2VsbCwgaWYgb25lIE1UQSAKPj4g
c2VydmVzIDEwLDAwMCBNVUFzIHRoYXQgZWFjaCB1cGxvYWQgbGVzcyB0aGFuIDEwMCBtZXNzYWdl
cyBhIGRheSwgCj4+IHRoYXQgTVRBIGlzIGF0IGFueSBnaXZlbiB0aW1lIHRhbGtpbmcgd2l0aCBv
bmx5IGEgZmV3IG9mIHRoZW0sIAo+PiBwZXJoYXBzIDEwLTEwMC4gQnV0IGl0IHdpbGwgYmUgY29u
c3RhbnRseSBjaGF0dGluZyB3aXRoIHRoZSBuZXh0IE1UQSAKPj4gdXBzdHJlYW0gYXMgaXQgc2Vu
ZHMgaXRzIGNsaWVudHMnIDEwLDAwMCoxMDAgbWVzc2FnZXMgYWxvbmcuCj4+Cj4+IEZvciBwZWVy
IHRvIHBlZXIgYXBwbGljYXRpb25zIGxpa2UgQml0VG9ycmVudCwgd2hpbGUgd2hhdCB3b3VsZCAK
Pj4gb3RoZXJ3aXNlIGJlIGNhbGxlZCAiY2xpZW50cyIgaW4gZmFjdCBvcGVuIFRDUC1saWtlIGNv
bm5lY3Rpb25zIAo+PiB3aWxseS1uaWxseSwgdGhleSBoYXZlIHJ1bGVzIGFib3V0IGhvdyB0aGV5
IG9wZW4gdGhlbS4gVGhleSB0ZW5kIHRvIAo+PiBvcGVuIGEgZmV3IGNvbm5lY3Rpb25zIHRoYXQg
dGhleSBsZWF2ZSBvcGVuIGZvciBhIGxvbmcgdGltZSBhbmQgdXNlIAo+PiBiaWRpcmVjdGlvbmFs
bHksIHNvIG9wZW5pbmcgYSBjb25uZWN0aW9uIGluIHRoZSBJUHY2LT5JUHY0IGRpcmVjdGlvbiAK
Pj4gd29ya3MgYWxzbyB0byBtb3ZlIGNvbnRlbnQgZnJvbSB0aGUgSVB2NCBkb21haW4gdG8gdGhl
IElQdjYgZG9tYWluLiAKPj4gV2l0aGluIGVhY2ggZG9tYWluLCBjb25uZWN0aW9ucyBnZW5lcmFs
bHkgd29yaywgYW5kIGNvbnRlbnQgY2FuIGJlIAo+PiBtb3ZlZCB3aGVyZSBpdCBuZWVkcyB0byBi
ZS4gVXNpbmcgTkFUNDQtbGlrZSB0ZWNobm9sb2d5LCBJUHY2IHN5c3RlbXMgCj4+IGNhbiBhY2Nl
c3MgSVB2NCBzeXN0ZW1zIHJlYWRpbHkuIElQdjQgc3lzdGVtcyB3b24ndCBiZSBhYmxlIHRvIGFj
Y2VzcyAKPj4gSVB2Ni1uYXRpdmUgcGVlcnMsIGJ1dCB0aGV5IHdvbid0IG5lZWQgdG8gYXMgdGhl
IGNvbnRlbnQgd2lsbCBhbHJlYWR5IAo+PiBiZSBpbiB0aGVpciBkb21haW4uCj4+Cj4+IFNvIEkg
ZG9uJ3QgdGhpbmsgd2UgbmVlZCBhbnk8LT5hbnkgYWNjZXNzIGFueXdoZXJlIG5lYXIgYXMgbXVj
aCBhcyB3ZSAKPj4gbmVlZCB0aGUgbXVjaCBzaW1wbGVyIGFiaWxpdHkgdG8gaGF2ZSBJUHY0IHN5
c3RlbXMgYWNjZXNzIElQdjYgCj4+ICpzZXJ2ZXJzKiwgc3lzdGVtcyB0aGF0IGhhdmUgc3RhYmxl
IGFkZHJlc3NlcyB0aGF0IGFyZSBnZW5lcmFsbHkgCj4+IGFzc2lnbmVkIHRvIHRoZW0gYW55d2F5
Lgo+Cj4gVGhhbmtzIQo+Cj4gU29tZSBhZGRpdGlvbmFsIG5vdGVzIGJhc2VkIG9uIENFUk5FVCB0
d28geWVhcnMgZXhwZXJpZW5jZSBvZiBydW5uaW5nIGEKPiBwdXJlIElQdjYgYmFja2JvbmUuCj4K
PiBXZSBiZWxpZXZlIHRoZSBzZWxlY3Rpb24gb2YgdGhlIHNjZW5hcmlvcyBjb3VsZCBiZSBiYXNl
ZCBvbiB0aGUKPiBpbmNlbnRpdmUgb2YgdGhlIG93bmVyIG9mIHRoZSBJUHY2IGhvc3RzLgo+ICgx
KSBJZiB0aGUgSVB2NiBob3N0IG5lZWRzIHRvIGJlIGFuIElQdjQtYWNjZXNzaWJsZSBzZXJ2ZXIs
IHRoZXkgd2lsbAo+IHVzZSB0aGUgSVZJIGFkZHJlc3MuIE90aGVyd2lzZSwgaXQgd2lsbCB1c2Ug
bm9uLUlWSSBhZGRyZXNzLiBUaGlzIGlzIHRvCj4gc2F5IHRoYXQgdGhlcmUgaXMgbm8gbmVlZCB0
byBwcm92aWRlIGEgZ2VuZXJhbCBzY2hlbWUgZm9yIGFueSBJUHY0IGhvc3QKPiBpbml0aWF0ZXMg
Y29tbXVuaWNhdGlvbiB3aXRoIEFOWSBJUHY2IGhvc3QsIHNpbmNlIHRoZSBvd25lciBvZiB0aGUg
SVB2Ngo+IGhvc3QgY2FuIHNlbGVjdCB0aGUgc3VpdGFibGUgY2F0ZWdvcnkgb2YgdGhlIElQdjYg
YWRkcmVzc2VzLgpoZXJlIGlzIHdoZXJlIGkgZGlzYWdyZWUKSSB0aGluayB3ZSBzaG91bGQgc3Vw
cG9ydCBjb21tdW5pY2F0aW9ucyB0byBzb21lIHY2IGFkZHJlc3NlcyBjcmVhdGluZyAKc29tZSBt
YW51YWwgb3IgYXV0b21hdGljIDE6MSBtYXBwaW5nIGJlY2F1c2UgaXQgaXMgdGhlIGJlc3QgdGhh
dCB3ZSBjYW4gCmRvIHdpdGhvdXQgaGF2aW5nIHRvIHVzZSB2ZXJ5IG5hc3R5IGhhY2tzIGxpa2Ug
dGhlIG9uZXMgZGVmaW5lZCBpbiB0aGUgCm9yaWdpbmFsIG5hdHB0LCBub3QgYmVjYXVzZSB0aGVy
ZSBpcyBubyBuZWVkIGZvciBzdWNoIHNjaGVtZQpNYW55IG1hbnkgaG9zdHMgdG9kYXkgcnVuIHAy
cCBhcHBsaWNhdGlvbnMuIHRoZXkgY2VydGFpbmx5IGNhbiB1c2UgYSAKcmVhY2hhYmxlIGFkZHJl
c3Mgd2lodG91dCBuZWVkZWRpbmcgdG8gcmVseSBvbiBuYXQgdHJhdmVyc2FsIHRlY2huaXF1ZXMu
IAphbmQgdGhpcyBpcyBqdXN0IG9uZSBleGFtcGxlLiB5b3UgY2FuIHRoaW5rIGFib3V0IG90aGVy
IGNhc2VzLCBsaWtlIHlvdXIgCmhvbWUgY2FtcmVhIHRoYXQgeW91IHdhbnQgdG8gYWNjZXNzIGZy
b20gdGhlIGludGVybmV0IGFuZCBzbyBvbi4KClNvLCBpIHRoaW5rIGl0IG1ha2VzIGEgbG90IG9m
IHNlbnNlIGlmIGFueSB2NiBhZGRyZXNzIGNvdWxkIGJlIHJlYWNoZWQgCmZyb20gdGhlIHY0IGlu
dGVybmV0IGFuZCBpIHRoaW5rIHRoaXMgd291bGQgcmVzdWx0IGluIGZhc3RlciBhZG9wdGlvbiBv
ZiAKdjYsIGJ1dCBpIGRvbid0IHRoaW5rIHdlIGNhbiBhY2hpZXZlIHRoaXMgaW4gYSBzdWZmaWNp
ZW50bHkgY2xlYW4gd2F5IAoobm90IHlldCBhdCBsZWFzdCwgbWF5YmUgaW4gc29tZSBuZWFyIGZ1
dHVyZSwgdGhlIG5hdHB0IHdvdWxkIGJlIApzdWZmaWNpZW50bHkgY2xlYW4gOi0pCgoKCj4gKDIp
IEFzIHRoZSBJU1AsIHdlIHByaWNlIElWSSBhZGRyZXNzZXMgKDE6MSBtYXBwaW5nIG9mIElQdjQg
YWRkcmVzcywKPiBzY2FyY2UgcmVzb3VyY2UpIGFuZCBub24tSVZJIGFkZHJlc3NlcyAobm9uLXNj
YXJjZSByZXNvdXJjZSkKPiBkaWZmZXJlbnRseS4gU28gaXQgaXMgYWxzbyBlY29ub21pY2FsbHkg
cmVhc29uYWJsZS4KUmlnaHQsIHRoaXMgaXMgZXhhY3RseSB3aGF0IGkgd291bGQgbGlrZSB0byBw
cmV2ZW50LCB0aGF0IElTUHMgaGF2ZSAKY29udHJvbCBvbiB3aGV0aGVyIHRoZWlyIGNsaWVudHMg
YXJlIGFibGUgb3Igbm90IHRvIHB1Ymxpc2ggY29udGVudCBmcm9tIAp0aGVpciBzaXRlcwoKUmVn
YXJkcywgbWFyY2VsbwoKCgo+Cj4gSnVzdCBvdXIgdHdvIGNlbnRzLgo+Cj4geGluZwo+Pgo+PiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+PiB2NHY2aW50
ZXJpbSBtYWlsaW5nIGxpc3QKPj4gdjR2NmludGVyaW1AaWV0Zi5vcmcKPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2aW50ZXJpbQo+Pgo+Pgo+Cj4KPgo+Cj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPiB2NHY2aW50ZXJp
bSBtYWlsaW5nIGxpc3QKPiB2NHY2aW50ZXJpbUBpZXRmLm9yZwo+IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0KCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fCnY0djZpbnRlcmltIG1haWxpbmcgbGlzdAp2NHY2aW50
ZXJpbUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y0djZp
bnRlcmltCg==


From v4v6interim-bounces@ietf.org  Mon Oct 20 00:04:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 332C13A6883;
	Mon, 20 Oct 2008 00:04:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A7C63A685A
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uRvKxLDNkCju for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 00:04:16 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id 772963A68F4
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:04:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,449,1220227200"; d="scan'208";a="31221155"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 20 Oct 2008 07:05:23 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9K75M83017172; 
	Mon, 20 Oct 2008 15:05:22 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com
	[64.104.123.69])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9K75Mrx026898;
	Mon, 20 Oct 2008 07:05:22 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 15:05:22 +0800
Received: from [64.104.120.94] ([64.104.120.94]) by xfe-hkg-412.apac.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 15:05:21 +0800
Message-Id: <F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
From: Fred Baker <fred@cisco.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
In-Reply-To: <48FC2AFC.60405@it.uc3m.es>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 15:05:21 +0800
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-
	4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
	<48FBC96D.5020207@cernet.edu.cn> <48FC2AFC.60405@it.uc3m.es>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Oct 2008 07:05:21.0589 (UTC)
	FILETIME=[378CEE50:01C93282]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1752; t=1224486322;
	x=1225350322; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=AkO2fsbYjAJi36mCnkdvObBT+gRcvojJ+uX2a8ugCOE=;
	b=MwwsCd9HmVLX76ibp5cBWuAKyzsE/2eiAzMZspcZbE56RBnJxNd2rtkE+y
	WR0m9hfYuj2BQANPF+VaACbMtha3fIWetiEoUMHprnalO7ZSp3O8fO3+cn2y
	dr6+av6nhCx6I+khC/Q4ma0BD0nUGeMcBUsdQ19Xok7kULy6hptVc=;
Authentication-Results: hkg-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 20, 2008, at 2:53 PM, marcelo bagnulo braun wrote:
>> (2) As the ISP, we price IVI addresses (1:1 mapping of IPv4  
>> address, scarce resource) and non-IVI addresses (non-scarce  
>> resource) differently. So it is also economically reasonable.
> Right, this is exactly what i would like to prevent, that ISPs have  
> control on whether their clients are able or not to publish content  
> from their sites

Excuse me?

Trust me, given that you attach to someone's network, they are in  
control of what services they offer you, and they are in a position to  
filter-or-whatever if they want. Given that you have a choice of  
offerings, they are not in control of the choices you make, but they  
can prevent you from making certain choices in their network by not  
offering you the choice.

What Xing Li proposes - and what I propose - is not as onerous as you  
appear to believe. He gives you the option of paying for a directly  
(1:1) translatable address and he doesn't tell you what you may do  
with it. Given that, you have the option of paying for the service he  
is offering or paying for a different one, perhaps one from a  
different ISP - the same choice you have with any ISP. Given that you  
choose to pay for a 1:1 translatable address (just as you would with  
the NAT64 model), you can put any content behind that address that you  
want to.

And in any event, I would really hope that we could avoid political  
agendas here. Last I checked, we're technologists and we are  
describing technology. Pretending that we are preventing ISPs from  
doing one thing or forcing them to do another is a pipe dream. Once it  
is deployed, they're in control.

Let's work on the technology.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 00:17:22 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26C933A6A18;
	Mon, 20 Oct 2008 00:17:22 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB0953A6A18
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.073
X-Spam-Level: *
X-Spam-Status: No, score=1.073 tagged_above=-999 required=5 tests=[AWL=-0.514, 
	BAYES_05=-1.11, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Hl7xvZ0YiJg2 for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 00:17:20 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66])
	by core3.amsl.com (Postfix) with SMTP id 5BFA53A6988
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:17:18 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0)
	with SMTP id jm548fc47b5; Mon, 20 Oct 2008 15:18:28 +0800
Message-ID: <48FC30A5.202@cernet.edu.cn>
Date: Mon, 20 Oct 2008 15:17:57 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-		4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
	<48FBC96D.5020207@cernet.edu.cn> <48FC2AFC.60405@it.uc3m.es>
In-Reply-To: <48FC2AFC.60405@it.uc3m.es>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: jtECprUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

bWFyY2VsbyBiYWdudWxvIGJyYXVuIOWGmemBkzoKPj4KPj4gU29tZSBhZGRpdGlvbmFsIG5vdGVz
IGJhc2VkIG9uIENFUk5FVCB0d28geWVhcnMgZXhwZXJpZW5jZSBvZiBydW5uaW5nIGEKPj4gcHVy
ZSBJUHY2IGJhY2tib25lLgo+Pgo+PiBXZSBiZWxpZXZlIHRoZSBzZWxlY3Rpb24gb2YgdGhlIHNj
ZW5hcmlvcyBjb3VsZCBiZSBiYXNlZCBvbiB0aGUKPj4gaW5jZW50aXZlIG9mIHRoZSBvd25lciBv
ZiB0aGUgSVB2NiBob3N0cy4KPj4gKDEpIElmIHRoZSBJUHY2IGhvc3QgbmVlZHMgdG8gYmUgYW4g
SVB2NC1hY2Nlc3NpYmxlIHNlcnZlciwgdGhleSB3aWxsCj4+IHVzZSB0aGUgSVZJIGFkZHJlc3Mu
IE90aGVyd2lzZSwgaXQgd2lsbCB1c2Ugbm9uLUlWSSBhZGRyZXNzLiBUaGlzIGlzIHRvCj4+IHNh
eSB0aGF0IHRoZXJlIGlzIG5vIG5lZWQgdG8gcHJvdmlkZSBhIGdlbmVyYWwgc2NoZW1lIGZvciBh
bnkgSVB2NCBob3N0Cj4+IGluaXRpYXRlcyBjb21tdW5pY2F0aW9uIHdpdGggQU5ZIElQdjYgaG9z
dCwgc2luY2UgdGhlIG93bmVyIG9mIHRoZSBJUHY2Cj4+IGhvc3QgY2FuIHNlbGVjdCB0aGUgc3Vp
dGFibGUgY2F0ZWdvcnkgb2YgdGhlIElQdjYgYWRkcmVzc2VzLgo+IGhlcmUgaXMgd2hlcmUgaSBk
aXNhZ3JlZQo+IEkgdGhpbmsgd2Ugc2hvdWxkIHN1cHBvcnQgY29tbXVuaWNhdGlvbnMgdG8gc29t
ZSB2NiBhZGRyZXNzZXMgY3JlYXRpbmcgCj4gc29tZSBtYW51YWwgb3IgYXV0b21hdGljIDE6MSBt
YXBwaW5nIGJlY2F1c2UgaXQgaXMgdGhlIGJlc3QgdGhhdCB3ZSAKPiBjYW4gZG8gd2l0aG91dCBo
YXZpbmcgdG8gdXNlIHZlcnkgbmFzdHkgaGFja3MgbGlrZSB0aGUgb25lcyBkZWZpbmVkIGluIAo+
IHRoZSBvcmlnaW5hbCBuYXRwdCwgbm90IGJlY2F1c2UgdGhlcmUgaXMgbm8gbmVlZCBmb3Igc3Vj
aCBzY2hlbWUKV2h5IG5vdD8gVGhpcyBpcyBXaGF0IElWSSBpcyBkb2luZyBpbiBDRVJORVQyLiBU
aGUgMToxIHN0YXRlbGVzcyBpcyBmb3IgCnRoZSBJUHY0IGluaXRpYXRlZCBjb21tdW5pY2F0aW9u
Lgo+IE1hbnkgbWFueSBob3N0cyB0b2RheSBydW4gcDJwIGFwcGxpY2F0aW9ucy4gdGhleSBjZXJ0
YWlubHkgY2FuIHVzZSBhIAo+IHJlYWNoYWJsZSBhZGRyZXNzIHdpaHRvdXQgbmVlZGVkaW5nIHRv
IHJlbHkgb24gbmF0IHRyYXZlcnNhbCAKPiB0ZWNobmlxdWVzLiBhbmQgdGhpcyBpcyBqdXN0IG9u
ZSBleGFtcGxlLiB5b3UgY2FuIHRoaW5rIGFib3V0IG90aGVyIAo+IGNhc2VzLCBsaWtlIHlvdXIg
aG9tZSBjYW1yZWEgdGhhdCB5b3Ugd2FudCB0byBhY2Nlc3MgZnJvbSB0aGUgaW50ZXJuZXQgCj4g
YW5kIHNvIG9uLgo+Cj4gU28sIGkgdGhpbmsgaXQgbWFrZXMgYSBsb3Qgb2Ygc2Vuc2UgaWYgYW55
IHY2IGFkZHJlc3MgY291bGQgYmUgcmVhY2hlZCAKPiBmcm9tIHRoZSB2NCBpbnRlcm5ldCBhbmQg
aSB0aGluayB0aGlzIHdvdWxkIHJlc3VsdCBpbiBmYXN0ZXIgYWRvcHRpb24gCj4gb2YgdjYsIGJ1
dCBpIGRvbid0IHRoaW5rIHdlIGNhbiBhY2hpZXZlIHRoaXMgaW4gYSBzdWZmaWNpZW50bHkgY2xl
YW4gCj4gd2F5IChub3QgeWV0IGF0IGxlYXN0LCBtYXliZSBpbiBzb21lIG5lYXIgZnV0dXJlLCB0
aGUgbmF0cHQgd291bGQgYmUgCj4gc3VmZmljaWVudGx5IGNsZWFuIDotKQpJVkkgMTpOIG1hcHBp
bmcgY2FuIHNvbHZlIHRoaXMgcHJvYmxlbS4gVGhlIDE6TiBTdGF0ZWZ1bCBpcyBmb3IgdGhlIElQ
djYgCmluaXRpYXRlZCBjb21tdW5pY2F0aW9uLgoKeGluZwo+Cj4KPgo+PiAoMikgQXMgdGhlIElT
UCwgd2UgcHJpY2UgSVZJIGFkZHJlc3NlcyAoMToxIG1hcHBpbmcgb2YgSVB2NCBhZGRyZXNzLAo+
PiBzY2FyY2UgcmVzb3VyY2UpIGFuZCBub24tSVZJIGFkZHJlc3NlcyAobm9uLXNjYXJjZSByZXNv
dXJjZSkKPj4gZGlmZmVyZW50bHkuIFNvIGl0IGlzIGFsc28gZWNvbm9taWNhbGx5IHJlYXNvbmFi
bGUuCj4gUmlnaHQsIHRoaXMgaXMgZXhhY3RseSB3aGF0IGkgd291bGQgbGlrZSB0byBwcmV2ZW50
LCB0aGF0IElTUHMgaGF2ZSAKPiBjb250cm9sIG9uIHdoZXRoZXIgdGhlaXIgY2xpZW50cyBhcmUg
YWJsZSBvciBub3QgdG8gcHVibGlzaCBjb250ZW50IAo+IGZyb20gdGhlaXIgc2l0ZXMKPgo+IFJl
Z2FyZHMsIG1hcmNlbG8KPgo+Cj4KPj4KPj4gSnVzdCBvdXIgdHdvIGNlbnRzLgo+Pgo+PiB4aW5n
Cj4+Pgo+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K
Pj4+IHY0djZpbnRlcmltIG1haWxpbmcgbGlzdAo+Pj4gdjR2NmludGVyaW1AaWV0Zi5vcmcKPj4+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0KPj4+Cj4+
Pgo+Pgo+Pgo+Pgo+Pgo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwo+PiB2NHY2aW50ZXJpbSBtYWlsaW5nIGxpc3QKPj4gdjR2NmludGVyaW1AaWV0Zi5v
cmcKPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2aW50ZXJpbQo+
Cj4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnY0djZp
bnRlcmltIG1haWxpbmcgbGlzdAp2NHY2aW50ZXJpbUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y0djZpbnRlcmltCg==


From v4v6interim-bounces@ietf.org  Mon Oct 20 00:17:58 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 490993A68F4;
	Mon, 20 Oct 2008 00:17:58 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DF8B3A68F4
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.638
X-Spam-Level: *
X-Spam-Status: No, score=1.638 tagged_above=-999 required=5 tests=[AWL=-0.873, 
	BAYES_40=-0.185, FH_HAS_XAIMC=2.696]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uuY4GFUOi6yd for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 00:17:56 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.3.66])
	by core3.amsl.com (Postfix) with SMTP id E73043A68F3
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:17:55 -0700 (PDT)
Received: from [127.0.0.1]([59.66.24.169]) by cernet.edu.cn(AIMC 3.2.0.0)
	with SMTP id jm3348fc47da; Mon, 20 Oct 2008 15:19:05 +0800
Message-ID: <48FC30EC.50609@cernet.edu.cn>
Date: Mon, 20 Oct 2008 15:19:08 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-
	4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>
	<48FBC96D.5020207@cernet.edu.cn> <48FC2AFC.60405@it.uc3m.es>
	<F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
In-Reply-To: <F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: jEfCprUB
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

RnJlZCBCYWtlciDlhpnpgZM6Cj4KPiBPbiBPY3QgMjAsIDIwMDgsIGF0IDI6NTMgUE0sIG1hcmNl
bG8gYmFnbnVsbyBicmF1biB3cm90ZToKPj4+ICgyKSBBcyB0aGUgSVNQLCB3ZSBwcmljZSBJVkkg
YWRkcmVzc2VzICgxOjEgbWFwcGluZyBvZiBJUHY0IGFkZHJlc3MsIAo+Pj4gc2NhcmNlIHJlc291
cmNlKSBhbmQgbm9uLUlWSSBhZGRyZXNzZXMgKG5vbi1zY2FyY2UgcmVzb3VyY2UpIAo+Pj4gZGlm
ZmVyZW50bHkuIFNvIGl0IGlzIGFsc28gZWNvbm9taWNhbGx5IHJlYXNvbmFibGUuCj4+IFJpZ2h0
LCB0aGlzIGlzIGV4YWN0bHkgd2hhdCBpIHdvdWxkIGxpa2UgdG8gcHJldmVudCwgdGhhdCBJU1Bz
IGhhdmUgCj4+IGNvbnRyb2wgb24gd2hldGhlciB0aGVpciBjbGllbnRzIGFyZSBhYmxlIG9yIG5v
dCB0byBwdWJsaXNoIGNvbnRlbnQgCj4+IGZyb20gdGhlaXIgc2l0ZXMKPgo+IEV4Y3VzZSBtZT8K
Pgo+IFRydXN0IG1lLCBnaXZlbiB0aGF0IHlvdSBhdHRhY2ggdG8gc29tZW9uZSdzIG5ldHdvcmss
IHRoZXkgYXJlIGluIAo+IGNvbnRyb2wgb2Ygd2hhdCBzZXJ2aWNlcyB0aGV5IG9mZmVyIHlvdSwg
YW5kIHRoZXkgYXJlIGluIGEgcG9zaXRpb24gdG8gCj4gZmlsdGVyLW9yLXdoYXRldmVyIGlmIHRo
ZXkgd2FudC4gR2l2ZW4gdGhhdCB5b3UgaGF2ZSBhIGNob2ljZSBvZiAKPiBvZmZlcmluZ3MsIHRo
ZXkgYXJlIG5vdCBpbiBjb250cm9sIG9mIHRoZSBjaG9pY2VzIHlvdSBtYWtlLCBidXQgdGhleSAK
PiBjYW4gcHJldmVudCB5b3UgZnJvbSBtYWtpbmcgY2VydGFpbiBjaG9pY2VzIGluIHRoZWlyIG5l
dHdvcmsgYnkgbm90IAo+IG9mZmVyaW5nIHlvdSB0aGUgY2hvaWNlLgo+Cj4gV2hhdCBYaW5nIExp
IHByb3Bvc2VzIC0gYW5kIHdoYXQgSSBwcm9wb3NlIC0gaXMgbm90IGFzIG9uZXJvdXMgYXMgeW91
IAo+IGFwcGVhciB0byBiZWxpZXZlLiBIZSBnaXZlcyB5b3UgdGhlIG9wdGlvbiBvZiBwYXlpbmcg
Zm9yIGEgZGlyZWN0bHkgCj4gKDE6MSkgdHJhbnNsYXRhYmxlIGFkZHJlc3MgYW5kIGhlIGRvZXNu
J3QgdGVsbCB5b3Ugd2hhdCB5b3UgbWF5IGRvIAo+IHdpdGggaXQuIEdpdmVuIHRoYXQsIHlvdSBo
YXZlIHRoZSBvcHRpb24gb2YgcGF5aW5nIGZvciB0aGUgc2VydmljZSBoZSAKPiBpcyBvZmZlcmlu
ZyBvciBwYXlpbmcgZm9yIGEgZGlmZmVyZW50IG9uZSwgcGVyaGFwcyBvbmUgZnJvbSBhIAo+IGRp
ZmZlcmVudCBJU1AgLSB0aGUgc2FtZSBjaG9pY2UgeW91IGhhdmUgd2l0aCBhbnkgSVNQLiBHaXZl
biB0aGF0IHlvdSAKPiBjaG9vc2UgdG8gcGF5IGZvciBhIDE6MSB0cmFuc2xhdGFibGUgYWRkcmVz
cyAoanVzdCBhcyB5b3Ugd291bGQgd2l0aCAKPiB0aGUgTkFUNjQgbW9kZWwpLCB5b3UgY2FuIHB1
dCBhbnkgY29udGVudCBiZWhpbmQgdGhhdCBhZGRyZXNzIHRoYXQgeW91IAo+IHdhbnQgdG8uCj4K
PiBBbmQgaW4gYW55IGV2ZW50LCBJIHdvdWxkIHJlYWxseSBob3BlIHRoYXQgd2UgY291bGQgYXZv
aWQgcG9saXRpY2FsIAo+IGFnZW5kYXMgaGVyZS4gTGFzdCBJIGNoZWNrZWQsIHdlJ3JlIHRlY2hu
b2xvZ2lzdHMgYW5kIHdlIGFyZSAKPiBkZXNjcmliaW5nIHRlY2hub2xvZ3kuIFByZXRlbmRpbmcg
dGhhdCB3ZSBhcmUgcHJldmVudGluZyBJU1BzIGZyb20gCj4gZG9pbmcgb25lIHRoaW5nIG9yIGZv
cmNpbmcgdGhlbSB0byBkbyBhbm90aGVyIGlzIGEgcGlwZSBkcmVhbS4gT25jZSBpdCAKPiBpcyBk
ZXBsb3llZCwgdGhleSdyZSBpbiBjb250cm9sLgo+Cj4gTGV0J3Mgd29yayBvbiB0aGUgdGVjaG5v
bG9neS4KQWdyZWUuIFdlIGFyZSB3b3JraW5nIG9uIHRlY2hub2xvZ3kgYW5kIHByb3ZpZGUgZmVh
c2libGUgc29sdXRpb25zLiBUaGUgCm1hcmtldCB3aWxsIG1ha2UgdGhlIGRlY2lzaW9uLiB4aW5n
Cj4KPgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdjR2
NmludGVyaW0gbWFpbGluZyBsaXN0CnY0djZpbnRlcmltQGlldGYub3JnCmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Mon Oct 20 00:22:06 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8FE23A6988;
	Mon, 20 Oct 2008 00:22:06 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F28B43A6988
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.847
X-Spam-Level: 
X-Spam-Status: No, score=-3.847 tagged_above=-999 required=5
	tests=[AWL=-0.085, BAYES_00=-2.599, RCVD_BAD_ID=2.837,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OTJZB19oFDxB for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 00:22:04 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131])
	by core3.amsl.com (Postfix) with ESMTP id 0180B3A6833
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:22:04 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown [85.53.133.67])by
	smtp01.uc3m.es (Postfix) with ESMTP id 59B8EAC275C;Mon, 20 Oct 2008 
	09:23:13 +0200 (CEST)
Message-ID: <48FC31E0.5060902@it.uc3m.es>
Date: Mon, 20 Oct 2008 09:23:12 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-
	4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@ci
	s	co.com> <48FBC96D.5020207@cernet.edu.cn> <48FC2AFC.60405@it.uc3m.es> 
	<F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
In-Reply-To: <F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-17.5655 TC:1F TRN:47 TV:5.5.1026(16228.005)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred Baker escribi=F3:
>
> On Oct 20, 2008, at 2:53 PM, marcelo bagnulo braun wrote:
>>> (2) As the ISP, we price IVI addresses (1:1 mapping of IPv4 address, =

>>> scarce resource) and non-IVI addresses (non-scarce resource) =

>>> differently. So it is also economically reasonable.
>> Right, this is exactly what i would like to prevent, that ISPs have =

>> control on whether their clients are able or not to publish content =

>> from their sites
>
> Excuse me?
>
> Trust me, given that you attach to someone's network, they are in =

> control of what services they offer you, and they are in a position to =

> filter-or-whatever if they want. =

No, that does have legal implications (at least in some countries)


> Given that you have a choice of offerings, they are not in control of =

> the choices you make, but they can prevent you from making certain =

> choices in their network by not offering you the choice.
>

that depends on how you define the underlying technology. Some =

technologies allows some players to do some operations and some =

technologies don't, and by enabling some functions you allow some =

parties to have some power.
See Clark's design for tussle paper for more discussion about this for =

instance.
> What Xing Li proposes - and what I propose - is not as onerous as you =

> appear to believe. He gives you the option of paying for a directly =

> (1:1) translatable address and he doesn't tell you what you may do =

> with it.Given that, you have the option of paying for the service he =

> is offering or paying for a different one, perhaps one from a =

> different ISP - the same choice you have with any ISP. Given that you =

> choose to pay for a 1:1 translatable address (just as you would with =

> the NAT64 model), you can put any content behind that address that you =

> want to.
>
> And in any event, I would really hope that we could avoid political =

> agendas here.
I don't think it is a political agenda to understand what the technology =

allows to do each stakeholder

Unfortunately, in this case that we are disucssing, i don't think we can =

define a reasonable technology for enabling any v4 node to contact any =

v6 node, so as i said, 1:1 mappings are the best we can do, even if we =

don't like what that implies to the end sites

Regards, marcelo


> Last I checked, we're technologists and we are describing technology. =

> Pretending that we are preventing ISPs from doing one thing or forcing =

> them to do another is a pipe dream. Once it is deployed, they're in =

> control.
>
> Let's work on the technology.
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 00:38:21 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7081C3A68F3;
	Mon, 20 Oct 2008 00:38:21 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 137D73A68DB
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 00:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level: 
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.068, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BOP8Z0GtIxqV for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 00:38:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id A88B03A6900
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 00:38:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,450,1220227200"; d="scan'208";a="23085303"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Oct 2008 07:39:29 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9K7dTg5027587; 
	Mon, 20 Oct 2008 09:39:29 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9K7dTh6013857;
	Mon, 20 Oct 2008 07:39:29 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 09:39:29 +0200
Received: from ams-townsley-8713.cisco.com ([10.55.233.228]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 09:39:28 +0200
Message-ID: <48FC3561.3040005@cisco.com>
Date: Mon, 20 Oct 2008 09:38:09 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-4DCD-8A38-F351C68058B5@muada.com>	<48F8A9F9.6000505@sri.com>
	<48F8BC64.10608@psg.com>	<48F8D984.90901@sri.com>
	<0F936B42-2FB9-413B-ADDF-BE881730F95E@cisco.com>
In-Reply-To: <0F936B42-2FB9-413B-ADDF-BE881730F95E@cisco.com>
X-OriginalArrivalTime: 20 Oct 2008 07:39:29.0028 (UTC)
	FILETIME=[FBEB5440:01C93286]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2188; t=1224488369;
	x=1225352369; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20=22IPv4->IPv6=20is=20ha
	rd=22 |Sender:=20;
	bh=POV0F23msJFqMNmBFJn+BJGuwsr3oKnE8ADgL4y8QQ8=;
	b=QecRWRZ6o18yB3keDmsrnZG5gwulb3FRf9yIK1fRKOJasuNOfnK3irNDG8
	C83OAdhSSJT53Y1lylJzviQ28ydt8Zk1v+0/POG9txUirOm4/Q2V4dwh9Nob
	jZiSIR9Wph;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Fred Baker wrote:
>
> On Oct 17, 2008, at 11:29 AM, Ed Jankiewicz wrote:
>
>> yup.  I really meant to say "right now" and even for the near future, 
>> don't we still expect most servers/applications to be dual-stack 
>> rather than IPv6-only?  My point was there are more pressing problems 
>> to solve, while it would be nice for all variations to work, some can 
>> be deferred.
>
> One has to define "dual stack".
>
> Everything that runs on my Mac is potentially dual stack, in the sense 
> that the code is there to run both IPv4 and IPv6. Present it with an 
> IPv4 network, it does so. Present it with an IPv6 network, it does so.
>
> It the thing it needs to talk with is IPvX and it only has IPvY 
> routing, however, it can't get there. From my home I can't access 
> ipv6.google.com because no ISP in Santa Barbara County runs IPv6.
>
> The DS-Lite model says that I should set up a tunnel across the IPv4 
> infrastructure, whether from my host or from my router; 6to4 is 
> similar, as are others.
Actually, the DS-Lite model targets setting up a tunnel to cross 
IPv6-only infrastructure - so, not very useful for you situation with an 
ISP not delivering IPv6.

- Mark
>
> The translation model says that the host should use the network 
> available to it and something in the network should change the 
> protocol when and where it must.
>
> My personal preference is for dual stack deployment, and where 
> necessary to change as little as possible, as the changes will outlive 
> the need for them by decades. Asking the host to build tunnels is an 
> example of such a change. Under the ISP's control or at least in 
> collusion with it, I can see building tunnels. But even there, as the 
> ISPs deploy IPv6 that becomes a change that will outlive the need for 
> it. That's why I'm working on translation - enable the network 
> administration to install what it needs to when it needs it, and 
> enable it to remove it when the need goes away.
>
> my two yen
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 03:36:09 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB1F43A68F3;
	Mon, 20 Oct 2008 03:36:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49CA83A68F3;
	Mon, 20 Oct 2008 03:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bNopP2XRqiTC; Mon, 20 Oct 2008 03:36:08 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 3C6DA3A68AB;
	Mon, 20 Oct 2008 03:36:08 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.38])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9KAamYG091619
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 20 Oct 2008 12:36:49 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <48FB9C5E.8070402@gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 12:37:05 +0200
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<024001c930a9$a5d00710$c3f0200a@cisco.com>
	<48FB9C5E.8070402@gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 19 okt 2008, at 22:45, Brian E Carpenter wrote:

>> NAT66 is still a third rail.  I don't want to go there.
>
> Yep. As Margaret well knows, RFC4864 was written to try to avoid
> stepping on that rail, and includes a gap analysis of what's
> needed to avoid it. I'd rather the IETF put effort into those
> gaps.

I talked about IPv6 NAT a bit in the shim6 meeting in Philly:

http://www.ietf.org/proceedings/08mar/slides/shim6-2.pdf

However, I didn't get ANY feedback on that (nor the issue of next  
steps for shim6 which the presentation was about), same thing when I  
mentioned IPv6 NAT a few other times.

Interestingly, I did a small survey about whether people _expect_  
there to be NAT66 in the future and the majority said "yes".

On the one hand we can do nothing and if all goes well there will be  
no IPv6 NAT so we're all happy because not doing anything made the  
right thing happen. (Although I've used a NAT66 implementation myself  
some years back, so there is at least one out there.)

But if we do nothing, we run the risk that someone will do a quick  
search and replace on their NAT44 code and create a port overloading  
NAT66. The port overloading is 90% of the harmful stuff that NAT boxes  
do.

What we could do is come up with a stateless, transport-agnostic 1- 
to-1 NAT66 spec so we at least avoid the port overloading and nothing  
much breaks except referrals.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 03:58:04 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5E513A69CA;
	Mon, 20 Oct 2008 03:58:04 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C048B3A696E;
	Mon, 20 Oct 2008 03:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 69HYGMjov1Oh; Mon, 20 Oct 2008 03:58:03 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id A46223A67BD;
	Mon, 20 Oct 2008 03:58:02 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9KAwfj0013133; Mon, 20 Oct 2008 13:59:04 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 13:58:42 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 13:58:29 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: 46translation@employees.org
Date: Mon, 20 Oct 2008 13:58:28 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
In-Reply-To: <3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810201358.29295.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 20 Oct 2008 10:58:29.0697 (UTC)
	FILETIME=[C91CD310:01C932A2]
X-Nokia-AV: Clean
Cc: v4v6interim@ietf.org, 'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Monday 20 October 2008 13:37:05 ext Iljitsch van Beijnum, you wrote:
> Interestingly, I did a small survey about whether people _expect_
> there to be NAT66 in the future and the majority said "yes".
>
> On the one hand we can do nothing and if all goes well there will be
> no IPv6 NAT so we're all happy because not doing anything made the
> right thing happen. (Although I've used a NAT66 implementation myself
> some years back, so there is at least one out there.)
>
> But if we do nothing, we run the risk that someone will do a quick
> search and replace on their NAT44 code and create a port overloading
> NAT66. The port overloading is 90% of the harmful stuff that NAT boxes
> do.
>
> What we could do is come up with a stateless, transport-agnostic 1-
> to-1 NAT66 spec so we at least avoid the port overloading and nothing
> much breaks except referrals.

I share your analysis that, _assuming_ we have NAT66, it should be =

transport-agnostic. IPv6 has a large enough address space, and we are =

painfully aware of the problems of transport-dependent NAT(44).

However, when I look at the reasons for deploying NAT:
1/ address space shortage
2/ inbound firewalling
3/ topology hiding
4/ prefix delegation "bypass"

(1) is a non-issue for IPv6. (2) is solved with stateful firewalling and do=
es =

not require NAT. 1:1 NAT fails to solve (3) as it does hide the subnetting =

scheme, but fails to hide individual hosts. This leaves only (4). Did I mis=
s =

anything?

I still believe we will see NAT66. Not because it's immediately useful. Rat=
her =

because someone will figure out it's easy to adapt NAT44 code to do NAT66. =

For instance, much of the Linux Netfilter framework has become IP =

version-independent lately, with NAT being the only one big remaining =

IPv4-specific chunk.



I guess only time would tell whether a NAT66 1:1 spec would help prevent su=
ch =

the transport-dependent NAT66 being _deployed_. It cannot hurt to write tha=
t =

spec, I suppose. In any case, the abomination will be _implemented_ :-( It =
is =

too natural/easy/tempting.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 04:05:34 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E66E63A696E;
	Mon, 20 Oct 2008 04:05:34 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32A4A3A6955;
	Mon, 20 Oct 2008 04:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.692
X-Spam-Level: 
X-Spam-Status: No, score=-3.692 tagged_above=-999 required=5
	tests=[AWL=-0.230, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0lDlkwM+8IUL; Mon, 20 Oct 2008 04:05:32 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id D67023A68FF;
	Mon, 20 Oct 2008 04:05:31 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local 
	(67.pool85-53-133.dynamic.orange.es [85.53.133.67])by smtp03.uc3m.es 
	(Postfix) with ESMTP id 49A446AA51E;
	Mon, 20 Oct 2008 13:06:39 +0200 (CEST)
Message-ID: <48FC663E.1070902@it.uc3m.es>
Date: Mon, 20 Oct 2008 13:06:38 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=<remi.denis-courmont@nokia.com>
References: <48F8539D.90608@ericsson.com> 
	<48FB9C5E.8070402@gmail.com><3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.co
	m> <200810201358.29295.remi.denis-courmont@nokia.com>
In-Reply-To: <200810201358.29295.remi.denis-courmont@nokia.com>
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-6.6642 TC:1F TRN:52 TV:5.5.1026(16228.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

R=E9mi Denis-Courmont escribi=F3:
> On Monday 20 October 2008 13:37:05 ext Iljitsch van Beijnum, you wrote:
>   =

>> Interestingly, I did a small survey about whether people _expect_
>> there to be NAT66 in the future and the majority said "yes".
>>
>> On the one hand we can do nothing and if all goes well there will be
>> no IPv6 NAT so we're all happy because not doing anything made the
>> right thing happen. (Although I've used a NAT66 implementation myself
>> some years back, so there is at least one out there.)
>>
>> But if we do nothing, we run the risk that someone will do a quick
>> search and replace on their NAT44 code and create a port overloading
>> NAT66. The port overloading is 90% of the harmful stuff that NAT boxes
>> do.
>>
>> What we could do is come up with a stateless, transport-agnostic 1-
>> to-1 NAT66 spec so we at least avoid the port overloading and nothing
>> much breaks except referrals.
>>     =

>
> I share your analysis that, _assuming_ we have NAT66, it should be =

> transport-agnostic. IPv6 has a large enough address space, and we are =

> painfully aware of the problems of transport-dependent NAT(44).
>
> However, when I look at the reasons for deploying NAT:
> 1/ address space shortage
> 2/ inbound firewalling
> 3/ topology hiding
> 4/ prefix delegation "bypass"
>
> (1) is a non-issue for IPv6. (2) is solved with stateful firewalling and =
does =

> not require NAT. 1:1 NAT fails to solve (3) as it does hide the subnettin=
g =

> scheme, but fails to hide individual hosts. This leaves only (4). Did I m=
iss =

> anything?
>   =


I think one main reason would be provider independence (ie. no need to =

renumber)  for small sites that cannot afford to have thier own PI =

address block allocated

regards, marcelo

> I still believe we will see NAT66. Not because it's immediately useful. R=
ather =

> because someone will figure out it's easy to adapt NAT44 code to do NAT66=
. =

> For instance, much of the Linux Netfilter framework has become IP =

> version-independent lately, with NAT being the only one big remaining =

> IPv4-specific chunk.
>
>
>
> I guess only time would tell whether a NAT66 1:1 spec would help prevent =
such =

> the transport-dependent NAT66 being _deployed_. It cannot hurt to write t=
hat =

> spec, I suppose. In any case, the abomination will be _implemented_ :-( I=
t is =

> too natural/easy/tempting.
>
>   =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 04:20:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4E193A69B5;
	Mon, 20 Oct 2008 04:20:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA57B3A68F3;
	Mon, 20 Oct 2008 04:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ko2i21QGf+x9; Mon, 20 Oct 2008 04:20:26 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id A92513A68C3;
	Mon, 20 Oct 2008 04:20:25 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.38])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9KBL9Wo092283
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 20 Oct 2008 13:21:09 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200810201358.29295.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 13:21:25 +0200
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 20 okt 2008, at 12:58, R=E9mi Denis-Courmont wrote:

> Did I miss anything?

The reason I brought up NAT66 in shim6 is that the right version of it  =

could be implemented as a simple router rewrite not unlike what's been  =

proposed in GSE/8+8 etc which would be very useful for shim6.

Stable internal addressing when external connectivity changes could  =

also be useful.

> I still believe we will see NAT66. Not because it's immediately  =

> useful. Rather
> because someone will figure out it's easy to adapt NAT44 code to do  =

> NAT66.
> For instance, much of the Linux Netfilter framework has become IP
> version-independent lately, with NAT being the only one big remaining
> IPv4-specific chunk.

As I said, I already played around with such an implementation years  =

ago. Of course it broke FTP, while FTP through NAT44 works because it  =

normally uses passive and even if it doesn't the NAT that I used  =

implements an FTP ALG.

> I guess only time would tell whether a NAT66 1:1 spec would help  =

> prevent such
> the transport-dependent NAT66 being _deployed_. It cannot hurt to  =

> write that
> spec, I suppose. In any case, the abomination will be  =

> _implemented_ :-( It is
> too natural/easy/tempting.

The IETF could exhibit some leadership by saying it will accommodate  =

the pure address rewriting that would be caused by NAT66 by making  =

applications that use referrals work through that, but not accommodate  =

port overloading. That might be enough to keep a port overloading IPv6  =

NAT from becoming widespread. (Or not. But it might.)

Of course the IETF could also come out and say that it will not  =

accommodate any type of IPv6 NAT.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 04:26:09 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 221AB3A69B5;
	Mon, 20 Oct 2008 04:26:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AE8C3A6838;
	Mon, 20 Oct 2008 04:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H+RiUiXwOiik; Mon, 20 Oct 2008 04:26:07 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3E81B3A68C3;
	Mon, 20 Oct 2008 04:26:07 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9KBQXtb013095; Mon, 20 Oct 2008 06:27:14 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 14:26:38 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 14:26:34 +0300
Received: from esdhcp041131.research.nokia.com ([172.21.41.131]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 14:26:33 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext marcelo bagnulo braun" <marcelo@it.uc3m.es>
Date: Mon, 20 Oct 2008 14:26:33 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<48FC663E.1070902@it.uc3m.es>
In-Reply-To: <48FC663E.1070902@it.uc3m.es>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810201426.33336.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 20 Oct 2008 11:26:33.0727 (UTC)
	FILETIME=[B4DF68F0:01C932A6]
X-Nokia-AV: Clean
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Monday 20 October 2008 14:06:38 ext marcelo bagnulo braun, you wrote:
> R=E9mi Denis-Courmont escribi=F3:
> > On Monday 20 October 2008 13:37:05 ext Iljitsch van Beijnum, you wrote:
> >> Interestingly, I did a small survey about whether people _expect_
> >> there to be NAT66 in the future and the majority said "yes".
> >>
> >> On the one hand we can do nothing and if all goes well there will be
> >> no IPv6 NAT so we're all happy because not doing anything made the
> >> right thing happen. (Although I've used a NAT66 implementation myself
> >> some years back, so there is at least one out there.)
> >>
> >> But if we do nothing, we run the risk that someone will do a quick
> >> search and replace on their NAT44 code and create a port overloading
> >> NAT66. The port overloading is 90% of the harmful stuff that NAT boxes
> >> do.
> >>
> >> What we could do is come up with a stateless, transport-agnostic 1-
> >> to-1 NAT66 spec so we at least avoid the port overloading and nothing
> >> much breaks except referrals.
> >
> > I share your analysis that, _assuming_ we have NAT66, it should be
> > transport-agnostic. IPv6 has a large enough address space, and we are
> > painfully aware of the problems of transport-dependent NAT(44).
> >
> > However, when I look at the reasons for deploying NAT:
> > 1/ address space shortage
> > 2/ inbound firewalling
> > 3/ topology hiding
> > 4/ prefix delegation "bypass"
> >
> > (1) is a non-issue for IPv6. (2) is solved with stateful firewalling and
> > does not require NAT. 1:1 NAT fails to solve (3) as it does hide the
> > subnetting scheme, but fails to hide individual hosts. This leaves only
> > (4). Did I miss anything?
>
> I think one main reason would be provider independence (ie. no need to
> renumber)  for small sites that cannot afford to have thier own PI
> address block allocated

That's prefix delegation/routing bypass.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 07:49:31 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E3213A6A95;
	Mon, 20 Oct 2008 07:49:31 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 992C93A6A95
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 07:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5
	tests=[AWL=-0.140, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LAN8SV2nPiy5 for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 07:49:26 -0700 (PDT)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id CC0E73A69CE
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 07:49:26 -0700 (PDT)
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id V0yy1a00817UAYkA72qeJt; Mon, 20 Oct 2008 14:50:38 +0000
Received: from [10.2.1.63] ([69.33.111.74])
	by OMTA13.emeryville.ca.mail.comcast.net with comcast
	id V2qL1a00W1cMU3H8Z2qPyl; Mon, 20 Oct 2008 14:50:36 +0000
X-Authority-Analysis: v=1.0 c=1 a=fY-3ZGM9zUEA:10 a=-v1FiXVGM4UA:10
	a=48vgC7mUAAAA:8 a=WMKt54jRsvVqkJSNMSAA:9 a=g_VGb3k8XEAmrydUpCMA:7
	a=K3nGTGE0AV4MnO-zvuPCZbkhsc0A:4 a=lZB815dzVvQA:10 a=WuK_CZDBSqoA:10
Message-Id: <930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200810201358.29295.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 10:50:19 -0400
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 20, 2008, at 6:58 AM, R=E9mi Denis-Courmont wrote:
> I share your analysis that, _assuming_ we have NAT66, it should be
> transport-agnostic. IPv6 has a large enough address space, and we are
> painfully aware of the problems of transport-dependent NAT(44).
>
> However, when I look at the reasons for deploying NAT:
> 1/ address space shortage
> 2/ inbound firewalling
> 3/ topology hiding
> 4/ prefix delegation "bypass"
>
> (1) is a non-issue for IPv6. (2) is solved with stateful firewalling  =

> and does
> not require NAT. 1:1 NAT fails to solve (3) as it does hide the  =

> subnetting
> scheme, but fails to hide individual hosts. This leaves only (4).  =

> Did I miss
> anything?

There are many enterprise networks that have plenty of IPv4 address  =

space available to them, but choose to use NAT44 as part of their  =

network architecture.  The most common reason I've heard for using  =

NAT44 in these cases is to separate an enterprise's internal address  =

block from the IP address block provided by their ISP, which I think  =

is akin to your option (4).  This allows their internal operations to  =

remain stable across ISP renumbering or a decision to change ISP.

There is every reason to believe that these same enterprises will use  =

NAT66 for exactly the same reason.  In fact, given that all IPv6  =

addresses will be ISP-provided, I'd predict that more, not fewer,  =

enterprises will choose to use NAT66 to gain provider independence.

I agree that it would be a good thing to provide a better alternative,  =

but we have yet to do so.  I'm also unconvinced that we can convince  =

everyone to try the "better" alternative before NAT66 becomes widely  =

deployed.

I don't _want_ NAT66 to be deployed any more than the rest of you, but  =

I believe it is inevitable.  We may have an opportunity to influence  =

how it is implemented and used, but I don't think we can stop it from  =

happening.

> I guess only time would tell whether a NAT66 1:1 spec would help  =

> prevent such
> the transport-dependent NAT66 being _deployed_. It cannot hurt to  =

> write that
> spec, I suppose. In any case, the abomination will be  =

> _implemented_ :-( It is
> too natural/easy/tempting.

After the encouraging response from Marcelo, I'm already working on a  =

draft...  I should have something out by the -00 deadline, but I  =

haven't figured out where to target it yet -- probably it makes more  =

sense to propose it as a behave work item than as a v4v6translation  =

item, since it doesn't involve any IPv4.  Suggestions are welcome,  =

though.

Margaret

>
> -- =

> R=E9mi Denis-Courmont
> Maemo Software, Nokia Devices R&D
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 07:51:20 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEEFF3A6AAD;
	Mon, 20 Oct 2008 07:51:20 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B8CA3A6A37;
	Mon, 20 Oct 2008 07:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.856
X-Spam-Level: 
X-Spam-Status: No, score=-5.856 tagged_above=-999 required=5
	tests=[AWL=-0.207, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qMut-gGvLlwk; Mon, 20 Oct 2008 07:51:15 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 251A23A69B1;
	Mon, 20 Oct 2008 07:51:15 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7933C21E60; Mon, 20 Oct 2008 16:52:10 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-8c-48fc9b1ad0ad
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	491BD21916; Mon, 20 Oct 2008 16:52:10 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 16:52:05 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 16:52:04 +0200
Message-ID: <48FC9B14.6020100@ericsson.com>
Date: Mon, 20 Oct 2008 16:52:04 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
In-Reply-To: <E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 20 Oct 2008 14:52:04.0752 (UTC)
	FILETIME=[6ABC8100:01C932C3]
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE]  Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Please see inline.

Margaret Wasserman skrev:


> =

>> The goal of this work is to encourage migration to IPv6 and compliance
>> with the UNSAF [RFC 3424] considerations. To support deployments where
>> communicating hosts require using different address families (IPv4 or
>> IPv6), address family translation is needed to establish communication.
>> BEHAVE will coordinate with the V6ops WG in this work.
> =

> I think it should be made clearer here whether the translation documents
> will be written in the v6ops WG or behave.  I _think_ this is intended
> to say that the documents will be written in behave, and that the behave
> WG will get input and review regarding operational  requirements and
> deployability from the v6ops WG, but I'd like to see that made clearer.

Yes, that is was intended.

> =

>> The BEHAVE WG will design solutions for the following four translation
>> scenarios; other scenarios are out of scope:
>>
>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and
> =

> "MY" should be expanded or explained before it is first used.

Okay, do you think the following is good enough?

"My" IPv4 or IPv6 network in the descriptions below refer to a network
with a clearly identifiable administrative domain (e.g., an enterprise
campus network, a mobile operator's cellular network, a residential
subscriber network, etc.).



> =

>>   IPv6 for packets in uni- or bi-directional flows that are
>>   initiated from an IPv6 host towards an IPv4 host. The
>>   translator function is intended to service a specific
>>   IPv6 network of arbitary size. Port translation is necessary on
>>   the IPv4 side for efficient IPv4 address usage.
>>
>> 2. IPv6 Internet to MY IPv4, i.e. perform translation between IPv4 and
>>   IPv6 for packets in uni- or bi-directional flows that are
>>   initiated from an IPv6 host towards an IPv4 host.  The translator
>>   function services is intended to service a specific IPv4 network
>>   using either private or public IPv4 addresses. Because this scenario
>>   has different constraints compared to (1), the WG should attempt to
>>   design a simpler solution with less impact on applications.
>>
>> 3. MY IPv4 to IPv6 Internet, i.e. perform translation between IPv4 and
>>   IPv6 for packets in uni- or bi-directional flows that are initiated
>>   from an IPv4 host towards an IPv6 host. The translator function is
>>   intended to service a specific IPv4 network using either public or
>>   private IPv4 address space.
>>
>> 4. IPv4 Internet to MY IPv6, i.e. perform translation between IPv4 and
>>   IPv6 for packets in uni- or bi-directional flows that are initiated
>>   from an IPv4 host towards an IPv6 host. The translator function is
>>   intended to service a specific IPv6 network where selected IPv6 hosts
>>   and services are to be reachable.
> =

> I would also like to us write (at least) two NAT-related documents that
> aren't listed here:
> =

> (1) A document that offers advice on how/when to deploy these translation
> mechanisms vs. other choices.  I think this document would cover topics
> such as:
> =

>     - If the infrastructure will support dual stack and you are running o=
ut
>           of IPv4 addresses, NAT IPv4 and leave IPv6 alone.
>     - The advantages of placing NATs closer to the edges of the network
> =


There has been discussion around a framework document already and I
think that makes sense. I do want to know if anyone is disagreeing.


> (2) An explanation of how to do IPv6 <=3D> IPv6 NAT.  It am convinced that
> there are some people who will choose to do this for the same reasons that
> people with plenty of IPv4 addresses choose to use IPv4 <=3D> IPv4 NATs
> today.  I think we could write a document that says something like:  IPv6
> <=3D> IPv6 NATs are not really necessary, don't provide any concrete
> advantages
> that can't be obtained through less disruptive means, and are not
> recommended
> by the IETF, but if you are planning to do this anyway, please do it
> right (don't
> include port translation, use algorithmic address mapping if possible,
> instead
> of state tables, etc.).

Considering the discussion so far I see some interest. But it seem to
not be a priority item. Lets get the important things going first before
using up a lot of resources in this discussion.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 07:57:38 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CC933A69B1;
	Mon, 20 Oct 2008 07:57:38 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5E693A681C;
	Mon, 20 Oct 2008 07:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.83
X-Spam-Level: 
X-Spam-Status: No, score=-3.83 tagged_above=-999 required=5 tests=[AWL=-0.068, 
	BAYES_00=-2.599, RCVD_BAD_ID=2.837, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mzGM9UFN8K3i; Mon, 20 Oct 2008 07:57:33 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132])
	by core3.amsl.com (Postfix) with ESMTP id 0AF263A69CE;
	Mon, 20 Oct 2008 07:57:32 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local 
	(67.pool85-53-133.dynamic.orange.es [85.53.133.67])by smtp02.uc3m.es 
	(Postfix) with ESMTP id E48015C44EB;
	Mon, 20 Oct 2008 16:58:40 +0200 (CEST)
Message-ID: <48FC9CA0.2060004@it.uc3m.es>
Date: Mon, 20 Oct 2008 16:58:40 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com> 
	<48FB9C5E.8070402@gmail.com><3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.co
	m	><200810201358.29295.remi.denis-courmont@nokia.com> 
	<930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
In-Reply-To: <930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:B L:E SM:2
X-imss-tmaseResult: TT:1 TS:-14.3887 TC:1F TRN:28 TV:5.5.1026(16228.007)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


>
> After the encouraging response from Marcelo, I'm already working on a =

> draft...  I should have something out by the -00 deadline, but I =

> haven't figured out where to target it yet -- probably it makes more =

> sense to propose it as a behave work item than as a v4v6translation =

> item, since it doesn't involve any IPv4.  Suggestions are welcome, =

> though.
>
I would go for int area
actually the nice thing about nat66 is that it is really an IP layer =

mechanism, as opposed to any form of current NATs, that involve transports

regards, marcelo


> Margaret
>
>>
>> -- =

>> R=E9mi Denis-Courmont
>> Maemo Software, Nokia Devices R&D
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 08:15:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 880913A69FF;
	Mon, 20 Oct 2008 08:15:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D41E3A69FF
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 08:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Gd8KrdhBA+9 for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 08:15:44 -0700 (PDT)
Received: from QMTA10.emeryville.ca.mail.comcast.net
	(qmta10.emeryville.ca.mail.comcast.net [76.96.30.17])
	by core3.amsl.com (Postfix) with ESMTP id 7BA2F3A6984
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 08:15:44 -0700 (PDT)
Received: from OMTA04.emeryville.ca.mail.comcast.net ([76.96.30.35])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id V0ls1a00H0lTkoCAA3GwAH; Mon, 20 Oct 2008 15:16:56 +0000
Received: from [10.2.1.63] ([69.33.111.74])
	by OMTA04.emeryville.ca.mail.comcast.net with comcast
	id V3Ge1a0011cMU3H8Q3Gh6S; Mon, 20 Oct 2008 15:16:54 +0000
X-Authority-Analysis: v=1.0 c=1 a=VwO5Xa_HGqIA:10 a=hoJ3PnpNJsQA:10
	a=1VSuPpdHM8vJtSXiC9AA:9 a=cNiumyp5JVoME6dUubgA:7
	a=zBdX0H1qfpYVvRfNRCsZDaI3R9YA:4 a=3SmO1NJXDBsA:10
Message-Id: <546D29AA-286F-4184-ABA0-341915657FF5@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <48FB9C5E.8070402@gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 20 Oct 2008 11:16:37 -0400
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<024001c930a9$a5d00710$c3f0200a@cisco.com>
	<48FB9C5E.8070402@gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


Hi Brian,

On Oct 19, 2008, at 4:45 PM, Brian E Carpenter wrote:
>> NAT66 is still a third rail.  I don't want to go there.
>
> Yep. As Margaret well knows, RFC4864 was written to try to avoid
> stepping on that rail, and includes a gap analysis of what's
> needed to avoid it. I'd rather the IETF put effort into those
> gaps.

As I said in my last message, I don't _want_ people to deploy NAT66.   
I would be extremely pleased if we could find an architecturally  
cleaner solution to meet the provider-independence requirements  
described in RFC 4864 and get people to actually deploy that solution...

However, I've talked to many enterprise network administrators who are  
very happy with their NAT-based network architectures.  The IETF has  
yet to offer a more effective or easier-to-deploy solution for  
provider independence, and I haven't seen anything that would  
incentivize network administrators to move away from their current NAT- 
based architecture as they move from IPv4 to IPv6.  So, I believe that  
there will be widespread deployment of NAT66.  I wish it were  
otherwise, but wishing doesn't make it so.

So, I believe that it is important that we encourage people who plan  
to implement and deploy NAT66 to do it in ways that will be far less  
damaging to the IPv6 Internet than a direct port of their IPv4 NATs to  
IPv6.  Using 1:1 NAT, we should be able to eliminate the port mapping  
mess.  Also, by advocating the option of algorithmic mapping (of ISP / 
48s straight into ULA /48s, for example), we can help people to avoid  
the need for per-connection state, thus eliminating the brittleness  
that NAT introduces into the network.  We could try to get people to  
separate the concept of a NAT and a stateful firewall, making it  
easier for administrators to enable peer-to-peer applications if/when  
their business needs require such applications.  Even little things,  
like encouraging NAT vendors to build NATs that will generate a random  
ULA prefix for the customer if configured to so, may help to avoid  
some of the pitfalls we've suffered with NAT44 and redundant net 10  
addressing.

I understand that you might not be interested in working on a NAT66  
document, instead choosing to focus on developing better solutions to  
the problems described in RFC 4864.  But, don't you think there is  
some good that we could do with a NAT66 document in the meantime?

Margaret
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 12:36:06 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 032683A6AC1;
	Mon, 20 Oct 2008 12:36:06 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58F8E3A6AC1
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 12:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[AWL=-0.021, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XfGAZabEniau for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 12:36:04 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id 001C13A6955
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 12:36:03 -0700 (PDT)
Received: by gxk9 with SMTP id 9so4313755gxk.13
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 12:36:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:from:to:references
	:in-reply-to:subject:date:message-id:mime-version:content-type
	:content-transfer-encoding:x-mailer:thread-index:content-language;
	bh=4FpadSyJ29khnpqerHg5eMzQocfyfWMM2ZR2PavU3Ws=;
	b=xQgYitlToFJaYleTwamCMc44qZ5VaYk7b+LwHhNVqmPuM51LpfA95pYJGg2zF238ET
	4p4kc/8hE0MqxVgCUfMWob6RW77zcQZB84+8BrdZyERmdTg/x10BehhrBqMPCcxHUBCw
	/zKcA1zJ69gjb0360kydoJhz2CBCrNzkLYlrM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:to:references:in-reply-to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding:x-mailer:thread-index
	:content-language;
	b=g/E69DJnJLJVKGTKWcrG1ygubpW3uaKqjFFqNrNxCK+fATzwNIyRtkWSJ92wRRRK8D
	GD3sKtOG84kHky0+OxwYolcjfeQBRa7iNShc/2sS5vlvoT7wrzcdJLgi0vFp261GJNmx
	oK28Il2Gcv8flFYCeq6oMOYGRe86J9YCEf2Zo=
Received: by 10.65.159.14 with SMTP id l14mr3908857qbo.73.1224530982667;
	Mon, 20 Oct 2008 12:29:42 -0700 (PDT)
Received: from Lapci010 (wsip-98-174-20-11.dc.dc.cox.net [98.174.20.11])
	by mx.google.com with ESMTPS id 6sm16796043yxg.6.2008.10.20.12.29.41
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 20 Oct 2008 12:29:42 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: <46translation@employees.org>, <v4v6interim@ietf.org>,
	"'Behave WG'" <behave@ietf.org>
References: <48F8539D.90608@ericsson.com>
	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
In-Reply-To: <200810201358.29295.remi.denis-courmont@nokia.com>
Date: Mon, 20 Oct 2008 15:29:40 -0400
Message-ID: <00fb01c932ea$331db210$99591630$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckyoutElgtDGmrbSlKgnHKIxOb1MAARu81g
Content-Language: en-us
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new
	BEHAVE	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


I am not entirely excited about this conversation, but WRT
	"3/ topology hiding"

NAT66 would accomplish something.  While it doesn't "hide" the specific host
_right now_, it does hide the underlying topology (no 1:1 correlation of
outside and inside addresses / network architecture) as well as hide the
specific host as time moves forward.



... hoping that if it does get defined it gets very little use ...
/TJ


>-----Original Message-----
>From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org] On
>Behalf Of R=E9mi Denis-Courmont
>Sent: Monday, October 20, 2008 6:58 AM
>To: 46translation@employees.org
>Cc: v4v6interim@ietf.org; 'Behave WG'
>Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
>charter
>
>On Monday 20 October 2008 13:37:05 ext Iljitsch van Beijnum, you wrote:
>> Interestingly, I did a small survey about whether people _expect_
>> there to be NAT66 in the future and the majority said "yes".
>>
>> On the one hand we can do nothing and if all goes well there will be
>> no IPv6 NAT so we're all happy because not doing anything made the
>> right thing happen. (Although I've used a NAT66 implementation myself
>> some years back, so there is at least one out there.)
>>
>> But if we do nothing, we run the risk that someone will do a quick
>> search and replace on their NAT44 code and create a port overloading
>> NAT66. The port overloading is 90% of the harmful stuff that NAT boxes
>> do.
>>
>> What we could do is come up with a stateless, transport-agnostic 1-
>> to-1 NAT66 spec so we at least avoid the port overloading and nothing
>> much breaks except referrals.
>
>I share your analysis that, _assuming_ we have NAT66, it should be
>transport-agnostic. IPv6 has a large enough address space, and we are
>painfully aware of the problems of transport-dependent NAT(44).
>
>However, when I look at the reasons for deploying NAT:
>1/ address space shortage
>2/ inbound firewalling
>3/ topology hiding
>4/ prefix delegation "bypass"
>
>(1) is a non-issue for IPv6. (2) is solved with stateful firewalling and
>does not require NAT. 1:1 NAT fails to solve (3) as it does hide the
>subnetting scheme, but fails to hide individual hosts. This leaves only
(4).
>Did I miss anything?
>
>I still believe we will see NAT66. Not because it's immediately useful.
>Rather because someone will figure out it's easy to adapt NAT44 code to do
>NAT66.
>For instance, much of the Linux Netfilter framework has become IP version-
>independent lately, with NAT being the only one big remaining IPv4-specific
>chunk.
>
>
>
>I guess only time would tell whether a NAT66 1:1 spec would help prevent
>such the transport-dependent NAT66 being _deployed_. It cannot hurt to
write
>that spec, I suppose. In any case, the abomination will be _implemented_
:-(
>It is too natural/easy/tempting.
>
>--
>R=E9mi Denis-Courmont
>Maemo Software, Nokia Devices R&D
>_______________________________________________
>v4v6interim mailing list
>v4v6interim@ietf.org
>https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 14:29:31 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46C693A6AF6;
	Mon, 20 Oct 2008 14:29:31 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D7393A6A10
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 14:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5
	tests=[AWL=-0.104, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FOuRyyW1j7-e for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 14:29:28 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id A8B7E3A6A82
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 14:29:28 -0700 (PDT)
Received: by gxk9 with SMTP id 9so4515537gxk.13
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 14:30:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=IgwUWR+8rRYpzdwdBaSCpMSEhb2NKzyCy4nJ36G5QT4=;
	b=VmSzMh6iopyw4ikBtxpswJF1lP+tVL35CDcjXbtr0dSuwGyppTqp4wWZ3WThfc2A6h
	ErV0NicBPw17G7alyTyWq8xgwrX0XY7Jy+rhi22v+Xxn47C6IP+Mh/0yfjemq6oP83ZP
	MbuxYGD3avZKloO9YOPfQ15HxEKRlj9xnXJBw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=exaBSYBoo342iCLHySOOBBrrbLXdQIfiE46OiyQD8w8jFUkIbcQqTb1qHqjlfUu06u
	9Zpol8i5aQvmjo02oMy1+5XIuYfyeJIr/jxBA/hKSC6un0YthcUap00Y5ln5zx2iFVIY
	7Nd/IlB5xuOSFue9tsei4sxPieSEg38KOwZ2Q=
Received: by 10.142.12.14 with SMTP id 14mr3322236wfl.182.1224538239944;
	Mon, 20 Oct 2008 14:30:39 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 28sm15733096wfg.15.2008.10.20.14.30.37
	(version=SSLv3 cipher=RC4-MD5); Mon, 20 Oct 2008 14:30:39 -0700 (PDT)
Message-ID: <48FCF87B.8060609@gmail.com>
Date: Tue, 21 Oct 2008 10:30:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?=
 <remi.denis-courmont@nokia.com>
References: <48F8539D.90608@ericsson.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<48FC663E.1070902@it.uc3m.es>
	<200810201426.33336.remi.denis-courmont@nokia.com>
In-Reply-To: <200810201426.33336.remi.denis-courmont@nokia.com>
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: [v4v6interim] NAT66 for PI [Re: [46translation] [BEHAVE] Proposal
 for new	BEHAVEcharter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

T24gMjAwOC0xMC0yMSAwMDoyNiwgUsOpbWkgRGVuaXMtQ291cm1vbnQgd3JvdGU6Ci4uLgo+Pj4g
NC8gcHJlZml4IGRlbGVnYXRpb24gImJ5cGFzcyIKPj4+Cj4+PiAoMSkgaXMgYSBub24taXNzdWUg
Zm9yIElQdjYuICgyKSBpcyBzb2x2ZWQgd2l0aCBzdGF0ZWZ1bCBmaXJld2FsbGluZyBhbmQKPj4+
IGRvZXMgbm90IHJlcXVpcmUgTkFULiAxOjEgTkFUIGZhaWxzIHRvIHNvbHZlICgzKSBhcyBpdCBk
b2VzIGhpZGUgdGhlCj4+PiBzdWJuZXR0aW5nIHNjaGVtZSwgYnV0IGZhaWxzIHRvIGhpZGUgaW5k
aXZpZHVhbCBob3N0cy4gVGhpcyBsZWF2ZXMgb25seQo+Pj4gKDQpLiBEaWQgSSBtaXNzIGFueXRo
aW5nPwo+PiBJIHRoaW5rIG9uZSBtYWluIHJlYXNvbiB3b3VsZCBiZSBwcm92aWRlciBpbmRlcGVu
ZGVuY2UgKGllLiBubyBuZWVkIHRvCj4+IHJlbnVtYmVyKSAgZm9yIHNtYWxsIHNpdGVzIHRoYXQg
Y2Fubm90IGFmZm9yZCB0byBoYXZlIHRoaWVyIG93biBQSQo+PiBhZGRyZXNzIGJsb2NrIGFsbG9j
YXRlZAo+IAo+IFRoYXQncyBwcmVmaXggZGVsZWdhdGlvbi9yb3V0aW5nIGJ5cGFzcy4KClllcy4g
SXQgYXZvaWRzIHJlbnVtYmVyaW5nLCBhbmQgYWxsb3dzIG11bHRpaG9taW5nLiBJdCdzIHZlcnkg
aGFyZAp0byBzdG9wIHRoaXMgdW5sZXNzIHRoZSBSUkcgY29tZXMgdXAgd2l0aCBhIG1pcmFjbGUg
c29sdXRpb24KaW4gdGhlIG5lYXIgZnV0dXJlLiBJZiB0aGUgc2l0ZSB1c2VzIGEgVUxBIHByZWZp
eCwgaXQgY2FuIGV2ZW4KYXZvaWQgdGhlIGFkZHJlc3MgYW1iaWd1aXR5IHByb2JsZW1zIG9mIFJG
QzE5MTgsIHdpdGhvdXQgZXZlcgpuZWVkIHRvIGFwcGx5IGZvciBQSSBzcGFjZS4KCk9uIDIwMDgt
MTAtMjEgMDQ6MTYsIE1hcmdhcmV0IFdhc3Nlcm1hbiB3cm90ZToKCj4gSSB1bmRlcnN0YW5kIHRo
YXQgeW91IG1pZ2h0IG5vdCBiZSBpbnRlcmVzdGVkIGluIHdvcmtpbmcgb24gYSBOQVQ2NiBkb2N1
bWVudCwgaW5zdGVhZCBjaG9vc2luZyB0byBmb2N1cyBvbiBkZXZlbG9waW5nIGJldHRlciBzb2x1
dGlvbnMgdG8gdGhlIHByb2JsZW1zIGRlc2NyaWJlZCBpbiBSRkMgNDg2NC4gIEJ1dCwgZG9uJ3Qg
eW91IHRoaW5rIHRoZXJlIGlzIHNvbWUgZ29vZCB0aGF0IHdlIGNvdWxkIGRvIHdpdGggYSBOQVQ2
NiBkb2N1bWVudCBpbiB0aGUgbWVhbnRpbWU/CgpNYXJnYXJldCwgSSBmZWFyIHRoYXQgZXZlbiBh
biBSRkMgc2F5aW5nICJEb24ndCBldmVyIGRvIHRoaXMsCmJ1dCBpZiB5b3UgZG8sIGhlcmUncyBo
b3ciIHdpbGwgYmUgd2lkZWx5IHZpZXdlZCBhcyBlbmNvdXJhZ2VtZW50LgpCdXQgdGhlIFJSRyBt
aXJhY2xlIHNlZW1zIHRvIGJlIHNsb3cgaW4gY29taW5nLiBTbyBJJ2xsIHRyeSB0bwpiaXRlIG15
IHRvbmd1ZSA7LSkKCiAgIEJyaWFuCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KdjR2NmludGVyaW0gbWFpbGluZyBsaXN0CnY0djZpbnRlcmltQGlldGYu
b3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Mon Oct 20 14:35:14 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB5E73A6B05;
	Mon, 20 Oct 2008 14:35:14 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 11C153A6849
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 14:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2KGcA0EGmCje for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 14:35:13 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id 9F6BC3A6AD5
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 14:35:12 -0700 (PDT)
Received: by gxk9 with SMTP id 9so4524135gxk.13
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 14:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=pq5c9w5e2qH8kbgJYKbI+lr4dSjgo7so5jvzf8icc8s=;
	b=EUDLRkLnF9liCLrfGw3xLhVuph2a46oxs6RsgsMfo6WlJJXLTEi3qw7qQfv/mVIDeg
	k4V31RM3OC2dz6zUIdyZVtyZP9a1/3sY1IQWjJkcKXzrITvXpi2aXJ0k3PLwZ8vznJVd
	72mQzS88eeBVCdP22ckC+XdRoqD3mRacJpxUQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=HyuERB9RlMIsOCNqIPDwJbtP4boHI82Qy+xjYneEaui89/pLl5aedtHq8A3uW3j9LG
	Yyzy881g0Bluefwmm2xSXxt1ZfEoHgjKzGVId4SxJPQAAnd9KRKP4GKaA/qM6AxvL10n
	v9dRrR1jGbQFZIRzrCucuDlsQJaIRe1ViLYYA=
Received: by 10.142.125.4 with SMTP id x4mr3314545wfc.324.1224538584250;
	Mon, 20 Oct 2008 14:36:24 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 30sm15729015wfd.1.2008.10.20.14.36.21
	(version=SSLv3 cipher=RC4-MD5); Mon, 20 Oct 2008 14:36:23 -0700 (PDT)
Message-ID: <48FCF9D3.7020705@gmail.com>
Date: Tue, 21 Oct 2008 10:36:19 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<48FC9B14.6020100@ericsson.com>
In-Reply-To: <48FC9B14.6020100@ericsson.com>
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: [v4v6interim] "My" [Re: [46translation] [BEHAVE] Proposal for new
 BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 2008-10-21 03:52, Magnus Westerlund wrote:
...
>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and
>> "MY" should be expanded or explained before it is first used.
> 
> Okay, do you think the following is good enough?
> 
> "My" IPv4 or IPv6 network in the descriptions below refer to a network
> with a clearly identifiable administrative domain (e.g., an enterprise
> campus network, a mobile operator's cellular network, a residential
> subscriber network, etc.).

I find the use of "My" frankly a bit silly in a charter.
My Computer is cluttered with silly things like My Network Places,
My Documents and My Pictures, and it's all a bit annoying...

s/My/A specific/ ?

   Brian

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 14:40:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 082923A6AC1;
	Mon, 20 Oct 2008 14:40:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2085E3A6AC1;
	Mon, 20 Oct 2008 14:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ChJTQcTUBrxD; Mon, 20 Oct 2008 14:40:54 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id E9F083A6A10;
	Mon, 20 Oct 2008 14:40:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,454,1220227200"; d="scan'208";a="31303091"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 20 Oct 2008 21:42:00 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9KLfxlG004450; 
	Tue, 21 Oct 2008 05:41:59 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com
	[64.104.123.72])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9KLfxOt006861;
	Mon, 20 Oct 2008 21:41:59 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by
	xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 05:41:59 +0800
Received: from [192.168.100.101] ([10.75.235.99]) by
	xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 05:41:59 +0800
Message-Id: <5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 05:41:57 +0800
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Oct 2008 21:41:59.0036 (UTC)
	FILETIME=[AE126BC0:01C932FC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=467; t=1224538919; x=1225402919;
	c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20[v4v6inter
	im]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=aMoDV+m/3BFWvLY4CNKW5lC74RoBbSgErgiAD+dVL38=;
	b=FMKgQdAXNDMOyJfq/90JJGfbDcPwCGWGwOedU4orMhwknOKSJ/XG0DF4Qe
	llq5tXFtlu0+Ubsjq1fx9IUn0rs6HensJujxwn65CgVbCRKvj0OfqLfUkCOO
	oWWrSZAz9l/7vhFSNpGbUWxTjNGCHoYQh+5wdDzDQ1sDKIY+/jjI8=;
Authentication-Results: hkg-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 20, 2008, at 7:21 PM, Iljitsch van Beijnum wrote:

> Of course the IETF could also come out and say that it will not  
> accommodate any type of IPv6 NAT.

That will travel about one meter and nose-dive. Remember the IETF  
being deluded into thinking that if it didn't work on lawful intercept  
the problem would go away?

Good solutions help, like what RFC 4864 tries to be. Delusional  
thinking and rants about what we don't like don't help.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 14:42:03 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7DF2C3A6B06;
	Mon, 20 Oct 2008 14:42:03 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B7703A6ADC;
	Mon, 20 Oct 2008 14:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PFOcc2uEk+GL; Mon, 20 Oct 2008 14:42:01 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id CD6CF3A6AC1;
	Mon, 20 Oct 2008 14:42:00 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 5A8C729E151F; Mon, 20 Oct 2008 17:43:13 -0400 (EDT)
Message-ID: <48FCFB70.3020207@viagenie.ca>
Date: Mon, 20 Oct 2008 17:43:12 -0400
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>	<48FC9B14.6020100@ericsson.com>
	<48FCF9D3.7020705@gmail.com>
In-Reply-To: <48FCF9D3.7020705@gmail.com>
X-Enigmail-Version: 0.95.7
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] "My" [Re: [46translation] [BEHAVE] Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Brian E Carpenter a =E9crit :
> On 2008-10-21 03:52, Magnus Westerlund wrote:
> ...
>>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4 and
>>> "MY" should be expanded or explained before it is first used.
>> Okay, do you think the following is good enough?
>>
>> "My" IPv4 or IPv6 network in the descriptions below refer to a network
>> with a clearly identifiable administrative domain (e.g., an enterprise
>> campus network, a mobile operator's cellular network, a residential
>> subscriber network, etc.).
> =

> I find the use of "My" frankly a bit silly in a charter.

I had the exact same concern but was shy to say it. now that someone did
it, I support 100%.

Marc.


> My Computer is cluttered with silly things like My Network Places,
> My Documents and My Pictures, and it's all a bit annoying...
> =

> s/My/A specific/ ?
> =

>    Brian
> =

> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim


-- =

=3D=3D=3D=3D=3D=3D=3D=3D=3D
IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
Stun/Turn server: http://numb.viagenie.ca

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 15:42:06 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 056D53A6B18;
	Mon, 20 Oct 2008 15:42:06 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C76B33A6AB4;
	Mon, 20 Oct 2008 15:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4MnUsMeI9wkL; Mon, 20 Oct 2008 15:42:02 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id 788183A6AA0;
	Mon, 20 Oct 2008 15:42:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,454,1220227200"; d="scan'208";a="31305274"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 20 Oct 2008 22:43:10 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9KMhAf4009085; 
	Tue, 21 Oct 2008 06:43:10 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com
	[64.104.123.72])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9KMhASc010855;
	Mon, 20 Oct 2008 22:43:10 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by
	xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 06:43:09 +0800
Received: from [192.168.100.101] ([10.75.235.99]) by
	xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 06:43:09 +0800
Message-Id: <D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Dave Thaler <dthaler@windows.microsoft.com>
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 06:43:08 +0800
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<48FC9B14.6020100@ericsson.com>	<48FCF9D3.7020705@gmail.com>
	<48FCFB70.3020207@viagenie.ca>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 20 Oct 2008 22:43:09.0404 (UTC)
	FILETIME=[39C821C0:01C93305]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2426; t=1224542590;
	x=1225406590; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[46translation]=20[v4v6inter
	im]=20=22My=22=20[Re=3A=20Proposal=20for=20new=20BEHAVE=20ch
	arter] |Sender:=20;
	bh=yM58JoCYzgNv8n4STD7NChZv25AfaWOGtridgIq9m9U=;
	b=Hp2QzDTQnD8ns+FaXY5FjxYQANhbewXFrj7vpJnCRCvwnbltz4q3jTHY/f
	pVC4psYpZeamuPxXQkMFuvPLbROWl2tGDy9rgUWkz7oZYn7hWp4wsQa756JE
	Wp1N37yPeelrvIRIWsAH4T5PTUdmXIdZUUe53XkBKKGJfoWxY9udk=;
Authentication-Results: hkg-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] "My" [Re: Proposal for
	new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Not even sure why it needs to be "a specific". We're going to ahve  =

cross-domain issues, and if we don't think about them we will amke  =

mistakes that will bite us later.

For my money, we are connecting "an IPv4 network" with "an IPv6  =

network", and either might be public or private.

On Oct 21, 2008, at 6:33 AM, Dave Thaler wrote:

> Agree with Brian: s/MY/A specific/
>
> -Dave
>
>> -----Original Message-----
>> From: 46translation-bounces@employees.org [mailto:46translation-
>> bounces@employees.org] On Behalf Of Marc Blanchet
>> Sent: Monday, October 20, 2008 2:43 PM
>> To: Brian E Carpenter
>> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
>> Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE]  =

>> Proposal
>> for new BEHAVE charter]
>>
>> Brian E Carpenter a =E9crit :
>>> On 2008-10-21 03:52, Magnus Westerlund wrote:
>>> ...
>>>>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between  =

>>>>>> IPv4
>> and
>>>>> "MY" should be expanded or explained before it is first used.
>>>> Okay, do you think the following is good enough?
>>>>
>>>> "My" IPv4 or IPv6 network in the descriptions below refer to a
>> network
>>>> with a clearly identifiable administrative domain (e.g., an
>> enterprise
>>>> campus network, a mobile operator's cellular network, a residential
>>>> subscriber network, etc.).
>>>
>>> I find the use of "My" frankly a bit silly in a charter.
>>
>> I had the exact same concern but was shy to say it. now that someone
>> did
>> it, I support 100%.
>>
>> Marc.
>>
>>
>>> My Computer is cluttered with silly things like My Network Places,
>>> My Documents and My Pictures, and it's all a bit annoying...
>>>
>>> s/My/A specific/ ?
>>>
>>>   Brian
>>>
>>> _______________________________________________
>>> v4v6interim mailing list
>>> v4v6interim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>
>>
>> --
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>> IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
>> Stun/Turn server: http://numb.viagenie.ca
>>
>> _______________________________________________
>> 46translation mailing list
>> 46translation@employees.org
>> https://www.employees.org/mailman/listinfo/46translation
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 16:45:33 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD9513A67E9;
	Mon, 20 Oct 2008 16:45:33 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D8BD3A6781;
	Mon, 20 Oct 2008 12:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.45
X-Spam-Level: 
X-Spam-Status: No, score=-110.45 tagged_above=-999 required=5
	tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i-Dm6UdoonxW; Mon, 20 Oct 2008 12:35:47 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id 3FA083A6780;
	Mon, 20 Oct 2008 12:35:47 -0700 (PDT)
Received: from TK5-EXHUB-C101.redmond.corp.microsoft.com (157.54.18.48) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Mon, 20 Oct 2008 12:36:18 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.33) by TK5-EXHUB-C101.redmond.corp.microsoft.com
	(157.54.18.48)
	with Microsoft SMTP Server id 8.1.291.1; Mon, 20 Oct 2008 12:36:16 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::8de9:51a2:cd62:f122]) by
	tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33])
	with mapi; Mon, 20 Oct 2008 12:36:42 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: TJ <trejrco@gmail.com>, "46translation@employees.org"
	<46translation@employees.org>,
	"v4v6interim@ietf.org" <v4v6interim@ietf.org>, 
	'Behave WG' <behave@ietf.org>
Date: Mon, 20 Oct 2008 12:36:14 -0700
Thread-Topic: [46translation] [v4v6interim] [BEHAVE] Proposal for new	BEHAVE
	charter
Thread-Index: AckyoutElgtDGmrbSlKgnHKIxOb1MAARu81gAAAhLFA=
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47610@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<00fb01c932ea$331db210$99591630$@com>
In-Reply-To: <00fb01c932ea$331db210$99591630$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 20 Oct 2008 16:45:32 -0700
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for
	new	BEHAVE	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

The real or perceived reasons to deploy NAT are covered in RFC 4864,
so yes there's more than were listed in below.

However the point of that RFC is to show that NAT is not the only
way to get those benefits.  It contains at least existence proofs
that benefits can be obtained with some other solution (not to
say that an example listed is necessarily the only or even the best
alternative).

-Dave

> -----Original Message-----
> From: 46translation-bounces@employees.org [mailto:46translation-
> bounces@employees.org] On Behalf Of TJ
> Sent: Monday, October 20, 2008 12:30 PM
> To: 46translation@employees.org; v4v6interim@ietf.org; 'Behave WG'
> Subject: Re: [46translation] [v4v6interim] [BEHAVE] Proposal for new
> BEHAVE charter
>
>
> I am not entirely excited about this conversation, but WRT
>         "3/ topology hiding"
>
> NAT66 would accomplish something.  While it doesn't "hide" the specific
> host
> _right now_, it does hide the underlying topology (no 1:1 correlation
> of
> outside and inside addresses / network architecture) as well as hide
> the
> specific host as time moves forward.
>
>
>
> ... hoping that if it does get defined it gets very little use ...
> /TJ
>
>
> >-----Original Message-----
> >From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-
> bounces@ietf.org] On
> >Behalf Of R=E9mi Denis-Courmont
> >Sent: Monday, October 20, 2008 6:58 AM
> >To: 46translation@employees.org
> >Cc: v4v6interim@ietf.org; 'Behave WG'
> >Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new
> BEHAVE
> >charter
> >
> >On Monday 20 October 2008 13:37:05 ext Iljitsch van Beijnum, you
> wrote:
> >> Interestingly, I did a small survey about whether people _expect_
> >> there to be NAT66 in the future and the majority said "yes".
> >>
> >> On the one hand we can do nothing and if all goes well there will be
> >> no IPv6 NAT so we're all happy because not doing anything made the
> >> right thing happen. (Although I've used a NAT66 implementation
> myself
> >> some years back, so there is at least one out there.)
> >>
> >> But if we do nothing, we run the risk that someone will do a quick
> >> search and replace on their NAT44 code and create a port overloading
> >> NAT66. The port overloading is 90% of the harmful stuff that NAT
> boxes
> >> do.
> >>
> >> What we could do is come up with a stateless, transport-agnostic 1-
> >> to-1 NAT66 spec so we at least avoid the port overloading and
> nothing
> >> much breaks except referrals.
> >
> >I share your analysis that, _assuming_ we have NAT66, it should be
> >transport-agnostic. IPv6 has a large enough address space, and we are
> >painfully aware of the problems of transport-dependent NAT(44).
> >
> >However, when I look at the reasons for deploying NAT:
> >1/ address space shortage
> >2/ inbound firewalling
> >3/ topology hiding
> >4/ prefix delegation "bypass"
> >
> >(1) is a non-issue for IPv6. (2) is solved with stateful firewalling
> and
> >does not require NAT. 1:1 NAT fails to solve (3) as it does hide the
> >subnetting scheme, but fails to hide individual hosts. This leaves
> only
> (4).
> >Did I miss anything?
> >
> >I still believe we will see NAT66. Not because it's immediately
> useful.
> >Rather because someone will figure out it's easy to adapt NAT44 code
> to do
> >NAT66.
> >For instance, much of the Linux Netfilter framework has become IP
> version-
> >independent lately, with NAT being the only one big remaining IPv4-
> specific
> >chunk.
> >
> >
> >
> >I guess only time would tell whether a NAT66 1:1 spec would help
> prevent
> >such the transport-dependent NAT66 being _deployed_. It cannot hurt to
> write
> >that spec, I suppose. In any case, the abomination will be
> _implemented_
> :-(
> >It is too natural/easy/tempting.
> >
> >--
> >R=E9mi Denis-Courmont
> >Maemo Software, Nokia Devices R&D
> >_______________________________________________
> >v4v6interim mailing list
> >v4v6interim@ietf.org
> >https://www.ietf.org/mailman/listinfo/v4v6interim
>
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 16:45:33 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D87203A69EC;
	Mon, 20 Oct 2008 16:45:33 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A749F3A68B3;
	Mon, 20 Oct 2008 15:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.456
X-Spam-Level: 
X-Spam-Status: No, score=-110.456 tagged_above=-999 required=5
	tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UxuaY0UWZo2t; Mon, 20 Oct 2008 15:32:45 -0700 (PDT)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214])
	by core3.amsl.com (Postfix) with ESMTP id BD22D3A6862;
	Mon, 20 Oct 2008 15:32:45 -0700 (PDT)
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.54.46.185) by
	TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Mon, 20 Oct 2008 15:33:58 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.33) by tk1-exhub-c101.redmond.corp.microsoft.com
	(157.54.46.185)
	with Microsoft SMTP Server id 8.1.291.1; Mon, 20 Oct 2008 15:33:58 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::8de9:51a2:cd62:f122]) by
	tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33])
	with mapi; Mon, 20 Oct 2008 15:34:24 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>, Brian E Carpenter
	<brian.e.carpenter@gmail.com>
Date: Mon, 20 Oct 2008 15:33:56 -0700
Thread-Topic: [46translation] [v4v6interim] "My" [Re: [BEHAVE] Proposal for
	new BEHAVE charter]
Thread-Index: Acky/ODF7p2ZuzMkQCO8+ltZRCSIyQABvx3A
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<48FC9B14.6020100@ericsson.com>	<48FCF9D3.7020705@gmail.com>
	<48FCFB70.3020207@viagenie.ca>
In-Reply-To: <48FCFB70.3020207@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 20 Oct 2008 16:45:32 -0700
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] "My" [Re: [BEHAVE] Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Agree with Brian: s/MY/A specific/

-Dave

> -----Original Message-----
> From: 46translation-bounces@employees.org [mailto:46translation-
> bounces@employees.org] On Behalf Of Marc Blanchet
> Sent: Monday, October 20, 2008 2:43 PM
> To: Brian E Carpenter
> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
> Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE] Proposal
> for new BEHAVE charter]
>
> Brian E Carpenter a =E9crit :
> > On 2008-10-21 03:52, Magnus Westerlund wrote:
> > ...
> >>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between IPv4
> and
> >>> "MY" should be expanded or explained before it is first used.
> >> Okay, do you think the following is good enough?
> >>
> >> "My" IPv4 or IPv6 network in the descriptions below refer to a
> network
> >> with a clearly identifiable administrative domain (e.g., an
> enterprise
> >> campus network, a mobile operator's cellular network, a residential
> >> subscriber network, etc.).
> >
> > I find the use of "My" frankly a bit silly in a charter.
>
> I had the exact same concern but was shy to say it. now that someone
> did
> it, I support 100%.
>
> Marc.
>
>
> > My Computer is cluttered with silly things like My Network Places,
> > My Documents and My Pictures, and it's all a bit annoying...
> >
> > s/My/A specific/ ?
> >
> >    Brian
> >
> > _______________________________________________
> > v4v6interim mailing list
> > v4v6interim@ietf.org
> > https://www.ietf.org/mailman/listinfo/v4v6interim
>
>
> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
> Stun/Turn server: http://numb.viagenie.ca
>
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 16:45:33 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA4203A6A9E;
	Mon, 20 Oct 2008 16:45:33 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 702403A6B19;
	Mon, 20 Oct 2008 15:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.466
X-Spam-Level: 
X-Spam-Status: No, score=-110.466 tagged_above=-999 required=5
	tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NWunD22uxqwr; Mon, 20 Oct 2008 15:44:59 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id 7372C3A6A95;
	Mon, 20 Oct 2008 15:44:59 -0700 (PDT)
Received: from tk5-exhub-c104.redmond.corp.microsoft.com (157.54.88.97) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Mon, 20 Oct 2008 15:46:07 -0700
Received: from tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.32) by tk5-exhub-c104.redmond.corp.microsoft.com
	(157.54.88.97)
	with Microsoft SMTP Server id 8.1.291.1; Mon, 20 Oct 2008 15:46:07 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::8de9:51a2:cd62:f122]) by
	tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.32])
	with mapi; Mon, 20 Oct 2008 15:46:30 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Fred Baker <fred@cisco.com>
Date: Mon, 20 Oct 2008 15:46:02 -0700
Thread-Topic: [BEHAVE] [46translation] [v4v6interim] "My" [Re: Proposal for
	new BEHAVE charter]
Thread-Index: AckzBUcy0boD8WIqQUqWBIktELNzggAABXPQ
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<48FC9B14.6020100@ericsson.com>	<48FCF9D3.7020705@gmail.com>
	<48FCFB70.3020207@viagenie.ca>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>
In-Reply-To: <D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 20 Oct 2008 16:45:32 -0700
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] "My" [Re: Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

The "specific" network is the one deploying the box that performs
translation.  The term "MY" was used at the interim, although I
agree with Brian that "a specific" is more readable, and is also
consistent with the text that follows the "MY" sentence which already
uses "a specific".

-Dave

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]
> Sent: Monday, October 20, 2008 3:43 PM
> To: Dave Thaler
> Cc: Marc Blanchet; Brian E Carpenter; v4v6interim@ietf.org;
> 46Translation; Behave WG
> Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: Proposal
> for new BEHAVE charter]
>
> Not even sure why it needs to be "a specific". We're going to ahve
> cross-domain issues, and if we don't think about them we will amke
> mistakes that will bite us later.
>
> For my money, we are connecting "an IPv4 network" with "an IPv6
> network", and either might be public or private.
>
> On Oct 21, 2008, at 6:33 AM, Dave Thaler wrote:
>
> > Agree with Brian: s/MY/A specific/
> >
> > -Dave
> >
> >> -----Original Message-----
> >> From: 46translation-bounces@employees.org [mailto:46translation-
> >> bounces@employees.org] On Behalf Of Marc Blanchet
> >> Sent: Monday, October 20, 2008 2:43 PM
> >> To: Brian E Carpenter
> >> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
> >> Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE]
> >> Proposal
> >> for new BEHAVE charter]
> >>
> >> Brian E Carpenter a =E9crit :
> >>> On 2008-10-21 03:52, Magnus Westerlund wrote:
> >>> ...
> >>>>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between
> >>>>>> IPv4
> >> and
> >>>>> "MY" should be expanded or explained before it is first used.
> >>>> Okay, do you think the following is good enough?
> >>>>
> >>>> "My" IPv4 or IPv6 network in the descriptions below refer to a
> >> network
> >>>> with a clearly identifiable administrative domain (e.g., an
> >> enterprise
> >>>> campus network, a mobile operator's cellular network, a
> residential
> >>>> subscriber network, etc.).
> >>>
> >>> I find the use of "My" frankly a bit silly in a charter.
> >>
> >> I had the exact same concern but was shy to say it. now that someone
> >> did
> >> it, I support 100%.
> >>
> >> Marc.
> >>
> >>
> >>> My Computer is cluttered with silly things like My Network Places,
> >>> My Documents and My Pictures, and it's all a bit annoying...
> >>>
> >>> s/My/A specific/ ?
> >>>
> >>>   Brian
> >>>
> >>> _______________________________________________
> >>> v4v6interim mailing list
> >>> v4v6interim@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/v4v6interim
> >>
> >>
> >> --
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
> >> Stun/Turn server: http://numb.viagenie.ca
> >>
> >> _______________________________________________
> >> 46translation mailing list
> >> 46translation@employees.org
> >> https://www.employees.org/mailman/listinfo/46translation
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 23:19:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A5B63A6AEB;
	Mon, 20 Oct 2008 23:19:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B81E63A6AEB
	for <v4v6interim@core3.amsl.com>; Mon, 20 Oct 2008 23:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=0.199, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G17spC1mLOnV for <v4v6interim@core3.amsl.com>;
	Mon, 20 Oct 2008 23:19:40 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id B41243A6A04
	for <v4v6interim@ietf.org>; Mon, 20 Oct 2008 23:19:39 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 6358819756;
	Tue, 21 Oct 2008 08:20:52 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id E045B1724F;
	Tue, 21 Oct 2008 08:20:51 +0200 (CEST)
Message-ID: <48FD746C.6070604@free.fr>
Date: Tue, 21 Oct 2008 08:19:24 +0200
From: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Xing Li <xing@cernet.edu.cn>
References: <B4A9FAB9-F39D-42AA-BE3B-AF6A3C48CC93@cisco.com>	<4391DDA1-6432-	4DCD-8A38-F351C68058B5@muada.com><0F551636-8059-4C93-81F6-AB5421CD4F3F@cisco.com>	<48FBC96D.5020207@cernet.edu.cn>
	<48FC2AFC.60405@it.uc3m.es>	<F2C58F5B-4A97-4F86-8987-832F41424D6E@cisco.com>
	<48FC30EC.50609@cernet.edu.cn>
In-Reply-To: <48FC30EC.50609@cernet.edu.cn>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] "IPv4->IPv6 is hard"
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

WGluZywKCjEuCkkgc2hhcmUgdGhlIHZpZXcgdGhhdCwgIGZvciBJU1BzIHRoYXQgaGF2ZW4ndCBl
bm91Z2ggdjQgYWRkcmVzc2VzIGZvcgphbGwgdGhlaXIgY3VzdG9tZXJzICh0aGVyZSB3aWxsIGJl
IG1vcmUgYW5kIG1vcmUpLCBjaGFyZ2luZyBhIGhpZ2hlcgpwcmljZSBmb3IgdGhvc2UgdGhhdCBu
ZWVkIG9uZSBvciBzZXZlcmFsICBnbG9iYWwgSVB2NCBhZGRyZXNzIG1ha2VzIGEKbG90IG9mIHNl
bnNlLgoKSXQgaXMgbm90IGluIGNvbmZsaWN0IHdpdGggdGhlIGZhY3QgdGhhdCBJU1BzIHRoYXQg
c3RpbGwgaGF2ZSBlbm91Z2ggdjQKc3BhY2UgdG8gZGlzdHJpYnV0ZSBjYW4gYWxzbyBkaXN0cmli
dXRlIElQdjYgcHJlZml4ZXMgd2l0aG91dCBleHRyYQpwcmljZS4gIChGcmVlIGRpZCBpbiBGcmFu
Y2UsIHVzaW5nIDZyZCBmb3IgdGhhdCkuCgpJIGZ1bGx5IGFncmVlIHdpdGggRnJlZCBhbmQgeW91
IHRoYXQsIGZvciB0aGUgY29leGlzdGVuY2UgcGVyaW9kLApwcm9ncmVzcyBvbiBfdGVjaG5vbG9n
aWVzXyBpcyBtb3JlIHRoYW4gZXZlciBhIGhpZ2ggcHJpb3JpdHkuClRoZSBnb2FsIG11c3QgYmUg
d29ya2FibGUgcHJvcG9zYWxzIGFtb25nIHdoaWNoIElTUHMgYW5kIG90aGVyIEludGVybmV0CmFj
dG9ycyB3aWxsIG1ha2UgdGhlaXIgY2hvaWNlcy4KCjIuCk5vdywgZm9yIElTUHMgdGhhdCBhcmUg
c2hvcnQgaW4gdjQgYWRkcmVzc2VzLCBJIGJlbGlldmUgdGhhdCBtZXJnaW5nCklWSSBhbmQgU0FN
IHdvdWxkIHBlcm1pdCB0byBvZmZlciBJUHY0IGNvbm5lY3Rpdml0eSBhY3Jvc3MgSVB2NgpuZXR3
b3JrcyBhdCBubyBleHRyYSBwcmljZS4KCklTUHMgd291bGQgZm9yIHRoaXMgYXNzaWduIHBvcnQt
cmVzdHJpY3RlZCBJUHY0IGFkZHJlc3NlcyB0byBvcmRpbmFyeSAKY3VzdG9tZXJzLCB3aXRoIDE6
MSBjb3JyZXNwb25kZW5jZSBiZXR3ZWVuIHRoZWlyIElQdjYgcHJlZml4ZXMgYW5kIHRoZWlyIApw
b3J0LXJlc3RyaWN0ZWQgYWRkcmVzc2VzLiBUaGlzIGlzIHdoYXQgaXMgZW52aXNhZ2VkIGluIHNl
Y3Rpb24gNi4yIG9mIAp5b3VyIGRyYWZ0LXhsaS1iZWhhdmUtaXZpLTAwLCBidXQgaW4gZml4aW5n
IGRldGFpbHMgYXMgcHJvcG9zZWQgaW4gU0FNLiAKKEEgbmV3IGRyYWZ0IG9uIFNBTSBpcyBwbGFu
bmVkIGZvciBNaW5uZWFwb2xpcy4gSXQgc2hvdWxkIGJlIGVhc2llciB0bwpyZWFkIHRoYW4gZHJh
ZnQtZGVzcHJlcy1zYW0tMDAgYW5kIGRyYWZ0LWRlc3ByZXMtc2FtLXNjZW5hcmlvcy0wMCB0aGF0
IEkgCmhhc3RpbHkgZmluaXNoZWQgd3JpdGluZyBmb3IgdGhlIE1vbnRyZWFsIG1lZXRpbmcpLgoK
Rmlyc3Qgc2ltcGxpZmljYXRpb24gY29tcGFyZWQgdG8gdGhlIGN1cnJlbnQgSVZJOgotIEluIFNB
TSwgdjQgcGFja2V0cyB0aGF0IHRyYXZlcnNlIElQdjYgZG9tYWlucyBhcmUgZm9yIHRoaXMgCmVu
Y2Fwc3VsYXRlZCBpbiB2NiBwYWNrZXRzLgotIFRodXMsIG5vIFNJSVQgdHJhbnNsYXRpb24gKGFu
ZCBubyBBTEcpIGlzIG5lZWRlZCBiZXR3ZWVuIElQdjQgYW5kIElQIAp2NiBhdCB0aGUgYm9yZGVy
IGJldHdlZW4gdGhlIElQdjQgYW5kIElQdjYgZG9tYWlucyA6LSkuCgpTZWNvbmQgc2ltcGxpZmlj
YXRpb246Ci0gSW4gYW4gSVB2NiBhZGRyZXNzLCBTQU0gZW1iZWRzIG9ubHkgdGhlIHBhcnQgb2Yg
dGhlIHBvcnQtcmVzdHJpY3RlZCAKSVB2NCBhZGRyZXNzIHRoYXQgaXMgdXNlZnVsIHRvIGZpbmQg
YSByb3V0ZSAobm90IHRoZSBmaXJzdCBiaXRzIG9mIHRoZSAKSVB2NCBhZGRyZXNzIHRoYXQgYXJl
IHJlZHVuZGFudCB3aXRoIHRoZSBJUHY2IHByZWZpeCkuCi0gVGh1cywgYXMgbG9uZyBhcyB0aGUg
SVB2NiBwcmVmaXggZml0cyBpbiA2NCBiaXRzICh3aGljaCBzaG91bGQgYmUgdGhlCnJ1bGUpLCBu
byBuZXcgdjYgYWRkcmVzcyBmb3JtYXQgaXMgbmVlZGVkIDotKS4KClN1cHBvcnQgb2YgdGhlIElQ
djQtPklQdjYgc2NlbmFyaW86CklmIGEgaG9zdCB0aGF0IHN1cHBvcnRzIFNBTSBpcyBhdHRhY2hl
ZCB0byBhbiBJUHY2LW9ubHkgbmV0d29yayB0aGF0IGhhcyAKU0FNIGdhdGV3YXlzIGF0IGl0cyBi
b3JkZXIgd2l0aCB0aGUgSVB2NCBJbnRlcm5ldCwgdGhpcyBob3N0IGNhbiBiZSAKcmVhY2hlZCwg
YXQgaXRzIHBvcnQtcmVzdHJpY3RlZCBJUHY0IGFkZHJlc3MsIGJ5IGFueSBob3N0IG9uIHRoZSBn
bG9iYWwKSVB2NCBJbnRlcm5ldC4gVGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBpZGVhIG9mIGhvc3Rz
IHRoYXQgZGlyZWN0bHkgCnN1cHBvcnQgSVZJLCB0aGUgIm1vcmUgaW50ZXJlc3Rpbmcgc2NlbmFy
aW8iIG9mIHNlY3Rpb24gNC44ICBpbiB5b3VyIApkcmFmdC14bGktYmVoYXZlLWl2aS0wMC4KCjMu
ClRyeWluZyB0byAgdGFrZSB0aGUgYmVzdCBvZiBJVkksIFNBTSwgYW5kIEErUCwgYW5kIHBvc3Np
Ymx5IG1lcmdlIHRoZW0sCndvdWxkIElNSE8gYmUgYW4gaW50ZXJlc3Rpbmcgc3ViamVjdCBmb3Ig
ZGlzY3Vzc2lvbiBpbiBNaW5uZWFwb2xpcy4KCgpCZXN0IHJlZ2FyZHMKClLDqW1pCgoKCgoKClhp
bmcgTGkgICAobS9qL2EpIDEwLzIwLzA4IDk6MTkgQU06Cj4gRnJlZCBCYWtlciDlhpnpgZM6Cj4+
IExldCdzIHdvcmsgb24gdGhlIHRlY2hub2xvZ3kuCj4gQWdyZWUuIFdlIGFyZSB3b3JraW5nIG9u
IHRlY2hub2xvZ3kgYW5kIHByb3ZpZGUgZmVhc2libGUgc29sdXRpb25zLiAKPiBUaGUgbWFya2V0
IHdpbGwgbWFrZSB0aGUgZGVjaXNpb24uIHhpbmcKPj4gCj4+IAo+IAo+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIHY0djZpbnRlcmltIG1haWxpbmcKPiBs
aXN0IHY0djZpbnRlcmltQGlldGYub3JnIAo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vdjR2NmludGVyaW0KCgoKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KdjR2NmludGVyaW0gbWFpbGluZyBsaXN0CnY0djZpbnRlcmltQGll
dGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0K


From v4v6interim-bounces@ietf.org  Mon Oct 20 23:29:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 368C53A6AF9;
	Mon, 20 Oct 2008 23:29:53 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 785D53A69CF;
	Mon, 20 Oct 2008 23:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level: 
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[AWL=0.188, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SsqAsSD-JrAZ; Mon, 20 Oct 2008 23:29:50 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id ADBB73A6869;
	Mon, 20 Oct 2008 23:29:50 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id E85AC17258;
	Tue, 21 Oct 2008 08:31:03 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 1067E19740;
	Tue, 21 Oct 2008 08:31:02 +0200 (CEST)
Message-ID: <48FD76D0.9050509@free.fr>
Date: Tue, 21 Oct 2008 08:29:36 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com>
	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>
	<930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
In-Reply-To: <930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Margaret Wasserman   (m/j/a) 10/20/08 4:50 PM:
> I don't _want_ NAT66 to be deployed any more than the rest of you, but 
> I believe it is inevitable. 
Although I also believe that IPv6 NATs will be deployed, there is IMO a 
competitive alternative, say SAM66, to implement purely local routing 
plans  in private sites.

It is an IPv6-IPv6 application of the Static Address Mapping approach 
(SAM) I presented in Montreal:
-  E2E IPv6 packets, where they  traverse private routing networks, are 
locally encapsulated (somewhat like for ISATAP, but IPv6 in IPv6).
-  Border routers of customer sites derive intra-site addresses from 
global addresses by substituting an intra-site header to an ISP site prefix.

Its advantages include:
- No interference with the DNS (global addresses are the only needed ones ).
- No interference with transport checksums.
- Stateless operation of border routers (scalability and resilience)
- Openness to site multi-homing with a unique intra-site routing plan 
(yet to be documented ).

Its main drawback is clearly that hosts have to be upgraded (very simple 
addition, yet a real one).  Also,  participation of DHCPv6 (or router 
advertisements?) is needed  to automate configuration. A possible 
consequence that  SAM66 and NAT66 will have to coexist.


Best regards,

RD

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 20 23:41:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91C843A6AEB;
	Mon, 20 Oct 2008 23:41:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 165613A69D0;
	Mon, 20 Oct 2008 23:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.771
X-Spam-Level: 
X-Spam-Status: No, score=-1.771 tagged_above=-999 required=5 tests=[AWL=0.178, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dVYd2dRsr015; Mon, 20 Oct 2008 23:41:47 -0700 (PDT)
Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27])
	by core3.amsl.com (Postfix) with ESMTP id 45CC03A6822;
	Mon, 20 Oct 2008 23:41:47 -0700 (PDT)
Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 1B1731AB2B6;
	Tue, 21 Oct 2008 08:43:00 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp1-g19.free.fr (Postfix) with ESMTP id 562761AB2EC;
	Tue, 21 Oct 2008 08:42:59 +0200 (CEST)
Message-ID: <48FD799C.3040006@free.fr>
Date: Tue, 21 Oct 2008 08:41:32 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dave Thaler <dthaler@windows.microsoft.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>	<48FC9B14.6020100@ericsson.com>	<48FCF9D3.7020705@gmail.com>	<48FCFB70.3020207@viagenie.ca>	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>	<D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] "My" [Re: Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Dave Thaler   (m/j/a) 10/21/08 12:46 AM:
> The "specific" network is the one deploying the box that performs
> translation.  The term "MY" was used at the interim, although I
> agree with Brian that "a specific" is more readable, and is also
> consistent with the text that follows the "MY" sentence which already
> uses "a specific".
>
> -Dave
>   
It seems to me that "an IPvX network" or "an IPvX domain",  as opposed 
to "the IPvY Internet" intuitively conveys the idea without a need for 
the word "specific".

The 4 scenarios are then:
- An IPv4 domain TO and FROM the IPv6 Internet.
- An IPv6 domain TO and FROM the IPv4 Internet.

Even better IMHO:
- A host in an IPvX domain TO and FROM a host on the IPvY Internet.

Regrards,

RD


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 21 00:53:48 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9EF7428C0FF;
	Tue, 21 Oct 2008 00:53:48 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B90E43A6AC1;
	Tue, 21 Oct 2008 00:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t9hRjrBzMwPc; Tue, 21 Oct 2008 00:53:45 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 8B8673A6B11;
	Tue, 21 Oct 2008 00:53:45 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.68])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9L7sPh1011176
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 21 Oct 2008 09:54:26 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <01462145-8E18-465A-8989-D1C98D421DED@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 09:54:43 +0200
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, iab@iab.org
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 20 okt 2008, at 23:41, Fred Baker wrote:

> On Oct 20, 2008, at 7:21 PM, Iljitsch van Beijnum wrote:

>> Of course the IETF could also come out and say that it will not  
>> accommodate any type of IPv6 NAT.

> That will travel about one meter and nose-dive. Remember the IETF  
> being deluded into thinking that if it didn't work on lawful  
> intercept the problem would go away?

Didn't it? This is now "solved" outside the IETF AFAIK.

> Good solutions help, like what RFC 4864 tries to be. Delusional  
> thinking and rants about what we don't like don't help.

Please read carefully. What I said that the IETF could decide that it  
wouldn't _accommodate_ any type of IPv6 NAT. In the past, the IETF has  
come up with numerous protocols that can't work through NAT. These  
days, working through NAT is always a consideration for end-to-end  
protocols that run on top of IPv4. This is often a hard problem, and  
there are many backward compatibility issues with older protocols.

Although we won't be able to make a completely clean break with IPv6,  
we do have the ability to do better than we've done in the past with  
IPv4. I basically see three options for IPv6:

1. We come to the conclusion that port overloading NAT is now part of  
the IP architecture so if at all possible, all protocols must work  
that type of NAT.

2. Since there are alternative mechanisms to reach the same goals in  
IPv6 that people use NAT for in IPv4, the IETF will not address NAT in  
protocols that run on top of IPv6. If end-users implement NAT66  
anyway, they are solely responsible for implementing the workarounds  
necessary to make this work.

3. Because we expect NAT66 to happen anyway, but because the port  
overloading is the most harmful part that we can possibly avoid, we  
specify a stateless, transport-agnostic 1-to-1 NAT66 and make sure  
protocols that run on top of IPv6 can work through that. In case  
people decide to run a port overloading NAT66, see 2.

Also note that the ship has already sailed on unrestricted end-to-end  
connectivity in IPv6, not only in practice but also by IETF mandate  
when the recommendation to use a stateful firewall between IPv6 nodes  
and the internet reached rough consensus. So some level of middlebox  
awareness is already a requirement for IPv6. (And the NAT64 efforts  
add to this to some degree.) The only question is if we want to extend  
this or not.

In my opinion, it would be good if the IETF or IAB (I'll CC them just  
in case they're looking for work) could come to some kind of  
conclusion regarding the above so that we can formulate  
recommendations for transport and application protocol developers.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 21 02:50:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAA8A3A6ACE;
	Tue, 21 Oct 2008 02:50:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CA553A6ACE;
	Tue, 21 Oct 2008 02:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4FNffmjidN5e; Tue, 21 Oct 2008 02:50:16 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id 9EFE33A6A7C;
	Tue, 21 Oct 2008 02:50:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,456,1220227200"; d="scan'208";a="31381804"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163])
	by ind-iport-1.cisco.com with ESMTP; 21 Oct 2008 09:51:13 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9L9pC8P028911; 
	Tue, 21 Oct 2008 17:51:12 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com
	[64.104.123.72])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9L9pC4A012524;
	Tue, 21 Oct 2008 09:51:12 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by
	xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 17:50:58 +0800
Received: from [64.104.120.94] ([64.104.120.94]) by xfe-hkg-411.apac.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 17:50:57 +0800
Message-Id: <B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <01462145-8E18-465A-8989-D1C98D421DED@muada.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 17:50:57 +0800
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 21 Oct 2008 09:50:57.0733 (UTC)
	FILETIME=[845DEF50:01C93362]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=862; t=1224582672; x=1225446672;
	c=relaxed/simple; s=hkgdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20[v4v6inter
	im]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=bRCfwV1VPiQeV0BcEm5baHmkLLJMCiRp2RqYiDRVz84=;
	b=k4Ivjgp+W/sL2w2k5fUV0x7LbV+QlZDG/5MKBgTCf0QVcSTxhsZE0CwtT9
	JfFtAPZ7uU4NMBXak0PLKOIPrZH6PKPA0OBK6xUUYP/yMM0I9tkeHsVN1YUs
	UecwaSvligL19QDbn3EcC64Sry/h2pG51WhaEcjlX7ZW/9quP6+xk=;
Authentication-Results: hkg-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim2001 verified; ); 
Cc: Behave WG <behave@ietf.org>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, iab@iab.org
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Oct 21, 2008, at 3:54 PM, Iljitsch van Beijnum wrote:
> On 20 okt 2008, at 23:41, Fred Baker wrote:
>> On Oct 20, 2008, at 7:21 PM, Iljitsch van Beijnum wrote:
>>> Of course the IETF could also come out and say that it will not  
>>> accommodate any type of IPv6 NAT.
>
>> That will travel about one meter and nose-dive. Remember the IETF  
>> being deluded into thinking that if it didn't work on lawful  
>> intercept the problem would go away?
>
> Didn't it? This is now "solved" outside the IETF AFAIK.

It's very much part of my world.

As to the rest of what you said, I'll agree with you that in a very  
real sense that ship has sailed, and I'll point out that we run the  
same protocols on IPv6 that we run on IPv4. If we have indeed made the  
protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting on  
IPv6 as well.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 21 03:33:20 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84E413A6AB8;
	Tue, 21 Oct 2008 03:33:20 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C72F83A6B0B;
	Tue, 21 Oct 2008 03:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R+U3UUY6sn3T; Tue, 21 Oct 2008 03:33:19 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id B040D3A6AB8;
	Tue, 21 Oct 2008 03:33:18 -0700 (PDT)
Received: from [IPv6:2002:a375:3717:9:21b:63ff:fe02:3c13]
	([IPv6:2002:a375:3717:9:21b:63ff:fe02:3c13]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9LAXv9N013811
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 21 Oct 2008 12:33:58 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 12:34:19 +0200
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>
	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 21 okt 2008, at 11:50, Fred Baker wrote:

> As to the rest of what you said, I'll agree with you that in a very  
> real sense that ship has sailed, and I'll point out that we run the  
> same protocols on IPv6 that we run on IPv4. If we have indeed made  
> the protocols NAT-accepting for IPv4, I'll bet they are NAT- 
> accepting on IPv6 as well.

If only things were this simple.

Many apps that break with NAT do referrals by IP address. So they must  
be updated to work with IPv6, and gain significant additional logic to  
work in a dual stack world. Things like STUN and ICE and their  
proprietary counterparts thus need to be reinvented/implemented for v6  
to make referrals work, and/or the UPnP/NAT-PMP protocols that open up  
ports in NAT devices must be recreated for IPv6 if port overloading  
NAT66s happen.

Today the routing people are complaining that the IPv6 builders didn't  
fix routing. I wonder if in 10 years the apps people are going to  
complain that we didn't fix NAT but just let the same thing happen as  
in IPv4 which BEHAVE has been trying to clean up.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 21 07:08:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC28028C114;
	Tue, 21 Oct 2008 07:08:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 165233A6834
	for <v4v6interim@core3.amsl.com>; Tue, 21 Oct 2008 07:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.028
X-Spam-Level: 
X-Spam-Status: No, score=-6.028 tagged_above=-999 required=5 tests=[AWL=0.017, 
	BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6gomajyGPHZO for <v4v6interim@core3.amsl.com>;
	Tue, 21 Oct 2008 07:07:57 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 430053A697A
	for <v4v6interim@ietf.org>; Tue, 21 Oct 2008 07:07:57 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 21 Oct 2008 14:08:35 -0000
X-AuditID: 80125474-ae19cbb000000a40-b7-48fde2630ae0
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	794A721AF2F; Tue, 21 Oct 2008 07:08:35 -0700 (PDT)
Received: from [192.168.2.101]
	(static-72-90-189-2.nwrknj.east.verizon.net [72.90.189.2])
	by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
	2006)) with ESMTPSA id <0K9300MCSDY9HG50@mail.sri.com>; Tue,
	21 Oct 2008 07:08:35 -0700 (PDT)
Date: Tue, 21 Oct 2008 10:08:34 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
To: Dave Thaler <dthaler@windows.microsoft.com>
Message-id: <48FDE262.8010207@sri.com>
MIME-version: 1.0
References: <48F8539D.90608@ericsson.com>
	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>
	<48FC9B14.6020100@ericsson.com> <48FCF9D3.7020705@gmail.com>
	<48FCFB70.3020207@viagenie.ca>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] "My" [Re: Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1868168912=="
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1868168912==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_SjYNxMVf7m1yCuL018B/xw)"

This is a multi-part message in MIME format.

--Boundary_(ID_SjYNxMVf7m1yCuL018B/xw)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 8BIT

I think what we are trying to get at with "my network" or "a specific 
network" is some handy handle for the domain with address family 
restriction that has a vested interest in translation and coexistence.  
While Fred is right that it is generically "an IPv4 network" with "an 
IPv6 network", the differences in the 4 sub-cases MAY result in 
different solutions:

1.  if "my" network is the one with the minority address family, "I" 
would/could/should be interested in bearing the burden of 
interoperation, hence a solution that costs "me" in time and money is 
acceptable.  As already discussed, this burden shifts over time from 
early adopters to legacy maintainers.  The burden is either doing it 
yourself or paying your ISP to provide the service and the addresses 
required.
2.  if I am the "called" party (i.e. a server) I have a vested interest 
in making "my" network reachable by all "calling" parties, hence a 
distinction between IPv4->IPv6 versus IPv6->IPv4.
3.  more generalized solutions would be nice, but it is easy to fail 
trying to do everything (NAT-PT) or build something that the motivated 
party doesn't need (e.g. someone with lots of IPv4 sensors, etc. may be 
motivated to make them reachable from IPv6, but doesn't need them to 
"call" or be clients to anything on the IPv6 side). 
4.  premature optimization is counterproductive - several solutions that 
each solve part of a big problem well can be combined and simplified, 
but one big solution that does everything not so well (or nothing well) 
tends to get worse in the patching.

I'd say don't get hung up on having a one-word handle to hang on what we 
mean by "the network that is constrained to one address family when the 
rest of the world prefers the other" but I'm sure that can be stated in 
a precise and concise manner in the charter, the scenarios draft, and 
for introductory context for all the solutions.  "Perfect" nomenclature 
is not necessary, but a consistent use of whatever nomenclature is. 

If I had to pick one word it would be "constrained" as in "an 
IPv4-constrained network" meaning (for whatever reason) that the network 
interface to the rest of the world is constrained to sending and 
receiving ONLY IPv4 addressed packets.

Dave Thaler wrote:
> The "specific" network is the one deploying the box that performs
> translation.  The term "MY" was used at the interim, although I
> agree with Brian that "a specific" is more readable, and is also
> consistent with the text that follows the "MY" sentence which already
> uses "a specific".
>
> -Dave
>
>   
>> -----Original Message-----
>> From: Fred Baker [mailto:fred@cisco.com]
>> Sent: Monday, October 20, 2008 3:43 PM
>> To: Dave Thaler
>> Cc: Marc Blanchet; Brian E Carpenter; v4v6interim@ietf.org;
>> 46Translation; Behave WG
>> Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: Proposal
>> for new BEHAVE charter]
>>
>> Not even sure why it needs to be "a specific". We're going to ahve
>> cross-domain issues, and if we don't think about them we will amke
>> mistakes that will bite us later.
>>
>> For my money, we are connecting "an IPv4 network" with "an IPv6
>> network", and either might be public or private.
>>
>> On Oct 21, 2008, at 6:33 AM, Dave Thaler wrote:
>>
>>     
>>> Agree with Brian: s/MY/A specific/
>>>
>>> -Dave
>>>
>>>       
>>>> -----Original Message-----
>>>> From: 46translation-bounces@employees.org [mailto:46translation-
>>>> bounces@employees.org] On Behalf Of Marc Blanchet
>>>> Sent: Monday, October 20, 2008 2:43 PM
>>>> To: Brian E Carpenter
>>>> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
>>>> Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE]
>>>> Proposal
>>>> for new BEHAVE charter]
>>>>
>>>> Brian E Carpenter a écrit :
>>>>         
>>>>> On 2008-10-21 03:52, Magnus Westerlund wrote:
>>>>> ...
>>>>>           
>>>>>>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between
>>>>>>>> IPv4
>>>>>>>>                 
>>>> and
>>>>         
>>>>>>> "MY" should be expanded or explained before it is first used.
>>>>>>>               
>>>>>> Okay, do you think the following is good enough?
>>>>>>
>>>>>> "My" IPv4 or IPv6 network in the descriptions below refer to a
>>>>>>             
>>>> network
>>>>         
>>>>>> with a clearly identifiable administrative domain (e.g., an
>>>>>>             
>>>> enterprise
>>>>         
>>>>>> campus network, a mobile operator's cellular network, a
>>>>>>             
>> residential
>>     
>>>>>> subscriber network, etc.).
>>>>>>             
>>>>> I find the use of "My" frankly a bit silly in a charter.
>>>>>           
>>>> I had the exact same concern but was shy to say it. now that someone
>>>> did
>>>> it, I support 100%.
>>>>
>>>> Marc.
>>>>
>>>>
>>>>         
>>>>> My Computer is cluttered with silly things like My Network Places,
>>>>> My Documents and My Pictures, and it's all a bit annoying...
>>>>>
>>>>> s/My/A specific/ ?
>>>>>
>>>>>   Brian
>>>>>
>>>>> _______________________________________________
>>>>> v4v6interim mailing list
>>>>> v4v6interim@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>>>           
>>>> --
>>>> =========
>>>> IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
>>>> Stun/Turn server: http://numb.viagenie.ca
>>>>
>>>> _______________________________________________
>>>> 46translation mailing list
>>>> 46translation@employees.org
>>>> https://www.employees.org/mailman/listinfo/46translation
>>>>         
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>       
>
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation
>
>   

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 


--Boundary_(ID_SjYNxMVf7m1yCuL018B/xw)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think what we are trying to get at with "my network" or "a specific
network" is some handy handle for the domain with address family
restriction that has a vested interest in translation and coexistence.&nbsp;
While Fred is right that it is generically "an IPv4 network" with "an
IPv6 network", the differences in the 4 sub-cases MAY result in
different solutions:<br>
<br>
1.&nbsp; if "my" network is the one with the minority address family, "I"
would/could/should be interested in bearing the burden of
interoperation, hence a solution that costs "me" in time and money is
acceptable.&nbsp; As already discussed, this burden shifts over time from
early adopters to legacy maintainers.&nbsp; The burden is either doing it
yourself or paying your ISP to provide the service and the addresses
required.<br>
2.&nbsp; if I am the "called" party (i.e. a server) I have a vested interest
in making "my" network reachable by all "calling" parties, hence a
distinction between IPv4-&gt;IPv6 versus IPv6-&gt;IPv4.<br>
3.&nbsp; more generalized solutions would be nice, but it is easy to fail
trying to do everything (NAT-PT) or build something that the motivated
party doesn't need (e.g. someone with lots of IPv4 sensors, etc. may be
motivated to make them reachable from IPv6, but doesn't need them to
"call" or be clients to anything on the IPv6 side).&nbsp; <br>
4.&nbsp; premature optimization is counterproductive - several solutions
that each solve part of a big problem well can be combined and
simplified, but one big solution that does everything not so well (or
nothing well) tends to get worse in the patching.<br>
<br>
I'd say don't get hung up on having a one-word handle to hang on what
we mean by "the network that is constrained to one address family when
the rest of the world prefers the other" but I'm sure that can be
stated in a precise and concise manner in the charter, the scenarios
draft, and for introductory context for all the solutions.&nbsp; "Perfect"
nomenclature is not necessary, but a consistent use of whatever
nomenclature is.&nbsp; <br>
<br>
If I had to pick one word it would be "constrained" as in "an
IPv4-constrained network" meaning (for whatever reason) that the
network interface to the rest of the world is constrained to sending
and receiving ONLY IPv4 addressed packets.<br>
<br>
Dave Thaler wrote:
<blockquote
 cite="mid:E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com"
 type="cite">
  <pre wrap="">The "specific" network is the one deploying the box that performs
translation.  The term "MY" was used at the interim, although I
agree with Brian that "a specific" is more readable, and is also
consistent with the text that follows the "MY" sentence which already
uses "a specific".

-Dave

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Fred Baker [<a class="moz-txt-link-freetext" href="mailto:fred@cisco.com">mailto:fred@cisco.com</a>]
Sent: Monday, October 20, 2008 3:43 PM
To: Dave Thaler
Cc: Marc Blanchet; Brian E Carpenter; <a class="moz-txt-link-abbreviated" href="mailto:v4v6interim@ietf.org">v4v6interim@ietf.org</a>;
46Translation; Behave WG
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: Proposal
for new BEHAVE charter]

Not even sure why it needs to be "a specific". We're going to ahve
cross-domain issues, and if we don't think about them we will amke
mistakes that will bite us later.

For my money, we are connecting "an IPv4 network" with "an IPv6
network", and either might be public or private.

On Oct 21, 2008, at 6:33 AM, Dave Thaler wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">Agree with Brian: s/MY/A specific/

-Dave

      </pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:46translation-bounces@employees.org">46translation-bounces@employees.org</a> [<a class="moz-txt-link-freetext" href="mailto:46translation">mailto:46translation</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@employees.org">bounces@employees.org</a>] On Behalf Of Marc Blanchet
Sent: Monday, October 20, 2008 2:43 PM
To: Brian E Carpenter
Cc: <a class="moz-txt-link-abbreviated" href="mailto:v4v6interim@ietf.org">v4v6interim@ietf.org</a>; 46Translation; Behave WG
Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE]
Proposal
for new BEHAVE charter]

Brian E Carpenter a &eacute;crit :
        </pre>
        <blockquote type="cite">
          <pre wrap="">On 2008-10-21 03:52, Magnus Westerlund wrote:
...
          </pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <blockquote type="cite">
                <pre wrap="">1. MY IPv6 to IPv4 Internet, i.e. perform translation between
IPv4
                </pre>
              </blockquote>
            </blockquote>
          </blockquote>
        </blockquote>
        <pre wrap="">and
        </pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">"MY" should be expanded or explained before it is first used.
              </pre>
            </blockquote>
            <pre wrap="">Okay, do you think the following is good enough?

"My" IPv4 or IPv6 network in the descriptions below refer to a
            </pre>
          </blockquote>
        </blockquote>
        <pre wrap="">network
        </pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">with a clearly identifiable administrative domain (e.g., an
            </pre>
          </blockquote>
        </blockquote>
        <pre wrap="">enterprise
        </pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">campus network, a mobile operator's cellular network, a
            </pre>
          </blockquote>
        </blockquote>
      </blockquote>
    </blockquote>
    <pre wrap="">residential
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">subscriber network, etc.).
            </pre>
          </blockquote>
          <pre wrap="">I find the use of "My" frankly a bit silly in a charter.
          </pre>
        </blockquote>
        <pre wrap="">I had the exact same concern but was shy to say it. now that someone
did
it, I support 100%.

Marc.


        </pre>
        <blockquote type="cite">
          <pre wrap="">My Computer is cluttered with silly things like My Network Places,
My Documents and My Pictures, and it's all a bit annoying...

s/My/A specific/ ?

  Brian

_______________________________________________
v4v6interim mailing list
<a class="moz-txt-link-abbreviated" href="mailto:v4v6interim@ietf.org">v4v6interim@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/v4v6interim">https://www.ietf.org/mailman/listinfo/v4v6interim</a>
          </pre>
        </blockquote>
        <pre wrap="">
--
=========
IPv6 book: Migrating to IPv6, Wiley, 2006. <a class="moz-txt-link-freetext" href="http://www.ipv6book.ca">http://www.ipv6book.ca</a>
Stun/Turn server: <a class="moz-txt-link-freetext" href="http://numb.viagenie.ca">http://numb.viagenie.ca</a>

_______________________________________________
46translation mailing list
<a class="moz-txt-link-abbreviated" href="mailto:46translation@employees.org">46translation@employees.org</a>
<a class="moz-txt-link-freetext" href="https://www.employees.org/mailman/listinfo/46translation">https://www.employees.org/mailman/listinfo/46translation</a>
        </pre>
      </blockquote>
      <pre wrap="">_______________________________________________
Behave mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Behave@ietf.org">Behave@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/behave">https://www.ietf.org/mailman/listinfo/behave</a>
      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
_______________________________________________
46translation mailing list
<a class="moz-txt-link-abbreviated" href="mailto:46translation@employees.org">46translation@employees.org</a>
<a class="moz-txt-link-freetext" href="https://www.employees.org/mailman/listinfo/46translation">https://www.employees.org/mailman/listinfo/46translation</a>

  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  <a class="moz-txt-link-abbreviated" href="mailto:ed.jankiewicz@sri.com">ed.jankiewicz@sri.com</a> 
</pre>
</body>
</html>

--Boundary_(ID_SjYNxMVf7m1yCuL018B/xw)--

--===============1868168912==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

--===============1868168912==--


From v4v6interim-bounces@ietf.org  Wed Oct 22 10:07:45 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0E4528C161;
	Wed, 22 Oct 2008 10:07:45 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 13E963A698A
	for <v4v6interim@core3.amsl.com>; Wed, 22 Oct 2008 10:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 16XDlr0RblQk for <v4v6interim@core3.amsl.com>;
	Wed, 22 Oct 2008 10:07:43 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id E55E83A6952
	for <v4v6interim@ietf.org>; Wed, 22 Oct 2008 10:07:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,465,1220227200"; d="scan'208";a="25279407"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2008 17:08:33 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MH8XEY026216; 
	Wed, 22 Oct 2008 13:08:33 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9MH8X5u023761;
	Wed, 22 Oct 2008 17:08:33 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 13:08:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 13:08:32 -0400
Message-ID: <BB56240F3A190F469C52A57138047A03013200E8@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BEF065E1-C7EC-4B15-9248-DDB8A7612931@lilacglade.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v4v6interim] Audio recording of interim meeting
Thread-Index: Acku5P+B2Ozq0mJ/T/q1sc9uobJzxwFg56ig
References: <48F6159A.5020801@innovationslab.net>
	<BEF065E1-C7EC-4B15-9248-DDB8A7612931@lilacglade.org>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "Margaret Wasserman" <mrw@lilacglade.org>,
	"Brian Haberman" <brian@innovationslab.net>
X-OriginalArrivalTime: 22 Oct 2008 17:08:33.0643 (UTC)
	FILETIME=[D0859BB0:01C93468]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1012; t=1224695313;
	x=1225559313; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m>
	|Subject:=20RE=3A=20[v4v6interim]=20Audio=20recording=20of=
	20interim=20meeting |Sender:=20
	|To:=20=22Margaret=20Wasserman=22=20<mrw@lilacglade.org>,=0
	A=20=20=20=20=20=20=20=20=22Brian=20Haberman=22=20<brian@inn
	ovationslab.net>;
	bh=K0YscyQB6ehuT/m+yESInsLcnuxi4HsnU2H+GmPsvp4=;
	b=Aq6c2TtvtJCrJlkyrNV76rVTiu/9FjxaM1kfXuF+OnhA+9zBoRTUriLUT2
	Wm7o65qhBoWYIWw49t4pFfH0SmT0dKkfz1V5c18dlf/gjLp1kVrm0IJkV0vJ
	d+lBcMMrAd;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Audio recording of interim meeting
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Is there a plan to do WebEx IETF-wide and for every IETF in the future?

- Wes

-----Original Message-----
From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
On Behalf Of Margaret Wasserman
Sent: Wednesday, October 15, 2008 12:42 PM
To: Brian Haberman
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Audio recording of interim meeting



This is great!  Thanks to everyone who helped to make this meeting so
accessible to those of us who couldn't attend in person.

Thanks,
Margaret

On Oct 15, 2008, at 12:08 PM, Brian Haberman wrote:

> All,
>     The audio recordings from the interim meeting are now available on

> the wiki.
>
> Regards,
> Brian
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct 22 10:19:00 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A552B3A69D0;
	Wed, 22 Oct 2008 10:19:00 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 734393A69C5
	for <v4v6interim@core3.amsl.com>; Wed, 22 Oct 2008 10:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.704
X-Spam-Level: 
X-Spam-Status: No, score=-2.704 tagged_above=-999 required=5
	tests=[AWL=-0.105, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XBAQiNekVk15 for <v4v6interim@core3.amsl.com>;
	Wed, 22 Oct 2008 10:18:57 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id 6091E3A698A
	for <v4v6interim@ietf.org>; Wed, 22 Oct 2008 10:18:57 -0700 (PDT)
Received: from ([128.244.206.121])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.121411321;
	Wed, 22 Oct 2008 13:19:31 -0400
Message-ID: <48FF60A3.7030803@innovationslab.net>
Date: Wed, 22 Oct 2008 13:19:31 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
References: <48F6159A.5020801@innovationslab.net>
	<BEF065E1-C7EC-4B15-9248-DDB8A7612931@lilacglade.org>
	<BB56240F3A190F469C52A57138047A03013200E8@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <BB56240F3A190F469C52A57138047A03013200E8@xmb-rtp-211.amer.cisco.com>
Cc: v4v6interim@ietf.org
Subject: Re: [v4v6interim] Audio recording of interim meeting
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Not that I am aware of, but that would be a question better suited for 
the IESG, IAOC, and the Secretariat.

Regards,
Brian


Wes Beebee (wbeebee) wrote:
> Is there a plan to do WebEx IETF-wide and for every IETF in the future?
> 
> - Wes
> 
> -----Original Message-----
> From: v4v6interim-bounces@ietf.org [mailto:v4v6interim-bounces@ietf.org]
> On Behalf Of Margaret Wasserman
> Sent: Wednesday, October 15, 2008 12:42 PM
> To: Brian Haberman
> Cc: v4v6interim@ietf.org
> Subject: Re: [v4v6interim] Audio recording of interim meeting
> 
> 
> 
> This is great!  Thanks to everyone who helped to make this meeting so
> accessible to those of us who couldn't attend in person.
> 
> Thanks,
> Margaret
> 
> On Oct 15, 2008, at 12:08 PM, Brian Haberman wrote:
> 
>> All,
>>     The audio recordings from the interim meeting are now available on
> 
>> the wiki.
>>
>> Regards,
>> Brian
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Wed Oct 22 11:33:51 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 181603A6A94;
	Wed, 22 Oct 2008 11:33:51 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 850703A6A58;
	Wed, 22 Oct 2008 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XjUXTYLkY-Nu; Wed, 22 Oct 2008 11:33:49 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130])
	by core3.amsl.com (Postfix) with ESMTP id C22703A680A;
	Wed, 22 Oct 2008 11:33:48 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1])
	by smtp.piuha.net (Postfix) with ESMTP id 4281819868A;
	Wed, 22 Oct 2008 21:35:05 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130])
	by smtp.piuha.net (Postfix) with ESMTP id CA16D198665;
	Wed, 22 Oct 2008 21:35:04 +0300 (EEST)
Message-ID: <48FF7296.9000100@piuha.net>
Date: Wed, 22 Oct 2008 21:36:06 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <48F8539D.90608@ericsson.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<48FC663E.1070902@it.uc3m.es>	<200810201426.33336.remi.denis-courmont@nokia.com>
	<48FCF87B.8060609@gmail.com>
In-Reply-To: <48FCF87B.8060609@gmail.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [v4v6interim] [BEHAVE] NAT66 for PI [Re: [46translation]
 Proposal for new	BEHAVEcharter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Folks,

We have quite a lot on our plate already. Lets not add NAT66 to it as well.

Jari

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 06:59:17 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58F5B28C0EA;
	Thu, 23 Oct 2008 06:59:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8523D3A6ACB;
	Thu, 23 Oct 2008 06:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.535
X-Spam-Level: 
X-Spam-Status: No, score=-6.535 tagged_above=-999 required=5 tests=[AWL=0.064, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hWqDBmZ3Q-Du; Thu, 23 Oct 2008 06:59:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0BF903A68C1;
	Thu, 23 Oct 2008 06:59:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="23527827"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:00:23 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NE0NB3012701; 
	Thu, 23 Oct 2008 16:00:23 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NE0MbZ028963;
	Thu, 23 Oct 2008 14:00:23 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:00:22 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:00:21 +0200
Message-ID: <49008372.6080909@cisco.com>
Date: Thu, 23 Oct 2008 16:00:18 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dave Thaler <dthaler@windows.microsoft.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>	<48FC9B14.6020100@ericsson.com>	<48FCF9D3.7020705@gmail.com>	<48FCFB70.3020207@viagenie.ca>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
X-OriginalArrivalTime: 23 Oct 2008 14:00:21.0989 (UTC)
	FILETIME=[B095B150:01C93517]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=566; t=1224770423; x=1225634423;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[46translation]=20[v4v6inter
	im]=20=22My=22=20[Re=3A=20Proposal=20for=0A=20new=20BEHAVE=2
	0charter] |Sender:=20;
	bh=9rDPS+ME05MixuHVBW1PAYrhI2OympHzaSljx/cG9jw=;
	b=e2L0KxtkbDQHJLkgiWZvAuEXpEESvpfnQL3tTFD3juzrhxD3q2LDWZGnb3
	UHFKLW6ZqfODjSAAYIMf4QYmaim2Bvjk9uXJbA+2zs65kCT2h4HWT8favMhG
	d9NDuW21Ez;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] "My" [Re: Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Dave Thaler wrote:
>>> My Computer is cluttered with silly things like My Network Places,
>>> My Documents and My Pictures, and it's all a bit annoying...
>>>
>>> s/My/A specific/ ?
>>>
>>>    Brian
>>>       

The use of "My" started with slides I hacked up in the middle of the 
Montreal meeting to make an illustrative point. I too was a little 
surprised that the same term made it as far as the charter.

Since I started it as much as anyone, please know that "A specific" or 
some other more formal language is perfectly fine with me.

- Mark
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 07:21:40 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 735AC3A6C34;
	Thu, 23 Oct 2008 07:21:40 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C7203A6AA9;
	Thu, 23 Oct 2008 07:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.536
X-Spam-Level: 
X-Spam-Status: No, score=-6.536 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Qu1goTwYBrlW; Thu, 23 Oct 2008 07:21:29 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 0519C3A6C30;
	Thu, 23 Oct 2008 07:21:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="23531494"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:22:47 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEMlXx021415; 
	Thu, 23 Oct 2008 16:22:47 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEMkiI007979;
	Thu, 23 Oct 2008 14:22:47 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:22:46 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:22:28 +0200
Message-ID: <490088A1.2000405@cisco.com>
Date: Thu, 23 Oct 2008 16:22:25 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>	<48FC9B14.6020100@ericsson.com>
	<48FCF9D3.7020705@gmail.com>	<48FCFB70.3020207@viagenie.ca>	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47782@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>	<D9C4C55A-F203-4D87-BCDE-C435C74B1A52@cisco.com>	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0BB47791@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<48FDE262.8010207@sri.com>
In-Reply-To: <48FDE262.8010207@sri.com>
X-OriginalArrivalTime: 23 Oct 2008 14:22:28.0351 (UTC)
	FILETIME=[C72878F0:01C9351A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8048; t=1224771767;
	x=1225635767; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20[v4v6inter
	im]=20=22My=22=20[Re=3A=20Proposal=20for=0A=20new=20BEHAVE=2
	0charter] |Sender:=20;
	bh=A3C9+lAIZodLLTanbX27sNGSL5JLCBc4eka05Cja7Ro=;
	b=i45MvmUlpdHBDVSVb+5GIfFEbzLdeR8isVRCOa1Fex0QuJ/UzDDrY7Hsqx
	Yhc2sUTnaLxhHOYISRyZssdmXiktwnm86vPguoW+5rwH1S+jmW2RO2vizZtB
	pAr7xWuCyr;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] "My" [Re: Proposal for
 new BEHAVE charter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


The point of "My" was to refer to someone's network, likely other than =

the whole of the IPv4 or IPv6 Internet. Someone will have to purchase, =

setup, and manage the translator understanding well what the demands on =

the translator will be based on the networks being connected. That is =

still understandably vague, but is about as far as we could get during =

the meeting in Montreal in terms of specifics.

At the start of the meeting, Jari and I tried to identify scenarios =

based on direct feedback from individuals which focused the problem a =

bit more... So, not just *any* type of network, but a rather specific =

one by comparison. Those that came to us with  scenarios were quite =

happy to see them portrayed, others that did not expressed either (1) =

confusion of what the scenario was, (2) doubt that the scenario was =

important, or (3) concern that it meant that their scenario, whether =

topologically similar or not, would not be considered by the IETF. So =

this tactic, frankly, didn't work all that well other than to teach us =

that constraining this problem space into specific types of networks is =

very difficult without losing a lot of consensus along the way.

Clearly, "translate all of IPv4 Internet to the IPv6 Internet in both =

directions" does not work. We were not able to get very specific in =

terms of prioritizing what types of networks should be able to be =

connected to others via translators either. What we ended up with was a =

compromise between the two, with some emphasis on being able to reach =

the IPv4 or IPv6 Internet.

- Mark

Ed Jankiewicz wrote:
> I think what we are trying to get at with "my network" or "a specific =

> network" is some handy handle for the domain with address family =

> restriction that has a vested interest in translation and =

> coexistence.  While Fred is right that it is generically "an IPv4 =

> network" with "an IPv6 network", the differences in the 4 sub-cases =

> MAY result in different solutions:
>
> 1.  if "my" network is the one with the minority address family, "I" =

> would/could/should be interested in bearing the burden of =

> interoperation, hence a solution that costs "me" in time and money is =

> acceptable.  As already discussed, this burden shifts over time from =

> early adopters to legacy maintainers.  The burden is either doing it =

> yourself or paying your ISP to provide the service and the addresses =

> required.
> 2.  if I am the "called" party (i.e. a server) I have a vested =

> interest in making "my" network reachable by all "calling" parties, =

> hence a distinction between IPv4->IPv6 versus IPv6->IPv4.
> 3.  more generalized solutions would be nice, but it is easy to fail =

> trying to do everything (NAT-PT) or build something that the motivated =

> party doesn't need (e.g. someone with lots of IPv4 sensors, etc. may =

> be motivated to make them reachable from IPv6, but doesn't need them =

> to "call" or be clients to anything on the IPv6 side). 4.  premature =

> optimization is counterproductive - several solutions that each solve =

> part of a big problem well can be combined and simplified, but one big =

> solution that does everything not so well (or nothing well) tends to =

> get worse in the patching.
>
> I'd say don't get hung up on having a one-word handle to hang on what =

> we mean by "the network that is constrained to one address family when =

> the rest of the world prefers the other" but I'm sure that can be =

> stated in a precise and concise manner in the charter, the scenarios =

> draft, and for introductory context for all the solutions.  "Perfect" =

> nomenclature is not necessary, but a consistent use of whatever =

> nomenclature is.
> If I had to pick one word it would be "constrained" as in "an =

> IPv4-constrained network" meaning (for whatever reason) that the =

> network interface to the rest of the world is constrained to sending =

> and receiving ONLY IPv4 addressed packets.
>
> Dave Thaler wrote:
>> The "specific" network is the one deploying the box that performs
>> translation.  The term "MY" was used at the interim, although I
>> agree with Brian that "a specific" is more readable, and is also
>> consistent with the text that follows the "MY" sentence which already
>> uses "a specific".
>>
>> -Dave
>>
>>  =

>>> -----Original Message-----
>>> From: Fred Baker [mailto:fred@cisco.com]
>>> Sent: Monday, October 20, 2008 3:43 PM
>>> To: Dave Thaler
>>> Cc: Marc Blanchet; Brian E Carpenter; v4v6interim@ietf.org;
>>> 46Translation; Behave WG
>>> Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: Proposal
>>> for new BEHAVE charter]
>>>
>>> Not even sure why it needs to be "a specific". We're going to ahve
>>> cross-domain issues, and if we don't think about them we will amke
>>> mistakes that will bite us later.
>>>
>>> For my money, we are connecting "an IPv4 network" with "an IPv6
>>> network", and either might be public or private.
>>>
>>> On Oct 21, 2008, at 6:33 AM, Dave Thaler wrote:
>>>
>>>    =

>>>> Agree with Brian: s/MY/A specific/
>>>>
>>>> -Dave
>>>>
>>>>      =

>>>>> -----Original Message-----
>>>>> From: 46translation-bounces@employees.org [mailto:46translation-
>>>>> bounces@employees.org] On Behalf Of Marc Blanchet
>>>>> Sent: Monday, October 20, 2008 2:43 PM
>>>>> To: Brian E Carpenter
>>>>> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
>>>>> Subject: Re: [46translation] [v4v6interim] "My" [Re: [BEHAVE]
>>>>> Proposal
>>>>> for new BEHAVE charter]
>>>>>
>>>>> Brian E Carpenter a =E9crit :
>>>>>        =

>>>>>> On 2008-10-21 03:52, Magnus Westerlund wrote:
>>>>>> ...
>>>>>>          =

>>>>>>>>> 1. MY IPv6 to IPv4 Internet, i.e. perform translation between
>>>>>>>>> IPv4
>>>>>>>>>                 =

>>>>> and
>>>>>        =

>>>>>>>> "MY" should be expanded or explained before it is first used.
>>>>>>>>               =

>>>>>>> Okay, do you think the following is good enough?
>>>>>>>
>>>>>>> "My" IPv4 or IPv6 network in the descriptions below refer to a
>>>>>>>             =

>>>>> network
>>>>>        =

>>>>>>> with a clearly identifiable administrative domain (e.g., an
>>>>>>>             =

>>>>> enterprise
>>>>>        =

>>>>>>> campus network, a mobile operator's cellular network, a
>>>>>>>             =

>>> residential
>>>    =

>>>>>>> subscriber network, etc.).
>>>>>>>             =

>>>>>> I find the use of "My" frankly a bit silly in a charter.
>>>>>>           =

>>>>> I had the exact same concern but was shy to say it. now that someone
>>>>> did
>>>>> it, I support 100%.
>>>>>
>>>>> Marc.
>>>>>
>>>>>
>>>>>        =

>>>>>> My Computer is cluttered with silly things like My Network Places,
>>>>>> My Documents and My Pictures, and it's all a bit annoying...
>>>>>>
>>>>>> s/My/A specific/ ?
>>>>>>
>>>>>>   Brian
>>>>>>
>>>>>> _______________________________________________
>>>>>> v4v6interim mailing list
>>>>>> v4v6interim@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/v4v6interim
>>>>>>           =

>>>>> -- =

>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> IPv6 book: Migrating to IPv6, Wiley, 2006. http://www.ipv6book.ca
>>>>> Stun/Turn server: http://numb.viagenie.ca
>>>>>
>>>>> _______________________________________________
>>>>> 46translation mailing list
>>>>> 46translation@employees.org
>>>>> https://www.employees.org/mailman/listinfo/46translation
>>>>>         =

>>>> _______________________________________________
>>>> Behave mailing list
>>>> Behave@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/behave
>>>>       =

>>
>> _______________________________________________
>> 46translation mailing list
>> 46translation@employees.org
>> https://www.employees.org/mailman/listinfo/46translation
>>
>>   =

>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation
>   =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 07:33:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19E153A69C9;
	Thu, 23 Oct 2008 07:33:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1754A3A69C9;
	Thu, 23 Oct 2008 07:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.148
X-Spam-Level: 
X-Spam-Status: No, score=-6.148 tagged_above=-999 required=5 tests=[AWL=0.101, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZlQZo9b3Na+V; Thu, 23 Oct 2008 07:33:39 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id E0BB03A68CE;
	Thu, 23 Oct 2008 07:33:38 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CB32D2214F; Thu, 23 Oct 2008 16:34:54 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-14-49008b8eca08
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BB5B321479; Thu, 23 Oct 2008 16:34:54 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:34:54 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:34:53 +0200
Message-ID: <49008B8E.9080408@ericsson.com>
Date: Thu, 23 Oct 2008 16:34:54 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <48F8539D.90608@ericsson.com>
	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
In-Reply-To: <9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 23 Oct 2008 14:34:53.0876 (UTC)
	FILETIME=[83868F40:01C9351C]
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Anyway,

Are anyone that thinks that NAT66 is so important that it takes
precedence over the NAT46 translator work? If not, can we postpone this
until we are ready to publish something on address family translators?

The reason I ask the above is that we will have enough work for all the
people in the translator work. Thus trying to avoid splitting the forces
to thinly.

Magnus

Iljitsch van Beijnum skrev:
> On 21 okt 2008, at 11:50, Fred Baker wrote:
> =

>> As to the rest of what you said, I'll agree with you that in a very
>> real sense that ship has sailed, and I'll point out that we run the
>> same protocols on IPv6 that we run on IPv4. If we have indeed made the
>> protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting on
>> IPv6 as well.
> =

> If only things were this simple.
> =

> Many apps that break with NAT do referrals by IP address. So they must
> be updated to work with IPv6, and gain significant additional logic to
> work in a dual stack world. Things like STUN and ICE and their
> proprietary counterparts thus need to be reinvented/implemented for v6
> to make referrals work, and/or the UPnP/NAT-PMP protocols that open up
> ports in NAT devices must be recreated for IPv6 if port overloading
> NAT66s happen.
> =

> Today the routing people are complaining that the IPv6 builders didn't
> fix routing. I wonder if in 10 years the apps people are going to
> complain that we didn't fix NAT but just let the same thing happen as in
> IPv4 which BEHAVE has been trying to clean up.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =



-- =


Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 07:40:43 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 520C63A69F3;
	Thu, 23 Oct 2008 07:40:43 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7D793A6919;
	Thu, 23 Oct 2008 07:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level: 
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.061, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OQvM529mV1G2; Thu, 23 Oct 2008 07:40:33 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 286433A66B4;
	Thu, 23 Oct 2008 07:40:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="23534294"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:41:10 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEfA9R028233; 
	Thu, 23 Oct 2008 16:41:10 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEfA9B014753;
	Thu, 23 Oct 2008 14:41:10 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:41:10 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:41:09 +0200
Message-ID: <49008D03.5080306@cisco.com>
Date: Thu, 23 Oct 2008 16:41:07 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <48F8539D.90608@ericsson.com>	<E1CC009B-8272-4DE7-8D93-88DCB1EDA37C@lilacglade.org>	<024001c930a9$a5d00710$c3f0200a@cisco.com>	<48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
In-Reply-To: <3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
X-OriginalArrivalTime: 23 Oct 2008 14:41:09.0822 (UTC)
	FILETIME=[639B5DE0:01C9351D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=640; t=1224772870; x=1225636870;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20[v4v6inter
	im]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=CHvHY8V05yfJy+0AzkSjwtcfwu8e2+uidGooK6kFMz0=;
	b=aNUySpduWlA+eL5q2oPGYNVcaJ9Y5C+srjAsoihjA+02qVecdV8sg+2Jvo
	ALN3wrMomthoPjSl5s9IF4Okv0SdZnIHcI3hm4Kl/9TD1hW9sGL/ygsmHAAR
	7K36Vh+7eF;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Iljitsch van Beijnum wrote:
>
> What we could do is come up with a stateless, transport-agnostic 
> 1-to-1 NAT66 spec so we at least avoid the port overloading and 
> nothing much breaks except referrals.
I agree that this, together with text touching on why port translation 
hurts, some of Dave Thaler's thoughts on topology hiding, etc. could be 
helpful to have waiting in the wings in the event that someone does 
decide they must do NAT66.

- Mark
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 07:48:56 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A9653A696E;
	Thu, 23 Oct 2008 07:48:56 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A2983A6883;
	Thu, 23 Oct 2008 07:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RbQhGEe1bI1b; Thu, 23 Oct 2008 07:48:54 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 6F27F3A6823;
	Thu, 23 Oct 2008 07:48:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="23535722"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:50:10 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEo9At031630; 
	Thu, 23 Oct 2008 16:50:09 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEo9Dp018038;
	Thu, 23 Oct 2008 14:50:09 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:50:09 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:50:09 +0200
Message-ID: <49008F1E.3010804@cisco.com>
Date: Thu, 23 Oct 2008 16:50:06 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com>
In-Reply-To: <49008B8E.9080408@ericsson.com>
X-OriginalArrivalTime: 23 Oct 2008 14:50:09.0172 (UTC)
	FILETIME=[A515A540:01C9351E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2543; t=1224773409;
	x=1225637409; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=D9VQ6yVggQPHgrYrhFWxhY43h2ko8OHMzXZIEkdLe3M=;
	b=hNpwmygYT+G9TYZ8f0KYao18rFxQih30EU1/a2ZKuaervROVN2zdVNMd/n
	+Db/CT0uTnvSeOivqERnTvcdO8tEOZULkWq1zGW28/AXfjT6jOh4D2obtKX9
	cU880CpQjc;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org, Behave WG <behave@ietf.org>,
	46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Magnus Westerlund wrote:
> Anyway,
>
> Are anyone that thinks that NAT66 is so important that it takes
> precedence over the NAT46 translator work? If not, can we postpone this
> until we are ready to publish something on address family translators?
>
> The reason I ask the above is that we will have enough work for all the
> people in the translator work. Thus trying to avoid splitting the forces
> to thinly.
>   
The NAT66 should be relatively straightforward, and could actually help 
highlight some of the reasons why 46 and 64 become problematic. NAT66 is 
a question that comes up again and again when talking about deploying 
IPv6, and I honestly think it would be useful to have a document to 
point to that brought light to and articulated some of the issues, gave 
strong warning where necessary, and described what was relatively safe 
and what not.

It doesn't really have to be part of behave though.  Magnus, I fully 
understand if you are looking at this new behave charter and can't 
imagine another thing on your plate. As Margaret and others mentioned, 
this can go through int-area, 6man, or some such.

- Mark
> Magnus
>
> Iljitsch van Beijnum skrev:
>   
>> On 21 okt 2008, at 11:50, Fred Baker wrote:
>>
>>     
>>> As to the rest of what you said, I'll agree with you that in a very
>>> real sense that ship has sailed, and I'll point out that we run the
>>> same protocols on IPv6 that we run on IPv4. If we have indeed made the
>>> protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting on
>>> IPv6 as well.
>>>       
>> If only things were this simple.
>>
>> Many apps that break with NAT do referrals by IP address. So they must
>> be updated to work with IPv6, and gain significant additional logic to
>> work in a dual stack world. Things like STUN and ICE and their
>> proprietary counterparts thus need to be reinvented/implemented for v6
>> to make referrals work, and/or the UPnP/NAT-PMP protocols that open up
>> ports in NAT devices must be recreated for IPv6 if port overloading
>> NAT66s happen.
>>
>> Today the routing people are complaining that the IPv6 builders didn't
>> fix routing. I wonder if in 10 years the apps people are going to
>> complain that we didn't fix NAT but just let the same thing happen as in
>> IPv4 which BEHAVE has been trying to clean up.
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
>>     
>
>
>   

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 08:06:08 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01DAF3A69C9;
	Thu, 23 Oct 2008 08:06:08 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCA3D3A696E;
	Thu, 23 Oct 2008 08:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.14
X-Spam-Level: 
X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=0.109, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aTnsP5HV7wx1; Thu, 23 Oct 2008 08:06:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 7F9A93A6821;
	Thu, 23 Oct 2008 08:06:00 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A13D421559; Thu, 23 Oct 2008 17:07:18 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-91-490093260bd7
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6F57521482; Thu, 23 Oct 2008 17:07:18 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:07:18 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:07:17 +0200
Message-ID: <49009325.4080704@ericsson.com>
Date: Thu, 23 Oct 2008 17:07:17 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Mark Townsley <townsley@cisco.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
In-Reply-To: <49008F1E.3010804@cisco.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 23 Oct 2008 15:07:17.0688 (UTC)
	FILETIME=[0A20BB80:01C93521]
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org, Behave WG <behave@ietf.org>,
	46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Mark Townsley skrev:
> Magnus Westerlund wrote:
>> Anyway,
>>
>> Are anyone that thinks that NAT66 is so important that it takes
>> precedence over the NAT46 translator work? If not, can we postpone this
>> until we are ready to publish something on address family translators?
>>
>> The reason I ask the above is that we will have enough work for all the
>> people in the translator work. Thus trying to avoid splitting the forces
>> to thinly.
>>   =

> The NAT66 should be relatively straightforward, and could actually help
> highlight some of the reasons why 46 and 64 become problematic. NAT66 is
> a question that comes up again and again when talking about deploying
> IPv6, and I honestly think it would be useful to have a document to
> point to that brought light to and articulated some of the issues, gave
> strong warning where necessary, and described what was relatively safe
> and what not.
> =

> It doesn't really have to be part of behave though.  Magnus, I fully
> understand if you are looking at this new behave charter and can't
> imagine another thing on your plate. As Margaret and others mentioned,
> this can go through int-area, 6man, or some such.
> =


Yes, I think that is worth considering. It will still likely take some
energy from people involved in the translation work. But, as you write
it might have benefits also.

When it comes to the BEHAVE charter I think there will be additional
items added further down the road. However, I am trying at this stage
charter what we know and are certain that we like to work on. Then we
can do another recharter in a couple of months if necessary. I don't
think we have fully baked where the NAT66 work belongs and will
definitely leave it out now. I am trying to meet the goal of having the
translation work chartered before the meeting.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 08:15:55 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B2A4F28C0DF;
	Thu, 23 Oct 2008 08:15:55 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFF193A6B0E;
	Thu, 23 Oct 2008 08:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level: 
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.059, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uH6XeuNnTyVe; Thu, 23 Oct 2008 08:15:49 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E73D53A6AD8;
	Thu, 23 Oct 2008 08:15:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="23539745"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 15:17:05 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NFH5xf009113; 
	Thu, 23 Oct 2008 17:17:05 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NFH5Pu028252;
	Thu, 23 Oct 2008 15:17:05 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:17:04 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:17:04 +0200
Message-ID: <4900956D.8090409@cisco.com>
Date: Thu, 23 Oct 2008 17:17:01 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<49009325.4080704@ericsson.com>
In-Reply-To: <49009325.4080704@ericsson.com>
X-OriginalArrivalTime: 23 Oct 2008 15:17:04.0424 (UTC)
	FILETIME=[67D98A80:01C93522]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2692; t=1224775025;
	x=1225639025; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=8q0ybtTmJMORnG8r9WSiBdsnIAjk/Vmo3QuIbzBGe+k=;
	b=HtdisT7GV2iffUOVyuLpH+ZlbSCRmPdaLWEqVkUO3/yee3hwLXS8fmnIxz
	kTn6fwZ3E1cfQg0SZ54yd0WlGAowQ69SfxSluDrUjU52JRHn9RpJbw25Xseu
	PnFIm1sQCa;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org, Behave WG <behave@ietf.org>,
	46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Magnus Westerlund wrote:
> Mark Townsley skrev:
>   =

>> Magnus Westerlund wrote:
>>     =

>>> Anyway,
>>>
>>> Are anyone that thinks that NAT66 is so important that it takes
>>> precedence over the NAT46 translator work? If not, can we postpone this
>>> until we are ready to publish something on address family translators?
>>>
>>> The reason I ask the above is that we will have enough work for all the
>>> people in the translator work. Thus trying to avoid splitting the forces
>>> to thinly.
>>>   =

>>>       =

>> The NAT66 should be relatively straightforward, and could actually help
>> highlight some of the reasons why 46 and 64 become problematic. NAT66 is
>> a question that comes up again and again when talking about deploying
>> IPv6, and I honestly think it would be useful to have a document to
>> point to that brought light to and articulated some of the issues, gave
>> strong warning where necessary, and described what was relatively safe
>> and what not.
>>
>> It doesn't really have to be part of behave though.  Magnus, I fully
>> understand if you are looking at this new behave charter and can't
>> imagine another thing on your plate. As Margaret and others mentioned,
>> this can go through int-area, 6man, or some such.
>>
>>     =

>
> Yes, I think that is worth considering. It will still likely take some
> energy from people involved in the translation work. But, as you write
> it might have benefits also.
>
> When it comes to the BEHAVE charter I think there will be additional
> items added further down the road. However, I am trying at this stage
> charter what we know and are certain that we like to work on. Then we
> can do another recharter in a couple of months if necessary. I don't
> think we have fully baked where the NAT66 work belongs and will
> definitely leave it out now. I am trying to meet the goal of having the
> translation work chartered before the meeting.
>   =

Thats fine with me, and in the mean time if someone is sitting on their =

hands with nothing to do, write up a good NAT66 document and we'll =

figure out where it should land.

- Mark
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> F=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>   =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 08:27:58 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0054C3A690B;
	Thu, 23 Oct 2008 08:27:58 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 118833A6AA9
	for <v4v6interim@core3.amsl.com>; Thu, 23 Oct 2008 08:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level: 
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5
	tests=[AWL=-0.386, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tQKnoPqKKY0Q for <v4v6interim@core3.amsl.com>;
	Thu, 23 Oct 2008 08:27:51 -0700 (PDT)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id 910C83A6883
	for <v4v6interim@ietf.org>; Thu, 23 Oct 2008 08:27:51 -0700 (PDT)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id WCwA1a0070EPchoA7FUYju; Thu, 23 Oct 2008 15:28:32 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id WFUE1a0091cMU3H8MFUHBj; Thu, 23 Oct 2008 15:28:30 +0000
X-Authority-Analysis: v=1.0 c=1 a=STE1HZUvVKYA:10 a=vmMR9lSFzVgA:10
	a=48vgC7mUAAAA:8 a=rS_hq24Kl_f0A5p26R0A:9 a=MxaJNUOki63sctjQcuIA:7
	a=WueSlf3LyR5PQ8_9RrPgupXwNQAA:4 a=lZB815dzVvQA:10 a=I2EqgwFF2xUA:10
Message-Id: <EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <49008F1E.3010804@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 11:28:11 -0400
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


I'm getting mixed messages here, but I have a proposal...

Perhaps I could finish the NAT66 draft I've already started, and  
submit it before the -00 cut-off (on Monday).

I think we all agree that NAT66 is not part of the 46translation  
effort and the chair of behave has indicated that it is not in scope  
for behave, so I'll stop cc:ing those groups on my messages about it.   
When the draft comes out, I will send a pointer to intarea and ask for  
feedback.

If Jari and Mark are willing to give me a slot, we could talk about  
the draft at the intarea meeting in Minneapolis.  If there is enough  
interest in NAT66 that it makes sense to continue working on the  
draft, I will.

Even if it takes a while for us to get the NAT66 document published as  
an RFC, we'll have a reasonably well-reviewed draft available in the  
meantime that may help people who start working on NAT66  
implementations to make good design choices.

Does that make sense?

Margaret


On Oct 23, 2008, at 10:50 AM, Mark Townsley wrote:

> Magnus Westerlund wrote:
>> Anyway,
>>
>> Are anyone that thinks that NAT66 is so important that it takes
>> precedence over the NAT46 translator work? If not, can we postpone  
>> this
>> until we are ready to publish something on address family  
>> translators?
>>
>> The reason I ask the above is that we will have enough work for all  
>> the
>> people in the translator work. Thus trying to avoid splitting the  
>> forces
>> to thinly.
>>
> The NAT66 should be relatively straightforward, and could actually  
> help highlight some of the reasons why 46 and 64 become problematic.  
> NAT66 is a question that comes up again and again when talking about  
> deploying IPv6, and I honestly think it would be useful to have a  
> document to point to that brought light to and articulated some of  
> the issues, gave strong warning where necessary, and described what  
> was relatively safe and what not.
>
> It doesn't really have to be part of behave though.  Magnus, I fully  
> understand if you are looking at this new behave charter and can't  
> imagine another thing on your plate. As Margaret and others  
> mentioned, this can go through int-area, 6man, or some such.
>
> - Mark
>> Magnus
>>
>> Iljitsch van Beijnum skrev:
>>
>>> On 21 okt 2008, at 11:50, Fred Baker wrote:
>>>
>>>
>>>> As to the rest of what you said, I'll agree with you that in a very
>>>> real sense that ship has sailed, and I'll point out that we run the
>>>> same protocols on IPv6 that we run on IPv4. If we have indeed  
>>>> made the
>>>> protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting  
>>>> on
>>>> IPv6 as well.
>>>>
>>> If only things were this simple.
>>>
>>> Many apps that break with NAT do referrals by IP address. So they  
>>> must
>>> be updated to work with IPv6, and gain significant additional  
>>> logic to
>>> work in a dual stack world. Things like STUN and ICE and their
>>> proprietary counterparts thus need to be reinvented/implemented  
>>> for v6
>>> to make referrals work, and/or the UPnP/NAT-PMP protocols that  
>>> open up
>>> ports in NAT devices must be recreated for IPv6 if port overloading
>>> NAT66s happen.
>>>
>>> Today the routing people are complaining that the IPv6 builders  
>>> didn't
>>> fix routing. I wonder if in 10 years the apps people are going to
>>> complain that we didn't fix NAT but just let the same thing happen  
>>> as in
>>> IPv4 which BEHAVE has been trying to clean up.
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>
>>
>>
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 08:29:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D7A53A6AE2;
	Thu, 23 Oct 2008 08:29:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB9DA3A6ACC;
	Thu, 23 Oct 2008 08:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.266
X-Spam-Level: 
X-Spam-Status: No, score=-106.266 tagged_above=-999 required=5
	tests=[AWL=-0.267, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xynUgKw+unZn; Thu, 23 Oct 2008 08:29:40 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by core3.amsl.com (Postfix) with ESMTP id E681B3A6A0E;
	Thu, 23 Oct 2008 08:29:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="50180665"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-5.cisco.com with ESMTP; 23 Oct 2008 15:30:59 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NFUxsk015029; 
	Thu, 23 Oct 2008 08:30:59 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9NFUv9n021454;
	Thu, 23 Oct 2008 15:30:58 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Mark Townsley <townsley@cisco.com>,
	Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <49008F1E.3010804@cisco.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
Message-Id: <FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 09:30:52 -0600
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3930; t=1224775859;
	x=1225639859; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=ui9wvLekFbrJHppoMN0JqylViY2l/QPs1bLCvE88Mgw=;
	b=AxDOWHRkxGQ6yMvNne7VUWqBy9CzJIfGKsfZse2npQMt6Q6XHI4w2xCdYY
	3+b8lbKkF3dIi8gFGZ6IA36Mf4x4F4bKg9kc4nYDeFXHgY7FRNPs9QUHPeQA
	DqoLUclIKw/Z4yS8sooEXP0oTfplGm7vGTiPA96Z/SxdwyBOySM5Q=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


I'm not worked up one way or the other about if we should specify  
NAT66 or not - however, if we do specify it, I am very concerned about  
how we do that. I see one good reason not to specify NAT66 and two  
good reasons to.

Reasons not to do NAT 66:
1) All the reasons explained in RFC 4864

Reason to do it:
1) Limitations of RFC 4864 as explained in 4864
2) Large vendors are building nat66 today and they are doing it in a  
way that breaks applications and leaves the application designers with  
no idea about what they can count on working and what they can't count  
on.

If #2 does not remind you of how we got into so much trouble nat44,  
well it should. Because of the impact on NAT66 on applications, if  
IETF does decide to do NAT66 specifications, I think it is very  
important that the specification is developed not only in the context  
of v6ops people but is also developed with input of folks from  
applications that need to use it. Today that would roughly mean behave.

Cullen



On Oct 23, 2008, at 8:50 AM, Mark Townsley wrote:

> Magnus Westerlund wrote:
>> Anyway,
>>
>> Are anyone that thinks that NAT66 is so important that it takes
>> precedence over the NAT46 translator work? If not, can we postpone  
>> this
>> until we are ready to publish something on address family  
>> translators?
>>
>> The reason I ask the above is that we will have enough work for all  
>> the
>> people in the translator work. Thus trying to avoid splitting the  
>> forces
>> to thinly.
>>
> The NAT66 should be relatively straightforward, and could actually  
> help highlight some of the reasons why 46 and 64 become problematic.  
> NAT66 is a question that comes up again and again when talking about  
> deploying IPv6, and I honestly think it would be useful to have a  
> document to point to that brought light to and articulated some of  
> the issues, gave strong warning where necessary, and described what  
> was relatively safe and what not.
>
> It doesn't really have to be part of behave though.  Magnus, I fully  
> understand if you are looking at this new behave charter and can't  
> imagine another thing on your plate. As Margaret and others  
> mentioned, this can go through int-area, 6man, or some such.
>
> - Mark
>> Magnus
>>
>> Iljitsch van Beijnum skrev:
>>
>>> On 21 okt 2008, at 11:50, Fred Baker wrote:
>>>
>>>
>>>> As to the rest of what you said, I'll agree with you that in a very
>>>> real sense that ship has sailed, and I'll point out that we run the
>>>> same protocols on IPv6 that we run on IPv4. If we have indeed  
>>>> made the
>>>> protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting  
>>>> on
>>>> IPv6 as well.
>>>>
>>> If only things were this simple.
>>>
>>> Many apps that break with NAT do referrals by IP address. So they  
>>> must
>>> be updated to work with IPv6, and gain significant additional  
>>> logic to
>>> work in a dual stack world. Things like STUN and ICE and their
>>> proprietary counterparts thus need to be reinvented/implemented  
>>> for v6
>>> to make referrals work, and/or the UPnP/NAT-PMP protocols that  
>>> open up
>>> ports in NAT devices must be recreated for IPv6 if port overloading
>>> NAT66s happen.
>>>
>>> Today the routing people are complaining that the IPv6 builders  
>>> didn't
>>> fix routing. I wonder if in 10 years the apps people are going to
>>> complain that we didn't fix NAT but just let the same thing happen  
>>> as in
>>> IPv4 which BEHAVE has been trying to clean up.
>>> _______________________________________________
>>> Behave mailing list
>>> Behave@ietf.org
>>> https://www.ietf.org/mailman/listinfo/behave
>>>
>>>
>>
>>
>>
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 08:46:12 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3230C3A6BE9;
	Thu, 23 Oct 2008 08:46:12 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B83D53A68D7;
	Thu, 23 Oct 2008 08:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.242
X-Spam-Level: 
X-Spam-Status: No, score=-6.242 tagged_above=-999 required=5
	tests=[AWL=-0.243, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZRm1iug5Xo9E; Thu, 23 Oct 2008 08:46:09 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id D09163A6975;
	Thu, 23 Oct 2008 08:46:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="23544306"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 15:47:27 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NFlRU7020103; 
	Thu, 23 Oct 2008 17:47:27 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NFlRUR009823;
	Thu, 23 Oct 2008 15:47:27 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:47:27 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 17:47:26 +0200
Message-ID: <49009C8B.80707@cisco.com>
Date: Thu, 23 Oct 2008 17:47:23 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
In-Reply-To: <FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 15:47:26.0314 (UTC)
	FILETIME=[A5C7E4A0:01C93526]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4375; t=1224776847;
	x=1225640847; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=/hE7iRD+gAhga0zo1N/ypFuNR9H6Tg85VdiZOi8pm24=;
	b=HbC8lYXUvh7uvRe7GBecjPxEAc1w5eJnDZWCDW7/rh9qLegZ45CI9+hug/
	x+dS1NqttidvXxokqgTSoMNVOA2wnvc4VcOK2/4HZLQNoglsHJpDXXCLmC4D
	lasWkHXbj0;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org



Cullen Jennings wrote:
>
> I'm not worked up one way or the other about if we should specify 
> NAT66 or not - however, if we do specify it, I am very concerned about 
> how we do that. I see one good reason not to specify NAT66 and two 
> good reasons to.

Since saying nothing and hoping folks will abstain doesn't work very 
well in practice, I'd rather we go in and describe safe NAT66 the best 
we can. I agree that we have to be careful to do a good job, as teaching 
bad NAT66 could be worse than not teaching it at all.

>
> Reasons not to do NAT 66:
> 1) All the reasons explained in RFC 4864
>
> Reason to do it:
> 1) Limitations of RFC 4864 as explained in 4864
> 2) Large vendors are building nat66 today and they are doing it in a 
> way that breaks applications and leaves the application designers with 
> no idea about what they can count on working and what they can't count 
> on.
>
> If #2 does not remind you of how we got into so much trouble nat44, 
> well it should. Because of the impact on NAT66 on applications, if 
> IETF does decide to do NAT66 specifications, I think it is very 
> important that the specification is developed not only in the context 
> of v6ops people but is also developed with input of folks from 
> applications that need to use it. Today that would roughly mean behave.
I think that something that operates only at the IP layer could stay in 
the int-area.

- Mark
>
> Cullen
>
>
>
> On Oct 23, 2008, at 8:50 AM, Mark Townsley wrote:
>
>> Magnus Westerlund wrote:
>>> Anyway,
>>>
>>> Are anyone that thinks that NAT66 is so important that it takes
>>> precedence over the NAT46 translator work? If not, can we postpone this
>>> until we are ready to publish something on address family translators?
>>>
>>> The reason I ask the above is that we will have enough work for all the
>>> people in the translator work. Thus trying to avoid splitting the 
>>> forces
>>> to thinly.
>>>
>> The NAT66 should be relatively straightforward, and could actually 
>> help highlight some of the reasons why 46 and 64 become problematic. 
>> NAT66 is a question that comes up again and again when talking about 
>> deploying IPv6, and I honestly think it would be useful to have a 
>> document to point to that brought light to and articulated some of 
>> the issues, gave strong warning where necessary, and described what 
>> was relatively safe and what not.
>>
>> It doesn't really have to be part of behave though.  Magnus, I fully 
>> understand if you are looking at this new behave charter and can't 
>> imagine another thing on your plate. As Margaret and others 
>> mentioned, this can go through int-area, 6man, or some such.
>>
>> - Mark
>>> Magnus
>>>
>>> Iljitsch van Beijnum skrev:
>>>
>>>> On 21 okt 2008, at 11:50, Fred Baker wrote:
>>>>
>>>>
>>>>> As to the rest of what you said, I'll agree with you that in a very
>>>>> real sense that ship has sailed, and I'll point out that we run the
>>>>> same protocols on IPv6 that we run on IPv4. If we have indeed made 
>>>>> the
>>>>> protocols NAT-accepting for IPv4, I'll bet they are NAT-accepting on
>>>>> IPv6 as well.
>>>>>
>>>> If only things were this simple.
>>>>
>>>> Many apps that break with NAT do referrals by IP address. So they must
>>>> be updated to work with IPv6, and gain significant additional logic to
>>>> work in a dual stack world. Things like STUN and ICE and their
>>>> proprietary counterparts thus need to be reinvented/implemented for v6
>>>> to make referrals work, and/or the UPnP/NAT-PMP protocols that open up
>>>> ports in NAT devices must be recreated for IPv6 if port overloading
>>>> NAT66s happen.
>>>>
>>>> Today the routing people are complaining that the IPv6 builders didn't
>>>> fix routing. I wonder if in 10 years the apps people are going to
>>>> complain that we didn't fix NAT but just let the same thing happen 
>>>> as in
>>>> IPv4 which BEHAVE has been trying to clean up.
>>>> _______________________________________________
>>>> Behave mailing list
>>>> Behave@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/behave
>>>>
>>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 09:05:43 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C616C3A69CE;
	Thu, 23 Oct 2008 09:05:43 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 443143A698E;
	Thu, 23 Oct 2008 09:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.258
X-Spam-Level: 
X-Spam-Status: No, score=-106.258 tagged_above=-999 required=5
	tests=[AWL=-0.259, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id blxdB3uQuFXX; Thu, 23 Oct 2008 09:05:41 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 6B1453A6A7E;
	Thu, 23 Oct 2008 09:05:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="95174443"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 23 Oct 2008 16:07:01 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NG6xAD023296; 
	Thu, 23 Oct 2008 09:06:59 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9NG6vu2027698;
	Thu, 23 Oct 2008 16:06:58 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <49009C8B.80707@cisco.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
Message-Id: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 10:06:52 -0600
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2473; t=1224778019;
	x=1225642019; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=7pqdRnzOHZ6GTa/RFByBc6atTfURGuocIqdpQ0F2U2s=;
	b=A0WPTV9pU7Vd7JKQDX0//06FON98vFhTn9x0HWJFdFdelp5lUfq8PCaceg
	XqYrBY/jmlfAAfZNWGWP8JHqCTl6u2cS6YW4kFccDmYJaI0yk+vy7N0mvhCz
	Os+rVf8KhL7IWulVmYNfTx9i2mmDUtfWwWP4E8kr/YwHd2WNjIwog=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 23, 2008, at 9:47 AM, Mark Townsley wrote:

>
>
> Cullen Jennings wrote:
>>
>> I'm not worked up one way or the other about if we should specify  
>> NAT66 or not - however, if we do specify it, I am very concerned  
>> about how we do that. I see one good reason not to specify NAT66  
>> and two good reasons to.
>
> Since saying nothing and hoping folks will abstain doesn't work very  
> well in practice, I'd rather we go in and describe safe NAT66 the  
> best we can. I agree that we have to be careful to do a good job, as  
> teaching bad NAT66 could be worse than not teaching it at all.
>
>>
>> Reasons not to do NAT 66:
>> 1) All the reasons explained in RFC 4864
>>
>> Reason to do it:
>> 1) Limitations of RFC 4864 as explained in 4864
>> 2) Large vendors are building nat66 today and they are doing it in  
>> a way that breaks applications and leaves the application designers  
>> with no idea about what they can count on working and what they  
>> can't count on.
>>
>> If #2 does not remind you of how we got into so much trouble nat44,  
>> well it should. Because of the impact on NAT66 on applications, if  
>> IETF does decide to do NAT66 specifications, I think it is very  
>> important that the specification is developed not only in the  
>> context of v6ops people but is also developed with input of folks  
>> from applications that need to use it. Today that would roughly  
>> mean behave.
> I think that something that operates only at the IP layer could stay  
> in the int-area.

If the mapping was purely and 1:1 mapping between internal and  
external IPs I would agree with you but unfortunately, I worry that  
meeting the requirement that drive section 4.4 of 4864 (privacy and  
topology hiding) really complicate trying to do it with 1:1 mapping at  
IP level.

If you want to be able hide that two uncorrelated sessions are  
actually coming from the same internal host, well, I'm not sure I see  
how to do this with 1:1 mappings. One might argue that one should  
ignore these requirements but this is one of key areas where some  
people feel that 4864 has limitations that drive the deployment of  
NAT66. Two solutions I have seen for this are a) different external IP  
for every internal flow b) doing port address translation similar to  
NAPT in NAT44. Either of these choices has some pretty substantial  
impacts on how to make applications like VoIP work.





_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 09:34:09 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE0EB3A6A30;
	Thu, 23 Oct 2008 09:34:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 089DA3A685C;
	Thu, 23 Oct 2008 09:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.291
X-Spam-Level: 
X-Spam-Status: No, score=-2.291 tagged_above=-999 required=5
	tests=[AWL=-0.292, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1317Ir+NqJvH; Thu, 23 Oct 2008 09:34:07 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id F26723A684D;
	Thu, 23 Oct 2008 09:34:06 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.32] (may be
	forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9NGYraJ064260
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 23 Oct 2008 18:34:54 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <AF18C523-B914-4B8B-80D0-F104D09C87D0@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 18:35:12 +0200
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 23 okt 2008, at 18:06, Cullen Jennings wrote:

> If the mapping was purely and 1:1 mapping between internal and  
> external IPs I would agree with you but unfortunately, I worry that  
> meeting the requirement that drive section 4.4 of 4864 (privacy and  
> topology hiding) really complicate trying to do it with 1:1 mapping  
> at IP level.

But there is no reasonable way to make this work along with incoming  
sessions. Of course all the NAT traversal techniques also expose the  
information that is being hidden here. It's just not compatible with  
the IP model.

Wouldn't proxies be a more reasonable way to solve this than NAT?

About a NAT66 doc: before it's published, it must absolutely be  
reviewed in apps, behave, trans, int, v6ops and 6man.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 09:40:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 027BB3A696E;
	Thu, 23 Oct 2008 09:40:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 341A33A696E;
	Thu, 23 Oct 2008 09:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.236
X-Spam-Level: 
X-Spam-Status: No, score=-6.236 tagged_above=-999 required=5
	tests=[AWL=-0.237, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yATzxnR1KbJh; Thu, 23 Oct 2008 09:40:39 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 9C2CC3A6405;
	Thu, 23 Oct 2008 09:40:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="23551022"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 16:41:57 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NGfvot001507; 
	Thu, 23 Oct 2008 18:41:57 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NGfusi027155;
	Thu, 23 Oct 2008 16:41:57 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 18:41:27 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 18:41:26 +0200
Message-ID: <4900A933.8020501@cisco.com>
Date: Thu, 23 Oct 2008 18:41:23 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
In-Reply-To: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 16:41:26.0249 (UTC)
	FILETIME=[30EEBD90:01C9352E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2699; t=1224780117;
	x=1225644117; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=yXAAqMLxLcxscN+W+ewRHOHWdU3piG87dMPTyj4RoII=;
	b=m0dC+AtW741vqi5EVrwo3zNTpjAhA+Mvtgh9rhRIsCtJbey90xR7eLpcZz
	nXIS6lFQOo02AAkUsCTgaAysxYPqEbn2T9J7wHSdPU0GfBeOezt8vs6LAf0Q
	Clm9V4xX5G;
Authentication-Results: ams-dkim-2; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Cullen Jennings wrote:
>
> On Oct 23, 2008, at 9:47 AM, Mark Townsley wrote:
>
>>
>>
>> Cullen Jennings wrote:
>>>
>>> I'm not worked up one way or the other about if we should specify 
>>> NAT66 or not - however, if we do specify it, I am very concerned 
>>> about how we do that. I see one good reason not to specify NAT66 and 
>>> two good reasons to.
>>
>> Since saying nothing and hoping folks will abstain doesn't work very 
>> well in practice, I'd rather we go in and describe safe NAT66 the 
>> best we can. I agree that we have to be careful to do a good job, as 
>> teaching bad NAT66 could be worse than not teaching it at all.
>>
>>>
>>> Reasons not to do NAT 66:
>>> 1) All the reasons explained in RFC 4864
>>>
>>> Reason to do it:
>>> 1) Limitations of RFC 4864 as explained in 4864
>>> 2) Large vendors are building nat66 today and they are doing it in a 
>>> way that breaks applications and leaves the application designers 
>>> with no idea about what they can count on working and what they 
>>> can't count on.
>>>
>>> If #2 does not remind you of how we got into so much trouble nat44, 
>>> well it should. Because of the impact on NAT66 on applications, if 
>>> IETF does decide to do NAT66 specifications, I think it is very 
>>> important that the specification is developed not only in the 
>>> context of v6ops people but is also developed with input of folks 
>>> from applications that need to use it. Today that would roughly mean 
>>> behave.
>> I think that something that operates only at the IP layer could stay 
>> in the int-area.
>
> If the mapping was purely and 1:1 mapping between internal and 
> external IPs I would agree with you but unfortunately, I worry that 
> meeting the requirement that drive section 4.4 of 4864 (privacy and 
> topology hiding) really complicate trying to do it with 1:1 mapping at 
> IP level.
>
> If you want to be able hide that two uncorrelated sessions are 
> actually coming from the same internal host, well, I'm not sure I see 
> how to do this with 1:1 mappings. One might argue that one should 
> ignore these requirements but this is one of key areas where some 
> people feel that 4864 has limitations that drive the deployment of 
> NAT66. Two solutions I have seen for this are a) different external IP 
> for every internal flow b) doing port address translation similar to 
> NAPT in NAT44. Either of these choices has some pretty substantial 
> impacts on how to make applications like VoIP work.
When I say 1:1, I mean one IP address on one side, one IP address on the 
other, with essentially a static mapping between the two.

- Mark
>
>
>
>
>
>

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 09:57:39 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19EBF3A6912;
	Thu, 23 Oct 2008 09:57:39 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE4BC3A6960;
	Thu, 23 Oct 2008 09:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.104
X-Spam-Level: **
X-Spam-Status: No, score=2.104 tagged_above=-999 required=5 tests=[AWL=-0.100, 
	BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768,
	HOST_EQ_MODEMCABLE=1.368, 
	J_CHICKENPOX_13=0.6, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yAGOTo7jyrhf; Thu, 23 Oct 2008 09:57:36 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com
	[24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 91C7A3A6912;
	Thu, 23 Oct 2008 09:57:35 -0700 (PDT)
Received: from ([10.52.116.30])
	by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.17436103;
	Thu, 23 Oct 2008 12:58:22 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 23 Oct 2008 12:58:21 -0400
Received: from 147.191.223.149 ([147.191.223.149]) by
	PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) via Exchange
	Front-End Server webmail.comcast.com ([24.40.8.152]) with
	Microsoft Exchange Server HTTP-DAV ; Thu, 23 Oct 2008 16:58:21 +0000
User-Agent: Microsoft-Entourage/12.12.0.080729
Date: Thu, 23 Oct 2008 12:58:19 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: Cullen Jennings <fluffy@cisco.com>,
	Mark Townsley <townsley@cisco.com>
Message-ID: <C526256B.1C487%alain_durand@cable.comcast.com>
Thread-Topic: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
Thread-Index: Ack1KXRIt+5f0az+SxaeSi3vqUz1XQABxhP4
In-Reply-To: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 23 Oct 2008 16:58:21.0490 (UTC)
	FILETIME=[8E103920:01C93530]
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
 BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I'm going to jump into this and probably not make friends...

IPv6 is just like IPv4 with longer addresses. This is where deployment
reality trumps architectural purity.

What I've seen in the last 3 years is that it is much, much easier to deploy
IPv6 if you keep the exact same operational model as in IPv4. This is one
(among many) reason why we pushed for DHCPv6.

Many folks are considering NAT44 as a simple solution where they just have
to put a box in front of their network to make whatever problem they think
they have go away. I can easily see that the same people would like to do
the same thing with IPv6. Which exact problem they were solving is
irrelevant to this discussion, the point is about preserving the same
operational model.

That, and Cullen Jennings point #2 argue for defining NAT66 exactly the same
way as NAT44, ie with (optional) port translation. We have the opportunity
to explain why some choices are less worse than others in doing so and put
all the caveats in place. That is, make sure all the behave work done for
NAT44 is immediately integrated in NAT66, or in  other words, lets define
NAT66 in behave. Now, we may argue about the urgency of doing this... Ie
should this be done in parallel as NAT64 & NAT46 or after.

   - Alain.


On 10/23/08 12:06 PM, "Cullen Jennings" <fluffy@cisco.com> wrote:

> 
> 
> On Oct 23, 2008, at 9:47 AM, Mark Townsley wrote:
> 
>> 
>> 
>> Cullen Jennings wrote:
>>> 
>>> I'm not worked up one way or the other about if we should specify
>>> NAT66 or not - however, if we do specify it, I am very concerned
>>> about how we do that. I see one good reason not to specify NAT66
>>> and two good reasons to.
>> 
>> Since saying nothing and hoping folks will abstain doesn't work very
>> well in practice, I'd rather we go in and describe safe NAT66 the
>> best we can. I agree that we have to be careful to do a good job, as
>> teaching bad NAT66 could be worse than not teaching it at all.
>> 
>>> 
>>> Reasons not to do NAT 66:
>>> 1) All the reasons explained in RFC 4864
>>> 
>>> Reason to do it:
>>> 1) Limitations of RFC 4864 as explained in 4864
>>> 2) Large vendors are building nat66 today and they are doing it in
>>> a way that breaks applications and leaves the application designers
>>> with no idea about what they can count on working and what they
>>> can't count on.
>>> 
>>> If #2 does not remind you of how we got into so much trouble nat44,
>>> well it should. Because of the impact on NAT66 on applications, if
>>> IETF does decide to do NAT66 specifications, I think it is very
>>> important that the specification is developed not only in the
>>> context of v6ops people but is also developed with input of folks
>>> from applications that need to use it. Today that would roughly
>>> mean behave.
>> I think that something that operates only at the IP layer could stay
>> in the int-area.
> 
> If the mapping was purely and 1:1 mapping between internal and
> external IPs I would agree with you but unfortunately, I worry that
> meeting the requirement that drive section 4.4 of 4864 (privacy and
> topology hiding) really complicate trying to do it with 1:1 mapping at
> IP level.
> 
> If you want to be able hide that two uncorrelated sessions are
> actually coming from the same internal host, well, I'm not sure I see
> how to do this with 1:1 mappings. One might argue that one should
> ignore these requirements but this is one of key areas where some
> people feel that 4864 has limitations that drive the deployment of
> NAT66. Two solutions I have seen for this are a) different external IP
> for every internal flow b) doing port address translation similar to
> NAPT in NAT44. Either of these choices has some pretty substantial
> impacts on how to make applications like VoIP work.
> 
> 
> 
> 
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 10:34:29 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7117E3A6912;
	Thu, 23 Oct 2008 10:34:29 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4A013A6838;
	Thu, 23 Oct 2008 10:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.231
X-Spam-Level: 
X-Spam-Status: No, score=-6.231 tagged_above=-999 required=5
	tests=[AWL=-0.232, BAYES_00=-2.599, J_CHICKENPOX_23=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tx2T8zQZwygi; Thu, 23 Oct 2008 10:34:26 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id E77B43A6767;
	Thu, 23 Oct 2008 10:34:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="110635448"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 23 Oct 2008 17:35:46 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9NHZkbq026730; 
	Thu, 23 Oct 2008 10:35:46 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9NHZkRB028741;
	Thu, 23 Oct 2008 17:35:46 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Margaret Wasserman'" <mrw@lilacglade.org>,
	"'Mark Townsley'" <townsley@cisco.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com><49008B8E.9080408@ericsson.com>
	<49008F1E.3010804@cisco.com>
	<EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
Date: Thu, 23 Oct 2008 10:35:46 -0700
Message-ID: <031d01c93535$c85b1140$9d6d6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack1JB96HKs8LawXS6GpGSOolw1R7QAEEtGw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5146; t=1224783346;
	x=1225647346; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVEcharter |Sender:=20;
	bh=vxAbm5XC2AOivPfJrZn2MMzd5MjeKxmnn9PLN8UTPRk=;
	b=WuqOGxnXmPv9DvlAoVVcpYvHFguHaypfA4k04VjWbtvqP3j2U/knCU6mGE
	5VeWyIvI53rDFFpbkam2c7uxP5j8xTxd9fZE8kLqbvR5k7/iPYE+cLBA5pas
	yjijmMVIQ+;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

 

> -----Original Message-----
> From: v4v6interim-bounces@ietf.org 
> [mailto:v4v6interim-bounces@ietf.org] On Behalf Of Margaret Wasserman
> Sent: Thursday, October 23, 2008 8:28 AM
> To: Mark Townsley
> Cc: v4v6interim@ietf.org; 46Translation; Behave WG
> Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal 
> for new BEHAVEcharter
> 
> 
> I'm getting mixed messages here, but I have a proposal...
> 
> Perhaps I could finish the NAT66 draft I've already started, and  
> submit it before the -00 cut-off (on Monday).
> 
> I think we all agree that NAT66 is not part of the 46translation  
> effort and the chair of behave has indicated that it is not in scope  
> for behave, so I'll stop cc:ing those groups on my messages 
> about it.  

BEHAVE is being re-chartered, so if the community wants BEHAVE to
do NAT66, now is a good time to tell the IESG to include NAT66 in 
BEHAVE's charter.  (as you all know.)  The new charter, at this
time, does not include NAT66.

And I only stated my desire to avoid the 'third rail'; the IESG can 
certainly decide they want NAT66 standardized.  Based on my 
understanding of how NAT66 would work, it would belong in BEHAVE.

> When the draft comes out, I will send a pointer to intarea 
> and ask for feedback.
> 
> If Jari and Mark are willing to give me a slot, we could talk about  
> the draft at the intarea meeting in Minneapolis.  If there is enough  
> interest in NAT66 that it makes sense to continue working on the  
> draft, I will.
>
> Even if it takes a while for us to get the NAT66 document 
> published as  
> an RFC, we'll have a reasonably well-reviewed draft available in the  
> meantime that may help people who start working on NAT66  
> implementations to make good design choices.
> 
> Does that make sense?

Yes, makes sense.

-d

> Margaret
> 
> 
> On Oct 23, 2008, at 10:50 AM, Mark Townsley wrote:
> 
> > Magnus Westerlund wrote:
> >> Anyway,
> >>
> >> Are anyone that thinks that NAT66 is so important that it takes
> >> precedence over the NAT46 translator work? If not, can we 
> postpone  
> >> this
> >> until we are ready to publish something on address family  
> >> translators?
> >>
> >> The reason I ask the above is that we will have enough 
> work for all  
> >> the
> >> people in the translator work. Thus trying to avoid splitting the  
> >> forces
> >> to thinly.
> >>
> > The NAT66 should be relatively straightforward, and could actually  
> > help highlight some of the reasons why 46 and 64 become 
> problematic.  
> > NAT66 is a question that comes up again and again when 
> talking about  
> > deploying IPv6, and I honestly think it would be useful to have a  
> > document to point to that brought light to and articulated some of  
> > the issues, gave strong warning where necessary, and 
> described what  
> > was relatively safe and what not.
> >
> > It doesn't really have to be part of behave though.  
> Magnus, I fully  
> > understand if you are looking at this new behave charter and can't  
> > imagine another thing on your plate. As Margaret and others  
> > mentioned, this can go through int-area, 6man, or some such.
> >
> > - Mark
> >> Magnus
> >>
> >> Iljitsch van Beijnum skrev:
> >>
> >>> On 21 okt 2008, at 11:50, Fred Baker wrote:
> >>>
> >>>
> >>>> As to the rest of what you said, I'll agree with you 
> that in a very
> >>>> real sense that ship has sailed, and I'll point out that 
> we run the
> >>>> same protocols on IPv6 that we run on IPv4. If we have indeed  
> >>>> made the
> >>>> protocols NAT-accepting for IPv4, I'll bet they are 
> NAT-accepting  
> >>>> on
> >>>> IPv6 as well.
> >>>>
> >>> If only things were this simple.
> >>>
> >>> Many apps that break with NAT do referrals by IP address. 
> So they  
> >>> must
> >>> be updated to work with IPv6, and gain significant additional  
> >>> logic to
> >>> work in a dual stack world. Things like STUN and ICE and their
> >>> proprietary counterparts thus need to be reinvented/implemented  
> >>> for v6
> >>> to make referrals work, and/or the UPnP/NAT-PMP protocols that  
> >>> open up
> >>> ports in NAT devices must be recreated for IPv6 if port 
> overloading
> >>> NAT66s happen.
> >>>
> >>> Today the routing people are complaining that the IPv6 builders  
> >>> didn't
> >>> fix routing. I wonder if in 10 years the apps people are going to
> >>> complain that we didn't fix NAT but just let the same 
> thing happen  
> >>> as in
> >>> IPv4 which BEHAVE has been trying to clean up.
> >>> _______________________________________________
> >>> Behave mailing list
> >>> Behave@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/behave
> >>>
> >>>
> >>
> >>
> >>
> >
> > _______________________________________________
> > v4v6interim mailing list
> > v4v6interim@ietf.org
> > https://www.ietf.org/mailman/listinfo/v4v6interim
> 
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 10:38:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD6EF3A697F;
	Thu, 23 Oct 2008 10:38:18 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E0103A697F
	for <v4v6interim@core3.amsl.com>; Thu, 23 Oct 2008 10:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5
	tests=[AWL=-0.372, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id giQFIiytOYid for <v4v6interim@core3.amsl.com>;
	Thu, 23 Oct 2008 10:38:18 -0700 (PDT)
Received: from QMTA06.westchester.pa.mail.comcast.net
	(qmta06.westchester.pa.mail.comcast.net [76.96.62.56])
	by core3.amsl.com (Postfix) with ESMTP id 280743A684D
	for <v4v6interim@ietf.org>; Thu, 23 Oct 2008 10:38:15 -0700 (PDT)
Received: from OMTA08.westchester.pa.mail.comcast.net ([76.96.62.12])
	by QMTA06.westchester.pa.mail.comcast.net with comcast
	id WHCr1a00f0Fqzac56HfD0B; Thu, 23 Oct 2008 17:39:13 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA08.westchester.pa.mail.comcast.net with comcast
	id WHf81a0091cMU3H3UHfAL2; Thu, 23 Oct 2008 17:39:24 +0000
X-Authority-Analysis: v=1.0 c=1 a=El3q9mXlNU8A:10 a=9ER3-GguvdgA:10
	a=WimRKRdZh2UhipNIl1wA:9 a=F7o7dGMhEbDOAcbZc-cA:7
	a=wLDca5O2SCctdisK0225KAuiukYA:4 a=MxZ3bB5I4kYA:10
Message-Id: <1DBE5796-E33C-4D1A-81CE-672E03F8D6D5@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 13:39:05 -0400
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> If #2 does not remind you of how we got into so much trouble nat44,  
> well it should. Because of the impact on NAT66 on applications, if  
> IETF does decide to do NAT66 specifications, I think it is very  
> important that the specification is developed not only in the  
> context of v6ops people but is also developed with input of folks  
> from applications that need to use it. Today that would roughly mean  
> behave.

I agree with you that NAT66 could (and probably would) have impact on  
other layers, so this problem is not specific to any one area.  I also  
share your concerns about working on NAT66 within v6ops or any other  
IPv6-specific WG, because we may get a solution that has unknown or  
unacceptable impact on applications.

I agree that the behave WG would be the best forum for this work,  
which is why I have suggested adding NAT66 to the behave charter while  
it is currently in the process of being updated.  Several people  
expressed interest in this work, but Dan Wing, who is one of the  
behave chairs, indicated that he considers NAT66 to be a political  
"third rail" and that he doesn't want to go there.  Magnus, one of the  
transport ADs, said that he sees "some interest" interest in NAT66,  
but that it is not a priority item.  He wants to finish "the important  
things first" before using resources to discuss NAT66.

I consider NAT66 to be an important and timely topic. So, I'm trying  
to figure out a way that we can make some progress on a NAT66 document  
in some other forum.  I'd be happy to bring it to behave when the  
current work has been completed, but that's likely to take quite a  
while, and I'm hoping we can make some progress on NAT66 in the  
meantime.

Do you think it would be better to just wait until behave finishes its  
current work and is ready to recharter again?

Margaret


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 10:40:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E9F903A6A1D;
	Thu, 23 Oct 2008 10:40:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90D2E3A6A2C
	for <v4v6interim@core3.amsl.com>; Thu, 23 Oct 2008 10:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level: 
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5
	tests=[AWL=-0.058, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Zgl8tEtNg4Dc for <v4v6interim@core3.amsl.com>;
	Thu, 23 Oct 2008 10:40:27 -0700 (PDT)
Received: from QMTA04.westchester.pa.mail.comcast.net
	(qmta04.westchester.pa.mail.comcast.net [76.96.62.40])
	by core3.amsl.com (Postfix) with ESMTP id 8C2D83A6A29
	for <v4v6interim@ietf.org>; Thu, 23 Oct 2008 10:40:27 -0700 (PDT)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA04.westchester.pa.mail.comcast.net with comcast
	id WE1j1a00P16LCl054HhlBe; Thu, 23 Oct 2008 17:41:45 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA06.westchester.pa.mail.comcast.net with comcast
	id WHhS1a00L1cMU3H3SHhVMa; Thu, 23 Oct 2008 17:41:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=_eXVZI6L6acA:10 a=9ER3-GguvdgA:10
	a=kwpamV_MTCDU6jv9GRsA:9 a=LEXJXwaLF0AGC5r4gHiPw9mOZccA:4
	a=WuK_CZDBSqoA:10
Message-Id: <4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <031d01c93535$c85b1140$9d6d6b80@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 13:41:24 -0400
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com><49008B8E.9080408@ericsson.com>
	<49008F1E.3010804@cisco.com>
	<EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
	<031d01c93535$c85b1140$9d6d6b80@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 23, 2008, at 1:35 PM, Dan Wing wrote:
> BEHAVE is being re-chartered, so if the community wants BEHAVE to
> do NAT66, now is a good time to tell the IESG to include NAT66 in
> BEHAVE's charter.  (as you all know.)  The new charter, at this
> time, does not include NAT66.
>
> And I only stated my desire to avoid the 'third rail'; the IESG can
> certainly decide they want NAT66 standardized.  Based on my
> understanding of how NAT66 would work, it would belong in BEHAVE.

Thanks, Dan.  This is very reasonable.

So, what's the best way forward?  Perhaps I could write a draft, sent  
a pointer to behave, and we could have a discussion over the next  
couple of weeks about whether the community does/doesn't want to  
include this in the new behave charter?

Margaret

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 10:46:09 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B16F93A6AC5;
	Thu, 23 Oct 2008 10:46:09 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 160E93A6AB1;
	Thu, 23 Oct 2008 10:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vJaHWtmXk3cP; Thu, 23 Oct 2008 10:46:04 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id D2C843A6A96;
	Thu, 23 Oct 2008 10:45:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="95236093"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 23 Oct 2008 17:47:07 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NHl7aE031980; 
	Thu, 23 Oct 2008 10:47:07 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9NHl7GT015415;
	Thu, 23 Oct 2008 17:47:07 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Margaret Wasserman'" <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com><49008B8E.9080408@ericsson.com>
	<49008F1E.3010804@cisco.com>
	<EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
	<031d01c93535$c85b1140$9d6d6b80@cisco.com>
	<4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
Date: Thu, 23 Oct 2008 10:47:06 -0700
Message-ID: <036801c93537$5dc254e0$9d6d6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack1NqDb6kA1/p1zTMuZjq83poHN4QAAIHfQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=865; t=1224784027; x=1225648027;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[BEHAVE]=20[v4v6interim]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVEcharter |Sender:=20;
	bh=pzFS4uvW74FZLQ6f/87NONtMgjOLevsyNiYlGQu9/WE=;
	b=K+pQlCtx6sy2FHXgV8+LvScLTdELltrnncKSBnkBHjkkLSnkbN4aFdYdIo
	FsxYPCTrfRCcG2N3RK9hyPnaSmVil20qRhPeF2ojY8hEGcY/UPYDEp+gzWnn
	LEVzvh+oNX2U+BXiI8jYYfYgkC+X5hD1CqsdFNuMT6ITqWpgSrQc0=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

> On Oct 23, 2008, at 1:35 PM, Dan Wing wrote:
> > BEHAVE is being re-chartered, so if the community wants BEHAVE to
> > do NAT66, now is a good time to tell the IESG to include NAT66 in
> > BEHAVE's charter.  (as you all know.)  The new charter, at this
> > time, does not include NAT66.
> >
> > And I only stated my desire to avoid the 'third rail'; the IESG can
> > certainly decide they want NAT66 standardized.  Based on my
> > understanding of how NAT66 would work, it would belong in BEHAVE.
> 
> Thanks, Dan.  This is very reasonable.
> 
> So, what's the best way forward?  Perhaps I could write a 
> draft, sent  
> a pointer to behave, and we could have a discussion over the next  
> couple of weeks about whether the community does/doesn't want to  
> include this in the new behave charter?

Yes, that would be ideal.  Thanks!

-d

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 10:48:32 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C6BE28C0FC;
	Thu, 23 Oct 2008 10:48:32 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC5603A6AA8;
	Thu, 23 Oct 2008 10:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level: 
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zNrnlscjdJGY; Thu, 23 Oct 2008 10:48:30 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 40F803A6AB2;
	Thu, 23 Oct 2008 10:48:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="23556265"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 23 Oct 2008 17:49:43 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NHnhbp016716; 
	Thu, 23 Oct 2008 19:49:43 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NHhZPW010352;
	Thu, 23 Oct 2008 17:49:43 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 19:49:11 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 19:49:11 +0200
Message-ID: <4900B914.1050908@cisco.com>
Date: Thu, 23 Oct 2008 19:49:08 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com><49008B8E.9080408@ericsson.com>
	<49008F1E.3010804@cisco.com>
	<EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
	<031d01c93535$c85b1140$9d6d6b80@cisco.com>
	<4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
	<036801c93537$5dc254e0$9d6d6b80@cisco.com>
In-Reply-To: <036801c93537$5dc254e0$9d6d6b80@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 17:49:11.0373 (UTC)
	FILETIME=[A7EF6FD0:01C93537]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=969; t=1224784183; x=1225648183;
	c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[v4v6interim]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVEcharter |Sender:=20;
	bh=2vJIkwNYJhDZ+OKDhUy1700XBKbjH3qFmVjchnN+lUc=;
	b=KImWNNiyPG2L2SlEZo+xWJpWzynYjTCDszw0iaw4iB/Rgqu68fTrDPVTHR
	/0yWwAsZQTm87Ls6laLpQvbrPZRygoqSt176ei7Y1x4ee0gYvxwosCffGagh
	L7Jlc8kJNY;
Authentication-Results: ams-dkim-2; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Dan Wing wrote:
>> On Oct 23, 2008, at 1:35 PM, Dan Wing wrote:
>>     
>>> BEHAVE is being re-chartered, so if the community wants BEHAVE to
>>> do NAT66, now is a good time to tell the IESG to include NAT66 in
>>> BEHAVE's charter.  (as you all know.)  The new charter, at this
>>> time, does not include NAT66.
>>>
>>> And I only stated my desire to avoid the 'third rail'; the IESG can
>>> certainly decide they want NAT66 standardized.  Based on my
>>> understanding of how NAT66 would work, it would belong in BEHAVE.
>>>       
>> Thanks, Dan.  This is very reasonable.
>>
>> So, what's the best way forward?  Perhaps I could write a 
>> draft, sent  
>> a pointer to behave, and we could have a discussion over the next  
>> couple of weeks about whether the community does/doesn't want to  
>> include this in the new behave charter?
>>     
>
> Yes, that would be ideal.  Thanks!
>   
Works for me as well.

- Mark
> -d
>
>
>   

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 14:12:26 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 469BF3A6993;
	Thu, 23 Oct 2008 14:12:26 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D00A3A68E1;
	Thu, 23 Oct 2008 14:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5So6u+PYwyJa; Thu, 23 Oct 2008 14:12:24 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 255FD3A6993;
	Thu, 23 Oct 2008 14:12:23 -0700 (PDT)
Received: from [192.168.0.195] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9NLD4Ad068411
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 23 Oct 2008 23:13:05 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E29AD07F-8C2A-4FC3-B676-E2C64C7281F7@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Alain Durand <alain_durand@cable.comcast.com>
In-Reply-To: <C526256B.1C487%alain_durand@cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 23:13:23 +0200
References: <C526256B.1C487%alain_durand@cable.comcast.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 23 okt 2008, at 18:58, Alain Durand wrote:

> IPv6 is just like IPv4 with longer addresses. This is where deployment
> reality trumps architectural purity.

Disagree. Two reasons:

1. The longer addresses don't just make a quantitative difference, but  
also a qualitative difference. Things like SEND, HIP and shim6 aren't  
possible with IPv4 because they put crypto stuff in spare address  
bits. Things like port overloading NAT aren't necessary in IPv6  
because there is abundant address space.

2. If we don't use the opportunity that IPv6 gives us to fix some of  
the brokennes of the current IPv4 internet, we're not going to get  
another chance any time soon. If we use IPv6 just like IPv4 we might  
as well stay with IPv4. We know that with enough NAT it actually is  
possible to squeeze blood from stones.

> What I've seen in the last 3 years is that it is much, much easier  
> to deploy
> IPv6 if you keep the exact same operational model as in IPv4.

But then we've gained nothing.

> Many folks are considering NAT44 as a simple solution where they  
> just have
> to put a box in front of their network to make whatever problem they  
> think
> they have go away. I can easily see that the same people would like  
> to do
> the same thing with IPv6. Which exact problem they were solving is
> irrelevant to this discussion, the point is about preserving the same
> operational model.

Let me try a more opportunistic argument on you: in IPv4, you can't be  
pedantic because then you're disconnected. With IPv6, you can not  
route, filter, break whatever you don't like and the offending party  
then falls back on IPv4 so you still have connectivity. For this  
reason, it's very likely that there will be a lot more operational  
hard ball with (perceived) architectural purity with IPv6. This means  
that the perfect storm of different kinds of users that all saw NAT as  
a solution to their problem and thus required application makers to  
work around NAT won't happen with IPv6, and the onus of implementing  
the workarounds will fall solely on the party implementing the NAT for  
a very long time to come. This is of course often impossible with a  
port overloading NAT so a lot of things that work with IPv4+NAT will  
fail with IPv6+NAT.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 14:37:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC11628C111;
	Thu, 23 Oct 2008 14:37:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E4143A686E;
	Thu, 23 Oct 2008 14:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LlWmmzyZRM0U; Thu, 23 Oct 2008 14:37:40 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id C5FC43A67A3;
	Thu, 23 Oct 2008 14:37:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,472,1220227200"; d="scan'208";a="31673729"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163])
	by ind-iport-1.cisco.com with ESMTP; 23 Oct 2008 21:38:53 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NLcqkn032286; 
	Fri, 24 Oct 2008 05:38:52 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com
	[64.104.123.72])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NLcqI2001726;
	Thu, 23 Oct 2008 21:38:52 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by
	xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 05:38:52 +0800
Received: from [192.168.100.101] ([10.75.234.250]) by
	xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 05:38:51 +0800
Message-Id: <C78E443E-054A-4F0C-B6D0-C8D7DDE34B47@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <49008F1E.3010804@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 05:38:51 +0800
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 23 Oct 2008 21:38:51.0811 (UTC)
	FILETIME=[BDB76730:01C93557]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=734; t=1224797932; x=1225661932;
	c=relaxed/simple; s=hkgdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=+aZROEPC7gKWO+WNFqiRpxUBJvARsbqWyJtAtI0I4oU=;
	b=L3S5I13kMUScRDFNVRorjZG8XwxI4IipZl2YwfZdavJA8R0V9lYA0bqenm
	L8kp2sXB8fH7AAu6KMdgAAvk/W/D8HWCYKxS3HrSuCN6TXkAy4/w/rMut0LG
	af5QR/scpPDzLnAarm/AtyqBIpkXs/JC8HSqx4iBgH/v5A3P73Fek=;
Authentication-Results: hkg-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim2001 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 23, 2008, at 10:50 PM, Mark Townsley wrote:

> The NAT66 should be relatively straightforward, and could actually  
> help highlight some of the reasons why 46 and 64 become problematic.  
> NAT66 is a question that comes up again and again when talking about  
> deploying IPv6, and I honestly think it would be useful to have a  
> document to point to that brought light to and articulated some of  
> the issues, gave strong warning where necessary, and described what  
> was relatively safe and what not.
>
> It doesn't really have to be part of behave though.

I actually think i should be in behave; they have the expertise. But I  
would agree with Magnus that it is a next step, not the current step.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Thu Oct 23 23:09:25 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 903B63A691E;
	Thu, 23 Oct 2008 23:09:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E07F43A6358;
	Thu, 23 Oct 2008 23:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nCpfbi++sYeW; Thu, 23 Oct 2008 23:09:23 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id CB5443A689F;
	Thu, 23 Oct 2008 23:09:22 -0700 (PDT)
Received: from [192.168.0.195] (static-167-138-7-89.ipcom.comunitel.net
	[89.7.138.167] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9O6A4Sn076306
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 08:10:05 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <36D6478D-4C43-4517-92B5-FA1ECCA94EA7@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 08:10:24 +0200
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 23 okt 2008, at 18:06, Cullen Jennings wrote:

> If you want to be able hide that two uncorrelated sessions are  
> actually coming from the same internal host, well, I'm not sure I  
> see how to do this with 1:1 mappings.

Here's how:

For every new session, the NAT66 box creates a new 1-to-1 maping. So  
for every new session it must choose a new address from a pool map  
that address to the internal source address of the host in question.  
As long as the external addresses checksum to the same value as the  
internal address, the transports that use the normal checksum over the  
pseudo header are happy and don't have to be modified by the  
translator. In IPv6 sessions can of course be identified by the flow  
label so this will work for transports that the translator doesn't  
know. Since the mappings are 1-to-1, incoming sessions can still work  
with help from STUN. The translator does need to keep and time out  
state for translation mappings, though.

This will burn through very many addresses, but even with the checksum  
restriction this shouldn't be much of a problem if the translator  
"owns" a reasonable size prefix, i.e. the prefix is routed to the  
translator so no neighbor discovery is necessary. This kind of  
obfuscation would work really well with a very large prefix and very  
many hosts, such as a /48 for a large site, although in that case the  
state maintenance could be an issue.

There is still the issue that hosts can be recognized by the value  
that the addresses checksum to, but this can be solved by aggressively  
using RFC 3041 or by assigning all hosts checksum-equivalent addresses  
using DHCPv6.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 02:09:33 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 180C03A68D1;
	Fri, 24 Oct 2008 02:09:33 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 193013A6810;
	Fri, 24 Oct 2008 02:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vcVcJ0F3BMZR; Fri, 24 Oct 2008 02:09:31 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 3AE8D3A6A6F;
	Fri, 24 Oct 2008 02:09:31 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9O99wxo002946; Fri, 24 Oct 2008 04:10:47 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 12:10:44 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 12:10:43 +0300
Received: from esdhcp04094.research.nokia.com ([172.21.40.94]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 12:10:43 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: v4v6interim@ietf.org
Date: Fri, 24 Oct 2008 12:10:45 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com> <49009C8B.80707@cisco.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
In-Reply-To: <A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241210.46374.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 09:10:43.0294 (UTC)
	FILETIME=[647D07E0:01C935B8]
X-Nokia-AV: Clean
Cc: 46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thursday 23 October 2008 19:06:52 ext Cullen Jennings, you wrote:
> If the mapping was purely and 1:1 mapping between internal and
> external IPs I would agree with you but unfortunately, I worry that
> meeting the requirement that drive section 4.4 of 4864 (privacy and
> topology hiding) really complicate trying to do it with 1:1 mapping at
> IP level.
>
> If you want to be able hide that two uncorrelated sessions are
> actually coming from the same internal host, well, I'm not sure I see
> how to do this with 1:1 mappings. One might argue that one should
> ignore these requirements but this is one of key areas where some
> people feel that 4864 has limitations that drive the deployment of
> NAT66. Two solutions I have seen for this are
> a) different external IP for every internal flow

This is unlikely to be deployed. It breaks to many applications that work f=
ine =

with NATs (e.g. many web apps tie their "session" to the client IP address).

> b) doing port address translation similar to =

> NAPT in NAT44. Either of these choices has some pretty substantial
> impacts on how to make applications like VoIP work.

I don't think there's a strong requirement to hide correlation (or rather, =

lack thereof) between VoIP sessions - human user being the bottleneck in ho=
w =

many VoIP sessions a system can have.

But most importantly, I doubt that people who are this paranoid about topol=
ogy =

hiding would tolerate using STUN, or any other server-reflexive address =

learning for that matter. But hey, you must know the SIP privacy work bette=
r =

than I do :) IIRC, it's proxy-based (TURN).

Therefore I am not convinced that 1:1 mapping would be a problem.
However, and to answer Alain's point, yes, some vendors will ship NAT66 box=
es =

that work exactly like NAT44. But these will be no more BEHAVE-compliant th=
an =

the NAT44 boxes. So it's kind of a non-issue from a standardization =

perspective - I tend to think that there is no problem if there is no =

solution.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 02:15:42 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC5C228C169;
	Fri, 24 Oct 2008 02:15:42 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E86FA28C152;
	Fri, 24 Oct 2008 02:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rwzWFOrkvQyq; Fri, 24 Oct 2008 02:15:41 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 0FE2028C169;
	Fri, 24 Oct 2008 02:15:18 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9O9G4PG010560; Fri, 24 Oct 2008 12:16:32 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 12:16:04 +0300
Received: from esdhcp04094.research.nokia.com ([172.21.40.94]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 12:16:03 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: v4v6interim@ietf.org
Date: Fri, 24 Oct 2008 12:16:06 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
	<36D6478D-4C43-4517-92B5-FA1ECCA94EA7@muada.com>
In-Reply-To: <36D6478D-4C43-4517-92B5-FA1ECCA94EA7@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241216.06565.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 09:16:03.0370 (UTC)
	FILETIME=[2344C0A0:01C935B9]
X-Nokia-AV: Clean
Cc: Behave WG <behave@ietf.org>, 46Translation <46translation@employees.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Friday 24 October 2008 09:10:24 ext Iljitsch van Beijnum, you wrote:
> For every new session, the NAT66 box creates a new 1-to-1 maping. So
> for every new session it must choose a new address from a pool map
> that address to the internal source address of the host in question.
> As long as the external addresses checksum to the same value as the
> internal address, the transports that use the normal checksum over the
> pseudo header are happy and don't have to be modified by the
> translator. In IPv6 sessions can of course be identified by the flow
> label so this will work for transports that the translator doesn't
> know. Since the mappings are 1-to-1, incoming sessions can still work
> with help from STUN. The translator does need to keep and time out
> state for translation mappings, though.

Yes.

> This will burn through very many addresses,

Not necessarily. You only need as many addresses as you have hosts. A =

single /64 would be sufficient for any single NAT. You only need a large =

address space if you want STATELESS mappings.

> but even with the checksum =

> restriction this shouldn't be much of a problem if the translator
> "owns" a reasonable size prefix, i.e. the prefix is routed to the
> translator so no neighbor discovery is necessary. This kind of
> obfuscation would work really well with a very large prefix and very
> many hosts, such as a /48 for a large site, although in that case the
> state maintenance could be an issue.

I don't think it's an issue. This is still less state (one mapping per host=
) =

than contemporary NAT44 (one mapping per flow).

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 02:33:27 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6C9F28C133;
	Fri, 24 Oct 2008 02:33:27 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 92EFC28C12E;
	Fri, 24 Oct 2008 02:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.138
X-Spam-Level: 
X-Spam-Status: No, score=-6.138 tagged_above=-999 required=5 tests=[AWL=0.111, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OTHo9ZOeQAmO; Fri, 24 Oct 2008 02:33:25 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 6D97E28C0E3;
	Fri, 24 Oct 2008 02:33:25 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	815E520F12; Fri, 24 Oct 2008 11:34:45 +0200 (CEST)
X-AuditID: c1b4fb3c-aa8c7bb0000015b5-cd-490196b59fcc
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4B23820DF9; Fri, 24 Oct 2008 11:34:45 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 11:34:44 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 11:34:44 +0200
Message-ID: <490196B4.3080907@ericsson.com>
Date: Fri, 24 Oct 2008 11:34:44 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<1DBE5796-E33C-4D1A-81CE-672E03F8D6D5@lilacglade.org>
In-Reply-To: <1DBE5796-E33C-4D1A-81CE-672E03F8D6D5@lilacglade.org>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 24 Oct 2008 09:34:44.0792 (UTC)
	FILETIME=[BFB02B80:01C935BB]
X-Brightmail-Tracker: AAAAAA==
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Margaret Wasserman skrev:
> I agree that the behave WG would be the best forum for this work, which
> is why I have suggested adding NAT66 to the behave charter while it is
> currently in the process of being updated.  Several people expressed
> interest in this work, but Dan Wing, who is one of the behave chairs,
> indicated that he considers NAT66 to be a political "third rail" and
> that he doesn't want to go there.  Magnus, one of the transport ADs,
> said that he sees "some interest" interest in NAT66, but that it is not
> a priority item.  He wants to finish "the important things first" before
> using resources to discuss NAT66.
> =

> I consider NAT66 to be an important and timely topic. So, I'm trying to
> figure out a way that we can make some progress on a NAT66 document in
> some other forum.  I'd be happy to bring it to behave when the current
> work has been completed, but that's likely to take quite a while, and
> I'm hoping we can make some progress on NAT66 in the meantime.

Margaret,

I am pushing back a bit to see if there actually are sufficient interest
in this. I definitely think you should try to write up your document so
that the community have something to discuss around. So far we have a
couple of people that definitely have views on this.

In regards to BEHAVE charter, if we actually have come to good enough
conclusions about what NAT66 really should do within a week or so, then
I don't see a problem with adding it to BEHAVE charter. However, BEHAVE
may not be the right home depending on what is to be done. If we haven't
come to good enough conclusions, I still plan to go forward with the
current proposed re-charter. I have no issues to do a another recharter
in a month or two. We do have a few other components in the co-existence
puzzle that may land in BEHAVE. So I am expecting to do another
recharter within the next couple of months.

But please go forward and continue to discuss this topic on the BEHAVE
list.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 02:55:32 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFEA53A6A71;
	Fri, 24 Oct 2008 02:55:32 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F8D83A6844;
	Fri, 24 Oct 2008 02:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5
	tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jeeMXLt68d5D; Fri, 24 Oct 2008 02:55:31 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 776713A6A0F;
	Fri, 24 Oct 2008 02:55:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,476,1220227200"; d="scan'208";a="23616143"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 24 Oct 2008 09:56:43 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9O9uht5012708; 
	Fri, 24 Oct 2008 11:56:43 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9O9uhRV008236;
	Fri, 24 Oct 2008 09:56:43 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 11:56:43 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 11:56:43 +0200
Message-ID: <49019BD9.4010005@cisco.com>
Date: Fri, 24 Oct 2008 11:56:41 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>
	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
	<alpine.LRH.2.00.0810241218190.1106@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0810241218190.1106@netcore.fi>
X-OriginalArrivalTime: 24 Oct 2008 09:56:43.0156 (UTC)
	FILETIME=[D17E8D40:01C935BE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2188; t=1224842203;
	x=1225706203; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[v4v6interim]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=6NpRYGOrl98K/j03lh/r0O297w2BJo55ZkRXGCJuqmk=;
	b=DOtGp44KhGfmMe140oZN/1bBUqxb4zau5+7pAI4Fuwx+P0AoqRVlv64uRq
	7c6VLvUFhmEQ4Kg5D2VxZuFm6CcyXK2MPAeh8UDMMYZCCqSjvdgJiJ2geU6A
	k66v8WqPGN;
Authentication-Results: ams-dkim-2; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Pekka Savola wrote:
> On Thu, 23 Oct 2008, Mark Townsley wrote:
>>>  If #2 does not remind you of how we got into so much trouble nat44, 
>>> well
>>>  it should. Because of the impact on NAT66 on applications, if IETF 
>>> does
>>>  decide to do NAT66 specifications, I think it is very important 
>>> that the
>>>  specification is developed not only in the context of v6ops people 
>>> but is
>>>  also developed with input of folks from applications that need to 
>>> use it.
>>>  Today that would roughly mean behave.
>>
>> I think that something that operates only at the IP layer could stay 
>> in the int-area.
>
> But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.) 
> that's broken today with NAT4 (with or without port translation) 
> unless the NAT has ALGs.  To implement such ALGs, NAT66 would need to 
> operate beyond the IP layer.
Of course, anything that IP does affects things above and below. By this 
argument we could collapse whole portions of int area into transport or 
vice-versa (which may be a fait accomplis anyhow, but I digress).

All of these translator things cross layer boundaries. My argument is, 
simply, that if any of it could land on the int area side, a strictly 
1:1 NAT might be the most likely candidate. Remember also, this was in 
response also to Magnus raising his arms overhead and looking for a 
liferaft amidst the new work behave already has. Honestly, if he is 
willing to take it on in behave, that's perfectly fine with me as long 
as it receives enough attention from int-area folks. I'm far less 
concerned about that last issue right now than I was, say, 6 months or 
so ago when we first started talking about bringing IPv6 translation 
into behave.

This discussion has already gotten ahead of itself though. Let's get the 
-00 out, discuss it where best we can find the time and cycles, and then 
decide where (and if) it should land as chartered work. Margaret asked 
for a slot in int-area, perhaps there will be time in behave as well, so 
for the moment some of you might see this discussed twice - as is the 
case often with work that is yet unchartered.

- Mark

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 03:00:18 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 001D63A6949;
	Fri, 24 Oct 2008 03:00:17 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E03B23A68E5;
	Fri, 24 Oct 2008 03:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bhVMXXSnv584; Fri, 24 Oct 2008 03:00:16 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 8BF663A6A58;
	Fri, 24 Oct 2008 03:00:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,476,1220227200"; d="scan'208";a="23617155"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 24 Oct 2008 10:01:36 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OA1Zvl019539; 
	Fri, 24 Oct 2008 12:01:35 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9OA1Zm6010613;
	Fri, 24 Oct 2008 10:01:35 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 12:01:35 +0200
Received: from ams-townsley-8711.cisco.com ([10.55.233.226]) by
	xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 12:01:33 +0200
Message-ID: <49019CE6.6070605@cisco.com>
Date: Fri, 24 Oct 2008 12:01:10 +0200
From: Mark Townsley <townsley@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<1DBE5796-E33C-4D1A-81CE-672E03F8D6D5@lilacglade.org>
	<490196B4.3080907@ericsson.com>
In-Reply-To: <490196B4.3080907@ericsson.com>
X-OriginalArrivalTime: 24 Oct 2008 10:01:33.0803 (UTC)
	FILETIME=[7EBBC3B0:01C935BF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=915; t=1224842495; x=1225706495;
	c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=townsley@cisco.com;
	z=From:=20Mark=20Townsley=20<townsley@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[v4v6interim]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=0A=20charter |Sender:=20;
	bh=iVyVBaZubESb2TisFMDSvpgJpVu1xfwhzGS9UNcyjr4=;
	b=MyCctm+KBnFBDCtudEF1anoGIdpZ90A5ZrJn2OnEBCBR8v1PrINu7Ml/aE
	OA2ITY07nXhNgLei6IiZMbBlx7SbT/sfdP5vlO3fEB5I8tchZ8d7dgPa7Vve
	gvJOYo/Pgy;
Authentication-Results: ams-dkim-1; header.From=townsley@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Magnus Westerlund wrote:
> But please go forward and continue to discuss this topic on the BEHAVE
> list.
>   =

No issue at all there, all NAT66 email discussion in one place, the =

behave list, is perfectly fine with me. Much better than chasing =

crossposts. I do hope that behave is seeing a lot of new membership from =

int-area folks these days though.

- Mark
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone +46 8 4048287
> F=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>   =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 03:08:53 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F33AA3A6A75;
	Fri, 24 Oct 2008 03:08:52 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6C693A69B2;
	Fri, 24 Oct 2008 03:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.184
X-Spam-Level: 
X-Spam-Status: No, score=-5.184 tagged_above=-999 required=5
	tests=[AWL=-1.115, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OQNMvo+078fr; Fri, 24 Oct 2008 03:08:51 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id B41613A6949;
	Fri, 24 Oct 2008 03:08:50 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9OA9uLF029715; Fri, 24 Oct 2008 13:10:05 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 13:09:56 +0300
Received: from esdhcp04094.research.nokia.com ([172.21.40.94]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 13:09:52 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Fri, 24 Oct 2008 13:09:55 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com> <49009C8B.80707@cisco.com>
	<alpine.LRH.2.00.0810241218190.1106@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0810241218190.1106@netcore.fi>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241309.55912.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 10:09:52.0669 (UTC)
	FILETIME=[A814ACD0:01C935C0]
X-Nokia-AV: Clean
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Friday 24 October 2008 12:20:51 ext Pekka Savola, you wrote:
> On Thu, 23 Oct 2008, Mark Townsley wrote:
> >>  If #2 does not remind you of how we got into so much trouble nat44,
> >> well it should. Because of the impact on NAT66 on applications, if IETF
> >> does decide to do NAT66 specifications, I think it is very important
> >> that the specification is developed not only in the context of v6ops
> >> people but is also developed with input of folks from applications that
> >> need to use it. Today that would roughly mean behave.
> >
> > I think that something that operates only at the IP layer could stay in
> > the int-area.
>
> But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.)
> that's broken today with NAT4 (with or without port translation)
> unless the NAT has ALGs.  To implement such ALGs, NAT66 would need to
> operate beyond the IP layer.

Not exactly. I know at least FTP/ESPV and RTSP would work as is through NAT=
66. =

I suspect many proprietary gaming protocol would end up there too. I'd like =

to know about CIFS and NFS.

FTP/EPRT is broken, also it could have been designed such that it would not =

have been (by making the remote address optional) :-( Also, for instance, S=
IP =

would be much easier to "fix" than with NAT44 + ICE, assuming you don't car=
e =

about IPv4 at all.


I assume Margaret plans to scope her I-D clearly such that the limitations =
are =

clearly stated and the reader is pointed to potential NAT-free alternative =

solutions (and especially to reading the IPv6 security RFC). I think we all =

know that NATs suck. The points are: 1/ NAPT sucks harder than pure NAT, an=
d =

2/ lets we IETFers not do the same mistake of ignoring NATs.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 04:21:49 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC97C28C156;
	Fri, 24 Oct 2008 04:21:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 969CB28C0E6;
	Fri, 24 Oct 2008 04:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.611
X-Spam-Level: 
X-Spam-Status: No, score=-1.611 tagged_above=-999 required=5
	tests=[AWL=-0.942, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	SARE_PROLOSTOCK_SYM3=1.63]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OwRFVoZzN+ca; Fri, 24 Oct 2008 04:21:47 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 8183028C0E3;
	Fri, 24 Oct 2008 04:21:47 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.51])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9OBMWV7081137
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 13:22:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?=
	<remi.denis-courmont@nokia.com>
In-Reply-To: <200810241309.55912.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 13:22:51 +0200
References: <48F8539D.90608@ericsson.com> <49009C8B.80707@cisco.com>
	<alpine.LRH.2.00.0810241218190.1106@netcore.fi>
	<200810241309.55912.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	behave@ietf.org, ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 24 okt 2008, at 12:09, R=E9mi Denis-Courmont wrote:

>> But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.)
>> that's broken today with NAT4 (with or without port translation)
>> unless the NAT has ALGs.  To implement such ALGs, NAT66 would need to
>> operate beyond the IP layer.

Or the clients must obtain their externally visible address and  =

present that in referrals. This is much preferable to ALGs.

Note that the stateful firewalls that are mandated for home use with  =

IPv6 also get in the way.

> FTP/EPRT is broken, also it could have been designed such that it  =

> would not
> have been (by making the remote address optional) :-(

That's what EPSV is for:

ftp> debug
Debugging on (debug=3D1).
ftp> ls
---> EPSV
229 Entering Extended Passive Mode (|||51239|)
---> LIST
150 Here comes the directory listing.

(Note that I was talking to the server over v4.)

On 24 okt 2008, at 11:16, R=E9mi Denis-Courmont wrote:

>> This will burn through very many addresses,

> Not necessarily. You only need as many addresses as you have hosts. A
> single /64 would be sufficient for any single NAT.

Our statements are not in opposition because a single /64 has very  =

many addresses.  :-)

> You only need a large
> address space if you want STATELESS mappings.

Wouldn't every internal address map to a single external address in  =

that case? That wouldn't use very many addresses. But if you need a  =

new address for every source address / flow label combo, things start  =

moving fast.

> I don't think it's an issue. This is still less state (one mapping  =

> per host)
> than contemporary NAT44 (one mapping per flow).

No, in this case we also do a mapping per flow, but the difference is  =

that we don't need to understand the transport to recognize flows  =

because we have the flow label, and because we use a different source  =

address per flow we don't need to recognize incoming packets by their  =

port numbers so referrals work. We also avoid touching the port  =

numbers and the checksums.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 04:42:51 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7FED3A6829;
	Fri, 24 Oct 2008 04:42:51 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51F3F3A6808;
	Fri, 24 Oct 2008 04:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.233
X-Spam-Level: 
X-Spam-Status: No, score=-6.233 tagged_above=-999 required=5 tests=[AWL=0.066, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZrOsSW8GSQ0r; Fri, 24 Oct 2008 04:42:49 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 3B2B13A6829;
	Fri, 24 Oct 2008 04:42:49 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9OBi44A021151; Fri, 24 Oct 2008 14:44:04 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 14:44:04 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 14:44:03 +0300
Received: from esdhcp04094.research.nokia.com ([172.21.40.94]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 14:44:03 +0300
From: "=?iso-8859-1?q?R=E9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: "ext Iljitsch van Beijnum" <iljitsch@muada.com>
Date: Fri, 24 Oct 2008 14:44:06 +0300
User-Agent: KMail/1.9.10
References: <48F8539D.90608@ericsson.com>
	<200810241309.55912.remi.denis-courmont@nokia.com>
	<E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>
In-Reply-To: <E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241444.06688.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 11:44:03.0676 (UTC)
	FILETIME=[D057E9C0:01C935CD]
X-Nokia-AV: Clean
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	behave@ietf.org, ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Friday 24 October 2008 14:22:51 ext Iljitsch van Beijnum, you wrote:
> > You only need a large
> > address space if you want STATELESS mappings.
>
> Wouldn't every internal address map to a single external address in
> that case? That wouldn't use very many addresses.

For stateless mapping, unless you have some extra assumptions about the =

internal addresses (e.g. only SLAAC EUI-48 are used, no static address, no =

privacy addresses), you need as large an external prefix as the internal on=
e.

> No, in this case we also do a mapping per flow, but the difference is
> that we don't need to understand the transport to recognize flows
> because we have the flow label, and because we use a different source
> address per flow we don't need to recognize incoming packets by their
> port numbers so referrals work.

NAT44 provide N:1 internal:external address mappings, not N:M. With N:M you =

will break applications that _do_ work with NAT44, including a very long ta=
il =

of HTTP-based applications. Making NAT66 worse than NAT44 is unlikely to fl=
y, =

even with those people who _do_ want to deploy NAT66.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 04:51:02 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58D353A69B2;
	Fri, 24 Oct 2008 04:51:02 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A04223A69D4;
	Fri, 24 Oct 2008 04:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5
	tests=[AWL=-0.079, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 435+4jWZEQMK; Fri, 24 Oct 2008 04:51:00 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id BD5503A6974;
	Fri, 24 Oct 2008 04:50:59 -0700 (PDT)
Received: from nirrti.it.uc3m.es (nirrti.it.uc3m.es [163.117.139.51])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9OBpgR6081617
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 13:51:51 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <372F2903-0116-45EF-87B0-304270667BBB@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?=
	<remi.denis-courmont@nokia.com>
In-Reply-To: <200810241444.06688.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 13:51:58 +0200
References: <48F8539D.90608@ericsson.com>
	<200810241309.55912.remi.denis-courmont@nokia.com>
	<E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>
	<200810241444.06688.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	behave@ietf.org, ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 24 okt 2008, at 13:44, R=E9mi Denis-Courmont wrote:

> NAT44 provide N:1 internal:external address mappings, not N:M. With  =

> N:M you
> will break applications that _do_ work with NAT44, including a very  =

> long tail
> of HTTP-based applications. Making NAT66 worse than NAT44 is  =

> unlikely to fly,
> even with those people who _do_ want to deploy NAT66.

If the load balancers ignore the bottom 64 bits there is no issue.

So I suggest we tell those vendors to do exactly that when they build  =

the IPv6 implementations of their products.
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 06:11:04 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54B7928C11F;
	Fri, 24 Oct 2008 06:11:04 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4347A3A6AD7;
	Fri, 24 Oct 2008 06:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.37
X-Spam-Level: 
X-Spam-Status: No, score=-6.37 tagged_above=-999 required=5 tests=[AWL=0.229, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WXCyJSfIU9WT; Fri, 24 Oct 2008 06:10:57 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7ob115.obsmtp.com [64.18.2.216])
	by core3.amsl.com (Postfix) with ESMTP id EE79F3A6B28;
	Fri, 24 Oct 2008 06:10:51 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob115.postini.com
	([64.18.6.12]) with SMTP; Fri, 24 Oct 2008 06:12:11 PDT
Received: from [172.23.10.9] ([172.23.10.9]) by p-emsmtp01.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Fri, 24 Oct 2008 06:09:22 -0700
Message-ID: <4901C8FB.80805@juniper.net>
Date: Fri, 24 Oct 2008 06:09:15 -0700
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <48F8539D.90608@ericsson.com>	<200810241309.55912.remi.denis-courmont@nokia.com>	<E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>	<200810241444.06688.remi.denis-courmont@nokia.com>
	<372F2903-0116-45EF-87B0-304270667BBB@muada.com>
In-Reply-To: <372F2903-0116-45EF-87B0-304270667BBB@muada.com>
X-OriginalArrivalTime: 24 Oct 2008 13:09:22.0492 (UTC)
	FILETIME=[BB653FC0:01C935D9]
Cc: behave@ietf.org, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>,
	ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Iljitsch,

IPv6 has been implemented years back.

Many production network are dual stack today or even running just pure =

v6. So with this in mind what are you proposing to tell the vendors reg =

hints for their upcoming implementations ???

Cheers,
R.

> On 24 okt 2008, at 13:44, R=E9mi Denis-Courmont wrote:
> =

>> NAT44 provide N:1 internal:external address mappings, not N:M. With =

>> N:M you
>> will break applications that _do_ work with NAT44, including a very =

>> long tail
>> of HTTP-based applications. Making NAT66 worse than NAT44 is unlikely =

>> to fly,
>> even with those people who _do_ want to deploy NAT66.
> =

> If the load balancers ignore the bottom 64 bits there is no issue.
> =

> So I suggest we tell those vendors to do exactly that when they build =

> the IPv6 implementations of their products.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =


_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 06:22:30 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CAD43A6B2E;
	Fri, 24 Oct 2008 06:22:30 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A60FC3A6B24;
	Fri, 24 Oct 2008 06:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mGIOx0NcZgRC; Fri, 24 Oct 2008 06:22:28 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id AE8253A6B22;
	Fri, 24 Oct 2008 06:22:27 -0700 (PDT)
Received: from [163.117.139.230] ([163.117.139.230]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m9ODNH8r082892
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 15:23:17 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <B94D8065-FF4B-4731-A04B-C31B4D86ACDC@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: raszuk@juniper.net
In-Reply-To: <4901C8FB.80805@juniper.net>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 15:23:36 +0200
References: <48F8539D.90608@ericsson.com>	<200810241309.55912.remi.denis-courmont@nokia.com>	<E1F09AB5-F343-4634-8CE9-B1C6CA92A261@muada.com>	<200810241444.06688.remi.denis-courmont@nokia.com>
	<372F2903-0116-45EF-87B0-304270667BBB@muada.com>
	<4901C8FB.80805@juniper.net>
X-Mailer: Apple Mail (2.929.2)
Cc: behave@ietf.org, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>,
	ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On 24 okt 2008, at 15:09, Robert Raszuk wrote:

> IPv6 has been implemented years back.

> Many production network are dual stack today or even running just  
> pure v6. So with this in mind what are you proposing to tell the  
> vendors reg hints for their upcoming implementations ???

What's the alternative? Not telling them?

What I hear is that many large content outfits have trouble going to  
v6 because the vendors of their load balancers don't have an IPv6  
solution yet. (Although I'm sure part of that is just an easy way of  
shifting the blame, but I'm also fairly sure it's true in a good  
number of cases.)
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 08:29:46 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51F4B28C1D9;
	Fri, 24 Oct 2008 08:29:46 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 873183A6A7C;
	Fri, 24 Oct 2008 02:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.231
X-Spam-Level: 
X-Spam-Status: No, score=-2.231 tagged_above=-999 required=5
	tests=[AWL=-0.232, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lDstL+zWfduQ; Fri, 24 Oct 2008 02:19:45 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1])
	by core3.amsl.com (Postfix) with ESMTP id 6D1FB3A6A6E;
	Fri, 24 Oct 2008 02:19:45 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id m9O9KpA7001395;
	Fri, 24 Oct 2008 12:20:51 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m9O9KpOp001392;
	Fri, 24 Oct 2008 12:20:51 +0300
Date: Fri, 24 Oct 2008 12:20:51 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <49009C8B.80707@cisco.com>
Message-ID: <alpine.LRH.2.00.0810241218190.1106@netcore.fi>
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>
	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.94,
	clamav-milter version 0.94 on otso.netcore.fi
X-Virus-Status: Clean
X-Mailman-Approved-At: Fri, 24 Oct 2008 08:29:45 -0700
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
 charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thu, 23 Oct 2008, Mark Townsley wrote:
>>  If #2 does not remind you of how we got into so much trouble nat44, well
>>  it should. Because of the impact on NAT66 on applications, if IETF does
>>  decide to do NAT66 specifications, I think it is very important that the
>>  specification is developed not only in the context of v6ops people but is
>>  also developed with input of folks from applications that need to use it.
>>  Today that would roughly mean behave.
>
> I think that something that operates only at the IP layer could stay in the 
> int-area.

But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.) 
that's broken today with NAT4 (with or without port translation) 
unless the NAT has ALGs.  To implement such ALGs, NAT66 would need to 
operate beyond the IP layer.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 08:29:46 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7022728C1F4;
	Fri, 24 Oct 2008 08:29:46 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B2BA3A6874;
	Fri, 24 Oct 2008 02:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yFIqjRwIv2pe; Fri, 24 Oct 2008 02:37:41 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [217.6.95.237])
	by core3.amsl.com (Postfix) with ESMTP id 2B2AA3A698B;
	Fri, 24 Oct 2008 02:37:41 -0700 (PDT)
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Fri, 24 Oct 2008 11:39:01 +0200
Received: from S4DE9JSAACY.ost.t-com.de ([10.125.177.233]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 11:38:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 11:38:34 +0200
Message-Id: <D83105B2AC38794CB78ADA2959F2C44F0270ECA2@S4DE9JSAACY.ost.t-com.de>
In-reply-to: <200810241210.46374.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
Thread-Index: Ack1uG8aHIuW25QMStWpjdSg/V7MPwAAwovQ
References: <48F8539D.90608@ericsson.com>
	<49009C8B.80707@cisco.com><A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
	<200810241210.46374.remi.denis-courmont@nokia.com>
From: "Bonness, Olaf" <Olaf.Bonness@t-systems.com>
To: <remi.denis-courmont@nokia.com>,
    <v4v6interim@ietf.org>
X-OriginalArrivalTime: 24 Oct 2008 09:38:34.0901 (UTC)
	FILETIME=[48D80450:01C935BC]
X-Mailman-Approved-At: Fri, 24 Oct 2008 08:29:45 -0700
Cc: 46translation@employees.org, behave@ietf.org
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thursday 23 October 2008 R=E9mi Denis-Courmont wrote:
> However, and to answer Alain's point, yes, some vendors will =

> ship NAT66 boxes =

> that work exactly like NAT44. But these will be no more =

> BEHAVE-compliant than =

> the NAT44 boxes. So it's kind of a non-issue from a standardization =

> perspective - I tend to think that there is no problem if there is no =

> solution.
> =

I agree with Remi.
Besides that I'm not realy sure if I buy the reasons why a NAT66 should be =
standardized. Only why some vendors will ship it? Only why some users are u=
sed to have NATs in their CPEs? Are there also stronger (more technical) re=
asons / problems a NAT66 would solve?
br
	olaf
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 08:43:30 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC14428C1D9;
	Fri, 24 Oct 2008 08:43:30 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3323828C1F3;
	Fri, 24 Oct 2008 08:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.008
X-Spam-Level: 
X-Spam-Status: No, score=-106.008 tagged_above=-999 required=5
	tests=[AWL=-0.009, BAYES_00=-2.599, J_CHICKENPOX_13=0.6,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f9IMHrWB4mWX; Fri, 24 Oct 2008 08:43:28 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 5B57628C1C1;
	Fri, 24 Oct 2008 08:43:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="95750028"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2008 15:44:41 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OFifob013318; 
	Fri, 24 Oct 2008 08:44:41 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18])
	by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m9OFidL0017422;
	Fri, 24 Oct 2008 15:44:39 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0810241218190.1106@netcore.fi>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com>
	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>
	<200810201358.29295.remi.denis-courmont@nokia.com>
	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>
	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>
	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>
	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>
	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com>
	<49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com>
	<FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com>
	<49009C8B.80707@cisco.com>
	<alpine.LRH.2.00.0810241218190.1106@netcore.fi>
Message-Id: <C592EC2D-16AE-4DBF-8772-C6B48F03D5D9@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 09:44:33 -0600
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1528; t=1224863081;
	x=1225727081; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fluffy@cisco.com;
	z=From:=20Cullen=20Jennings=20<fluffy@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20[v4v6interim]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVE=20charter |Sender:=20;
	bh=IjiQNneWwTRLbJlobZOw62eAbrvYXIpY2GcPe82q9/I=;
	b=YOwB45gYdRUz3/kRnAvFAbze52pQtuqwGYoog2Almo6F27TRUreWcvJryS
	IeQ76xzJWXwSUxsCH5meOd+gZezLP2glS5fxB0Z83IBLvjN1Mg7JpvLKE8U/
	Q0qWL/eS5M6wFTK+C2gmFoR4r1P1t+/F8YRKXBXsaaEwNFqqMn3JU=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE
	charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org


On Oct 24, 2008, at 3:20 AM, Pekka Savola wrote:

> On Thu, 23 Oct 2008, Mark Townsley wrote:
>>> If #2 does not remind you of how we got into so much trouble  
>>> nat44, well
>>> it should. Because of the impact on NAT66 on applications, if IETF  
>>> does
>>> decide to do NAT66 specifications, I think it is very important  
>>> that the
>>> specification is developed not only in the context of v6ops people  
>>> but is
>>> also developed with input of folks from applications that need to  
>>> use it.
>>> Today that would roughly mean behave.
>>
>> I think that something that operates only at the IP layer could  
>> stay in the int-area.
>
> But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.)  
> that's broken today with NAT4 (with or without port translation)  
> unless the NAT has ALGs.  To implement such ALGs, NAT66 would need  
> to operate beyond the IP layer.


My SIP phone has worked fine behind a NAT with no SIP ALG for several  
years now and so do my FTP sessions. Let me reiterate that is a NAT  
with no SIP or FTP ALG.  Sure it was a nightmare, and continues to be  
a nightmare, for applications to be designed to work behind NATs but  
that is how applications are designed for today. I wish it was not  
this way but it is. The whole point of BEHAVE was to make that  
slightly better by providing guidance for NATs that allowed  
applications to make reasonable assumptions about what type of NAT  
environment they might have to work behind. 
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 09:18:25 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 24DD93A69B9;
	Fri, 24 Oct 2008 09:18:25 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EDA603A6979;
	Fri, 24 Oct 2008 09:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.683
X-Spam-Level: 
X-Spam-Status: No, score=-105.683 tagged_above=-999 required=5
	tests=[AWL=-0.753, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xT57Dxd-LJqD; Fri, 24 Oct 2008 09:18:22 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id B959928C217;
	Fri, 24 Oct 2008 09:18:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="98578607"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 24 Oct 2008 16:19:43 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OGJhhH021457; 
	Fri, 24 Oct 2008 09:19:43 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9OGJgAg005105;
	Fri, 24 Oct 2008 16:19:43 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:19:43 -0700
Received: from [192.168.0.194] ([10.21.92.194]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:19:41 -0700
Message-Id: <0EFD0E10-B267-4079-B772-AEC8BE2D61FD@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Alain Durand <alain_durand@cable.comcast.com>
In-Reply-To: <C526256B.1C487%alain_durand@cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:21:44 +0800
References: <C526256B.1C487%alain_durand@cable.comcast.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Oct 2008 16:19:41.0957 (UTC)
	FILETIME=[51ED5350:01C935F4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4438; t=1224865183;
	x=1225729183; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[v4v6interim]=20[BEHAVE]=20[46translati
	on]=20Proposal=20for=20new=20BEHAVEcharter |Sender:=20;
	bh=JRer3aE63AbONZelAJZeZMQoIWi2JUAYFBTAnVpLju8=;
	b=qh/FXcKuYJhkdliMt5JAiPSJ1Wz+TFxvzqtzsRFMIKncZdg7GgDfSp9t1l
	dvescDP4Vgc3Nv4yK9u8wR4ZYQoaPIrm+fv/r3SDArxWP8SRIrckUlDIDDeY
	DPGE/UzPJGob0o8QDw38S6px8cRp6npKIg67ivTiqQU+9jvIkyhRA=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Very much agree.

On Oct 24, 2008, at 12:58 AM, Alain Durand wrote:

> I'm going to jump into this and probably not make friends...
>
> IPv6 is just like IPv4 with longer addresses. This is where deployment
> reality trumps architectural purity.
>
> What I've seen in the last 3 years is that it is much, much easier  
> to deploy
> IPv6 if you keep the exact same operational model as in IPv4. This  
> is one
> (among many) reason why we pushed for DHCPv6.
>
> Many folks are considering NAT44 as a simple solution where they  
> just have
> to put a box in front of their network to make whatever problem they  
> think
> they have go away. I can easily see that the same people would like  
> to do
> the same thing with IPv6. Which exact problem they were solving is
> irrelevant to this discussion, the point is about preserving the same
> operational model.
>
> That, and Cullen Jennings point #2 argue for defining NAT66 exactly  
> the same
> way as NAT44, ie with (optional) port translation. We have the  
> opportunity
> to explain why some choices are less worse than others in doing so  
> and put
> all the caveats in place. That is, make sure all the behave work  
> done for
> NAT44 is immediately integrated in NAT66, or in  other words, lets  
> define
> NAT66 in behave. Now, we may argue about the urgency of doing  
> this... Ie
> should this be done in parallel as NAT64 & NAT46 or after.
>
>   - Alain.
>
>
> On 10/23/08 12:06 PM, "Cullen Jennings" <fluffy@cisco.com> wrote:
>
>>
>>
>> On Oct 23, 2008, at 9:47 AM, Mark Townsley wrote:
>>
>>>
>>>
>>> Cullen Jennings wrote:
>>>>
>>>> I'm not worked up one way or the other about if we should specify
>>>> NAT66 or not - however, if we do specify it, I am very concerned
>>>> about how we do that. I see one good reason not to specify NAT66
>>>> and two good reasons to.
>>>
>>> Since saying nothing and hoping folks will abstain doesn't work very
>>> well in practice, I'd rather we go in and describe safe NAT66 the
>>> best we can. I agree that we have to be careful to do a good job, as
>>> teaching bad NAT66 could be worse than not teaching it at all.
>>>
>>>>
>>>> Reasons not to do NAT 66:
>>>> 1) All the reasons explained in RFC 4864
>>>>
>>>> Reason to do it:
>>>> 1) Limitations of RFC 4864 as explained in 4864
>>>> 2) Large vendors are building nat66 today and they are doing it in
>>>> a way that breaks applications and leaves the application designers
>>>> with no idea about what they can count on working and what they
>>>> can't count on.
>>>>
>>>> If #2 does not remind you of how we got into so much trouble nat44,
>>>> well it should. Because of the impact on NAT66 on applications, if
>>>> IETF does decide to do NAT66 specifications, I think it is very
>>>> important that the specification is developed not only in the
>>>> context of v6ops people but is also developed with input of folks
>>>> from applications that need to use it. Today that would roughly
>>>> mean behave.
>>> I think that something that operates only at the IP layer could stay
>>> in the int-area.
>>
>> If the mapping was purely and 1:1 mapping between internal and
>> external IPs I would agree with you but unfortunately, I worry that
>> meeting the requirement that drive section 4.4 of 4864 (privacy and
>> topology hiding) really complicate trying to do it with 1:1 mapping  
>> at
>> IP level.
>>
>> If you want to be able hide that two uncorrelated sessions are
>> actually coming from the same internal host, well, I'm not sure I see
>> how to do this with 1:1 mappings. One might argue that one should
>> ignore these requirements but this is one of key areas where some
>> people feel that 4864 has limitations that drive the deployment of
>> NAT66. Two solutions I have seen for this are a) different external  
>> IP
>> for every internal flow b) doing port address translation similar to
>> NAPT in NAT44. Either of these choices has some pretty substantial
>> impacts on how to make applications like VoIP work.
>>
>>
>>
>>
>>
>> _______________________________________________
>> v4v6interim mailing list
>> v4v6interim@ietf.org
>> https://www.ietf.org/mailman/listinfo/v4v6interim
>
> _______________________________________________
> v4v6interim mailing list
> v4v6interim@ietf.org
> https://www.ietf.org/mailman/listinfo/v4v6interim

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Fri Oct 24 09:18:28 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70F9B28C225;
	Fri, 24 Oct 2008 09:18:28 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3072228C225;
	Fri, 24 Oct 2008 09:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.972
X-Spam-Level: 
X-Spam-Status: No, score=-105.972 tagged_above=-999 required=5
	tests=[AWL=-0.442, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069,
	RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s5vkqApjUzSA; Fri, 24 Oct 2008 09:18:22 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id C203428C218;
	Fri, 24 Oct 2008 09:18:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="110909704"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 24 Oct 2008 16:19:44 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9OGJism028877; 
	Fri, 24 Oct 2008 09:19:44 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OGJi9Y024230;
	Fri, 24 Oct 2008 16:19:44 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:19:44 -0700
Received: from [192.168.0.194] ([10.21.92.194]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:19:43 -0700
Message-Id: <DBC9F399-F309-45D1-9CE3-FFDCF19FAE4A@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:28:50 +0800
References: <48F8539D.90608@ericsson.com>	<48FB9C5E.8070402@gmail.com>	<3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<8E5328A8-4937-41A8-A650-204795E074D1@muada.com>	<5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com>	<01462145-8E18-465A-8989-D1C98D421DED@muada.com>	<B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com>	<9E0384AB-A20B-44E7-8575-9275101FF920@muada.com><49008B8E.9080408@ericsson.com>
	<49008F1E.3010804@cisco.com>
	<EE6DCD77-43B9-40A8-B0BC-FAE79B3D8B49@lilacglade.org>
	<031d01c93535$c85b1140$9d6d6b80@cisco.com>
	<4C1AFFD1-34DF-4DDE-A081-09C652A63CF4@lilacglade.org>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 24 Oct 2008 16:19:43.0926 (UTC)
	FILETIME=[5319C560:01C935F4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2114; t=1224865184;
	x=1225729184; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20[v4v6inter
	im]=20Proposal=20for=20new=20BEHAVEcharter |Sender:=20;
	bh=zc6q7Tv64H4WAK4xzybJ8vangOgNmS9AwfupjT4Q2yo=;
	b=pGuKapVBNXrjx5GBjjKmk922w/mBrZVdgtaR19W3GdFIon0RqlB58R6Hai
	Qkvr1S3dOaOpGhkzXJElvjzmFSMTD2UgFlLys+oW5RMXKWGhsf8Gv7CDUTIl
	IYVGol9XrK;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org, '46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] Proposal for new
	BEHAVEcharter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

I think the best approach is to start work on it, but decouple it from  
4/6 NAT. There is, for example, no serious question of how to embed an  
IPv6 address into an IPv6 address.

I would recommend considering GSE as a basis - changing the prefix  
between two prefixes, such as a ULA and an operator prefix.

There will be issues with multiple subnet IDs; from a topology hiding  
model one wants them to go away, and in such a case there is a problem  
with host ID collisions. And if the "inside" and "outside" prefixes  
are of different lengths (ISP allocated a /56 but in my ULA I am using  
the equivalent of a /48 and embedding more than 2^8 prefixes in it)  
that also creates an issue. I would suggest a simple approach - tell  
the edge network operator that they need prefixes from the upstream  
LIRs that allow them to map subnets statelessly - that if they have  
2^9 subnets their upstreams need to give them a prefix no longer than  
64-9 bits, and they need to enumerate them so as to allow stateless  
translation.

On Oct 24, 2008, at 1:41 AM, Margaret Wasserman wrote:

>
> On Oct 23, 2008, at 1:35 PM, Dan Wing wrote:
>> BEHAVE is being re-chartered, so if the community wants BEHAVE to
>> do NAT66, now is a good time to tell the IESG to include NAT66 in
>> BEHAVE's charter.  (as you all know.)  The new charter, at this
>> time, does not include NAT66.
>>
>> And I only stated my desire to avoid the 'third rail'; the IESG can
>> certainly decide they want NAT66 standardized.  Based on my
>> understanding of how NAT66 would work, it would belong in BEHAVE.
>
> Thanks, Dan.  This is very reasonable.
>
> So, what's the best way forward?  Perhaps I could write a draft,  
> sent a pointer to behave, and we could have a discussion over the  
> next couple of weeks about whether the community does/doesn't want  
> to include this in the new behave charter?
>
> Margaret
>
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Sat Oct 25 13:51:05 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 66DBA3A6810;
	Sat, 25 Oct 2008 13:51:05 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 665DD3A6804;
	Sat, 25 Oct 2008 12:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.242
X-Spam-Level: 
X-Spam-Status: No, score=-102.242 tagged_above=-999 required=5
	tests=[AWL=0.023, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rjE-xzJhnLgp; Sat, 25 Oct 2008 12:35:43 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id C268F3A6802;
	Sat, 25 Oct 2008 12:35:43 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id F1AC26C984AC; Sat, 25 Oct 2008 19:37:08 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 0639B6C9843C;
	Sat, 25 Oct 2008 19:37:06 +0000 (UTC)
Message-ID: <49037562.5050708@acm.org>
Date: Sat, 25 Oct 2008 12:37:06 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.17 (X11/20081018)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <48F8539D.90608@ericsson.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<48FC663E.1070902@it.uc3m.es>	<200810201426.33336.remi.denis-courmont@nokia.com>
	<48FCF87B.8060609@gmail.com>
In-Reply-To: <48FCF87B.8060609@gmail.com>
X-Mailman-Approved-At: Sat, 25 Oct 2008 13:51:04 -0700
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [v4v6interim] [BEHAVE] NAT66 for PI [Re: [46translation]
 Proposal for new	BEHAVEcharter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

QnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6Cj4gT24gMjAwOC0xMC0yMSAwMDoyNiwgUsOpbWkgRGVu
aXMtQ291cm1vbnQgd3JvdGU6Cj4gLi4uCj4+Pj4gNC8gcHJlZml4IGRlbGVnYXRpb24gImJ5cGFz
cyIKPj4+Pgo+Pj4+ICgxKSBpcyBhIG5vbi1pc3N1ZSBmb3IgSVB2Ni4gKDIpIGlzIHNvbHZlZCB3
aXRoIHN0YXRlZnVsIGZpcmV3YWxsaW5nIGFuZAo+Pj4+IGRvZXMgbm90IHJlcXVpcmUgTkFULiAx
OjEgTkFUIGZhaWxzIHRvIHNvbHZlICgzKSBhcyBpdCBkb2VzIGhpZGUgdGhlCj4+Pj4gc3VibmV0
dGluZyBzY2hlbWUsIGJ1dCBmYWlscyB0byBoaWRlIGluZGl2aWR1YWwgaG9zdHMuIFRoaXMgbGVh
dmVzIG9ubHkKPj4+PiAoNCkuIERpZCBJIG1pc3MgYW55dGhpbmc/Cj4+PiBJIHRoaW5rIG9uZSBt
YWluIHJlYXNvbiB3b3VsZCBiZSBwcm92aWRlciBpbmRlcGVuZGVuY2UgKGllLiBubyBuZWVkIHRv
Cj4+PiByZW51bWJlcikgIGZvciBzbWFsbCBzaXRlcyB0aGF0IGNhbm5vdCBhZmZvcmQgdG8gaGF2
ZSB0aGllciBvd24gUEkKPj4+IGFkZHJlc3MgYmxvY2sgYWxsb2NhdGVkCj4+IFRoYXQncyBwcmVm
aXggZGVsZWdhdGlvbi9yb3V0aW5nIGJ5cGFzcy4KPgo+IFllcy4gSXQgYXZvaWRzIHJlbnVtYmVy
aW5nLCBhbmQgYWxsb3dzIG11bHRpaG9taW5nLiBJdCdzIHZlcnkgaGFyZAo+IHRvIHN0b3AgdGhp
cyB1bmxlc3MgdGhlIFJSRyBjb21lcyB1cCB3aXRoIGEgbWlyYWNsZSBzb2x1dGlvbgo+IGluIHRo
ZSBuZWFyIGZ1dHVyZS4KCkRvZXNuJ3QgSElQIHNvbHZlIHRoaXMgcHJvYmxlbT8KCi0tIApNYXJj
IFBldGl0LUh1Z3VlbmluICAgICAgICAgICBbICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgXQpIb21lOiBtYXJjQHBldGl0LWh1Z3VlbmluLm9yZyBbUkZDMTg1NS1jb21wbGlhbnQgc3Bh
Y2UgZm9yIHJlbnQgXQpXb3JrOiBtYXJjQDh4OC5jb20gICAgICAgICAgICBbICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgXQpbICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgXQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwp2NHY2aW50ZXJpbSBtYWlsaW5nIGxpc3QKdjR2NmludGVy
aW1AaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92NHY2aW50
ZXJpbQo=


From v4v6interim-bounces@ietf.org  Sat Oct 25 14:13:50 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F09423A690E;
	Sat, 25 Oct 2008 14:13:49 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21F853A6886;
	Sat, 25 Oct 2008 14:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.5
X-Spam-Level: 
X-Spam-Status: No, score=-106.5 tagged_above=-999 required=5 tests=[AWL=0.099, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id It+K0E9S90Ap; Sat, 25 Oct 2008 14:13:47 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 2C6DC3A6818;
	Sat, 25 Oct 2008 14:13:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,485,1220227200"; d="scan'208";a="182625173"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 25 Oct 2008 21:15:12 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9PLFC2j009429; 
	Sat, 25 Oct 2008 14:15:12 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9PLFCoW017320;
	Sat, 25 Oct 2008 21:15:12 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 14:15:12 -0700
Received: from [192.168.100.101] ([10.21.71.28]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 14:15:11 -0700
Message-Id: <5665336F-F111-48F2-AFC4-0CB6587A844F@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <49037562.5050708@acm.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 26 Oct 2008 05:15:09 +0800
References: <48F8539D.90608@ericsson.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<48FC663E.1070902@it.uc3m.es>	<200810201426.33336.remi.denis-courmont@nokia.com>
	<48FCF87B.8060609@gmail.com> <49037562.5050708@acm.org>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 25 Oct 2008 21:15:11.0728 (UTC)
	FILETIME=[C41B6F00:01C936E6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2335; t=1224969312;
	x=1225833312; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20[46translation]=20[BEHAVE]=20NAT66=20fo
	r=20PI=20[Re=3A=20[v4v6interim]=20Proposal=20for=20new=09BEH
	AVEcharter] |Sender:=20;
	bh=uJ0DqhnSmq6kceKwcxd+0T/6ha/FbjnCQP/uv+u6RKY=;
	b=QPCBhiyNF5n+ViKpER4gQGgN3GPHSZe3aARDfzYTPTHLmIojo5vswPp4qo
	f4rxWRyh2jFRi5V8QM7RQpH0VFmrDmqGcIc/Bfstv6f7C54w22jnfZefILnr
	ZHg4nybRQe;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] [46translation] [BEHAVE] NAT66 for PI [Re:
	Proposal for new	BEHAVEcharter]
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

no, at least I don't think so.

HIP tries to provide what RFC 1498 and 1753 call an "endpoint ID", but  =

provides no way to associate locators with it. Hence, while from an  =

application perspective it enables the application to ensure that the  =

system or service it is talking with is the one it intends to, it  =

doesn't enable the transport to select an address pair to use in  =

routing - and yes, the choice of a source and a destination address  =

has the effect of routing a session, as it determines important points  =

that the datagram will transit.

Read all of RFCs 1483, 1753, 1992, http://ana.lcs.mit.edu/~jnc/tech/endpoin=
ts.txt =

, and http://tools.ietf.org/html/draft-irtf-nsrg-report for a complete  =

discussion of the problem. Getting network folks and application folks  =

to describe the problem is a little like describing the elephant -  =

each only describes part.

On Oct 26, 2008, at 3:37 AM, Marc Petit-Huguenin wrote:

> Brian E Carpenter wrote:
>> On 2008-10-21 00:26, R=E9mi Denis-Courmont wrote:
>> ...
>>>>> 4/ prefix delegation "bypass"
>>>>>
>>>>> (1) is a non-issue for IPv6. (2) is solved with stateful  =

>>>>> firewalling and
>>>>> does not require NAT. 1:1 NAT fails to solve (3) as it does hide  =

>>>>> the
>>>>> subnetting scheme, but fails to hide individual hosts. This  =

>>>>> leaves only
>>>>> (4). Did I miss anything?
>>>> I think one main reason would be provider independence (ie. no  =

>>>> need to
>>>> renumber)  for small sites that cannot afford to have thier own PI
>>>> address block allocated
>>> That's prefix delegation/routing bypass.
>>
>> Yes. It avoids renumbering, and allows multihoming. It's very hard
>> to stop this unless the RRG comes up with a miracle solution
>> in the near future.
>
> Doesn't HIP solve this problem?
>
> -- =

> Marc Petit-Huguenin           [                                 ]
> Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
> Work: marc@8x8.com            [                                 ]
> [                                                               ]
> _______________________________________________
> 46translation mailing list
> 46translation@employees.org
> https://www.employees.org/mailman/listinfo/46translation

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Mon Oct 27 05:54:46 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C9703A6A94;
	Mon, 27 Oct 2008 05:54:46 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D43083A6A8F;
	Mon, 27 Oct 2008 05:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.035
X-Spam-Level: 
X-Spam-Status: No, score=-3.035 tagged_above=-999 required=5
	tests=[AWL=-0.800, BAYES_40=-0.185, HELO_EQ_SE=0.35, J_BACKHAIR_44=1,
	J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jVgPznI5YHxY; Mon, 27 Oct 2008 05:54:44 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id A8CAA3A680D;
	Mon, 27 Oct 2008 05:54:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	23171206D0; Mon, 27 Oct 2008 13:54:39 +0100 (CET)
X-AuditID: c1b4fb3e-af787bb00000537b-77-4905ba0e6c39
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F04E720242; Mon, 27 Oct 2008 13:54:38 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 13:54:38 +0100
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 13:54:37 +0100
Message-ID: <4905BA0E.7000502@ericsson.com>
Date: Mon, 27 Oct 2008 13:54:38 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>, 46Translation <46translation@employees.org>,
	v4v6interim@ietf.org, IETF V6OPS WG <v6ops@ops.ietf.org>, 
	softwires@ietf.org, Internet Area <int-area@ietf.org>, 
	TSV Area <tsv-area@ietf.org>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 27 Oct 2008 12:54:37.0889 (UTC)
	FILETIME=[2B5ECB10:01C93833]
X-Brightmail-Tracker: AAAAAA==
Subject: [v4v6interim] Status of IPv4-IPv6 Coexistence Work
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

IETF Community,

There has been a lot of activity on the topic of improving IPv4 and IPv6
coexistence, deployment of IPv6, and coping with the increasing shortage
of unassigned IPv4 addresses. This work crosses a number of layer and
area boundaries, which has led to new lists, cross-posting, etc. In
order to limit confusion, we'd like to give some guidance on where
to discuss what on which lists. The intent is not to declare any work
as in or out of charter with this message, only to try and direct list
discussion. These are only general guidelines, so please don't be
alarmed if we missed something in particular. Our hope is that this will
help everyone to continue the rich dialog on this important topic.

1. softwires@ietf.org

Softwires is chartered to work on combinations of IPv4/IPv6 and
IPv6/IPv4, including "dual-stack lite" functionality. This includes
discussion related to:

- All types of IPv4/IPv6 tunnels, including encapsulation, control
  plane, etc.
- Affects of tunnel endpoints terminating into a concentrator performing
  IPv4 to IPv4 NAT
- Discovery of tunnel endpoints
- Tunnels initiated by hosts or gateways
- Tunnels automatically setup by routing and special prefixes

Thus, if it involves a tunnel or encapsulation of IPvX over IPvY,
softwires is the place to go.

2. behave@ietf.org

The Behave WG is currently being rechartered. If the new charter is
approved, behave will work on various types of IPv4<->IPv6 translation.
Please direct all discussion related to:

- IPv4 to IPv6 and IPv6 to IPv4 translation
- IPv6 to IPv6 NAT
- Division of port space to share one IPv4 addresses among multiple
  endpoints at the same time
- Affects on applications and transport protocols
- ALGs
- IPv4 to IPv4 NAT functionality, including for ISP deployments

Thus, if discussion involves an IP translator or the internal function
of a NAT, behave is the place to go.

3. v6ops@ietf.org

- Operational discussions on the topic of coexistence in general
- IPv6-only deployment

Thus, if it involves operational issues of IPv6 or IPv4 exhaustion, go
to v6ops.

4. The v4v6interim@ietf.org list will be removed after the Minneapolis
IETF meeting.


Jari Arkko
Ron Bonica
Lars Eggert
Mark Townsley
Magnus Westerlund


Resources:

WGs
Behave: http://www.ietf.org/html.charters/behave-charter.html
Softwire: http://www.ietf.org/html.charters/softwire-charter.html
v6ops: http://www.ietf.org/html.charters/v6ops-charter.html

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim


From v4v6interim-bounces@ietf.org  Tue Oct 28 17:52:36 2008
Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 13C573A6A0C;
	Tue, 28 Oct 2008 17:52:36 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27E8D3A68E6
	for <v4v6interim@core3.amsl.com>; Tue, 28 Oct 2008 17:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TJXqxjZid9tl for <v4v6interim@core3.amsl.com>;
	Tue, 28 Oct 2008 17:52:33 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169])
	by core3.amsl.com (Postfix) with ESMTP id D5C693A6A0C
	for <v4v6interim@ietf.org>; Tue, 28 Oct 2008 17:52:33 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so3173952wfd.31
	for <v4v6interim@ietf.org>; Tue, 28 Oct 2008 17:52:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from
	:organization:user-agent:mime-version:to:cc:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=B8vuPAsF+0XFKyksyii5z5LfktwiaESkBGyWJNSTy6Q=;
	b=p4gsMS4ZjOIDhjbiQ4AvSwFnIgQRLkMuHhJwOpgtKIakcQLHg1Lb0kOsnNYIbFN83i
	jeJQQTVUc5JeFYMl6ZBaqxBIls5zpeWYXA7iDma/v0cD7zo4DylXuQv/bkaZOwEBzO7G
	7C9zW+U1bSKVrlr0G/LlX1MC1qJJhrZ4UbXzs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=weoBdFI/Bp6RyxZu4e46xlc6NQRnUr2/Iqdu2xjziULTeGvtr17PJq/JyMK0r0VpXN
	6eJyDEtyLUcMCT6sNjcRtwEbk1APuEnDZSa5b9WeSQ7Bi8j9ng0FQPdA47GiYBx2kAh6
	yp3LYcUA6WzhfSxzSVfLtEDJIM6N4K9fP8tEE=
Received: by 10.142.223.4 with SMTP id v4mr3692533wfg.48.1225241551152;
	Tue, 28 Oct 2008 17:52:31 -0700 (PDT)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz
	[130.216.38.124])
	by mx.google.com with ESMTPS id 9sm5149227wfc.19.2008.10.28.17.52.29
	(version=SSLv3 cipher=RC4-MD5); Tue, 28 Oct 2008 17:52:30 -0700 (PDT)
Message-ID: <4907B3CB.8040304@gmail.com>
Date: Wed, 29 Oct 2008 13:52:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <48F8539D.90608@ericsson.com>	<200810201358.29295.remi.denis-courmont@nokia.com>	<48FC663E.1070902@it.uc3m.es>	<200810201426.33336.remi.denis-courmont@nokia.com>
	<48FCF87B.8060609@gmail.com> <49037562.5050708@acm.org>
	<5665336F-F111-48F2-AFC4-0CB6587A844F@cisco.com>
In-Reply-To: <5665336F-F111-48F2-AFC4-0CB6587A844F@cisco.com>
Cc: Marc Petit-Huguenin <petithug@acm.org>, v4v6interim@ietf.org,
	46translation@employees.org, 'Behave WG' <behave@ietf.org>
Subject: Re: [v4v6interim] Doesn't HIP solve this problem?
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6
	coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>,
	<mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

RnJlZCwKCkkgdGhpbmsgeW91IGFyZSBzcG90IG9uLiBBIG5ldyBzZXNzaW9uIGxheWVyIGlkZW50
aWZpZXIgbmFtZXNwYWNlIHdvdWxkCnNvbHZlIGEgbG90IG9mIHByb2JsZW1zLCBidXQgd291bGQg
cmVxdWlyZSBhIG5ldyBpZGVudGlmaWVyIG1hcHBpbmcKc3lzdGVtIHRvIGxpbmsgaXQgYmFjayB0
byB0aGUgbmV0d29yayBsYXllciBhbmQgdGhlIHJvdXRpbmcgc3lzdGVtLgpUaGF0J3MgbWlzc2lu
ZyBpbiBISVAgdG9kYXkgKHdoaWNoIGlzIHdoeSB3ZSBnZXQgYSBtaXNobWFzaCBsaWtlClJGQyA0
ODQzKS4KCkkgc3VnZ2VzdCB0aGlzIGxpbmUgb2YgZGlzY3Vzc2lvbiBpcyBjbG9zZXIgdG8gdGhl
IFJSRyBjaGFydGVyCnRoYW4gdG8gQkVIQVZFLgoKICAgIEJyaWFuCgpPbiAyMDA4LTEwLTI2IDEw
OjE1LCBGcmVkIEJha2VyIHdyb3RlOgo+IG5vLCBhdCBsZWFzdCBJIGRvbid0IHRoaW5rIHNvLgo+
IAo+IEhJUCB0cmllcyB0byBwcm92aWRlIHdoYXQgUkZDIDE0OTggYW5kIDE3NTMgY2FsbCBhbiAi
ZW5kcG9pbnQgSUQiLCBidXQKPiBwcm92aWRlcyBubyB3YXkgdG8gYXNzb2NpYXRlIGxvY2F0b3Jz
IHdpdGggaXQuIEhlbmNlLCB3aGlsZSBmcm9tIGFuCj4gYXBwbGljYXRpb24gcGVyc3BlY3RpdmUg
aXQgZW5hYmxlcyB0aGUgYXBwbGljYXRpb24gdG8gZW5zdXJlIHRoYXQgdGhlCj4gc3lzdGVtIG9y
IHNlcnZpY2UgaXQgaXMgdGFsa2luZyB3aXRoIGlzIHRoZSBvbmUgaXQgaW50ZW5kcyB0bywgaXQK
PiBkb2Vzbid0IGVuYWJsZSB0aGUgdHJhbnNwb3J0IHRvIHNlbGVjdCBhbiBhZGRyZXNzIHBhaXIg
dG8gdXNlIGluIHJvdXRpbmcKPiAtIGFuZCB5ZXMsIHRoZSBjaG9pY2Ugb2YgYSBzb3VyY2UgYW5k
IGEgZGVzdGluYXRpb24gYWRkcmVzcyBoYXMgdGhlCj4gZWZmZWN0IG9mIHJvdXRpbmcgYSBzZXNz
aW9uLCBhcyBpdCBkZXRlcm1pbmVzIGltcG9ydGFudCBwb2ludHMgdGhhdCB0aGUKPiBkYXRhZ3Jh
bSB3aWxsIHRyYW5zaXQuCj4gCj4gUmVhZCBhbGwgb2YgUkZDcyAxNDgzLCAxNzUzLCAxOTkyLAo+
IGh0dHA6Ly9hbmEubGNzLm1pdC5lZHUvfmpuYy90ZWNoL2VuZHBvaW50cy50eHQsIGFuZAo+IGh0
dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlydGYtbnNyZy1yZXBvcnQgZm9yIGEgY29t
cGxldGUKPiBkaXNjdXNzaW9uIG9mIHRoZSBwcm9ibGVtLiBHZXR0aW5nIG5ldHdvcmsgZm9sa3Mg
YW5kIGFwcGxpY2F0aW9uIGZvbGtzCj4gdG8gZGVzY3JpYmUgdGhlIHByb2JsZW0gaXMgYSBsaXR0
bGUgbGlrZSBkZXNjcmliaW5nIHRoZSBlbGVwaGFudCAtIGVhY2gKPiBvbmx5IGRlc2NyaWJlcyBw
YXJ0Lgo+IAo+IE9uIE9jdCAyNiwgMjAwOCwgYXQgMzozNyBBTSwgTWFyYyBQZXRpdC1IdWd1ZW5p
biB3cm90ZToKPiAKPj4gQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6Cj4+PiBPbiAyMDA4LTEwLTIx
IDAwOjI2LCBSw6ltaSBEZW5pcy1Db3VybW9udCB3cm90ZToKPj4+IC4uLgo+Pj4+Pj4gNC8gcHJl
Zml4IGRlbGVnYXRpb24gImJ5cGFzcyIKPj4+Pj4+Cj4+Pj4+PiAoMSkgaXMgYSBub24taXNzdWUg
Zm9yIElQdjYuICgyKSBpcyBzb2x2ZWQgd2l0aCBzdGF0ZWZ1bAo+Pj4+Pj4gZmlyZXdhbGxpbmcg
YW5kCj4+Pj4+PiBkb2VzIG5vdCByZXF1aXJlIE5BVC4gMToxIE5BVCBmYWlscyB0byBzb2x2ZSAo
MykgYXMgaXQgZG9lcyBoaWRlIHRoZQo+Pj4+Pj4gc3VibmV0dGluZyBzY2hlbWUsIGJ1dCBmYWls
cyB0byBoaWRlIGluZGl2aWR1YWwgaG9zdHMuIFRoaXMgbGVhdmVzCj4+Pj4+PiBvbmx5Cj4+Pj4+
PiAoNCkuIERpZCBJIG1pc3MgYW55dGhpbmc/Cj4+Pj4+IEkgdGhpbmsgb25lIG1haW4gcmVhc29u
IHdvdWxkIGJlIHByb3ZpZGVyIGluZGVwZW5kZW5jZSAoaWUuIG5vIG5lZWQgdG8KPj4+Pj4gcmVu
dW1iZXIpICBmb3Igc21hbGwgc2l0ZXMgdGhhdCBjYW5ub3QgYWZmb3JkIHRvIGhhdmUgdGhpZXIg
b3duIFBJCj4+Pj4+IGFkZHJlc3MgYmxvY2sgYWxsb2NhdGVkCj4+Pj4gVGhhdCdzIHByZWZpeCBk
ZWxlZ2F0aW9uL3JvdXRpbmcgYnlwYXNzLgo+Pj4KPj4+IFllcy4gSXQgYXZvaWRzIHJlbnVtYmVy
aW5nLCBhbmQgYWxsb3dzIG11bHRpaG9taW5nLiBJdCdzIHZlcnkgaGFyZAo+Pj4gdG8gc3RvcCB0
aGlzIHVubGVzcyB0aGUgUlJHIGNvbWVzIHVwIHdpdGggYSBtaXJhY2xlIHNvbHV0aW9uCj4+PiBp
biB0aGUgbmVhciBmdXR1cmUuCj4+Cj4+IERvZXNuJ3QgSElQIHNvbHZlIHRoaXMgcHJvYmxlbT8K
Pj4KPj4gLS0gCj4+IE1hcmMgUGV0aXQtSHVndWVuaW4gICAgICAgICAgIFsgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBdCj4+IEhvbWU6IG1hcmNAcGV0aXQtaHVndWVuaW4ub3JnIFtS
RkMxODU1LWNvbXBsaWFudCBzcGFjZSBmb3IgcmVudCBdCj4+IFdvcms6IG1hcmNAOHg4LmNvbSAg
ICAgICAgICAgIFsgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBdCj4+IFsgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBd
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+IDQ2
dHJhbnNsYXRpb24gbWFpbGluZyBsaXN0Cj4+IDQ2dHJhbnNsYXRpb25AZW1wbG95ZWVzLm9yZwo+
PiBodHRwczovL3d3dy5lbXBsb3llZXMub3JnL21haWxtYW4vbGlzdGluZm8vNDZ0cmFuc2xhdGlv
bgo+IAo+IAoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K
djR2NmludGVyaW0gbWFpbGluZyBsaXN0CnY0djZpbnRlcmltQGlldGYub3JnCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjR2NmludGVyaW0K


