From behave-bounces@ietf.org  Wed Oct  1 06:31:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D1953A69DE;
	Wed,  1 Oct 2008 06:31:40 -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 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: Brian Haberman <brian@innovationslab.net>,
	Internet Area <int-area@ietf.org>, "Narayanan,
	Vidya" <vidyan@qualcomm.com>, ipv6@ietf.org, softwires@ietf.org,
	Dan Wing <dwing@cisco.com>, Margaret Wasserman <mrw@lilacglade.org>,
	Mark Townsley <townsley@cisco.com>,
	IPv6 Operations <v6ops@ops.ietf.org>, v4v6interim@ietf.org,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] v4v6interim@ietf.org Mailing list
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>>> --------------------------------------------------------------------
>>>
>
>
>

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


From behave-bounces@ietf.org  Wed Oct  1 11:08:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB3423A6AB5;
	Wed,  1 Oct 2008 11:08:28 -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 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: [BEHAVE] FW: New Version Notification for
	draft-endo-v6ops-dnsproxy-01
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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.


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


From behave-bounces@ietf.org  Wed Oct  1 22:39:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 354D13A69A4;
	Wed,  1 Oct 2008 22:39:50 -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 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:39:48 -0700
Cc: Brian Haberman <brian@innovationslab.net>,
	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: [BEHAVE] v4v6interim@ietf.org Mailing list
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

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
> > --------------------------------------------------------------------
> >


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


From behave-bounces@ietf.org  Fri Oct  3 13:24:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5745C3A6A15;
	Fri,  3 Oct 2008 13:24:50 -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 F375028C0E8
	for <behave@core3.amsl.com>; Fri,  3 Oct 2008 13:24:48 -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 n+2vIhSNqQra for <behave@core3.amsl.com>;
	Fri,  3 Oct 2008 13:24:48 -0700 (PDT)
Received: from mail-05.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id 446423A6A15
	for <behave@ietf.org>; Fri,  3 Oct 2008 13:24:48 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1KlrAv-0000qt-1a
	for behave@ietf.org; Fri, 03 Oct 2008 16:22:57 -0400
Message-Id: <C05248C9-8F55-4925-8983-AE9BB4E836FE@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
In-Reply-To: <A86E5007-C463-4E45-ACF4-F5B7E9152A25@magma.ca>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 3 Oct 2008 16:24:47 -0400
References: <C78053D0-D4BE-4C57-AFB0-8310985645A8@magma.ca>
	<48DD0357.8000901@acm.org>
	<B0F8A909-221D-44AF-B028-39B46F8639C4@magma.ca>
	<48DD0B98.9060602@acm.org>
	<A86E5007-C463-4E45-ACF4-F5B7E9152A25@magma.ca>
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Subject: Re: [BEHAVE] TURN: Problems with Send request concept
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Right now, I am seeing a preference on the mailing list and with  
people I have talked with privately to keep the ability for  
CreatePermission to create permission. People like the fact that this  
ability reduced the amount of messages that clients need to send.

I am currently seeing mixed support for making channel lifetimes and  
permission lifetimes equal. Though I agree it makes things a little  
cleaner, it seems to have very little practical impact. Since I am in  
favor of leaving things as they are unless there is strong support to  
change things, I am currently not planning to make this change.

- Philip


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


From behave-bounces@ietf.org  Fri Oct  3 13:55:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3D4B3A689C;
	Fri,  3 Oct 2008 13:55:09 -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 C68133A689C
	for <behave@core3.amsl.com>; Fri,  3 Oct 2008 13:55: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=[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 bwxFGwnkQzgA for <behave@core3.amsl.com>;
	Fri,  3 Oct 2008 13:55:07 -0700 (PDT)
Received: from mail-07.primus.ca (mail3.primus.ca [216.254.141.170])
	by core3.amsl.com (Postfix) with ESMTP id E48EB3A6833
	for <behave@ietf.org>; Fri,  3 Oct 2008 13:55:06 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1KlrgQ-0004VQ-38
	for behave@ietf.org; Fri, 03 Oct 2008 16:55:31 -0400
Message-Id: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Fri, 3 Oct 2008 16:55:34 -0400
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Subject: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

TURN-10 introduces the CreatePermission request for creating or  
updating a permission. With this new request comes the question of  
what to do if the server receives a Send indication when no permission  
is installed towards the peer. There are two options:
a) Send the UDP datagram towards the peer anyway, or
b) Drop the Send indication

In TURN-10, we opted for (a) because there didn't seem to be any good  
reason to do (b).  However, Cullen has now found an example where  
option (a) seems to be a problem.

Consider a TURN server operated by an organization O and located in  
the organization's DMZ. Consider a laptop owned by user Fred (who  
works for the organization). Fred's laptop is configured to use the  
organization's TURN server. Now consider what happens if Fred goes off  
to an IETF meeting.

Fred's laptop will still try to use O's TURN server, except now the  
TURN server is being accessed from the Internet. At the IETF meeting,  
an attacker can sniff the wireless network and see the TURN packets  
Fred's laptop is exchanging with the TURN server. The attacker can  
then use TURN to attack the other servers in the O's DMZ by sending a  
Send indication to the TURN server with a PEER-ADDRESS attribute of  
the other server. The attacker can do this because Send indications  
are not authenticated. In this way, the attacker has bypassed any  
rules that the Outer Firewall has installed about who may access the  
other servers in the DMZ.

                                                    +---------------+
                                                    | Fred's laptop |
            +----------------+                      +---------------+
    +-------| Outer Firewall |----------+
    |       +----------------+          |
    |                                   |
    | +-------------+   +------------+  |
    | | TURN server |   | Web Server |  |
    | +-------------+   +------------+  |
    |                                   |
    |       +-----------------+         |
    +-------| Inner Firewall  |---------+
    |       +-----------------+         |
    |                                   |
    |     Organization's network        |
    |                                   |
    +-----------------------------------+


Given this example, I am proposing to change to option (b). In other  
words, the Server will drop an incoming Send indication unless there  
is an active permission towards the IP address in the PEER-ADDRESS.

Comments?
Does anyone think that we should address Cullen's example in another  
way? Does anyone think that there are reasons a client would like the  
behavior that option (a) offers?

- Philip


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


From behave-bounces@ietf.org  Sat Oct  4 10:10:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0EFE3A68AD;
	Sat,  4 Oct 2008 10:10:36 -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 4DE723A659A;
	Sat,  4 Oct 2008 10:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.300, 
	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 wMX6vKVIAyAj; Sat,  4 Oct 2008 10:10:35 -0700 (PDT)
Received: from yop.chewa.net (yop.chewa.net [91.121.105.214])
	by core3.amsl.com (Postfix) with ESMTP id 318C73A68AD;
	Sat,  4 Oct 2008 10:10:35 -0700 (PDT)
Received: from basile.remlab.net (unknown
	[IPv6:2002:591b:3aef:0:211:11ff:fe25:e6b4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by yop.chewa.net (Postfix) with ESMTP id 18B833867;
	Sat,  4 Oct 2008 19:10:53 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Sat, 4 Oct 2008 20:10:50 +0300
User-Agent: KMail/1.9.9
References: <48D79E56.3030107@ericsson.com>
In-Reply-To: <48D79E56.3030107@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810042010.50772.rdenis@simphalempin.com>
Cc: IETF DCCP Working Group <dccp@ietf.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] AD comments on draft-ietf-behave-dccp-02
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

Le lundi 22 septembre 2008 16:32:06 Magnus Westerlund, vous avez =E9crit=A0:
> 3. Section 10:
> "  Similar to [I-D.ietf-behave-tcp], REQ-4 of this document recommends a
>     NAT to respond to unsolicited inbound Sync packets with an ICMP error
>     delayed by a few seconds."
>
> This sentence mentions "sync" packets, while REQ-4 only talks about
> Listen. Which packet type is the right one or should both be mentioned i
> both places?

Indeed, if we want to limit timing problems for simultaneous open (dependin=
g =

which sides talks first), both packets types should be handled this way.

-- =

R=E9mi Denis-Courmont
http://www.remlab.net/
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat Oct  4 10:15:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D75E28C0DD;
	Sat,  4 Oct 2008 10:15:04 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id AB1D73A68F0; Sat,  4 Oct 2008 10:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081004171501.AB1D73A68F0@core3.amsl.com>
Date: Sat,  4 Oct 2008 10:15:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-dccp-03.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Network Address Translation (NAT) Behavioral Requirements for DCCP
	Author(s)       : R. Denis-Courmont
	Filename        : draft-ietf-behave-dccp-03.txt
	Pages           : 11
	Date            : 2008-10-04

This document defines a set of requirements for NATs handling the
Datagram Congestion Control Protocol (DCCP).  Those allow DCCP
applications, such as streaming applications to operate consistently.
These requirements are very similar to the TCP requirements for NATs
already published by the IETF Behavior Engineering for Hindrance
Avoidance (BEHAVE) working group.  Developing NATs that meet this set
of requirements will greatly increase the likelihood that
applications using DCCP will function properly.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-dccp-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-dccp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From behave-bounces@ietf.org  Mon Oct  6 07:46:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D1D728C10F;
	Mon,  6 Oct 2008 07:46:50 -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 456233A67B4
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 07:46:49 -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 Pxmb0yDfpvq8 for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 07:46:48 -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 15D9428C10F
	for <behave@ietf.org>; Mon,  6 Oct 2008 07:46:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,368,1220227200"; d="scan'208";a="169636997"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 06 Oct 2008 14:47:22 +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 m96ElM4Q007420; 
	Mon, 6 Oct 2008 07:47:22 -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 m96ElGlj006849;
	Mon, 6 Oct 2008 14:47:22 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); 
	Mon, 6 Oct 2008 10:47:22 -0400
Received: from [10.82.247.74] ([10.82.247.74]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 10:47:21 -0400
Message-ID: <48EA24F7.9070800@cisco.com>
Date: Mon, 06 Oct 2008 10:47:19 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
In-Reply-To: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
X-OriginalArrivalTime: 06 Oct 2008 14:47:21.0936 (UTC)
	FILETIME=[7061B500:01C927C2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3414; t=1223304442;
	x=1224168442; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20TURN=3A=20Send=20indication=
	20when=20no=20permission=20exists |Sender:=20;
	bh=xvZ3S8SpEKFhCIIXZaMbuDyowtuuSMa0fTWxE+FPwpk=;
	b=APCEkvsPWDRhCeaVUO4688+Yktq2a7XIxFQUt520H/TX7N8+tBzSU5B9j9
	DXbqghPpzXsaOON2bnkiH76/gQOtNtuqNxsfrKlIVDg6LOSyAKCHsaO2p/9O
	/H3dWY+1XF;
Authentication-Results: sj-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I agree with Cullen's concern and think the proposed remedy - requiring 
a CreatePermission first - is the right approach.

-Jonathan R.

Philip Matthews wrote:
> TURN-10 introduces the CreatePermission request for creating or updating 
> a permission. With this new request comes the question of what to do if 
> the server receives a Send indication when no permission is installed 
> towards the peer. There are two options:
> a) Send the UDP datagram towards the peer anyway, or
> b) Drop the Send indication
> 
> In TURN-10, we opted for (a) because there didn't seem to be any good 
> reason to do (b).  However, Cullen has now found an example where option 
> (a) seems to be a problem.
> 
> Consider a TURN server operated by an organization O and located in the 
> organization's DMZ. Consider a laptop owned by user Fred (who works for 
> the organization). Fred's laptop is configured to use the organization's 
> TURN server. Now consider what happens if Fred goes off to an IETF meeting.
> 
> Fred's laptop will still try to use O's TURN server, except now the TURN 
> server is being accessed from the Internet. At the IETF meeting, an 
> attacker can sniff the wireless network and see the TURN packets Fred's 
> laptop is exchanging with the TURN server. The attacker can then use 
> TURN to attack the other servers in the O's DMZ by sending a Send 
> indication to the TURN server with a PEER-ADDRESS attribute of the other 
> server. The attacker can do this because Send indications are not 
> authenticated. In this way, the attacker has bypassed any rules that the 
> Outer Firewall has installed about who may access the other servers in 
> the DMZ.
> 
>                                                    +---------------+
>                                                    | Fred's laptop |
>            +----------------+                      +---------------+
>    +-------| Outer Firewall |----------+
>    |       +----------------+          |
>    |                                   |
>    | +-------------+   +------------+  |
>    | | TURN server |   | Web Server |  |
>    | +-------------+   +------------+  |
>    |                                   |
>    |       +-----------------+         |
>    +-------| Inner Firewall  |---------+
>    |       +-----------------+         |
>    |                                   |
>    |     Organization's network        |
>    |                                   |
>    +-----------------------------------+
> 
> 
> Given this example, I am proposing to change to option (b). In other 
> words, the Server will drop an incoming Send indication unless there is 
> an active permission towards the IP address in the PEER-ADDRESS.
> 
> Comments?
> Does anyone think that we should address Cullen's example in another 
> way? Does anyone think that there are reasons a client would like the 
> behavior that option (a) offers?
> 
> - Philip
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct  6 08:47:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C19C128C1B7;
	Mon,  6 Oct 2008 08:47:02 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id B53723A688C; Mon,  6 Oct 2008 08:47:00 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081006154700.B53723A688C@core3.amsl.com>
Date: Mon,  6 Oct 2008 08:47:00 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-dccp (Network Address
 Translation (NAT) Behavioral Requirements for DCCP) to Proposed Standard
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'Network Address Translation (NAT) Behavioral Requirements for DCCP '
   <draft-ietf-behave-dccp-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-20. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-dccp-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17233&rfc_flag=0

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


From behave-bounces@ietf.org  Mon Oct  6 09:49:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 950CC3A6B16;
	Mon,  6 Oct 2008 09:49:24 -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 A57373A6B15
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 09:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.191
X-Spam-Level: 
X-Spam-Status: No, score=-6.191 tagged_above=-999 required=5 tests=[AWL=0.058, 
	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 dWBGXPvmM4Mq for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 09:49:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id BF7213A698E
	for <behave@ietf.org>; Mon,  6 Oct 2008 09:49:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	71B5F20B63; Mon,  6 Oct 2008 18:49:42 +0200 (CEST)
X-AuditID: c1b4fb3c-ad0ccbb0000015b5-4c-48ea41a64ef0
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	584E820C20; Mon,  6 Oct 2008 18:49:42 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 18:49:42 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 18:49:41 +0200
Message-ID: <48EA41A5.1080608@ericsson.com>
Date: Mon, 06 Oct 2008 18:49:41 +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>, Dave Thaler <dthaler@microsoft.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 06 Oct 2008 16:49:41.0943 (UTC)
	FILETIME=[875DE470:01C927D3]
X-Brightmail-Tracker: AAAAAA==
Subject: [BEHAVE] Additional WG co-chair for Behave
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

WG,

I have decided to add Dave Thaler (dthaler@microsoft.com) as an co-chair
for the BEHAVE WG to help Dan wing. This is in light of all the IPv4
IPv6 coexistence work that are coming into BEHAVE.

Chairs and ADs are working on rechartering of additional work in the
space of v4v6 coexistence. There will definitely be work items in
regards to Address Family Translation. It also looks like some of the
consideration of the more advanced proposals for providing IPv4
connectivity belongs in BEHAVE. You can expect more information in the
coming weeks.

Welcome Dave

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


From behave-bounces@ietf.org  Mon Oct  6 10:32:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B15E3A6AD4;
	Mon,  6 Oct 2008 10:32:38 -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 EABC03A6A28
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 10:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 r5-GBzmT0-qp for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 10:32:36 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1])
	by core3.amsl.com (Postfix) with ESMTP id 505D53A6A24
	for <behave@ietf.org>; Mon,  6 Oct 2008 10:32:36 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2])
	by where.matthew.at (Postfix) with ESMTP id 90FC214804D;
	Mon,  6 Oct 2008 10:32:30 -0700 (PDT)
Message-ID: <48EA4A87.6090606@matthew.at>
Date: Mon, 06 Oct 2008 10:27:35 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
In-Reply-To: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: matthew@matthew.at
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> TURN-10 introduces the CreatePermission request for creating or 
> updating a permission. With this new request comes the question of 
> what to do if the server receives a Send indication when no permission 
> is installed towards the peer. There are two options:
> a) Send the UDP datagram towards the peer anyway, or
> b) Drop the Send indication
>
> In TURN-10, we opted for (a) because there didn't seem to be any good 
> reason to do (b).  However, Cullen has now found an example where 
> option (a) seems to be a problem.
>
> Consider a TURN server operated by an organization O and located in 
> the organization's DMZ. Consider a laptop owned by user Fred (who 
> works for the organization). Fred's laptop is configured to use the 
> organization's TURN server. Now consider what happens if Fred goes off 
> to an IETF meeting.
>
> Fred's laptop will still try to use O's TURN server, except now the 
> TURN server is being accessed from the Internet. At the IETF meeting, 
> an attacker can sniff the wireless network and see the TURN packets 
> Fred's laptop is exchanging with the TURN server. The attacker can 
> then use TURN to attack the other servers in the O's DMZ by sending a 
> Send indication to the TURN server with a PEER-ADDRESS attribute of 
> the other server. The attacker can do this because Send indications 
> are not authenticated. In this way, the attacker has bypassed any 
> rules that the Outer Firewall has installed about who may access the 
> other servers in the DMZ.
>
I read TURN-10 again, and I don't see why the attacker can't simply send 
a CreatePermission before every Send, since there's nothing in 9.1 that 
says that CreatePermission requests must be authenticated.

I also have an example of a UDP network protocol that is becoming less 
and less TURN-friendly with the addition of CreatePermission and the 
stateful client behavior required to ensure that permissions are 
actually created first.

Matthew Kaufman
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct  6 11:53:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A98CA3A6452;
	Mon,  6 Oct 2008 11:53:51 -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 118733A6452
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 11:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5
	tests=[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 6zc9NbDHq27w for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 11:53:49 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215])
	by core3.amsl.com (Postfix) with ESMTP id 047663A63D2
	for <behave@ietf.org>; Mon,  6 Oct 2008 11:53:48 -0700 (PDT)
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Mon, 6 Oct 2008 11:52:38 -0700
Received: from tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.32) by tk5-exhub-c103.redmond.corp.microsoft.com
	(157.54.88.96)
	with Microsoft SMTP Server id 8.1.291.1; Mon, 6 Oct 2008 11:52:38 -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, 6 Oct 2008 11:52:50 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Behave WG
	<behave@ietf.org>
Date: Mon, 6 Oct 2008 11:52:34 -0700
Thread-Topic: Additional WG co-chair for Behave
Thread-Index: Ackn05+S2jdz4SzFQoGue/+MEOEkfwAEOrdA
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0B866941@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <48EA41A5.1080608@ericsson.com>
In-Reply-To: <48EA41A5.1080608@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [BEHAVE] Additional WG co-chair for Behave
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

Thanks Magnus,

Glad to help.  This is important work.

-Dave

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
Sent: Monday, October 06, 2008 9:50 AM
To: Behave WG; Dave Thaler
Subject: Additional WG co-chair for Behave

WG,

I have decided to add Dave Thaler (dthaler@microsoft.com) as an co-chair
for the BEHAVE WG to help Dan wing. This is in light of all the IPv4
IPv6 coexistence work that are coming into BEHAVE.

Chairs and ADs are working on rechartering of additional work in the
space of v4v6 coexistence. There will definitely be work items in
regards to Address Family Translation. It also looks like some of the
consideration of the more advanced proposals for providing IPv4
connectivity belongs in BEHAVE. You can expect more information in the
coming weeks.

Welcome Dave

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


From behave-bounces@ietf.org  Mon Oct  6 12:00:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E7DA28C21C;
	Mon,  6 Oct 2008 12:00:06 -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 A6FD028C1D9
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 12:00: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 B6J4NWCv+wxv for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 12:00:02 -0700 (PDT)
Received: from mail-08.primus.ca (mail4.primus.ca [216.254.141.171])
	by core3.amsl.com (Postfix) with ESMTP id 9FCDD28C139
	for <behave@ietf.org>; Mon,  6 Oct 2008 12:00:02 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KmvJj-0006lf-02; Mon, 06 Oct 2008 15:00:27 -0400
Message-Id: <72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: matthew@matthew.at
In-Reply-To: <48EA4A87.6090606@matthew.at>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 6 Oct 2008 15:00:24 -0400
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
	<48EA4A87.6090606@matthew.at>
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Mon, 6-Oct-08, at 13:27 , Matthew Kaufman wrote:

> I read TURN-10 again, and I don't see why the attacker can't simply  
> send a CreatePermission before every Send, since there's nothing in  
> 9.1 that says that CreatePermission requests must be authenticated.

TURN-10 says (section 4) that the server SHOULD require that all  
requests be authenticated, and that all clients MUST be prepared to  
authenticate requests if required. This language has been in the draft  
for a few versions now.


>
> I also have an example of a UDP network protocol that is becoming  
> less and less TURN-friendly with the addition of CreatePermission  
> and the stateful client behavior required to ensure that permissions  
> are actually created first.
>

I don't know your application protocol, but do you have an alternative  
suggestion for how to proceed? Is there something we can do to TURN to  
make things better?

- Philip




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


From behave-bounces@ietf.org  Mon Oct  6 12:57:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF7E33A6B1E;
	Mon,  6 Oct 2008 12:57:11 -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 0DB083A68DB
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 12:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.13
X-Spam-Level: 
X-Spam-Status: No, score=-1.13 tagged_above=-999 required=5 tests=[AWL=-0.300, 
	BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745,
	J_CHICKENPOX_74=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 QoJVCV-oS+gf for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 12:57:10 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1])
	by core3.amsl.com (Postfix) with ESMTP id 258183A6ACE
	for <behave@ietf.org>; Mon,  6 Oct 2008 12:57:10 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2])
	by where.matthew.at (Postfix) with ESMTP id 616DD14807F;
	Mon,  6 Oct 2008 12:57:45 -0700 (PDT)
Message-ID: <48EA6C92.5070701@matthew.at>
Date: Mon, 06 Oct 2008 12:52:50 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
	<48EA4A87.6090606@matthew.at>
	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
In-Reply-To: <72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: matthew@matthew.at
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> I don't know your application protocol, but do you have an alternative 
> suggestion for how to proceed? Is there something we can do to TURN to 
> make things better?
>
What I need is a way to establish a channel between my application and 
the proxy (auto-discovery of the proxy via DHCP would be nice for the 
corporate IT-provided proxy case), optionally authenticate with the 
proxy (optionally, because some IT organizations might be sufficiently 
comfortable with the idea of allowing everyone on the "inside" net to 
use the proxy without authentication), and then once that channel is 
open to use it to send traffic to any UDP address+port while ensuring 
that return traffic comes back over the same channel as well. Once the 
channel is established and authenticated to the proxy, I'd like to see 
there be nothing but encapsulation required as far as client logic goes, 
as the more heavy-weight the communication and/or logic needs to be, 
especially on a per-destination basis, the less suitable the proxy 
protocol becomes.

My application establishes the proxy connection at startup, but does not 
use its UDP network protocol stack to open network sessions with far 
endpoints until later (sometimes a very short time later, sometimes 
longer), and when creating those network sessions it sends UDP packets 
to several candidate endpoint addresses in parallel, then sticking with 
the one that actually worked. It does this work in parallel in order to 
reduce the latency between a request to open a session and the time the 
session is up, which is the same reason that the session establishment 
is fine-tuned to bring up an encrypted network session in just 2 RTTs. 
The longer it takes to establish a session to a new endpoint, the worse 
the user experience is.

Requiring that each possible candidate address have a permission 
installed beforehand means that either there's extra RTTs (and traffic) 
between the proxy server and the application in order to wait for the 
permissions to be verified, or even more traffic generated by the 
asynchronous implementation of sending a permission request before every 
send that is to an address for which a permission grant hasn't (yet) 
been received. RTT to the proxy matters in cases where a company has an 
office in India but proxies all their external Internet via the US, a 
not-uncommon situation.

TURN has slowly moved from being almost exactly the right proxy protocol 
for this application to one which is now very close to being inferior 
enough that we'd switch to a proprietary proxy protocol instead, which 
has disadvantages for both the TURN effort (because our application 
would no longer be a driver for TURN deployment) and our users (because 
they'd be more limited in their choice of proxies).

Matthew Kaufman
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct  6 13:29:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A50328C0DB;
	Mon,  6 Oct 2008 13:29:06 -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 5A4553A6A32
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 13:29:05 -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 2uEoRBjq+U2Y for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 13:29:04 -0700 (PDT)
Received: from mail-05.primus.ca (mail4.primus.ca [216.254.141.171])
	by core3.amsl.com (Postfix) with ESMTP id 415483A68F6
	for <behave@ietf.org>; Mon,  6 Oct 2008 13:29:04 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KmwgE-0006dV-02; Mon, 06 Oct 2008 16:27:46 -0400
Message-Id: <D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: matthew@matthew.at
In-Reply-To: <48EA6C92.5070701@matthew.at>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 6 Oct 2008 16:29:39 -0400
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
	<48EA4A87.6090606@matthew.at>
	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
	<48EA6C92.5070701@matthew.at>
X-Mailer: Apple Mail (2.926)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Mon, 6-Oct-08, at 15:52 , Matthew Kaufman wrote:

> Philip Matthews wrote:
>> I don't know your application protocol, but do you have an  
>> alternative suggestion for how to proceed? Is there something we  
>> can do to TURN to make things better?
>>
> What I need is a way to establish a channel between my application  
> and the proxy (auto-discovery of the proxy via DHCP would be nice  
> for the corporate IT-provided proxy case), optionally authenticate  
> with the proxy (optionally, because some IT organizations might be  
> sufficiently comfortable with the idea of allowing everyone on the  
> "inside" net to use the proxy without authentication), and then once  
> that channel is open to use it to send traffic to any UDP address 
> +port while ensuring that return traffic comes back over the same  
> channel as well. Once the channel is established and authenticated  
> to the proxy, I'd like to see there be nothing but encapsulation  
> required as far as client logic goes, as the more heavy-weight the  
> communication and/or logic needs to be, especially on a per- 
> destination basis, the less suitable the proxy protocol becomes.
>
> My application establishes the proxy connection at startup, but does  
> not use its UDP network protocol stack to open network sessions with  
> far endpoints until later (sometimes a very short time later,  
> sometimes longer), and when creating those network sessions it sends  
> UDP packets to several candidate endpoint addresses in parallel,  
> then sticking with the one that actually worked. It does this work  
> in parallel in order to reduce the latency between a request to open  
> a session and the time the session is up, which is the same reason  
> that the session establishment is fine-tuned to bring up an  
> encrypted network session in just 2 RTTs. The longer it takes to  
> establish a session to a new endpoint, the worse the user experience  
> is.
>
> Requiring that each possible candidate address have a permission  
> installed beforehand means that either there's extra RTTs (and  
> traffic) between the proxy server and the application in order to  
> wait for the permissions to be verified, or even more traffic  
> generated by the asynchronous implementation of sending a permission  
> request before every send that is to an address for which a  
> permission grant hasn't (yet) been received. RTT to the proxy  
> matters in cases where a company has an office in India but proxies  
> all their external Internet via the US, a not-uncommon situation.
>
> TURN has slowly moved from being almost exactly the right proxy  
> protocol for this application to one which is now very close to  
> being inferior enough that we'd switch to a proprietary proxy  
> protocol instead, which has disadvantages for both the TURN effort  
> (because our application would no longer be a driver for TURN  
> deployment) and our users (because they'd be more limited in their  
> choice of proxies).

Note that TURN does not REQUIRE that the server use authentication --  
there may be situations where authentication is not required. However,  
the security of TURN without authentication is poor.

I don't know how much data your client sends to each peer, but if  
there is a fair amount of data, then you will probably want to bind a  
channel to each peer to reduce overhead (from 36 bytes to 4 bytes).  
Two notes when using channels. First, a ChannelBind creates both a  
channel and a permission. Second, there is nothing that stops your  
application from sending ChannelData messages immediately after  
sending the ChannelBind request. In most cases, everything will work  
fine. It is only if the ChannelBind fails that you will have to recover.

Do you have a suggestion for another way to do things? What would you  
do in a proprietary protocol that is different from the way TURN works?

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct  6 13:33:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD6AD3A6B3C;
	Mon,  6 Oct 2008 13:33:59 -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 29FAB3A6B3C
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 13:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.28
X-Spam-Level: 
X-Spam-Status: No, score=-1.28 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 sa6Q48YrHczs for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 13:33:57 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1])
	by core3.amsl.com (Postfix) with ESMTP id 67A1A3A6804
	for <behave@ietf.org>; Mon,  6 Oct 2008 13:33:57 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2])
	by where.matthew.at (Postfix) with ESMTP id C1581148068;
	Mon,  6 Oct 2008 13:34:34 -0700 (PDT)
Message-ID: <48EA7533.8040200@matthew.at>
Date: Mon, 06 Oct 2008 13:29:39 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
In-Reply-To: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: matthew@matthew.at
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Meanwhile...

Philip Matthews wrote:
>
> Consider a TURN server operated by an organization O and located in 
> the organization's DMZ. Consider a laptop owned by user Fred (who 
> works for the organization). Fred's laptop is configured to use the 
> organization's TURN server. Now consider what happens if Fred goes off 
> to an IETF meeting.
>
> Fred's laptop will still try to use O's TURN server, except now the 
> TURN server is being accessed from the Internet. At the IETF meeting, 
> an attacker can sniff the wireless network and see the TURN packets 
> Fred's laptop is exchanging with the TURN server. The attacker can 
> then use TURN to attack the other servers in the O's DMZ by sending a 
> Send indication to the TURN server with a PEER-ADDRESS attribute of 
> the other server. The attacker can do this because Send indications 
> are not authenticated. In this way, the attacker has bypassed any 
> rules that the Outer Firewall has installed about who may access the 
> other servers in the DMZ.

1. Fred's laptop shouldn't be able to reach O's TURN server, because if 
O wants their TURN server in their DMZ to be only used by members of 
their organization, they should have either set up the TURN server to 
only talk TURN to/from the inside net and/or set up the DMZ-Outside 
firewall to block inbound TURN traffic from the outside from even 
reaching the TURN server.

2. If Fred still needs to use his organization's TURN server, he should 
VPN in to work and then he'd be on the inside net and able to use the 
TURN server.

3. Perhaps send indications shouldn't be allowed for clients that have 
not successfully Allocated, rather than for clients that have not 
successfully CreatePermissioned. If the attacker cannot forge source 
addresses, then the behavior is the same as proposed. If the attacker 
can forge source addresses, then even in the proposed change they can 
still generate packets for any host that Fred has already done a 
CreatePermission for (which is potentially just as bad) *or* that Fred 
can be convinced by some means to do a CreatePermission for (e.g., DNS 
spoofing) (which leads us right back to where we were before).

Given the relatively low security of TURN, I think that an organization 
that lets outside users talk to a TURN server in their DMZ is going to 
have to protect the TURN server from talking to other things in the DMZ 
that it isn't supposed to reach anyway, no matter which proposal is adopted.

Since the proposal makes my client have to do more work for questionable 
benefit, I'm not in favor of it.


Matthew Kaufman

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


From behave-bounces@ietf.org  Mon Oct  6 13:42:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C14403A68AF;
	Mon,  6 Oct 2008 13:42:40 -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 668A03A6AA5
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 13:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096, 
	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 ygmweMzsXFo5 for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 13:42:38 -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 96B863A676A
	for <behave@ietf.org>; Mon,  6 Oct 2008 13:42:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,369,1220227200"; d="scan'208";a="169862880"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 06 Oct 2008 20:43:13 +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 m96KhDhA018498; 
	Mon, 6 Oct 2008 13:43:13 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m96KhDYk000277;
	Mon, 6 Oct 2008 20:43:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dave Thaler'" <dthaler@windows.microsoft.com>,
	"'Magnus Westerlund'" <magnus.westerlund@ericsson.com>,
	"'Behave WG'" <behave@ietf.org>
References: <48EA41A5.1080608@ericsson.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A0B866941@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Date: Mon, 6 Oct 2008 13:43:13 -0700
Message-ID: <01e501c927f4$270c70c0$c2f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0A0B866941@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Thread-Index: Ackn05+S2jdz4SzFQoGue/+MEOEkfwAEOrdAAAPj47A=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1926; t=1223325793;
	x=1224189793; 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[BEHAVE]=20Additional=20WG=20co-chair=2
	0for=20Behave |Sender:=20;
	bh=yy6rkgbpOE3UHPHb7SVtKOInBw3JNLG6DGbaVCfNAfM=;
	b=rHPtGJ2rTJ/YZqWsC5sr+s2dL3DOoTSAllAhwB6/Cg12Fpq8NpNA6DjxcN
	JGyjd2w8sbbxVeifbasifX4b0JZazvVZkkH0Xf/XUJu4qde2beO26J+DH+Nx
	0LEJoFY79l;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [BEHAVE] Additional WG co-chair for Behave
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

Thanks for volunteering, Dave!

-d
 =


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

> [mailto:behave-bounces@ietf.org] On Behalf Of Dave Thaler
> Sent: Monday, October 06, 2008 11:53 AM
> To: Magnus Westerlund; Behave WG
> Subject: Re: [BEHAVE] Additional WG co-chair for Behave
> =

> Thanks Magnus,
> =

> Glad to help.  This is important work.
> =

> -Dave
> =

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Monday, October 06, 2008 9:50 AM
> To: Behave WG; Dave Thaler
> Subject: Additional WG co-chair for Behave
> =

> WG,
> =

> I have decided to add Dave Thaler (dthaler@microsoft.com) as =

> an co-chair
> for the BEHAVE WG to help Dan wing. This is in light of all the IPv4
> IPv6 coexistence work that are coming into BEHAVE.
> =

> Chairs and ADs are working on rechartering of additional work in the
> space of v4v6 coexistence. There will definitely be work items in
> regards to Address Family Translation. It also looks like some of the
> consideration of the more advanced proposals for providing IPv4
> connectivity belongs in BEHAVE. You can expect more information in the
> coming weeks.
> =

> Welcome Dave
> =

> 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

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


From behave-bounces@ietf.org  Mon Oct  6 13:44:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C0FA33A6B3C;
	Mon,  6 Oct 2008 13:44:38 -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 6F7E83A69EA
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 13:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.33
X-Spam-Level: 
X-Spam-Status: No, score=-1.33 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 pRcT6XOVb0LX for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 13:44:36 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1])
	by core3.amsl.com (Postfix) with ESMTP id ADB5C3A6B39
	for <behave@ietf.org>; Mon,  6 Oct 2008 13:44:36 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2])
	by where.matthew.at (Postfix) with ESMTP id ECD4D148065;
	Mon,  6 Oct 2008 13:45:08 -0700 (PDT)
Message-ID: <48EA77AD.2050100@matthew.at>
Date: Mon, 06 Oct 2008 13:40:13 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
	<48EA4A87.6090606@matthew.at>
	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
	<48EA6C92.5070701@matthew.at>
	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>
In-Reply-To: <D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: matthew@matthew.at
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
>
> Note that TURN does not REQUIRE that the server use authentication -- 
> there may be situations where authentication is not required. However, 
> the security of TURN without authentication is poor.
>
For the IT-organization-provided-proxy case, it needs to be as good as 
the HTTP proxy is. Which is to say "anyone who can speak port 80 from an 
inside address on the inside network interface is A-OK."

> I don't know how much data your client sends to each peer, but if 
> there is a fair amount of data, then you will probably want to bind a 
> channel to each peer to reduce overhead (from 36 bytes to 4 bytes). 
> Two notes when using channels. First, a ChannelBind creates both a 
> channel and a permission. Second, there is nothing that stops your 
> application from sending ChannelData messages immediately after 
> sending the ChannelBind request. In most cases, everything will work 
> fine. It is only if the ChannelBind fails that you will have to recover.
>
The amount of data the client sends to each peer is very small 
(potentially just a single packet) when doing session establishment. I 
don't want to pay for either the ChannelBind or CreatePermission cost to 
get set up to send a single packet to a candidate address that is quite 
likely to fail. Once I have a session established then yes, there's an 
overhead reduction to be had by doing ChannelBind at the cost of 
additional client logic that isn't needed for the native UDP case. Since 
in the IT-provided-proxy case we usually care more about PPS than BPS, 
the extra 32 bytes aren't actually that big a deal except when the proxy 
is on a different continent. But again, until I've done my initial round 
of packets to potential candidate addresses, received a response, and 
completed my 2nd pair of handshake, I need a lightweight way of talking 
to lots more addresses than I want to do ChannelBind for.
> Do you have a suggestion for another way to do things? What would you 
> do in a proprietary protocol that is different from the way TURN works?
If we did our own protocol we would make the permission mechanism be an 
up-front authentication followed by the ability to send to any address 
(and get the return traffic), and once we moved away from TURN we'd 
probably also use proxy-session-identifying tags so that the proxy could 
do the same kind of IP address mobility our transport protocol supports. 
(It would mean that the proxy could identify that this packet was from 
someone who had already allocated/authenticated but who has moved to a 
new IP address (perhaps plugged in at a podium ethernet jack after being 
on wireless) and then after a challenge/response switch the proxy 
permission to be associated with the new address). Right now, if a 
client is forced by IT to go through a TURN proxy, they lose the IP 
address mobility they would have had if they could talk native UDP to 
the outside.

Matthew Kaufman


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


From behave-bounces@ietf.org  Mon Oct  6 15:13:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E87528C135;
	Mon,  6 Oct 2008 15:13:18 -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 10AF73A68C4
	for <behave@core3.amsl.com>; Mon,  6 Oct 2008 15:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	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 RUF+gg71HzFC for <behave@core3.amsl.com>;
	Mon,  6 Oct 2008 15:13:15 -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 6A7C928C135
	for <behave@ietf.org>; Mon,  6 Oct 2008 15:13:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,369,1220227200"; 
	d="txt'?scan'208";a="47930887"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-5.cisco.com with ESMTP; 06 Oct 2008 22:13:52 +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 m96MDqGr014543; 
	Mon, 6 Oct 2008 15:13:52 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m96MDqUk019823;
	Mon, 6 Oct 2008 22:13:52 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
References: 
Date: Mon, 6 Oct 2008 15:13:52 -0700
Message-ID: <028801c92800$d0fe2f40$c2f0200a@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0289_01C927C6.249F5740"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: 
Thread-Index: AckYQ4VdB/IMxxSQSqWlPe0biz8Y3gPvRHRg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9250; t=1223331232;
	x=1224195232; 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=20WGLC=3A=20draft-ietf-behave-stun-test-v
	ectors-03 |Sender:=20;
	bh=7+J4YMGDwiSLEkM2IBby+cqPbEDRF/pS3lt3qp5WI5I=;
	b=F/Z+YzHY6TNDWV+hD/cTIxcnXz8MbSp93qfbpmGS5qMzcY6MOUzutOm7bo
	H3OTUM5hrkvYr2AVaZfwPSN2J8Z5ZSxqi3zK4eWvvd3zLGwB8t1XUd0IWKpK
	ruLFygujV4;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave-chairs@tools.ietf.org, 'Dave Thaler' <dthaler@windows.microsoft.com>
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-stun-test-vectors-03
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0289_01C927C6.249F5740
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

WGLC for draft-ietf-behave-stun-test-vectors-03 has concluded; the only
comment received was Marc Petit-Huguenin saying the test vectors are =
good.  I
have requested publication.  For those interested, the PROTO writeup is
attached.

-d


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]=20
> Sent: Tuesday, September 16, 2008 2:31 PM
> To: 'Behave WG'
> Cc: 'R=E9mi Denis-Courmont'
> Subject: WGLC: draft-ietf-behave-stun-test-vectors-03
>=20
> We are starting a two-week WGLC for "Test vectors for STUN",=20
> draft-ietf-behave-stun-test-vectors-03,=20
> http://tools.ietf.org/html/draft-ietf-behave-stun-test-vectors-03
>=20
> The WGLC ends on Tuesday, September 30.
>=20
> Please send your comments to the list.
>=20
> -d
>=20

------=_NextPart_000_0289_01C927C6.249F5740
Content-Type: text/plain;
	name="proto-stun-test-vectors.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="proto-stun-test-vectors.txt"

PROTO writeup for draft-ietf-behave-stun-test-vectors-03
PROTO writeup date: 6-Oct-2008


   (1.a)  Who is the Document Shepherd for this document? 

Dan Wing, dwing@cisco.com

          Has the
          Document Shepherd personally reviewed this version of the
          document and, in particular, does he or she believe this
          version is ready for forwarding to the IESG for publication?

Yes.


   (1.b)  Has the document had adequate review both from key WG members
          and from key non-WG members?  Does the Document Shepherd have
          any concerns about the depth or breadth of the reviews that
          have been performed?

This document has been reviewed by several implementors, who all 
concur it is accurate.  Most recently:

http://www.ietf.org/mail-archive/web/behave/current/msg04367.html


   (1.c)  Does the Document Shepherd have concerns that the document
          needs more review from a particular or broader perspective,
          e.g., security, operational complexity, someone familiar with
          AAA, internationalization, or XML?

No concerns.


   (1.d)  Does the Document Shepherd have any specific concerns or
          issues with this document that the Responsible Area Director
          and/or the IESG should be aware of?  For example, perhaps he
          or she is uncomfortable with certain parts of the document, or
          has concerns whether there really is a need for it.  In any
          event, if the WG has discussed those issues and has indicated
          that it still wishes to advance the document, detail those
          concerns here. 

The only concern was if this document should be included as an 
appendix to draft-ietf-behave-rfc3489bis.  The author prefers a 
standalone document, and the WG and the chair are comfortable with
a separate document.


          Has an IPR disclosure related to this document
          been filed?  If so, please include a reference to the
          disclosure and summarize the WG discussion and conclusion on
          this issue.

There is no IPR on this document.


   (1.e)  How solid is the WG consensus behind this document?  Does it
          represent the strong concurrence of a few individuals, with
          others being silent, or does the WG as a whole understand and
          agree with it?

It represents strong consensus.



   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize the areas of conflict in
          separate email messages to the Responsible Area Director.  (It
          should be in a separate email because this questionnaire is
          entered into the ID Tracker.)


There is no discontent of any sort with this document.


   (1.g)  Has the Document Shepherd personally verified that the
          document satisfies all ID nits?  (See
          http://www.ietf.org/ID-Checklist.html and
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are
          not enough; this check needs to be thorough.  Has the document
          met all formal review criteria it needs to, such as the MIB
          Doctor, media type, and URI type reviews?  If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

All ID nits are satisfied.

Intended status:  informational (which also appears on the first page)


   (1.h)  Has the document split its references into normative and
          informative? 

Yes; there are no informational references.


          Are there normative references to documents that
          are not ready for advancement or are otherwise in an unclear
          state?  If such normative references exist, what is the
          strategy for their completion? 

Two documents are normatively referenced, ICE and RFC3489bis.  Both
are in RFC Editor's queue.


          Are there normative references
          that are downward references, as described in [RFC3967]? 

No, they are upward references.


          If
          so, list these downward references to support the Area
          Director in the Last Call procedure for them [RFC3967].

   (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations section exists and is consistent with the body
          of the document? 

Yes; this document has no IANA considerations, and none are needed.


          If the document specifies protocol
          extensions, are reservations requested in appropriate IANA
          registries?  Are the IANA registries clearly identified?  If
          the document creates a new registry, does it define the
          proposed initial contents of the registry and an allocation
          procedure for future registrations?  Does it suggest a
          reasonable name for the new registry?  See [RFC2434].  If the
          document describes an Expert Review process, has the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

   (1.j)  Has the Document Shepherd verified that sections of the
          document that are written in a formal language, such as XML
          code, BNF rules, MIB definitions, etc., validate correctly in
          an automated checker?


The C code, in Appendix A, has been verified to compile.


   (1.k)  The IESG approval announcement includes a Document
          Announcement Write-Up.  Please provide such a Document
          Announcement Write-Up.  Recent examples can be found in the
          "Action" announcements for approved documents.  The approval
          announcement contains the following sections:

          Technical Summary
             Relevant content can frequently be found in the abstract
             and/or introduction of the document.  If not, this may be
             an indication that there are deficiencies in the abstract
             or introduction.


Technical Summary:

The Session Traversal Utilities for NAT (STUN) protocol defines 
two STUN attributes -- FINGERPRINT and MESSAGE-INTEGRITY -- that 
may be included in STUN messages.  This document provides test 
vectors for those two attributes.


          Working Group Summary
             Was there anything in the WG process that is worth noting?
             For example, was there controversy about particular points
             or were there decisions where the consensus was
             particularly rough?

No.

          Document Quality
             Are there existing implementations of the protocol?

Yes, and this document helps implementors with one of the more difficult
parts of implementing the protocol.

             Have a
             significant number of vendors indicated their plan to
             implement the specification?  Are there any reviewers that
             merit special mention as having done a thorough review,
             e.g., one that resulted in important changes or a
             conclusion that the document had no substantive issues? 

There have been several reviews, but no substantial changes since initial
publication of the document.

             If
             there was a MIB Doctor, Media Type, or other Expert Review,
             what was its course (briefly)?  In the case of a Media Type
             Review, on what date was the request posted?

None needed.

          Personnel
             Who is the Document Shepherd for this document? 

Dan Wing, dwing@cisco.com

             Who is the
             Responsible Area Director? 

Magnus Westerlund, magnus.westerlund@ericsson.com

             If the document requires IANA
             experts(s), insert 'The IANA Expert(s) for the registries
             in this document are <TO BE ADDED BY THE AD>.'


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

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

------=_NextPart_000_0289_01C927C6.249F5740--



From behave-bounces@ietf.org  Mon Oct  6 15:21:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 75EBB3A6935;
	Mon,  6 Oct 2008 15:21:41 -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 0ED1528C1A8;
	Mon,  6 Oct 2008 10:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=0.900, 
	BAYES_00=-2.599, 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 cMuRDp+yqFNY; Mon,  6 Oct 2008 10:04:30 -0700 (PDT)
Received: from cox.com (post3.cox.com [24.248.72.35])
	by core3.amsl.com (Postfix) with ESMTP id DDE3628C114;
	Mon,  6 Oct 2008 10:04:28 -0700 (PDT)
Received: from ([192.168.72.254])
	by post3.cox.com with ESMTP  id 5503596.66809567;
	Mon, 06 Oct 2008 13:04:40 -0400
Received: from CATL0MS21.CORP.COX.COM ([10.64.210.21]) by
	catl0ms22.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 13:04:39 -0400
Received: from CATL0MS01.corp.cox.com ([10.62.210.87]) by
	CATL0MS21.CORP.COX.COM with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 13:04:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 13:04:38 -0400
Message-ID: <8720A864484AB04082CD55A4AEAADAB60481CE72@CATL0MS01.corp.cox.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-ietf-behave-dccp (Network Address Translation
	(NAT) Behavioral Requirements for DCCP) to Proposed Standard 
Thread-Index: AcknyvyKmb28/Ne4STqqaKhrZqxqBgACqCIQ
From: <Jason.Weil@cox.com>
To: <ietf@ietf.org>,
	<ietf-announce@ietf.org>
X-OriginalArrivalTime: 06 Oct 2008 17:04:39.0618 (UTC)
	FILETIME=[9E6C3A20:01C927D5]
X-Mailman-Approved-At: Mon, 06 Oct 2008 15:21:40 -0700
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Last Call: draft-ietf-behave-dccp (Network Address
	Translation (NAT) Behavioral Requirements for DCCP) to
	Proposed Standard
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Cxvvv

----- Original Message -----
From: ietf-announce-bounces@ietf.org <ietf-announce-bounces@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: behave@ietf.org <behave@ietf.org>
Sent: Mon Oct 06 11:47:00 2008
Subject: Last Call: draft-ietf-behave-dccp (Network Address Translation (NAT) Behavioral Requirements for DCCP) to Proposed Standard 

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'Network Address Translation (NAT) Behavioral Requirements for DCCP '
   <draft-ietf-behave-dccp-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-20. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-dccp-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17233&rfc_flag=0

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct  7 10:03:13 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09CF43A6B5C;
	Tue,  7 Oct 2008 10:03:13 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id DBA233A6B4F; Tue,  7 Oct 2008 10:03:11 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081007170311.DBA233A6B4F@core3.amsl.com>
Date: Tue,  7 Oct 2008 10:03:11 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] Last Call: draft-ietf-behave-stun-test-vectors (Test
 vectors for STUN) to Informational RFC
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

The IESG has received a request from the Behavior Engineering for 
Hindrance Avoidance WG (behave) to consider the following document:

- 'Test vectors for STUN '
   <draft-ietf-behave-stun-test-vectors-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-21. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-behave-stun-test-vectors-03.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16804&rfc_flag=0

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


From behave-bounces@ietf.org  Tue Oct  7 13:28:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99F7D3A69A9;
	Tue,  7 Oct 2008 13:28:04 -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 2A32D3A6924
	for <behave@core3.amsl.com>; Tue,  7 Oct 2008 13:28:03 -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 Edv3Gtrh22sR for <behave@core3.amsl.com>;
	Tue,  7 Oct 2008 13:28:02 -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 42BB93A686C
	for <behave@ietf.org>; Tue,  7 Oct 2008 13:28:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,375,1220227200"; d="scan'208";a="170635556"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 07 Oct 2008 20:28:42 +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 m97KSgl3007290; 
	Tue, 7 Oct 2008 13:28:42 -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 m97KSgf9001431;
	Tue, 7 Oct 2008 20:28:42 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Tue, 7 Oct 2008 13:28:41 -0700
Message-ID: <004001c928bb$49d12b10$35666b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ackou0m7T1l7JY9qTqOZY5GsZkwWpA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3248; t=1223411322;
	x=1224275322; 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:=20WGLC=3A=20draft-ietf-behave-nat-icmp-09=20
	|Sender:=20; bh=MuGjWNE4bJVeQiyuloV/URcJgf9UT678HJ5u+hPvp9c=;
	b=OXFQPI9cfxYqstduQr7Wq/Tqb4hBOaaYprA5/TDZezXOaNnWmtI6Een9XG
	kbG9hV2vDhiPRBIV1269+uMpZQ1ZVemdCfRkrCsshNjmyL8O/kvd/wyQ9JxJ
	OTyQ6MUAqM;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave-chairs@tools.ietf.org
Subject: [BEHAVE] WGLC: draft-ietf-behave-nat-icmp-09
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

During IESG evaluation a DISCUSS was raised regarding the Section 4.3 RFC1812
conformance requirement.  As a result section 7.0 of
draft-ietf-behave-nat-icmp-09 was changed to specify which ICMP messages need
to be supported by a NAT.  The new text from -09 is below, and you can also
find it at:

http://tools.ietf.org/html/draft-ietf-behave-nat-icmp-09
and side-by-side diffs are available by clicking "Diff2".

The DISCUSS can be found at
https://datatracker.ietf.org/idtracker/draft-ietf-behave-nat-icmp/


I expect there may be some reaction to certain ICMP messages being in the
MUST/MAY/SHOULD NOT category -- please look this over and comment.  I will
wait one week, until October 14, before progressing the document.  Please send
comments to behave@ietf.org or the chairs.

Thanks.
-d

-----

   7. Conformance to RFC 1812

   NAT devices should follow the best current practices of modern
   routers when handling ICMP messages, as specified in Section 4.3 of
   [RFC1812].  However, since the publication of RFC1812 some of its
   requirements are no longer best current practices.  Thus, the
   following requirements are derived from RFC1812 and apply to NATs
   compliant with this specification:

   REQ-9: A NAT device MAY implement a policy control that prevents
   ICMP messages being generated toward certain interface(s).
   Implementation of such a policy control overrides the MUSTs in
   REQ-10.

   REQ-10: Unless overridden by REQ-9's policy, a NAT device needs to
   support ICMP messages as below, some conforming to Section 4.3 of
   [RFC1812] and some superseding the requirements of Section 4.3 of
   [RFC1812].
       a. MUST support:
          1. Destination Unreachable Message, as described in
             Section 7.1 of this document,
          2. Time Exceeded Message, as described in Section 7.2 of
             of this document,
          3. Parameter Problem Message, as described in
             Section 4.3.3.5 of [RFC1812],
          4. Echo Request/Reply Messages, as described in REQ-1,
          5. Router Advertisement and Solicitations, as described in
             Section 4.3.3.10 of [RFC1812].

       b. MAY support:
          1. Redirect Message, as described in Section 4.3.3.2 of
             [RFC1812],
          2. Source Route Options, as described in Section 7.3 of
             this document,
          3. Timestamp and TimeStamp Reply Messages, as described in
             Section 4.3.3.8 of [RFC1812],
          4. Address Mask Request/Reply Message, as described in
             Section 7.4 of this document.

       c. SHOULD NOT support:
          1. Source Quench Message, as described in Section 4.3.3.3
             of [RFC1812],
          2. Information Request/reply, as described in
             Section 4.3.3.7 of [RFC1812]).

   In addition, a NAT device is RECOMMENDED to conform to the following
   implementation considerations in [RFC1812]:
       d. TOS and Precedence, as described in Section 4.3.2.5 of
          [RFC1812],
       e. When Not to Send ICMP Errors, as described in
          Section 4.3.2.7 of [RFC1812],
       f. Rate Limiting, as described in Section 4.3.2.8 of [RFC1812].

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


From behave-bounces@ietf.org  Wed Oct  8 12:28:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 232EB3A6BD6;
	Wed,  8 Oct 2008 12:28:29 -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 3EEE63A6BB5;
	Wed,  8 Oct 2008 12:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, 
	RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.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 PZyaYJ9t1ZZi; Wed,  8 Oct 2008 12:28:27 -0700 (PDT)
Received: from smtp1.xmundo.net (unknown [201.216.232.80])
	by core3.amsl.com (Postfix) with ESMTP id 8F3023A6B92;
	Wed,  8 Oct 2008 12:28:25 -0700 (PDT)
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id B5ACB6B6854;
	Wed,  8 Oct 2008 16:21:25 -0300 (ART)
Received: from notebook.gont.com.ar (host15.190-139-184.telecom.net.ar
	[190.139.184.15]) (authenticated bits=0)
	by venus.xmundo.net (8.14.1/8.13.8) with ESMTP id m98JLBYV015522;
	Wed, 8 Oct 2008 16:21:13 -0300
Message-Id: <200810081921.m98JLBYV015522@venus.xmundo.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 08 Oct 2008 16:15:07 -0300
To: Behave WG <behave@ietf.org>, "'Internet Area'" <int-area@ietf.org>
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <004101c928bb$be0e3f90$35666b80@cisco.com>
References: <004101c928bb$be0e3f90$35666b80@cisco.com>
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0 (venus.xmundo.net [201.216.232.56]);
	Wed, 08 Oct 2008 16:21:24 -0300 (ART)
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

At 05:31 p.m. 07/10/2008, Dan Wing wrote:

>    REQ-9: A NAT device MAY implement a policy control that prevents
>    ICMP messages being generated toward certain interface(s).
>    Implementation of such a policy control overrides the MUSTs in
>    REQ-10.

Then.... shouldn't the requirements be "SHOULD"s rather than "MUST"s?



>    REQ-10: Unless overridden by REQ-9's policy, a NAT device needs to
>    support ICMP messages as below, some conforming to Section 4.3 of
>    [RFC1812] and some superseding the requirements of Section 4.3 of
>    [RFC1812].
>        a. MUST support:
>          1. Destination Unreachable Message, as described in
>              Section 7.1 of this document,
>           2. Time Exceeded Message, as described in Section 7.2 of
>              of this document,
>           3. Parameter Problem Message, as described in
>              Section 4.3.3.5 of [RFC1812],
>           4. Echo Request/Reply Messages, as described in REQ-1,
>           5. Router Advertisement and Solicitations, as described in
>              Section 4.3.3.10 of [RFC1812].

Does anybody actually use these ICMPv4 messages? I do recall Windows 
systems sending these messages when they are bootstrapped, but...



>        b. MAY support:
>           1. Redirect Message, as described in Section 4.3.3.2 of
>              [RFC1812],

If anything, I'd add that support should default to "off".



>           2. Source Route Options, as described in Section 7.3 of
>              this document,

The draft says:
"If a NAT device does not support forwarding packets with
    the source route option, the NAT device SHOULD NOT forward
    outbound ICMP messages that contain source route option in the
    outer or inner ICMP header."

s/ICMP header/IP header/



>           4. Address Mask Request/Reply Message, as described in
>              Section 7.4 of this document.

AFAIK, these messages are not used in practice (even when a number of 
systems support them). Shouldn't they be deprecated as with the 
information request/response?

Last, but not least:

In Section 7.1.2, the draft says:
"   When NAT device is the recipient of "Packet Too Big" ICMP message
    from the network, the NAT device MUST forward the ICMP message back
    to the intended recipient, pursuant to the previously stated
    requirements REQ-3, REQ-4, REQ-5 and REQ-6."

Does REQ-6 really apply here? (ICMP PTBs are not query/response messages)

Kind regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




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


From behave-bounces@ietf.org  Wed Oct  8 16:37:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C2A303A6BF6;
	Wed,  8 Oct 2008 16:37:46 -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 26AD23A6BEB
	for <behave@core3.amsl.com>; Wed,  8 Oct 2008 16:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.129
X-Spam-Level: 
X-Spam-Status: No, score=-1.129 tagged_above=-999 required=5
	tests=[AWL=-0.490, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 rpa8ujVmcrHl for <behave@core3.amsl.com>;
	Wed,  8 Oct 2008 16:37:44 -0700 (PDT)
Received: from web33303.mail.mud.yahoo.com (web33303.mail.mud.yahoo.com
	[68.142.206.118])
	by core3.amsl.com (Postfix) with SMTP id 17A5B3A6BE6
	for <behave@ietf.org>; Wed,  8 Oct 2008 16:37:44 -0700 (PDT)
Received: (qmail 93701 invoked by uid 60001); 8 Oct 2008 23:38:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
	b=ZnjNnpW2Uc7QrN68qGC/dBfdv6FRYR6j7pa/sNVi+dS9zuJOm4741HywJeb65dd81PICCaOfOhMGZP16ng6KgQYbT53LCDPEn1f8gYR5c6RWYUPrg9YlsjglE2rbirdAk1Ob7uSF0Whv2sw/0AsCp51jCxdgzHTfXMuKXqieelo=;
X-YMail-OSG: GJwjTWEVM1k36w3jMHVKMQC.iNLGCTdBXU7LxvJXV1maE5w6lle5yWllDh.5kt8LdhZF.XCwjpydtDaPGap65oPEembdYY.B3xXkItVoZhjbcjoZaBJt9R1ApLFm0wMBYIez1Tf5RyZ6rVwy12LLCGtlOC2qWBeRJnr0nbLY.6fkB1QjcMKoWTlxaA--
Received: from [209.172.74.45] by web33303.mail.mud.yahoo.com via HTTP;
	Wed, 08 Oct 2008 16:38:21 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Wed, 8 Oct 2008 16:38:21 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: Behave WG <behave@ietf.org>, 'Internet Area' <int-area@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <200810081921.m98JLBYV015522@venus.xmundo.net>
MIME-Version: 1.0
Message-ID: <631999.92686.qm@web33303.mail.mud.yahoo.com>
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: srisuresh@yahoo.com
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


Fernando, 

Thank you for the comments. Please see my responses inline.

regards,
suresh

--- On Wed, 10/8/08, Fernando Gont <fernando@gont.com.ar> wrote:

> From: Fernando Gont <fernando@gont.com.ar>
> Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
> To: "Behave WG" <behave@ietf.org>, "'Internet Area'" <int-area@ietf.org>
> Cc: behave-chairs@tools.ietf.org
> Date: Wednesday, October 8, 2008, 12:15 PM
> At 05:31 p.m. 07/10/2008, Dan Wing wrote:
> 
> >    REQ-9: A NAT device MAY implement a policy control
> that prevents
> >    ICMP messages being generated toward certain
> interface(s).
> >    Implementation of such a policy control overrides
> the MUSTs in
> >    REQ-10.
> 
> Then.... shouldn't the requirements be
> "SHOULD"s rather than "MUST"s?
> 

[suresh] Essentially, the objective is not to dilute the MUST or SHOULD requirement on the NAT device, but to give the device admin an override capability. So, if the admin chooses to enforce local policies to override NAT operation, then the NAT device MAY enforce the local policy control. Would the following revised wording work for you?

Implementation of such a policy control overrides the MUSTs and SHOULDs in REQ-10.

> 
> 
> >    REQ-10: Unless overridden by REQ-9's policy, a
> NAT device needs to
> >    support ICMP messages as below, some conforming to
> Section 4.3 of
> >    [RFC1812] and some superseding the requirements of
> Section 4.3 of
> >    [RFC1812].
> >        a. MUST support:
> >          1. Destination Unreachable Message, as
> described in
> >              Section 7.1 of this document,
> >           2. Time Exceeded Message, as described in
> Section 7.2 of
> >              of this document,
> >           3. Parameter Problem Message, as described
> in
> >              Section 4.3.3.5 of [RFC1812],
> >           4. Echo Request/Reply Messages, as described
> in REQ-1,
> >           5. Router Advertisement and Solicitations,
> as described in
> >              Section 4.3.3.10 of [RFC1812].
> 
> Does anybody actually use these ICMPv4 messages? I do
> recall Windows 
> systems sending these messages when they are bootstrapped,
> but...
> 

[suresh] If the WG believes any of these ought to be obsoleted for NAT devices, one option would be to dilute the requirement to MAY for NATs in this document. However, we need to provide sufficient justification for any deviation for NATs from RFC 1812.

> 
> 
> >        b. MAY support:
> >           1. Redirect Message, as described in Section
> 4.3.3.2 of
> >              [RFC1812],
> 
> If anything, I'd add that support should default to
> "off".
> 

[suresh] RFC1812 already has MAY requirement on this and doesnot mandate this. RFC 1812 says:

   Contrary to [INTRO:2], a router MAY ignore ICMP Redirects when
   choosing a path for a packet originated by the router if the router
   is running a routing protocol or if forwarding is enabled on the
   router and on the interface over which the packet is being sent.


> 
> 
> >           2. Source Route Options, as described in
> Section 7.3 of
> >              this document,
> 
> The draft says:
> "If a NAT device does not support forwarding packets
> with
>     the source route option, the NAT device SHOULD NOT
> forward
>     outbound ICMP messages that contain source route option
> in the
>     outer or inner ICMP header."
> 
> s/ICMP header/IP header/
> 

[suresh] OK. Thanks.

> 
> 
> >           4. Address Mask Request/Reply Message, as
> described in
> >              Section 7.4 of this document.
> 
> AFAIK, these messages are not used in practice (even when a
> number of 
> systems support them). Shouldn't they be deprecated as
> with the 
> information request/response?
> 

[suresh] I believe, It is not in the scope of this document to deprecate ICMP messages or their use outside of NATs. 

For this reason, the requirement for Address mask request/Reply support for NATs is diluted to MAY (from MUST in RFC 1812). 

Information Request/response message is already obsoleted by RFC 1812. RFC 1812 recommends SHOULD NOT for the message and says the following on this.

      The Information Request/Reply pair was intended to support self-
      configuring systems such as diskless workstations, to allow them
      to discover their IP network prefixes at boot time.  However,
      these messages are now obsolete.  The RARP and BOOTP protocols
      provide better mechanisms for a host to discover its own IP
      address.

> Last, but not least:
> 
> In Section 7.1.2, the draft says:
> "   When NAT device is the recipient of "Packet
> Too Big" ICMP message
>     from the network, the NAT device MUST forward the ICMP
> message back
>     to the intended recipient, pursuant to the previously
> stated
>     requirements REQ-3, REQ-4, REQ-5 and REQ-6."
> 
> Does REQ-6 really apply here? (ICMP PTBs are not
> query/response messages)
> 

[suresh] You are right, REQ-6 is not applicable here. It should have been just REQ-3, REQ-4 and REQ-5.

regards,
suresh

> Kind regards,
> 
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF
> D076 FFF1
> 
> 
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Oct  8 17:36:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 039363A6BEE;
	Wed,  8 Oct 2008 17:36:05 -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 467DA3A6BCC
	for <behave@core3.amsl.com>; Wed,  8 Oct 2008 17:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5
	tests=[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 ZlYWWXWYZxVT for <behave@core3.amsl.com>;
	Wed,  8 Oct 2008 17:36:02 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 7BB953A6BEE
	for <behave@ietf.org>; Wed,  8 Oct 2008 17:36:02 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 2B24BEBC400C; Thu,  9 Oct 2008 00:36:44 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 57BDDEBC400A
	for <behave@ietf.org>; Thu,  9 Oct 2008 00:36:43 +0000 (UTC)
Message-ID: <48ED521A.5040004@acm.org>
Date: Wed, 08 Oct 2008 17:36:42 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
Subject: [BEHAVE] TURN and TURNS URI and resolution mechanism (-03)
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I just submitted an updated I-D:

http://www.ietf.org/internet-drafts/draft-petithuguenin-behave-turn-uri-03.txt

Comments appreciated.

Thanks.

Changelog:

   o  Added Running Code Consideration section.
   o  Added Remote Hosting example in introduction.
   o  Changed back to opaque URIs because of [RFC4395] Section 2.2.  Now
      use "?" as separator.
   o  Added IANA considerations section.
   o  Added security considerations section.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Oct  8 18:35:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 667C43A6C1C;
	Wed,  8 Oct 2008 18:35:31 -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 4AADC3A6C12;
	Wed,  8 Oct 2008 18:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, 
	RCVD_IN_DNSWL_LOW=-1, RDNS_NONE=0.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 y45V2GVZw0eD; Wed,  8 Oct 2008 18:35:29 -0700 (PDT)
Received: from smtp1.xmundo.net (unknown [201.216.232.80])
	by core3.amsl.com (Postfix) with ESMTP id 577E63A68D6;
	Wed,  8 Oct 2008 18:35:27 -0700 (PDT)
Received: from venus.xmundo.net (venus.xmundo.net [201.216.232.56])
	by smtp1.xmundo.net (Postfix) with ESMTP id 7A08E6B68E9;
	Wed,  8 Oct 2008 22:36:10 -0300 (ART)
Received: from notebook.gont.com.ar (host15.190-139-184.telecom.net.ar
	[190.139.184.15]) (authenticated bits=0)
	by venus.xmundo.net (8.14.1/8.13.8) with ESMTP id m991ZlpM029936;
	Wed, 8 Oct 2008 22:35:57 -0300
Message-Id: <200810090135.m991ZlpM029936@venus.xmundo.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 08 Oct 2008 21:37:05 -0300
To: srisuresh@yahoo.com, Behave WG <behave@ietf.org>,
	"'Internet Area'" <int-area@ietf.org>
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <631999.92686.qm@web33303.mail.mud.yahoo.com>
References: <200810081921.m98JLBYV015522@venus.xmundo.net>
	<631999.92686.qm@web33303.mail.mud.yahoo.com>
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0 (venus.xmundo.net [201.216.232.56]);
	Wed, 08 Oct 2008 22:36:10 -0300 (ART)
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hello, Pyda,

Comments in-line...


> > >    REQ-9: A NAT device MAY implement a policy control
> > that prevents
> > >    ICMP messages being generated toward certain
> > interface(s).
> > >    Implementation of such a policy control overrides
> > the MUSTs in
> > >    REQ-10.
> >
> > Then.... shouldn't the requirements be
> > "SHOULD"s rather than "MUST"s?
>
>[suresh] Essentially, the objective is not to dilute the MUST or 
>SHOULD requirement on the NAT device, but to give the device admin 
>an override capability. So, if the admin chooses to enforce local 
>policies to override NAT operation, then the NAT device MAY enforce 
>the local policy control. Would the following revised wording work for you?
>
>Implementation of such a policy control overrides the MUSTs and 
>SHOULDs in REQ-10.

Any would work for me. I was just wondering if it was correct (from a 
the perspective of RFC2119) to include a MUST that could be overiden. 
That is, I was wondering if that means that the "requirements" should 
be a "SHOULD" rather than a "MUST".


> > >           5. Router Advertisement and Solicitations,
> > as described in
> > >              Section 4.3.3.10 of [RFC1812].
> >
> > Does anybody actually use these ICMPv4 messages? I do
> > recall Windows
> > systems sending these messages when they are bootstrapped,
> > but...
> >
>
>[suresh] If the WG believes any of these ought to be obsoleted for 
>NAT devices, one option would be to dilute the requirement to MAY 
>for NATs in this document. However, we need to provide sufficient 
>justification for any deviation for NATs from RFC 1812.

While these messages are a "MUST" in RFC1812, my take is that RFC1812 
is outdated in this respect, and that we should not *require* them 
for NATs. I'm not saying we should obsolete these messages here (it 
would be out of the scope of the document), but rather that we should 
not require NATs to support these messages that nobody (that I know 
of) is depending on.




> > >        b. MAY support:
> > >           1. Redirect Message, as described in Section
> > 4.3.3.2 of
> > >              [RFC1812],
> >
> > If anything, I'd add that support should default to
> > "off".
>
>[suresh] RFC1812 already has MAY requirement on this and doesnot 
>mandate this. RFC 1812 says:

MAYs are less of a concern to me (as they give you the option to 
support them, but do not require you to).



>    Contrary to [INTRO:2], a router MAY ignore ICMP Redirects when
>    choosing a path for a packet originated by the router if the router
>    is running a routing protocol or if forwarding is enabled on the
>    router and on the interface over which the packet is being sent.

My take here is that the spirit f RFC1812 is that you can discard 
redirects *if* you are running a routing protocol (i.e., you're 
knowledgeable about routing). However, it would be insane to honor 
redirects nowadays.... unless you're enforcing something like GTSM 
(the TTL hack). If not, basically anybody could DoS you by sending 
you a forged ICMP redirect.

In anycase, as I said above, given that this is a MAY in your 
document, no changes are needed (i.e., you are not mandating support 
for redirects).




> > >           4. Address Mask Request/Reply Message, as
> > described in
> > >              Section 7.4 of this document.
> >
> > AFAIK, these messages are not used in practice (even when a
> > number of
> > systems support them). Shouldn't they be deprecated as
> > with the
> > information request/response?
>
>[suresh] I believe, It is not in the scope of this document to 
>deprecate ICMP messages or their use outside of NATs.
>
>For this reason, the requirement for Address mask request/Reply 
>support for NATs is diluted to MAY (from MUST in RFC 1812).

Same here. I have no real concerns here.

Kind regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




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


From behave-bounces@ietf.org  Wed Oct  8 22:49:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B1E13A6C5F;
	Wed,  8 Oct 2008 22:49:12 -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 337F828C176
	for <behave@core3.amsl.com>; Wed,  8 Oct 2008 22:49:11 -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 2fuwey0KgUfx for <behave@core3.amsl.com>;
	Wed,  8 Oct 2008 22:49:10 -0700 (PDT)
Received: from web33301.mail.mud.yahoo.com (web33301.mail.mud.yahoo.com
	[68.142.206.116])
	by core3.amsl.com (Postfix) with SMTP id 80D2E3A6C5D
	for <behave@ietf.org>; Wed,  8 Oct 2008 22:49:07 -0700 (PDT)
Received: (qmail 33945 invoked by uid 60001); 9 Oct 2008 05:49:50 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
	b=csCvZ05HgUYN2orPMlLgYWudqSlbELil3F2LQdzn7CriQwttLP+3ZVhSUOPaOmsWjNCZIBGw+bqMkpWyoM/0zIQlVp+KoDsG7c/PK1zyW4w8JKUehocEo6WQw/pSZoSvJLzMbLPDnoYKewBnMPoQZ14AhCC8BDv2l4Cwrg46lo0=;
X-YMail-OSG: Y.ZklX4VM1mw1AdH29qYV3XdHE.f84QAXGeIeM5QioU.7kk532Wy0f8dlcUGcFPFBsWClpAskT5Myxw8PKBuZfZlo8F.H84C9ZLiIkiEzbnPprK..1rPt.8Yh0O3kZuNCxajpBMzTJZkXago90GKGj70hqWvPzxe.StJDixNdElvj_aBxrXfbvVT4w--
Received: from [75.61.81.19] by web33301.mail.mud.yahoo.com via HTTP;
	Wed, 08 Oct 2008 22:49:50 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Wed, 8 Oct 2008 22:49:50 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: Behave WG <behave@ietf.org>, 'Internet Area' <int-area@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <200810090135.m991ZlpM029936@venus.xmundo.net>
MIME-Version: 1.0
Message-ID: <564433.33479.qm@web33301.mail.mud.yahoo.com>
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: srisuresh@yahoo.com
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org






--- On Wed, 10/8/08, Fernando Gont <fernando@gont.com.ar> wrote:

> From: Fernando Gont <fernando@gont.com.ar>
> Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
> To: srisuresh@yahoo.com, "Behave WG" <behave@ietf.org>, "'Internet Area'" <int-area@ietf.org>
> Cc: behave-chairs@tools.ietf.org
> Date: Wednesday, October 8, 2008, 5:37 PM
> Hello, Pyda,
> 
> Comments in-line...
> 
> 
> > > >    REQ-9: A NAT device MAY implement a
> policy control
> > > that prevents
> > > >    ICMP messages being generated toward
> certain
> > > interface(s).
> > > >    Implementation of such a policy control
> overrides
> > > the MUSTs in
> > > >    REQ-10.
> > >
> > > Then.... shouldn't the requirements be
> > > "SHOULD"s rather than
> "MUST"s?
> >
> >[suresh] Essentially, the objective is not to dilute
> the MUST or 
> >SHOULD requirement on the NAT device, but to give the
> device admin 
> >an override capability. So, if the admin chooses to
> enforce local 
> >policies to override NAT operation, then the NAT device
> MAY enforce 
> >the local policy control. Would the following revised
> wording work for you?
> >
> >Implementation of such a policy control overrides the
> MUSTs and 
> >SHOULDs in REQ-10.
> 
> Any would work for me. I was just wondering if it was
> correct (from a 
> the perspective of RFC2119) to include a MUST that could be
> overiden. 
> That is, I was wondering if that means that the
> "requirements" should 
> be a "SHOULD" rather than a "MUST".
> 
> 
> > > >           5. Router Advertisement and
> Solicitations,
> > > as described in
> > > >              Section 4.3.3.10 of [RFC1812].
> > >
> > > Does anybody actually use these ICMPv4 messages?
> I do
> > > recall Windows
> > > systems sending these messages when they are
> bootstrapped,
> > > but...
> > >
> >
> >[suresh] If the WG believes any of these ought to be
> obsoleted for 
> >NAT devices, one option would be to dilute the
> requirement to MAY 
> >for NATs in this document. However, we need to provide
> sufficient 
> >justification for any deviation for NATs from RFC 1812.
> 
> While these messages are a "MUST" in RFC1812, my
> take is that RFC1812 
> is outdated in this respect, and that we should not
> *require* them 
> for NATs. I'm not saying we should obsolete these
> messages here (it 
> would be out of the scope of the document), but rather that
> we should 
> not require NATs to support these messages that nobody
> (that I know 
> of) is depending on.
> 
[suresh] Agreed. Do you suggest diluting both of the below MUSTs into MAY for NATs. 

          3. Parameter Problem Message, 
          5. Router Advertisement and Solicitations 

> 
> 
> 
> > > >        b. MAY support:
> > > >           1. Redirect Message, as described
> in Section
> > > 4.3.3.2 of
> > > >              [RFC1812],
> > >
> > > If anything, I'd add that support should
> default to
> > > "off".
> >
> >[suresh] RFC1812 already has MAY requirement on this
> and doesnot 
> >mandate this. RFC 1812 says:
> 
> MAYs are less of a concern to me (as they give you the
> option to 
> support them, but do not require you to).
> 

[suresh] OK.

> 
> 
> >    Contrary to [INTRO:2], a router MAY ignore ICMP
> Redirects when
> >    choosing a path for a packet originated by the
> router if the router
> >    is running a routing protocol or if forwarding is
> enabled on the
> >    router and on the interface over which the packet
> is being sent.
> 
> My take here is that the spirit f RFC1812 is that you can
> discard 
> redirects *if* you are running a routing protocol (i.e.,
> you're 
> knowledgeable about routing). However, it would be insane
> to honor 
> redirects nowadays.... unless you're enforcing
> something like GTSM 
> (the TTL hack). If not, basically anybody could DoS you by
> sending 
> you a forged ICMP redirect.
> 
> In anycase, as I said above, given that this is a MAY in
> your 
> document, no changes are needed (i.e., you are not
> mandating support 
> for redirects).
> 

[suresh] Right.

> 
> 
> 
> > > >           4. Address Mask Request/Reply
> Message, as
> > > described in
> > > >              Section 7.4 of this document.
> > >
> > > AFAIK, these messages are not used in practice
> (even when a
> > > number of
> > > systems support them). Shouldn't they be
> deprecated as
> > > with the
> > > information request/response?
> >
> >[suresh] I believe, It is not in the scope of this
> document to 
> >deprecate ICMP messages or their use outside of NATs.
> >
> >For this reason, the requirement for Address mask
> request/Reply 
> >support for NATs is diluted to MAY (from MUST in RFC
> 1812).
> 
> Same here. I have no real concerns here.
> 
[suresh] OK. 

Regards,
suresh

> Kind regards,
> 
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF
> D076 FFF1
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct  9 00:37:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD36C3A6C79;
	Thu,  9 Oct 2008 00:37:24 -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 F3CE53A6C6D;
	Thu,  9 Oct 2008 00:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011, 
	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 i05lF-2BfClR; Thu,  9 Oct 2008 00:37:22 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk
	[IPv6:2001:630:241:204:203:baff:fe9a:8c9b])
	by core3.amsl.com (Postfix) with ESMTP id 764233A6359;
	Thu,  9 Oct 2008 00:37:20 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop.local (fgrpf.plus.com [212.159.18.54])
	(authenticated bits=0)
	by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id m997bvFF000325
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT);
	Thu, 9 Oct 2008 08:37:57 +0100 (BST)
Message-ID: <48EDB4D4.60508@erg.abdn.ac.uk>
Date: Thu, 09 Oct 2008 08:37:56 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland, 
	No SC013683. 
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: draft-ietf-behave-dccp@tools.ietf.org,
	"'dccp' working group" <dccp@ietf.org>, behave@ietf.org
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: [BEHAVE] Review comments on draft-ietf-behave-dccp-03.txt (LC)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This draft looks good to me. I have a few comments on the DCCP aspects 
of NAT traversal. (Some of these are editorial, a few were also noted 
earlier but do not seem to have resulted in new text or discussion).

I look forward to seeing new text or feedback on these topics,

Best wishes,

Gorry

P.S. draft-ietf-dccp-simul-open has now been rev'ed to -05.

----
* Abstract:
/(DCCP).  Those allow DCCP/
- Should this be /(DCCP).  Those allow DCCP/ ?
- I suggest replacing this with...
/(DCCP) that allow DCCP/
        ^^^^^^
----
* Introduction
- It could be helpful to add some explanatory text to a NAT implementor
to explain what DCCP actually is. Here is a suggestion, based on the
introductions from various DCCP-related documents:

"The Datagram Congestion Control Protocol (DCCP) [RFC4340] is an IETF
standards-track transport protocol that allows the transmission of
congestion-controlled, unreliable datagrams. DCCP can be viewed equally
  as either UDP-plus-congestion-control or TCP-minus-reliability
(although, unlike TCP, DCCP offers a choice from multiple congestion
control algorithms). It is intended for applications such as streaming
media, Internet telephony, and on-line games. Since it is both
datagram-based and connection-oriented, it faces similar problems to TCP
NAT traversal."
----
* Introduction:
The first use of "NAT" is not defined, I'd normally expect this to be 
expanded in the introduction.
----
* Applicability, para 1
- I didn't see any feedback or new text concerning the following earlier 
comment:
/This document applies to NAT devices that want to handle DCCP
datagrams. /
- Suggest we extend this to say:
/This document is an adjunct to [i-d.BEHAVE-UDP] and [i-d.BEHAVE-TCP]
which define many terms relating to NATs, lay out general requirements
for all NATs, and sets requirements for NATs that handle IP and unicast
UDP traffic. The purpose of this document is to set requirements for
NATs that handle DCCP traffic.

The requirements of this specification apply to Traditional NATs as
described in [RFC2663]./
----
* Applicability
- I am concerned that the text at the end of the first paragraph can be
read either way. If this is going forward as a BCP, then it should
provide clear guidance, on how this *should* be deployed if you wish
your NAT to support DCCP, not be seen to make a judgment call on the
state of current deployment, which I think is not helpful.

Currently it says:
   /It is not the intent of this document to deprecate the
    overwhelming majority of deployed NAT devices.  These NATs are/
    ^^^^^^^^^^^^^^^^^^^^^
   /It is not the intent of this document to deprecate already
                                                       ^^^^^^^
    deployed NAT devices.  These NATs are/
----
* Section 4.2
- Remove extra "The"
/The A DCCP-Listen packet/
  ^^^
---

*  Section 4.3.  Externally Initiated Connections
/RECOMMENDED that a NAT have an "Endpoint-independent/
                         ^^^^^
/RECOMMENDED that a NAT has an "Endpoint-independent/
                         ^^^
----
* Section 4.3
/RECOMMENDED that a NAT have an "Endpoint/
                         ^^^^^
/RECOMMENDED that a NAT has an "Endpoint/
                         ^^^
----
* Section 4.3
/RECOMMENDED that a NAT have an "Address/
                         ^^^^
/RECOMMENDED that a NAT has an "Address/
                         ^^^
----
* Security Considerations
/inbound Listen and Sync packets/
          ^          ^
/inbound DCCP-Listen and DCCP-Sync packets/
          ^^^^^           ^^^^^
----
* Security Considerations
/Listen makes it harder /
  ^      ^
/DCCP-Listen packet makes it harder /
  ^^^^^       ^^^^^^
----
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct  9 08:51:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 019EA3A68DF;
	Thu,  9 Oct 2008 08:51:34 -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 7440F3A68DF
	for <behave@core3.amsl.com>; Thu,  9 Oct 2008 08:51:32 -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 aiOq6zvDrGdp for <behave@core3.amsl.com>;
	Thu,  9 Oct 2008 08:51:31 -0700 (PDT)
Received: from mail-02.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id 6576B3A6843
	for <behave@ietf.org>; Thu,  9 Oct 2008 08:51:31 -0700 (PDT)
Received: from dialin-156-53.tor.primus.ca ([216.254.156.53])
	by mail-02.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KnxnP-0007RS-1e; Thu, 09 Oct 2008 11:51:30 -0400
Message-Id: <F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: matthew@matthew.at
In-Reply-To: <48EA77AD.2050100@matthew.at>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 9 Oct 2008 11:50:54 -0400
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>
	<48EA4A87.6090606@matthew.at>
	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>
	<48EA6C92.5070701@matthew.at>
	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>
	<48EA77AD.2050100@matthew.at>
X-Mailer: Apple Mail (2.915)
X-Authenticated: philip_matthews@magma.ca - dialin-156-53.tor.primus.ca
	[216.254.156.53]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 From your comments below, it seems that you want to not only send a  
packet to the peer, but also install a permission, so that a  
connectivity check packet can be received back from the peer. Thus it  
seems that your concern is not so much with the topic on this thread  
(whether a Send indication can be used when no permission exists), but  
rather with the decision to go with the CreatePermission approach  
rather than the Send request approach.

The concern Jonathan and I had with the SendRequest approach was that  
the STUN state machine inside the TURN client might retransmit the  
Send request if the Send response was lost. This could result in  
multiple copies of the data being sent to the peer.

I am guessing that, in your application, sending multiple copies of  
the data to the peer is not a problem, and you prefer the efficiency  
of using a single Send request rather than needing both a  
CreatePermission and a Send indication.

Am I correct?

- Philip

On Mon, 6-Oct-08, at 16:40 , Matthew Kaufman wrote:

> Philip Matthews wrote:
>>
>> Note that TURN does not REQUIRE that the server use authentication  
>> -- there may be situations where authentication is not required.  
>> However, the security of TURN without authentication is poor.
>>
> For the IT-organization-provided-proxy case, it needs to be as good  
> as the HTTP proxy is. Which is to say "anyone who can speak port 80  
> from an inside address on the inside network interface is A-OK."
>
>> I don't know how much data your client sends to each peer, but if  
>> there is a fair amount of data, then you will probably want to bind  
>> a channel to each peer to reduce overhead (from 36 bytes to 4  
>> bytes). Two notes when using channels. First, a ChannelBind creates  
>> both a channel and a permission. Second, there is nothing that  
>> stops your application from sending ChannelData messages  
>> immediately after sending the ChannelBind request. In most cases,  
>> everything will work fine. It is only if the ChannelBind fails that  
>> you will have to recover.
>>
> The amount of data the client sends to each peer is very small  
> (potentially just a single packet) when doing session establishment.  
> I don't want to pay for either the ChannelBind or CreatePermission  
> cost to get set up to send a single packet to a candidate address  
> that is quite likely to fail. Once I have a session established then  
> yes, there's an overhead reduction to be had by doing ChannelBind at  
> the cost of additional client logic that isn't needed for the native  
> UDP case. Since in the IT-provided-proxy case we usually care more  
> about PPS than BPS, the extra 32 bytes aren't actually that big a  
> deal except when the proxy is on a different continent. But again,  
> until I've done my initial round of packets to potential candidate  
> addresses, received a response, and completed my 2nd pair of  
> handshake, I need a lightweight way of talking to lots more  
> addresses than I want to do ChannelBind for.
>> Do you have a suggestion for another way to do things? What would  
>> you do in a proprietary protocol that is different from the way  
>> TURN works?
> If we did our own protocol we would make the permission mechanism be  
> an up-front authentication followed by the ability to send to any  
> address (and get the return traffic), and once we moved away from  
> TURN we'd probably also use proxy-session-identifying tags so that  
> the proxy could do the same kind of IP address mobility our  
> transport protocol supports. (It would mean that the proxy could  
> identify that this packet was from someone who had already allocated/ 
> authenticated but who has moved to a new IP address (perhaps plugged  
> in at a podium ethernet jack after being on wireless) and then after  
> a challenge/response switch the proxy permission to be associated  
> with the new address). Right now, if a client is forced by IT to go  
> through a TURN proxy, they lose the IP address mobility they would  
> have had if they could talk native UDP to the outside.
>
> Matthew Kaufman
>
>
>

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


From behave-bounces@ietf.org  Thu Oct  9 11:05:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B05E73A69B9;
	Thu,  9 Oct 2008 11:05:52 -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 473483A6AE8
	for <behave@core3.amsl.com>; Thu,  9 Oct 2008 11:05:51 -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 LIgNataYVZiL for <behave@core3.amsl.com>;
	Thu,  9 Oct 2008 11:05:50 -0700 (PDT)
Received: from mail-05.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id 56EE23A6843
	for <behave@ietf.org>; Thu,  9 Oct 2008 11:05:50 -0700 (PDT)
Received: from dialin-207-112-31-139.tor.primus.ca ([207.112.31.139])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1Knzrq-0005lZ-2M
	for behave@ietf.org; Thu, 09 Oct 2008 14:04:07 -0400
Message-Id: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 9 Oct 2008 13:28:48 -0400
X-Mailer: Apple Mail (2.915)
X-Authenticated: philip_matthews@magma.ca -
	dialin-207-112-31-139.tor.primus.ca [207.112.31.139]
Subject: [BEHAVE] TURN: Reduce the channel number range?
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

In the current version of the TURN spec (TURN-10), channel numbers can  
range from 0x4000 to 0xFFFE, which 0xFFFF reserved for future  
extensions. This gives approx 49000 channels. (There are no channel  
numbers in the range 0x0000 to 0x3FFF to allow ChannelData messages to  
be easily distinguished from other TURN messages).

Cullen recently pointed out to me that 49000 channels is a lot more  
channels that we currently envision a client ever using, and that it  
might be good if we reserved some more of these channel numbers in  
case we need some special channels in the future.

In thinking about Cullen's suggestion, it seems totally impractical to  
me for a client to even use 10,000 channels, let alone 49,000. I am  
proposing the following:
*  0x4000 through 0x7FFF will be used for channel numbers (gives  
14,745 channels)
*  0x8000 through 0xFFFF will be reserved (reserving 32767 numbers for  
the future)
To enforce this, the server would reject ChannelBind requests with a  
CHANNEL-NUMBER value outside of 0x4000 - 0x7FFF

Does it seem a good idea to reserve a significant portion of the  
possible channel number range?
Does my concrete proposal seem sensible, or would a different division  
of the possible channel number space be better?

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct  9 11:05:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E71FD28C0F0;
	Thu,  9 Oct 2008 11:05:58 -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 38E013A6AF6
	for <behave@core3.amsl.com>; Thu,  9 Oct 2008 11:05:57 -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 czTtKFBxGI9p for <behave@core3.amsl.com>;
	Thu,  9 Oct 2008 11:05:56 -0700 (PDT)
Received: from mail-05.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id C570A3A6932
	for <behave@ietf.org>; Thu,  9 Oct 2008 11:05:55 -0700 (PDT)
Received: from dialin-207-112-31-139.tor.primus.ca ([207.112.31.139])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1Knzru-0005lZ-1j
	for behave@ietf.org; Thu, 09 Oct 2008 14:04:17 -0400
Message-Id: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Thu, 9 Oct 2008 13:57:40 -0400
X-Mailer: Apple Mail (2.915)
X-Authenticated: philip_matthews@magma.ca -
	dialin-207-112-31-139.tor.primus.ca [207.112.31.139]
Subject: [BEHAVE] TURN: Handling of IP header fields
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

In TURN-09, the spec defined a preferred and alternate behavior for  
how the server should set various fields in the IP header when  
relaying data. The idea was that the preferred behavior was the one we  
wanted the server to do, but some servers might not be able to do the  
preferred behavior (due to socket API restrictions or similar on a  
particular OS), in which case they should do the alternate behavior.  
Further, there was the concept of a Preserving allocation for which  
the server MUST  do the preferred behavior.

In TURN-10, as a result of the discussions in Dublin, the concept of a  
Preserving allocation was removed from the base document to allow the  
spec to advance more quickly. As part of that removal, the preferred  
behaviors were removed, and TURN-10 contains only the alternate  
behaviors.

Cullen, in a phone call to me, has objected to the removal of the  
preferred behavior. He has complained that the spec no longer allows  
his TURN server to preserve the DSCP if it can, but requires the  
server set it to Best Effort.

Cullen is suggesting that add the preferred behaviors back into the  
spec, however wording the text so that there would no longer be a  
preference between the two behaviors. For example, in the case of  
DSCP, TURN-09 said that the server SHOULD copy the DSCP if it could,  
and should only set it to Best Effort if that was not possible. Cullen  
is instead proposing that the text say that either behavior is  
acceptable and not indicate a preference.

To give you an idea what the result would be, I have included the text  
from TURN-09 below. If we went ahead with Cullen's proposal, then the  
text would no longer distinguish between the preferred and alternate  
behavior, but would describe both behaviors in the same paragraph.  
(Also note that TURN-10 removed IPv6 support, so all the IPv6-related  
stuff would not go back in).

Comments?
Do people like Cullen's suggestion?

- Philip


----------------------------
Text from TURN-09:

11.1.  IP

    This section describes the preferred and alternate behavior for
    various fields in the IP header.

    Time to Live (IPv4) or Hop Count (IPv6)

       Preferred Behavior: If the incoming value is 0, then send an ICMP
       Time Exceeded message back to the sender.  Otherwise set the
       outgoing Time to Live/Hop Count to one less than the incoming
       value.

       Alternate Behavior: Set the outgoing value to the default for
       outgoing packets.


    Diff-Serv Code Point

       Preferred Behavior: Set the outgoing value to the incoming value,
       unless the server includes a differentiated services classifier
       and marker [RFC2474].

       Alternate Behavior: Set the outgoing value to a fixed value,  
which
       by default is Best Effort unless configured otherwise.

       In both cases, if the server is immediately adjacent to a
       differentiated services classifier and marker, then DSCP MAY be
       set to any arbitrary value in the direction towards the
       classifier.


    ECN

       Preferred Behavior: Set the outgoing value to the incoming value,
       UNLESS the server is doing Active Queue Management, the incoming
       ECN field is 01 or 10, and the server wishes to indicate that
       congestion has been experienced, in which case set the outgoing
       value to 11.

       Alternate Behavior: Set the outgoing value to 00 (ECN not
       supported)


    Flow Label

       Preferred Behavior: Set the outgoing flow label to 0.

       Alternate Behavior: Same as the Preferred behavior.


    IPv4 Fragmentation

       Preferred Behavior:

          If the outgoing packet size does not exceed the outgoing  
link's
          MTU, then send the outgoing packet unfragmented.  Set the DF
          bit in the outgoing packet to the value of the DF bit in the
          incoming packet, and set the other fragmentation fields
          (Identification, MF, Fragment Offset) as appropriate for a
          packet originating from the server.

          Otherwise, if the outgoing link's MTU is exceeded and the
          incoming DF bit is 0, then fragment the packet before sending.
          Set the outgoing DF to 0, and set the other fragmentation
          fields as appropriate for fragments originated from the  
server.

          Otherwise [link MTU exceeded and incoming DF set], drop the
          outgoing packet and send an ICMP message of type 3 code 4
          ("fragmentation needed and DF set") to the sender of the
          incoming packet.

       Alternate Behavior: As described in the Preferred Behavior,  
except
       always assume the incoming DF bit is 0.


    IPv6 Fragmentation

       Preferred Behavior:

          If the incoming packet did not include a Fragmentation header
          and the outgoing packet size does not exceed the outgoing
          link's MTU, then send the outgoing packet without a
          Fragmentation header.

          If the incoming packet included a Fragment header and if the
          outgoing packet size (with a Fragmentation header included)
          does not exceed the outgoing link's MTU, then send the  
outgoing
          packet with a Fragmentation header.  Set the fields of the
          Fragmentation header as appropriate for a packet originating
          from the server.

          If the incoming packet did not include a Fragmentation header
          and the outgoing packet size exceeds the outgoing link's MTU ,
          then drop the outgoing packet and send an ICMP message of type
          2 code 0 ("Packet too big") to the sender of the incoming
          packet.  If the packet is being sent to the peer, then reduce
          the MTU reported in the ICMP message by 48 bytes to allow room
          for the overhead of a Data indication.

          Otherwise, if the link's MTU is exceeded and the incoming
          packet contained a Fragmentation header, then fragment the
          outgoing packet into fragments of no more than 1280 bytes.   
Set
          the fields of the Fragmentation header as appropriate for a
          packet originating from the server.

       Alternate Behavior: As described in the Preferred Behavior,  
except
       always assume incoming packet has a Fragmentation header.


    IPv4 Options

       Preferred Behavior: The outgoing packet is sent without any IPv4
       options.

       Alternate Behavior: Same as preferred.


    IPv6 Extention Headers

       Preferred Behavior: The outgoing packet is sent without any IPv6
       extension headers, with the exception of the Fragmentation header
       as described above

       Alternate Behavior: Same as preferred.

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


From behave-bounces@ietf.org  Thu Oct  9 11:43:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A72B23A6A3B;
	Thu,  9 Oct 2008 11:43:00 -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 48BDE3A6AC0
	for <behave@core3.amsl.com>; Thu,  9 Oct 2008 11:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5
	tests=[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 0shJ5-qhXa5N for <behave@core3.amsl.com>;
	Thu,  9 Oct 2008 11:42:58 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 867F83A6843
	for <behave@ietf.org>; Thu,  9 Oct 2008 11:42:58 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id 6571DDBCC014; Thu,  9 Oct 2008 18:43:13 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id EAE23DBCC012
	for <behave@ietf.org>; Thu,  9 Oct 2008 18:43:12 +0000 (UTC)
Message-ID: <48EE50C0.4000803@acm.org>
Date: Thu, 09 Oct 2008 11:43:12 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: behave@ietf.org
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
In-Reply-To: <20080929171502.0885D3A6B0F@core3.amsl.com>
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Please find below my review of TURN-10.

BTW, I will be in Minneapolis so I will be happy to do some interop with
other implementers of TURN-10.  Send me an email if you are interested.

Also, we have a patch ready for Wireshark and will be submitting it next
week to the Wireshark developers.

-----------------------------------------------------------------------

- Abstract:  "... with other hosts (peers) located behind other NATs."

Communication can be impossible even if the peers are not behind a NAT.
Same thing in Section 1, second paragraph.

- Section 3, definition of 5-tuple:  "...and transport protocol (UDP or
TCP))..."

Can be something else than UDP or TCP.

- Section 14.6:

This attribute is one byte long, which I understand as been padded to 4
bytes by the algorithm described in rfc3489bis.  I think that it is a
good idea to do this, but this is not consistent with CHANNEL-NUMBER and
REQUESTED-TRANSPORT that are both 4 bytes, with RFFU.


NITS
----

- Section 2, paragraph 2:  "On the public Internet..."

Pleonasm.

- Section 3, definition of 5-tuple: "...used to communicate between the
client and the server ."

Remove the space before the stop.

- Section 6.2, bullet #3:  "...contain a REQUESTED-TRANPORT..."

REQUESTED-TRANSPORT

- Section 6.2, bullet #8:  "...as in authenticated error responses.."

Remove redundant stop.

- Section 8, paragraph 7: "...at a different point in time, or vica-versa."

...vice versa.

- Section 9, second paragraph: "...with either the Send mechanismSection
10 or the Channel mechanismSection 11."

...mechanism in Section...

- Section 14:  "0x001a: DONT-FRAGMENT"

0x001A

- Section 14.6:

The unused bits in the ASCII art should be marked RFFU.

- Section 14.6: "...to reserve the next highest port..."

...to reserve the next port...

- Section 16.1.3: "...by sending it a Refresh with an..."

...by sending it a Refresh request with an...

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 10 00:22:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51BEF3A6AE6;
	Fri, 10 Oct 2008 00:22:41 -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 261363A6AE6
	for <behave@core3.amsl.com>; Fri, 10 Oct 2008 00:22:40 -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 I6H2qWnKiEzs for <behave@core3.amsl.com>;
	Fri, 10 Oct 2008 00:22:39 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 1865D3A6AEF
	for <behave@ietf.org>; Fri, 10 Oct 2008 00:22:38 -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
	m9A7MPcC024288; Fri, 10 Oct 2008 10:22:27 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 10:22:22 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 10:22:13 +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 10:22:12 +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, 10 Oct 2008 10:22:16 +0300
User-Agent: KMail/1.9.10
References: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
In-Reply-To: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810101022.16660.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 10 Oct 2008 07:22:12.0709 (UTC)
	FILETIME=[EA181950:01C92AA8]
X-Nokia-AV: Clean
Cc: ext Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] TURN: Reduce the channel number range?
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

On Thursday 09 October 2008 20:28:48 ext Philip Matthews, you wrote:
> In the current version of the TURN spec (TURN-10), channel numbers can
> range from 0x4000 to 0xFFFE, which 0xFFFF reserved for future
> extensions. This gives approx 49000 channels. (There are no channel
> numbers in the range 0x0000 to 0x3FFF to allow ChannelData messages to
> be easily distinguished from other TURN messages).
>
> Cullen recently pointed out to me that 49000 channels is a lot more
> channels that we currently envision a client ever using, and that it
> might be good if we reserved some more of these channel numbers in
> case we need some special channels in the future.
>
> In thinking about Cullen's suggestion, it seems totally impractical to
> me for a client to even use 10,000 channels, let alone 49,000. I am
> proposing the following:
> *  0x4000 through 0x7FFF will be used for channel numbers (gives
> 14,745 channels)
> *  0x8000 through 0xFFFF will be reserved (reserving 32767 numbers for
> the future)
> To enforce this, the server would reject ChannelBind requests with a
> CHANNEL-NUMBER value outside of 0x4000 - 0x7FFF
>
> Does it seem a good idea to reserve a significant portion of the
> possible channel number range?
> Does my concrete proposal seem sensible, or would a different division
> of the possible channel number space be better?

To me, yes.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 10 00:25:57 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 925A93A6800;
	Fri, 10 Oct 2008 00:25:57 -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 68DBF3A6800
	for <behave@core3.amsl.com>; Fri, 10 Oct 2008 00:25:56 -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 cCICuNTSigTr for <behave@core3.amsl.com>;
	Fri, 10 Oct 2008 00:25:55 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 816093A67D0
	for <behave@ietf.org>; Fri, 10 Oct 2008 00:25:55 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9A7Otbu030261; Fri, 10 Oct 2008 02:25:34 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 10:25:14 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 10 Oct 2008 10:25:14 +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 10:25:14 +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, 10 Oct 2008 10:25:17 +0300
User-Agent: KMail/1.9.10
References: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>
In-Reply-To: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810101025.18081.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 10 Oct 2008 07:25:14.0066 (UTC)
	FILETIME=[5630FB20:01C92AA9]
X-Nokia-AV: Clean
Cc: ext Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] TURN: Handling of IP header fields
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

On Thursday 09 October 2008 20:57:40 ext Philip Matthews, you wrote:
> In TURN-09, the spec defined a preferred and alternate behavior for
> how the server should set various fields in the IP header when
> relaying data. The idea was that the preferred behavior was the one we
> wanted the server to do, but some servers might not be able to do the
> preferred behavior (due to socket API restrictions or similar on a
> particular OS), in which case they should do the alternate behavior.
> Further, there was the concept of a Preserving allocation for which
> the server MUST  do the preferred behavior.
>
> In TURN-10, as a result of the discussions in Dublin, the concept of a
> Preserving allocation was removed from the base document to allow the
> spec to advance more quickly. As part of that removal, the preferred
> behaviors were removed, and TURN-10 contains only the alternate
> behaviors.
>
> Cullen, in a phone call to me, has objected to the removal of the
> preferred behavior. He has complained that the spec no longer allows
> his TURN server to preserve the DSCP if it can, but requires the
> server set it to Best Effort.
>
> Cullen is suggesting that add the preferred behaviors back into the
> spec, however wording the text so that there would no longer be a
> preference between the two behaviors. For example, in the case of
> DSCP, TURN-09 said that the server SHOULD copy the DSCP if it could,
> and should only set it to Best Effort if that was not possible. Cullen
> is instead proposing that the text say that either behavior is
> acceptable and not indicate a preference.
>
> To give you an idea what the result would be, I have included the text
> from TURN-09 below. If we went ahead with Cullen's proposal, then the
> text would no longer distinguish between the preferred and alternate
> behavior, but would describe both behaviors in the same paragraph.
> (Also note that TURN-10 removed IPv6 support, so all the IPv6-related
> stuff would not go back in).
>
> Comments?

Well, the preferred behavior remains "preferred", right? I mean, we should =

have something like "The server SHOULD do [preferred behavior]. If this is =

not possible, the server MUST do [alternate behavior] instead."

> Do people like Cullen's suggestion?

At least I would rather we keep the both behaviors mentioned somehow.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat Oct 11 09:14:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B10DD3A6B3E;
	Sat, 11 Oct 2008 09:14:41 -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 801193A6B3E
	for <behave@core3.amsl.com>; Sat, 11 Oct 2008 09:14:40 -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 Jhegety6uu1s for <behave@core3.amsl.com>;
	Sat, 11 Oct 2008 09:14:39 -0700 (PDT)
Received: from mail-05.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id 1DA273A6B3A
	for <behave@ietf.org>; Sat, 11 Oct 2008 09:14:38 -0700 (PDT)
Received: from psound-lib-dsl.vianet.ca ([209.91.163.97] helo=[192.168.0.11])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Koh5F-0000jS-0j; Sat, 11 Oct 2008 12:12:49 -0400
Message-Id: <4C822400-B2AD-4F52-BD37-34775A5C58C3@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: =?ISO-8859-1?Q?=22R=E9mi_Denis-Courmont=22?=
	<remi.denis-courmont@nokia.com>
In-Reply-To: <200810101025.18081.remi.denis-courmont@nokia.com>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Sat, 11 Oct 2008 12:14:45 -0400
References: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>
	<200810101025.18081.remi.denis-courmont@nokia.com>
X-Mailer: Apple Mail (2.915)
X-Authenticated: philip_matthews@magma.ca - psound-lib-dsl.vianet.ca
	([192.168.0.11]) [209.91.163.97]
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Handling of IP header fields
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Fri, 10-Oct-08, at 03:25 , R=E9mi Denis-Courmont wrote:

>>
>
> Well, the preferred behavior remains "preferred", right? I mean, we  =

> should
> have something like "The server SHOULD do [preferred behavior]. If  =

> this is
> not possible, the server MUST do [alternate behavior] instead."
>
>> Do people like Cullen's suggestion?
>
> At least I would rather we keep the both behaviors mentioned somehow.
>

Cullen proposed that the spec NOT express a preference between the two  =

behaviors. Not sure if this was because he felt this was the right way  =

to go, or if that was just to make things easier.

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Sat Oct 11 09:26:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0214B3A68C2;
	Sat, 11 Oct 2008 09:26:03 -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 AADA83A6780
	for <behave@core3.amsl.com>; Sat, 11 Oct 2008 09:26:01 -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 RrzPqSWBYYLL for <behave@core3.amsl.com>;
	Sat, 11 Oct 2008 09:26:00 -0700 (PDT)
Received: from mail-05.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id A82D73A6774
	for <behave@ietf.org>; Sat, 11 Oct 2008 09:26:00 -0700 (PDT)
Received: from psound-lib-dsl.vianet.ca ([209.91.163.97] helo=[192.168.0.11])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KohGv-0006xG-1Y; Sat, 11 Oct 2008 12:24:53 -0400
Message-Id: <B7A939E1-8800-4E20-8547-B98B8192AD6D@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <48EE50C0.4000803@acm.org>
Mime-Version: 1.0 (Apple Message framework v915)
Date: Sat, 11 Oct 2008 12:26:53 -0400
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
	<48EE50C0.4000803@acm.org>
X-Mailer: Apple Mail (2.915)
X-Authenticated: philip_matthews@magma.ca - psound-lib-dsl.vianet.ca
	([192.168.0.11]) [209.91.163.97]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Marc:

Thanks for your review!
See inline for some quick responses.

- Philip

On Thu, 9-Oct-08, at 14:43 , Marc Petit-Huguenin wrote:

> Please find below my review of TURN-10.
>
> BTW, I will be in Minneapolis so I will be happy to do some interop  
> with
> other implementers of TURN-10.  Send me an email if you are  
> interested.
>
> Also, we have a patch ready for Wireshark and will be submitting it  
> next
> week to the Wireshark developers.
>
> -----------------------------------------------------------------------
>
> - Abstract:  "... with other hosts (peers) located behind other NATs."
>
> Communication can be impossible even if the peers are not behind a  
> NAT.
> Same thing in Section 1, second paragraph.

OK. I have deleted the "located behind other NATs".

>
>
> - Section 3, definition of 5-tuple:  "...and transport protocol (UDP  
> or
> TCP))..."
>
> Can be something else than UDP or TCP.

Not sure what you are driving at. Protocols like DCCP or SCTP are not  
supported for communication with the TURN server (yet).

>
>
> - Section 14.6:
>
> This attribute is one byte long, which I understand as been padded  
> to 4
> bytes by the algorithm described in rfc3489bis.  I think that it is a
> good idea to do this, but this is not consistent with CHANNEL-NUMBER  
> and
> REQUESTED-TRANSPORT that are both 4 bytes, with RFFU.

Yes, there is a small inconsistency. Since EVEN-PORT is only for use  
with older RTP clients, and since we have previously agreed to really  
restrict what can be done here, I didn't see any need for an RFFU  
field. Also, I didn't want to change the format of the other  
attributes unless there was a good reason.

As you noted, the padding rules of rfc3489bis handle one-byte  
attributes.


I'll comment on (and fix) the nits below later.

>
>
>
> NITS
> ----
>
> - Section 2, paragraph 2:  "On the public Internet..."
>
> Pleonasm.
>
> - Section 3, definition of 5-tuple: "...used to communicate between  
> the
> client and the server ."
>
> Remove the space before the stop.
>
> - Section 6.2, bullet #3:  "...contain a REQUESTED-TRANPORT..."
>
> REQUESTED-TRANSPORT
>
> - Section 6.2, bullet #8:  "...as in authenticated error responses.."
>
> Remove redundant stop.
>
> - Section 8, paragraph 7: "...at a different point in time, or vica- 
> versa."
>
> ...vice versa.
>
> - Section 9, second paragraph: "...with either the Send  
> mechanismSection
> 10 or the Channel mechanismSection 11."
>
> ...mechanism in Section...
>
> - Section 14:  "0x001a: DONT-FRAGMENT"
>
> 0x001A
>
> - Section 14.6:
>
> The unused bits in the ASCII art should be marked RFFU.
>
> - Section 14.6: "...to reserve the next highest port..."
>
> ...to reserve the next port...
>
> - Section 16.1.3: "...by sending it a Refresh with an..."
>
> ...by sending it a Refresh request with an...
>
> -- 
> Marc Petit-Huguenin           [                                 ]
> Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
> Work: marc@8x8.com            [                                 ]
> [                                                               ]
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Sat Oct 11 10:20:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C34CF3A686E;
	Sat, 11 Oct 2008 10:20:37 -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 9C5A73A67B6
	for <behave@core3.amsl.com>; Sat, 11 Oct 2008 10:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5
	tests=[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 TTs3ccGfszlb for <behave@core3.amsl.com>;
	Sat, 11 Oct 2008 10:20:36 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 112D53A686E
	for <behave@ietf.org>; Sat, 11 Oct 2008 10:20:36 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id EAB53DFC51BC; Sat, 11 Oct 2008 17:21:18 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 7EB46DFC51B8;
	Sat, 11 Oct 2008 17:21:18 +0000 (UTC)
Message-ID: <48F0E08D.9080205@acm.org>
Date: Sat, 11 Oct 2008 10:21:17 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
	<48EE50C0.4000803@acm.org>
	<B7A939E1-8800-4E20-8547-B98B8192AD6D@magma.ca>
In-Reply-To: <B7A939E1-8800-4E20-8547-B98B8192AD6D@magma.ca>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> Hi Marc:
> 
> Thanks for your review!
> See inline for some quick responses.
> 
> - Philip
> 
> On Thu, 9-Oct-08, at 14:43 , Marc Petit-Huguenin wrote:
> 

[...]

>> - Section 3, definition of 5-tuple:  "...and transport protocol (UDP or
>> TCP))..."
>>
>> Can be something else than UDP or TCP.
> 
> Not sure what you are driving at. Protocols like DCCP or SCTP are not
> supported for communication with the TURN server (yet).
> 

Yes, but TURN-10 also does not support IPv6, or TCP between the server
and the peer, but still mention the possibility of using them.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 13 04:06:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E00AB3A68DC;
	Mon, 13 Oct 2008 04:06:10 -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 030843A68DC
	for <behave@core3.amsl.com>; Mon, 13 Oct 2008 04:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.193
X-Spam-Level: 
X-Spam-Status: No, score=-6.193 tagged_above=-999 required=5 tests=[AWL=0.056, 
	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 8TN9ClvuMG8U for <behave@core3.amsl.com>;
	Mon, 13 Oct 2008 04:06:08 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 91BE63A659B
	for <behave@ietf.org>; Mon, 13 Oct 2008 04:06:08 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	49B642130A; Mon, 13 Oct 2008 13:06:43 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-6f-48f32bc38b79
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	22FD3212FD; Mon, 13 Oct 2008 13:06:43 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 13:06:37 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 13:06:37 +0200
Message-ID: <48F32BBD.9090609@ericsson.com>
Date: Mon, 13 Oct 2008 13:06:37 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>	<200810101025.18081.remi.denis-courmont@nokia.com>
	<4C822400-B2AD-4F52-BD37-34775A5C58C3@magma.ca>
In-Reply-To: <4C822400-B2AD-4F52-BD37-34775A5C58C3@magma.ca>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 13 Oct 2008 11:06:37.0241 (UTC)
	FILETIME=[C2D1E290:01C92D23]
X-Brightmail-Tracker: AAAAAA==
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Handling of IP header fields
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

Philip Matthews skrev:
> On Fri, 10-Oct-08, at 03:25 , R=E9mi Denis-Courmont wrote:
> =

>>>
>>
>> Well, the preferred behavior remains "preferred", right? I mean, we
>> should
>> have something like "The server SHOULD do [preferred behavior]. If
>> this is
>> not possible, the server MUST do [alternate behavior] instead."
>>
>>> Do people like Cullen's suggestion?
>>
>> At least I would rather we keep the both behaviors mentioned somehow.
>>
> =

> Cullen proposed that the spec NOT express a preference between the two
> behaviors. Not sure if this was because he felt this was the right way
> to go, or if that was just to make things easier.

Personal view, but we really should express which is the preferred one.
Because I don't think there is anyone here that thinks the alternative
behavior is better if the relay have no issues with reading the
information.

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 13 06:59:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AF8528C10B;
	Mon, 13 Oct 2008 06:59:01 -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 A410C3A6A5B
	for <behave@core3.amsl.com>; Mon, 13 Oct 2008 06:58:59 -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 O67rAfBX-vWo for <behave@core3.amsl.com>;
	Mon, 13 Oct 2008 06:58:58 -0700 (PDT)
Received: from web33308.mail.mud.yahoo.com (web33308.mail.mud.yahoo.com
	[68.142.206.123])
	by core3.amsl.com (Postfix) with SMTP id 77B133A6947
	for <behave@ietf.org>; Mon, 13 Oct 2008 06:58:58 -0700 (PDT)
Received: (qmail 24483 invoked by uid 60001); 13 Oct 2008 13:58:50 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
	b=Xd8+tfUVjn8Dzp7dMELnYu1LPBNpi9Wewy+5jTXa0BvKCmNH70pCv0AYK0rTCwaJ/nLS45Io+n3i/XXCDV2f1rsvpmkY+YO8Ojq/ODtr+3OPF4PcHVB7gE9TWwhBBH37m9ef45KCi+Asqy6ZpmW7CF96z1hlpJPerEr3v94D4BM=;
X-YMail-OSG: Sq48AhIVM1nvv15An0Ho8LhQcXGB655thn.XUf3AKFXcmVrN2Wjdi8pFkuaNsr05jcCxiWCyjHsAj7_6l5W2E7HLrv.cIEhRQMbT0j_vrEMrEzfiU8ge07FHRmFmioHgD26iw6gy6OMUzFo0pLhB45Ps_Ih664H6GZmYiSMy2l0Y83aQ8G5XKEA1uA--
Received: from [76.254.90.187] by web33308.mail.mud.yahoo.com via HTTP;
	Mon, 13 Oct 2008 06:58:50 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Mon, 13 Oct 2008 06:58:50 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: Behave WG <behave@ietf.org>, 'Internet Area' <int-area@ietf.org>,
	Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <564433.33479.qm@web33301.mail.mud.yahoo.com>
MIME-Version: 1.0
Message-ID: <673187.24451.qm@web33308.mail.mud.yahoo.com>
Cc: behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: srisuresh@yahoo.com
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Folks,

The "Router advertisements and solicitations" message appears to be rarely used in Ipv4 networks. Please let me know if anyone has objections to changing the requirement for this message to MAY from MUST for NATs. If I dont hear any objection, I will convert this to MAY in the next rev of the draft.

Thanks.

regards,
suresh

--- On Wed, 10/8/08, Pyda Srisuresh <srisuresh@yahoo.com> wrote:

> From: Pyda Srisuresh <srisuresh@yahoo.com>
> Subject: Re: [BEHAVE] [Int-area] WGLC: draft-ietf-behave-nat-icmp-09
> To: "Behave WG" <behave@ietf.org>, "'Internet Area'" <int-area@ietf.org>, "Fernando Gont" <fernando@gont.com.ar>
> Cc: behave-chairs@tools.ietf.org
> Date: Wednesday, October 8, 2008, 10:49 PM
> --- On Wed, 10/8/08, Fernando Gont
> <fernando@gont.com.ar> wrote:
> 
> > From: Fernando Gont <fernando@gont.com.ar>
> > Subject: Re: [BEHAVE] [Int-area] WGLC:
> draft-ietf-behave-nat-icmp-09
> > To: srisuresh@yahoo.com, "Behave WG"
> <behave@ietf.org>, "'Internet Area'"
> <int-area@ietf.org>
> > Cc: behave-chairs@tools.ietf.org
> > Date: Wednesday, October 8, 2008, 5:37 PM
> > Hello, Pyda,
> > 
> > Comments in-line...
> > 
> > 
> > > > >    REQ-9: A NAT device MAY implement a
> > policy control
> > > > that prevents
> > > > >    ICMP messages being generated toward
> > certain
> > > > interface(s).
> > > > >    Implementation of such a policy
> control
> > overrides
> > > > the MUSTs in
> > > > >    REQ-10.
> > > >
> > > > Then.... shouldn't the requirements be
> > > > "SHOULD"s rather than
> > "MUST"s?
> > >
> > >[suresh] Essentially, the objective is not to
> dilute
> > the MUST or 
> > >SHOULD requirement on the NAT device, but to give
> the
> > device admin 
> > >an override capability. So, if the admin chooses
> to
> > enforce local 
> > >policies to override NAT operation, then the NAT
> device
> > MAY enforce 
> > >the local policy control. Would the following
> revised
> > wording work for you?
> > >
> > >Implementation of such a policy control overrides
> the
> > MUSTs and 
> > >SHOULDs in REQ-10.
> > 
> > Any would work for me. I was just wondering if it was
> > correct (from a 
> > the perspective of RFC2119) to include a MUST that
> could be
> > overiden. 
> > That is, I was wondering if that means that the
> > "requirements" should 
> > be a "SHOULD" rather than a
> "MUST".
> > 
> > 
> > > > >           5. Router Advertisement and
> > Solicitations,
> > > > as described in
> > > > >              Section 4.3.3.10 of
> [RFC1812].
> > > >
> > > > Does anybody actually use these ICMPv4
> messages?
> > I do
> > > > recall Windows
> > > > systems sending these messages when they are
> > bootstrapped,
> > > > but...
> > > >
> > >
> > >[suresh] If the WG believes any of these ought to
> be
> > obsoleted for 
> > >NAT devices, one option would be to dilute the
> > requirement to MAY 
> > >for NATs in this document. However, we need to
> provide
> > sufficient 
> > >justification for any deviation for NATs from RFC
> 1812.
> > 
> > While these messages are a "MUST" in
> RFC1812, my
> > take is that RFC1812 
> > is outdated in this respect, and that we should not
> > *require* them 
> > for NATs. I'm not saying we should obsolete these
> > messages here (it 
> > would be out of the scope of the document), but rather
> that
> > we should 
> > not require NATs to support these messages that nobody
> > (that I know 
> > of) is depending on.
> > 
> [suresh] Agreed. Do you suggest diluting both of the below
> MUSTs into MAY for NATs. 
> 
>           3. Parameter Problem Message, 
>           5. Router Advertisement and Solicitations 
> 
> > 
> > 
> > 
> > > > >        b. MAY support:
> > > > >           1. Redirect Message, as
> described
> > in Section
> > > > 4.3.3.2 of
> > > > >              [RFC1812],
> > > >
> > > > If anything, I'd add that support should
> > default to
> > > > "off".
> > >
> > >[suresh] RFC1812 already has MAY requirement on
> this
> > and doesnot 
> > >mandate this. RFC 1812 says:
> > 
> > MAYs are less of a concern to me (as they give you the
> > option to 
> > support them, but do not require you to).
> > 
> 
> [suresh] OK.
> 
> > 
> > 
> > >    Contrary to [INTRO:2], a router MAY ignore
> ICMP
> > Redirects when
> > >    choosing a path for a packet originated by the
> > router if the router
> > >    is running a routing protocol or if forwarding
> is
> > enabled on the
> > >    router and on the interface over which the
> packet
> > is being sent.
> > 
> > My take here is that the spirit f RFC1812 is that you
> can
> > discard 
> > redirects *if* you are running a routing protocol
> (i.e.,
> > you're 
> > knowledgeable about routing). However, it would be
> insane
> > to honor 
> > redirects nowadays.... unless you're enforcing
> > something like GTSM 
> > (the TTL hack). If not, basically anybody could DoS
> you by
> > sending 
> > you a forged ICMP redirect.
> > 
> > In anycase, as I said above, given that this is a MAY
> in
> > your 
> > document, no changes are needed (i.e., you are not
> > mandating support 
> > for redirects).
> > 
> 
> [suresh] Right.
> 
> > 
> > 
> > 
> > > > >           4. Address Mask Request/Reply
> > Message, as
> > > > described in
> > > > >              Section 7.4 of this
> document.
> > > >
> > > > AFAIK, these messages are not used in
> practice
> > (even when a
> > > > number of
> > > > systems support them). Shouldn't they be
> > deprecated as
> > > > with the
> > > > information request/response?
> > >
> > >[suresh] I believe, It is not in the scope of this
> > document to 
> > >deprecate ICMP messages or their use outside of
> NATs.
> > >
> > >For this reason, the requirement for Address mask
> > request/Reply 
> > >support for NATs is diluted to MAY (from MUST in
> RFC
> > 1812).
> > 
> > Same here. I have no real concerns here.
> > 
> [suresh] OK. 
> 
> Regards,
> suresh
> 
> > Kind regards,
> > 
> > --
> > Fernando Gont
> > e-mail: fernando@gont.com.ar || fgont@acm.org
> > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE
> A9EF
> > D076 FFF1
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 13 15:06:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C6C63A69DB;
	Mon, 13 Oct 2008 15:06:17 -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 6C3593A68FB
	for <behave@core3.amsl.com>; Mon, 13 Oct 2008 15:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057, 
	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 8ykY6IGHQxpf for <behave@core3.amsl.com>;
	Mon, 13 Oct 2008 15:06:15 -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 CC5EC3A68A0
	for <behave@ietf.org>; Mon, 13 Oct 2008 15:06:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="108216151"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 13 Oct 2008 22:06:32 +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 m9DM6WLl021708; 
	Mon, 13 Oct 2008 15:06:32 -0700
Received: from dwingwxp01 ([10.32.240.194])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9DM6Va2017917;
	Mon, 13 Oct 2008 22:06:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
Date: Mon, 13 Oct 2008 15:06:32 -0700
Message-ID: <018501c92d7f$f36e7a10$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: Acktf/M56J6cz4NOSfqenRLfjYYe9Q==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=148; t=1223935592; x=1224799592;
	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:=20agenda=20time |Sender:=20;
	bh=XnqFcujKgDUReUQIbn+5r0LxK1M3Ln9orxMBJ5eSi4A=;
	b=Unmnt2YPvdxST7yvTz/YYa7IyhptQLHyN/hKWLbiDOPs7w4pX43w9p1l6u
	cthQey2tPV2hY9I3sbr1qE02siphk16HWOTm7o4ppsAedPVpVRGwtyVCwz1A
	fdvqmTlMwU;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave-chairs@tools.ietf.org
Subject: [BEHAVE] agenda time
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

If you want agenda time at the upcoming BEHAVE meeting, please let us know the
topic, Internet Draft name, speaker, and requested duration.

-d




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


From behave-bounces@ietf.org  Tue Oct 14 07:24:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2E8B13A6BF1;
	Tue, 14 Oct 2008 07:24:29 -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 0949828C1C1
	for <behave@core3.amsl.com>; Tue, 14 Oct 2008 07:24:28 -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 tSqFBBWOd+Yz for <behave@core3.amsl.com>;
	Tue, 14 Oct 2008 07:24:26 -0700 (PDT)
Received: from web33305.mail.mud.yahoo.com (web33305.mail.mud.yahoo.com
	[68.142.206.120])
	by core3.amsl.com (Postfix) with SMTP id 5A4853A69C3
	for <behave@ietf.org>; Tue, 14 Oct 2008 07:24:26 -0700 (PDT)
Received: (qmail 44872 invoked by uid 60001); 14 Oct 2008 14:24:13 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
	b=2l4V4Buuxli1VOQmyWk3v51PwAc4hHoJdXPe/FBv6luNkkdqijgWDFGU8HMrsysiLI+sbfAkx736p1UUebkemtk8wLFA9LuJMOsCmY1qQzy/DWUfHt6yxPeDH4mCSriDDegURfceUsRHGki+j8wdIhP78AaWwOdA3wP5zHekg/4=;
X-YMail-OSG: W_8khRsVM1lHRjxVYrkKyA9POUBPqHQWuFYtwCRkmllhA6uwWS8SADv_of7Gml94qUpW15KRHrhA_V5pfg77z64OF0vZ5Dd4dGqsm2sJ_h_GwVsUhV0D65bXPxtd_wySoZSGIHkTAaNT.QV09VBJjfyinaXYfkq5vfnWk3Mb2MEZ2IxOfc0w0YUXXg--
Received: from [76.254.90.187] by web33305.mail.mud.yahoo.com via HTTP;
	Tue, 14 Oct 2008 07:24:13 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Tue, 14 Oct 2008 07:24:13 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: int-area@ietf.org, Julien Laganier <julien.laganier.ietf@googlemail.com>
In-Reply-To: <200810141307.24875.julien.laganier.IETF@googlemail.com>
MIME-Version: 1.0
Message-ID: <395866.44476.qm@web33305.mail.mud.yahoo.com>
Cc: Behave WG <behave@ietf.org>, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area]   WGLC: draft-ietf-behave-nat-icmp-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: srisuresh@yahoo.com
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks, Julien. This is a good data point. DO you know if the network has NAT devices, that also respond to the router discovery messages?

regards,
suresh

--- On Tue, 10/14/08, Julien Laganier <julien.laganier.ietf@googlemail.com> wrote:

> From: Julien Laganier <julien.laganier.ietf@googlemail.com>
> Subject: Re: [Int-area] [BEHAVE]  WGLC: draft-ietf-behave-nat-icmp-09
> To: int-area@ietf.org, srisuresh@yahoo.com
> Cc: "Behave WG" <behave@ietf.org>, "Fernando Gont" <fernando@gont.com.ar>, behave-chairs@tools.ietf.org
> Date: Tuesday, October 14, 2008, 4:07 AM
> Suresh,
> 
> FWIW, I've seen ICMP router discovery being used
> extensively in at least 
> one large managed network.
> 
> --julien
> 
> On Monday 13 October 2008, Pyda Srisuresh wrote:
> > Folks,
> >
> > The "Router advertisements and
> solicitations" message appears to be
> > rarely used in Ipv4 networks. Please let me know if
> anyone has
> > objections to changing the requirement for this
> message to MAY from
> > MUST for NATs. If I dont hear any objection, I will
> convert this to
> > MAY in the next rev of the draft.
> >
> > Thanks.
> >
> > regards,
> > suresh
> >
> > --- On Wed, 10/8/08, Pyda Srisuresh
> <srisuresh@yahoo.com> wrote:
> > > From: Pyda Srisuresh <srisuresh@yahoo.com>
> > > Subject: Re: [BEHAVE] [Int-area] WGLC:
> > > draft-ietf-behave-nat-icmp-09 To: "Behave
> WG" <behave@ietf.org>,
> > > "'Internet Area'"
> <int-area@ietf.org>, "Fernando Gont"
> > > <fernando@gont.com.ar> Cc:
> behave-chairs@tools.ietf.org
> > > Date: Wednesday, October 8, 2008, 10:49 PM
> > > --- On Wed, 10/8/08, Fernando Gont
> > >
> > > <fernando@gont.com.ar> wrote:
> > > > From: Fernando Gont
> <fernando@gont.com.ar>
> > > > Subject: Re: [BEHAVE] [Int-area] WGLC:
> > >
> > > draft-ietf-behave-nat-icmp-09
> > >
> > > > To: srisuresh@yahoo.com, "Behave
> WG"
> > >
> > > <behave@ietf.org>, "'Internet
> Area'"
> > > <int-area@ietf.org>
> > >
> > > > Cc: behave-chairs@tools.ietf.org
> > > > Date: Wednesday, October 8, 2008, 5:37 PM
> > > > Hello, Pyda,
> > > >
> > > > Comments in-line...
> > > >
> > > > > > >    REQ-9: A NAT device MAY
> implement a
> > > >
> > > > policy control
> > > >
> > > > > > that prevents
> > > > > >
> > > > > > >    ICMP messages being
> generated toward
> > > >
> > > > certain
> > > >
> > > > > > interface(s).
> > > > > >
> > > > > > >    Implementation of such a
> policy
> > >
> > > control
> > >
> > > > overrides
> > > >
> > > > > > the MUSTs in
> > > > > >
> > > > > > >    REQ-10.
> > > > > >
> > > > > > Then.... shouldn't the
> requirements be
> > > > > > "SHOULD"s rather than
> > > >
> > > > "MUST"s?
> > > >
> > > > >[suresh] Essentially, the objective is
> not to
> > >
> > > dilute
> > >
> > > > the MUST or
> > > >
> > > > >SHOULD requirement on the NAT device,
> but to give
> > >
> > > the
> > >
> > > > device admin
> > > >
> > > > >an override capability. So, if the admin
> chooses
> > >
> > > to
> > >
> > > > enforce local
> > > >
> > > > >policies to override NAT operation, then
> the NAT
> > >
> > > device
> > >
> > > > MAY enforce
> > > >
> > > > >the local policy control. Would the
> following
> > >
> > > revised
> > >
> > > > wording work for you?
> > > >
> > > > >Implementation of such a policy control
> overrides
> > >
> > > the
> > >
> > > > MUSTs and
> > > >
> > > > >SHOULDs in REQ-10.
> > > >
> > > > Any would work for me. I was just wondering
> if it was
> > > > correct (from a
> > > > the perspective of RFC2119) to include a
> MUST that
> > >
> > > could be
> > >
> > > > overiden.
> > > > That is, I was wondering if that means that
> the
> > > > "requirements" should
> > > > be a "SHOULD" rather than a
> > >
> > > "MUST".
> > >
> > > > > > >           5. Router
> Advertisement and
> > > >
> > > > Solicitations,
> > > >
> > > > > > as described in
> > > > > >
> > > > > > >              Section 4.3.3.10
> of
> > >
> > > [RFC1812].
> > >
> > > > > > Does anybody actually use these
> ICMPv4
> > >
> > > messages?
> > >
> > > > I do
> > > >
> > > > > > recall Windows
> > > > > > systems sending these messages
> when they are
> > > >
> > > > bootstrapped,
> > > >
> > > > > > but...
> > > > >
> > > > >[suresh] If the WG believes any of these
> ought to
> > >
> > > be
> > >
> > > > obsoleted for
> > > >
> > > > >NAT devices, one option would be to
> dilute the
> > > >
> > > > requirement to MAY
> > > >
> > > > >for NATs in this document. However, we
> need to
> > >
> > > provide
> > >
> > > > sufficient
> > > >
> > > > >justification for any deviation for NATs
> from RFC
> > >
> > > 1812.
> > >
> > > > While these messages are a "MUST"
> in
> > >
> > > RFC1812, my
> > >
> > > > take is that RFC1812
> > > > is outdated in this respect, and that we
> should not
> > > > *require* them
> > > > for NATs. I'm not saying we should
> obsolete these
> > > > messages here (it
> > > > would be out of the scope of the document),
> but rather
> > >
> > > that
> > >
> > > > we should
> > > > not require NATs to support these messages
> that nobody
> > > > (that I know
> > > > of) is depending on.
> > >
> > > [suresh] Agreed. Do you suggest diluting both of
> the below
> > > MUSTs into MAY for NATs.
> > >
> > >           3. Parameter Problem Message,
> > >           5. Router Advertisement and
> Solicitations
> > >
> > > > > > >        b. MAY support:
> > > > > > >           1. Redirect
> Message, as
> > >
> > > described
> > >
> > > > in Section
> > > >
> > > > > > 4.3.3.2 of
> > > > > >
> > > > > > >              [RFC1812],
> > > > > >
> > > > > > If anything, I'd add that
> support should
> > > >
> > > > default to
> > > >
> > > > > > "off".
> > > > >
> > > > >[suresh] RFC1812 already has MAY
> requirement on
> > >
> > > this
> > >
> > > > and doesnot
> > > >
> > > > >mandate this. RFC 1812 says:
> > > >
> > > > MAYs are less of a concern to me (as they
> give you the
> > > > option to
> > > > support them, but do not require you to).
> > >
> > > [suresh] OK.
> > >
> > > > >    Contrary to [INTRO:2], a router MAY
> ignore
> > >
> > > ICMP
> > >
> > > > Redirects when
> > > >
> > > > >    choosing a path for a packet
> originated by the
> > > >
> > > > router if the router
> > > >
> > > > >    is running a routing protocol or if
> forwarding
> > >
> > > is
> > >
> > > > enabled on the
> > > >
> > > > >    router and on the interface over
> which the
> > >
> > > packet
> > >
> > > > is being sent.
> > > >
> > > > My take here is that the spirit f RFC1812 is
> that you
> > >
> > > can
> > >
> > > > discard
> > > > redirects *if* you are running a routing
> protocol
> > >
> > > (i.e.,
> > >
> > > > you're
> > > > knowledgeable about routing). However, it
> would be
> > >
> > > insane
> > >
> > > > to honor
> > > > redirects nowadays.... unless you're
> enforcing
> > > > something like GTSM
> > > > (the TTL hack). If not, basically anybody
> could DoS
> > >
> > > you by
> > >
> > > > sending
> > > > you a forged ICMP redirect.
> > > >
> > > > In anycase, as I said above, given that this
> is a MAY
> > >
> > > in
> > >
> > > > your
> > > > document, no changes are needed (i.e., you
> are not
> > > > mandating support
> > > > for redirects).
> > >
> > > [suresh] Right.
> > >
> > > > > > >           4. Address Mask
> Request/Reply
> > > >
> > > > Message, as
> > > >
> > > > > > described in
> > > > > >
> > > > > > >              Section 7.4 of
> this
> > >
> > > document.
> > >
> > > > > > AFAIK, these messages are not used
> in
> > >
> > > practice
> > >
> > > > (even when a
> > > >
> > > > > > number of
> > > > > > systems support them).
> Shouldn't they be
> > > >
> > > > deprecated as
> > > >
> > > > > > with the
> > > > > > information request/response?
> > > > >
> > > > >[suresh] I believe, It is not in the
> scope of this
> > > >
> > > > document to
> > > >
> > > > >deprecate ICMP messages or their use
> outside of
> > >
> > > NATs.
> > >
> > > > >For this reason, the requirement for
> Address mask
> > > >
> > > > request/Reply
> > > >
> > > > >support for NATs is diluted to MAY (from
> MUST in
> > >
> > > RFC
> > >
> > > > 1812).
> > > >
> > > > Same here. I have no real concerns here.
> > >
> > > [suresh] OK.
> > >
> > > Regards,
> > > suresh
> > >
> > > > Kind regards,
> > > >
> > > > --
> > > > Fernando Gont
> > > > e-mail: fernando@gont.com.ar ||
> fgont@acm.org
> > > > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9
> 3945 96EE
> > >
> > > A9EF
> > >
> > > > D076 FFF1
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area
> 
> 
> 
> -- 
> --julien
> 
> [ New email address: julien.laganier.IETF@googlemail.com ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 14 08:19:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EBC228C1DD;
	Tue, 14 Oct 2008 08:19:43 -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 6398B3A6889
	for <behave@core3.amsl.com>; Tue, 14 Oct 2008 04:07: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=[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 hiWbj2YVHxfF for <behave@core3.amsl.com>;
	Tue, 14 Oct 2008 04:07:04 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27])
	by core3.amsl.com (Postfix) with ESMTP id DB2143A69C6
	for <behave@ietf.org>; Tue, 14 Oct 2008 04:07:03 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so834777eyd.31
	for <behave@ietf.org>; Tue, 14 Oct 2008 04:07:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:to:subject:date:user-agent:cc
	:references:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:message-id:from;
	bh=L396HsHhMkaOkpk0jLzi65AURuXlU7gWpvzDwSv0P+s=;
	b=OOaLfl/u6LVasC6ARqkJhd3iMzBjyNB/Gd5RftpQkyzITWgaAfpxeGHdOSjBh8y573
	XpEYsP/8Zc7AEWC9lhIWqjqB+dPIzf1RJnOn+kzd4IbeG7QlOmgU1R8romqfa1FRrlQg
	YMMTxi3ytReKF1N0dEzkDhuc0Ahym9nzZfVNg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=to:subject:date:user-agent:cc:references:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:message-id:from;
	b=Uw7HMNQ6mJQ7wVRbYUd+O4VakE0/loWLeX2yA7bEnCjozCYj3OBZ6qCAkqaeNAs9yB
	KNc5Pk04T7vxTQ/ibKAbXOL6z9nwBizGvg/h2x6/qjt4E4cxFx1zKZpV3+YRZvVSjwBg
	XYR1Hk2FOyCSq4jeMZCy2nEv1bWJiyR8BpZfg=
Received: by 10.210.67.20 with SMTP id p20mr7104408eba.116.1223982448331;
	Tue, 14 Oct 2008 04:07:28 -0700 (PDT)
Received: from klee.local ([212.119.9.178])
	by mx.google.com with ESMTPS id m5sm10391850gve.3.2008.10.14.04.07.26
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 14 Oct 2008 04:07:27 -0700 (PDT)
To: int-area@ietf.org,
 srisuresh@yahoo.com
Date: Tue, 14 Oct 2008 13:07:24 +0200
User-Agent: KMail/1.9.9
References: <673187.24451.qm@web33308.mail.mud.yahoo.com>
In-Reply-To: <673187.24451.qm@web33308.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810141307.24875.julien.laganier.IETF@googlemail.com>
From: Julien Laganier <julien.laganier.ietf@googlemail.com>
X-Mailman-Approved-At: Tue, 14 Oct 2008 08:19:43 -0700
Cc: Behave WG <behave@ietf.org>, behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area]   WGLC: draft-ietf-behave-nat-icmp-09
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Suresh,

FWIW, I've seen ICMP router discovery being used extensively in at least 
one large managed network.

--julien

On Monday 13 October 2008, Pyda Srisuresh wrote:
> Folks,
>
> The "Router advertisements and solicitations" message appears to be
> rarely used in Ipv4 networks. Please let me know if anyone has
> objections to changing the requirement for this message to MAY from
> MUST for NATs. If I dont hear any objection, I will convert this to
> MAY in the next rev of the draft.
>
> Thanks.
>
> regards,
> suresh
>
> --- On Wed, 10/8/08, Pyda Srisuresh <srisuresh@yahoo.com> wrote:
> > From: Pyda Srisuresh <srisuresh@yahoo.com>
> > Subject: Re: [BEHAVE] [Int-area] WGLC:
> > draft-ietf-behave-nat-icmp-09 To: "Behave WG" <behave@ietf.org>,
> > "'Internet Area'" <int-area@ietf.org>, "Fernando Gont"
> > <fernando@gont.com.ar> Cc: behave-chairs@tools.ietf.org
> > Date: Wednesday, October 8, 2008, 10:49 PM
> > --- On Wed, 10/8/08, Fernando Gont
> >
> > <fernando@gont.com.ar> wrote:
> > > From: Fernando Gont <fernando@gont.com.ar>
> > > Subject: Re: [BEHAVE] [Int-area] WGLC:
> >
> > draft-ietf-behave-nat-icmp-09
> >
> > > To: srisuresh@yahoo.com, "Behave WG"
> >
> > <behave@ietf.org>, "'Internet Area'"
> > <int-area@ietf.org>
> >
> > > Cc: behave-chairs@tools.ietf.org
> > > Date: Wednesday, October 8, 2008, 5:37 PM
> > > Hello, Pyda,
> > >
> > > Comments in-line...
> > >
> > > > > >    REQ-9: A NAT device MAY implement a
> > >
> > > policy control
> > >
> > > > > that prevents
> > > > >
> > > > > >    ICMP messages being generated toward
> > >
> > > certain
> > >
> > > > > interface(s).
> > > > >
> > > > > >    Implementation of such a policy
> >
> > control
> >
> > > overrides
> > >
> > > > > the MUSTs in
> > > > >
> > > > > >    REQ-10.
> > > > >
> > > > > Then.... shouldn't the requirements be
> > > > > "SHOULD"s rather than
> > >
> > > "MUST"s?
> > >
> > > >[suresh] Essentially, the objective is not to
> >
> > dilute
> >
> > > the MUST or
> > >
> > > >SHOULD requirement on the NAT device, but to give
> >
> > the
> >
> > > device admin
> > >
> > > >an override capability. So, if the admin chooses
> >
> > to
> >
> > > enforce local
> > >
> > > >policies to override NAT operation, then the NAT
> >
> > device
> >
> > > MAY enforce
> > >
> > > >the local policy control. Would the following
> >
> > revised
> >
> > > wording work for you?
> > >
> > > >Implementation of such a policy control overrides
> >
> > the
> >
> > > MUSTs and
> > >
> > > >SHOULDs in REQ-10.
> > >
> > > Any would work for me. I was just wondering if it was
> > > correct (from a
> > > the perspective of RFC2119) to include a MUST that
> >
> > could be
> >
> > > overiden.
> > > That is, I was wondering if that means that the
> > > "requirements" should
> > > be a "SHOULD" rather than a
> >
> > "MUST".
> >
> > > > > >           5. Router Advertisement and
> > >
> > > Solicitations,
> > >
> > > > > as described in
> > > > >
> > > > > >              Section 4.3.3.10 of
> >
> > [RFC1812].
> >
> > > > > Does anybody actually use these ICMPv4
> >
> > messages?
> >
> > > I do
> > >
> > > > > recall Windows
> > > > > systems sending these messages when they are
> > >
> > > bootstrapped,
> > >
> > > > > but...
> > > >
> > > >[suresh] If the WG believes any of these ought to
> >
> > be
> >
> > > obsoleted for
> > >
> > > >NAT devices, one option would be to dilute the
> > >
> > > requirement to MAY
> > >
> > > >for NATs in this document. However, we need to
> >
> > provide
> >
> > > sufficient
> > >
> > > >justification for any deviation for NATs from RFC
> >
> > 1812.
> >
> > > While these messages are a "MUST" in
> >
> > RFC1812, my
> >
> > > take is that RFC1812
> > > is outdated in this respect, and that we should not
> > > *require* them
> > > for NATs. I'm not saying we should obsolete these
> > > messages here (it
> > > would be out of the scope of the document), but rather
> >
> > that
> >
> > > we should
> > > not require NATs to support these messages that nobody
> > > (that I know
> > > of) is depending on.
> >
> > [suresh] Agreed. Do you suggest diluting both of the below
> > MUSTs into MAY for NATs.
> >
> >           3. Parameter Problem Message,
> >           5. Router Advertisement and Solicitations
> >
> > > > > >        b. MAY support:
> > > > > >           1. Redirect Message, as
> >
> > described
> >
> > > in Section
> > >
> > > > > 4.3.3.2 of
> > > > >
> > > > > >              [RFC1812],
> > > > >
> > > > > If anything, I'd add that support should
> > >
> > > default to
> > >
> > > > > "off".
> > > >
> > > >[suresh] RFC1812 already has MAY requirement on
> >
> > this
> >
> > > and doesnot
> > >
> > > >mandate this. RFC 1812 says:
> > >
> > > MAYs are less of a concern to me (as they give you the
> > > option to
> > > support them, but do not require you to).
> >
> > [suresh] OK.
> >
> > > >    Contrary to [INTRO:2], a router MAY ignore
> >
> > ICMP
> >
> > > Redirects when
> > >
> > > >    choosing a path for a packet originated by the
> > >
> > > router if the router
> > >
> > > >    is running a routing protocol or if forwarding
> >
> > is
> >
> > > enabled on the
> > >
> > > >    router and on the interface over which the
> >
> > packet
> >
> > > is being sent.
> > >
> > > My take here is that the spirit f RFC1812 is that you
> >
> > can
> >
> > > discard
> > > redirects *if* you are running a routing protocol
> >
> > (i.e.,
> >
> > > you're
> > > knowledgeable about routing). However, it would be
> >
> > insane
> >
> > > to honor
> > > redirects nowadays.... unless you're enforcing
> > > something like GTSM
> > > (the TTL hack). If not, basically anybody could DoS
> >
> > you by
> >
> > > sending
> > > you a forged ICMP redirect.
> > >
> > > In anycase, as I said above, given that this is a MAY
> >
> > in
> >
> > > your
> > > document, no changes are needed (i.e., you are not
> > > mandating support
> > > for redirects).
> >
> > [suresh] Right.
> >
> > > > > >           4. Address Mask Request/Reply
> > >
> > > Message, as
> > >
> > > > > described in
> > > > >
> > > > > >              Section 7.4 of this
> >
> > document.
> >
> > > > > AFAIK, these messages are not used in
> >
> > practice
> >
> > > (even when a
> > >
> > > > > number of
> > > > > systems support them). Shouldn't they be
> > >
> > > deprecated as
> > >
> > > > > with the
> > > > > information request/response?
> > > >
> > > >[suresh] I believe, It is not in the scope of this
> > >
> > > document to
> > >
> > > >deprecate ICMP messages or their use outside of
> >
> > NATs.
> >
> > > >For this reason, the requirement for Address mask
> > >
> > > request/Reply
> > >
> > > >support for NATs is diluted to MAY (from MUST in
> >
> > RFC
> >
> > > 1812).
> > >
> > > Same here. I have no real concerns here.
> >
> > [suresh] OK.
> >
> > Regards,
> > suresh
> >
> > > Kind regards,
> > >
> > > --
> > > Fernando Gont
> > > e-mail: fernando@gont.com.ar || fgont@acm.org
> > > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE
> >
> > A9EF
> >
> > > D076 FFF1
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area



-- 
--julien

[ New email address: julien.laganier.IETF@googlemail.com ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Oct 15 04:30:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C066928C205;
	Wed, 15 Oct 2008 04:30:56 -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 E68E828C205
	for <behave@core3.amsl.com>; Wed, 15 Oct 2008 04:30:55 -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 IYOnWI90eUlO for <behave@core3.amsl.com>;
	Wed, 15 Oct 2008 04:30:54 -0700 (PDT)
Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.178])
	by core3.amsl.com (Postfix) with ESMTP id CC1873A68B0
	for <behave@ietf.org>; Wed, 15 Oct 2008 04:30:53 -0700 (PDT)
Received: by ik-out-1112.google.com with SMTP id c30so1964606ika.5
	for <behave@ietf.org>; Wed, 15 Oct 2008 04:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:to:subject:date:user-agent:cc
	:references:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:message-id:from;
	bh=e71m+tr1TCgS4D8qfJZBNmQPU4xrgrcSDa1HsJSKTBo=;
	b=kGFXtRqR9yEGnGlWMzW43XqpfSlgt1oXZoaldvyywpLzFRebP8+W3ng3IdOehbq5p6
	5KYmftaPC8+R5FoDxLUqh50eJwBNGcx8uMb2bkXvdXnM4HhQ8XJdk7EXAoqm7U7Bd09P
	DPI7ZzYRjP8S5TQJnAKUYR+fOE6zrW1Q6TQLw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=to:subject:date:user-agent:cc:references:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:message-id:from;
	b=cQYKqirei0+c4h3FLM+qQJsBOR5kbRY0/9vLHZQEKWtF2uYHVnaN0QoXqHMxvTy7zJ
	LuM3XxWxRsi+UvCdj8HpNWkcA3iB5cbQ2Ehyr+aUdZqs2Z8WL04XA2aoLx9LxkrCHB2/
	LzMm/1t5F0bqfsSvihJyXJPknv0piVDs52VCs=
Received: by 10.210.130.14 with SMTP id c14mr1053793ebd.63.1224070258979;
	Wed, 15 Oct 2008 04:30:58 -0700 (PDT)
Received: from klee.local ([212.119.9.178])
	by mx.google.com with ESMTPS id q9sm2532126gve.5.2008.10.15.04.30.56
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 15 Oct 2008 04:30:57 -0700 (PDT)
To: srisuresh@yahoo.com
Date: Wed, 15 Oct 2008 13:30:58 +0200
User-Agent: KMail/1.9.9
References: <395866.44476.qm@web33305.mail.mud.yahoo.com>
In-Reply-To: <395866.44476.qm@web33305.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810151330.59231.julien.laganier.IETF@googlemail.com>
From: Julien Laganier <julien.laganier.ietf@googlemail.com>
Cc: Behave WG <behave@ietf.org>, int-area@ietf.org,
	behave-chairs@tools.ietf.org
Subject: Re: [BEHAVE] [Int-area]   WGLC: draft-ietf-behave-nat-icmp-09
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On Tuesday 14 October 2008, Pyda Srisuresh wrote:
> Thanks, Julien. This is a good data point. DO you know if the network
> has NAT devices, that also respond to the router discovery messages?

To my knowledge the network had no NAT devices.

--julien

> --- On Tue, 10/14/08, Julien Laganier 
<julien.laganier.ietf@googlemail.com> wrote:
> > From: Julien Laganier <julien.laganier.ietf@googlemail.com>
> > Subject: Re: [Int-area] [BEHAVE]  WGLC:
> > draft-ietf-behave-nat-icmp-09 To: int-area@ietf.org,
> > srisuresh@yahoo.com
> > Cc: "Behave WG" <behave@ietf.org>, "Fernando Gont"
> > <fernando@gont.com.ar>, behave-chairs@tools.ietf.org Date: Tuesday,
> > October 14, 2008, 4:07 AM
> > Suresh,
> >
> > FWIW, I've seen ICMP router discovery being used
> > extensively in at least
> > one large managed network.
> >
> > --julien
> >
> > On Monday 13 October 2008, Pyda Srisuresh wrote:
> > > Folks,
> > >
> > > The "Router advertisements and
> >
> > solicitations" message appears to be
> >
> > > rarely used in Ipv4 networks. Please let me know if
> >
> > anyone has
> >
> > > objections to changing the requirement for this
> >
> > message to MAY from
> >
> > > MUST for NATs. If I dont hear any objection, I will
> >
> > convert this to
> >
> > > MAY in the next rev of the draft.
> > >
> > > Thanks.
> > >
> > > regards,
> > > suresh
> > >
> > > --- On Wed, 10/8/08, Pyda Srisuresh
> >
> > <srisuresh@yahoo.com> wrote:
> > > > From: Pyda Srisuresh <srisuresh@yahoo.com>
> > > > Subject: Re: [BEHAVE] [Int-area] WGLC:
> > > > draft-ietf-behave-nat-icmp-09 To: "Behave
> >
> > WG" <behave@ietf.org>,
> >
> > > > "'Internet Area'"
> >
> > <int-area@ietf.org>, "Fernando Gont"
> >
> > > > <fernando@gont.com.ar> Cc:
> >
> > behave-chairs@tools.ietf.org
> >
> > > > Date: Wednesday, October 8, 2008, 10:49 PM
> > > > --- On Wed, 10/8/08, Fernando Gont
> > > >
> > > > <fernando@gont.com.ar> wrote:
> > > > > From: Fernando Gont
> >
> > <fernando@gont.com.ar>
> >
> > > > > Subject: Re: [BEHAVE] [Int-area] WGLC:
> > > >
> > > > draft-ietf-behave-nat-icmp-09
> > > >
> > > > > To: srisuresh@yahoo.com, "Behave
> >
> > WG"
> >
> > > > <behave@ietf.org>, "'Internet
> >
> > Area'"
> >
> > > > <int-area@ietf.org>
> > > >
> > > > > Cc: behave-chairs@tools.ietf.org
> > > > > Date: Wednesday, October 8, 2008, 5:37 PM
> > > > > Hello, Pyda,
> > > > >
> > > > > Comments in-line...
> > > > >
> > > > > > > >    REQ-9: A NAT device MAY
> >
> > implement a
> >
> > > > > policy control
> > > > >
> > > > > > > that prevents
> > > > > > >
> > > > > > > >    ICMP messages being
> >
> > generated toward
> >
> > > > > certain
> > > > >
> > > > > > > interface(s).
> > > > > > >
> > > > > > > >    Implementation of such a
> >
> > policy
> >
> > > > control
> > > >
> > > > > overrides
> > > > >
> > > > > > > the MUSTs in
> > > > > > >
> > > > > > > >    REQ-10.
> > > > > > >
> > > > > > > Then.... shouldn't the
> >
> > requirements be
> >
> > > > > > > "SHOULD"s rather than
> > > > >
> > > > > "MUST"s?
> > > > >
> > > > > >[suresh] Essentially, the objective is
> >
> > not to
> >
> > > > dilute
> > > >
> > > > > the MUST or
> > > > >
> > > > > >SHOULD requirement on the NAT device,
> >
> > but to give
> >
> > > > the
> > > >
> > > > > device admin
> > > > >
> > > > > >an override capability. So, if the admin
> >
> > chooses
> >
> > > > to
> > > >
> > > > > enforce local
> > > > >
> > > > > >policies to override NAT operation, then
> >
> > the NAT
> >
> > > > device
> > > >
> > > > > MAY enforce
> > > > >
> > > > > >the local policy control. Would the
> >
> > following
> >
> > > > revised
> > > >
> > > > > wording work for you?
> > > > >
> > > > > >Implementation of such a policy control
> >
> > overrides
> >
> > > > the
> > > >
> > > > > MUSTs and
> > > > >
> > > > > >SHOULDs in REQ-10.
> > > > >
> > > > > Any would work for me. I was just wondering
> >
> > if it was
> >
> > > > > correct (from a
> > > > > the perspective of RFC2119) to include a
> >
> > MUST that
> >
> > > > could be
> > > >
> > > > > overiden.
> > > > > That is, I was wondering if that means that
> >
> > the
> >
> > > > > "requirements" should
> > > > > be a "SHOULD" rather than a
> > > >
> > > > "MUST".
> > > >
> > > > > > > >           5. Router
> >
> > Advertisement and
> >
> > > > > Solicitations,
> > > > >
> > > > > > > as described in
> > > > > > >
> > > > > > > >              Section 4.3.3.10
> >
> > of
> >
> > > > [RFC1812].
> > > >
> > > > > > > Does anybody actually use these
> >
> > ICMPv4
> >
> > > > messages?
> > > >
> > > > > I do
> > > > >
> > > > > > > recall Windows
> > > > > > > systems sending these messages
> >
> > when they are
> >
> > > > > bootstrapped,
> > > > >
> > > > > > > but...
> > > > > >
> > > > > >[suresh] If the WG believes any of these
> >
> > ought to
> >
> > > > be
> > > >
> > > > > obsoleted for
> > > > >
> > > > > >NAT devices, one option would be to
> >
> > dilute the
> >
> > > > > requirement to MAY
> > > > >
> > > > > >for NATs in this document. However, we
> >
> > need to
> >
> > > > provide
> > > >
> > > > > sufficient
> > > > >
> > > > > >justification for any deviation for NATs
> >
> > from RFC
> >
> > > > 1812.
> > > >
> > > > > While these messages are a "MUST"
> >
> > in
> >
> > > > RFC1812, my
> > > >
> > > > > take is that RFC1812
> > > > > is outdated in this respect, and that we
> >
> > should not
> >
> > > > > *require* them
> > > > > for NATs. I'm not saying we should
> >
> > obsolete these
> >
> > > > > messages here (it
> > > > > would be out of the scope of the document),
> >
> > but rather
> >
> > > > that
> > > >
> > > > > we should
> > > > > not require NATs to support these messages
> >
> > that nobody
> >
> > > > > (that I know
> > > > > of) is depending on.
> > > >
> > > > [suresh] Agreed. Do you suggest diluting both of
> >
> > the below
> >
> > > > MUSTs into MAY for NATs.
> > > >
> > > >           3. Parameter Problem Message,
> > > >           5. Router Advertisement and
> >
> > Solicitations
> >
> > > > > > > >        b. MAY support:
> > > > > > > >           1. Redirect
> >
> > Message, as
> >
> > > > described
> > > >
> > > > > in Section
> > > > >
> > > > > > > 4.3.3.2 of
> > > > > > >
> > > > > > > >              [RFC1812],
> > > > > > >
> > > > > > > If anything, I'd add that
> >
> > support should
> >
> > > > > default to
> > > > >
> > > > > > > "off".
> > > > > >
> > > > > >[suresh] RFC1812 already has MAY
> >
> > requirement on
> >
> > > > this
> > > >
> > > > > and doesnot
> > > > >
> > > > > >mandate this. RFC 1812 says:
> > > > >
> > > > > MAYs are less of a concern to me (as they
> >
> > give you the
> >
> > > > > option to
> > > > > support them, but do not require you to).
> > > >
> > > > [suresh] OK.
> > > >
> > > > > >    Contrary to [INTRO:2], a router MAY
> >
> > ignore
> >
> > > > ICMP
> > > >
> > > > > Redirects when
> > > > >
> > > > > >    choosing a path for a packet
> >
> > originated by the
> >
> > > > > router if the router
> > > > >
> > > > > >    is running a routing protocol or if
> >
> > forwarding
> >
> > > > is
> > > >
> > > > > enabled on the
> > > > >
> > > > > >    router and on the interface over
> >
> > which the
> >
> > > > packet
> > > >
> > > > > is being sent.
> > > > >
> > > > > My take here is that the spirit f RFC1812 is
> >
> > that you
> >
> > > > can
> > > >
> > > > > discard
> > > > > redirects *if* you are running a routing
> >
> > protocol
> >
> > > > (i.e.,
> > > >
> > > > > you're
> > > > > knowledgeable about routing). However, it
> >
> > would be
> >
> > > > insane
> > > >
> > > > > to honor
> > > > > redirects nowadays.... unless you're
> >
> > enforcing
> >
> > > > > something like GTSM
> > > > > (the TTL hack). If not, basically anybody
> >
> > could DoS
> >
> > > > you by
> > > >
> > > > > sending
> > > > > you a forged ICMP redirect.
> > > > >
> > > > > In anycase, as I said above, given that this
> >
> > is a MAY
> >
> > > > in
> > > >
> > > > > your
> > > > > document, no changes are needed (i.e., you
> >
> > are not
> >
> > > > > mandating support
> > > > > for redirects).
> > > >
> > > > [suresh] Right.
> > > >
> > > > > > > >           4. Address Mask
> >
> > Request/Reply
> >
> > > > > Message, as
> > > > >
> > > > > > > described in
> > > > > > >
> > > > > > > >              Section 7.4 of
> >
> > this
> >
> > > > document.
> > > >
> > > > > > > AFAIK, these messages are not used
> >
> > in
> >
> > > > practice
> > > >
> > > > > (even when a
> > > > >
> > > > > > > number of
> > > > > > > systems support them).
> >
> > Shouldn't they be
> >
> > > > > deprecated as
> > > > >
> > > > > > > with the
> > > > > > > information request/response?
> > > > > >
> > > > > >[suresh] I believe, It is not in the
> >
> > scope of this
> >
> > > > > document to
> > > > >
> > > > > >deprecate ICMP messages or their use
> >
> > outside of
> >
> > > > NATs.
> > > >
> > > > > >For this reason, the requirement for
> >
> > Address mask
> >
> > > > > request/Reply
> > > > >
> > > > > >support for NATs is diluted to MAY (from
> >
> > MUST in
> >
> > > > RFC
> > > >
> > > > > 1812).
> > > > >
> > > > > Same here. I have no real concerns here.
> > > >
> > > > [suresh] OK.
> > > >
> > > > Regards,
> > > > suresh
> > > >
> > > > > Kind regards,
> > > > >
> > > > > --
> > > > > Fernando Gont
> > > > > e-mail: fernando@gont.com.ar ||
> >
> > fgont@acm.org
> >
> > > > > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9
> >
> > 3945 96EE
> >
> > > > A9EF
> > > >
> > > > > D076 FFF1
> > > >
> > > > _______________________________________________
> > > > Behave mailing list
> > > > Behave@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/behave
> > >
> > > _______________________________________________
> > > Int-area mailing list
> > > Int-area@ietf.org
> > > https://www.ietf.org/mailman/listinfo/int-area
> >
> > --
> > --julien
> >
> > [ New email address: julien.laganier.IETF@googlemail.com ]



-- 
--julien

[ New email address: julien.laganier.IETF@googlemail.com ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Oct 15 04:45:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCC1B3A68E5;
	Wed, 15 Oct 2008 04:45:04 -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 9EE353A68B0
	for <behave@core3.amsl.com>; Wed, 15 Oct 2008 04:45: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 pyh78dcxwUpp for <behave@core3.amsl.com>;
	Wed, 15 Oct 2008 04:45:02 -0700 (PDT)
Received: from mail-05.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id C8B943A68E5
	for <behave@ietf.org>; Wed, 15 Oct 2008 04:45:02 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1Kq4nL-0006gp-0a
	for behave@ietf.org; Wed, 15 Oct 2008 07:44:03 -0400
Message-Id: <C0BE72B1-3A80-4860-91B9-EB51412006F2@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
In-Reply-To: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 07:45:56 -0400
References: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Subject: Re: [BEHAVE] TURN: Reduce the channel number range?
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I now know of four people (Cullen, Dan, Remi, and myself) who support  
this idea and I have heard no objections. So unless I hear a strong  
objection, I will make this change in the next version of TURN (coming  
soon).

- Philip

On Thu, 9-Oct-08, at 13:28 , Philip Matthews wrote:

> In the current version of the TURN spec (TURN-10), channel numbers  
> can range from 0x4000 to 0xFFFE, which 0xFFFF reserved for future  
> extensions. This gives approx 49000 channels. (There are no channel  
> numbers in the range 0x0000 to 0x3FFF to allow ChannelData messages  
> to be easily distinguished from other TURN messages).
>
> Cullen recently pointed out to me that 49000 channels is a lot more  
> channels that we currently envision a client ever using, and that it  
> might be good if we reserved some more of these channel numbers in  
> case we need some special channels in the future.
>
> In thinking about Cullen's suggestion, it seems totally impractical  
> to me for a client to even use 10,000 channels, let alone 49,000. I  
> am proposing the following:
> *  0x4000 through 0x7FFF will be used for channel numbers (gives  
> 14,745 channels)
> *  0x8000 through 0xFFFF will be reserved (reserving 32767 numbers  
> for the future)
> To enforce this, the server would reject ChannelBind requests with a  
> CHANNEL-NUMBER value outside of 0x4000 - 0x7FFF
>
> Does it seem a good idea to reserve a significant portion of the  
> possible channel number range?
> Does my concrete proposal seem sensible, or would a different  
> division of the possible channel number space be better?
>
> - Philip
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Thu Oct 16 06:38:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFEB03A682F;
	Thu, 16 Oct 2008 06:38:09 -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 A17983A682F
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 06:38:08 -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 lM881zCKMQeJ for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 06:38:07 -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 6F3D83A6800
	for <behave@ietf.org>; Thu, 16 Oct 2008 06:38:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,423,1220227200"; d="scan'208";a="24497600"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 16 Oct 2008 13:38:38 +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 m9GDccKD024688; 
	Thu, 16 Oct 2008 09:38:38 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9GDcbJa025708;
	Thu, 16 Oct 2008 13:38:38 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:38:04 -0400
Received: from [10.82.254.61] ([10.82.254.61]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:38:04 -0400
Message-ID: <48F743BC.6060302@cisco.com>
Date: Thu, 16 Oct 2008 09:38:04 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <2530BA4A-308C-4149-8C08-56550AA0ECAD@magma.ca>	<200810101025.18081.remi.denis-courmont@nokia.com>	<4C822400-B2AD-4F52-BD37-34775A5C58C3@magma.ca>
	<48F32BBD.9090609@ericsson.com>
In-Reply-To: <48F32BBD.9090609@ericsson.com>
X-OriginalArrivalTime: 16 Oct 2008 13:38:04.0395 (UTC)
	FILETIME=[6A6CCBB0:01C92F94]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2381; t=1224164318;
	x=1225028318; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20TURN=3A=20Handling=20of=20IP
	=20header=20fields |Sender:=20
	|To:=20Magnus=20Westerlund=20<magnus.westerlund@ericsson.co m>;
	bh=hDJ7kS8GSUqvtVBFHdYkmh/1bCRzYYyTk4igpQO64Bg=;
	b=KH8kE7JnU2v5kQYVOlt5IZUpNLIsBbVhe7jI4frq/Nq1atFQewDSOm1rAj
	JTDLAhEx28tzjz7aZaa/IojNLqSkUATxXyb5YUNoSRL9iggEc5LTqDubv0VH
	BmCWJsIIXv;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] TURN: Handling of IP header fields
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I'm OK with putting this back in (though I had previously advocated =

removal along with the rest of the preserving behaviors). However if it =

does go back, I agree it doesn't make sense to include both without =

preference. Especially since, for some of these (like ECN), I'm not sure =

there is really many other choices. So if options A and B are the only =

options, and we say you can do A or B, that is a tautology and not worth =

occupying space in the document.

-Jonathan R.

Magnus Westerlund wrote:
> Philip Matthews skrev:
>> On Fri, 10-Oct-08, at 03:25 , R=E9mi Denis-Courmont wrote:
>>
>>> Well, the preferred behavior remains "preferred", right? I mean, we
>>> should
>>> have something like "The server SHOULD do [preferred behavior]. If
>>> this is
>>> not possible, the server MUST do [alternate behavior] instead."
>>>
>>>> Do people like Cullen's suggestion?
>>> At least I would rather we keep the both behaviors mentioned somehow.
>>>
>> Cullen proposed that the spec NOT express a preference between the two
>> behaviors. Not sure if this was because he felt this was the right way
>> to go, or if that was just to make things easier.
> =

> Personal view, but we really should express which is the preferred one.
> Because I don't think there is anyone here that thinks the alternative
> behavior is better if the relay have no issues with reading the
> information.
> =

> 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
> ----------------------------------------------------------------------
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =


-- =

Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 07:06:11 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 798623A688E;
	Thu, 16 Oct 2008 07:06:11 -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 C00C33A688E
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 07:06:09 -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 TXB9AJ+zg98g for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 07:06:05 -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 966DE3A63D3
	for <behave@ietf.org>; Thu, 16 Oct 2008 07:06:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,423,1220227200"; d="scan'208";a="24470558"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 16 Oct 2008 14:07:06 +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 m9GE76aB008823; 
	Thu, 16 Oct 2008 10:07:06 -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 m9GE7674000080;
	Thu, 16 Oct 2008 14:07:06 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); 
	Thu, 16 Oct 2008 10:07:06 -0400
Received: from [10.82.254.61] ([10.82.254.61]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 10:07:06 -0400
Message-ID: <48F74A89.9010900@cisco.com>
Date: Thu, 16 Oct 2008 10:07:05 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <A24E325E-4F65-4367-9A7A-D15CDA13348C@magma.ca>
	<C0BE72B1-3A80-4860-91B9-EB51412006F2@magma.ca>
In-Reply-To: <C0BE72B1-3A80-4860-91B9-EB51412006F2@magma.ca>
X-OriginalArrivalTime: 16 Oct 2008 14:07:06.0082 (UTC)
	FILETIME=[788D2420:01C92F98]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2328; t=1224166026;
	x=1225030026; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20TURN=3A=20Reduce=20the=20cha
	nnel=20number=20range? |Sender:=20
	|To:=20Philip=20Matthews=20<philip_matthews@magma.ca>;
	bh=gDa9E5gL1+j2B/dGhpnmopW1V9LBy4kL8E+sqd6eQys=;
	b=a0DdSyBqc/KoGo3JxI1F0bIDpJVFV91lQeKhTD3CVhiHdx5MSeQ3mwq9FI
	gzhdmXAAe5HAlCq4hqnIPLXksqs6TEUcasnf/X/NndWd1hzB2eevFxXo5ymm
	UcEB49TWn2;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>
Subject: Re: [BEHAVE] TURN: Reduce the channel number range?
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I'm fine with this too.

-Jonathan R.

Philip Matthews wrote:
> I now know of four people (Cullen, Dan, Remi, and myself) who support 
> this idea and I have heard no objections. So unless I hear a strong 
> objection, I will make this change in the next version of TURN (coming 
> soon).
> 
> - Philip
> 
> On Thu, 9-Oct-08, at 13:28 , Philip Matthews wrote:
> 
>> In the current version of the TURN spec (TURN-10), channel numbers can 
>> range from 0x4000 to 0xFFFE, which 0xFFFF reserved for future 
>> extensions. This gives approx 49000 channels. (There are no channel 
>> numbers in the range 0x0000 to 0x3FFF to allow ChannelData messages to 
>> be easily distinguished from other TURN messages).
>>
>> Cullen recently pointed out to me that 49000 channels is a lot more 
>> channels that we currently envision a client ever using, and that it 
>> might be good if we reserved some more of these channel numbers in 
>> case we need some special channels in the future.
>>
>> In thinking about Cullen's suggestion, it seems totally impractical to 
>> me for a client to even use 10,000 channels, let alone 49,000. I am 
>> proposing the following:
>> *  0x4000 through 0x7FFF will be used for channel numbers (gives 
>> 14,745 channels)
>> *  0x8000 through 0xFFFF will be reserved (reserving 32767 numbers for 
>> the future)
>> To enforce this, the server would reject ChannelBind requests with a 
>> CHANNEL-NUMBER value outside of 0x4000 - 0x7FFF
>>
>> Does it seem a good idea to reserve a significant portion of the 
>> possible channel number range?
>> Does my concrete proposal seem sensible, or would a different division 
>> of the possible channel number space be better?
>>
>> - Philip
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 07:13:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EBB5A3A698E;
	Thu, 16 Oct 2008 07:13:44 -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 070E03A688E
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 07:13:44 -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 phieb+YJDjhm for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 07:13:42 -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 86BBE3A698E
	for <behave@ietf.org>; Thu, 16 Oct 2008 07:13:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,423,1220227200"; d="scan'208";a="24502715"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 16 Oct 2008 14:14:43 +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 m9GEEhXf013734; 
	Thu, 16 Oct 2008 10:14:43 -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 m9GEEh1H003614;
	Thu, 16 Oct 2008 14:14:43 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 10:14:43 -0400
Received: from [10.82.254.61] ([10.82.254.61]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 10:14:43 -0400
Message-ID: <48F74C52.4030203@cisco.com>
Date: Thu, 16 Oct 2008 10:14:42 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>
	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
In-Reply-To: <F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
X-OriginalArrivalTime: 16 Oct 2008 14:14:43.0270 (UTC)
	FILETIME=[890E7E60:01C92F99]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6523; t=1224166483;
	x=1225030483; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20TURN=3A=20Send=20indication=
	20when=20no=20permission=20exists |Sender:=20
	|To:=20Philip=20Matthews=20<philip_matthews@magma.ca>;
	bh=Aiu/5IaeApSBHrQ0UB6CO//L6Qxmz5FBI2QQubtko9M=;
	b=X1ar2eK+SLdT9s2gegh1JMikd9cPJC9BXL4/aJRssmGMtysY17I9Yv4zhJ
	BmZGwrKnHp0dk3g4QJbed48siuAjys7ya3++GAuaitM4vmZhhGzU35M5dv0n
	SUkgkpdMpP;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>, matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

So I just got off the phone with Philip, we were talking about this, and 
here is an interesting idea.

As Philip points out, the CreatePermission is required if you want the 
far end to be able to send you a response to a message delivered via a 
Send indication. So, regardless of the question about whether you can do 
a Send prior to CreatePermission, there *will* need to be a 
CreatePermission for each unique IP address you want to send to, even if 
there will be just a single packet and response from that IP address.

The concern raised by Matthew applies to ICE as well; that for cases 
where there are a lot of candidates, you'll end up sending a 
connectivity check and a CreatePermission, thus increasing the number of 
packets sent for connectivity checks.

The solution we came up with for this is very simple. We allow 
CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes, which 
opens permissions to many IP addresses with one transaction. In the case 
of ICE, after the O/A exchange is done, each agent knows the full set of 
IP addresses it might eventually do a check to. Thus, it would do a 
single CreatePermission to all of them, and then proceed with the checks 
using Send indications. Once ICE completes, if a TURN candidate is 
selected, the client would do a CHannelBind for high volume 
transcations. With this solution, the CreatePermission mechanism imposes 
only a single packet overhead, independent of the number of candidates. 
It can be paralellized with the connectivity checks themselves, and thus 
has no impact on the latency of ICE.

This would work well in conjunction with the proposal that you cannot do 
a Send to a destination without previously doing a CreatePermission.

What do folks think of this solution?

-Jonathan R.

Philip Matthews wrote:
>  From your comments below, it seems that you want to not only send a 
> packet to the peer, but also install a permission, so that a 
> connectivity check packet can be received back from the peer. Thus it 
> seems that your concern is not so much with the topic on this thread 
> (whether a Send indication can be used when no permission exists), but 
> rather with the decision to go with the CreatePermission approach rather 
> than the Send request approach.
> 
> The concern Jonathan and I had with the SendRequest approach was that 
> the STUN state machine inside the TURN client might retransmit the Send 
> request if the Send response was lost. This could result in multiple 
> copies of the data being sent to the peer.
> 
> I am guessing that, in your application, sending multiple copies of the 
> data to the peer is not a problem, and you prefer the efficiency of 
> using a single Send request rather than needing both a CreatePermission 
> and a Send indication.
> 
> Am I correct?
> 
> - Philip
> 
> On Mon, 6-Oct-08, at 16:40 , Matthew Kaufman wrote:
> 
>> Philip Matthews wrote:
>>>
>>> Note that TURN does not REQUIRE that the server use authentication -- 
>>> there may be situations where authentication is not required. 
>>> However, the security of TURN without authentication is poor.
>>>
>> For the IT-organization-provided-proxy case, it needs to be as good as 
>> the HTTP proxy is. Which is to say "anyone who can speak port 80 from 
>> an inside address on the inside network interface is A-OK."
>>
>>> I don't know how much data your client sends to each peer, but if 
>>> there is a fair amount of data, then you will probably want to bind a 
>>> channel to each peer to reduce overhead (from 36 bytes to 4 bytes). 
>>> Two notes when using channels. First, a ChannelBind creates both a 
>>> channel and a permission. Second, there is nothing that stops your 
>>> application from sending ChannelData messages immediately after 
>>> sending the ChannelBind request. In most cases, everything will work 
>>> fine. It is only if the ChannelBind fails that you will have to recover.
>>>
>> The amount of data the client sends to each peer is very small 
>> (potentially just a single packet) when doing session establishment. I 
>> don't want to pay for either the ChannelBind or CreatePermission cost 
>> to get set up to send a single packet to a candidate address that is 
>> quite likely to fail. Once I have a session established then yes, 
>> there's an overhead reduction to be had by doing ChannelBind at the 
>> cost of additional client logic that isn't needed for the native UDP 
>> case. Since in the IT-provided-proxy case we usually care more about 
>> PPS than BPS, the extra 32 bytes aren't actually that big a deal 
>> except when the proxy is on a different continent. But again, until 
>> I've done my initial round of packets to potential candidate 
>> addresses, received a response, and completed my 2nd pair of 
>> handshake, I need a lightweight way of talking to lots more addresses 
>> than I want to do ChannelBind for.
>>> Do you have a suggestion for another way to do things? What would you 
>>> do in a proprietary protocol that is different from the way TURN works?
>> If we did our own protocol we would make the permission mechanism be 
>> an up-front authentication followed by the ability to send to any 
>> address (and get the return traffic), and once we moved away from TURN 
>> we'd probably also use proxy-session-identifying tags so that the 
>> proxy could do the same kind of IP address mobility our transport 
>> protocol supports. (It would mean that the proxy could identify that 
>> this packet was from someone who had already allocated/authenticated 
>> but who has moved to a new IP address (perhaps plugged in at a podium 
>> ethernet jack after being on wireless) and then after a 
>> challenge/response switch the proxy permission to be associated with 
>> the new address). Right now, if a client is forced by IT to go through 
>> a TURN proxy, they lose the IP address mobility they would have had if 
>> they could talk native UDP to the outside.
>>
>> Matthew Kaufman
>>
>>
>>
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 09:35:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 162D73A6A04;
	Thu, 16 Oct 2008 09:35:53 -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 469CD3A6A04
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 09:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.235
X-Spam-Level: 
X-Spam-Status: No, score=-102.235 tagged_above=-999 required=5
	tests=[AWL=0.030, 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 tj3Xo89bIwhm for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 09:35:50 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 8BE0A3A6A38
	for <behave@ietf.org>; Thu, 16 Oct 2008 09:35:50 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id EFE1615BC4018; Thu, 16 Oct 2008 16:36:51 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 74F0815BC4016;
	Thu, 16 Oct 2008 16:36:51 +0000 (UTC)
Message-ID: <48F76DA2.4020406@acm.org>
Date: Thu, 16 Oct 2008 09:36:50 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
	<48F74C52.4030203@cisco.com>
In-Reply-To: <48F74C52.4030203@cisco.com>
Cc: BEHAVE WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Jonathan Rosenberg wrote:
> So I just got off the phone with Philip, we were talking about this, and
> here is an interesting idea.
> 
> As Philip points out, the CreatePermission is required if you want the
> far end to be able to send you a response to a message delivered via a
> Send indication. So, regardless of the question about whether you can do
> a Send prior to CreatePermission, there *will* need to be a
> CreatePermission for each unique IP address you want to send to, even if
> there will be just a single packet and response from that IP address.
> 
> The concern raised by Matthew applies to ICE as well; that for cases
> where there are a lot of candidates, you'll end up sending a
> connectivity check and a CreatePermission, thus increasing the number of
> packets sent for connectivity checks.
> 
> The solution we came up with for this is very simple. We allow
> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes, which
> opens permissions to many IP addresses with one transaction. In the case
> of ICE, after the O/A exchange is done, each agent knows the full set of
> IP addresses it might eventually do a check to. Thus, it would do a
> single CreatePermission to all of them, and then proceed with the checks
> using Send indications. Once ICE completes, if a TURN candidate is
> selected, the client would do a CHannelBind for high volume
> transcations. With this solution, the CreatePermission mechanism imposes
> only a single packet overhead, independent of the number of candidates.
> It can be paralellized with the connectivity checks themselves, and thus
> has no impact on the latency of ICE.
> 
> This would work well in conjunction with the proposal that you cannot do
> a Send to a destination without previously doing a CreatePermission.
> 
> What do folks think of this solution?

I am OK with this, but I am not sure that having multiple
XOR-PEER-ADDRESS attributes would work, because of this sentence in
rfc3489bis:

"Any attribute type MAY appear more than once in a STUN message.
Unless specified otherwise, the order of appearance is significant:
only the first occurance needs to be processed by a receiver, and any
duplicates MAY be ignored by a receiver."

I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating the
family, port and address field for each address.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 09:39:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70BFC3A6A38;
	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: c1b4fb3e-a9e87bb000007a96-f5-48f76e78c774
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: AAAAAA==
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

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


From behave-bounces@ietf.org  Thu Oct 16 10:00:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9CB43A6B56;
	Thu, 16 Oct 2008 10:00:02 -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 B379E3A680A
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 10:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.503
X-Spam-Level: 
X-Spam-Status: No, score=-106.503 tagged_above=-999 required=5
	tests=[AWL=0.096, 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 lHURWgCB51Uk for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 10:00: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 36AE03A682B
	for <behave@ietf.org>; Thu, 16 Oct 2008 09:59:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,424,1220227200"; d="scan'208";a="95915588"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 16 Oct 2008 17:01:00 +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 m9GH10cq007725
	for <behave@ietf.org>; Thu, 16 Oct 2008 10:01: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 m9GH10Ze002481
	for <behave@ietf.org>; Thu, 16 Oct 2008 17:01:00 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, 16 Oct 2008 10:01:00 -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); 
	Thu, 16 Oct 2008 10:01:00 -0700
Message-Id: <5D1F98C1-B5ED-491B-BBB7-D14174A5D5EB@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Behave WG <behave@ietf.org>
In-Reply-To: <48F76EFC.9000703@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 10:01:00 -0700
References: <48F76EFC.9000703@ericsson.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Oct 2008 17:01:00.0283 (UTC)
	FILETIME=[C3D1DCB0:01C92FB0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=884; t=1224176460; x=1225040460;
	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[46translation]=20[Fwd=3A=20[BEHAVE]=20
	Proposal=20for=20new=20BEHAVE=20charter] |Sender:=20;
	bh=6768YWR7fYuxxoGYpEmXgrzI4QxnnoYLVdjTDIEF4BM=;
	b=k+iULDkpkYHok38DSvNnBUgDVLDc1ZQW9ct2RoA45D20ba+Yg3mX59ddV+
	EkbMdYO7dUqdhhOWWkw8Ox5BwNNhu6kqOOTA0ilKn/Ssiwe3X0GsZlbPHawU
	2PFWs3Mf8j;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [BEHAVE] [46translation] [Fwd: 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

what attached message?

On Oct 16, 2008, at 9:42 AM, Magnus Westerlund wrote:

> 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=E4r=F6gatan 6                | Fax   +46 8 7575550
> S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> 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


From behave-bounces@ietf.org  Thu Oct 16 10:11:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 943003A680A;
	Thu, 16 Oct 2008 10:11:47 -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 717C03A6895
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 10:11: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=[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 EmXLybnmXwIh for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 10:11:45 -0700 (PDT)
Received: from mail-08.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id A0F763A6358
	for <behave@ietf.org>; Thu, 16 Oct 2008 10:11:45 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KqWP1-0000Cu-0u; Thu, 16 Oct 2008 13:12:47 -0400
Message-Id: <B892D42F-5346-4767-B960-835B8DECE717@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <48F0E08D.9080205@acm.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 13:12:45 -0400
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
	<48EE50C0.4000803@acm.org>
	<B7A939E1-8800-4E20-8547-B98B8192AD6D@magma.ca>
	<48F0E08D.9080205@acm.org>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Sat, 11-Oct-08, at 13:21 , Marc Petit-Huguenin wrote:

> Philip Matthews wrote:
>> On Thu, 9-Oct-08, at 14:43 , Marc Petit-Huguenin wrote:
>>
>
> [...]
>
>>> - Section 3, definition of 5-tuple:  "...and transport protocol  
>>> (UDP or
>>> TCP))..."
>>>
>>> Can be something else than UDP or TCP.
>>
>> Not sure what you are driving at. Protocols like DCCP or SCTP are not
>> supported for communication with the TURN server (yet).
>>
>
> Yes, but TURN-10 also does not support IPv6, or TCP between the server
> and the peer, but still mention the possibility of using them.

My criterion for mentioning a future extension to TURN has been  
whether or not there exists an accepted Working Group document  
specifying it. Both IPv6 and TCP have such WG documents. By contrast,  
preserving allocations, even though they used to be in the base spec  
and have been discussed at two WG meetings, are not, because there is  
not yet a WG document for them.


But how about:
    "... and transport protocol (currently one of UDP, TCP, or TLS))"
which is both more accurate and suggests (with the word "currently")  
that other possibilities might be defined in the future?

- Philip
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 10:26:31 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C9323A68D2;
	Thu, 16 Oct 2008 10:26:31 -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 D21163A6939
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 10:26: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=[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 anzESb-iMjYN for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 10:26:28 -0700 (PDT)
Received: from mail-07.primus.ca (mail5.primus.ca [216.254.141.172])
	by core3.amsl.com (Postfix) with ESMTP id BF3EA3A682B
	for <behave@ietf.org>; Thu, 16 Oct 2008 10:26:28 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KqWcs-0001iR-05; Thu, 16 Oct 2008 13:27:06 -0400
Message-Id: <9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <48F76DA2.4020406@acm.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 13:27:10 -0400
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
	<48F74C52.4030203@cisco.com> <48F76DA2.4020406@acm.org>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: BEHAVE WG <behave@ietf.org>, matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Thu, 16-Oct-08, at 12:36 , Marc Petit-Huguenin wrote:

> Jonathan Rosenberg wrote:
>> So I just got off the phone with Philip, we were talking about  
>> this, and
>> here is an interesting idea.
>>
>> As Philip points out, the CreatePermission is required if you want  
>> the
>> far end to be able to send you a response to a message delivered  
>> via a
>> Send indication. So, regardless of the question about whether you  
>> can do
>> a Send prior to CreatePermission, there *will* need to be a
>> CreatePermission for each unique IP address you want to send to,  
>> even if
>> there will be just a single packet and response from that IP address.
>>
>> The concern raised by Matthew applies to ICE as well; that for cases
>> where there are a lot of candidates, you'll end up sending a
>> connectivity check and a CreatePermission, thus increasing the  
>> number of
>> packets sent for connectivity checks.
>>
>> The solution we came up with for this is very simple. We allow
>> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes,  
>> which
>> opens permissions to many IP addresses with one transaction. In the  
>> case
>> of ICE, after the O/A exchange is done, each agent knows the full  
>> set of
>> IP addresses it might eventually do a check to. Thus, it would do a
>> single CreatePermission to all of them, and then proceed with the  
>> checks
>> using Send indications. Once ICE completes, if a TURN candidate is
>> selected, the client would do a CHannelBind for high volume
>> transcations. With this solution, the CreatePermission mechanism  
>> imposes
>> only a single packet overhead, independent of the number of  
>> candidates.
>> It can be paralellized with the connectivity checks themselves, and  
>> thus
>> has no impact on the latency of ICE.
>>
>> This would work well in conjunction with the proposal that you  
>> cannot do
>> a Send to a destination without previously doing a CreatePermission.
>>
>> What do folks think of this solution?
>
> I am OK with this, but I am not sure that having multiple
> XOR-PEER-ADDRESS attributes would work, because of this sentence in
> rfc3489bis:
>
> "Any attribute type MAY appear more than once in a STUN message.
> Unless specified otherwise, the order of appearance is significant:
> only the first occurance needs to be processed by a receiver, and any
> duplicates MAY be ignored by a receiver."
>
> I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
> XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating  
> the
> family, port and address field for each address.

Well, our idea was to take advantage of the "Unless specified  
otherwise ..." clause and specify that, for the XOR-PEER-ADDRESS  
attribute in the CreatePermission request, multiple occurrences _are_  
significant. [Option 1]

However, there are two other options:
2) Allow the XOR-PEER-ADDRESS attribute to contain multiple addresses  
for CreatePermission, but not for Send indication, Data indication, or  
ChannelBind, OR
3) Define a new attribute XOR-PEER-ADDRESSES, which is used only in  
CreatePermission, that allows multiple addresses. The existing XOR- 
PEER-ADDRESS would be used in Send indication, Data indication, and  
ChannelBind.

My personal preference is for 1. However, if implementors say "My  
stack won't allow option 1, because it assumes that only the first  
occurrence of an attribute is significant", then we could do option 3  
instead.

- Philip






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


From behave-bounces@ietf.org  Thu Oct 16 10:31:22 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B190E3A6802;
	Thu, 16 Oct 2008 10:31:22 -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 97E753A63D3
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 10:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.238
X-Spam-Level: 
X-Spam-Status: No, score=-102.238 tagged_above=-999 required=5
	tests=[AWL=0.027, 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 CeFKhgyc4VOD for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 10:31:20 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id E19EC3A6802
	for <behave@ietf.org>; Thu, 16 Oct 2008 10:31:20 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id C0D71E3C42C4; Thu, 16 Oct 2008 17:32:22 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id 48855E3C418A;
	Thu, 16 Oct 2008 17:32:19 +0000 (UTC)
Message-ID: <48F77A9E.4010003@acm.org>
Date: Thu, 16 Oct 2008 10:32:14 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
	<48EE50C0.4000803@acm.org>
	<B7A939E1-8800-4E20-8547-B98B8192AD6D@magma.ca>
	<48F0E08D.9080205@acm.org>
	<B892D42F-5346-4767-B960-835B8DECE717@magma.ca>
In-Reply-To: <B892D42F-5346-4767-B960-835B8DECE717@magma.ca>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> 
> On Sat, 11-Oct-08, at 13:21 , Marc Petit-Huguenin wrote:
> 
>> Philip Matthews wrote:
>>> On Thu, 9-Oct-08, at 14:43 , Marc Petit-Huguenin wrote:
>>>
>>
>> [...]
>>
>>>> - Section 3, definition of 5-tuple:  "...and transport protocol (UDP or
>>>> TCP))..."
>>>>
>>>> Can be something else than UDP or TCP.
>>>
>>> Not sure what you are driving at. Protocols like DCCP or SCTP are not
>>> supported for communication with the TURN server (yet).
>>>
>>
>> Yes, but TURN-10 also does not support IPv6, or TCP between the server
>> and the peer, but still mention the possibility of using them.
> 
> My criterion for mentioning a future extension to TURN has been whether
> or not there exists an accepted Working Group document specifying it.
> Both IPv6 and TCP have such WG documents. By contrast, preserving
> allocations, even though they used to be in the base spec and have been
> discussed at two WG meetings, are not, because there is not yet a WG
> document for them.
> 
> 
> But how about:
>    "... and transport protocol (currently one of UDP, TCP, or TLS))"
> which is both more accurate and suggests (with the word "currently")
> that other possibilities might be defined in the future?

OK.

Thanks.

-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 10:35:34 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 364C43A69AD;
	Thu, 16 Oct 2008 10:35:34 -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 0E0AA3A681A
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 10:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.385
X-Spam-Level: 
X-Spam-Status: No, score=-6.385 tagged_above=-999 required=5 tests=[AWL=0.214, 
	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 tkFxOSNH4cGB for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 10:35: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 12B1C3A6802
	for <behave@ietf.org>; Thu, 16 Oct 2008 10:35:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,424,1220227200"; d="scan'208";a="109023379"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 16 Oct 2008 17:36:15 +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 m9GHaFCH028520; 
	Thu, 16 Oct 2008 10:36:15 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9GHaFOr009038;
	Thu, 16 Oct 2008 17:36:15 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); 
	Thu, 16 Oct 2008 13:36:14 -0400
Received: from [10.82.254.61] ([10.82.254.61]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 13:36:14 -0400
Message-ID: <48F77B8E.9070900@cisco.com>
Date: Thu, 16 Oct 2008 13:36:14 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
	<48F74C52.4030203@cisco.com> <48F76DA2.4020406@acm.org>
	<9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
In-Reply-To: <9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
X-OriginalArrivalTime: 16 Oct 2008 17:36:14.0314 (UTC)
	FILETIME=[AFE164A0:01C92FB5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4069; t=1224178575;
	x=1225042575; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20Re=3A=20[BEHAVE]=20TURN=3A=20Send=20indication=
	20when=20no=20permission=20exists |Sender:=20;
	bh=XhvbAYEWql7rBk0H+ChljX9zw7WoHGxBYCkqXLBgk1w=;
	b=Vz/4nnwSaEmimrPK2dAccIIyK8jD5I6i9fEaa63kHQaTwuU6iVBJ1LZmoq
	6EbVA2Obzlk7z5xMYBy02S66LEAcFuLxp4avc+x/8HkLERmwKdDW/HefM5vR
	ENMp64dvsEPtN6QpFYxhoG/L8W32l97PNY6Fzvaa0lMwyUTP/gbZA=;
Authentication-Results: sj-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: BEHAVE WG <behave@ietf.org>, matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I'd suggest option 3 so that we don't violate existing rfc3489bis rules 
and don't introduce additional error cases when XOR-PEER-ADDRESS is used 
in other places.

-Jonathan R.

Philip Matthews wrote:
> 
> On Thu, 16-Oct-08, at 12:36 , Marc Petit-Huguenin wrote:
> 
>> Jonathan Rosenberg wrote:
>>> So I just got off the phone with Philip, we were talking about this, and
>>> here is an interesting idea.
>>>
>>> As Philip points out, the CreatePermission is required if you want the
>>> far end to be able to send you a response to a message delivered via a
>>> Send indication. So, regardless of the question about whether you can do
>>> a Send prior to CreatePermission, there *will* need to be a
>>> CreatePermission for each unique IP address you want to send to, even if
>>> there will be just a single packet and response from that IP address.
>>>
>>> The concern raised by Matthew applies to ICE as well; that for cases
>>> where there are a lot of candidates, you'll end up sending a
>>> connectivity check and a CreatePermission, thus increasing the number of
>>> packets sent for connectivity checks.
>>>
>>> The solution we came up with for this is very simple. We allow
>>> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes, which
>>> opens permissions to many IP addresses with one transaction. In the case
>>> of ICE, after the O/A exchange is done, each agent knows the full set of
>>> IP addresses it might eventually do a check to. Thus, it would do a
>>> single CreatePermission to all of them, and then proceed with the checks
>>> using Send indications. Once ICE completes, if a TURN candidate is
>>> selected, the client would do a CHannelBind for high volume
>>> transcations. With this solution, the CreatePermission mechanism imposes
>>> only a single packet overhead, independent of the number of candidates.
>>> It can be paralellized with the connectivity checks themselves, and thus
>>> has no impact on the latency of ICE.
>>>
>>> This would work well in conjunction with the proposal that you cannot do
>>> a Send to a destination without previously doing a CreatePermission.
>>>
>>> What do folks think of this solution?
>>
>> I am OK with this, but I am not sure that having multiple
>> XOR-PEER-ADDRESS attributes would work, because of this sentence in
>> rfc3489bis:
>>
>> "Any attribute type MAY appear more than once in a STUN message.
>> Unless specified otherwise, the order of appearance is significant:
>> only the first occurance needs to be processed by a receiver, and any
>> duplicates MAY be ignored by a receiver."
>>
>> I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
>> XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating the
>> family, port and address field for each address.
> 
> Well, our idea was to take advantage of the "Unless specified otherwise 
> ..." clause and specify that, for the XOR-PEER-ADDRESS attribute in the 
> CreatePermission request, multiple occurrences _are_ significant. 
> [Option 1]
> 
> However, there are two other options:
> 2) Allow the XOR-PEER-ADDRESS attribute to contain multiple addresses 
> for CreatePermission, but not for Send indication, Data indication, or 
> ChannelBind, OR
> 3) Define a new attribute XOR-PEER-ADDRESSES, which is used only in 
> CreatePermission, that allows multiple addresses. The existing 
> XOR-PEER-ADDRESS would be used in Send indication, Data indication, and 
> ChannelBind.
> 
> My personal preference is for 1. However, if implementors say "My stack 
> won't allow option 1, because it assumes that only the first occurrence 
> of an attribute is significant", then we could do option 3 instead.
> 
> - Philip
> 
> 
> 
> 
> 
> 
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 11:08:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1011F3A6980;
	Thu, 16 Oct 2008 11:08:21 -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 177363A6980
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 11:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level: 
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5
	tests=[AWL=0.025, 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 YzxehCOaJWH1 for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 11:08:19 -0700 (PDT)
Received: from server.implementers.org (server.implementers.org [69.55.225.91])
	by core3.amsl.com (Postfix) with ESMTP id 38EB43A6A6B
	for <behave@ietf.org>; Thu, 16 Oct 2008 11:08:19 -0700 (PDT)
Received: by server.implementers.org (Postfix, from userid 1001)
	id D633EE3C42C8; Thu, 16 Oct 2008 18:09:18 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1])
	by server.implementers.org (Postfix) with ESMTP id F07F2E3C418A;
	Thu, 16 Oct 2008 18:08:51 +0000 (UTC)
Message-ID: <48F78333.8040000@acm.org>
Date: Thu, 16 Oct 2008 11:08:51 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@cisco.com>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
	<48F74C52.4030203@cisco.com> <48F76DA2.4020406@acm.org>
	<9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
	<48F77B8E.9070900@cisco.com>
In-Reply-To: <48F77B8E.9070900@cisco.com>
Cc: BEHAVE WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Jonathan Rosenberg wrote:
> I'd suggest option 3 so that we don't violate existing rfc3489bis rules
> and don't introduce additional error cases when XOR-PEER-ADDRESS is used
> in other places.

OK for me.

> 
> -Jonathan R.
> 
> Philip Matthews wrote:
>>
>> On Thu, 16-Oct-08, at 12:36 , Marc Petit-Huguenin wrote:
>>
>>> Jonathan Rosenberg wrote:
>>>> So I just got off the phone with Philip, we were talking about this,
>>>> and
>>>> here is an interesting idea.
>>>>
>>>> As Philip points out, the CreatePermission is required if you want the
>>>> far end to be able to send you a response to a message delivered via a
>>>> Send indication. So, regardless of the question about whether you
>>>> can do
>>>> a Send prior to CreatePermission, there *will* need to be a
>>>> CreatePermission for each unique IP address you want to send to,
>>>> even if
>>>> there will be just a single packet and response from that IP address.
>>>>
>>>> The concern raised by Matthew applies to ICE as well; that for cases
>>>> where there are a lot of candidates, you'll end up sending a
>>>> connectivity check and a CreatePermission, thus increasing the
>>>> number of
>>>> packets sent for connectivity checks.
>>>>
>>>> The solution we came up with for this is very simple. We allow
>>>> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes, which
>>>> opens permissions to many IP addresses with one transaction. In the
>>>> case
>>>> of ICE, after the O/A exchange is done, each agent knows the full
>>>> set of
>>>> IP addresses it might eventually do a check to. Thus, it would do a
>>>> single CreatePermission to all of them, and then proceed with the
>>>> checks
>>>> using Send indications. Once ICE completes, if a TURN candidate is
>>>> selected, the client would do a CHannelBind for high volume
>>>> transcations. With this solution, the CreatePermission mechanism
>>>> imposes
>>>> only a single packet overhead, independent of the number of candidates.
>>>> It can be paralellized with the connectivity checks themselves, and
>>>> thus
>>>> has no impact on the latency of ICE.
>>>>
>>>> This would work well in conjunction with the proposal that you
>>>> cannot do
>>>> a Send to a destination without previously doing a CreatePermission.
>>>>
>>>> What do folks think of this solution?
>>>
>>> I am OK with this, but I am not sure that having multiple
>>> XOR-PEER-ADDRESS attributes would work, because of this sentence in
>>> rfc3489bis:
>>>
>>> "Any attribute type MAY appear more than once in a STUN message.
>>> Unless specified otherwise, the order of appearance is significant:
>>> only the first occurance needs to be processed by a receiver, and any
>>> duplicates MAY be ignored by a receiver."
>>>
>>> I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
>>> XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating the
>>> family, port and address field for each address.
>>
>> Well, our idea was to take advantage of the "Unless specified
>> otherwise ..." clause and specify that, for the XOR-PEER-ADDRESS
>> attribute in the CreatePermission request, multiple occurrences _are_
>> significant. [Option 1]
>>
>> However, there are two other options:
>> 2) Allow the XOR-PEER-ADDRESS attribute to contain multiple addresses
>> for CreatePermission, but not for Send indication, Data indication, or
>> ChannelBind, OR
>> 3) Define a new attribute XOR-PEER-ADDRESSES, which is used only in
>> CreatePermission, that allows multiple addresses. The existing
>> XOR-PEER-ADDRESS would be used in Send indication, Data indication,
>> and ChannelBind.
>>
>> My personal preference is for 1. However, if implementors say "My
>> stack won't allow option 1, because it assumes that only the first
>> occurrence of an attribute is significant", then we could do option 3
>> instead.
>>
>> - Philip
>>
>>
>>
>>
>>
>>
>>
> 


-- 
Marc Petit-Huguenin           [                                 ]
Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
Work: marc@8x8.com            [                                 ]
[                                                               ]
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 11:21:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E9A73A6A13;
	Thu, 16 Oct 2008 11:21:19 -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 C2B413A684C
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 11:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.507
X-Spam-Level: 
X-Spam-Status: No, score=-106.507 tagged_above=-999 required=5
	tests=[AWL=0.092, 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 MnDIakqt9H+V for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 11:21:16 -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 D1BEC3A67F1
	for <behave@ietf.org>; Thu, 16 Oct 2008 11:21:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,425,1220227200"; d="scan'208";a="92027145"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 16 Oct 2008 18:22: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 m9GIMEwL014034; 
	Thu, 16 Oct 2008 11:22:14 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9GIMETr024547;
	Thu, 16 Oct 2008 18:22:14 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, 16 Oct 2008 11:22:13 -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); 
	Thu, 16 Oct 2008 11:22:13 -0700
From: Fred Baker <fred@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <48F76EFC.9000703@ericsson.com>
References: <48F76EFC.9000703@ericsson.com>
Message-Id: <F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 11:22:12 -0700
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Oct 2008 18:22:13.0453 (UTC)
	FILETIME=[1C7497D0:01C92FBC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2272; t=1224181334;
	x=1225045334; 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[Fwd=3A=20[BEHAVE]=20
	Proposal=20for=20new=20BEHAVE=20charter] |Sender:=20;
	bh=z5150L7JXovHCekdk1qN+vXsiSdMHwwBNCKcytUmGE8=;
	b=qUMhlfbd9lEBoZfLS+B9FNACJaZMzY3d2c3DipWaLdDrLCn2ff7NBGRW8n
	hBIBreIXeYAMswJW2LF6E5DvoTUVUdKhw/bMmRhUOSB0mxsPgaE54BCHaL1d
	g5oKG+GylY;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [Fwd: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Oct 16, 2008, at 9:42 AM, Magnus Westerlund wrote:

> The attached message was just sent to BEHAVE. Please send any comments
> to BEHAVE.

Andrew Yourtchenko forwarded the proposed behave charter to me; why I  
didn't get the attachment is not clear - it was clearly in the email  
he received, but there was no such attachment in the one I received.  
Mumble.

I have a point I would like to question.


The concept of "my domain" is something that came up in the interim  
meeting, concocted more or less at the last minute by Mark Townsley. I  
don't think it is very clearly explained in the proposed charter, and  
the applicability is also a concern. Which makes "and anything else is  
out of scope" a real problem.

In an IPv4/IPv6 translator, we have a succession of cases that we need  
to deal with as we proceed through the adoption curve. Work in the  
past decade has presumed islands of IPv6 in a world of IPv4, which is  
in part why the interdomain routing issues of a magic prefix such as  
proposed in section 2.1 of RFC 2765 were not seriously considered. At  
a different point in the adoption curve, we will be dealing with  
islands of IPv4 in an IPv6 world, and today some networks are dealing  
with gateways between what is essentially the public IPv4 network and  
the public IPv6 network. Since the beginning of August, we (Cisco)  
have had four public networks whose names you would recognize tell us  
that this is exactly the worldview they need. Hence, any intimation  
that we are dealing with a private domain ("my" domain) and a public  
domain are seriously dated - they reflect RFC 1918 but not technology  
coexistence and eventual transition.

Hence, what I would strongly suggest is that the concept in the  
charter be simply translation between an IPv4 network and an IPv6  
network, without any superimposition of a model of which is dominant  
and which is otherwise. I would further suggest that the model  
explicitly support both islands of either (which will have to be  
identified - the addresses of the right translator for *this* address  
and *that* address may be different, regardless of address type) and a  
global model.

I also think this has far too many words.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 12:12:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 40D293A6ADF;
	Thu, 16 Oct 2008 12:12:32 -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 5C19D3A6917
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 12:12:31 -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 L31zCvTUf87v for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 12:12:30 -0700 (PDT)
Received: from epost.nunatak.no (epost.nunatak.no [193.200.93.202])
	by core3.amsl.com (Postfix) with ESMTP id 2AD6A3A6ADF
	for <behave@ietf.org>; Thu, 16 Oct 2008 12:12:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by epost.nunatak.no (Postfix) with ESMTP id A1ECB121C9AF;
	Thu, 16 Oct 2008 21:13:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at 
Received: from epost.nunatak.no ([127.0.0.1])
	by localhost (epost.nunatak.no [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EHvMdSqgKSpo; Thu, 16 Oct 2008 21:13:29 +0200 (CEST)
Received: from [192.168.0.189] (cm-84.215.116.30.getinternet.no
	[84.215.116.30])
	by epost.nunatak.no (Postfix) with ESMTP id 2DA16121C99B;
	Thu, 16 Oct 2008 21:13:29 +0200 (CEST)
Message-ID: <48F79258.8000702@medianetworkservices.com>
Date: Thu, 16 Oct 2008 21:13:28 +0200
From: Richard Aas <richard@medianetworkservices.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>	<48F74C52.4030203@cisco.com>
	<48F76DA2.4020406@acm.org>
	<9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
In-Reply-To: <9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
Cc: BEHAVE WG <behave@ietf.org>, matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Philip Matthews wrote:
> 
> On Thu, 16-Oct-08, at 12:36 , Marc Petit-Huguenin wrote:
> 
>> Jonathan Rosenberg wrote:
>>> So I just got off the phone with Philip, we were talking about this, and
>>> here is an interesting idea.
>>>
>>> As Philip points out, the CreatePermission is required if you want the
>>> far end to be able to send you a response to a message delivered via a
>>> Send indication. So, regardless of the question about whether you can do
>>> a Send prior to CreatePermission, there *will* need to be a
>>> CreatePermission for each unique IP address you want to send to, even if
>>> there will be just a single packet and response from that IP address.
>>>
>>> The concern raised by Matthew applies to ICE as well; that for cases
>>> where there are a lot of candidates, you'll end up sending a
>>> connectivity check and a CreatePermission, thus increasing the number of
>>> packets sent for connectivity checks.
>>>
>>> The solution we came up with for this is very simple. We allow
>>> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes, which
>>> opens permissions to many IP addresses with one transaction. In the case
>>> of ICE, after the O/A exchange is done, each agent knows the full set of
>>> IP addresses it might eventually do a check to. Thus, it would do a
>>> single CreatePermission to all of them, and then proceed with the checks
>>> using Send indications. Once ICE completes, if a TURN candidate is
>>> selected, the client would do a CHannelBind for high volume
>>> transcations. With this solution, the CreatePermission mechanism imposes
>>> only a single packet overhead, independent of the number of candidates.
>>> It can be paralellized with the connectivity checks themselves, and thus
>>> has no impact on the latency of ICE.
>>>
>>> This would work well in conjunction with the proposal that you cannot do
>>> a Send to a destination without previously doing a CreatePermission.
>>>
>>> What do folks think of this solution?
>>
>> I am OK with this, but I am not sure that having multiple
>> XOR-PEER-ADDRESS attributes would work, because of this sentence in
>> rfc3489bis:
>>
>> "Any attribute type MAY appear more than once in a STUN message.
>> Unless specified otherwise, the order of appearance is significant:
>> only the first occurance needs to be processed by a receiver, and any
>> duplicates MAY be ignored by a receiver."
>>
>> I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
>> XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating the
>> family, port and address field for each address.
> 
> Well, our idea was to take advantage of the "Unless specified otherwise 
> ..." clause and specify that, for the XOR-PEER-ADDRESS attribute in the 
> CreatePermission request, multiple occurrences _are_ significant. 
> [Option 1]
> 
> However, there are two other options:
> 2) Allow the XOR-PEER-ADDRESS attribute to contain multiple addresses 
> for CreatePermission, but not for Send indication, Data indication, or 
> ChannelBind, OR
> 3) Define a new attribute XOR-PEER-ADDRESSES, which is used only in 
> CreatePermission, that allows multiple addresses. The existing 
> XOR-PEER-ADDRESS would be used in Send indication, Data indication, and 
> ChannelBind.
> 
> My personal preference is for 1. However, if implementors say "My stack 
> won't allow option 1, because it assumes that only the first occurrence 
> of an attribute is significant", then we could do option 3 instead.

I vote for option 1. From an implementors perspective, this option is
best aligned with encoding/decoding of existing address/port type of
attributes and thus easier to implement. Additionally I don't buy the
rfc3489bis violation argument as long as we have an "Unless specified
otherwise..." clause.

	Richard

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


From behave-bounces@ietf.org  Thu Oct 16 13:10:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA5293A6852;
	Thu, 16 Oct 2008 13:10:30 -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 A05713A6852
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 13:10: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=[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 yDl0mwN9GBYR for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 13:10:28 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2])
	by core3.amsl.com (Postfix) with ESMTP id 32F013A6452
	for <behave@ietf.org>; Thu, 16 Oct 2008 13:10:28 -0700 (PDT)
Received: by jazz.viagenie.ca (Postfix, from userid 8)
	id 6440229E1530; Thu, 16 Oct 2008 16:11:30 -0400 (EDT)
Received: from ringo.viagenie.ca (ringo.viagenie.ca [IPv6:2620:0:230:c000::67])
	by jazz.viagenie.ca (Postfix) with ESMTP id 5A5F629E1433;
	Thu, 16 Oct 2008 16:11:30 -0400 (EDT)
Message-ID: <48F79FF2.5030700@viagenie.ca>
Date: Thu, 16 Oct 2008 16:11:30 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Thunderbird 2.0.0.16 (X11/20080723)
MIME-Version: 1.0
To: Richard Aas <richard@medianetworkservices.com>
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>	<48F74C52.4030203@cisco.com>	<48F76DA2.4020406@acm.org>	<9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
	<48F79258.8000702@medianetworkservices.com>
In-Reply-To: <48F79258.8000702@medianetworkservices.com>
X-Enigmail-Version: 0.95.6
Cc: BEHAVE WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>,
	matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Richard Aas wrote:
> I vote for option 1. From an implementors perspective, this option is
> best aligned with encoding/decoding of existing address/port type of
> attributes and thus easier to implement.

Also from an implementor's perspective, I vote for option 1.

-- 
Please try Numb, a STUN/TURN server implementation.
Free access at http://numb.viagenie.ca/.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 14:06:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF96A3A68BE;
	Thu, 16 Oct 2008 14:06:32 -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 0D8233A68F0
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 14:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	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 2zLHg5lKYb79 for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 14:06:30 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224])
	by core3.amsl.com (Postfix) with ESMTP id 1DA873A685C
	for <behave@ietf.org>; Thu, 16 Oct 2008 14:06:30 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so154777rvf.49
	for <behave@ietf.org>; Thu, 16 Oct 2008 14:07:30 -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=CEfhL6oSjPbQKvTNULOJnw0XJ9icWkDzA7fJoIP8L6g=;
	b=blsBV5nhWSCrmVvjwo5QCf9TxDRcYVVF0qoXWwFfN9FspDnlZ8t2MD/maCvAT07Wml
	vKWkKAHx3Fc3SN4UiA39Z/3CvqLXW4jVCzaA3GTTfNNOxVmdGmHigxxkuziInr2hvYr2
	viv0+T1B0+Hxi/iBIzJc9hXlYSz5HwQNjJ9SU=
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=pZJ63q4NZKHW/xPTRBLq5RpKeIg/TeTL1PeARfaliQnK5mZx/llZ/x1M6XMEs5kTjB
	buVNf9f7hWAD6/S6FavlaH+OmhL+QdTybd+I4ksGTJ6ellk2qy3/YLHRxEuvEuTpgZSq
	Tnft0/1ov+hMEqQ0h+vPasA/cu5+UN7p/IRHU=
Received: by 10.141.79.12 with SMTP id g12mr1979556rvl.182.1224191250735;
	Thu, 16 Oct 2008 14:07:30 -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 g31sm5001728rvb.7.2008.10.16.14.07.28
	(version=SSLv3 cipher=RC4-MD5); Thu, 16 Oct 2008 14:07:29 -0700 (PDT)
Message-ID: <48F7AD0E.7000501@gmail.com>
Date: Fri, 17 Oct 2008 10:07:26 +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: <48F76EFC.9000703@ericsson.com>
	<F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>
In-Reply-To: <F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [Fwd: 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I agree with Fred's comments. As in my response to Fred
a few minutes ago, the "private" side of a translator, which
I guess is the "MY" side, could be a very large network
in itself. It might be reasonable to replace "MY" by
"Administratively delimited" since it does seem that these
translators would need to be in front of a delimited domain
of some kind.

   Brian

On 2008-10-17 07:22, Fred Baker wrote:
> 
> On Oct 16, 2008, at 9:42 AM, Magnus Westerlund wrote:
> 
>> The attached message was just sent to BEHAVE. Please send any comments
>> to BEHAVE.
> 
> Andrew Yourtchenko forwarded the proposed behave charter to me; why I
> didn't get the attachment is not clear - it was clearly in the email he
> received, but there was no such attachment in the one I received. Mumble.
> 
> I have a point I would like to question.
> 
> 
> The concept of "my domain" is something that came up in the interim
> meeting, concocted more or less at the last minute by Mark Townsley. I
> don't think it is very clearly explained in the proposed charter, and
> the applicability is also a concern. Which makes "and anything else is
> out of scope" a real problem.
> 
> In an IPv4/IPv6 translator, we have a succession of cases that we need
> to deal with as we proceed through the adoption curve. Work in the past
> decade has presumed islands of IPv6 in a world of IPv4, which is in part
> why the interdomain routing issues of a magic prefix such as proposed in
> section 2.1 of RFC 2765 were not seriously considered. At a different
> point in the adoption curve, we will be dealing with islands of IPv4 in
> an IPv6 world, and today some networks are dealing with gateways between
> what is essentially the public IPv4 network and the public IPv6 network.
> Since the beginning of August, we (Cisco) have had four public networks
> whose names you would recognize tell us that this is exactly the
> worldview they need. Hence, any intimation that we are dealing with a
> private domain ("my" domain) and a public domain are seriously dated -
> they reflect RFC 1918 but not technology coexistence and eventual
> transition.
> 
> Hence, what I would strongly suggest is that the concept in the charter
> be simply translation between an IPv4 network and an IPv6 network,
> without any superimposition of a model of which is dominant and which is
> otherwise. I would further suggest that the model explicitly support
> both islands of either (which will have to be identified - the addresses
> of the right translator for *this* address and *that* address may be
> different, regardless of address type) and a global model.
> 
> I also think this has far too many words.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> 
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 14:28:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7C363A684F;
	Thu, 16 Oct 2008 14:28:25 -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 54A183A684F
	for <behave@core3.amsl.com>; Thu, 16 Oct 2008 14:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.51
X-Spam-Level: 
X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5
	tests=[AWL=0.089, 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 iqHJO6atu7YR for <behave@core3.amsl.com>;
	Thu, 16 Oct 2008 14:28:24 -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 9FC343A67FB
	for <behave@ietf.org>; Thu, 16 Oct 2008 14:28:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,426,1220227200"; d="scan'208";a="176789746"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 16 Oct 2008 21:29:27 +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 m9GLTRDq008640; 
	Thu, 16 Oct 2008 14:29:27 -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 m9GLTRq1028898;
	Thu, 16 Oct 2008 21:29:27 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, 16 Oct 2008 14:29:26 -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); 
	Thu, 16 Oct 2008 14:29:26 -0700
Message-Id: <8BA447AF-2B80-4776-8F17-8872D885E580@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <48F7AD0E.7000501@gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 14:29:26 -0700
References: <48F76EFC.9000703@ericsson.com>
	<F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>
	<48F7AD0E.7000501@gmail.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Oct 2008 21:29:26.0801 (UTC)
	FILETIME=[440D7810:01C92FD6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=322; t=1224192567; x=1225056567;
	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[BEHAVE]=20[46translation]=20[Fwd=3A=20
	Proposal=20for=20new=20BEHAVE=20charter] |Sender:=20;
	bh=s4ICdkuFs8XffTGS8Shw8bOOattQhc+rxB6VLSIBk6c=;
	b=jBGDB9ZWQLZAutfuebRL/dBWxwFQg3VxJ4KnxBXH6v4p+s1BjnjUYNRCbf
	qBV9dTzBzWsdcV9hGVGfAPDUUcMS/pvnL98efrlvuWIRP+w7OPLT8xZV/NWq
	rnnXaaA/y9;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [Fwd: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Oct 16, 2008, at 2:07 PM, Brian E Carpenter wrote:

> It might be reasonable to replace "MY" by
> "Administratively delimited" since it does seem that these
> translators would need to be in front of a delimited domain
> of some kind.

modify that to "could be administratively delimited" and I'm OK with it.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 16 15:07:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 357603A6973;
	Thu, 16 Oct 2008 15:07:19 -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 8D0E93A68BE;
	Thu, 16 Oct 2008 15:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.4
X-Spam-Level: 
X-Spam-Status: No, score=-17.4 tagged_above=-999 required=5 tests=[AWL=0.199, 
	BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 gT3gAhl6TZPZ; Thu, 16 Oct 2008 15:07:15 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id A79093A68AA;
	Thu, 16 Oct 2008 15:07:15 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 177D3168619; Thu, 16 Oct 2008 15:08:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081016220817.177D3168619@bosco.isi.edu>
Date: Thu, 16 Oct 2008 15:08:17 -0700 (PDT)
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] BCP 142, RFC 5382 on NAT Behavioral Requirements for TCP
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


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

        BCP 142        
        RFC 5382

        Title:      NAT Behavioral Requirements for TCP 
        Author:     S. Guha, Ed.,
                    K. Biswas, B. Ford,
                    S. Sivakumar, P. Srisuresh
        Status:     Best Current Practice
        Date:       October 2008
        Mailbox:    saikat@cs.cornell.edu, 
                    kbiswas@cisco.com, 
                    baford@mpi-sws.org,
                    ssenthil@cisco.com, 
                    srisuresh@yahoo.com
        Pages:      31
        Characters: 50306
        See Also:   BCP0142

        I-D Tag:    draft-ietf-behave-tcp-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5382.txt

This document defines a set of requirements for NATs that handle TCP
that would allow many applications, such as peer-to-peer applications
and online games to work consistently.  Developing NATs that meet
this set of requirements will greatly increase the likelihood that
these applications will function properly.  This document specifies 
an Internet Best Current Practices for the Internet Community, 
and requests discussion and suggestions for improvements.

This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


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


From behave-bounces@ietf.org  Fri Oct 17 00:22:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F32B73A6985;
	Fri, 17 Oct 2008 00:22:47 -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 7C22D3A6985
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 00:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[AWL=0.211, 
	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 WaR5zawuWuH0 for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 00:22:46 -0700 (PDT)
Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65])
	by core3.amsl.com (Postfix) with ESMTP id 99E3A3A6965
	for <behave@ietf.org>; Fri, 17 Oct 2008 00:22:46 -0700 (PDT)
Received: from smtp8-g19.free.fr (localhost [127.0.0.1])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 7F97432A829;
	Fri, 17 Oct 2008 09:23:49 +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 54C7532A7C5;
	Fri, 17 Oct 2008 09:23:47 +0200 (CEST)
Message-ID: <48F83D2F.8040902@free.fr>
Date: Fri, 17 Oct 2008 09:22: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: <48F76EFC.9000703@ericsson.com>	<F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>	<48F7AD0E.7000501@gmail.com>
	<8BA447AF-2B80-4776-8F17-8872D885E580@cisco.com>
In-Reply-To: <8BA447AF-2B80-4776-8F17-8872D885E580@cisco.com>
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [Fwd: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I do share the view that MY would be unclear to those who didn't attend 
the interim meeting.

To avoid the ambiguity of "MY", and also some verbosity of "(possibly)
administratively delimited", wouldn't there be a solution by just
deleting MY from scenario titles, and by adding in the text "on the IPv4 
(or IPv6) Internet" where it applies?

The text would become:

1. 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 on the IPv4
Internet. The translator function is intended to service a specific
IPv6 network of arbitrary size. Port translation is necessary on
the IPv4 side for efficient IPv4 address usage.

2. IPv4 from IPv6 Internet, i.e. perform translation between IPv4 and
IPv6 for packets in uni- or bi-directional flows that are
initiated from an IPv6 host on the IPv6 Internet 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. 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 on the IPv6 Internet. The 
translator function is intended to service a specific IPv4 network using 
either public or private IPv4 address space.

4. IPv6 from IPv4 Internet, i.e. perform translation between IPv4 and
IPv6 for packets in uni- or bi-directional flows that are initiated
from an IPv4 host on the IPv4 Internet 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.

RD


Fred Baker   (m/j/a) 10/16/08 11:29 PM:
> 
> On Oct 16, 2008, at 2:07 PM, Brian E Carpenter wrote:
> 
>> It might be reasonable to replace "MY" by "Administratively
>> delimited" since it does seem that these translators would need to
>> be in front of a delimited domain of some kind.
> 
> modify that to "could be administratively delimited" and I'm OK with
> it. _______________________________________________ Behave mailing
> list Behave@ietf.org https://www.ietf.org/mailman/listinfo/behave
> 
> 

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


From behave-bounces@ietf.org  Fri Oct 17 01:55:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8B333A67D0;
	Fri, 17 Oct 2008 01:55:29 -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 824B13A680B
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 01:55:28 -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.076, 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 Pa1bIWlAepys for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 01:55:27 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 40AF53A63D2
	for <behave@ietf.org>; Fri, 17 Oct 2008 01:55:27 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7A99D209D7; Fri, 17 Oct 2008 10:56:29 +0200 (CEST)
X-AuditID: c1b4fb3c-af0d0bb0000015b5-b1-48f8533da3cd
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	567F02052C; Fri, 17 Oct 2008 10:56:29 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 10:56:29 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 10:56:28 +0200
Message-ID: <48F8533D.9060507@ericsson.com>
Date: Fri, 17 Oct 2008 10:56:29 +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_Despr=E9s?= <remi.despres@free.fr>
References: <48F76EFC.9000703@ericsson.com>	<F9E018C1-2A50-460E-84EF-8E8BEB16BD67@cisco.com>	<48F7AD0E.7000501@gmail.com>	<8BA447AF-2B80-4776-8F17-8872D885E580@cisco.com>
	<48F83D2F.8040902@free.fr>
In-Reply-To: <48F83D2F.8040902@free.fr>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 17 Oct 2008 08:56:28.0772 (UTC)
	FILETIME=[3E431240:01C93036]
X-Brightmail-Tracker: AAAAAA==
Cc: Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] [46translation] [Fwd: 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

I have received the comment before about this maybe being unclear from
Mark Townsley. He also suggested that we add something like this text to
explain MY:

"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 didn't include that previous because I and a few other thought it was
reasonably clear anyway. I fully agree that the MY network may not be
any simple network, but it is administered by someone that makes a
concuss decision to deploy translators. There is possible to have some
restrictions on the deployment, i.e. it is not IPv4 Internet to IPv6
Internet. Maybe the above paragraph is better clarification on what is
intended than R=E9mi's suggestion below.

In regards to it being wordy. Yes, it is and I don't see how one easily
can make it less so without removing information that I want to include.
Many IETF WG charters are so short and void of information that no
outsider who wasn't part of the chartering process can determine what it
really says. But, if someone has a bright idea how to accomplish that
please write up a proposal.

Cheers

Magnus

R=E9mi Despr=E9s skrev:
> I do share the view that MY would be unclear to those who didn't attend
> the interim meeting.
> =

> To avoid the ambiguity of "MY", and also some verbosity of "(possibly)
> administratively delimited", wouldn't there be a solution by just
> deleting MY from scenario titles, and by adding in the text "on the IPv4
> (or IPv6) Internet" where it applies?
> =

> The text would become:
> =

> 1. 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 on the IPv4
> Internet. The translator function is intended to service a specific
> IPv6 network of arbitrary size. Port translation is necessary on
> the IPv4 side for efficient IPv4 address usage.
> =

> 2. IPv4 from IPv6 Internet, i.e. perform translation between IPv4 and
> IPv6 for packets in uni- or bi-directional flows that are
> initiated from an IPv6 host on the IPv6 Internet 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. 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 on the IPv6 Internet. The
> translator function is intended to service a specific IPv4 network using
> either public or private IPv4 address space.
> =

> 4. IPv6 from IPv4 Internet, i.e. perform translation between IPv4 and
> IPv6 for packets in uni- or bi-directional flows that are initiated
> from an IPv4 host on the IPv4 Internet 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.
> =

> RD
> =

> =

> Fred Baker   (m/j/a) 10/16/08 11:29 PM:
>>
>> On Oct 16, 2008, at 2:07 PM, Brian E Carpenter wrote:
>>
>>> It might be reasonable to replace "MY" by "Administratively
>>> delimited" since it does seem that these translators would need to
>>> be in front of a delimited domain of some kind.
>>
>> modify that to "could be administratively delimited" and I'm OK with
>> it. _______________________________________________ Behave mailing
>> list Behave@ietf.org https://www.ietf.org/mailman/listinfo/behave
>>
>>
> =

> _______________________________________________
> 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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 17 02:50:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B8A03A68DC;
	Fri, 17 Oct 2008 02:50:37 -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 A07063A697F
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 02:50: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 3G9DcHIqd4kP for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 02:50:31 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2])
	by core3.amsl.com (Postfix) with ESMTP id 8EC773A6924
	for <behave@ietf.org>; Fri, 17 Oct 2008 02:50:31 -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 m9H9pA7c030884
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Oct 2008 11:51:11 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Message-Id: <E03C9DF8-9225-45AF-BCCD-FCFCB06CB412@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Behave WG <behave@ietf.org>
In-Reply-To: <48F76EFC.9000703@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 11:51:24 +0200
References: <48F76EFC.9000703@ericsson.com>
X-Mailer: Apple Mail (2.929.2)
Cc: 46Translation <46translation@employees.org>
Subject: Re: [BEHAVE] [v4v6interim] [Fwd:  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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

On 16 okt 2008, at 18:42, Magnus Westerlund wrote:

> 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.

Isn't this trivial: just add "fake" AAAA records manually and do SIIT  
(1-to-1)? (Same thing for 4.)

> 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.

Will this be a separate solution or integrated with v6-to-v4?

> All translation solutions shall be capable of handling flows using  
> TCP,
> UDP, DCCP, and SCTP.

I disagree. This is a quick fix effort. DCCP and SCTP have essentially  
zero deployment, making these "MUST" will slow down the work without a  
real world benefit. Same thing for multicast. There is no end-to-end  
multicast on the internet today, so there is no vicious deployment  
cycle to break with translation.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 17 06:42:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D1EB63A69E3;
	Fri, 17 Oct 2008 06:42:24 -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 C218C3A69E3
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 06:42:23 -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 2P5Z3ehgHjRN for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 06:42:23 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id BF7C83A696A
	for <behave@ietf.org>; Fri, 17 Oct 2008 06:42:22 -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
	m9HDgvbN027520; Fri, 17 Oct 2008 16:43:23 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 17 Oct 2008 16:43:13 +0300
Received: from esdhcp04064.research.nokia.com ([172.21.40.64]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 17 Oct 2008 16:43:01 +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, behave-chairs@tools.ietf.org
Date: Fri, 17 Oct 2008 16:43:04 +0300
User-Agent: KMail/1.9.10
References: <018501c92d7f$f36e7a10$c2f0200a@cisco.com>
In-Reply-To: <018501c92d7f$f36e7a10$c2f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810171643.04438.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 17 Oct 2008 13:43:01.0469 (UTC)
	FILETIME=[45E870D0:01C9305E]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] agenda time
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

On Tuesday 14 October 2008 01:06:32 ext Dan Wing, you wrote:
> If you want agenda time at the upcoming BEHAVE meeting, please let us know
> the topic, Internet Draft name, speaker, and requested duration.

I missed the agenda deadline last time. I would like to discuss transport =

encapsulation over UDP as in: =

http://www.ietf.org/internet-drafts/draft-denis-udp-transport-00.txt

This is more intricate than ICE-TCP, but at least, it provides reasonable =

NAT-to-NAT traversal success rate - essentially the same as UDP.

Or perhaps, this should go to TSVAREA instead? (cc'ing our AD's in case)

Regards,

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 17 07:33:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 09A083A6A4C;
	Fri, 17 Oct 2008 07:33:14 -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 AA27C3A6A4C
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 07:33:12 -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 9SHxZq0A8CLj for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 07:33:11 -0700 (PDT)
Received: from QMTA03.westchester.pa.mail.comcast.net
	(qmta03.westchester.pa.mail.comcast.net [76.96.62.32])
	by core3.amsl.com (Postfix) with ESMTP id 2CF023A6826
	for <behave@ietf.org>; Fri, 17 Oct 2008 07:33:11 -0700 (PDT)
Received: from OMTA12.westchester.pa.mail.comcast.net ([76.96.62.44])
	by QMTA03.westchester.pa.mail.comcast.net with comcast
	id TouP1a01w0xGWP853qaFTp; Fri, 17 Oct 2008 14:34:15 +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: [BEHAVE] [v4v6interim] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Fri Oct 17 10:57:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CFAC3A6A9E;
	Fri, 17 Oct 2008 10:57:53 -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 9D94F3A6A9E
	for <behave@core3.amsl.com>; Fri, 17 Oct 2008 10:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072, 
	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 2DncdEoeBLkk for <behave@core3.amsl.com>;
	Fri, 17 Oct 2008 10:57:51 -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 971423A6A72
	for <behave@ietf.org>; Fri, 17 Oct 2008 10:57:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,432,1220227200"; d="scan'208";a="92598737"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 17 Oct 2008 17:58:56 +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 m9HHwukG010530; 
	Fri, 17 Oct 2008 10:58:56 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9HHwtA1001008;
	Fri, 17 Oct 2008 17:58:55 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Saikat Guha'" <saikat@cs.cornell.edu>,
	"'Kaushik Biswas \(kbiswas\)'" <kbiswas@cisco.com>,
	"'Bryan Ford'" <baford@mit.edu>,
	"'Senthil Sivakumar \(ssenthil\)'" <ssenthil@cisco.com>,
	<srisuresh@yahoo.com>
References: <20081016220817.177D3168619@bosco.isi.edu>
Date: Fri, 17 Oct 2008 10:58:54 -0700
Message-ID: <004101c93082$056581f0$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: Ackv28/0h/HmtylbQgCVi9kWBsQthgApf0Cg
In-Reply-To: <20081016220817.177D3168619@bosco.isi.edu>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2990; t=1224266336;
	x=1225130336; 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=20BCP=20142,=20RFC=205382=20on=20NAT=20Be
	havioral=20Requirements=20for=20TCP |Sender:=20;
	bh=hoZYlNelZi6q4sHAqYDacNU9gNiHxmQ5U+cQh7zyHio=;
	b=MKOV0mpAqYaiMXptksU7s9pxs4Sg5mrkNSoNCDYJRvC+vjitzlXLMSV5QB
	BsB/TZbv+ZRfjtE5KDnH2RR4WW90aS9nS+7XvMeTWG29PxNzovN9EBYU7R6I
	PDm0uOaKg9;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] BCP 142,
	RFC 5382 on NAT Behavioral Requirements for TCP
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Congratulations to the authors and the working group for getting this
published!

-d
 

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org 
> [mailto:ietf-announce-bounces@ietf.org] On Behalf Of 
> rfc-editor@rfc-editor.org
> Sent: Thursday, October 16, 2008 3:08 PM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: behave@ietf.org; rfc-editor@rfc-editor.org
> Subject: BCP 142, RFC 5382 on NAT Behavioral Requirements for TCP
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
>         BCP 142        
>         RFC 5382
> 
>         Title:      NAT Behavioral Requirements for TCP 
>         Author:     S. Guha, Ed.,
>                     K. Biswas, B. Ford,
>                     S. Sivakumar, P. Srisuresh
>         Status:     Best Current Practice
>         Date:       October 2008
>         Mailbox:    saikat@cs.cornell.edu, 
>                     kbiswas@cisco.com, 
>                     baford@mpi-sws.org,
>                     ssenthil@cisco.com, 
>                     srisuresh@yahoo.com
>         Pages:      31
>         Characters: 50306
>         See Also:   BCP0142
> 
>         I-D Tag:    draft-ietf-behave-tcp-08.txt
> 
>         URL:        http://www.rfc-editor.org/rfc/rfc5382.txt
> 
> This document defines a set of requirements for NATs that handle TCP
> that would allow many applications, such as peer-to-peer applications
> and online games to work consistently.  Developing NATs that meet
> this set of requirements will greatly increase the likelihood that
> these applications will function properly.  This document specifies 
> an Internet Best Current Practices for the Internet Community, 
> and requests discussion and suggestions for improvements.
> 
> This document is a product of the Behavior Engineering for 
> Hindrance Avoidance Working Group of the IETF.
> 
> 
> BCP: This document specifies an Internet Best Current 
> Practices for the
> Internet Community, and requests discussion and suggestions for 
> improvements. Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see 
> http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to 
> rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> USC/Information Sciences Institute
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

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


From behave-bounces@ietf.org  Fri Oct 17 15:41:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D17783A6874;
	Fri, 17 Oct 2008 15:41:30 -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 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: [BEHAVE] [v4v6interim] 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Sat Oct 18 07:04:15 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2961D28C100;
	Sat, 18 Oct 2008 07:04:15 -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 94C2028C0F7
	for <behave@core3.amsl.com>; Sat, 18 Oct 2008 07:04:13 -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 IY7w5GT1-I54 for <behave@core3.amsl.com>;
	Sat, 18 Oct 2008 07:04:12 -0700 (PDT)
Received: from mail-07.primus.ca (mail6.primus.ca [216.254.141.173])
	by core3.amsl.com (Postfix) with ESMTP id 8F12228C0FD
	for <behave@ietf.org>; Sat, 18 Oct 2008 07:04:12 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KrCQV-0006Vz-0l; Sat, 18 Oct 2008 10:05:07 -0400
Message-Id: <099EC4CA-7EA1-431B-A673-8EBACC12CE11@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Marc Petit-Huguenin <petithug@acm.org>
In-Reply-To: <48EE50C0.4000803@acm.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 18 Oct 2008 10:05:11 -0400
References: <20080929171502.0885D3A6B0F@core3.amsl.com>
	<48EE50C0.4000803@acm.org>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] I-D Action:draft-ietf-behave-turn-10.txt
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Responding to your remaining points.

On Thu, 9-Oct-08, at 14:43 , Marc Petit-Huguenin wrote:

[Snip]

>
> NITS
> ----
>
> - Section 2, paragraph 2:  "On the public Internet..."
>
> Pleonasm.

I suppose that it true. But it is in contrast to the phrase "private  
network" in the previous sentence, and I personally feel it re- 
enforces the difference. I have left the text as is.
>
>
> - Section 3, definition of 5-tuple: "...used to communicate between  
> the
> client and the server ."
>
> Remove the space before the stop.
Fixed.

>
>
> - Section 6.2, bullet #3:  "...contain a REQUESTED-TRANPORT..."
>
> REQUESTED-TRANSPORT

Fixed.

>
>
> - Section 6.2, bullet #8:  "...as in authenticated error responses.."
>
> Remove redundant stop.

Fixed.

>
>
> - Section 8, paragraph 7: "...at a different point in time, or vica- 
> versa."
>
> ...vice versa.

Fixed.

>
>
> - Section 9, second paragraph: "...with either the Send  
> mechanismSection
> 10 or the Channel mechanismSection 11."
>
> ...mechanism in Section...

Fixed.

>
>
> - Section 14:  "0x001a: DONT-FRAGMENT"
>
> 0x001A

Fixed.

>
>
> - Section 14.6:
>
> The unused bits in the ASCII art should be marked RFFU.

Fixed.


>
>
> - Section 14.6: "...to reserve the next highest port..."
>
> ...to reserve the next port...

I changed "highest" to "higher".

>
>
> - Section 16.1.3: "...by sending it a Refresh with an..."
>
> ...by sending it a Refresh request with an...

Fixed.

>
>
> -- 
> Marc Petit-Huguenin           [                                 ]
> Home: marc@petit-huguenin.org [RFC1855-compliant space for rent ]
> Work: marc@8x8.com            [                                 ]
> [                                                               ]
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Sun Oct 19 09:21:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35D4E3A6A86;
	Sun, 19 Oct 2008 09:21:41 -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 3B6273A682E
	for <behave@core3.amsl.com>; Sun, 19 Oct 2008 09:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072, 
	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 haOP+5Ftuu0r for <behave@core3.amsl.com>;
	Sun, 19 Oct 2008 09:21:39 -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 59B9F3A6A07
	for <behave@ietf.org>; Sun, 19 Oct 2008 09:21:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,446,1220227200"; d="scan'208";a="93015510"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 19 Oct 2008 16:22:39 +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 m9JGMdRW030453; 
	Sun, 19 Oct 2008 09:22:39 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9JGMdaS014275;
	Sun, 19 Oct 2008 16:22:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
References: <004001c928bb$49d12b10$35666b80@cisco.com>
Date: Sun, 19 Oct 2008 09:22:39 -0700
Message-ID: <009301c93206$e7dea310$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ackou0m7T1l7JY9qTqOZY5GsZkwWpAJSwYTQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <004001c928bb$49d12b10$35666b80@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1540; t=1224433359;
	x=1225297359; 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]=20WGLC=3A=20draft-ietf-behave-
	nat-icmp-09 |Sender:=20;
	bh=QY6G8Nf3egtyKMKwXNq6sDQrtZP+Hoo+mGVE1hfR+W0=;
	b=dseES7rk1xVCqx7BOxmbHt/6mE9NwoC03BBx0EtqptHNJvmOX+mzFnOrlW
	fTW35ozjr/Sn9t1HjHw0hiezPuxw/WDF8Bxa9h9qr3xxwmnXMiXJsqCNxmBg
	/nA3L0rDi/rw4k7dblpkwUEx87jyAS0qMvC2zkYVoXHEJ8pGO3ca0=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave-chairs@tools.ietf.org, draft-ietf-behave-nat-icmp@tools.ietf.org
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-nat-icmp-09
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks to Fernando and Julien Laganier for their comments during the WGLC of
the changes to -behave-nat-icmp-09.

Here is my summary of the discussion and the changes that should be reflected
in the next version of the document:


The following are currently MUST in icmp-09, and should be moved to the MAY
section and should cite new text in the -behave-nat-icmp document as
justification (rather than citing RFC1812 as justification):

  - Parameter Problem Message, as described in Section 
    4.3.3.5 of [RFC1812]
  - Router Advertisement and Solicitations, as described 
    in Section 4.3.3.10 of [RFC1812].

And also incorporate the edits suggested by Fernando Gont:

1.

"If a NAT device does not support forwarding packets with
    the source route option, the NAT device SHOULD NOT forward
    outbound ICMP messages that contain source route option in the
    outer or inner ICMP header."

s/ICMP header/IP header/

2.

In Section 7.1.2, the draft says:
"   When NAT device is the recipient of "Packet Too Big" ICMP message
    from the network, the NAT device MUST forward the ICMP message back
    to the intended recipient, pursuant to the previously stated
    requirements REQ-3, REQ-4, REQ-5 and REQ-6."

Does REQ-6 really apply here? (ICMP PTBs are not query/response messages)

[resolution was that REQ-6 doesn't apply]

3.

Include SHOULD in the exception text,

"Implementation of such a policy control overrides the 
MUSTs and SHOULDs in REQ-10."
      ^^^^^^^^^^^

-d

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


From behave-bounces@ietf.org  Sun Oct 19 13:44:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A6AB28C0F4;
	Sun, 19 Oct 2008 13:44:14 -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 A70FE3A6AB5
	for <behave@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.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 B3EBiW8Kp9ob for <behave@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.224])
	by core3.amsl.com (Postfix) with ESMTP id D62203A6AB4
	for <behave@ietf.org>; Sun, 19 Oct 2008 13:44:12 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1316100rvf.49
	for <behave@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: 'Margaret Wasserman' <mrw@lilacglade.org>, v4v6interim@ietf.org,
	'46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 03:36:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E861B3A69C6;
	Mon, 20 Oct 2008 03:36:09 -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 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: 'Margaret Wasserman' <mrw@lilacglade.org>, v4v6interim@ietf.org,
	'46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 03:58:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FBD83A696E;
	Mon, 20 Oct 2008 03:58:04 -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 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: [BEHAVE] [46translation] [v4v6interim] 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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 04:05:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18F123A69CA;
	Mon, 20 Oct 2008 04:05:35 -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 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: [BEHAVE] [46translation] [v4v6interim] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
>
>   =


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


From behave-bounces@ietf.org  Mon Oct 20 04:20:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BF1D3A68FF;
	Mon, 20 Oct 2008 04:20: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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 04:26:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E69853A68C3;
	Mon, 20 Oct 2008 04:26:08 -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 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: [BEHAVE] [46translation] [v4v6interim] Proposal for new
	BEHAVEcharter
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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 04:45:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73D133A698C;
	Mon, 20 Oct 2008 04:45:03 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id DB6E03A698C; Mon, 20 Oct 2008 04:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081020114501.DB6E03A698C@core3.amsl.com>
Date: Mon, 20 Oct 2008 04:45:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-nat-icmp-10.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : NAT Behavioral Requirements for ICMP protocol
	Author(s)       : P. Srisuresh, et al.
	Filename        : draft-ietf-behave-nat-icmp-10.txt
	Pages           : 28
	Date            : 2008-10-20

This document specifies the behavioral properties required of the 
Network Address Translator (NAT) devices in conjunction with the
Internet Control Message Protocol (ICMP). The objective of this
memo is to make NAT devices more predictable and compatible with
diverse application protocols that traverse the devices. Companion
documents provide behavioral recommendations specific to TCP, UDP
and other protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-nat-icmp-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-nat-icmp-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From behave-bounces@ietf.org  Mon Oct 20 04:46:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEA573A69CE;
	Mon, 20 Oct 2008 04:46:12 -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 7F3263A6919
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 04:46:11 -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 adNpx-LYhnW6 for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 04:46:10 -0700 (PDT)
Received: from web33306.mail.mud.yahoo.com (web33306.mail.mud.yahoo.com
	[68.142.206.121])
	by core3.amsl.com (Postfix) with SMTP id 7AA963A6915
	for <behave@ietf.org>; Mon, 20 Oct 2008 04:46:10 -0700 (PDT)
Received: (qmail 55023 invoked by uid 60001); 20 Oct 2008 11:47:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
	b=Nj6Z/kROP6B89Pcai0BfpJc/SP8ovq5mUzVR7hRTTLgnWSfoWI1pNPkQelqI6OY8oePP9y3fqsppycz9QtjtESEOWdvZUMnWO/WEiddb723lwXDg0wfcvyQ4Ey96LUs/W1vHrkJiUVnkfLDGAgGV69sSdcKMEViKti17wUMTyEM=;
X-YMail-OSG: dDGdKTQVM1luCPY1Y4OWzAtk6uvsA01yPJIf8vSExKaJQwCs7wCbogR.R9jyAG4Rs9N.j.XRUIX8IcYTzmT47G62t3Jf5skY3K.VGMOzzLyebmnUs4OQ.Un6Wuj3l11im.tIs1e4oAZyClc0wU0UG4MRaUiltnLFqCfUbLS0kNWP
Received: from [76.254.90.187] by web33306.mail.mud.yahoo.com via HTTP;
	Mon, 20 Oct 2008 04:47:21 PDT
X-Mailer: YahooMailWebService/0.7.247.3
Date: Mon, 20 Oct 2008 04:47:21 -0700 (PDT)
From: Pyda Srisuresh <srisuresh@yahoo.com>
To: 'Behave WG' <behave@ietf.org>, Dan Wing <dwing@cisco.com>
In-Reply-To: <009301c93206$e7dea310$c3f0200a@cisco.com>
MIME-Version: 1.0
Message-ID: <520857.55008.qm@web33306.mail.mud.yahoo.com>
Cc: behave-chairs@tools.ietf.org, draft-ietf-behave-nat-icmp@tools.ietf.org
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-nat-icmp-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: srisuresh@yahoo.com
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks to Fernando Gont and Julien Laganier for their comments and feedback. Thanks to Dan for summarizing the WGLC comments. Revised document (draft-ietf-behave-nat-icmp-10.txt) folding in the WG feedback is now posted. FYI.

regards,
suresh

--- On Sun, 10/19/08, Dan Wing <dwing@cisco.com> wrote:

> From: Dan Wing <dwing@cisco.com>
> Subject: RE: [BEHAVE] WGLC: draft-ietf-behave-nat-icmp-09
> To: "'Behave WG'" <behave@ietf.org>
> Cc: behave-chairs@tools.ietf.org, draft-ietf-behave-nat-icmp@tools.ietf.org, srisuresh@yahoo.com
> Date: Sunday, October 19, 2008, 9:22 AM
> Thanks to Fernando and Julien Laganier for their comments
> during the WGLC of
> the changes to -behave-nat-icmp-09.
> 
> Here is my summary of the discussion and the changes that
> should be reflected
> in the next version of the document:
> 
> 
> The following are currently MUST in icmp-09, and should be
> moved to the MAY
> section and should cite new text in the -behave-nat-icmp
> document as
> justification (rather than citing RFC1812 as
> justification):
> 
>   - Parameter Problem Message, as described in Section 
>     4.3.3.5 of [RFC1812]
>   - Router Advertisement and Solicitations, as described 
>     in Section 4.3.3.10 of [RFC1812].
> 
> And also incorporate the edits suggested by Fernando Gont:
> 
> 1.
> 
> "If a NAT device does not support forwarding packets
> with
>     the source route option, the NAT device SHOULD NOT
> forward
>     outbound ICMP messages that contain source route option
> in the
>     outer or inner ICMP header."
> 
> s/ICMP header/IP header/
> 
> 2.
> 
> In Section 7.1.2, the draft says:
> "   When NAT device is the recipient of "Packet
> Too Big" ICMP message
>     from the network, the NAT device MUST forward the ICMP
> message back
>     to the intended recipient, pursuant to the previously
> stated
>     requirements REQ-3, REQ-4, REQ-5 and REQ-6."
> 
> Does REQ-6 really apply here? (ICMP PTBs are not
> query/response messages)
> 
> [resolution was that REQ-6 doesn't apply]
> 
> 3.
> 
> Include SHOULD in the exception text,
> 
> "Implementation of such a policy control overrides the
> 
> MUSTs and SHOULDs in REQ-10."
>       ^^^^^^^^^^^
> 
> -d
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 06:56:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B88973A6A2F;
	Mon, 20 Oct 2008 06:56:32 -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 22E9E3A6A2F
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 06:56: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 q7O1flaaIgWU for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 06:56:31 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 0A52D3A67EE
	for <behave@ietf.org>; Mon, 20 Oct 2008 06:56:30 -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
	m9KDvSxL015912 for <behave@ietf.org>; Mon, 20 Oct 2008 16:57:40 +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 16:57:15 +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 16:57:12 +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 16:57:12 +0300
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Mon, 20 Oct 2008 16:57:11 +0300
User-Agent: KMail/1.9.10
References: <20081020133243.50D063A698B@core3.amsl.com>
In-Reply-To: <20081020133243.50D063A698B@core3.amsl.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810201657.11772.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 20 Oct 2008 13:57:12.0251 (UTC)
	FILETIME=[C040B8B0:01C932BB]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] New Version Notification for
	draft-denis-behave-v4v6exthdr-00
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

RllJIC0gY29tbWVudHMgbW9zdCB3ZWxjb21lOgpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0
LWRyYWZ0cy9kcmFmdC1kZW5pcy1iZWhhdmUtdjR2NmV4dGhkci0wMC50eHQKCk9uIE1vbmRheSAy
MCBPY3RvYmVyIDIwMDggMTY6MzI6NDMsIHlvdSB3cm90ZToKPiBBIG5ldyB2ZXJzaW9uIG9mIEkt
RCwgZHJhZnQtZGVuaXMtYmVoYXZlLXY0djZleHRoZHItMDAudHh0IGhhcyBiZWVuCj4gc3VjY2Vz
c2Z1bHkgc3VibWl0dGVkIGJ5IFJlbWkgRGVuaXMtQ291cm1vbnQgYW5kIHBvc3RlZCB0byB0aGUg
SUVURgo+IHJlcG9zaXRvcnkuCj4KPiBGaWxlbmFtZToJIGRyYWZ0LWRlbmlzLWJlaGF2ZS12NHY2
ZXh0aGRyCj4gUmV2aXNpb246CSAwMAo+IFRpdGxlOgkJIElQdjYgZGVzdGluYXRpb24gaGVhZGVy
IG9wdGlvbiBmb3IgSVB2NCB0cmFuc2xhdG9yIG1hcHBpbmcKPiBub3RpZmljYXRpb24gQ3JlYXRp
b25fZGF0ZToJIDIwMDgtMTAtMTcKPiBXRyBJRDoJCSBJbmRlcGVuZGVudCBTdWJtaXNzaW9uCj4g
TnVtYmVyX29mX3BhZ2VzOiAxMwo+Cj4gQWJzdHJhY3Q6Cj4gVGhpcyBtZW1vIGRlZmluZXMgYSBu
ZXcgSVB2NiBEZXN0aW5hdGlvbiBoZWFkZXIgb3B0aW9uIHRvIGNvbnZleSB0aGUKPiB0cmFuc3Bv
cnQgbWFwcGluZyBpbmZvcm1hdGlvbiBmcm9tIGFuIElQdjQtSVB2NCBwcm90b2NvbCB0cmFuc2xh
dG9yCj4gdG8gdGhlIElQdjYgZW5kIG9mIGEgcHJvdG9jb2wtdHJhbnNsYXRlZCBwYWNrZXQgZmxv
dy4KCi0tIApSw6ltaSBEZW5pcy1Db3VybW9udApNYWVtbyBTb2Z0d2FyZSwgTm9raWEgRGV2aWNl
cyBSJkQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQmVo
YXZlIG1haWxpbmcgbGlzdApCZWhhdmVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9iZWhhdmUK


From behave-bounces@ietf.org  Mon Oct 20 07:49:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F91D3A6A35;
	Mon, 20 Oct 2008 07:49:29 -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 A2E023A6A35
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 07:49:27 -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 bnK4rW6ectgM for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 07:49:26 -0700 (PDT)
Received: from QMTA06.emeryville.ca.mail.comcast.net
	(qmta06.emeryville.ca.mail.comcast.net [76.96.30.56])
	by core3.amsl.com (Postfix) with ESMTP id CC1293A69E2
	for <behave@ietf.org>; Mon, 20 Oct 2008 07:49:26 -0700 (PDT)
Received: from OMTA13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id V0M91a00417UAYkA62qegZ; 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Mon Oct 20 07:51:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82DC33A69FF;
	Mon, 20 Oct 2008 07:51:03 -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 3FBBC3A69CE
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 07:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.155
X-Spam-Level: 
X-Spam-Status: No, score=-6.155 tagged_above=-999 required=5 tests=[AWL=0.094, 
	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 qzRRnK4bT9Mi for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 07:51:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 1C6813A6839
	for <behave@ietf.org>; Mon, 20 Oct 2008 07:51:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E9EF220DF6; Mon, 20 Oct 2008 16:52:11 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-38-48fc9b1be4d2
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C59E220E13; Mon, 20 Oct 2008 16:52:11 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 16:52:11 +0200
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 16:52:10 +0200
Message-ID: <48FC9B1B.1040108@ericsson.com>
Date: Mon, 20 Oct 2008 16:52:11 +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: <48F76EFC.9000703@ericsson.com>
	<E03C9DF8-9225-45AF-BCCD-FCFCB06CB412@muada.com>
In-Reply-To: <E03C9DF8-9225-45AF-BCCD-FCFCB06CB412@muada.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 20 Oct 2008 14:52:10.0863 (UTC)
	FILETIME=[6E60F7F0:01C932C3]
X-Brightmail-Tracker: AAAAAA==
Cc: 46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] [Fwd: 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

Inline,

Iljitsch van Beijnum skrev:
> On 16 okt 2008, at 18:42, Magnus Westerlund wrote:
> =

>> 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.
> =

> Isn't this trivial: just add "fake" AAAA records manually and do SIIT
> (1-to-1)? (Same thing for 4.)

Probably, but we need to document it so that people don't get inventive.

> =

>> 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.
> =

> Will this be a separate solution or integrated with v6-to-v4?

A very good question that I intended to give the WG a while to determine.

> =

>> All translation solutions shall be capable of handling flows using TCP,
>> UDP, DCCP, and SCTP.
> =

> I disagree. This is a quick fix effort. DCCP and SCTP have essentially
> zero deployment, making these "MUST" will slow down the work without a
> real world benefit. Same thing for multicast. There is no end-to-end
> multicast on the internet today, so there is no vicious deployment cycle
> to break with translation.

Lets start with multicast. I agree about that over the general Internet
there isn't deployment. However, if for example Cisco is going to deploy
a new office that only has IPv6, then they likely need multicast support
towards the rest of their IPv4 network to support there conferencing
tools. That is why I am very hesitant to leave it out without first
saying that it is to hard.

When it comes to our "new" transport protocol, I don't like to make
deployment even harder. If they slow this work down significantly I am
okay to cut them out. But I don't believe that will be the case. The
specification for DCCP is already done for IPv4, and the reality is that
if you can support TCP and UDP, you have all the components for DCCP.
SCTP is not yet ready when it comes to v4v4 translation.

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 07:51:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B30F63A6A37;
	Mon, 20 Oct 2008 07:51:20 -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 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: [BEHAVE] [v4v6interim] 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

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 07:57:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7063C3A6A37;
	Mon, 20 Oct 2008 07:57:38 -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 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: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>

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


From behave-bounces@ietf.org  Mon Oct 20 08:15:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 553C83A68D0;
	Mon, 20 Oct 2008 08:15:46 -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 0CA453A69B1
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 08:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 
	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 F2mWStpuwyyn for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 08:15:44 -0700 (PDT)
Received: from QMTA06.emeryville.ca.mail.comcast.net
	(qmta06.emeryville.ca.mail.comcast.net [76.96.30.56])
	by core3.amsl.com (Postfix) with ESMTP id 37C803A68D0
	for <behave@ietf.org>; Mon, 20 Oct 2008 08:15:44 -0700 (PDT)
Received: from OMTA04.emeryville.ca.mail.comcast.net ([76.96.30.35])
	by QMTA06.emeryville.ca.mail.comcast.net with comcast
	id V0vx1a0090lTkoCA63GwoQ; 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>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 12:35:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B49AF3A6A72;
	Mon, 20 Oct 2008 12:35:49 -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 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
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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

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

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


From behave-bounces@ietf.org  Mon Oct 20 14:29:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 192303A6A82;
	Mon, 20 Oct 2008 14:29:30 -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 431BA3A6A9C
	for <behave@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.405
X-Spam-Level: 
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5
	tests=[AWL=-0.106, 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 c5MUcX3P1Ifz for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 14:29:28 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28])
	by core3.amsl.com (Postfix) with ESMTP id 4B1593A6A10
	for <behave@ietf.org>; Mon, 20 Oct 2008 14:29:28 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so347222ywj.49
	for <behave@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: [BEHAVE] NAT66 for PI [Re: [46translation] [v4v6interim] Proposal
 for new	BEHAVEcharter]
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-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
X19fX19fX19fX19fX18KQmVoYXZlIG1haWxpbmcgbGlzdApCZWhhdmVAaWV0Zi5vcmcKaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9iZWhhdmUK


From behave-bounces@ietf.org  Mon Oct 20 14:35:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F71F3A6AD5;
	Mon, 20 Oct 2008 14:35:14 -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 9F0E83A6AC1
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 14:35:12 -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 DYNNxmDI5E0T for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 14:35:11 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.172])
	by core3.amsl.com (Postfix) with ESMTP id DA6A83A6849
	for <behave@ietf.org>; Mon, 20 Oct 2008 14:35:11 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so2308093wfd.31
	for <behave@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: Margaret Wasserman <mrw@lilacglade.org>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: [BEHAVE] "My" [Re: [46translation] [v4v6interim] 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Mon Oct 20 14:40:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 277573A6B05;
	Mon, 20 Oct 2008 14:40:56 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 20 14:42:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 571F63A6ADC;
	Mon, 20 Oct 2008 14:42:03 -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 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: [BEHAVE] [v4v6interim] "My" [Re: [46translation] 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

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

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


From behave-bounces@ietf.org  Mon Oct 20 15:32:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D79083A68B3;
	Mon, 20 Oct 2008 15:32:47 -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 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
Cc: "v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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

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


From behave-bounces@ietf.org  Mon Oct 20 15:42:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7DC53A6AA0;
	Mon, 20 Oct 2008 15:42:05 -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 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: Marc Blanchet <marc.blanchet@viagenie.ca>,
	"v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Mon Oct 20 15:45:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 070033A6B1B;
	Mon, 20 Oct 2008 15:45:02 -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 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
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>,
	"v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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

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
>

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


From behave-bounces@ietf.org  Mon Oct 20 23:29:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 071403A69CF;
	Mon, 20 Oct 2008 23:29:53 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Mon Oct 20 23:41:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6815F3A6A04;
	Mon, 20 Oct 2008 23:41:49 -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 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: Marc Blanchet <marc.blanchet@viagenie.ca>,
	"v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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


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


From behave-bounces@ietf.org  Tue Oct 21 00:53:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AB2F3A6B11;
	Tue, 21 Oct 2008 00:53:48 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 21 02:50:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 229B63A6B0B;
	Tue, 21 Oct 2008 02:50:19 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 21 03:33:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3B2528C0D0;
	Tue, 21 Oct 2008 03:33:20 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 21 07:08:01 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 021E328C11C;
	Tue, 21 Oct 2008 07:08:01 -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 16BA93A6943
	for <behave@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.029
X-Spam-Level: 
X-Spam-Status: No, score=-6.029 tagged_above=-999 required=5 tests=[AWL=0.016, 
	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 iQFyj2nfMNKH for <behave@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 7235D28C114
	for <behave@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>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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: multipart/mixed; boundary="===============1622928512=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1622928512==
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)--

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

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

--===============1622928512==--


From behave-bounces@ietf.org  Tue Oct 21 08:43:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C58393A6B3E;
	Tue, 21 Oct 2008 08:43:30 -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 D19883A6936
	for <behave@core3.amsl.com>; Mon, 20 Oct 2008 12:28:43 -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 bvE6bOJr7esL for <behave@core3.amsl.com>;
	Mon, 20 Oct 2008 12:28:43 -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 BEB9C3A68D0
	for <behave@ietf.org>; Mon, 20 Oct 2008 12:28:42 -0700 (PDT)
Received: by gxk9 with SMTP id 9so4300413gxk.13
	for <behave@ietf.org>; Mon, 20 Oct 2008 12:29:43 -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
X-Mailman-Approved-At: Tue, 21 Oct 2008 08:43:28 -0700
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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


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

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


From behave-bounces@ietf.org  Tue Oct 21 08:51:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C74C73A6A42;
	Tue, 21 Oct 2008 08:51:47 -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 2128D3A6A42
	for <behave@core3.amsl.com>; Tue, 21 Oct 2008 08:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.529
X-Spam-Level: 
X-Spam-Status: No, score=-6.529 tagged_above=-999 required=5 tests=[AWL=0.070, 
	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 KedbTrb18cUC for <behave@core3.amsl.com>;
	Tue, 21 Oct 2008 08:51:40 -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 CDA363A6A39
	for <behave@ietf.org>; Tue, 21 Oct 2008 08:51:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="97318131"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 21 Oct 2008 15:52:35 +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 m9LFqX47003445; 
	Tue, 21 Oct 2008 08:52:33 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9LFqWEP023916;
	Tue, 21 Oct 2008 15:52:32 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Tue, 21 Oct 2008 08:52:32 -0700
Message-ID: <01d801c93395$07ccdd60$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: AckzlQeFGcfzPoV6QnKmJGpjpA/QOQ==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=447; t=1224604353; x=1225468353;
	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:=20interim=20meeting,=20January=2020-22,=202009
	|Sender:=20; bh=BHLiScitQ4HkNNKDLqXm8E2LaJMgoIHxpACKlCKfUyw=;
	b=IN31LoFLzDOmYYTTjnl4LohxRWZnxREh4oEmU2Ari9OIkAqOKhW2pzqUKs
	I2dS1t+HEm2QORAGfsg3oqACsxCKZjGumI38Ktav0r/mzwdbOngUUnGfgN/j
	JFqsvN43orQvpz8DV3H+BcgqfByz9KTT4HXw6EdTC8BZ1W9qq+c2I=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Dave Thaler <dthaler@microsoft.com>
Subject: [BEHAVE] interim meeting, January 20-22, 2009
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

An IETF-wide interim meeting is planned for January 20-22, 2009
in Malta.  Based on the ~60 people we had in Montreal, the
BEHAVE chairs requested a slot at this interim.  More details
can be found here:
http://trac.tools.ietf.org/2009/jan-large-interim/

Please consider if this interim meeting would be useful to you
and the agenda you would like for the meeting, and let us know
in Minneapolis or via email.

-Dave Thaler
-Dan Wing

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


From behave-bounces@ietf.org  Wed Oct 22 10:15:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29C0628C178;
	Wed, 22 Oct 2008 10:15:04 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 51D7A3A68D1; Wed, 22 Oct 2008 10:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081022171501.51D7A3A68D1@core3.amsl.com>
Date: Wed, 22 Oct 2008 10:15:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-sctpnat-00.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Stream Control Transmission Protocol (SCTP) Network Address Translation
	Author(s)       : R. Stewart, et al.
	Filename        : draft-ietf-behave-sctpnat-00.txt
	Pages           : 24
	Date            : 2008-10-22

Stream Control Transmission Protocol [RFC4960] provides a reliable
communications channel between two end-hosts in many ways similar to
TCP [RFC0793].  With the widespread deployment of Network Address
Translators (NAT), specialized code has been added to NAT for TCP
that allows multiple hosts to reside behind a NAT and yet use only a
single globally unique IPv4 address, even when two hosts (behind a
NAT) choose the same port numbers for their connection.  This
additional code is sometimes classified as Network Address and Port
Translation or NAPT.  To date, specialized code for SCTP has NOT yet
been added to most NATs so that only pure NAT is available.  The end
result of this is that only one SCTP capable host can be behind a
NAT.

This document describes an SCTP specific variant of NAT which
provides similar features of NAPT in the single point and multi-point
traversal scenario.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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


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

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

--NextPart--


From behave-bounces@ietf.org  Wed Oct 22 11:33:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF69E3A6A58;
	Wed, 22 Oct 2008 11:33:50 -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 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: [BEHAVE] NAT66 for PI [Re: [46translation] [v4v6interim]
 Proposal for new	BEHAVEcharter]
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Folks,

We have quite a lot on our plate already. Lets not add NAT66 to it as well.

Jari

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


From behave-bounces@ietf.org  Thu Oct 23 06:59:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A8D83A6ABB;
	Thu, 23 Oct 2008 06:59:17 -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 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: Marc Blanchet <marc.blanchet@viagenie.ca>,
	"v4v6interim@ietf.org" <v4v6interim@ietf.org>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 07:21:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A448A3A6C32;
	Thu, 23 Oct 2008 07:21:40 -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 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: [BEHAVE] [46translation] [v4v6interim] "My" [Re: 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>   =


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


From behave-bounces@ietf.org  Thu Oct 23 07:33:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 393A83A6ACC;
	Thu, 23 Oct 2008 07:33:49 -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 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>, Fred Baker <fred@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 07:40:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 270703A6928;
	Thu, 23 Oct 2008 07:40:43 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>

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


From behave-bounces@ietf.org  Thu Oct 23 07:48:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80B573A6A29;
	Thu, 23 Oct 2008 07:48:56 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>>
>>     
>
>
>   

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


From behave-bounces@ietf.org  Thu Oct 23 08:06:07 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD4BF3A696E;
	Thu, 23 Oct 2008 08:06:07 -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 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: [BEHAVE] [v4v6interim] [46translation] 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

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 08:15:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85FC128B23E;
	Thu, 23 Oct 2008 08:15:55 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
> ----------------------------------------------------------------------
>
>   =


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


From behave-bounces@ietf.org  Thu Oct 23 08:17:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A2673A6B80;
	Thu, 23 Oct 2008 08:17:37 -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 13B3B3A6AD7;
	Thu, 23 Oct 2008 08:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level: 
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5
	tests=[AWL=-0.052, BAYES_00=-2.599, SPF_PASS=-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 P7D52GSlMRiN; Thu, 23 Oct 2008 08:17:27 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 19B2C3A69E2;
	Thu, 23 Oct 2008 08:17:26 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9NFIhfo021448
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 23 Oct 2008 10:18:43 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <BAB44C27-EEFC-4208-BC1A-82C89D42E7D8@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: sipping LIST <sipping@ietf.org>, behave@ietf.org, mmusic@ietf.org,
	avt@ietf.org, simple mailing list <simple@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 10:18:43 -0500
X-Mailer: Apple Mail (2.929.2)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8476/Thu Oct 23 09:46:06 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Subject: [BEHAVE] SIPit23 Survey notes
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Notes from SIPit23 are available at https://www.sipit.net/SIPit23_Summary 
.

(Apologies for the crosspost).

RjS
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 08:27:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C773A3A6A27;
	Thu, 23 Oct 2008 08:27:56 -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 A26563A690B
	for <behave@core3.amsl.com>; Thu, 23 Oct 2008 08:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5
	tests=[AWL=-0.400, 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 xFrPX5Wav-g6 for <behave@core3.amsl.com>;
	Thu, 23 Oct 2008 08:27:51 -0700 (PDT)
Received: from QMTA04.emeryville.ca.mail.comcast.net
	(qmta04.emeryville.ca.mail.comcast.net [76.96.30.40])
	by core3.amsl.com (Postfix) with ESMTP id 7F97C3A681C
	for <behave@ietf.org>; Thu, 23 Oct 2008 08:27:51 -0700 (PDT)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA04.emeryville.ca.mail.comcast.net with comcast
	id WANo1a0040EPchoA4FUYe7; 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Thu Oct 23 08:29:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 631723A6A0E;
	Thu, 23 Oct 2008 08:29:42 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Thu Oct 23 08:46:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1C3B3A6A03;
	Thu, 23 Oct 2008 08:46:11 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>
>

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


From behave-bounces@ietf.org  Thu Oct 23 09:05:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5DD73A6AB0;
	Thu, 23 Oct 2008 09:05:43 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.





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


From behave-bounces@ietf.org  Thu Oct 23 09:34:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A55BE3A684D;
	Thu, 23 Oct 2008 09:34:09 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 09:40:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 218C93A6A0A;
	Thu, 23 Oct 2008 09:40:42 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>
>
>
>
>
>

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


From behave-bounces@ietf.org  Thu Oct 23 10:34:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41A9A3A684D;
	Thu, 23 Oct 2008 10:34:29 -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 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: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Thu Oct 23 10:38:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2DCC3A6892;
	Thu, 23 Oct 2008 10:38:17 -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 682A23A68E8
	for <behave@core3.amsl.com>; Thu, 23 Oct 2008 10:38:16 -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 tEPobGzwogZL for <behave@core3.amsl.com>;
	Thu, 23 Oct 2008 10:38:15 -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 52F193A6767
	for <behave@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 WH1F1a0010Fqzac56HfD0A; 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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


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


From behave-bounces@ietf.org  Thu Oct 23 10:40:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1553E3A6A3A;
	Thu, 23 Oct 2008 10:40:29 -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 90BF53A6A0E
	for <behave@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.659
X-Spam-Level: 
X-Spam-Status: No, score=-2.659 tagged_above=-999 required=5
	tests=[AWL=-0.060, 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 vKD9Q+FmFw5C for <behave@core3.amsl.com>;
	Thu, 23 Oct 2008 10:40:27 -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 7304F3A6A1D
	for <behave@ietf.org>; Thu, 23 Oct 2008 10:40:27 -0700 (PDT)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA10.westchester.pa.mail.comcast.net with comcast
	id WFhg1a00616LCl05AHhjCf; Thu, 23 Oct 2008 17:41:43 +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: 'Mark Townsley' <townsley@cisco.com>, v4v6interim@ietf.org,
	'46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Thu Oct 23 10:46:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79D933A6AB1;
	Thu, 23 Oct 2008 10:46:09 -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 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: 'Mark Townsley' <townsley@cisco.com>, v4v6interim@ietf.org,
	'46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Thu Oct 23 10:48:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AD603A6AAF;
	Thu, 23 Oct 2008 10:48:32 -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 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: 'Margaret Wasserman' <mrw@lilacglade.org>, v4v6interim@ietf.org,
	'46Translation' <46translation@employees.org>,
	'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
>
>
>   

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


From behave-bounces@ietf.org  Thu Oct 23 14:12:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 639FB3A6A78;
	Thu, 23 Oct 2008 14:12:26 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 14:37:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A9A63A686E;
	Thu, 23 Oct 2008 14:37:42 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 23 16:27:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38BD23A6823;
	Thu, 23 Oct 2008 16:27:00 -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 CD2ED3A6823
	for <behave@core3.amsl.com>; Thu, 23 Oct 2008 16:26:58 -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 med+WPLneBxD for <behave@core3.amsl.com>;
	Thu, 23 Oct 2008 16:26:57 -0700 (PDT)
Received: from mail-08.primus.ca (mail6.primus.ca [216.254.141.173])
	by core3.amsl.com (Postfix) with ESMTP id B1A233A67EE
	for <behave@ietf.org>; Thu, 23 Oct 2008 16:26:57 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-08.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1Kt9bA-0000Nh-2l; Thu, 23 Oct 2008 19:28:13 -0400
Message-Id: <F140F99A-AE70-4EA1-8B4F-E969C9EC08E6@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
In-Reply-To: <9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 19:28:08 -0400
References: <58AE9DA8-E81A-4D68-A498-12339AA07976@magma.ca>	<48EA4A87.6090606@matthew.at>	<72CDC7AC-8927-44E4-8910-77D92742DB5A@magma.ca>	<48EA6C92.5070701@matthew.at>	<D6215C36-EA5D-4455-A4F7-473F91EAA551@magma.ca>	<48EA77AD.2050100@matthew.at>	<F649A330-7A4B-4773-B0A9-BDFF8322BAAD@magma.ca>
	<48F74C52.4030203@cisco.com> <48F76DA2.4020406@acm.org>
	<9CDBB9BF-F199-49CC-82A2-66FD85BECE5A@magma.ca>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: matthew@matthew.at
Subject: Re: [BEHAVE] TURN: Send indication when no permission exists
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Thu, 16-Oct-08, at 13:27 , Philip Matthews wrote:

>
> On Thu, 16-Oct-08, at 12:36 , Marc Petit-Huguenin wrote:
>
>> Jonathan Rosenberg wrote:
>>> So I just got off the phone with Philip, we were talking about  
>>> this, and
>>> here is an interesting idea.
>>>
>>> As Philip points out, the CreatePermission is required if you want  
>>> the
>>> far end to be able to send you a response to a message delivered  
>>> via a
>>> Send indication. So, regardless of the question about whether you  
>>> can do
>>> a Send prior to CreatePermission, there *will* need to be a
>>> CreatePermission for each unique IP address you want to send to,  
>>> even if
>>> there will be just a single packet and response from that IP  
>>> address.
>>>
>>> The concern raised by Matthew applies to ICE as well; that for cases
>>> where there are a lot of candidates, you'll end up sending a
>>> connectivity check and a CreatePermission, thus increasing the  
>>> number of
>>> packets sent for connectivity checks.
>>>
>>> The solution we came up with for this is very simple. We allow
>>> CreatePermission to carry *multiple* XOR-PEER-ADDRESS attributes,  
>>> which
>>> opens permissions to many IP addresses with one transaction. In  
>>> the case
>>> of ICE, after the O/A exchange is done, each agent knows the full  
>>> set of
>>> IP addresses it might eventually do a check to. Thus, it would do a
>>> single CreatePermission to all of them, and then proceed with the  
>>> checks
>>> using Send indications. Once ICE completes, if a TURN candidate is
>>> selected, the client would do a CHannelBind for high volume
>>> transcations. With this solution, the CreatePermission mechanism  
>>> imposes
>>> only a single packet overhead, independent of the number of  
>>> candidates.
>>> It can be paralellized with the connectivity checks themselves,  
>>> and thus
>>> has no impact on the latency of ICE.
>>>
>>> This would work well in conjunction with the proposal that you  
>>> cannot do
>>> a Send to a destination without previously doing a CreatePermission.
>>>
>>> What do folks think of this solution?
>>
>> I am OK with this, but I am not sure that having multiple
>> XOR-PEER-ADDRESS attributes would work, because of this sentence in
>> rfc3489bis:
>>
>> "Any attribute type MAY appear more than once in a STUN message.
>> Unless specified otherwise, the order of appearance is significant:
>> only the first occurance needs to be processed by a receiver, and any
>> duplicates MAY be ignored by a receiver."
>>
>> I would suggest to allow XOR-PEER-ADDRESS (perhaps renamed to
>> XOR-PEER-ADDRESSES) to contain multiple addresses, simply repeating  
>> the
>> family, port and address field for each address.
>
> Well, our idea was to take advantage of the "Unless specified  
> otherwise ..." clause and specify that, for the XOR-PEER-ADDRESS  
> attribute in the CreatePermission request, multiple occurrences  
> _are_ significant. [Option 1]
>
> However, there are two other options:
> 2) Allow the XOR-PEER-ADDRESS attribute to contain multiple  
> addresses for CreatePermission, but not for Send indication, Data  
> indication, or ChannelBind, OR
> 3) Define a new attribute XOR-PEER-ADDRESSES, which is used only in  
> CreatePermission, that allows multiple addresses. The existing XOR- 
> PEER-ADDRESS would be used in Send indication, Data indication, and  
> ChannelBind.
>
> My personal preference is for 1. However, if implementors say "My  
> stack won't allow option 1, because it assumes that only the first  
> occurrence of an attribute is significant", then we could do option  
> 3 instead.

I have seen two responses (from Simon and Richard) asking for option  
1. Marc said that is is OK with option 1, and Jonathan has told me  
privately that he is also ok with option 1. So unless someone raises a  
strong objection, TURN-11 will use option 1.

As Jonathan points out, this also works well with the proposal that  
you cannot do a Send to a destination without previously doing a  
CreatePermission, which was the original subject of this thread. Since  
we seem to have addressed the only concern with this second proposal,  
TURN-11 will also document this restriction.

Hopefully, these two issues are now closed.

- Philip

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


From behave-bounces@ietf.org  Thu Oct 23 23:09:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 681A23A68AA;
	Thu, 23 Oct 2008 23:09:25 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:09:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3437A3A6A7C;
	Fri, 24 Oct 2008 02:09:33 -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 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: Mark Townsley <townsley@cisco.com>,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:15:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 622533A6A6A;
	Fri, 24 Oct 2008 02:15:42 -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 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: [BEHAVE] [v4v6interim] [46translation] 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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:19:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15A283A6A92;
	Fri, 24 Oct 2008 02:19:48 -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 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
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:33:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8E4F28C149;
	Fri, 24 Oct 2008 02:33: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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:37:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B6503A692B;
	Fri, 24 Oct 2008 02:37:43 -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 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]
Cc: townsley@cisco.com, 46translation@employees.org, behave@ietf.org
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 02:55:32 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BA543A6A16;
	Fri, 24 Oct 2008 02:55:32 -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 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: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Fri Oct 24 03:00:18 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 236013A6A75;
	Fri, 24 Oct 2008 03:00:18 -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 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: Margaret Wasserman <mrw@lilacglade.org>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
> ----------------------------------------------------------------------
>
>   =


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


From behave-bounces@ietf.org  Fri Oct 24 03:08:52 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C90663A69EF;
	Fri, 24 Oct 2008 03:08:52 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>,
	ext Pekka Savola <pekkas@netcore.fi>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 04:21:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB2893A6A9C;
	Fri, 24 Oct 2008 04:21:49 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 04:42:51 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D52653A69D4;
	Fri, 24 Oct 2008 04:42:51 -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 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: [BEHAVE] [46translation] [v4v6interim] 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

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
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 04:51:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1555C3A6A41;
	Fri, 24 Oct 2008 04:51:02 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 06:11:04 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AF333A6B21;
	Fri, 24 Oct 2008 06:11:04 -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 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: [BEHAVE] [46translation] [v4v6interim] Proposal for new BEHAVE
 charter
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-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
> =


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


From behave-bounces@ietf.org  Fri Oct 24 06:15:13 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 810753A6B21;
	Fri, 24 Oct 2008 06:15:13 -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 0A6373A6B21
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 06:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.258
X-Spam-Level: 
X-Spam-Status: No, score=-1.258 tagged_above=-999 required=5 tests=[AWL=1.991, 
	BAYES_00=-2.599, HELO_EQ_FR=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 qmj25+IX54FQ for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 06:15:11 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id D008F3A6AA3
	for <behave@ietf.org>; Fri, 24 Oct 2008 06:15:10 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 15:16:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C935DA.BAFE8C37"
Date: Fri, 24 Oct 2008 15:16:30 +0200
Message-ID: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-boucadair-port-range-00.txt 
Thread-Index: Ack1DZBIfgXcTQ//TVCUWnQhN9YVOAAzAofQ
From: <pierre.levis@orange-ftgroup.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 24 Oct 2008 13:16:31.0517 (UTC)
	FILETIME=[BB1D44D0:01C935DA]
Subject: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

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

Hi all,

I would like to draw your attention on the following draft.

We (the authors) are looking forward to reading your comments.


Regards


Pierre



-----Message d'origine-----
De : i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org] De la part de =
Internet-Drafts@ietf.org
Envoy=E9 : jeudi 23 octobre 2008 14:45
=C0 : i-d-announce@ietf.org
Objet : I-D Action:draft-boucadair-port-range-00.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts =
directories.

	Title           : Provider-Provisioned CPE: IPv4 Connectivity Access in =
the context of IPv4 address exhaustion
	Author(s)       : M. Boucadair, et al.
	Filename        : draft-boucadair-port-range-00.txt
	Pages           : 33
	Date            : 2008-10-23

This memo proposes a solution, based on fractional addresses, to face =
the IPv4 public address exhaustion.  It details the solution and =
presents a mock-up implementation, with the results of tests that =
validate the concept.  Finally, it makes a comparison with the =
alternative Carrier-Grade NAT (CG-NAT) solutions.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader =
implementation to automatically retrieve the ASCII version of the =
Internet-Draft.

------_=_NextPart_001_01C935DA.BAFE8C37
Content-Type: application/octet-stream;
	name="draft-boucadair-port-range-00.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-boucadair-port-range-00.URL
Content-Disposition: attachment;
	filename="draft-boucadair-port-range-00.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1ib3VjYWRhaXItcG9ydC1yYW5nZS0wMC50eHQNCg==

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

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

------_=_NextPart_001_01C935DA.BAFE8C37--


From behave-bounces@ietf.org  Fri Oct 24 06:22:29 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E81A23A6B24;
	Fri, 24 Oct 2008 06:22:29 -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 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: [BEHAVE] [46translation] [v4v6interim] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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.)
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 06:44:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EC6428C194;
	Fri, 24 Oct 2008 06:44:56 -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 5E64228C18A
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 06:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.237
X-Spam-Level: 
X-Spam-Status: No, score=-6.237 tagged_above=-999 required=5 tests=[AWL=0.062, 
	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 q4Ip9uq432-o for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 06:44:53 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 366EA28C179
	for <behave@ietf.org>; Fri, 24 Oct 2008 06:44:53 -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
	m9ODjmlR003282; Fri, 24 Oct 2008 16:46:12 +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 16:44:22 +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 16:44:19 +0300
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org, alain.villefranque@orange-ftgroup.com
Date: Fri, 24 Oct 2008 16:44:22 +0300
User-Agent: KMail/1.9.10
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
In-Reply-To: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241644.22542.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 13:44:19.0446 (UTC)
	FILETIME=[9D470960:01C935DE]
X-Nokia-AV: Clean
Cc: mohamed.boucadair@orange-ftgroup.com,
	"ext pierre.levis@orange-ftgroup.com" <pierre.levis@orange-ftgroup.com>,
	jean-luc.grimault@orange-ftgroup.com
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

CglIZWxsbywKCk9uIEZyaWRheSAyNCBPY3RvYmVyIDIwMDggMTY6MTY6MzAgZXh0IHBpZXJyZS5s
ZXZpc0BvcmFuZ2UtZnRncm91cC5jb20sIHlvdSAKd3JvdGU6Cj4gSSB3b3VsZCBsaWtlIHRvIGRy
YXcgeW91ciBhdHRlbnRpb24gb24gdGhlIGZvbGxvd2luZyBkcmFmdC4KPgo+IFdlICh0aGUgYXV0
aG9ycykgYXJlIGxvb2tpbmcgZm9yd2FyZCB0byByZWFkaW5nIHlvdXIgY29tbWVudHMuCgpTZWN0
aW9uIDUuNCBpcyBhIGJpdCB1bmNsZWFyIHRvIG1lLiBJdCBzZWVtcyBsaWtlIHlvdSBhcmUgcmVm
ZXJyaW5nIHRvIHRoZSAKaW5hYmlsaXR5IG9mIENHLU5BVHMgKG9yIGFueSBuZXN0ZWQgTkFUIHNj
ZW5hcmlvIGZvciB0aGF0IG1hdHRlcikgdG8gaGFuZGxlIApVUG5QIElHRCwgTkFULVBNUCBhbmQv
b3IgbWFudWFsIHBvcnQgZm9yd2FyZGluZy4gVGhhdCdzIHRydWUsIGFuZCB0aGF0IGlzIGEgCnBy
b2JsZW0gZm9yIGNlcnRhaW4gYXBwbGljYXRpb25zLgoKSG93ZXZlciwgdGhpcyBzZWVtcyB0byBh
c3N1bWUgdGhhdCBhbGwgUDJQIGFwcGxpY2F0aW9ucyByZWx5IG9uIHRoaXMuIEFzIGZhciAKYXMg
SSBrbm93LCB0aGVyZSBhcmUgYSBidW5jaCBvZiBQMlAgYXBwbGljYXRpb25zIHVzaW5nICJiaWxh
dGVyYWwiIE5BVCAKdHJhdmVyc2FsLCBmb3IgaW5zdGFuY2UgVm9JUCBjbGllbnRzIG9yIFRlcmVk
by1iYXNlZCBQMlAgZmlsZSBzaGFyaW5nIGFwcHMuCgoKTW9yZSBpbXBvcnRhbnRseSwgc29tZSBx
dWVzdGlvbnMgKHNvcnJ5IGlmIEkgbWlzc2VkIHRoZSBleHBsYW5hdGlvbiBpbiB0aGUgCmRvY3Vt
ZW50KSBhcyB0byBob3cgUFJSIHdvcmtzIGluIHRoZSBmb2xsb3dpbmcgY2FzZXM6CiogYSBjb250
ZW1wb3JhcnkgQ1BFIGlzIGF0dGFjaGVkIHRvIGEgUFJSLCB0aGF0IGRvZXMgbm90IGltcGxlbWVu
dCB0aGUgREhDUCBvciAKUFBQIFBSUiBleHRlbnNpb24/CiogYSBwbGFpbiBJUHY0IGhvc3QgaXMg
YXR0YWNoZWQgZGlyZWN0bHkgdG8gYSBQUlIgKG5vIENQRSBhdCBhbGwpPwoqIHNoYXJlZC1tZWRp
dW0gKG5vbiBwb2ludC10by1wb2ludCkgYWNjZXNzIG5ldHdvcmtzLCBzdWNoIGFzIERPQ1NJUywg
d2hpY2ggCnVzZXMgQVJQIGlmIEknbSBub3QgbWlzdGFrZW4/CgpSZWdhcmRzLAoKLS0gClLDqW1p
IERlbmlzLUNvdXJtb250Ck1hZW1vIFNvZnR3YXJlLCBOb2tpYSBEZXZpY2VzIFImRApfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpCZWhhdmUgbWFpbGluZyBs
aXN0CkJlaGF2ZUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2JlaGF2ZQo=


From behave-bounces@ietf.org  Fri Oct 24 06:49:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0AD228C17A;
	Fri, 24 Oct 2008 06:49:48 -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 08EEC28C17A
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 06:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.445
X-Spam-Level: 
X-Spam-Status: No, score=-6.445 tagged_above=-999 required=5 tests=[AWL=0.154, 
	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 6EJazFLABiEb for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 06:49:47 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id A22903A6B46
	for <behave@ietf.org>; Fri, 24 Oct 2008 06:49:46 -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
	m9ODojJq007766; Fri, 24 Oct 2008 16:51:06 +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 16:50:31 +0300
Received: from vaebe102.NOE.Nokia.com ([10.160.244.12]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 16:50:30 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 16:50:28 +0300
Message-ID: <DC237AE116C10E4C9AD162D6C2EE62FE0134DAEE@vaebe102.NOE.Nokia.com>
In-Reply-To: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
Thread-Index: Ack1DZBIfgXcTQ//TVCUWnQhN9YVOAAzAofQAAFCQ7A=
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
From: <teemu.savolainen@nokia.com>
To: <pierre.levis@orange-ftgroup.com>, <behave@ietf.org>,
	<Gabor.Bajko@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 13:50:30.0698 (UTC)
	FILETIME=[7A8F98A0:01C935DF]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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

Hi Pierre & all,

Please note that we have recently updated the "Dynamic Host Configuration P=
rotocol (DHCP) Options for Port Restricted IP Address Assignment" to contai=
n use cases and also e.g. considerations on relation to DS-Lite.

http://www.ietf.org/internet-drafts/draft-bajko-v6ops-port-restricted-ipadd=
r-assign-01.txt

(I will comment your draft next week when I have had time to properly read =
it trough).

Best regards,

	Teemu


>-----Original Message-----
>From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] =

>On Behalf Of ext pierre.levis@orange-ftgroup.com
>Sent: 24 October, 2008 16:17
>To: behave@ietf.org
>Subject: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
>
>Hi all,
>
>I would like to draw your attention on the following draft.
>
>We (the authors) are looking forward to reading your comments.
>
>
>Regards
>
>
>Pierre
>
>
>
>-----Message d'origine-----
>De : i-d-announce-bounces@ietf.org =

>[mailto:i-d-announce-bounces@ietf.org] De la part de =

>Internet-Drafts@ietf.org Envoy=E9 : jeudi 23 octobre 2008 14:45 =

>=C0 : i-d-announce@ietf.org Objet : I-D =

>Action:draft-boucadair-port-range-00.txt =

>
>A New Internet-Draft is available from the on-line =

>Internet-Drafts directories.
>
>	Title           : Provider-Provisioned CPE: IPv4 =

>Connectivity Access in the context of IPv4 address exhaustion
>	Author(s)       : M. Boucadair, et al.
>	Filename        : draft-boucadair-port-range-00.txt
>	Pages           : 33
>	Date            : 2008-10-23
>
>This memo proposes a solution, based on fractional addresses, =

>to face the IPv4 public address exhaustion.  It details the =

>solution and presents a mock-up implementation, with the =

>results of tests that validate the concept.  Finally, it makes =

>a comparison with the alternative Carrier-Grade NAT (CG-NAT) solutions.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>Below is the data which will enable a MIME compliant mail =

>reader implementation to automatically retrieve the ASCII =

>version of the Internet-Draft.
>
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 06:49:54 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1805628C1A0;
	Fri, 24 Oct 2008 06:49:54 -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 5198328C19D
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 06:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.94
X-Spam-Level: 
X-Spam-Status: No, score=-5.94 tagged_above=-999 required=5 tests=[AWL=-0.241, 
	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 fpcx-lDB9gzF for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 06:49:52 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 8388228C199
	for <behave@ietf.org>; Fri, 24 Oct 2008 06:49:52 -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
	m9ODnVoA032243; Fri, 24 Oct 2008 08:51:11 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 24 Oct 2008 16:49:55 +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 16:49:54 +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 16:49:54 +0300
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: dwing@cisco.com, Dave Thaler <dthaler@microsoft.com>
Date: Fri, 24 Oct 2008 16:49:57 +0300
User-Agent: KMail/1.9.10
References: <20081020133243.50D063A698B@core3.amsl.com>
	<200810201657.11772.remi.denis-courmont@nokia.com>
In-Reply-To: <200810201657.11772.remi.denis-courmont@nokia.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810241649.57686.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 24 Oct 2008 13:49:54.0783 (UTC)
	FILETIME=[652766F0:01C935DF]
X-Nokia-AV: Clean
Cc: Mark Townsley <townsley@cisco.com>, ext Jari Arkko <jari.arkko@piuha.net>,
	behave@ietf.org
Subject: Re: [BEHAVE] New Version Notification for
	draft-denis-behave-v4v6exthdr-00
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

CglIZWxsbywKCkRvIHlvdSB0aGluayBpdCB3b3VsZCBiZSBhcHByb3ByaWF0ZSB0byBkaXNjdXNz
IHRoaXMgaW4gQkVIQVZFPyBvciBJTlQtQVJFQT8gCm9yIG5vd2hlcmU/IG9yLi4uPyAoSSBhc3N1
bWUgbm90IDZtYW4gc2luY2UgaXQncyBub3QgbWFpbnRlbmFuY2UsIGFuZCBub3QgCnY2b3BzIHNp
bmNlIGl0IGlzIHByb3RvY29sIHdvcmspCgpUaGFua3MgaW4gYWR2YW5jZSwKCkJlc3QgcmVnYXJk
cywKCk9uIE1vbmRheSAyMCBPY3RvYmVyIDIwMDggMTY6NTc6MTEgZXh0IFLDqW1pIERlbmlzLUNv
dXJtb250LCB5b3Ugd3JvdGU6Cj4gRllJIC0gY29tbWVudHMgbW9zdCB3ZWxjb21lOgo+IGh0dHA6
Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWRlbmlzLWJlaGF2ZS12NHY2ZXh0
aGRyLTAwLnR4dAoKLS0gClLDqW1pIERlbmlzLUNvdXJtb250Ck1hZW1vIFNvZnR3YXJlLCBOb2tp
YSBEZXZpY2VzIFImRApfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXwpCZWhhdmUgbWFpbGluZyBsaXN0CkJlaGF2ZUBpZXRmLm9yZwpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQo=


From behave-bounces@ietf.org  Fri Oct 24 07:04:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E643528C19F;
	Fri, 24 Oct 2008 07:04:00 -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 20ACD3A6B3F
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 07:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.691
X-Spam-Level: 
X-Spam-Status: No, score=-5.691 tagged_above=-999 required=5
	tests=[AWL=-0.342, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	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 tWhNKWQXjFrb for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 07:03:59 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2D5473A687C
	for <behave@ietf.org>; Fri, 24 Oct 2008 07:03:59 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	EAF2320E42; Fri, 24 Oct 2008 16:05:19 +0200 (CEST)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-6f-4901d61fac6c
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D25BC20ABC; Fri, 24 Oct 2008 16:05:19 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 16:05:19 +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 16:05:18 +0200
Message-ID: <4901D61F.8040703@ericsson.com>
Date: Fri, 24 Oct 2008 16:05:19 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?=
 <remi.denis-courmont@nokia.com>
References: <20081020133243.50D063A698B@core3.amsl.com>	<200810201657.11772.remi.denis-courmont@nokia.com>
	<200810241649.57686.remi.denis-courmont@nokia.com>
In-Reply-To: <200810241649.57686.remi.denis-courmont@nokia.com>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 24 Oct 2008 14:05:18.0814 (UTC)
	FILETIME=[8BEB57E0:01C935E1]
X-Brightmail-Tracker: AAAAAA==
Cc: Mark Townsley <townsley@cisco.com>, behave@ietf.org,
	ext Jari Arkko <jari.arkko@piuha.net>,
	Dave Thaler <dthaler@microsoft.com>, dwing@cisco.com
Subject: Re: [BEHAVE] New Version Notification
	for	draft-denis-behave-v4v6exthdr-00
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

UsOpbWkgRGVuaXMtQ291cm1vbnQgc2tyZXY6Cj4gCUhlbGxvLAo+IAo+IERvIHlvdSB0aGluayBp
dCB3b3VsZCBiZSBhcHByb3ByaWF0ZSB0byBkaXNjdXNzIHRoaXMgaW4gQkVIQVZFPyBvciBJTlQt
QVJFQT8gCj4gb3Igbm93aGVyZT8gb3IuLi4/IChJIGFzc3VtZSBub3QgNm1hbiBzaW5jZSBpdCdz
IG5vdCBtYWludGVuYW5jZSwgYW5kIG5vdCAKPiB2Nm9wcyBzaW5jZSBpdCBpcyBwcm90b2NvbCB3
b3JrKQo+IAoKSSB0aGluayB3ZSBmaXN0IHN0YXJ0IGluIEJlaGF2ZSB0byBkaXNjdXNzIHRoZSBn
ZW5lcmFsIGZ1bmN0aW9uYWxpdHkKd2hlbiBwZXJmb3JtaW5nIHRyYW5zbGF0aW9uLiBUaGUgZmlu
YWwgZGV2ZWxvcG1lbnQgbWF5IGJlIGhhcHBlbmluZyBpbgphbm90aGVyIFdHIGxpa2UgNm1hbiBi
dXQgdGhhdCBpcyBmb3IgdGhlIGZ1dHVyZS4KCkNoZWVycwoKTWFnbnVzIFdlc3Rlcmx1bmQKCklF
VEYgVHJhbnNwb3J0IEFyZWEgRGlyZWN0b3IgJiBUU1ZXRyBDaGFpcgotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCk11
bHRpbWVkaWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFZNCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0KRXJpY3Nzb24gQUIgICAgICAgICAgICAgICAgfCBQaG9uZSArNDYgOCA0MDQ4Mjg3CkbD
pHLDtmdhdGFuIDYgICAgICAgICAgICAgICAgfCBGYXggICArNDYgOCA3NTc1NTUwClMtMTY0IDgw
IFN0b2NraG9sbSwgU3dlZGVuIHwgbWFpbHRvOiBtYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5j
b20KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwpCZWhhdmUgbWFpbGluZyBsaXN0CkJlaGF2ZUBpZXRmLm9yZwpodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQo=


From behave-bounces@ietf.org  Fri Oct 24 08:31:40 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21C3C3A6BCD;
	Fri, 24 Oct 2008 08:31:40 -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 D02393A6B5A
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 08:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.144
X-Spam-Level: 
X-Spam-Status: No, score=-106.144 tagged_above=-999 required=5
	tests=[AWL=0.155, 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 9VZHW4plwAL3 for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 08: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 2DE1828C114
	for <behave@ietf.org>; Fri, 24 Oct 2008 08:31:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,478,1220227200"; d="scan'208";a="95744030"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2008 15:32:40 +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 m9OFWdIa012256; 
	Fri, 24 Oct 2008 08:32:39 -0700
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18])
	by sj-core-3.cisco.com (8.13.8/8.13.8) with ESMTP id m9OFWciX024440;
	Fri, 24 Oct 2008 15:32:39 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <remi.denis-courmont@nokia.com>
In-Reply-To: <200810241210.46374.remi.denis-courmont@nokia.com>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <48F8539D.90608@ericsson.com> <49009C8B.80707@cisco.com>
	<A1BB57A1-8B5F-44FF-85BE-C533D0FAE85D@cisco.com>
	<200810241210.46374.remi.denis-courmont@nokia.com>
Message-Id: <ECC2575B-F1FC-4E66-818F-65AC58F70ECB@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 09:32:33 -0600
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1514; t=1224862359;
	x=1225726359; c=relaxed/simple; s=sjdkim2002;
	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=uf2v7CCY3LdJSNr8XHFYBhj28Kv/Yfb5gznkxjx5Ytw=;
	b=dPGs9ACu0b2Mv9A6VkchmZc0K/5SmFTeztA8+rtDo4cjoIB0lX2oHqUFP/
	fO6UDeimJdVxtT2szrm8ACUX8NftCbj1HpGfiTFk/vllusDbYWyjiyEFqk0U
	hqlemUNNq2;
Authentication-Results: sj-dkim-2; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Oct 24, 2008, at 3:10 AM, R=E9mi Denis-Courmont wrote:

> 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 fine
> with NATs (e.g. many web apps tie their "session" to the client IP  =

> address).

Agree - this email I think demonstrates why we are going to need a  =

wide range of people to get a good solution here. Iljitsch proposed a  =

very reasonable solution and Remi brought up something that apps do  =

that make this not work. Another example along the lines Remi is that  =

many SMTP servers authorize the user by first requiring a POP or IMAP  =

session from the same IP.


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


From behave-bounces@ietf.org  Fri Oct 24 08:43:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C391428C206;
	Fri, 24 Oct 2008 08:43:30 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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. 
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 24 08:46:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B3E23A6943;
	Fri, 24 Oct 2008 08:46:19 -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 BF63C3A6834
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 08:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.076
X-Spam-Level: 
X-Spam-Status: No, score=-6.076 tagged_above=-999 required=5
	tests=[AWL=-0.377, 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 SO-e-un2qrRL for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 08:46:16 -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 DC5053A6943
	for <behave@ietf.org>; Fri, 24 Oct 2008 08:46:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="98562443"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-2.cisco.com with ESMTP; 24 Oct 2008 15:47:39 +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 m9OFldtR007588; 
	Fri, 24 Oct 2008 08:47:39 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9OFlcW7004596;
	Fri, 24 Oct 2008 15:47:38 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>,
	"'Dave Thaler'" <dthaler@microsoft.com>
References: <20081020133243.50D063A698B@core3.amsl.com>
	<200810201657.11772.remi.denis-courmont@nokia.com>
	<200810241649.57686.remi.denis-courmont@nokia.com>
Date: Fri, 24 Oct 2008 08:47:38 -0700
Message-ID: <07f601c935ef$d79d5cc0$9d6d6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200810241649.57686.remi.denis-courmont@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack135YoD5of10/tRIezSq2ONq8IfQAD//Vw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1010; t=1224863259;
	x=1225727259; 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]=20New=20Version=20Notification
	=20for=20draft-denis-behave-v4v6exthdr-00 |Sender:=20;
	bh=XUYnrlZftA3FQh9QIxVIJqoe8vukuCFYQrVLOSZeiOU=;
	b=GgbWDdv8+mxc+BtGBFEYLH4/rVQOtYP9bKuIYvz1SpIQtD8aELWlArkEor
	YftUd8BnvMZLJRLjYf8OgU313BobMqirZgfbd4Nbfofl7WNa+vHVOn7eUEBi
	M/Yr1eNUvX;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: 'Mark Townsley' <townsley@cisco.com>,
	'ext Jari Arkko' <jari.arkko@piuha.net>, behave@ietf.org
Subject: Re: [BEHAVE] New Version Notification for
	draft-denis-behave-v4v6exthdr-00
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

 =


> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

> Sent: Friday, October 24, 2008 6:50 AM
> To: dwing@cisco.com; Dave Thaler
> Cc: behave@ietf.org; Mark Townsley; ext Jari Arkko
> Subject: Re: [BEHAVE] New Version Notification for =

> draft-denis-behave-v4v6exthdr-00
> =

> =

> 	Hello,
> =

> Do you think it would be appropriate to discuss this in =

> BEHAVE? or INT-AREA? =

> or nowhere? or...? (I assume not 6man since it's not =

> maintenance, and not =

> v6ops since it is protocol work)

BEHAVE, because that draft is all about informing the host's IPv6 stack of =
the
translator.

-d

> Thanks in advance,
> =

> Best regards,
> =

> On Monday 20 October 2008 16:57:11 ext R=E9mi Denis-Courmont, you wrote:
> > FYI - comments most welcome:
> > =

> http://www.ietf.org/internet-drafts/draft-denis-behave-v4v6ext
> hdr-00.txt
> =

> -- =

> R=E9mi Denis-Courmont
> Maemo Software, Nokia Devices R&D

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


From behave-bounces@ietf.org  Fri Oct 24 09:18:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 42EC728C21D;
	Fri, 24 Oct 2008 09:18:25 -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 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: Mark Townsley <townsley@cisco.com>, v4v6interim@ietf.org,
	46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Fri Oct 24 09:18:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F21728C22E;
	Fri, 24 Oct 2008 09:18:28 -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 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>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] [46translation] [v4v6interim] Proposal for new
	BEHAVEcharter
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Fri Oct 24 09:48:09 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEF2E3A6A65;
	Fri, 24 Oct 2008 09:48:09 -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 DB4A03A6A65
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 09:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.546
X-Spam-Level: 
X-Spam-Status: No, score=-6.546 tagged_above=-999 required=5 tests=[AWL=0.053, 
	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 XaEyUHKSy-rw for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 09:48:08 -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 0DF4028C218
	for <behave@ietf.org>; Fri, 24 Oct 2008 09:48:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="95786793"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 24 Oct 2008 16:49:30 +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 m9OGnUXu008269
	for <behave@ietf.org>; Fri, 24 Oct 2008 09:49:30 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9OGnTGB004033
	for <behave@ietf.org>; Fri, 24 Oct 2008 16:49:30 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 24 Oct 2008 09:49:28 -0700
Message-ID: <083f01c935f8$7b075750$9d6d6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack1+HrcR8Uh5DVUTImYImC13iD2yA==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=597; t=1224866970; x=1225730970;
	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:=20draft-wing-behave-learn-prefix-00 |Sender:=20;
	bh=OLcjCNYiOh9sz5WAHnFUYyEROihThTnYzjdWpmP5qnA=;
	b=l1ggf6Ncqw4GKW35ebBhBVaNMDPJhSPNGssN8zi/Cxx/2jOsCtitHrod7b
	AcNCUEo9/QNtGwmL3ThrQaNhrubpbLOmea+Xu1eZgpP6u67H1S1nqiGRH39u
	/ks0WsxVrZ;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [BEHAVE] draft-wing-behave-learn-prefix-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

(as individual contributor)

I just posted "Learning the Address Family Translator's IPv6 Prefix",
http://tools.ietf.org/html/draft-wing-behave-learn-prefix-00, abstract:

   In some IPv6/IPv4 translation scenarios it is necessary for an IPv6
   host to know the IPv6 prefix used by its address family translator.
   In some of the IPv6/IPv4 translation proposals, the prefix is not
   fixed; that is, the prefix is chosen by the network operator.  This
   specification provides several methods to learn the prefix and its
   length.

I hope this strawman proposal is helpful.

-d

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


From behave-bounces@ietf.org  Fri Oct 24 09:59:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E18813A6B49;
	Fri, 24 Oct 2008 09:59:53 -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 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]
X-Mailman-Approved-At: Fri, 24 Oct 2008 09:59:52 -0700
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>,
	Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] [v4v6interim] [46translation] Proposal for new
 BEHAVEcharter
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Fri Oct 24 10:11:58 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54A5E3A6B3D;
	Fri, 24 Oct 2008 10:11:58 -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 5ADC33A6B86
	for <behave@core3.amsl.com>; Fri, 24 Oct 2008 10:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.548
X-Spam-Level: 
X-Spam-Status: No, score=-6.548 tagged_above=-999 required=5 tests=[AWL=0.051, 
	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 3mk52g5+cY7M for <behave@core3.amsl.com>;
	Fri, 24 Oct 2008 10:11:56 -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 00D083A6A70
	for <behave@ietf.org>; Fri, 24 Oct 2008 10:11:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="110933113"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 24 Oct 2008 17:13:18 +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 m9OHDIdJ021865; 
	Fri, 24 Oct 2008 10:13:18 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OHDIVQ018016;
	Fri, 24 Oct 2008 17:13:18 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pierre.levis@orange-ftgroup.com>, <behave@ietf.org>
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
Date: Fri, 24 Oct 2008 10:13:17 -0700
Message-ID: <085f01c935fb$ceb45d00$9d6d6b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack1DZBIfgXcTQ//TVCUWnQhN9YVOAAzAofQAAhes7A=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1544; t=1224868398;
	x=1225732398; 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]=20TR=3A=20I-D=20Action=3Adraft
	-boucadair-port-range-00.txt |Sender:=20;
	bh=NvyinbyIDDiCxPws/JMLS8kbINMQye+xnWjZuc94rOQ=;
	b=DUPI/JmmdvWqruzewLJNdpTaFg5pnQpLmVjAmyNO9Dj4z3ybw0qO3QIhaX
	yznOYQWDUG3Yz7//LMTSLi9hGTg8LxOCarJIb5VlBF5ySQlRGDqHiBIhQETm
	J6J/gLfTFS;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> I would like to draw your attention on the following draft.
> 
> We (the authors) are looking forward to reading your comments.

This seems to be the core of the idea:

   3.2.  Basic Principles

   The major idea is to assign the same IP address to several end-
   users' devices (e.g.  Home Gateways (HGW) embedding NAT) and to
   constraint the (source) port numbers to be used by each HGW.  In
   addition to the assigned IP address to access IP connectivity
   services, an additional parameter, called Port Mask, is also assigned
   to the customer's device.  This mask indicates which Port Range is to
   be used by the customers' devices.

If that is the core of the idea, the idea seems similar to both Remi Despres's
draft-despres-sam-00.txt and to "A Better Approach than Carrier Grade NAT"
<https://mice.cs.columbia.edu/getTechreport.php?techreportID=560> (which I
understand is being converted into an I-D).

Can you compare your proposal with SAM?  And with the
Maennel/Bush/Cittadini/Bellovin proposal?


I have noticed two deficiencies with pre-allocating a set of ports to a
subscriber:  some techniques suffer from an inability to randomize ports
(reference draft-ietf-tsvwg-port-randomization), and also prevent the user
from utilizing more ports even if more ports are available (in the middle of
the night, for example) -- much as that same user could use more bandwidth
when other users are not using bandwidth.  Can you comment on these two issues
as they relate to your proposal?

-d



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


From behave-bounces@ietf.org  Fri Oct 24 15:44:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C01AF28C1AF;
	Fri, 24 Oct 2008 15:44:06 -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 B0BA328C1AB;
	Fri, 24 Oct 2008 15:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.125
X-Spam-Level: 
X-Spam-Status: No, score=-17.125 tagged_above=-999 required=5
	tests=[AWL=-0.126, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
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 L2CX9MpAuH4c; Fri, 24 Oct 2008 15:44:04 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id C037E28C1A9;
	Fri, 24 Oct 2008 15:44:04 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 713AA16AD60; Fri, 24 Oct 2008 15:45:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081024224523.713AA16AD60@bosco.isi.edu>
Date: Fri, 24 Oct 2008 15:45:23 -0700 (PDT)
Cc: behave@ietf.org, rfc-editor@rfc-editor.org
Subject: [BEHAVE] RFC 5389 on Session Traversal Utilities for NAT (STUN)
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


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

        
        RFC 5389

        Title:      Session Traversal Utilities for NAT 
                    (STUN) 
        Author:     J. Rosenberg, R. Mahy,
                    P. Matthews, D. Wing
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    jdrosen@cisco.com, 
                    rohan@ekabal.com, 
                    philip_matthews@magma.ca, 
                    dwing@cisco.com
        Pages:      51
        Characters: 125650
        Obsoletes:  RFC3489

        I-D Tag:    draft-ietf-behave-rfc3489bis-18.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5389.txt

Session Traversal Utilities for NAT (STUN) is a protocol that serves
as a tool for other protocols in dealing with Network Address
Translator (NAT) traversal.  It can be used by an endpoint to
determine the IP address and port allocated to it by a NAT.  It can
also be used to check connectivity between two endpoints, and as a
%keep-alive protocol to maintain NAT bindings.  STUN works with many
existing NATs, and does not require any special behavior from them.

STUN is not a NAT traversal solution by itself.  Rather, it is a tool
to be used in the context of a NAT traversal solution.  This is an
important change from the previous version of this specification (RFC
3489), which presented STUN as a complete solution.

This document obsoletes RFC 3489.  [STANDARDS TRACK]

This document is a product of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


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


From behave-bounces@ietf.org  Sat Oct 25 12:35:45 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 662633A6804;
	Sat, 25 Oct 2008 12:35:45 -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 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>
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org,
	46translation@employees.org
Subject: Re: [BEHAVE] NAT66 for PI [Re: [46translation] [v4v6interim]
 Proposal for new	BEHAVEcharter]
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-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
X19fX19fX19fX19fX19fX19fX19fXwpCZWhhdmUgbWFpbGluZyBsaXN0CkJlaGF2ZUBpZXRmLm9y
ZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQo=


From behave-bounces@ietf.org  Sat Oct 25 14:13:49 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B83FA3A6886;
	Sat, 25 Oct 2008 14:13:49 -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 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: [BEHAVE] [46translation] NAT66 for PI [Re: [v4v6interim]
	Proposal for new	BEHAVEcharter]
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Sun Oct 26 00:12:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 450173A68FB;
	Sun, 26 Oct 2008 00:12:30 -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 0EB713A67E7
	for <behave@core3.amsl.com>; Sun, 26 Oct 2008 00:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.253
X-Spam-Level: 
X-Spam-Status: No, score=-106.253 tagged_above=-999 required=5
	tests=[AWL=-0.254, BAYES_00=-2.599, J_CHICKENPOX_93=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 MSKOVezYWrsB for <behave@core3.amsl.com>;
	Sun, 26 Oct 2008 00:12:28 -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 20C643A68FB
	for <behave@ietf.org>; Sun, 26 Oct 2008 00:12:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,488,1220227200"; d="scan'208";a="23714274"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 26 Oct 2008 07:13:46 +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 m9Q7DkSF017677; 
	Sun, 26 Oct 2008 00:13:46 -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 m9Q7DiOX009922;
	Sun, 26 Oct 2008 07:13:45 GMT
From: Cullen Jennings <fluffy@cisco.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	Philip Matthews <philip_matthews@magma.ca>, Dan Wing <dwing@cisco.com>
In-Reply-To: <20081024224523.713AA16AD60@bosco.isi.edu>
Impp: xmpp:cullenfluffyjennings@jabber.org
References: <20081024224523.713AA16AD60@bosco.isi.edu>
Message-Id: <C785868F-470A-4723-B4C9-10180B942FD6@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 26 Oct 2008 01:13:39 -0600
X-Mailer: Apple Mail (2.929.2)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3232; t=1225005226;
	x=1225869226; 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:=20Congradulation=20on=20RFC=205389=20on=20Session
	=20Traversal=20Utilities=20for=20NAT=20(STUN) |Sender:=20;
	bh=9K3V/1zgeivwDGJp8ORlde/+Mo7cW5lqWf9SJ+8ljKc=;
	b=KhcftsMy4/Kzg9xdEUg0/OkPZRHWcBJh8NpjB5uU4pBaDsbmG/H8UP/bIx
	QP6f9O67j8F2qV9aVPj0YJwO/OVhR5vOvgkKsupozibgHA/iLR5+YHI1TsJg
	WdCqxrwx3xg2z1g3+IPObI/70DeD3MQsiLVsUiZyMhAK8ufLXD29s=;
Authentication-Results: sj-dkim-1; header.From=fluffy@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: Behave WG <behave@ietf.org>
Subject: [BEHAVE] Congradulation on RFC 5389 on Session Traversal Utilities
	for NAT (STUN)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


I just wanted to tell you and all the other folks that worked on STUN  
a big THANKS. I know it was a long road but I'm really glad to see  
this key part of the whole NAT traversal solution done and published.

Thanks, Cullen

On Oct 24, 2008, at 4:45 PM, rfc-editor@rfc-editor.org wrote:

>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 5389
>
>        Title:      Session Traversal Utilities for NAT
>                    (STUN)
>        Author:     J. Rosenberg, R. Mahy,
>                    P. Matthews, D. Wing
>        Status:     Standards Track
>        Date:       October 2008
>        Mailbox:    jdrosen@cisco.com,
>                    rohan@ekabal.com,
>                    philip_matthews@magma.ca,
>                    dwing@cisco.com
>        Pages:      51
>        Characters: 125650
>        Obsoletes:  RFC3489
>
>        I-D Tag:    draft-ietf-behave-rfc3489bis-18.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc5389.txt
>
> Session Traversal Utilities for NAT (STUN) is a protocol that serves
> as a tool for other protocols in dealing with Network Address
> Translator (NAT) traversal.  It can be used by an endpoint to
> determine the IP address and port allocated to it by a NAT.  It can
> also be used to check connectivity between two endpoints, and as a
> %keep-alive protocol to maintain NAT bindings.  STUN works with many
> existing NATs, and does not require any special behavior from them.
>
> STUN is not a NAT traversal solution by itself.  Rather, it is a tool
> to be used in the context of a NAT traversal solution.  This is an
> important change from the previous version of this specification (RFC
> 3489), which presented STUN as a complete solution.
>
> This document obsoletes RFC 3489.  [STANDARDS TRACK]
>
> This document is a product of the Behavior Engineering for Hindrance  
> Avoidance Working Group of the IETF.
>
> This is now a Proposed Standard Protocol.
>
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and  
> suggestions
> for improvements.  Please refer to the current edition of the Internet
> Official Protocol Standards (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html 
> .
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.   
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

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


From behave-bounces@ietf.org  Sun Oct 26 07:10:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9F0CB3A686C;
	Sun, 26 Oct 2008 07:10:43 -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 3E8C33A686C
	for <behave@core3.amsl.com>; Sun, 26 Oct 2008 07:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.785
X-Spam-Level: 
X-Spam-Status: No, score=-105.785 tagged_above=-999 required=5
	tests=[AWL=-0.619, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_RECV_IP_221000=1.433, 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 l161JuLaR4QG for <behave@core3.amsl.com>;
	Sun, 26 Oct 2008 07:10: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 55E453A67BD
	for <behave@ietf.org>; Sun, 26 Oct 2008 07:10:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,488,1220227200"; d="scan'208";a="96193592"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 26 Oct 2008 14:12:08 +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 m9QEC8aU026254
	for <behave@ietf.org>; Sun, 26 Oct 2008 07:12:08 -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 m9QEC8du022005
	for <behave@ietf.org>; Sun, 26 Oct 2008 14:12:08 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); 
	Sun, 26 Oct 2008 07:12:08 -0700
Received: from [221.0.175.29] ([10.70.231.95]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 07:12:07 -0700
Message-Id: <526E8F3D-AA05-44F5-9CE6-CDD7B6A1390E@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Behave WG <behave@ietf.org>
In-Reply-To: <20081026140911.67B983A6889@core3.amsl.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 26 Oct 2008 22:12:02 +0800
References: <20081026140911.67B983A6889@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Oct 2008 14:12:08.0016 (UTC)
	FILETIME=[D4A61D00:01C93774]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=791; t=1225030328; x=1225894328;
	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:=20draft-baker-behave-v4v6-framework-00=20
	|Sender:=20; bh=qsw8INhX1l7vvoBRsglXy5cIfsykYANifolRcyxxMK4=;
	b=GCowK/q6JzDkH3hf8P+I1hGOPIXWuFokuOOTSK0i78mDWkDfxJqnNCrafh
	qqBFhtLaj9tnpcmSkCR9L1azWv4MujTJz/8VL3F2ht3VEF8869FJTSalXyfD
	p0SGyXKe8P;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: [BEHAVE] draft-baker-behave-v4v6-framework-00
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I would invite comment on this

On Oct 26, 2008, at 10:09 PM, IETF I-D Submission Tool wrote:

>
> A new version of I-D, draft-baker-behave-v4v6-framework-00.txt has  
> been successfuly submitted by Fred Baker and posted to the IETF  
> repository.
>
> Filename:	 draft-baker-behave-v4v6-framework
> Revision:	 00
> Title:		 Framework for IPv4/IPv6 Translation
> Creation_date:	 2008-10-26
> WG ID:		 Independent Submission
> Number_of_pages: 33
>
> Abstract:
> This note describes a framework for IPv4/IPv6 translation.  This is
> in the context of replacing NAT-PT, which was deprecated by RFC 4966,
> and to enable networks to have IPv4 and IPv6 coexist in a somewhat
> rational manner while transitioning to an IPv6 network.
>
>
>
> The IETF Secretariat.
>
>

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


From behave-bounces@ietf.org  Sun Oct 26 07:11:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE3BC3A6942;
	Sun, 26 Oct 2008 07:11:02 -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 E409F3A687E
	for <behave@core3.amsl.com>; Sun, 26 Oct 2008 07:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.776
X-Spam-Level: 
X-Spam-Status: No, score=-105.776 tagged_above=-999 required=5
	tests=[AWL=-0.610, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_RECV_IP_221000=1.433, 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 qDo0f5TZ0hbq for <behave@core3.amsl.com>;
	Sun, 26 Oct 2008 07:11:01 -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 0D8A93A6942
	for <behave@ietf.org>; Sun, 26 Oct 2008 07:11:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,488,1220227200"; d="scan'208";a="98814347"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 26 Oct 2008 14:12:28 +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 m9QECSus019061; 
	Sun, 26 Oct 2008 07:12:28 -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 m9QECSLF022065;
	Sun, 26 Oct 2008 14:12: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); 
	Sun, 26 Oct 2008 07:12:27 -0700
Received: from [221.0.175.29] ([10.70.231.95]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 07:12:25 -0700
Message-Id: <14699B93-EC21-43D8-9E2A-7159F38379C8@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Behave WG <behave@ietf.org>
In-Reply-To: <20081026140919.DA1AC3A691A@core3.amsl.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 26 Oct 2008 22:12:22 +0800
References: <20081026140919.DA1AC3A691A@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 26 Oct 2008 14:12:25.0703 (UTC)
	FILETIME=[DF30EF70:01C93774]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2596; t=1225030348;
	x=1225894348; 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=20New=20Version=20Notification=20for=20=2
	0draft-baker-behave-v4v6-translation-00=20 |Sender:=20;
	bh=Tt9u2SlkmqGJp9Vjs1wvh4xew7jp15ryAKNQv8Z6YLs=;
	b=FgTPq4HSvGBIrlSIcfI/D6mb9TecPRcNTPave5yJIcaDFqzcIwTLW76H4C
	NkjLrQcy7eDXkFPqlTBXLc1sG4eNlRbln2PR4a9/M56Ub62lgJ8O8j93ibkq
	9xGFGPhdvbAOF7dgtHTf1k7Gbs16st+g+iW/VYuQRH1TSrZ7aEez0=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: congxiao@cernet.edu.cn, xing@cernet.edu.cn
Subject: Re: [BEHAVE] New Version Notification for
	draft-baker-behave-v4v6-translation-00
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I would invite comment on this.

On Oct 26, 2008, at 10:09 PM, IETF I-D Submission Tool wrote:

>
> A new version of I-D, draft-baker-behave-v4v6-translation-00.txt has  
> been successfuly submitted by Fred Baker and posted to the IETF  
> repository.
>
> Filename:	 draft-baker-behave-v4v6-translation
> Revision:	 00
> Title:		 IP/ICMP Translation Algorithm
> Creation_date:	 2008-10-26
> WG ID:		 Independent Submission
> Number_of_pages: 30
>
> Abstract:
> This document specifies an update to the Stateless IP/ICMP
> Translation Algorithm (SIIT) described in RFC 2765.  The algorithm
> translates between IPv4 and IPv6 packet headers (including ICMP
> headers).
>
> This specification addresses both a stateful and a stateless mode.
> In the stateful mode, translation state is maintained between IPv4
> address/transport/port tuples and IPv6 address/transport/port tuples,
> enabling IPv6 systems to open sessions with IPv4 systems.  In the
> stateless mode, translation information is carried in the address
> itself, permitting both IPv4->IPv6 and IPv6->IPv4 session
> establishment with neither state nor configuration in the translator.
> The choice of operational mode is made by the operator deploying the
> network and is critical to the operation of the applications using
> it.
>
> Significant issues exist in the stateful mode that are not addressed
> in this document, related to the maintenance of the translation
> tables.  This document confines itself to the actual translation.
>
> Acknowledgement of previous work
>
> This document is a product of the 2008-2009 effort to define a
> replacement for NAT-PT.  It is an update to and directly derivative
> from Erik Nordmark's [RFC2765], which similarly provides both
> stateless and stateful translation between IPv4 [RFC0791] and IPv6
> [RFC2460], and between ICMPv4 [RFC0792] and ICMPv6 [RFC4443].  The
> original document was a product of the NGTRANS working group.  Some
> text had been extracted from an old Internet Draft titled "IPAE: The
> SIPP Interoperability and Transition Mechanism" authored by R.
> Gilligan, E. Nordmark, and B. Hinden.
>
> The changes in this document reflect five components:
>
> 1.  Updating references
>
> 2.  Redescribing the network model to map to present and projected
>
> usage
>
> 3.  Moving the address format to the framework document, to
>
> coordinate with other drafts on the topic
>
> 4.  Some changes in ICMP.
>
> 5.  Description of both stateful and stateless operation.
>
>
>
> The IETF Secretariat.
>
>

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


From behave-bounces@ietf.org  Sun Oct 26 15:17:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B7893A683E;
	Sun, 26 Oct 2008 15:17:08 -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 32E693A676A
	for <behave@core3.amsl.com>; Sun, 26 Oct 2008 15:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.222
X-Spam-Level: *
X-Spam-Status: No, score=1.222 tagged_above=-999 required=5
	tests=[FM_FORGED_GMAIL=0.622, J_CHICKENPOX_93=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 LFKN2egyhpFj for <behave@core3.amsl.com>;
	Sun, 26 Oct 2008 15:17:06 -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 3DDCA3A683E
	for <behave@ietf.org>; Sun, 26 Oct 2008 15:17:06 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id n4so1025022wag.5
	for <behave@ietf.org>; Sun, 26 Oct 2008 15:17:04 -0700 (PDT)
Received: by 10.115.73.20 with SMTP id a20mr4549420wal.32.1225059424316;
	Sun, 26 Oct 2008 15:17:04 -0700 (PDT)
Received: by 10.114.92.9 with HTTP; Sun, 26 Oct 2008 15:17:04 -0700 (PDT)
Message-ID: <bc023dcd0810261517o6e35b0ddo92144cb8e8424bc7@mail.gmail.com>
Date: Sun, 26 Oct 2008 18:17:04 -0400
From: "Bruce Lowekamp" <bbl@lowekamp.net>
To: "Cullen Jennings" <fluffy@cisco.com>
In-Reply-To: <C785868F-470A-4723-B4C9-10180B942FD6@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20081024224523.713AA16AD60@bosco.isi.edu>
	<C785868F-470A-4723-B4C9-10180B942FD6@cisco.com>
Cc: Rohan Mahy <rohan@ekabal.com>, Dan Wing <dwing@cisco.com>,
	Behave WG <behave@ietf.org>, Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [BEHAVE] Congradulation on RFC 5389 on Session Traversal
	Utilities for NAT (STUN)
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Echoing the congratulations and thanks for the work.

Would have sent this out earlier, but I think we've all been too busy
updating all the drafts that reference 5389!!!

Bruce


On Sun, Oct 26, 2008 at 3:13 AM, Cullen Jennings <fluffy@cisco.com> wrote:
>
> I just wanted to tell you and all the other folks that worked on STUN a big
> THANKS. I know it was a long road but I'm really glad to see this key part
> of the whole NAT traversal solution done and published.
>
> Thanks, Cullen
>
> On Oct 24, 2008, at 4:45 PM, rfc-editor@rfc-editor.org wrote:
>
>>
>> A new Request for Comments is now available in online RFC libraries.
>>
>>
>>       RFC 5389
>>
>>       Title:      Session Traversal Utilities for NAT
>>                   (STUN)
>>       Author:     J. Rosenberg, R. Mahy,
>>                   P. Matthews, D. Wing
>>       Status:     Standards Track
>>       Date:       October 2008
>>       Mailbox:    jdrosen@cisco.com,
>>                   rohan@ekabal.com,
>>                   philip_matthews@magma.ca,
>>                   dwing@cisco.com
>>       Pages:      51
>>       Characters: 125650
>>       Obsoletes:  RFC3489
>>
>>       I-D Tag:    draft-ietf-behave-rfc3489bis-18.txt
>>
>>       URL:        http://www.rfc-editor.org/rfc/rfc5389.txt
>>
>> Session Traversal Utilities for NAT (STUN) is a protocol that serves
>> as a tool for other protocols in dealing with Network Address
>> Translator (NAT) traversal.  It can be used by an endpoint to
>> determine the IP address and port allocated to it by a NAT.  It can
>> also be used to check connectivity between two endpoints, and as a
>> %keep-alive protocol to maintain NAT bindings.  STUN works with many
>> existing NATs, and does not require any special behavior from them.
>>
>> STUN is not a NAT traversal solution by itself.  Rather, it is a tool
>> to be used in the context of a NAT traversal solution.  This is an
>> important change from the previous version of this specification (RFC
>> 3489), which presented STUN as a complete solution.
>>
>> This document obsoletes RFC 3489.  [STANDARDS TRACK]
>>
>> This document is a product of the Behavior Engineering for Hindrance
>> Avoidance Working Group of the IETF.
>>
>> This is now a Proposed Standard Protocol.
>>
>> STANDARDS TRACK: This document specifies an Internet standards track
>> protocol for the Internet community,and requests discussion and
>> suggestions
>> for improvements.  Please refer to the current edition of the Internet
>> Official Protocol Standards (STD 1) for the standardization state and
>> status of this protocol.  Distribution of this memo is unlimited.
>>
>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>> To subscribe or unsubscribe, see
>>  http://www.ietf.org/mailman/listinfo/ietf-announce
>>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>
>> For searching the RFC series, see
>> http://www.rfc-editor.org/rfcsearch.html.
>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>>
>> Requests for special distribution should be addressed to either the
>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for
>> unlimited distribution.
>>
>>
>> The RFC Editor Team
>> USC/Information Sciences Institute
>>
>>
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 27 00:29:50 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FAE428C14A;
	Mon, 27 Oct 2008 00:29:50 -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 0267E28C14A
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 00:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.651
X-Spam-Level: *
X-Spam-Status: No, score=1.651 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, MANGLED_YOUR=2.3,
	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 tnB0Ln0zwvDe for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 00:29:48 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id ACA1B28C147
	for <behave@ietf.org>; Mon, 27 Oct 2008 00:29:47 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:29:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 08:29:24 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AACD6E3@ftrdmel1>
In-Reply-To: <200810241644.22542.remi.denis-courmont@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
Thread-Index: Ack13uO3rVSZPbx/SN6c9cRHwePnJQCICwaw
From: <pierre.levis@orange-ftgroup.com>
To: <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 07:29:44.0315 (UTC)
	FILETIME=[C84B74B0:01C93805]
Cc: jean-luc.grimault@orange-ftgroup.com, mohamed.boucadair@orange-ftgroup.com,
	alain.villefranque@orange-ftgroup.com
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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

 Thank you R=E9mi for your questions, please find my answers in the text (>=
>PL):

-----Message d'origine-----
De : R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

Envoy=E9 : vendredi 24 octobre 2008 15:44
=C0 : behave@ietf.org; VILLEFRANQUE Alain RD-CORE-CAE
Cc : LEVIS Pierre RD-CORE-CAE; BOUCADAIR Mohamed RD-CORE-CAE; jean-luc.grim=
ault@orange-ftgroup.com
Objet : Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt


	Hello,

On Friday 24 October 2008 16:16:30 ext pierre.levis@orange-ftgroup.com, you
wrote:
> I would like to draw your attention on the following draft.
>
> We (the authors) are looking forward to reading your comments.

Section 5.4 is a bit unclear to me. It seems like you are referring to the =
inability of CG-NATs (or any nested NAT scenario for that matter) to handle=
 UPnP IGD, NAT-PMP and/or manual port forwarding. That's true, and that is =
a problem for certain applications.

However, this seems to assume that all P2P applications rely on this. As fa=
r as I know, there are a bunch of P2P applications using "bilateral" NAT tr=
aversal, for instance VoIP clients or Teredo-based P2P file sharing apps.
>>PL: You're right, we'll make it clearer


More importantly, some questions (sorry if I missed the explanation in the
document) as to how PRR works in the following cases:
* a contemporary CPE is attached to a PRR, that does not implement the DHCP=
 or PPP PRR extension?
>>PL: Then it cannot use the PRR system, however it is not impacted by the =
presence of the PRR. Your question raises the important issue of who is goi=
ng to have a shared address and who is going to have a unique public addres=
s. I guess the answer will depend on the ISP, its level of address shortage=
, and its policy.

* a plain IPv4 host is attached directly to a PRR (no CPE at all)?
>>PL: this case it not described in the draft, but the mechanism could easi=
ly be applied directly to terminals (it surely makes sense for mobile phone=
s)

* shared-medium (non point-to-point) access networks, such as DOCSIS, which=
 uses ARP if I'm not mistaken?
>>PL: The solution is compatible with shared-medium as Ethernet; this point=
 is treated in the draft (description of the mock-up in =A7 4.3)with the us=
e of a private address:
"The PRR proceeds to an ARP (Address Resolution Protocol) resolution (if no=
t already achieved previously) and matches the [private addr EXT CPE-x] wit=
h the MAC (Media Access Control) address of EXT CPE x;"

 =


Regards,

>>PL:
Regards,

Pierre

--
R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Mon Oct 27 00:57:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE6693A6855;
	Mon, 27 Oct 2008 00:57:41 -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 966003A6850
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 00:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.109
X-Spam-Level: **
X-Spam-Status: No, score=2.109 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457]
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 4LTdCPCw+Q9S for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 00:57:39 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36])
	by core3.amsl.com (Postfix) with ESMTP id 603663A677E
	for <behave@ietf.org>; Mon, 27 Oct 2008 00:57:39 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp6-g19.free.fr (Postfix) with ESMTP id 21C1519736;
	Mon, 27 Oct 2008 08:57:38 +0100 (CET)
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 3CFE5197B0;
	Mon, 27 Oct 2008 08:57:37 +0100 (CET)
Message-ID: <4905741B.6070306@free.fr>
Date: Mon, 27 Oct 2008 08:56:11 +0100
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: Dan Wing <dwing@cisco.com>
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
	<085f01c935fb$ceb45d00$9d6d6b80@cisco.com>
In-Reply-To: <085f01c935fb$ceb45d00$9d6d6b80@cisco.com>
Cc: behave@ietf.org, pierre.levis@orange-ftgroup.com
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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: multipart/mixed; boundary="===============1848005214=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============1848005214==
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">
Dan,<br>
<br>
IPv4 address extension based on port ranges is not only common to :<br>
- My "Stateless Address mapping" (SAM)<br>
- Randy Bush's "A+P",<br>
- Mohamed Boucadair's "Port Provided CPEs" (which contains useful first
hand experience,&nbsp; acquired with real tests)<br>
But also to:<br>
- Gabor Bajko &amp; Teemu Savolainen's "Port-restricted IPv4 address
assignment".<br>
- IVI where it is, in my understanding of the "port multiplexing"
section, a possible extension.<br>
<br>
I find this very encouraging.<br>
<br>
I hope that meeting in Minneapolis will help clarifying common grounds
and possible convergence.<br>
If not in Behave, or in any scheduled meeting, I would like to propose,
when we are there,
a place and a time for an informal meeting, like the one we had in
Dublin after the APBP presentation. <br>
Anyone interested in participating to this convergence work is welcome
to be
identified.<br>
<br>
Regards,<br>
<br>
RD<br>
<br>
<br>
Dan Wing&nbsp;&nbsp; (m/j/a) 10/24/08 7:13 PM:
<blockquote cite="mid:085f01c935fb$ceb45d00$9d6d6b80@cisco.com"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">I would like to draw your attention on the following draft.

We (the authors) are looking forward to reading your comments.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
This seems to be the core of the idea:

   3.2.  Basic Principles

   The major idea is to assign the same IP address to several end-
   users' devices (e.g.  Home Gateways (HGW) embedding NAT) and to
   constraint the (source) port numbers to be used by each HGW.  In
   addition to the assigned IP address to access IP connectivity
   services, an additional parameter, called Port Mask, is also assigned
   to the customer's device.  This mask indicates which Port Range is to
   be used by the customers' devices.

If that is the core of the idea, the idea seems similar to both Remi Despres's
draft-despres-sam-00.txt and to "A Better Approach than Carrier Grade NAT"
<a class="moz-txt-link-rfc2396E"
 href="https://mice.cs.columbia.edu/getTechreport.php?techreportID=560">&lt;https://mice.cs.columbia.edu/getTechreport.php?techreportID=560&gt;</a> (which I
understand is being converted into an I-D).

Can you compare your proposal with SAM?  And with the
Maennel/Bush/Cittadini/Bellovin proposal?


I have noticed two deficiencies with pre-allocating a set of ports to a
subscriber:  some techniques suffer from an inability to randomize ports
(reference draft-ietf-tsvwg-port-randomization), and also prevent the user
from utilizing more ports even if more ports are available (in the middle of
the night, for example) -- much as that same user could use more bandwidth
when other users are not using bandwidth.  Can you comment on these two issues
as they relate to your proposal?

-d



_______________________________________________
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>
<br>
</body>
</html>

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

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

--===============1848005214==--


From behave-bounces@ietf.org  Mon Oct 27 01:40:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D27153A6851;
	Mon, 27 Oct 2008 01:40:55 -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 456623A689B
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 01:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.016
X-Spam-Level: **
X-Spam-Status: No, score=2.016 tagged_above=-999 required=5 tests=[AWL=0.093, 
	BAYES_40=-0.185, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457]
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 lb4ikTR39GBF for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 01:40:53 -0700 (PDT)
Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27])
	by core3.amsl.com (Postfix) with ESMTP id 4268F3A68CC
	for <behave@ietf.org>; Mon, 27 Oct 2008 01:40:53 -0700 (PDT)
Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp1-g19.free.fr (Postfix) with ESMTP id C70E21AB325;
	Mon, 27 Oct 2008 09:40:51 +0100 (CET)
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 601F91AB362;
	Mon, 27 Oct 2008 09:40:51 +0100 (CET)
Message-ID: <49057E3D.5090401@free.fr>
Date: Mon, 27 Oct 2008 09:39:25 +0100
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: pierre.levis@orange-ftgroup.com
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
In-Reply-To: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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: multipart/mixed; boundary="===============2024446590=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============2024446590==
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">
Hi Pierre,<br>
<br>
I find the draft most interesting, in particular the real experiment it
describes .<br>
<br>
In sec 4.4&nbsp; it says :"For one P2P (Peer-to-Peer) application tested, we
found that two&nbsp; peers each behind a CPE sharing the same public address
cannot&nbsp; download a SAME file from a source peer."<br>
- Is there a problem in telling&nbsp; which application this is?<br>
- Do we know if this application works (for the same file) across NATs,
and if yes how?<br>
<br>
Regards,<br>
<br>
RD<br>
<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:pierre.levis@orange-ftgroup.com">pierre.levis@orange-ftgroup.com</a>&nbsp;&nbsp; (m/j/a) 10/24/08 3:16 PM:
<blockquote cite="mid:D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1"
 type="cite">
  <pre wrap="">Hi all,

I would like to draw your attention on the following draft.

We (the authors) are looking forward to reading your comments.


Regards


Pierre



-----Message d'origine-----
De : <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce-bounces@ietf.org">i-d-announce-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:i-d-announce-bounces@ietf.org">mailto:i-d-announce-bounces@ietf.org</a>] De la part de <a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>
Envoy&eacute; : jeudi 23 octobre 2008 14:45
&Agrave; : <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a>
Objet : I-D Action:draft-boucadair-port-range-00.txt 

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Provider-Provisioned CPE: IPv4 Connectivity Access in the context of IPv4 address exhaustion
	Author(s)       : M. Boucadair, et al.
	Filename        : draft-boucadair-port-range-00.txt
	Pages           : 33
	Date            : 2008-10-23

This memo proposes a solution, based on fractional addresses, to face the IPv4 public address exhaustion.  It details the solution and presents a mock-up implementation, with the results of tests that validate the concept.  Finally, it makes a comparison with the alternative Carrier-Grade NAT (CG-NAT) solutions.

A URL for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt">http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt</a>

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>

Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
  </pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
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>
<br>
</body>
</html>

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

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

--===============2024446590==--


From behave-bounces@ietf.org  Mon Oct 27 05:54:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6287E3A6A99;
	Mon, 27 Oct 2008 05:54:46 -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 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: [BEHAVE] Status of IPv4-IPv6 Coexistence Work
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-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

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


From behave-bounces@ietf.org  Mon Oct 27 06:23:47 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DE223A6AD5;
	Mon, 27 Oct 2008 06:23:47 -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 A3D6D3A6AC0
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 06:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level: 
X-Spam-Status: No, score=0.501 tagged_above=-999 required=5 tests=[AWL=1.150, 
	BAYES_50=0.001, HELO_EQ_FR=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 CHV6HBqfrhfC for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 06:23:45 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id F2DF13A6AD0
	for <behave@ietf.org>; Mon, 27 Oct 2008 06:23:44 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:23:15 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 14:23:06 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB01EED@ftrdmel1>
In-Reply-To: <085f01c935fb$ceb45d00$9d6d6b80@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
Thread-Index: Ack1DZBIfgXcTQ//TVCUWnQhN9YVOAAzAofQAAhes7AAhvrioA==
From: <pierre.levis@orange-ftgroup.com>
To: <dwing@cisco.com>,
	<behave@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 13:23:15.0637 (UTC)
	FILETIME=[2B3A5650:01C93837]
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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

Hi Dan,

Please find my answers in the text (>>PL): =


-----Message d'origine-----
De : Dan Wing [mailto:dwing@cisco.com] =

Envoy=E9 : vendredi 24 octobre 2008 19:13
=C0 : LEVIS Pierre RD-CORE-CAE; behave@ietf.org
Objet : RE: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt

> I would like to draw your attention on the following draft.
> =

> We (the authors) are looking forward to reading your comments.

This seems to be the core of the idea:

   3.2.  Basic Principles

   The major idea is to assign the same IP address to several end-
   users' devices (e.g.  Home Gateways (HGW) embedding NAT) and to
   constraint the (source) port numbers to be used by each HGW.  In
   addition to the assigned IP address to access IP connectivity
   services, an additional parameter, called Port Mask, is also assigned
   to the customer's device.  This mask indicates which Port Range is to
   be used by the customers' devices.

If that is the core of the idea, the idea seems similar to both Remi Despre=
s's draft-despres-sam-00.txt and to "A Better Approach than Carrier Grade N=
AT"
<https://mice.cs.columbia.edu/getTechreport.php?techreportID=3D560> (which =
I understand is being converted into an I-D).

Can you compare your proposal with SAM?  And with the Maennel/Bush/Cittadin=
i/Bellovin proposal?

>>PL: As R=E9mi Despr=E9s pointed out this proposal is one among several pr=
oposals that are all based on the idea of allocating a restricted set of po=
rts. In this context, this draft is an effort to address the recommendation=
 in <draft-arkko-townsley-coexistence-00> to develop new guidelines and spe=
cifications for some already known solutions.
What we more specifically bring is:
-Show the involvement of an ISP
-Present an early implementation
-Extend the notion of port range to non-contiguous values with the use of p=
ort range mask
-Propose a mechanism where the port allocation is handled by a DHCP proxy i=
n order to let the already existing DHCP servers unaware

I have noticed two deficiencies with pre-allocating a set of ports to a
subscriber:  some techniques suffer from an inability to randomize ports (r=
eference draft-ietf-tsvwg-port-randomization), and also prevent the user fr=
om utilizing more ports even if more ports are available (in the middle of =
the night, for example) -- much as that same user could use more bandwidth =
when other users are not using bandwidth.  Can you comment on these two iss=
ues as they relate to your proposal?

>>PL: Right, the idea of pre-allocating a set of ports seems contrary to th=
e idea of randomizing the port choice. Intuitively, the smaller the port ra=
nge is, the more predictable the port choice is. But this needs to be quant=
ified.
 =

As for the efficiency of port range allocation vs pure dynamic port allocat=
ion, this can be mitigated by:
-A more elaborated and dynamic way to split the port space is possible but =
this would bring much (too much?) complexity.
-A key parameter is the factor by which you want to multiply your address s=
pace. Maybe this factor is only some units (less than 10). The purpose of t=
his kind of mechanism (port range, CG-NAT, or whatever) is "only" (I know t=
his is not straightforward!) to survive until IPv6 is deployed enough that =
the use of IPv4 public addresses begins to decrease. Then the breadth (seve=
ral thousands) of the port space can be sufficient to accommodate to almost=
 any use cases (x8; ~8000 ports available).

Pierre
 =

-d



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


From behave-bounces@ietf.org  Mon Oct 27 07:14:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9ADD93A6B54;
	Mon, 27 Oct 2008 07:14:30 -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 AA5D83A6B25
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 07:14:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=1.875, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	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 lYvMEUHoLhj3 for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 07:14:25 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id F2B033A6B49
	for <behave@ietf.org>; Mon, 27 Oct 2008 07:14:24 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 15:14:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 15:14:20 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1>
In-Reply-To: <49057E3D.5090401@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QA
From: <pierre.levis@orange-ftgroup.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 14:14:22.0540 (UTC)
	FILETIME=[4F3E98C0:01C9383E]
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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: multipart/mixed; boundary="===============0929008747=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0929008747==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9383E.4F3B70E5"

This is a multi-part message in MIME format.

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

Hi R=E9mi,
=20
Thank you for your careful reading.
=20
This is one of the most commonly used p2p application!
More seriously, we're bound to have the same issue as soon as we do =
address sharing, no matter the mechanism. So, I would say that it should =
not work accross a Carrier Grade NAT.
=20
=20
Regards,
=20
=20
Pierre

________________________________

De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 27 octobre 2008 09:39
=C0 : LEVIS Pierre RD-CORE-CAE
Cc : behave@ietf.org
Objet : Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt


Hi Pierre,

I find the draft most interesting, in particular the real experiment it =
describes .

In sec 4.4  it says :"For one P2P (Peer-to-Peer) application tested, we =
found that two  peers each behind a CPE sharing the same public address =
cannot  download a SAME file from a source peer."
- Is there a problem in telling  which application this is?
- Do we know if this application works (for the same file) across NATs, =
and if yes how?

Regards,

RD




pierre.levis@orange-ftgroup.com   (m/j/a) 10/24/08 3:16 PM:=20

	Hi all,
=09
	I would like to draw your attention on the following draft.
=09
	We (the authors) are looking forward to reading your comments.
=09
=09
	Regards
=09
=09
	Pierre
=09
=09
=09
	-----Message d'origine-----
	De : i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org] De la part de =
Internet-Drafts@ietf.org
	Envoy=E9 : jeudi 23 octobre 2008 14:45
	=C0 : i-d-announce@ietf.org
	Objet : I-D Action:draft-boucadair-port-range-00.txt=20
=09
	A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
=09
		Title           : Provider-Provisioned CPE: IPv4 Connectivity Access =
in the context of IPv4 address exhaustion
		Author(s)       : M. Boucadair, et al.
		Filename        : draft-boucadair-port-range-00.txt
		Pages           : 33
		Date            : 2008-10-23
=09
	This memo proposes a solution, based on fractional addresses, to face =
the IPv4 public address exhaustion.  It details the solution and =
presents a mock-up implementation, with the results of tests that =
validate the concept.  Finally, it makes a comparison with the =
alternative Carrier-Grade NAT (CG-NAT) solutions.
=09
	A URL for this Internet-Draft is:
	http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt
=09
	Internet-Drafts are also available by anonymous FTP at:
	ftp://ftp.ietf.org/internet-drafts/
=09
	Below is the data which will enable a MIME compliant mail reader =
implementation to automatically retrieve the ASCII version of the =
Internet-Draft.
	 =20
=09
________________________________


	_______________________________________________
	Behave mailing list
	Behave@ietf.org
	https://www.ietf.org/mailman/listinfo/behave
	 =20



------_=_NextPart_001_01C9383E.4F3B70E5
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi R=E9mi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thank you for your careful =
reading.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>This is one of the most commonly used p2p=20
application!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>More seriously, we're bound to have the same =
issue as soon=20
as we do address sharing, no matter the mechanism. So, I would say that =
it=20
should not work accross a Carrier Grade NAT.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D227334513-27102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Pierre</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> R=E9mi Despr=E9s=20
[mailto:remi.despres@free.fr] <BR><B>Envoy=E9&nbsp;:</B> lundi 27 =
octobre 2008=20
09:39<BR><B>=C0&nbsp;:</B> LEVIS Pierre RD-CORE-CAE<BR><B>Cc&nbsp;:</B>=20
behave@ietf.org<BR><B>Objet&nbsp;:</B> Re: [BEHAVE] TR: I-D=20
Action:draft-boucadair-port-range-00.txt<BR></FONT><BR></DIV>
<DIV></DIV>Hi Pierre,<BR><BR>I find the draft most interesting, in =
particular=20
the real experiment it describes .<BR><BR>In sec 4.4&nbsp; it says :"For =
one P2P=20
(Peer-to-Peer) application tested, we found that two&nbsp; peers each =
behind a=20
CPE sharing the same public address cannot&nbsp; download a SAME file =
from a=20
source peer."<BR>- Is there a problem in telling&nbsp; which application =
this=20
is?<BR>- Do we know if this application works (for the same file) across =
NATs,=20
and if yes how?<BR><BR>Regards,<BR><BR>RD<BR><BR><BR><BR><BR><A=20
class=3Dmoz-txt-link-abbreviated=20
href=3D"mailto:pierre.levis@orange-ftgroup.com">pierre.levis@orange-ftgro=
up.com</A>&nbsp;&nbsp;=20
(m/j/a) 10/24/08 3:16 PM:=20
<BLOCKQUOTE cite=3Dmid:D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1 =

type=3D"cite"><PRE wrap=3D"">Hi all,

I would like to draw your attention on the following draft.

We (the authors) are looking forward to reading your comments.


Regards


Pierre



-----Message d'origine-----
De : <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:i-d-announce-bounces@ietf.org">i-d-announce-bounces@ietf.o=
rg</A> [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:i-d-announce-bounces@ietf.org">mailto:i-d-announce-bounces=
@ietf.org</A>] De la part de <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</A>
Envoy=E9 : jeudi 23 octobre 2008 14:45
=C0 : <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</A>
Objet : I-D Action:draft-boucadair-port-range-00.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts =
directories.

	Title           : Provider-Provisioned CPE: IPv4 Connectivity Access in =
the context of IPv4 address exhaustion
	Author(s)       : M. Boucadair, et al.
	Filename        : draft-boucadair-port-range-00.txt
	Pages           : 33
	Date            : 2008-10-23

This memo proposes a solution, based on fractional addresses, to face =
the IPv4 public address exhaustion.  It details the solution and =
presents a mock-up implementation, with the results of tests that =
validate the concept.  Finally, it makes a comparison with the =
alternative Carrier-Grade NAT (CG-NAT) solutions.

A URL for this Internet-Draft is:
<A class=3Dmoz-txt-link-freetext =
href=3D"http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00=
.txt">http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.t=
xt</A>

Internet-Drafts are also available by anonymous FTP at:
<A class=3Dmoz-txt-link-freetext =
href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-=
drafts/</A>

Below is the data which will enable a MIME compliant mail reader =
implementation to automatically retrieve the ASCII version of the =
Internet-Draft.
  </PRE><PRE wrap=3D""><HR width=3D"90%" SIZE=3D4>
_______________________________________________
Behave mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:Behave@ietf.org">Behave@ietf.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www.ietf.org/mailman/listinfo/behave">https://www.ietf.or=
g/mailman/listinfo/behave</A>
  </PRE></BLOCKQUOTE><BR></BODY></HTML>

------_=_NextPart_001_01C9383E.4F3B70E5--

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

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

--===============0929008747==--


From behave-bounces@ietf.org  Mon Oct 27 07:32:33 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 744EC3A6AD9;
	Mon, 27 Oct 2008 07:32:33 -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 712813A6A4A
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 07:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.762
X-Spam-Level: 
X-Spam-Status: No, score=0.762 tagged_above=-999 required=5 tests=[AWL=1.254, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457]
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 0DiQiLMKrv+Z for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 07:32:28 -0700 (PDT)
Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35])
	by core3.amsl.com (Postfix) with ESMTP id A71933A6AD9
	for <behave@ietf.org>; Mon, 27 Oct 2008 07:32:28 -0700 (PDT)
Received: from smtp5-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp5-g19.free.fr (Postfix) with ESMTP id 7141A3EA341;
	Mon, 27 Oct 2008 15:32:27 +0100 (CET)
Received: from ordinateur-de-remi-despres.local
	(per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144])
	by smtp5-g19.free.fr (Postfix) with ESMTP id 357993EA2A3;
	Mon, 27 Oct 2008 15:32:27 +0100 (CET)
Message-ID: <4905D0A4.2080005@free.fr>
Date: Mon, 27 Oct 2008 15:31:00 +0100
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: pierre.levis@orange-ftgroup.com
References: <D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1>
In-Reply-To: <D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1>
Cc: behave@ietf.org
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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: multipart/mixed; boundary="===============1642829896=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

--===============1642829896==
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">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:pierre.levis@orange-ftgroup.com">pierre.levis@orange-ftgroup.com</a>&nbsp;&nbsp; (m/j/a) 10/27/08 3:14 PM:
<blockquote cite="mid:D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1"
 type="cite">
  <meta http-equiv="Context-Type"
 content="text/html; charset=iso-8859-1">
  <div><span>&nbsp;we're bound to have the same issue as soon as we do
address sharing, no matter the mechanism. So, I would say that it
should not work accross a Carrier Grade NAT.</span></div>
</blockquote>
And not more across "CPE" NATs that have only one IPv4 address to
share, right?<br>
(This one instance where working in IPv6, if possible, is cleaner,
simpler, safer....)<br>
RD<br>
<br>
<br>
<b>De&nbsp;:</b> R&eacute;mi Despr&eacute;s [<a class="moz-txt-link-freetext" href="mailto:remi.despres@free.fr">mailto:remi.despres@free.fr</a>] <br>
<b>Envoy&eacute;&nbsp;:</b> lundi 27 octobre 2008 09:39
<blockquote cite="mid:D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1"
 type="cite">
  <div><span> </span></div>
In sec 4.4&nbsp; it says :"For one P2P (Peer-to-Peer) application tested, we
found that two&nbsp; peers each behind a CPE sharing the same public address
cannot&nbsp; download a SAME file from a source peer."<br>
  <br>
- Do we know if this application works (for the same file) across NATs,
and if yes how?<br>
</blockquote>
<br>
</body>
</html>

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

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

--===============1642829896==--


From behave-bounces@ietf.org  Mon Oct 27 07:40:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBB1A3A6B5B;
	Mon, 27 Oct 2008 07:40:30 -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 0FA973A6AF8
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 07:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[AWL=1.250, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	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 a7E-tR9av8hS for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 07:40:29 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id 83A463A6B5B
	for <behave@ietf.org>; Mon, 27 Oct 2008 07:40:28 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 15:40:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 15:40:25 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB02025@ftrdmel1>
In-Reply-To: <4905D0A4.2080005@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
Thread-Index: Ack4QO2HNZ2PfZSgQeC1Ke8ZigD4YQAAMZPQ
From: <pierre.levis@orange-ftgroup.com>
To: <remi.despres@free.fr>
X-OriginalArrivalTime: 27 Oct 2008 14:40:27.0326 (UTC)
	FILETIME=[F3EDFDE0:01C93841]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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: multipart/mixed; boundary="===============0360171738=="
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0360171738==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93841.F3BABA77"

This is a multi-part message in MIME format.

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

Right!

________________________________

De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part =
de R=E9mi Despr=E9s
Envoy=E9 : lundi 27 octobre 2008 15:31
=C0 : LEVIS Pierre RD-CORE-CAE
Cc : behave@ietf.org
Objet : Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt


pierre.levis@orange-ftgroup.com   (m/j/a) 10/27/08 3:14 PM:=20

	 we're bound to have the same issue as soon as we do address sharing, =
no matter the mechanism. So, I would say that it should not work accross =
a Carrier Grade NAT.

And not more across "CPE" NATs that have only one IPv4 address to share, =
right?
(This one instance where working in IPv6, if possible, is cleaner, =
simpler, safer....)
RD


De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 27 octobre 2008 09:39=20

=09
	In sec 4.4  it says :"For one P2P (Peer-to-Peer) application tested, we =
found that two  peers each behind a CPE sharing the same public address =
cannot  download a SAME file from a source peer."
=09
	- Do we know if this application works (for the same file) across NATs, =
and if yes how?
=09



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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3429" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D841393814-27102008>Right!</SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>De&nbsp;:</B> behave-bounces@ietf.org=20
[mailto:behave-bounces@ietf.org] <B>De la part de</B> R=E9mi=20
Despr=E9s<BR><B>Envoy=E9&nbsp;:</B> lundi 27 octobre 2008 =
15:31<BR><B>=C0&nbsp;:</B>=20
LEVIS Pierre RD-CORE-CAE<BR><B>Cc&nbsp;:</B>=20
behave@ietf.org<BR><B>Objet&nbsp;:</B> Re: [BEHAVE] TR: I-D=20
Action:draft-boucadair-port-range-00.txt<BR></FONT><BR></DIV>
<DIV></DIV><A class=3Dmoz-txt-link-abbreviated=20
href=3D"mailto:pierre.levis@orange-ftgroup.com">pierre.levis@orange-ftgro=
up.com</A>&nbsp;&nbsp;=20
(m/j/a) 10/27/08 3:14 PM:=20
<BLOCKQUOTE cite=3Dmid:D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1 =

type=3D"cite">
  <META http-equiv=3DContext-Type content=3D"text/html; =
charset=3Diso-8859-1">
  <DIV><SPAN>&nbsp;we're bound to have the same issue as soon as we do =
address=20
  sharing, no matter the mechanism. So, I would say that it should not =
work=20
  accross a Carrier Grade NAT.</SPAN></DIV></BLOCKQUOTE>And not more =
across "CPE"=20
NATs that have only one IPv4 address to share, right?<BR>(This one =
instance=20
where working in IPv6, if possible, is cleaner, simpler,=20
safer....)<BR>RD<BR><BR><BR><B>De&nbsp;:</B> R=E9mi Despr=E9s [<A=20
class=3Dmoz-txt-link-freetext=20
href=3D"mailto:remi.despres@free.fr">mailto:remi.despres@free.fr</A>]=20
<BR><B>Envoy=E9&nbsp;:</B> lundi 27 octobre 2008 09:39=20
<BLOCKQUOTE cite=3Dmid:D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1 =

type=3D"cite">
  <DIV><SPAN></SPAN></DIV>In sec 4.4&nbsp; it says :"For one P2P =
(Peer-to-Peer)=20
  application tested, we found that two&nbsp; peers each behind a CPE =
sharing=20
  the same public address cannot&nbsp; download a SAME file from a =
source=20
  peer."<BR><BR>- Do we know if this application works (for the same =
file)=20
  across NATs, and if yes how?<BR></BLOCKQUOTE><BR></BODY></HTML>

------_=_NextPart_001_01C93841.F3BABA77--

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

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

--===============0360171738==--


From behave-bounces@ietf.org  Mon Oct 27 08:55:38 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AE0F3A6B2E;
	Mon, 27 Oct 2008 08:55:38 -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 BED893A6B60
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 08:55:36 -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 JaDFBEfo0EjL for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 08:55:35 -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 8B4F93A6AD0
	for <behave@ietf.org>; Mon, 27 Oct 2008 08:55:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,492,1220227200"; d="scan'208";a="183366895"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 27 Oct 2008 15:55:34 +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 m9RFtZsO029974
	for <behave@ietf.org>; Mon, 27 Oct 2008 08:55:35 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9RFtYr2019037
	for <behave@ietf.org>; Mon, 27 Oct 2008 15:55:35 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Behave WG'" <behave@ietf.org>
References: 
Date: Mon, 27 Oct 2008 08:55:34 -0700
Message-ID: <01a801c9384c$72e77090$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: 
Thread-Index: AckYQ0LBnKoRYWK4S92hrl4bdPZh2wAAAY2wCAIxF8A=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8728; t=1225122935;
	x=1225986935; 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:=20draft-ietf-behave-dccp=20as=20BCP |Sender:=20;
	bh=C5UsoW/RAquqdCBSnn+bhmsRwDtYCsxCHSApXS47ZnI=;
	b=U3U/PsXSljwiGfT7ANzcVVVBg1dASze++MfwNVy0b8P7jfSlmJ8mGp4rRw
	JLIxOjxpSO1ZzrgAl9eeB7tgxggAZv86OjLK5SXeZbpfRGAeQK1N8G64FAKJ
	PPzAkTRUx0;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: [BEHAVE] draft-ietf-behave-dccp as BCP
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Magnus just pointed out the intended status for this document is supposed to
be BCP -- not proposed standard.  My write up said 'standards track', which is
vague between BCP and proposed standard.

To clarify:  draft-ietf-behave-dccp is going to be a BCP, along with similar
documents that BEHAVE has published (TCP, UDP, ICMP, etc.).

Sorry about that,
-d


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Tuesday, September 16, 2008 2:29 PM
> To: 'Behave WG'
> Subject: FW: pub request, draft-ietf-behave-dccp-02.txt
> 
> FYI.
> 
> -d
>  
> 
> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: Tuesday, September 16, 2008 2:29 PM
> To: 'iesg-secretary@ietf.org'; 'Magnus Westerlund'
> Subject: pub request, draft-ietf-behave-dccp-02.txt
> 
> Document shepherd write-up for draft-ietf-behave-dccp-02.txt
> date: 16-Sep-2008
> 
>    (1.a)  Who is the Document Shepherd for this document? 
> 
> Dan Wing, dwing@cisco.com
> 
>           Has the
>           Document Shepherd personally reviewed this version of the
>           document and, in particular, does he or she believe this
>           version is ready for forwarding to the IESG for publication?
> 
> Yes.
> 
> 
>    (1.b)  Has the document had adequate review both from key 
> WG members
>           and from key non-WG members?  Does the Document 
> Shepherd have
>           any concerns about the depth or breadth of the reviews that
>           have been performed?
> 
> No concerns.
> 
> 
>    (1.c)  Does the Document Shepherd have concerns that the document
>           needs more review from a particular or broader perspective,
>           e.g., security, operational complexity, someone 
> familiar with
>           AAA, internationalization, or XML?
> 
> The WGLC was done in conunction with the DCCP working group.
> 
> 
>    (1.d)  Does the Document Shepherd have any specific concerns or
>           issues with this document that the Responsible Area Director
>           and/or the IESG should be aware of?  For example, perhaps he
>           or she is uncomfortable with certain parts of the 
> document, or
>           has concerns whether there really is a need for it.  In any
>           event, if the WG has discussed those issues and has 
> indicated
>           that it still wishes to advance the document, detail those
>           concerns here.  Has an IPR disclosure related to 
> this document
>           been filed?  If so, please include a reference to the
>           disclosure and summarize the WG discussion and conclusion on
>           this issue.
> 
> No concerns.
> 
> 
> 
>    (1.e)  How solid is the WG consensus behind this document?  Does it
>           represent the strong concurrence of a few individuals, with
>           others being silent, or does the WG as a whole 
> understand and
>           agree with it?
> 
> There is solid WG consensus behind this document; many of its 
> recommendations are derived from BEHAVE's UDP document (RFC4787) and
> TCP document (draft-ietf-behave-tcp).
> 
> 
>    (1.f)  Has anyone threatened an appeal or otherwise 
> indicated extreme
>           discontent?  If so, please summarize the areas of 
> conflict in
>           separate email messages to the Responsible Area 
> Director.  (It
>           should be in a separate email because this questionnaire is
>           entered into the ID Tracker.)
> 
> There has been no discontent.
> 
> 
>    (1.g)  Has the Document Shepherd personally verified that the
>           document satisfies all ID nits?  (See
>           http://www.ietf.org/ID-Checklist.html and
>           http://tools.ietf.org/tools/idnits/.)  Boilerplate 
> checks are
>           not enough; this check needs to be thorough. 
> 
> Yes.
> 
>           Has the document
>           met all formal review criteria it needs to, such as the MIB
>           Doctor, media type, and URI type reviews? 
> 
> Yes.
> 
>           If the document
>           does not already indicate its intended status at the top of
>           the first page, please indicate the intended status here.
> 
> intended status: Standards Track
> 
> 
>    (1.h)  Has the document split its references into normative and
>           informative?  Are there normative references to 
> documents that
>           are not ready for advancement or are otherwise in an unclear
>           state?  If such normative references exist, what is the
>           strategy for their completion?  Are there normative 
> references
>           that are downward references, as described in [RFC3967]?  If
>           so, list these downward references to support the Area
>           Director in the Last Call procedure for them [RFC3967].
> 
> All references are verified by the document shepherd, and are good.
> 
> 
>    (1.i)  Has the Document Shepherd verified that the document's IANA
>           Considerations section exists and is consistent 
> with the body
>           of the document?  If the document specifies protocol
>           extensions, are reservations requested in appropriate IANA
>           registries?  Are the IANA registries clearly identified?  If
>           the document creates a new registry, does it define the
>           proposed initial contents of the registry and an allocation
>           procedure for future registrations?  Does it suggest a
>           reasonable name for the new registry?  See 
> [RFC2434].  If the
>           document describes an Expert Review process, has 
> the Document
>           Shepherd conferred with the Responsible Area 
> Director so that
>           the IESG can appoint the needed Expert during IESG 
> Evaluation?
> 
> There are no IANA actions for this document.
> 
> 
>    (1.j)  Has the Document Shepherd verified that sections of the
>           document that are written in a formal language, such as XML
>           code, BNF rules, MIB definitions, etc., validate 
> correctly in
>           an automated checker?
> 
> The document contains no formal language.
> 
> 
>    (1.k)  The IESG approval announcement includes a Document
>           Announcement Write-Up.  Please provide such a Document
>           Announcement Write-Up.  Recent examples can be found in the
>           "Action" announcements for approved documents.  The approval
>           announcement contains the following sections:
> 
>           Technical Summary
>              Relevant content can frequently be found in the abstract
>              and/or introduction of the document.  If not, this may be
>              an indication that there are deficiencies in the abstract
>              or introduction.
> 
> 
> This document defines a set of requirements for DCCP-capable NATs
> that would allow certain applications, such as streaming applications
> to operate consistently.  
> 
> 
>           Working Group Summary
>              Was there anything in the WG process that is 
> worth noting?
>              For example, was there controversy about 
> particular points
>              or were there decisions where the consensus was
>              particularly rough?
> 
> Nothing worth noting.
> 
> 
>           Document Quality
>              Are there existing implementations of the 
> protocol?  Have a
>              significant number of vendors indicated their plan to
>              implement the specification? 
> 
> Unknown.
> 
> 
>              Are there any reviewers that
>              merit special mention as having done a thorough review,
>              e.g., one that resulted in important changes or a
>              conclusion that the document had no substantive issues? 
> 
> They are listed in the acknowledgements section.
> 
>              If
>              there was a MIB Doctor, Media Type, or other 
> Expert Review,
>              what was its course (briefly)?  In the case of a 
> Media Type
>              Review, on what date was the request posted?
> 
> This document did not include such reviews, and doesn't need one.
> 
> 
>           Personnel
>              Who is the Document Shepherd for this document?
> 
> Dan Wing, dwing@cisco.com
> 
>              Who is the
>              Responsible Area Director? 
> 
> Magnus Westerlund, magnus.westerlund@ericsson.com
> 
>              If the document requires IANA
>              experts(s), insert 'The IANA Expert(s) for the registries
>              in this document are <TO BE ADDED BY THE AD>.'
> 
> No experts are needed.
> 
> 
> 

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


From behave-bounces@ietf.org  Mon Oct 27 11:38:16 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEE0E3A6B8F;
	Mon, 27 Oct 2008 11:38:15 -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 3D9723A6B8F
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 11:38:15 -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 xp3rbQGxJy-7 for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 11:38:14 -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 421143A6B88
	for <behave@ietf.org>; Mon, 27 Oct 2008 11:38:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,493,1220227200"; d="scan'208";a="111216556"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 27 Oct 2008 18:38: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 m9RIcDns019660; 
	Mon, 27 Oct 2008 11:38:13 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9RIcDwZ027221;
	Mon, 27 Oct 2008 18:38:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pierre.levis@orange-ftgroup.com>, <behave@ietf.org>
References: <49057E3D.5090401@free.fr>
	<D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1>
Date: Mon, 27 Oct 2008 11:38:13 -0700
Message-ID: <040001c93863$2b718ef0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1>
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3983; t=1225132693;
	x=1225996693; 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[BEHAVE]=20TR=3A=20I-D=20Action=3Adraft
	-boucadair-port-range-00.txt |Sender:=20;
	bh=O8o+3POC4QUV1td1VM8U6NU6tyDW97c2PbO9N+fNpqc=;
	b=RzCd30n1XXO4AnW7eFnnqTjNqBEzDqtTnPRs5cx/rUYXTq52TkBXbOfNBr
	ZMz+D41yYWd/stc4HdBz52Mj6OjcHHVY26BClWbnZ3mzPntQouFcPtd0+Plv
	r8P0X/pixA;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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

I will go out on a limb, for the benefit of anyone reading these
archives in 5 years, that the application must be BitTorrent.

Assuming that is correct, the probably reason BitTorrent prevents simultane=
ous
downloading by two hosts with the same identifier (IP address) is to provide
fairer bandwidth sharing.  Without such protection, you could get 2x downlo=
ad
speed for a file if a person's two BitTorrent clients happened to download
from completely different peers.

-d


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

> [mailto:behave-bounces@ietf.org] On Behalf Of =

> pierre.levis@orange-ftgroup.com
> Sent: Monday, October 27, 2008 7:14 AM
> To: behave@ietf.org
> Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
> =

> Hi R=E9mi,
>  =

> Thank you for your careful reading.
>  =

> This is one of the most commonly used p2p application!
> More seriously, we're bound to have the same issue as soon as =

> we do address sharing, no matter the mechanism. So, I would =

> say that it should not work accross a Carrier Grade NAT.
>  =

>  =

> Regards,
>  =

>  =

> Pierre
> =

> ________________________________
> =

> De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr] =

> Envoy=E9 : lundi 27 octobre 2008 09:39
> =C0 : LEVIS Pierre RD-CORE-CAE
> Cc : behave@ietf.org
> Objet : Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
> =

> =

> Hi Pierre,
> =

> I find the draft most interesting, in particular the real =

> experiment it describes .
> =

> In sec 4.4  it says :"For one P2P (Peer-to-Peer) application =

> tested, we found that two  peers each behind a CPE sharing =

> the same public address cannot  download a SAME file from a =

> source peer."
> - Is there a problem in telling  which application this is?
> - Do we know if this application works (for the same file) =

> across NATs, and if yes how?
> =

> Regards,
> =

> RD
> =

> =

> =

> =

> pierre.levis@orange-ftgroup.com   (m/j/a) 10/24/08 3:16 PM: =

> =

> 	Hi all,
> 	=

> 	I would like to draw your attention on the following draft.
> 	=

> 	We (the authors) are looking forward to reading your comments.
> 	=

> 	=

> 	Regards
> 	=

> 	=

> 	Pierre
> 	=

> 	=

> 	=

> 	-----Message d'origine-----
> 	De : i-d-announce-bounces@ietf.org =

> [mailto:i-d-announce-bounces@ietf.org] De la part de =

> Internet-Drafts@ietf.org
> 	Envoy=E9 : jeudi 23 octobre 2008 14:45
> 	=C0 : i-d-announce@ietf.org
> 	Objet : I-D Action:draft-boucadair-port-range-00.txt =

> 	=

> 	A New Internet-Draft is available from the on-line =

> Internet-Drafts directories.
> 	=

> 		Title           : Provider-Provisioned CPE: =

> IPv4 Connectivity Access in the context of IPv4 address exhaustion
> 		Author(s)       : M. Boucadair, et al.
> 		Filename        : draft-boucadair-port-range-00.txt
> 		Pages           : 33
> 		Date            : 2008-10-23
> 	=

> 	This memo proposes a solution, based on fractional =

> addresses, to face the IPv4 public address exhaustion.  It =

> details the solution and presents a mock-up implementation, =

> with the results of tests that validate the concept.  =

> Finally, it makes a comparison with the alternative =

> Carrier-Grade NAT (CG-NAT) solutions.
> 	=

> 	A URL for this Internet-Draft is:
> 	=

> http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt
> 	=

> 	Internet-Drafts are also available by anonymous FTP at:
> 	ftp://ftp.ietf.org/internet-drafts/
> 	=

> 	Below is the data which will enable a MIME compliant =

> mail reader implementation to automatically retrieve the =

> ASCII version of the Internet-Draft.
> 	  =

> 	=

> ________________________________
> =

> =

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

> =

> =

> =


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


From behave-bounces@ietf.org  Mon Oct 27 11:59:46 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BE5D3A69AA;
	Mon, 27 Oct 2008 11:59:46 -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 887ED3A69AA
	for <behave@core3.amsl.com>; Mon, 27 Oct 2008 11:59:45 -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=[AWL=0.300, 
	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 aITcyLbTesuT for <behave@core3.amsl.com>;
	Mon, 27 Oct 2008 11:59:44 -0700 (PDT)
Received: from QMTA02.emeryville.ca.mail.comcast.net
	(qmta02.emeryville.ca.mail.comcast.net [76.96.30.24])
	by core3.amsl.com (Postfix) with ESMTP id C1BC53A6981
	for <behave@ietf.org>; Mon, 27 Oct 2008 11:59:44 -0700 (PDT)
Received: from OMTA09.emeryville.ca.mail.comcast.net ([76.96.30.20])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id XoP51a00W0S2fkCA2uzijg; Mon, 27 Oct 2008 18:59:42 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA09.emeryville.ca.mail.comcast.net with comcast
	id XuzW1a00a1cMU3H8VuzaxG; Mon, 27 Oct 2008 18:59:39 +0000
X-Authority-Analysis: v=1.0 c=1 a=tm1f5XwphL8A:10 a=-Z49rLPW_xMA:10
	a=48vgC7mUAAAA:8 a=AZrt9R9Y2ahf2sKsaMUA:9 a=jiFrM0_qrm7E7fba7zwA:7
	a=62YSukodpuVlRIGyspagQH-m9OMA:4 a=I2EqgwFF2xUA:10
Message-Id: <D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Behave WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 14:59:30 -0400
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
Subject: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


I have posted a NAT66 draft, so that we can have a better-grounded  
discussion of whether it makes sense to include NAT66 as a work item  
in the behave charter.  The draft can be found at the following URL:

http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt

Feedback would be greatly appreciated!

Margaret


> A new version of I-D, draft-mrw-behave-nat66-00.txt has been  
> successfuly submitted by Margaret Wasserman and posted to the IETF  
> repository.
>
> Filename:	 draft-mrw-behave-nat66
> Revision:	 00
> Title:		 IPv6-to-IPv6 Network Address Translation (NAT66)
> Creation_date:	 2008-10-27
> WG ID:		 Independent Submission
> Number_of_pages: 13
>
> Abstract:
> This document describes a stateless, transport-agnostic IPv6-to-IPv6
> Network Address Translation (NAT66) function that provides the
> address independence benefit associated with IPv4-to-IPv4 NAT (NAT44)
> while minimizing, but not completely eliminating, the problems
> associated with NAT44.
>
> This document also describes an address mapping option for NAT66 that
> offers the topology hiding benefit associated with NAT44 at the cost
> of additional state in the NAT66 device.

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


From behave-bounces@ietf.org  Tue Oct 28 07:13:08 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B1493A6A92;
	Tue, 28 Oct 2008 07:13:08 -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 1AB8D3A6A92
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 07:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.623
X-Spam-Level: 
X-Spam-Status: No, score=-5.623 tagged_above=-999 required=5 tests=[AWL=0.626, 
	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 GbH2wl3z5u+o for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 07:13:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 43F603A69FD
	for <behave@ietf.org>; Tue, 28 Oct 2008 07:13:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C51E820268
	for <behave@ietf.org>; Tue, 28 Oct 2008 15:12:16 +0100 (CET)
X-AuditID: c1b4fb3e-aa77dbb00000537b-87-49071dc0e83b
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A33A4201FC
	for <behave@ietf.org>; Tue, 28 Oct 2008 15:12:16 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 15:11:19 +0100
Received: from [147.214.183.48] ([147.214.183.48]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 15:11:18 +0100
Message-ID: <49071D86.5000108@ericsson.com>
Date: Tue, 28 Oct 2008 15:11:18 +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>
X-Enigmail-Version: 0.95.7
X-OriginalArrivalTime: 28 Oct 2008 14:11:18.0863 (UTC)
	FILETIME=[0C2D75F0:01C93907]
X-Brightmail-Tracker: AAAAAA==
Subject: [BEHAVE] Additional comments on draft-ietf-behave-nat-icmp
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

Hi,

I did a review of what it really meant to follow the following text in
Section 7:

In addition, a NAT device is RECOMMENDED to conform to the following
   implementation considerations in [RFC1812]:
       d. TOS and Precedence, as described in Section 4.3.2.5 of
          [RFC1812],

the section of RFC 1812 reads like following:

4.3.2.5 TOS and Precedence


   ICMP error messages SHOULD have their TOS bits set to the same value
   as the TOS bits in the packet that provoked the sending of the ICMP
   error message, unless setting them to that value would cause the ICMP
   error message to be immediately discarded because it could not be
   routed to its destination.  Otherwise, ICMP error messages MUST be
   sent with a normal (i.e., zero) TOS.  An ICMP reply message SHOULD
   have its TOS bits set to the same value as the TOS bits in the ICMP
   request that provoked the reply.

   ICMP Source Quench error messages, if sent at all, MUST have their IP
   Precedence field set to the same value as the IP Precedence field in
   the packet that provoked the sending of the ICMP Source Quench
   message.  All other ICMP error messages (Destination Unreachable,
   Redirect, Time Exceeded, and Parameter Problem) SHOULD have their
   precedence value set to 6 (INTERNETWORK CONTROL) or 7 (NETWORK
   CONTROL).  The IP Precedence value for these error messages MAY be
   settable.

   An ICMP reply message MUST have its IP Precedence field set to the
   same value as the IP Precedence field in the ICMP request that
   provoked the reply.


As RFC 1812 talks about TOS and IP precedence and RFC 2474 redefined
these field the text is not correct. In addition there is a good
question about the traffic class marking recommendations in RFC 1812 is
relevant today. First the classes that are recommend are now made legacy
by RFC 2474. There is the class selector to deal with this to certain
degree, see RFC 4594. The second is if anyone really prioritize their
ICMP error messages to another class then what the traffic was. Some may
even send it with best-effort only to avoid DoS issues.

My personal suggestion on how to fix this is the following. Comments and
better suggestions are really appreciated. So replace the whole
reference to d. with a new paragraph saying the following:

The NAT SHOULD copy the diffserv class of the message that causes the
sending of an ICMP error message. A NAT MAY allow configuration of the
diffserv class to use for the different types of ICMP messages.

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
----------------------------------------------------------------------
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 28 07:19:41 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47CAC28C208;
	Tue, 28 Oct 2008 07:19:41 -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 47D813A6A92
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 07:19:39 -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 zD8Egwsq5W1u for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 07:19:38 -0700 (PDT)
Received: from QMTA03.emeryville.ca.mail.comcast.net
	(qmta03.emeryville.ca.mail.comcast.net [76.96.30.32])
	by core3.amsl.com (Postfix) with ESMTP id 69CA93A6A0D
	for <behave@ietf.org>; Tue, 28 Oct 2008 07:19:38 -0700 (PDT)
Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51])
	by QMTA03.emeryville.ca.mail.comcast.net with comcast
	id YDSv1a00216AWCUA3EKStu; Tue, 28 Oct 2008 14:19:26 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA06.emeryville.ca.mail.comcast.net with comcast
	id YEKE1a00C1cMU3H8SEKHQu; Tue, 28 Oct 2008 14:19:24 +0000
X-Authority-Analysis: v=1.0 c=1 a=qXtqn8Pk-tcA:10 a=oZwnVYdGwtoA:10
	a=48vgC7mUAAAA:8 a=9XPhgVF_trD45Z-HNAQA:9 a=CKjFDsenPrLakUphcj4A:7
	a=uFeTliGFqUrx8jEUiMuCFzUxLYEA:4 a=lZB815dzVvQA:10 a=R6fQ0Q4ov3oA:10
Message-Id: <0011E99C-0FB6-4E54-A1B4-8FF12759575C@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 28 Oct 2008 09:22:44 -0400
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


Shortly after posting this, I realized that I made an error in
transcribing the math in section 5.1.1.

The draft says:

 >  The one's complement checksum of FD01:0203:0405 is 0xFCF5.  The  
one's
 >  complement checksum of 2001:0DB8:0001 is 0xD245.  Using one's
 >  complement math, 0xD245 - 0xFCF5 = 0xD54F. The subnet mask in the
 >  original packet is 0x0001.  Using one's complement math, 0x0001 +
 >  0xD54F = 0xD550.
 >
 >  So, the value D54F is written in the 16-bit subnet mask area,
 >  resulting in a mapped external address of 2001:0DB8:0001:D54F::0001.
 >
 >  When a response packet is received, it will contain the destination
 >  address 2001:0DB8:0001:D54F::0001, which will be mapped using the
 >  same mapping algorithm, back to FD01:0203:0405:0000::0001.

The first paragraph is correct, and the subnet mask should be set to
0xD54F + 0x0001, which equals 0xD54F.

In the second and third paragraphs, all three instances of D54F should  
be
replaced with D550.

I have corrected this in my -01 edit buffer.  I'll wait to see if I  
get any other
feedback this week, and if I have enough changes to make it worthwhile,
I'll post an update before the final draft deadline.

I would appreciate your feedback on the draft, as well as your opinions
about whether a NAT66 effort should be chartered in the behave WG.

Margaret

On Oct 27, 2008, at 2:59 PM, Margaret Wasserman wrote:

>
> I have posted a NAT66 draft, so that we can have a better-grounded  
> discussion of whether it makes sense to include NAT66 as a work item  
> in the behave charter.  The draft can be found at the following URL:
>
> http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt
>
> Feedback would be greatly appreciated!
>
> Margaret
>
>
>> A new version of I-D, draft-mrw-behave-nat66-00.txt has been  
>> successfuly submitted by Margaret Wasserman and posted to the IETF  
>> repository.
>>
>> Filename:	 draft-mrw-behave-nat66
>> Revision:	 00
>> Title:		 IPv6-to-IPv6 Network Address Translation (NAT66)
>> Creation_date:	 2008-10-27
>> WG ID:		 Independent Submission
>> Number_of_pages: 13
>>
>> Abstract:
>> This document describes a stateless, transport-agnostic IPv6-to-IPv6
>> Network Address Translation (NAT66) function that provides the
>> address independence benefit associated with IPv4-to-IPv4 NAT (NAT44)
>> while minimizing, but not completely eliminating, the problems
>> associated with NAT44.
>>
>> This document also describes an address mapping option for NAT66 that
>> offers the topology hiding benefit associated with NAT44 at the cost
>> of additional state in the NAT66 device.
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

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


From behave-bounces@ietf.org  Tue Oct 28 07:25:56 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F5263A6A99;
	Tue, 28 Oct 2008 07:25:56 -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 4042A3A6A64
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 07:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	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 oBsokrdasAd5 for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 07:25:54 -0700 (PDT)
Received: from QMTA09.emeryville.ca.mail.comcast.net
	(qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])
	by core3.amsl.com (Postfix) with ESMTP id 624113A6A8C
	for <behave@ietf.org>; Tue, 28 Oct 2008 07:25:54 -0700 (PDT)
Received: from OMTA11.emeryville.ca.mail.comcast.net ([76.96.30.36])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id YBB31a0020mlR8UA9ERtZ5; Tue, 28 Oct 2008 14:25:53 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA11.emeryville.ca.mail.comcast.net with comcast
	id YERh1a00B1cMU3H8XERkXV; Tue, 28 Oct 2008 14:25:51 +0000
X-Authority-Analysis: v=1.0 c=1 a=qXtqn8Pk-tcA:10 a=oZwnVYdGwtoA:10
	a=uBQGQ-TyPeKLxAf6rJ4A:9 a=UqYZ-uZYn5LVa-yfISLOgScOF-wA:4
	a=c06vB5MgL9cA:10
Message-Id: <22939476-00C4-4650-976B-80FA1500EAE0@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <0011E99C-0FB6-4E54-A1B4-8FF12759575C@lilacglade.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 28 Oct 2008 10:25:40 -0400
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
	<0011E99C-0FB6-4E54-A1B4-8FF12759575C@lilacglade.org>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


For some reason, I just can't get this right...  :-)

On Oct 28, 2008, at 9:22 AM, Margaret Wasserman wrote:
> The first paragraph is correct, and the subnet mask should be set to
> 0xD54F + 0x0001, which equals 0xD54F.

0xD54F + 1 = 0xD550, of course!

Anyway, there is no problem with the algorithm described, as far as I  
know, just with my ability to type in accurate calculations.

Margaret

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


From behave-bounces@ietf.org  Tue Oct 28 11:00:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FF6328C36A;
	Tue, 28 Oct 2008 11:00:02 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id BF3BA28C369; Tue, 28 Oct 2008 11:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081028180001.BF3BA28C369@core3.amsl.com>
Date: Tue, 28 Oct 2008 11:00:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-dccp-04.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol
	Author(s)       : R. Denis-Courmont
	Filename        : draft-ietf-behave-dccp-04.txt
	Pages           : 11
	Date            : 2008-10-28

This document defines a set of requirements for NATs handling the
Datagram Congestion Control Protocol (DCCP).  Those allow DCCP
applications, such as streaming applications to operate consistently.
These requirements are very similar to the TCP requirements for NATs
already published by the IETF.  Developing NATs that meet this set of
requirements will greatly increase the likelihood that applications
using DCCP will function properly.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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


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

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

--NextPart--


From behave-bounces@ietf.org  Tue Oct 28 11:56:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 118D028C21D;
	Tue, 28 Oct 2008 11:56:05 -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 1597228C1CD
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 11:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	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 u+L44rQF3WlI for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 11:56:02 -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 D2F8F3A6817
	for <behave@ietf.org>; Tue, 28 Oct 2008 11:56:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,500,1220227200"; d="scan'208";a="184230563"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 28 Oct 2008 18:56:02 +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 m9SIu2q9001738; 
	Tue, 28 Oct 2008 11:56:02 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9SItqGl025316;
	Tue, 28 Oct 2008 18:55:54 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pierre.levis@orange-ftgroup.com>
References: <49057E3D.5090401@free.fr>
	<D109C8C97C15294495117745780657AE0AB01FB3@ftrdmel1> 
Date: Tue, 28 Oct 2008 11:55:50 -0700
Message-ID: <00b001c9392e$cf656f60$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: 
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZAAMsaucA==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5385; t=1225220162;
	x=1226084162; 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:=20BitTorrent=20with=20shared=20IP=20addresses=20[
	was=20RE=3A=20[BEHAVE]=20TR=3A=20I-D=20Action=3Adraft-boucad
	air-port-range-00.txt] |Sender:=20;
	bh=EEO8HpdCNyTjP5gOtDcy1CNG9KLLckavl3QvyxAHFHI=;
	b=qGFW29CrHt9VFGHCE5zJopnjP6cNfYoJzuRR07rHDmOiEQ2Rb73V2RnGNu
	bfjALZEirgNYM2cKXt/dnI53AI6Oh9ObGqcVRmjlKuJqOL7L4Ro/U7n0Bth3
	OkZSa0gm/f;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org
Subject: [BEHAVE] BitTorrent with shared IP addresses [was RE: TR: I-D
	Action:draft-boucadair-port-range-00.txt]
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

Pierre,

I decided to test how BitTorrent works with two clients behind the same IP
address.  My results show that it works fine.  I tested by running both
uTorrent and Vuze (formerly called Azureus) on the same Windows PC, with one
IPv4 address towards the Internet (my trusty Linksys WRT54G running Tomato =
3rd
party firmware).

For my torrent download, I used 2.9Gb copy of Wikipedia was recently made
available,
http://www.soschildrensvillages.org.uk/charity-news/2008-wikipedia-for-scho=
ols
.htm#download

Can you provide details on the test you performed that showed "one of the m=
ost
commonly used p2p applications" did not work at all when two hosts shared t=
he
same IP address?  I am now suspicious it was the tracker causing the
restriction you observed, and not the BitTorrent protocol itself.

-d


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] =

> Sent: Monday, October 27, 2008 11:38 AM
> To: 'pierre.levis@orange-ftgroup.com'; 'behave@ietf.org'
> Subject: RE: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
> =

> I will go out on a limb, for the benefit of anyone reading these
> archives in 5 years, that the application must be BitTorrent.
> =

> Assuming that is correct, the probably reason BitTorrent =

> prevents simultaneous downloading by two hosts with the same =

> identifier (IP address) is to provide fairer bandwidth =

> sharing.  Without such protection, you could get 2x download =

> speed for a file if a person's two BitTorrent clients =

> happened to download from completely different peers.
> =

> -d
> =

> =

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

> > [mailto:behave-bounces@ietf.org] On Behalf Of =

> > pierre.levis@orange-ftgroup.com
> > Sent: Monday, October 27, 2008 7:14 AM
> > To: behave@ietf.org
> > Subject: Re: [BEHAVE] TR: I-D =

> Action:draft-boucadair-port-range-00.txt
> > =

> > Hi R=E9mi,
> >  =

> > Thank you for your careful reading.
> >  =

> > This is one of the most commonly used p2p application!
> > More seriously, we're bound to have the same issue as soon as =

> > we do address sharing, no matter the mechanism. So, I would =

> > say that it should not work accross a Carrier Grade NAT.
> >  =

> >  =

> > Regards,
> >  =

> >  =

> > Pierre
> > =

> > ________________________________
> > =

> > De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr] =

> > Envoy=E9 : lundi 27 octobre 2008 09:39
> > =C0 : LEVIS Pierre RD-CORE-CAE
> > Cc : behave@ietf.org
> > Objet : Re: [BEHAVE] TR: I-D =

> Action:draft-boucadair-port-range-00.txt
> > =

> > =

> > Hi Pierre,
> > =

> > I find the draft most interesting, in particular the real =

> > experiment it describes .
> > =

> > In sec 4.4  it says :"For one P2P (Peer-to-Peer) application =

> > tested, we found that two  peers each behind a CPE sharing =

> > the same public address cannot  download a SAME file from a =

> > source peer."
> > - Is there a problem in telling  which application this is?
> > - Do we know if this application works (for the same file) =

> > across NATs, and if yes how?
> > =

> > Regards,
> > =

> > RD
> > =

> > =

> > =

> > =

> > pierre.levis@orange-ftgroup.com   (m/j/a) 10/24/08 3:16 PM: =

> > =

> > 	Hi all,
> > 	=

> > 	I would like to draw your attention on the following draft.
> > 	=

> > 	We (the authors) are looking forward to reading your comments.
> > 	=

> > 	=

> > 	Regards
> > 	=

> > 	=

> > 	Pierre
> > 	=

> > 	=

> > 	=

> > 	-----Message d'origine-----
> > 	De : i-d-announce-bounces@ietf.org =

> > [mailto:i-d-announce-bounces@ietf.org] De la part de =

> > Internet-Drafts@ietf.org
> > 	Envoy=E9 : jeudi 23 octobre 2008 14:45
> > 	=C0 : i-d-announce@ietf.org
> > 	Objet : I-D Action:draft-boucadair-port-range-00.txt =

> > 	=

> > 	A New Internet-Draft is available from the on-line =

> > Internet-Drafts directories.
> > 	=

> > 		Title           : Provider-Provisioned CPE: =

> > IPv4 Connectivity Access in the context of IPv4 address exhaustion
> > 		Author(s)       : M. Boucadair, et al.
> > 		Filename        : draft-boucadair-port-range-00.txt
> > 		Pages           : 33
> > 		Date            : 2008-10-23
> > 	=

> > 	This memo proposes a solution, based on fractional =

> > addresses, to face the IPv4 public address exhaustion.  It =

> > details the solution and presents a mock-up implementation, =

> > with the results of tests that validate the concept.  =

> > Finally, it makes a comparison with the alternative =

> > Carrier-Grade NAT (CG-NAT) solutions.
> > 	=

> > 	A URL for this Internet-Draft is:
> > 	=

> > =

> http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt
> > 	=

> > 	Internet-Drafts are also available by anonymous FTP at:
> > 	ftp://ftp.ietf.org/internet-drafts/
> > 	=

> > 	Below is the data which will enable a MIME compliant =

> > mail reader implementation to automatically retrieve the =

> > ASCII version of the Internet-Draft.
> > 	  =

> > 	=

> > ________________________________
> > =

> > =

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

> > =

> > =

> > =

> =


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


From behave-bounces@ietf.org  Tue Oct 28 12:57:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54AB128C135;
	Tue, 28 Oct 2008 12:57:30 -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 16F913A6CA0
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 12:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5
	tests=[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 9lGUtSrRR6rV for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 12:57:28 -0700 (PDT)
Received: from mailgate-internal4.sri.com (mailgate-internal4.SRI.COM
	[128.18.84.114]) by core3.amsl.com (Postfix) with SMTP id 0EE513A6B7F
	for <behave@ietf.org>; Tue, 28 Oct 2008 12:57:27 -0700 (PDT)
Received: from smssmtp-internal2.sri.com (128.18.84.116)
	by mailgate-internal4.sri.com with SMTP; 28 Oct 2008 19:57:25 -0000
X-AuditID: 80125474-ac198bb000000a40-91-49076ea53933
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal2.sri.com (Symantec Mail Security) with ESMTP id
	7AB2221AF2A
	for <behave@ietf.org>; Tue, 28 Oct 2008 12:57:25 -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 <0K9G00FH6SRO6AC0@mail.sri.com> for
	behave@ietf.org; Tue, 28 Oct 2008 12:57:25 -0700 (PDT)
Date: Tue, 28 Oct 2008 15:57:26 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
Message-id: <49076EA6.3040802@sri.com>
MIME-version: 1.0
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Seems a reasonable draft, lives up to its abstract.  A couple comments.

1.  Introduction:  "interference with security mechanisms that involve 
end-to-end encryption of IP headers" I think that's not exactly right, 
as AH authentication is not end-to-end encryption, but won't work with 
any NAT that modifies the protected header fields, including IP 
addresses.  ESP would work through NAT66, allowing end-to-end encryption 
but not authentication.  Unless I'm missing something.

2.  Motivation:  subtle difference between "not recommending the use of 
NAT" and "recommending not having NAT66" but overall the draft seems to 
lean towards "not recommending" rather than "recommending not".  Hence 
the definition of a "safer" way of doing it if you must?   This explains 
the motivation for the draft, but the draft does not give convincing 
motivation FOR using NAT66.  It seems like having both a ULA and global 
unicast address on an interface allows use of ULA for local traffic and 
the global otherwise.  Topology hiding is already provided in RFC 4864.  
I'm not invoking the third rail, but I think the draft should provide 
some good reasons or scenarios when use of NAT66 would be a reasonable 
alternative. 

3.  Security Considerations:  the risk is no worse than native IPv6 
without a firewall, but it is good to point out that the NAT44 "security 
side effect" doesn't carry over to NAT66.

Ed J.
Margaret Wasserman wrote:
>
> I have posted a NAT66 draft, so that we can have a better-grounded 
> discussion of whether it makes sense to include NAT66 as a work item 
> in the behave charter.  The draft can be found at the following URL:
>
> http://www.ietf.org/internet-drafts/draft-mrw-behave-nat66-00.txt
>
> Feedback would be greatly appreciated!
>
> Margaret
>
>
>> A new version of I-D, draft-mrw-behave-nat66-00.txt has been 
>> successfuly submitted by Margaret Wasserman and posted to the IETF 
>> repository.
>>
>> Filename:     draft-mrw-behave-nat66
>> Revision:     00
>> Title:         IPv6-to-IPv6 Network Address Translation (NAT66)
>> Creation_date:     2008-10-27
>> WG ID:         Independent Submission
>> Number_of_pages: 13
>>
>> Abstract:
>> This document describes a stateless, transport-agnostic IPv6-to-IPv6
>> Network Address Translation (NAT66) function that provides the
>> address independence benefit associated with IPv4-to-IPv4 NAT (NAT44)
>> while minimizing, but not completely eliminating, the problems
>> associated with NAT44.
>>
>> This document also describes an address mapping option for NAT66 that
>> offers the topology hiding benefit associated with NAT44 at the cost
>> of additional state in the NAT66 device.
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Tue Oct 28 13:06:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0CEB3A6C93;
	Tue, 28 Oct 2008 13:06:03 -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 AB11A3A6C93
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 13:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	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 PhZYdMAXf2Gf for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 13:05:55 -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 E052D3A67B2
	for <behave@ietf.org>; Tue, 28 Oct 2008 13:05:55 -0700 (PDT)
Received: from OMTA03.emeryville.ca.mail.comcast.net ([76.96.30.27])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id YGof1a00E0b6N64A7L5vCd; Tue, 28 Oct 2008 20:05:55 +0000
Received: from [10.2.0.63] ([69.33.111.74])
	by OMTA03.emeryville.ca.mail.comcast.net with comcast
	id YL5i1a00R1cMU3H8PL5meY; Tue, 28 Oct 2008 20:05:53 +0000
X-Authority-Analysis: v=1.0 c=1 a=qXtqn8Pk-tcA:10 a=oZwnVYdGwtoA:10
	a=l_bUiVUIRkzdDZJFYG0A:9 a=o5Bp1sfRQkBYSpenT9sA:7
	a=lIZ9lcdfxtLt5LbWF-X5w3T2G6cA:4 a=uVawpVqKyvgA:10
Message-Id: <D41DAFEC-1D0D-4DE5-8428-736D175C938A@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-Reply-To: <49076EA6.3040802@sri.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 28 Oct 2008 16:05:41 -0400
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
	<49076EA6.3040802@sri.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


Thanks, Ed!

Your feedback is helpful, and I will attempt to address your comments  
in the next version of the draft.

Margaret

On Oct 28, 2008, at 3:57 PM, Ed Jankiewicz wrote:

> Seems a reasonable draft, lives up to its abstract.  A couple  
> comments.
>
> 1.  Introduction:  "interference with security mechanisms that  
> involve end-to-end encryption of IP headers" I think that's not  
> exactly right, as AH authentication is not end-to-end encryption,  
> but won't work with any NAT that modifies the protected header  
> fields, including IP addresses.  ESP would work through NAT66,  
> allowing end-to-end encryption but not authentication.  Unless I'm  
> missing something.
>
> 2.  Motivation:  subtle difference between "not recommending the use  
> of NAT" and "recommending not having NAT66" but overall the draft  
> seems to lean towards "not recommending" rather than "recommending  
> not".  Hence the definition of a "safer" way of doing it if you  
> must?   This explains the motivation for the draft, but the draft  
> does not give convincing motivation FOR using NAT66.  It seems like  
> having both a ULA and global unicast address on an interface allows  
> use of ULA for local traffic and the global otherwise.  Topology  
> hiding is already provided in RFC 4864.  I'm not invoking the third  
> rail, but I think the draft should provide some good reasons or  
> scenarios when use of NAT66 would be a reasonable alternative.
> 3.  Security Considerations:  the risk is no worse than native IPv6  
> without a firewall, but it is good to point out that the NAT44  
> "security side effect" doesn't carry over to NAT66.
>
> Ed J.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 28 14:12:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 640CB28C336;
	Tue, 28 Oct 2008 14:12:37 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 83D0828C2DE; Tue, 28 Oct 2008 14:12:34 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Mime-Version: 1.0
Message-Id: <20081028211234.83D0828C2DE@core3.amsl.com>
Date: Tue, 28 Oct 2008 14:12:34 -0700 (PDT)
Cc: behave@ietf.org, dthaler@microsoft.com, dwing@cisco.com
Subject: [BEHAVE] WG Review: Recharter of Behavior Engineering for Hindrance
 Avoidance (behave)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

A modified charter has been submitted for the Behavior Engineering for
Hindrance Avoidance working group in the Transport Area of the IETF.  The
IESG has not made any determination as yet.  The modified charter is
provided below for informational purposes only.  Please send your comments
to the IESG mailing list (iesg@ietf.org) by November 4, 2008.

Behavior Engineering for Hindrance Avoidance (behave)
=====================================================

Last Modified: 2008-10-23

Current Status: Active Working Group

Chair(s):
Dan Wing [dwing@cisco.com]
Dave Thaler [dthaler@microsoft.com]

Transport Area Director(s):
Magnus Westerlund [magnus.westerlund@ericsson.com]
Lars Eggert [lars.eggert@nokia.com]

Transport Area Advisor:
Magnus Westerlund [magnus.westerlund@ericsson.com] 

Mailing Lists:
General Discussion: behave@ietf.org
To Subscribe: behave-request@ietf.org
In Body: In Body: subscribe
Archive:
http://www1.ietf.org/mail-archive/web/behave/current/index.html

Description of Working Group:

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. To support
deployments where communicating hosts require using different address
families (IPv4 or IPv6), address family translation is needed to
establish communication. In BEHAVE's specification work on this topic
it will coordinate with the V6ops WG on requirements and operational
considerations.

"An IPv4 network" or "an 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.). It will also be that network that
deploys the necessary equipment for translation.

The BEHAVE WG will design solutions for the following four translation
scenarios; other scenarios are out of scope:

1. An IPv6 network 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 an IPv4 network, 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), e.g. the IPv4 hosts that
are to be reachable over IPv6 can be enumerated. The WG should
attempt to design a simpler solution with less impact on
applications.

3. An IPv4 network 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 an IPv6 network, 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, unless they prevent a timely completion of the work
item. The fundamental parts of ICMP are also required to work.
Additional protocols directly on top of IP may be supported. Translation
mechanisms must handle IP 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 for
publication as standards track RFC. 
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Tue Oct 28 17:52:36 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FDEC28C1A4;
	Tue, 28 Oct 2008 17:52:36 -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 281273A6C00
	for <behave@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 zRzBD2GBa0cn for <behave@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.170])
	by core3.amsl.com (Postfix) with ESMTP id D6AC43A6A17
	for <behave@ietf.org>; Tue, 28 Oct 2008 17:52:33 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so3173953wfd.31
	for <behave@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: v4v6interim@ietf.org, 46translation@employees.org,
	'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Doesn't HIP solve this problem?
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-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
QmVoYXZlIG1haWxpbmcgbGlzdApCZWhhdmVAaWV0Zi5vcmcKaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9iZWhhdmUK


From behave-bounces@ietf.org  Tue Oct 28 22:17:14 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96A323A684E;
	Tue, 28 Oct 2008 22:17:14 -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 0907F3A684E
	for <behave@core3.amsl.com>; Tue, 28 Oct 2008 22:17:13 -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 7VkgBjUzzCkw for <behave@core3.amsl.com>;
	Tue, 28 Oct 2008 22:17:11 -0700 (PDT)
Received: from QMTA01.emeryville.ca.mail.comcast.net
	(qmta01.emeryville.ca.mail.comcast.net [76.96.30.16])
	by core3.amsl.com (Postfix) with ESMTP id DFC163A6801
	for <behave@ietf.org>; Tue, 28 Oct 2008 22:17:11 -0700 (PDT)
Received: from OMTA02.emeryville.ca.mail.comcast.net ([76.96.30.19])
	by QMTA01.emeryville.ca.mail.comcast.net with comcast
	id YTyV1a0060QkzPwA1VHA6p; Wed, 29 Oct 2008 05:17:10 +0000
Received: from [10.36.0.45] ([76.119.58.152])
	by OMTA02.emeryville.ca.mail.comcast.net with comcast
	id YVH71a0083H3vh08NVH88u; Wed, 29 Oct 2008 05:17:09 +0000
X-Authority-Analysis: v=1.0 c=1 a=qXtqn8Pk-tcA:10 a=oZwnVYdGwtoA:10
	a=b41qRHdkxu5hypAdgigA:9 a=lLVvPY3NleDSj4OOCscA:7
	a=r_HzKEVZ9Tc7AnLTaNgRa9-1IW8A:4 a=pQ5v7ofoLL0A:10
Message-Id: <BB700DFF-D3C9-4794-866F-E0E3966D3608@lilacglade.org>
From: Margaret Wasserman <mrw@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <D41DAFEC-1D0D-4DE5-8428-736D175C938A@lilacglade.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 01:17:06 -0400
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
	<49076EA6.3040802@sri.com>
	<D41DAFEC-1D0D-4DE5-8428-736D175C938A@lilacglade.org>
X-Mailer: Apple Mail (2.929.2)
Cc: Behave WG <behave@ietf.org>, Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


Actually, let me respond to one of your points here:

On Oct 28, 2008, at 4:05 PM, Margaret Wasserman wrote:
>> 2.  Motivation:  subtle difference between "not recommending the  
>> use of NAT" and "recommending not having NAT66" but overall the  
>> draft seems to lean towards "not recommending" rather than  
>> "recommending not".  Hence the definition of a "safer" way of doing  
>> it if you must?

Yes, that is the point I am trying to make.  I've tried to strike a  
balance between making it clear that we don't recommend NAT and  
pointing to alternatives vs. making to clear that we understand that  
there are some reasons why people will choose to use NAT66 and  
offering a way to implement one that is less harmful and more  
functional than traditional NAT44.  Maybe I didn't strike that balance  
correctly...

>>  This explains the motivation for the draft, but the draft does not  
>> give convincing motivation FOR using NAT66.  It seems like having  
>> both a ULA and global unicast address on an interface allows use of  
>> ULA for local traffic and the global otherwise.

No, not so.  The use of both ULAs and global addresses does allow  
local traffic to use local addresses (in most cases) and external  
traffic to use external addresses.  However, it still requires that  
the external, provider-allocated addresses be configured throughout  
the network (in routers, in DHCP servers, in security ACLs, etc.), and  
that they be exposed to external nodes in the DNS, etc.  It also  
requires that every node in the network make the "right" choice about  
whether to use a local or global address for communication with both  
local and global nodes, something that we've struggled with how to do  
correctly in IPv6.

There are many enterprise networks that have plenty of IPv4 addresses  
available to them who choose to use NAT44, anyway.  When we've talked  
to these people about why they use NAT44, they have pointed to several  
different reasons, the four most common/compelling of which are:  (1)  
provider independent internal addressing -- no need to renumber to  
change ISP, ISP can't force renumbering even by going out of business,  
etc. (2)  topology hiding -- a desire to hide their internal network  
structure/subnetting plan from the outside world, (3) site multihoming  
-- they want to connect their site to two different providers without  
having to get those providers to coordinate on using a single global  
address prefix for their site, without the complexity of using  
multiple address prefixes internally, and/or (4) "security" --  
referring to the fact that a NAT44 box effectively blocks inbound  
connections.

RFC4864 talks about all of the "benefits" of NAT and how they can be  
obtained in IPv6.  However, it contains no real answer for (1)  
provider independent addressing, which is an even wider issue in IPv6,  
as many sites that have their own IPv4 addresses today will not be  
able to get their own global IPv6 address prefix.  It says "use ULAs"  
as though that solves the independent addressing issue, when it  
doesn't, as every node that wishes to communicate on the global  
Internet will also need a global unicast address.  The answers for (2)  
topology hiding are more fleshed out, but there is no reason to  
believe that administrators will prefer them to NAT.  The solutions  
rely on RFC 3041, which is not widely implemented and, even if it  
were, only solves a small part of the problem, because it only works  
for connections where the internal nodes initiates the connection, and  
it is only used when an application requests an RFC 3041 address,  
which virtually no applications do today.  Randomizing subnets does  
not help at all if the knowledge of the internal structure is gathered  
by observing traffic entering and exiting the site.  There are also  
some other methods discussed in the document, but most or all of those  
methods are just as possible in IPv4, and they have not been preferred  
over NAT44 by people who actually deploy enterprise networks.  
Regarding (3) site multihoming, RFC 4864 makes it clear that IPv6 has  
no real solution to this problem.  Work is underway on a shim6-based  
solution, but shim6 will require changes in every host, and it is not  
yet clear that it will be widely implemented or deployed.  I think we  
all know that NAT doesn't provide any real "security", but it does  
provide something similar to an inflexible stateful firewall  
function.  This behavior is important enough to enterprise  
administrators that people who produce IPv6 routers have pretty much  
been forced to include a stateful firewall in their products that  
defaults to essentially the same behavior as a NAT44 device.  That  
seems to solve the problem pretty well, so I don't think it is  
necessary that NAT66 have the same firewall-like side effect as NAT44.

>>  Topology hiding is already provided in RFC 4864.  I'm not invoking  
>> the third rail, but I think the draft should provide some good  
>> reasons or scenarios when use of NAT66 would be a reasonable  
>> alternative.

Do the above arguments make sense to you?   I didn't include this type  
of text in the draft, because I don't want to get into an argument  
about whether this draft or RFC4864 is more correct.  RFC4864 explains  
how you can do a number of things without deploying NAT66, and you  
can.  What it doesn't explain is why people will take those steps to  
avoid deploying NAT66, when they haven't been willing to take some of  
the same steps to avoid deploying NAT44.  In fact, most of the people  
I know who run NAT44-based networks in their homes or enterprises are  
quite happy with them.

This is a long story that tries to explain why I think people _will_  
deploy NAT66, even though we'd prefer that they didn't.  Given that I  
believe that it is inevitable that NAT66 will be widely deployed, I'd  
like to try to get the folks who implement it to do it in a way that  
has fewer problems and less negative impact on the IPv6 Internet than  
NAT44 does.

How much of this does it make sense to include in the draft?

Margaret
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Wed Oct 29 04:45:03 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C38828C2DB;
	Wed, 29 Oct 2008 04:45:03 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 71F083A69F5; Wed, 29 Oct 2008 04:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081029114501.71F083A69F5@core3.amsl.com>
Date: Wed, 29 Oct 2008 04:45:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-turn-ipv6-05.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Traversal Using Relays around NAT (TURN) Extension for IPv4/IPv6 Transition
	Author(s)       : G. Camarillo, O. Novo
	Filename        : draft-ietf-behave-turn-ipv6-05.txt
	Pages           : 10
	Date            : 2008-10-29

This document defines the REQUESTED-ADDRESS-TYPE attribute for
Traversal Using Relays around NAT (TURN).  The REQUESTED-ADDRESS-TYPE
attribute allows a client to explicitly request the address type the
TURN server will allocate (e.g., an IPv4-only node may request the
TURN server to allocate an IPv6 address).  Additionally, this
document also defines a new error response code with the value 440
(Address Family not Supported).

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-turn-ipv6-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From behave-bounces@ietf.org  Wed Oct 29 05:33:30 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E442528C377;
	Wed, 29 Oct 2008 05:33:30 -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 3041E28C377
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 05:33:30 -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 8K2Qxdg4HQDV for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 05:33:29 -0700 (PDT)
Received: from mail-07.primus.ca (mail6.primus.ca [216.254.141.173])
	by core3.amsl.com (Postfix) with ESMTP id 6569B28C363
	for <behave@ietf.org>; Wed, 29 Oct 2008 05:33:29 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1KvAEk-0000BW-0P
	for behave@ietf.org; Wed, 29 Oct 2008 08:33:22 -0400
Message-Id: <DE2D74EC-72AC-413F-8481-93156A438E24@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 08:33:27 -0400
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Subject: [BEHAVE] TURN: Restricting who a server will relay to
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I have added a few sentences to TURN that explicitly allows a server  
to restrict the range of IP addresses and ports that it will relay to.  
More precisely, restrict the range of IP addresses and ports that can  
appear in an XOR-PEER-ADDRESS attribute in a CreatePermission,  
ChannelBind, or Send. For Send, for example, the text now says:

    The server MAY impose additional restrictions on the range of values
    allowed for the IP address and port contained in the XOR-PEER- 
ADDRESS
    attribute.

This was prompted by my updating of the TURN security considerations  
section to discuss the attack that Cullen raised a couple of weeks  
ago, where a TURN server is located in the DMZ.

I don't see this as adding anything new. An administrator can always  
achieve the same affect by placing the TURN server behind its own  
firewall and configuring the firewall rules appropriately. And even if  
it wasn't explicitly allowed, I suspect that many TURN implementations  
might do it anyway.

Comments?

- Philip


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


From behave-bounces@ietf.org  Wed Oct 29 06:15:02 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0CC683A69DF;
	Wed, 29 Oct 2008 06:15:02 -0700 (PDT)
X-Original-To: behave@ietf.org
Delivered-To: behave@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id A52C23A69DF; Wed, 29 Oct 2008 06:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081029131501.A52C23A69DF@core3.amsl.com>
Date: Wed, 29 Oct 2008 06:15:01 -0700 (PDT)
Cc: behave@ietf.org
Subject: [BEHAVE] I-D Action:draft-ietf-behave-turn-11.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Behavior Engineering for Hindrance Avoidance Working Group of the IETF.


	Title           : Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
	Author(s)       : J. Rosenberg, et al.
	Filename        : draft-ietf-behave-turn-11.txt
	Pages           : 72
	Date            : 2008-10-29

If a host is located behind a NAT, then in certain situations it can
be impossible for that host to communicate directly with other hosts
(peers).  In these situations, it is necessary for the host to use
the services of an intermediate node that acts as a communication
relay.  This specification defines a protocol, called TURN (Traversal
Using Relays around NAT), that allows the host to control the
operation of the relay and to exchange packets with its peers using
the relay.  TURN differs from some other relay control protocols in
that it allows a client to communicate with multiple peers using a
single relay address.

The TURN protocol was designed to be used as part of the ICE
(Interactive Connectivity Establishment) approach to NAT traversal,
though it can be also used without ICE.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-behave-turn-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-behave-turn-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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

--NextPart--


From behave-bounces@ietf.org  Wed Oct 29 06:15:55 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 814E028C2E3;
	Wed, 29 Oct 2008 06:15:55 -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 A157928C2DB
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 06:15:54 -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 3IQxAVH6xVXg for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 06:15:53 -0700 (PDT)
Received: from mail-07.primus.ca (mail6.primus.ca [216.254.141.173])
	by core3.amsl.com (Postfix) with ESMTP id 8E9A83A6BED
	for <behave@ietf.org>; Wed, 29 Oct 2008 06:15:31 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-07.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>) id 1KvAtP-0005zB-34
	for behave@ietf.org; Wed, 29 Oct 2008 09:15:24 -0400
Message-Id: <CD2563CD-664C-47DD-9FA8-6ECA45EBE100@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: BEHAVE WG <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 09:15:28 -0400
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Subject: [BEHAVE] Version -11 of TURN posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I have posted a new version of TURN (draft-ietf-behave-turn-11) to the  
IETF servers. This version addresses a number of issues raised in  
reviews of TURN-10 by various people. Thanks to Dan Wing, Cullen  
Jennings, Magnus Westerlund, and Marc Petit-Huguenin for their  
reviews. The major technical changes in this version have all been  
discussed on the mailing list.

As far as I am aware, there are no outstanding issues with this  
version of TURN.

A complete list of the changes in the document are copied below, and  
can also be found in the document itself.

- Philip

21.1.  Changes from -10 to -11

    o  Clarified that, when the client is redirected to an alternate
       server, the client uses the same transport protocol to the
       alternate server as it did to the original server.

    o  Clarified the information that the server needs to store to
       authenticate requests and to compute the message-integrity on
       responses.  Noted that the server need not store the password
       explicitly, but can instead store the key value, which may be
       desirable for security reasons.

    o  Clarified that TURN runs on the same ports as TURN by default,  
but
       noted that a server can use a different port because TURN has its
       own SRV service names.  Strenghened the language for using the  
SRV
       procedures from "typically" to "SHOULD".  Also added a sentence  
in
       the IANA considerations section requesting that IANA reserve the
       service names for TURN; previously they were described in the  
text
       but not mentioned in the IANA considerations section.

    o  Added a detailed example, complete with attributes and their
       values, of the use of TURN.

    o  Reduced the range of channel numbers.  Channel numbers now range
       from 0x4000 through 0x7FFF.  Values in the range 0x8000 through
       0xFFFF are now reserved.

    o  Rewrote the IAB Considerations section to directly address the
       considerations listed in [RFC3424].

    o  Generalized the 508 error code so it can be used for any sort of
       capacity-related problem.  This error code was previously allowed
       only in Allocate responses, but is now also allowed in
       CreatePermission and ChannelBind responses to indicate that the
       server is unable to carry out the request due to some capacity
       problem.

    o  Changed the syntax of the CreatePermission request to allow
       multiple XOR-PEER-ADDRESS attributes to appear in the message, so
       that multiple permissions can be created or refreshed at the same
       time.

    o  Added the restriction that the server must already have a
       permission installed for the IP address in the XOR-PEER-ADDRESS
       attribute of a Send indication, otherwise the Send indication is
       ignored by the server.

    o  Put back the preferred behaviors into Section 12, reversing the
       change made in version -10.

    o  Explicitly allow the server to restrict the range of IP addresses
       and ports it is willing to relay data too.





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


From behave-bounces@ietf.org  Wed Oct 29 07:52:42 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E6C628C3AD;
	Wed, 29 Oct 2008 07:52:42 -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 61EFC28C3AE
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 07:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[AWL=0.938, 
	BAYES_00=-2.599, HELO_EQ_FR=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 xwp5h-kx7wRs for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 07:52:40 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com
	[195.101.245.15])
	by core3.amsl.com (Postfix) with ESMTP id A8B9328C391
	for <behave@ietf.org>; Wed, 29 Oct 2008 07:52:39 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 15:52:33 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 15:52:26 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB4C944@ftrdmel1>
In-Reply-To: <00b001c9392e$cf656f60$c3f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: BitTorrent with shared IP addresses [was RE: [BEHAVE] TR: I-D
	Action:draft-boucadair-port-range-00.txt]
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZAAMsaucAApJfBg
From: <pierre.levis@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 29 Oct 2008 14:52:33.0592 (UTC)
	FILETIME=[F9A4E380:01C939D5]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] BitTorrent with shared IP addresses [was RE: TR: I-D
	Action:draft-boucadair-port-range-00.txt]
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

Dan,

Yes, the test you carried out work also in our lab (I have tested the same =
torrent download as yours on two different PCs sharing the same IP address).

In fact, the result we have mentionned in our draft is from another test wh=
ich is much more constrained:

"For one P2P (Peer-to-Peer) application tested, we found that two
   peers each behind a CPE sharing the same public address cannot
   download a SAME file from a source peer."

By "SAME file from a source peer" we mean a single file on a single locatio=
n.
Then, the two PCs with the same IP address tried to download the file from =
the very same location, by BitTorrent.

So, of course we cannot say that it does not work at all, we can only say t=
hat it does not work in these very particular conditions.


Pierre


-----Message d'origine-----
De : Dan Wing [mailto:dwing@cisco.com] =

Envoy=E9 : mardi 28 octobre 2008 19:56
=C0 : LEVIS Pierre RD-CORE-CAE
Cc : behave@ietf.org
Objet : BitTorrent with shared IP addresses [was RE: [BEHAVE] TR: I-D Actio=
n:draft-boucadair-port-range-00.txt]

Pierre,

I decided to test how BitTorrent works with two clients behind the same IP =
address.  My results show that it works fine.  I tested by running both uTo=
rrent and Vuze (formerly called Azureus) on the same Windows PC, with one
IPv4 address towards the Internet (my trusty Linksys WRT54G running Tomato =
3rd party firmware).

For my torrent download, I used 2.9Gb copy of Wikipedia was recently made a=
vailable, http://www.soschildrensvillages.org.uk/charity-news/2008-wikipedi=
a-for-schools
.htm#download

Can you provide details on the test you performed that showed "one of the m=
ost commonly used p2p applications" did not work at all when two hosts shar=
ed the same IP address?  I am now suspicious it was the tracker causing the=
 restriction you observed, and not the BitTorrent protocol itself.

-d


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, October 27, 2008 11:38 AM
> To: 'pierre.levis@orange-ftgroup.com'; 'behave@ietf.org'
> Subject: RE: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
> =

> I will go out on a limb, for the benefit of anyone reading these =

> archives in 5 years, that the application must be BitTorrent.
> =

> Assuming that is correct, the probably reason BitTorrent prevents =

> simultaneous downloading by two hosts with the same identifier (IP =

> address) is to provide fairer bandwidth sharing.  Without such =

> protection, you could get 2x download speed for a file if a person's =

> two BitTorrent clients happened to download from completely different =

> peers.
> =

> -d
> =

> =

> > -----Original Message-----
> > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of =

> > pierre.levis@orange-ftgroup.com
> > Sent: Monday, October 27, 2008 7:14 AM
> > To: behave@ietf.org
> > Subject: Re: [BEHAVE] TR: I-D
> Action:draft-boucadair-port-range-00.txt
> > =

> > Hi R=E9mi,
> >  =

> > Thank you for your careful reading.
> >  =

> > This is one of the most commonly used p2p application!
> > More seriously, we're bound to have the same issue as soon as we do =

> > address sharing, no matter the mechanism. So, I would say that it =

> > should not work accross a Carrier Grade NAT.
> >  =

> >  =

> > Regards,
> >  =

> >  =

> > Pierre
> > =

> > ________________________________
> > =

> > De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr] Envoy=E9 : lundi 27 =

> > octobre 2008 09:39 =C0 : LEVIS Pierre RD-CORE-CAE Cc : behave@ietf.org =

> > Objet : Re: [BEHAVE] TR: I-D
> Action:draft-boucadair-port-range-00.txt
> > =

> > =

> > Hi Pierre,
> > =

> > I find the draft most interesting, in particular the real experiment =

> > it describes .
> > =

> > In sec 4.4  it says :"For one P2P (Peer-to-Peer) application tested, =

> > we found that two  peers each behind a CPE sharing the same public =

> > address cannot  download a SAME file from a source peer."
> > - Is there a problem in telling  which application this is?
> > - Do we know if this application works (for the same file) across =

> > NATs, and if yes how?
> > =

> > Regards,
> > =

> > RD
> > =

> > =

> > =

> > =

> > pierre.levis@orange-ftgroup.com   (m/j/a) 10/24/08 3:16 PM: =

> > =

> > 	Hi all,
> > 	=

> > 	I would like to draw your attention on the following draft.
> > 	=

> > 	We (the authors) are looking forward to reading your comments.
> > 	=

> > 	=

> > 	Regards
> > 	=

> > 	=

> > 	Pierre
> > 	=

> > 	=

> > 	=

> > 	-----Message d'origine-----
> > 	De : i-d-announce-bounces@ietf.org =

> > [mailto:i-d-announce-bounces@ietf.org] De la part de =

> > Internet-Drafts@ietf.org
> > 	Envoy=E9 : jeudi 23 octobre 2008 14:45
> > 	=C0 : i-d-announce@ietf.org
> > 	Objet : I-D Action:draft-boucadair-port-range-00.txt
> > 	=

> > 	A New Internet-Draft is available from the on-line Internet-Drafts =

> > directories.
> > 	=

> > 		Title           : Provider-Provisioned CPE: =

> > IPv4 Connectivity Access in the context of IPv4 address exhaustion
> > 		Author(s)       : M. Boucadair, et al.
> > 		Filename        : draft-boucadair-port-range-00.txt
> > 		Pages           : 33
> > 		Date            : 2008-10-23
> > 	=

> > 	This memo proposes a solution, based on fractional addresses, to =

> > face the IPv4 public address exhaustion.  It details the solution =

> > and presents a mock-up implementation, with the results of tests =

> > that validate the concept.
> > Finally, it makes a comparison with the alternative Carrier-Grade =

> > NAT (CG-NAT) solutions.
> > 	=

> > 	A URL for this Internet-Draft is:
> > 	=

> > =

> http://www.ietf.org/internet-drafts/draft-boucadair-port-range-00.txt
> > 	=

> > 	Internet-Drafts are also available by anonymous FTP at:
> > 	ftp://ftp.ietf.org/internet-drafts/
> > 	=

> > 	Below is the data which will enable a MIME compliant mail reader =

> > implementation to automatically retrieve the ASCII version of the =

> > Internet-Draft.
> > 	  =

> > 	=

> > ________________________________
> > =

> > =

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

> > =

> > =

> > =

> =


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


From behave-bounces@ietf.org  Wed Oct 29 08:55:05 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 769863A69F0;
	Wed, 29 Oct 2008 08:55:05 -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 030093A69EE
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 08:55:04 -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 wUZ-uP8oAlNO for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 08:55:03 -0700 (PDT)
Received: from dizzyd.com (dizzyd.com [207.210.219.225])
	by core3.amsl.com (Postfix) with ESMTP id 528023A69C0
	for <behave@ietf.org>; Wed, 29 Oct 2008 08:55:03 -0700 (PDT)
Received: from wrk225.corp.jabber.com (dencfw1.jabber.com [207.182.164.5])
	(Authenticated sender: stpeter)
	by dizzyd.com (Postfix) with ESMTPSA id 8E07C40128
	for <behave@ietf.org>; Wed, 29 Oct 2008 09:50:49 -0600 (MDT)
Message-ID: <49088754.9040806@stpeter.im>
Date: Wed, 29 Oct 2008 09:55:00 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.1.17) Gecko/20080914 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: 'Behave WG' <behave@ietf.org>
X-Enigmail-Version: 0.95.7
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Subject: [BEHAVE] Happy ICE-iversary!
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

I notice that draft-ietf-mmusic-ice-19 was published a year ago today.
Here's hoping that someday it will become an RFC! :)

Peter


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


From behave-bounces@ietf.org  Wed Oct 29 10:35:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E39D43A6CB7;
	Wed, 29 Oct 2008 10:35:17 -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 E4E6928C186
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 10:35:16 -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 5R8tFD67zg7f for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 10:35:16 -0700 (PDT)
Received: from mail-05.primus.ca (mail6.primus.ca [216.254.141.173])
	by core3.amsl.com (Postfix) with ESMTP id 42EBD3A6C7E
	for <behave@ietf.org>; Wed, 29 Oct 2008 10:35:16 -0700 (PDT)
Received: from [24.139.16.154] (helo=[10.0.1.3])
	by mail-05.primus.ca with esmtpa (Exim 4.63)
	(envelope-from <philip_matthews@magma.ca>)
	id 1KvEuP-0005Uf-0t; Wed, 29 Oct 2008 13:32:41 -0400
Message-Id: <EE5B39C8-E585-47C8-8375-BE0B226CFAA0@magma.ca>
From: Philip Matthews <philip_matthews@magma.ca>
To: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <49088754.9040806@stpeter.im>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 13:34:41 -0400
References: <49088754.9040806@stpeter.im>
X-Mailer: Apple Mail (2.929.2)
X-Authenticated: philip_matthews@magma.ca - ([10.0.1.3]) [24.139.16.154]
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Happy ICE-iversary!
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

ICE depends on TURN. The ICE RFC cannot be published until the TURN  
RFC is published.
This is why there is a big push on to finish TURN.
- Philip

On Wed, 29-Oct-08, at 11:55 , Peter Saint-Andre wrote:

> I notice that draft-ietf-mmusic-ice-19 was published a year ago today.
> Here's hoping that someday it will become an RFC! :)
>
> Peter
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Wed Oct 29 11:22:53 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E1BA28C3AF;
	Wed, 29 Oct 2008 11:22:53 -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 CC95A28C3AF
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 11:22:52 -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 qopSHSNQDHeN for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 11:22:52 -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 C50643A6A7F
	for <behave@ietf.org>; Wed, 29 Oct 2008 11:22:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,507,1220227200"; d="scan'208";a="99789084"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-2.cisco.com with ESMTP; 29 Oct 2008 18:22:33 +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 m9TIMYwC017700; 
	Wed, 29 Oct 2008 11:22:34 -0700
Received: from dwingwxp01 (dhcp-128-107-114-36.cisco.com [128.107.114.36])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9TIMIXa016763;
	Wed, 29 Oct 2008 18:22:33 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pierre.levis@orange-ftgroup.com>
References: <00b001c9392e$cf656f60$c3f0200a@cisco.com>
	<D109C8C97C15294495117745780657AE0AB4C944@ftrdmel1>
Date: Wed, 29 Oct 2008 11:22:18 -0700
Message-ID: <000201c939f3$50f9bcb0$24726b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZAAMsaucAApJfBgAAeGGXA=
In-Reply-To: <D109C8C97C15294495117745780657AE0AB4C944@ftrdmel1>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1830; t=1225304554;
	x=1226168554; 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=20BitTorrent=20with=20shared=20IP=20addre
	sses |Sender:=20;
	bh=/SVUpFbusjNAGPqTZmW+Tl5N6JYY8oYjDZnJ0Hb3M00=;
	b=WcrNCLdntbuZZ/8zIYh2m6pQ0NU1XB/B6DSyaPcCQm0U2xpCqQG7oQ882W
	CgdSIwk5qFTDTPvphcpl9yb3NEpUAvb9GdVkGvOCWxo02kDbcYjp/P8hPRSE
	zXSalLT2mZ;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] BitTorrent with shared IP addresses
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

 

> -----Original Message-----
> From: pierre.levis@orange-ftgroup.com 
> [mailto:pierre.levis@orange-ftgroup.com] 
> Sent: Wednesday, October 29, 2008 7:52 AM
> To: dwing@cisco.com
> Cc: behave@ietf.org
> Subject: RE: BitTorrent with shared IP addresses [was RE: 
> [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt]
> 
> Dan,
> 
> Yes, the test you carried out work also in our lab (I have 
> tested the same torrent download as yours on two different 
> PCs sharing the same IP address).
> 
> In fact, the result we have mentionned in our draft is from 
> another test which is much more constrained:
> 
> "For one P2P (Peer-to-Peer) application tested, we found that two
>    peers each behind a CPE sharing the same public address cannot
>    download a SAME file from a source peer."
> 
> By "SAME file from a source peer" we mean a single file on a 
> single location.
> Then, the two PCs with the same IP address tried to download 
> the file from the very same location, by BitTorrent.
>
> So, of course we cannot say that it does not work at all, we 
> can only say that it does not work in these very particular 
> conditions.

Ah, okay.  So the failure occurs when a file that has only one 
seed in the BitTorrent swarm, like this:


             PC-A--+
                    \
                     NAT--seed
                    /
             PC-B--+


And PC-A is able to download the file, but PC-B can't download
the file.  

What happens after PC-A completes downloading the file --
can PC-B start downloading it immediately after PC-A finishes?  
Perhaps after the next tracker update, can PC-B start downloading 
it?   Or does your testing show that PC-B is *never* able to 
download the file because PC-A already downloaded it from the 
seed?

-d


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


From behave-bounces@ietf.org  Wed Oct 29 11:24:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FC1C28C3C0;
	Wed, 29 Oct 2008 11:24: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 C9C7128C37A
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 11:24: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 K4szB1RA7tnY for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 11:24:25 -0700 (PDT)
Received: from dizzyd.com (dizzyd.com [207.210.219.225])
	by core3.amsl.com (Postfix) with ESMTP id D4BEF28C3C5
	for <behave@ietf.org>; Wed, 29 Oct 2008 11:24:22 -0700 (PDT)
Received: from wrk225.corp.jabber.com (dencfw1.jabber.com [207.182.164.5])
	(Authenticated sender: stpeter)
	by dizzyd.com (Postfix) with ESMTPSA id 6719040128;
	Wed, 29 Oct 2008 12:20:02 -0600 (MDT)
Message-ID: <4908AA4B.8020204@stpeter.im>
Date: Wed, 29 Oct 2008 12:24:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.1.17) Gecko/20080914 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Philip Matthews <philip_matthews@magma.ca>
References: <49088754.9040806@stpeter.im>
	<EE5B39C8-E585-47C8-8375-BE0B226CFAA0@magma.ca>
In-Reply-To: <EE5B39C8-E585-47C8-8375-BE0B226CFAA0@magma.ca>
X-Enigmail-Version: 0.95.7
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Cc: 'Behave WG' <behave@ietf.org>
Subject: Re: [BEHAVE] Happy ICE-iversary!
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Yes, I know, unfortunate but true. I'll give the TURN I-D another
reading here soon...

Philip Matthews wrote:
> ICE depends on TURN. The ICE RFC cannot be published until the TURN RFC
> is published.
> This is why there is a big push on to finish TURN.
> - Philip
> 
> On Wed, 29-Oct-08, at 11:55 , Peter Saint-Andre wrote:
> 
>> I notice that draft-ietf-mmusic-ice-19 was published a year ago today.
>> Here's hoping that someday it will become an RFC! :)
>>
>> Peter
>>

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


From behave-bounces@ietf.org  Wed Oct 29 15:00:24 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32FFC28C3FD;
	Wed, 29 Oct 2008 15:00:24 -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 4503E28C403
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 15:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5
	tests=[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 2kLQgfPPKXFI for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 15:00:22 -0700 (PDT)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM
	[128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id 38AB728C3FD
	for <behave@ietf.org>; Wed, 29 Oct 2008 15:00:21 -0700 (PDT)
Received: from smssmtp-internal1.sri.com (128.18.84.115)
	by mailgate-internal3.sri.com with SMTP; 29 Oct 2008 22:00:19 -0000
X-AuditID: 80125473-ac4e4bb000000a55-af-4908dcf3d90c
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id
	2E0A821AF2D
	for <behave@ietf.org>; Wed, 29 Oct 2008 15:00:19 -0700 (PDT)
Received: from [192.168.1.2] (nj-76-1-240-80.dhcp.embarqhsd.net [76.1.240.80])
	by mail.sri.com
	(Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with
	ESMTPSA id <0K9I008IVT4I3H80@mail.sri.com> for behave@ietf.org; Wed,
	29 Oct 2008 15:00:19 -0700 (PDT)
Date: Wed, 29 Oct 2008 18:00:17 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <BB700DFF-D3C9-4794-866F-E0E3966D3608@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
Message-id: <4908DCF1.8060707@sri.com>
MIME-version: 1.0
References: <20081027185105.E7CD03A6B88@core3.amsl.com>
	<D0E80AE6-C5B5-4EBC-AAD8-8F0B058E1BFB@lilacglade.org>
	<49076EA6.3040802@sri.com>
	<D41DAFEC-1D0D-4DE5-8428-736D175C938A@lilacglade.org>
	<BB700DFF-D3C9-4794-866F-E0E3966D3608@lilacglade.org>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: Behave WG <behave@ietf.org>
Subject: Re: [BEHAVE] draft-mrw-behave-nat66-00.txt is now posted
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

thanks for your thoughtful response.  I guess I could have refreshed on 
the details of 4864 before chiming in.  In general, I support this 
document and see it as a necessary evil, and agree that it should be 
complementary to 4864, not replacing or refuting it.  Nothing to be 
gained by ignoring and forbidding the use of IPv6 NAT if it's going to 
happen anyway.

See some follow-up in-line.

Margaret Wasserman wrote:
>
> Actually, let me respond to one of your points here:
>
> On Oct 28, 2008, at 4:05 PM, Margaret Wasserman wrote:
>>> 2.  Motivation:  subtle difference between "not recommending the use 
>>> of NAT" and "recommending not having NAT66" but overall the draft 
>>> seems to lean towards "not recommending" rather than "recommending 
>>> not".  Hence the definition of a "safer" way of doing it if you must?
>
> Yes, that is the point I am trying to make.  I've tried to strike a 
> balance between making it clear that we don't recommend NAT and 
> pointing to alternatives vs. making to clear that we understand that 
> there are some reasons why people will choose to use NAT66 and 
> offering a way to implement one that is less harmful and more 
> functional than traditional NAT44.  Maybe I didn't strike that balance 
> correctly...
Perhaps be more explicit - replace the first sentence of the second 
paragraph of Motivations with three points:  The IETF does not recommend 
the use of NAT in IPv6 networks [is there a citation?]. Some deployments 
will choose to use an IPv6 NAT as an alternative or complement to the 
methods defined in [RFC 4864].  It is important to understand the impact 
of this decision and the intention of this document is to  provided 
guidance to the design and deployment of NAT66 to avoid the drawbacks of 
NAT44.
>
>>>  This explains the motivation for the draft, but the draft does not 
>>> give convincing motivation FOR using NAT66.  It seems like having 
>>> both a ULA and global unicast address on an interface allows use of 
>>> ULA for local traffic and the global otherwise.
>
> No, not so.  The use of both ULAs and global addresses does allow 
> local traffic to use local addresses (in most cases) and external 
> traffic to use external addresses.  However, it still requires that 
> the external, provider-allocated addresses be configured throughout 
> the network (in routers, in DHCP servers, in security ACLs, etc.), and 
> that they be exposed to external nodes in the DNS, etc.  It also 
> requires that every node in the network make the "right" choice about 
> whether to use a local or global address for communication with both 
> local and global nodes, something that we've struggled with how to do 
> correctly in IPv6.
>
> There are many enterprise networks that have plenty of IPv4 addresses 
> available to them who choose to use NAT44, anyway.  When we've talked 
> to these people about why they use NAT44, they have pointed to several 
> different reasons, the four most common/compelling of which are:  (1) 
> provider independent internal addressing -- no need to renumber to 
> change ISP, ISP can't force renumbering even by going out of business, 
> etc. (2)  topology hiding -- a desire to hide their internal network 
> structure/subnetting plan from the outside world, (3) site multihoming 
> -- they want to connect their site to two different providers without 
> having to get those providers to coordinate on using a single global 
> address prefix for their site, without the complexity of using 
> multiple address prefixes internally, and/or (4) "security" -- 
> referring to the fact that a NAT44 box effectively blocks inbound 
> connections.
>
> RFC4864 talks about all of the "benefits" of NAT and how they can be 
> obtained in IPv6.  However, it contains no real answer for (1) 
> provider independent addressing, which is an even wider issue in IPv6, 
> as many sites that have their own IPv4 addresses today will not be 
> able to get their own global IPv6 address prefix.  It says "use ULAs" 
> as though that solves the independent addressing issue, when it 
> doesn't, as every node that wishes to communicate on the global 
> Internet will also need a global unicast address.  The answers for (2) 
> topology hiding are more fleshed out, but there is no reason to 
> believe that administrators will prefer them to NAT.  The solutions 
> rely on RFC 3041, which is not widely implemented and, even if it 
> were, only solves a small part of the problem, because it only works 
> for connections where the internal nodes initiates the connection, and 
> it is only used when an application requests an RFC 3041 address, 
> which virtually no applications do today.  Randomizing subnets does 
> not help at all if the knowledge of the internal structure is gathered 
> by observing traffic entering and exiting the site.  There are also 
> some other methods discussed in the document, but most or all of those 
> methods are just as possible in IPv4, and they have not been preferred 
> over NAT44 by people who actually deploy enterprise networks. 
> Regarding (3) site multihoming, RFC 4864 makes it clear that IPv6 has 
> no real solution to this problem.  Work is underway on a shim6-based 
> solution, but shim6 will require changes in every host, and it is not 
> yet clear that it will be widely implemented or deployed.  I think we 
> all know that NAT doesn't provide any real "security", but it does 
> provide something similar to an inflexible stateful firewall 
> function.  This behavior is important enough to enterprise 
> administrators that people who produce IPv6 routers have pretty much 
> been forced to include a stateful firewall in their products that 
> defaults to essentially the same behavior as a NAT44 device.  That 
> seems to solve the problem pretty well, so I don't think it is 
> necessary that NAT66 have the same firewall-like side effect as NAT44.
>
>>>  Topology hiding is already provided in RFC 4864.  I'm not invoking 
>>> the third rail, but I think the draft should provide some good 
>>> reasons or scenarios when use of NAT66 would be a reasonable 
>>> alternative.
>
> Do the above arguments make sense to you?   I didn't include this type 
> of text in the draft, because I don't want to get into an argument 
> about whether this draft or RFC4864 is more correct.  RFC4864 explains 
> how you can do a number of things without deploying NAT66, and you 
> can.  What it doesn't explain is why people will take those steps to 
> avoid deploying NAT66, when they haven't been willing to take some of 
> the same steps to avoid deploying NAT44.  In fact, most of the people 
> I know who run NAT44-based networks in their homes or enterprises are 
> quite happy with them.
>
> This is a long story that tries to explain why I think people _will_ 
> deploy NAT66, even though we'd prefer that they didn't.  Given that I 
> believe that it is inevitable that NAT66 will be widely deployed, I'd 
> like to try to get the folks who implement it to do it in a way that 
> has fewer problems and less negative impact on the IPv6 Internet than 
> NAT44 does.
>
> How much of this does it make sense to include in the draft?
There is no need to regurgitate large parts of RFC 4864 in the draft - 
but an annotated list of the recommendations made in 4864, identifying 
the relationship of the two documents as complementary, indicating where 
4864 provides the best approach, where this document provides an 
alternative to what is recommended there, and especially where this 
document fills gaps in 4864 - that would be sufficient.  Definitely less 
detail than the above, but guidance to the reader on using the two docs 
in parallel and choosing appropriate solution for their deployment.  
Don't absolve the reader of responsibility to read and understand 4864.  
One way to do it would be a table similar to the one in the intro to 
4864.  Either way, just enough to provide the context.  It's definitely 
more important to focus on the new material.

Thanks again.  I will plow through RFC 4864 again and see if I can come 
up with any more specific comments.
 
>
> Margaret
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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

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


From behave-bounces@ietf.org  Wed Oct 29 17:47:25 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A8243A6974;
	Wed, 29 Oct 2008 17:47:25 -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 7361E3A6974
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 17:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.687
X-Spam-Level: 
X-Spam-Status: No, score=-6.687 tagged_above=-999 required=5
	tests=[AWL=-0.087, 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 msbvr7w9+qGs for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 17:47:23 -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 944573A68F7
	for <behave@ietf.org>; Wed, 29 Oct 2008 17:47:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,510,1220227200"; d="scan'208";a="185193502"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 30 Oct 2008 00:47:22 +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 m9U0lMg4013831
	for <behave@ietf.org>; Wed, 29 Oct 2008 17:47:22 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9U0lMrY005300
	for <behave@ietf.org>; Thu, 30 Oct 2008 00:47:22 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Wed, 29 Oct 2008 17:47:21 -0700
Message-ID: <009e01c93a29$11f72710$24726b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack5TXS0F/hYcbkOQTm3WHspp0bTEQA2zCSA
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=929; t=1225327642; x=1226191642;
	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:=20IPR=20disclosure=20for=20draft-denis-behave-v4v
	6exthdr=20 |Sender:=20;
	bh=3Il9iGpulpTevmYEnupl3pC+i3YJr3P0BONqS9zXLy8=;
	b=JFnJdkyQwN8FoQK6YZWuZDM1bCJu0BJq/AAb6xhIiAyarvV3QB0SHGnMvT
	a1aYrOjaSj+qO8Y8lPcrj/YcToQt1gjeD7ywnUu7hSXXrgtQ9THRqnSua+8G
	TrGPBFCUuw;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Subject: [BEHAVE] IPR disclosure for draft-denis-behave-v4v6exthdr
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

draft-denis-behave-v4v6exthdr is not a BEHAVE working group document, but I
wanted to ensure that BEHAVE is aware of this IPR disclosure.

-d
 

-----Original Message-----
From: IETF Secretariat [mailto:ietf-ipr@ietf.org] 
Sent: Tuesday, October 28, 2008 3:35 PM
To: remi.denis-courmont@nokia.com
Cc: housley@vigilsec.com; dwing@cisco.com
Subject: Posting of IPR Disclosure

Dear Remi Denis-Courmont:

An IPR disclosure that pertains to your Internet-Draft entitled "IPv6
destination header option for IPv4 translator mapping notification"
(draft-denis-behave-v4v6exthdr) was submitted to the IETF Secretariat on
2008-10-24 and has been posted on the "IETF Page of Intellectual Property
Rights
Disclosures" (https://datatracker.ietf.org/public/ipr_list.cgi). The title of
the IPR disclosure is "Nokia Corporation 's Statement about IPR related to
draft-denis-behave-v4v6exthdr-00."

The IETF Secretariat


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


From behave-bounces@ietf.org  Wed Oct 29 20:43:48 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A719A3A6B3F;
	Wed, 29 Oct 2008 20:43:48 -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 BB1EE3A6B3F
	for <behave@core3.amsl.com>; Wed, 29 Oct 2008 20:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023, 
	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 7d00T4zcOM3I for <behave@core3.amsl.com>;
	Wed, 29 Oct 2008 20:43:47 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.224])
	by core3.amsl.com (Postfix) with ESMTP id 17A033A68B1
	for <behave@ietf.org>; Wed, 29 Oct 2008 20:43:47 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so348477rvf.49
	for <behave@ietf.org>; Wed, 29 Oct 2008 20:43: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:subject:references
	:in-reply-to:content-type:content-transfer-encoding;
	bh=AZ03w/Dz6xpiumU6MoxfQsWQL1TWdA3GX76bfHfhKbQ=;
	b=fnjYKn8lAI4kFC6851oKbaGhv9n+f3Rmj2RgtcNsLuBifVaw75sfzXpc7W0nfmN0cv
	omGYdCeoZsXM2pBAqbkI23dhRTskDaCnw0QmoKId/Qhqm6yGIfof1XiPP9n44Jx8cb0V
	v1B4MRheXOqMX4xZk1zfycWsBrLePxF8Y0APM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:organization:user-agent:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	b=VJB/RUBtRuyK69idg7AoZfwu/jI2wT7ys2EakZIQuULhS/94cnYm661XFnwEGSIDkx
	28VbdjxVMJa+R9hKnFzgvxYbRy77iLYxABQ4VNRyv9kWQqLmyqQtCj+0vUIMotw3RSRX
	YgeOiOFrJ/ccjraewJ+Kr/lUUwgpC9/Beh+Vw=
Received: by 10.114.210.2 with SMTP id i2mr7936893wag.18.1225338220703;
	Wed, 29 Oct 2008 20:43:40 -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 m30sm4310465wag.0.2008.10.29.20.43.39
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Oct 2008 20:43:40 -0700 (PDT)
Message-ID: <49092D69.4040909@gmail.com>
Date: Thu, 30 Oct 2008 16:43:37 +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: behave@ietf.org
References: <20081026141501.6F05F3A69EE@core3.amsl.com>
In-Reply-To: <20081026141501.6F05F3A69EE@core3.amsl.com>
Subject: Re: [BEHAVE] I-D Action:draft-baker-behave-v4v6-translation-00.txt
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi,

Should this be marked for the standards track
and as obsoleting RFC2765?

A couple of minor comments on the algorithms:

> 4.1.  Translating IPv4 Headers into IPv6 Headers
...
>    Flow Label:  0 (all zero bits)

Can we make this RECOMMENDED? I can't see any real
problem with a translator setting an actual value
for the flow label, and doing so wouldn't outrage
me as an author of RFC3697. So I don't think we
should make it completely invalid to do so.

> 5.1.  Translating IPv6 Headers into IPv4 Headers

For complete clarity, I suggest saying that
in this direction the flow label is dropped.

Nit: if this does obsolete RFC2765, the latter should
be an Informative reference.

    Brian

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


From behave-bounces@ietf.org  Thu Oct 30 03:30:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD4A53A698D;
	Thu, 30 Oct 2008 03:30:19 -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 90AC63A698D
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 03:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=0.625, 
	BAYES_00=-2.599, HELO_EQ_FR=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 iIE4Ihc-pbpA for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 03:30:17 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 685FE3A6881
	for <behave@ietf.org>; Thu, 30 Oct 2008 03:30:17 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 11:30:08 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C93A7A.7AB7831A"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 30 Oct 2008 11:30:07 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB4CD8F@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-boucadair-dhc-port-range-01.txt 
thread-index: Ack6XTu8x2thbHU5Q9KQzjX9sPH6rwAHIVSw
From: <pierre.levis@orange-ftgroup.com>
To: <behave@ietf.org>
X-OriginalArrivalTime: 30 Oct 2008 10:30:08.0369 (UTC)
	FILETIME=[7B2C4610:01C93A7A]
Cc: alain.villefranque@orange-ftgroup.com, mohamed.boucadair@orange-ftgroup.com,
	jeanluc.grimault@orange-ftgroup.com
Subject: [BEHAVE] TR: I-D Action:draft-boucadair-dhc-port-range-01.txt
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.

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

FYI

We have a companion draft to <draft-boucadair-port-range-00.txt> that =
describes new dhcp options for port allocation.

Comments welcome.

Pierre


-----Message d'origine-----
De : i-d-announce-bounces@ietf.org =
[mailto:i-d-announce-bounces@ietf.org] De la part de =
Internet-Drafts@ietf.org
Envoy=E9 : jeudi 30 octobre 2008 08:00
=C0 : i-d-announce@ietf.org
Objet : I-D Action:draft-boucadair-dhc-port-range-01.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts =
directories.

	Title           : DHCP Options for Conveying Port Mask and Port Range =
Router IP Address
	Author(s)       : M. Boucadair, et al.
	Filename        : draft-boucadair-dhc-port-range-01.txt
	Pages           : 15
	Date            : 2008-10-29

This draft defines two new DHCP (Dynamic Host Configuration Protocol,
[RFC2131]) Options to be used in the context of Provider-Provisioned CPE =
solution (a.k.a.  Port Range solution or Fractional Address).
The first option is used to convey a Port Mask and the second one may be =
used to convey a list of Port Range Router IP addresses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-boucadair-dhc-port-range-01.txt=


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader =
implementation to automatically retrieve the ASCII version of the =
Internet-Draft.

------_=_NextPart_001_01C93A7A.7AB7831A
Content-Type: application/octet-stream;
	name="draft-boucadair-dhc-port-range-01.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-boucadair-dhc-port-range-01.URL
Content-Disposition: attachment;
	filename="draft-boucadair-dhc-port-range-01.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1ib3VjYWRhaXItZGhjLXBvcnQtcmFuZ2UtMDEudHh0DQo=

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

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

------_=_NextPart_001_01C93A7A.7AB7831A--


From behave-bounces@ietf.org  Thu Oct 30 07:27:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4B3D3A689B;
	Thu, 30 Oct 2008 07:27:26 -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 441953A689B
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 07:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.205
X-Spam-Level: 
X-Spam-Status: No, score=-2.205 tagged_above=-999 required=5 tests=[AWL=0.394, 
	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 5Cvg3CtL5Lg1 for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 07:27:24 -0700 (PDT)
Received: from n2.nomadiclab.com (n2.nomadiclab.com
	[IPv6:2001:14b8:400:101::2])
	by core3.amsl.com (Postfix) with ESMTP id 2D2F63A688B
	for <behave@ietf.org>; Thu, 30 Oct 2008 07:27:24 -0700 (PDT)
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 596F81EF130;
	Thu, 30 Oct 2008 16:27:22 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1])
	by n2.nomadiclab.com (Postfix) with ESMTP id 184571EF12C;
	Thu, 30 Oct 2008 16:27:22 +0200 (EET)
Message-Id: <DB2AE4C3-DF3C-40CD-BDB1-EEC03695B80C@nomadiclab.com>
From: Christian Vogt <christian.vogt@nomadiclab.com>
To: 46Translation <46translation@employees.org>,
	Behave Mailing List <behave@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 16:27:21 +0200
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: Alain Durand <alain_durand@cable.comcast.com>, v6ops-ads@tools.ietf.org,
	6man-ads@tools.ietf.org, David Thaler <dthaler@microsoft.com>,
	Dan Wing <dwing@cisco.com>
Subject: [BEHAVE] New I-D: IPv4/IPv6 Translator for IPv4-Only Networks
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Folks,

at the IPv4/IPv6 co-existence interim, Alain and I had sketched a
translation-based IPv4/IPv6 interworking method that, unlike other
translation-based solution proposals, is for deployment in IPv4
networks.  Here is now a more detailed specification of this method,
which we call "Virtual IPv6 Connectivity for IPv4-only networks":

http://tools.ietf.org/html/draft-vogt-durand-virtual-ip6-connectivity

Recall from the interim:  The main advantage of Virtual IPv6
Connectivity is that it does not require extra global IPv4 addresses.
We hence believe that the method will be of advantage when (a) the pool
of unallocated IPv4 addresses is exhausted, and (b) there is sufficient
IPv6 deployment to make it worthwhile for IPv4 networks to invest into
IPv4/IPv6 interworking.  Consequently, Virtual IPv6 Connectivity is not
intended to replace any other solution proposal.  It is instead intended
to complement other solution proposals in a future where the impetus to
invest into IPv4/IPv6 interworking has shifted from the IPv6 side to the
IPv4 side.

Furthermore, Virtual IPv6 Connectivity 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.  An example is scenario (4) in Mark's and Jari's analysis [1].

Finally, we would like to request a presentation slot for Virtual IPv6
Connectivity at IETF 73.  Dan and Dave, I am assuming this would be in
the BEHAVE session, right?

Thanks everybody.

- Christian, for Alain and Christian


[1] http://tools.ietf.org/html/draft-arkko-townsley-coexistence



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


From behave-bounces@ietf.org  Thu Oct 30 10:10:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D87673A6906;
	Thu, 30 Oct 2008 10:10:16 -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 738953A6819
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 10:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.805
X-Spam-Level: 
X-Spam-Status: No, score=-5.805 tagged_above=-999 required=5
	tests=[AWL=-0.836, BAYES_00=-2.599, 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 kc2HA4vsbjJi for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 10:10:12 -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 158FE3A6906
	for <behave@ietf.org>; Thu, 30 Oct 2008 10:10:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,516,1220227200"; d="scan'208";a="98168499"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 30 Oct 2008 17:10:11 +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 m9UHAB8v028100; 
	Thu, 30 Oct 2008 10:10:11 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9UHAANa011719;
	Thu, 30 Oct 2008 17:10:11 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Fred Baker'" <fred@cisco.com>, "'Xing Li'" <xing@cernet.edu.cn>,
	<congxiao@cernet.edu.cn>
Date: Thu, 30 Oct 2008 10:10:10 -0700
Message-ID: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack6sl252j/2qmrtS2iCmbJTZ5EaaQ==
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3918; t=1225386611;
	x=1226250611; 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:=20Application=20awareness=20of=20translator=20in=
	20draft-baker-behave-v4v6-translation-00 |Sender:=20;
	bh=LJoqmVdoT6I9O4D/+v4uPuME0SIl3p6sRE5at8kNg5o=;
	b=JxGrSvPJUoZp730ry8IZCFijBAJsRFcvh37ACTwQmJ9dc2ieIV+e9vGElP
	QbUOCB5BLAYN8BCEq7Q2vX4aZ6ulJBqDwyXwOGkIQ9wunTc6tAwmSBsBieAq
	rzfui2letqs6eos81hDCI3uh1/ON+jvJayz/UrxfY/gUJXYTIoIic=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Fred, Xing, Congxiao,

(speaking as individual contributor)

I stumbled when I read Section 1.4 of
http://tools.ietf.org/html/draft-baker-behave-v4v6-translation-00.  Three
points:

* I believe much of the text in that section belongs in the Framework document
as it is not specific to a particular kind of translation.  The text is trying
to describe the problem (when translation occurs, an application will be
connecting to a host with a different address family and over that connection
the 'wrong' address family might be exchanged; this can lead to application
confusion) and also a solution (IN6_IS_ADDR_V4MAPPED).

* Some of the text describes stuff that just doesn't work.  For example,

   There are no extra changes needed to applications to operate through
   a translator beyond what applications already need to do to operate
   on a dual node.  The applications that have been modified to work on
   a dual node already have the mechanisms to determine whether they are
   communicating with an IPv4 or an IPv6 peer.  Thus if the applications
   need to modify their behavior depending on the type of the peer, such
   as ftp determining whether to fallback to using the PORT/PASV command
   when EPRT/EPSV fails (as specified in [RFC2428]), they already need
   to do that when running on dual nodes and the presence of translators
   does not add anything.  For example, when using the socket API
   [RFC3493] the applications know that the peer is IPv6 if they get an
   AF_INET6 address from the name service and the address is not an
   IPv4-mapped address (i.e., IN6_IS_ADDR_V4MAPPED returns false).  If
   this is not the case, i.e., the address is AF_INET or an IPv4-mapped
   IPv6 address, the peer is IPv4.

IN6_IS_ADDR_V4MAPPED only knows about IANA-registered prefixes for Teredo and
6to4.  I don't believe IN6_IS_ADDR_V4MAPPED is able, by itself, to determine
there is an embedded IPv4 address in the IPv6 address -- but correct me if I'm
wrong.  In order for IN6_IS_ADDR_V4MAPPED to indicate the address went through
a translator when the translator's IPv6 prefix is chosen by the ISP (rather
than IANA) the host needs to know the IPv6 prefix (and length) in order for
the IN6_IS_ADDR_V4MAPPED macro to function as expected.  This means (a) the
host's stack needs to implement something like
draft-wing-behave-learn-prefix-00.txt and tie that learned adddress into to
its IN6_IS_ADDR_V4MAPPED macro or (b) the application needs to implement
something like draft-wing-behave-learn-prefix-00.txt.  

* The text describing EPRT/EPSV needs considerable expansion.  At this point
there is consensus that a DNSSEC-aware resolver in the end host needs to know
about the translator.  But I don't believe there is consensus that other
applications -- such as FTP -- need to be knowledgable about the translator.
In the past, Brian Carpenter has raised an objection to the idea of putting
translator awareness into IPv6 applications
<http://www.ietf.org/mail-archive/web/behave/current/msg04129.html> so I
expect more discussion around this will be necessary.  If we decide to have
the application be aware of the translator, a generalized document titled
"Application Aspects of IPv6 Translation" seems appropriate and would be
similar to the existing RFC4038 ("Application Aspects of IPv6 Transition",
previously draft-ietf-v6ops-application-transition).

The alternative to translator awareness in the host's application is an ALG
somewhere in the network (probably as part of the translator).  In BEHAVE for
NAT44, due to the existing deployment of FTP ALGs we agreed that FTP ALGs were
tolerable.  

We need to decide where protocols should be 'fixed up' for translation.  This
decision might be on an application-by-application basis.  Starting with the
FTP seems appropriate, as everyone is reasonably familiar with it.

-d

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


From behave-bounces@ietf.org  Thu Oct 30 12:15:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3358B28C1CF;
	Thu, 30 Oct 2008 12:15:21 -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 2E6763A6AB1
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 12:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.698
X-Spam-Level: 
X-Spam-Status: No, score=-109.698 tagged_above=-999 required=5
	tests=[AWL=-0.729, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8,
	SARE_PROLOSTOCK_SYM3=1.63, 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 56ff9y0cIYbx for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 12:15:19 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212])
	by core3.amsl.com (Postfix) with ESMTP id 21C4B3A6A3F
	for <behave@ietf.org>; Thu, 30 Oct 2008 12:15:19 -0700 (PDT)
Received: from tk1-exhub-c104.redmond.corp.microsoft.com (157.54.46.188) by
	TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Thu, 30 Oct 2008 12:15:17 -0700
Received: from tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.32) by tk1-exhub-c104.redmond.corp.microsoft.com
	(157.54.46.188)
	with Microsoft SMTP Server id 8.1.291.1; Thu, 30 Oct 2008 12:15:16 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::75be:c82f:ae04:55bf]) by
	tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.32])
	with mapi; Thu, 30 Oct 2008 12:15:16 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Fred Baker' <fred@cisco.com>, 'Xing Li'
	<xing@cernet.edu.cn>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>
Date: Thu, 30 Oct 2008 12:15:15 -0700
Thread-Topic: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
Thread-Index: Ack6sl252j/2qmrtS2iCmbJTZ5EaaQAETWPw
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E98A@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
In-Reply-To: <033e01c93ab2$5df07840$c3f0200a@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
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Application awareness of translator
	in	draft-baker-behave-v4v6-translation-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

IN6_IS_ADDR_V4MAPPED() specifically tests if an address is an IPv4-mapped
address (::FFFF:<IPv4-address>) as defined in RFC 3493 section 3.7.
It does not know about Teredo or 6to4 or anything else.

-Dave

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of Dan Wing
> Sent: Thursday, October 30, 2008 10:10 AM
> To: 'Fred Baker'; 'Xing Li'; congxiao@cernet.edu.cn
> Cc: behave@ietf.org
> Subject: [BEHAVE] Application awareness of translator in draft-baker-
> behave-v4v6-translation-00
>
> Fred, Xing, Congxiao,
>
> (speaking as individual contributor)
>
> I stumbled when I read Section 1.4 of
> http://tools.ietf.org/html/draft-baker-behave-v4v6-translation-00.
> Three
> points:
>
> * I believe much of the text in that section belongs in the Framework
> document
> as it is not specific to a particular kind of translation.  The text is
> trying
> to describe the problem (when translation occurs, an application will
> be
> connecting to a host with a different address family and over that
> connection
> the 'wrong' address family might be exchanged; this can lead to
> application
> confusion) and also a solution (IN6_IS_ADDR_V4MAPPED).
>
> * Some of the text describes stuff that just doesn't work.  For
> example,
>
>    There are no extra changes needed to applications to operate through
>    a translator beyond what applications already need to do to operate
>    on a dual node.  The applications that have been modified to work on
>    a dual node already have the mechanisms to determine whether they
> are
>    communicating with an IPv4 or an IPv6 peer.  Thus if the
> applications
>    need to modify their behavior depending on the type of the peer,
> such
>    as ftp determining whether to fallback to using the PORT/PASV
> command
>    when EPRT/EPSV fails (as specified in [RFC2428]), they already need
>    to do that when running on dual nodes and the presence of
> translators
>    does not add anything.  For example, when using the socket API
>    [RFC3493] the applications know that the peer is IPv6 if they get an
>    AF_INET6 address from the name service and the address is not an
>    IPv4-mapped address (i.e., IN6_IS_ADDR_V4MAPPED returns false).  If
>    this is not the case, i.e., the address is AF_INET or an IPv4-mapped
>    IPv6 address, the peer is IPv4.
>
> IN6_IS_ADDR_V4MAPPED only knows about IANA-registered prefixes for
> Teredo and
> 6to4.  I don't believe IN6_IS_ADDR_V4MAPPED is able, by itself, to
> determine
> there is an embedded IPv4 address in the IPv6 address -- but correct me
> if I'm
> wrong.  In order for IN6_IS_ADDR_V4MAPPED to indicate the address went
> through
> a translator when the translator's IPv6 prefix is chosen by the ISP
> (rather
> than IANA) the host needs to know the IPv6 prefix (and length) in order
> for
> the IN6_IS_ADDR_V4MAPPED macro to function as expected.  This means (a)
> the
> host's stack needs to implement something like
> draft-wing-behave-learn-prefix-00.txt and tie that learned adddress
> into to
> its IN6_IS_ADDR_V4MAPPED macro or (b) the application needs to
> implement
> something like draft-wing-behave-learn-prefix-00.txt.
>
> * The text describing EPRT/EPSV needs considerable expansion.  At this
> point
> there is consensus that a DNSSEC-aware resolver in the end host needs
> to know
> about the translator.  But I don't believe there is consensus that
> other
> applications -- such as FTP -- need to be knowledgable about the
> translator.
> In the past, Brian Carpenter has raised an objection to the idea of
> putting
> translator awareness into IPv6 applications
> <http://www.ietf.org/mail-archive/web/behave/current/msg04129.html> so
> I
> expect more discussion around this will be necessary.  If we decide to
> have
> the application be aware of the translator, a generalized document
> titled
> "Application Aspects of IPv6 Translation" seems appropriate and would
> be
> similar to the existing RFC4038 ("Application Aspects of IPv6
> Transition",
> previously draft-ietf-v6ops-application-transition).
>
> The alternative to translator awareness in the host's application is an
> ALG
> somewhere in the network (probably as part of the translator).  In
> BEHAVE for
> NAT44, due to the existing deployment of FTP ALGs we agreed that FTP
> ALGs were
> tolerable.
>
> We need to decide where protocols should be 'fixed up' for translation.
> This
> decision might be on an application-by-application basis.  Starting
> with the
> FTP seems appropriate, as everyone is reasonably familiar with it.
>
> -d
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

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


From behave-bounces@ietf.org  Thu Oct 30 12:25:37 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D53823A6A5F;
	Thu, 30 Oct 2008 12:25:37 -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 A8B4D3A6987
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 12:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.741
X-Spam-Level: 
X-Spam-Status: No, score=-5.741 tagged_above=-999 required=5
	tests=[AWL=-0.772, BAYES_00=-2.599, 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 vOlnQHDT+W8X for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 12:25:35 -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 EEC303A6909
	for <behave@ietf.org>; Thu, 30 Oct 2008 12:25:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,517,1220227200"; d="scan'208";a="98238369"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 30 Oct 2008 19:25:27 +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 m9UJPRRp006927; 
	Thu, 30 Oct 2008 12:25:27 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9UJPReF017339;
	Thu, 30 Oct 2008 19:25:27 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dave Thaler'" <dthaler@windows.microsoft.com>,
	"'Fred Baker'" <fred@cisco.com>, "'Xing Li'" <xing@cernet.edu.cn>,
	<congxiao@cernet.edu.cn>
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E98A@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 30 Oct 2008 12:25:27 -0700
Message-ID: <051e01c93ac5$43c01580$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack6sl252j/2qmrtS2iCmbJTZ5EaaQAETWPwAAA2DQA=
In-Reply-To: <E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E98A@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5491; t=1225394727;
	x=1226258727; 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]=20Application=20awareness=20of
	=20translator=20indraft-baker-behave-v4v6-translation-00
	|Sender:=20; bh=NiMUNwvaN5t9A+EHOM78iGw4Gvxf/iogZJIf5eryj28=;
	b=IQaCwY+tfrIavP9UnzMbXWG+GqvvaQGaOQ/Dm0AIzF3mCxZYoFEBkRPfJR
	5B9lFgQWGQgplVjAGuzSBWDOLiReAGG6OcSUcEnKTH2qBLyh9qhrTK3eQVaJ
	/tquWKZcEZgFsIJpd808teDUz4uXsAgjyFRp9F/ZHsqVIADfdUvQg=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] Application awareness of translator
	indraft-baker-behave-v4v6-translation-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

> IN6_IS_ADDR_V4MAPPED() specifically tests if an address is an 
> IPv4-mapped
> address (::FFFF:<IPv4-address>) as defined in RFC 3493 section 3.7.
> It does not know about Teredo or 6to4 or anything else.

Thanks.  

But none of the proposals (IVI, NAT64, sNAT-PT) propose using that prefix --
they're all using operator prefixes,
http://tools.ietf.org/html/draft-baker-behave-v4v6-framework-00#appendix-A.2 

So IN6_IS_ADDR_V4MAPPED would return false for a translated address, right?

-d


> -Dave
> 
> > -----Original Message-----
> > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> > Behalf Of Dan Wing
> > Sent: Thursday, October 30, 2008 10:10 AM
> > To: 'Fred Baker'; 'Xing Li'; congxiao@cernet.edu.cn
> > Cc: behave@ietf.org
> > Subject: [BEHAVE] Application awareness of translator in 
> draft-baker-
> > behave-v4v6-translation-00
> >
> > Fred, Xing, Congxiao,
> >
> > (speaking as individual contributor)
> >
> > I stumbled when I read Section 1.4 of
> > http://tools.ietf.org/html/draft-baker-behave-v4v6-translation-00.
> > Three
> > points:
> >
> > * I believe much of the text in that section belongs in the 
> Framework
> > document
> > as it is not specific to a particular kind of translation.  
> The text is
> > trying
> > to describe the problem (when translation occurs, an 
> application will
> > be
> > connecting to a host with a different address family and over that
> > connection
> > the 'wrong' address family might be exchanged; this can lead to
> > application
> > confusion) and also a solution (IN6_IS_ADDR_V4MAPPED).
> >
> > * Some of the text describes stuff that just doesn't work.  For
> > example,
> >
> >    There are no extra changes needed to applications to 
> operate through
> >    a translator beyond what applications already need to do 
> to operate
> >    on a dual node.  The applications that have been 
> modified to work on
> >    a dual node already have the mechanisms to determine whether they
> > are
> >    communicating with an IPv4 or an IPv6 peer.  Thus if the
> > applications
> >    need to modify their behavior depending on the type of the peer,
> > such
> >    as ftp determining whether to fallback to using the PORT/PASV
> > command
> >    when EPRT/EPSV fails (as specified in [RFC2428]), they 
> already need
> >    to do that when running on dual nodes and the presence of
> > translators
> >    does not add anything.  For example, when using the socket API
> >    [RFC3493] the applications know that the peer is IPv6 if 
> they get an
> >    AF_INET6 address from the name service and the address is not an
> >    IPv4-mapped address (i.e., IN6_IS_ADDR_V4MAPPED returns 
> false).  If
> >    this is not the case, i.e., the address is AF_INET or an 
> IPv4-mapped
> >    IPv6 address, the peer is IPv4.
> >
> > IN6_IS_ADDR_V4MAPPED only knows about IANA-registered prefixes for
> > Teredo and
> > 6to4.  I don't believe IN6_IS_ADDR_V4MAPPED is able, by itself, to
> > determine
> > there is an embedded IPv4 address in the IPv6 address -- 
> but correct me
> > if I'm
> > wrong.  In order for IN6_IS_ADDR_V4MAPPED to indicate the 
> address went
> > through
> > a translator when the translator's IPv6 prefix is chosen by the ISP
> > (rather
> > than IANA) the host needs to know the IPv6 prefix (and 
> length) in order
> > for
> > the IN6_IS_ADDR_V4MAPPED macro to function as expected.  
> This means (a)
> > the
> > host's stack needs to implement something like
> > draft-wing-behave-learn-prefix-00.txt and tie that learned adddress
> > into to
> > its IN6_IS_ADDR_V4MAPPED macro or (b) the application needs to
> > implement
> > something like draft-wing-behave-learn-prefix-00.txt.
> >
> > * The text describing EPRT/EPSV needs considerable 
> expansion.  At this
> > point
> > there is consensus that a DNSSEC-aware resolver in the end 
> host needs
> > to know
> > about the translator.  But I don't believe there is consensus that
> > other
> > applications -- such as FTP -- need to be knowledgable about the
> > translator.
> > In the past, Brian Carpenter has raised an objection to the idea of
> > putting
> > translator awareness into IPv6 applications
> > 
> <http://www.ietf.org/mail-archive/web/behave/current/msg04129.html> so
> > I
> > expect more discussion around this will be necessary.  If 
> we decide to
> > have
> > the application be aware of the translator, a generalized document
> > titled
> > "Application Aspects of IPv6 Translation" seems appropriate 
> and would
> > be
> > similar to the existing RFC4038 ("Application Aspects of IPv6
> > Transition",
> > previously draft-ietf-v6ops-application-transition).
> >
> > The alternative to translator awareness in the host's 
> application is an
> > ALG
> > somewhere in the network (probably as part of the translator).  In
> > BEHAVE for
> > NAT44, due to the existing deployment of FTP ALGs we agreed that FTP
> > ALGs were
> > tolerable.
> >
> > We need to decide where protocols should be 'fixed up' for 
> translation.
> > This
> > decision might be on an application-by-application basis.  Starting
> > with the
> > FTP seems appropriate, as everyone is reasonably familiar with it.
> >
> > -d
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> 

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


From behave-bounces@ietf.org  Thu Oct 30 12:27:20 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15DAC3A6A33;
	Thu, 30 Oct 2008 12:27:20 -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 E679E3A6A33
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 12:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.607
X-Spam-Level: 
X-Spam-Status: No, score=-109.607 tagged_above=-999 required=5
	tests=[AWL=-0.638, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8,
	SARE_PROLOSTOCK_SYM3=1.63, 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 8I3N8uwy9-2x for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 12:27:17 -0700 (PDT)
Received: from smtp.microsoft.com (mail1.microsoft.com [131.107.115.212])
	by core3.amsl.com (Postfix) with ESMTP id DC9943A6987
	for <behave@ietf.org>; Thu, 30 Oct 2008 12:27:17 -0700 (PDT)
Received: from tk1-exhub-c103.redmond.corp.microsoft.com (157.54.46.187) by
	TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with
	Microsoft
	SMTP Server (TLS) id 8.1.291.1; Thu, 30 Oct 2008 12:27:07 -0700
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com
	(157.54.18.33) by tk1-exhub-c103.redmond.corp.microsoft.com
	(157.54.46.187)
	with Microsoft SMTP Server id 8.1.291.1; Thu, 30 Oct 2008 12:27:07 -0700
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com
	([fe80::75be:c82f:ae04:55bf]) by
	tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33])
	with mapi; Thu, 30 Oct 2008 12:27:47 -0700
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Fred Baker' <fred@cisco.com>, 'Xing Li'
	<xing@cernet.edu.cn>, "congxiao@cernet.edu.cn" <congxiao@cernet.edu.cn>
Date: Thu, 30 Oct 2008 12:27:06 -0700
Thread-Topic: [BEHAVE] Application awareness of translator
	indraft-baker-behave-v4v6-translation-00
Thread-Index: Ack6sl252j/2qmrtS2iCmbJTZ5EaaQAETWPwAAA2DQAAAEJJ8A==
Message-ID: <E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E9A3@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E98A@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<051e01c93ac5$43c01580$c3f0200a@cisco.com>
In-Reply-To: <051e01c93ac5$43c01580$c3f0200a@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
Cc: "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] Application awareness of translator
 indraft-baker-behave-v4v6-translation-00
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

That's correct.

-Dave

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Thursday, October 30, 2008 12:25 PM
> To: Dave Thaler; 'Fred Baker'; 'Xing Li'; congxiao@cernet.edu.cn
> Cc: behave@ietf.org
> Subject: RE: [BEHAVE] Application awareness of translator indraft-
> baker-behave-v4v6-translation-00
>
> > IN6_IS_ADDR_V4MAPPED() specifically tests if an address is an
> > IPv4-mapped
> > address (::FFFF:<IPv4-address>) as defined in RFC 3493 section 3.7.
> > It does not know about Teredo or 6to4 or anything else.
>
> Thanks.
>
> But none of the proposals (IVI, NAT64, sNAT-PT) propose using that
> prefix --
> they're all using operator prefixes,
> http://tools.ietf.org/html/draft-baker-behave-v4v6-framework-
> 00#appendix-A.2
>
> So IN6_IS_ADDR_V4MAPPED would return false for a translated address,
> right?
>
> -d
>
>
> > -Dave
> >
> > > -----Original Message-----
> > > From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> > > Behalf Of Dan Wing
> > > Sent: Thursday, October 30, 2008 10:10 AM
> > > To: 'Fred Baker'; 'Xing Li'; congxiao@cernet.edu.cn
> > > Cc: behave@ietf.org
> > > Subject: [BEHAVE] Application awareness of translator in
> > draft-baker-
> > > behave-v4v6-translation-00
> > >
> > > Fred, Xing, Congxiao,
> > >
> > > (speaking as individual contributor)
> > >
> > > I stumbled when I read Section 1.4 of
> > > http://tools.ietf.org/html/draft-baker-behave-v4v6-translation-00.
> > > Three
> > > points:
> > >
> > > * I believe much of the text in that section belongs in the
> > Framework
> > > document
> > > as it is not specific to a particular kind of translation.
> > The text is
> > > trying
> > > to describe the problem (when translation occurs, an
> > application will
> > > be
> > > connecting to a host with a different address family and over that
> > > connection
> > > the 'wrong' address family might be exchanged; this can lead to
> > > application
> > > confusion) and also a solution (IN6_IS_ADDR_V4MAPPED).
> > >
> > > * Some of the text describes stuff that just doesn't work.  For
> > > example,
> > >
> > >    There are no extra changes needed to applications to
> > operate through
> > >    a translator beyond what applications already need to do
> > to operate
> > >    on a dual node.  The applications that have been
> > modified to work on
> > >    a dual node already have the mechanisms to determine whether
> they
> > > are
> > >    communicating with an IPv4 or an IPv6 peer.  Thus if the
> > > applications
> > >    need to modify their behavior depending on the type of the peer,
> > > such
> > >    as ftp determining whether to fallback to using the PORT/PASV
> > > command
> > >    when EPRT/EPSV fails (as specified in [RFC2428]), they
> > already need
> > >    to do that when running on dual nodes and the presence of
> > > translators
> > >    does not add anything.  For example, when using the socket API
> > >    [RFC3493] the applications know that the peer is IPv6 if
> > they get an
> > >    AF_INET6 address from the name service and the address is not an
> > >    IPv4-mapped address (i.e., IN6_IS_ADDR_V4MAPPED returns
> > false).  If
> > >    this is not the case, i.e., the address is AF_INET or an
> > IPv4-mapped
> > >    IPv6 address, the peer is IPv4.
> > >
> > > IN6_IS_ADDR_V4MAPPED only knows about IANA-registered prefixes for
> > > Teredo and
> > > 6to4.  I don't believe IN6_IS_ADDR_V4MAPPED is able, by itself, to
> > > determine
> > > there is an embedded IPv4 address in the IPv6 address --
> > but correct me
> > > if I'm
> > > wrong.  In order for IN6_IS_ADDR_V4MAPPED to indicate the
> > address went
> > > through
> > > a translator when the translator's IPv6 prefix is chosen by the ISP
> > > (rather
> > > than IANA) the host needs to know the IPv6 prefix (and
> > length) in order
> > > for
> > > the IN6_IS_ADDR_V4MAPPED macro to function as expected.
> > This means (a)
> > > the
> > > host's stack needs to implement something like
> > > draft-wing-behave-learn-prefix-00.txt and tie that learned adddress
> > > into to
> > > its IN6_IS_ADDR_V4MAPPED macro or (b) the application needs to
> > > implement
> > > something like draft-wing-behave-learn-prefix-00.txt.
> > >
> > > * The text describing EPRT/EPSV needs considerable
> > expansion.  At this
> > > point
> > > there is consensus that a DNSSEC-aware resolver in the end
> > host needs
> > > to know
> > > about the translator.  But I don't believe there is consensus that
> > > other
> > > applications -- such as FTP -- need to be knowledgable about the
> > > translator.
> > > In the past, Brian Carpenter has raised an objection to the idea of
> > > putting
> > > translator awareness into IPv6 applications
> > >
> > <http://www.ietf.org/mail-archive/web/behave/current/msg04129.html>
> so
> > > I
> > > expect more discussion around this will be necessary.  If
> > we decide to
> > > have
> > > the application be aware of the translator, a generalized document
> > > titled
> > > "Application Aspects of IPv6 Translation" seems appropriate
> > and would
> > > be
> > > similar to the existing RFC4038 ("Application Aspects of IPv6
> > > Transition",
> > > previously draft-ietf-v6ops-application-transition).
> > >
> > > The alternative to translator awareness in the host's
> > application is an
> > > ALG
> > > somewhere in the network (probably as part of the translator).  In
> > > BEHAVE for
> > > NAT44, due to the existing deployment of FTP ALGs we agreed that
> FTP
> > > ALGs were
> > > tolerable.
> > >
> > > We need to decide where protocols should be 'fixed up' for
> > translation.
> > > This
> > > decision might be on an application-by-application basis.  Starting
> > > with the
> > > FTP seems appropriate, as everyone is reasonably familiar with it.
> > >
> > > -d
> > >
> > > _______________________________________________
> > > Behave mailing list
> > > Behave@ietf.org
> > > https://www.ietf.org/mailman/listinfo/behave
> >
>

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


From behave-bounces@ietf.org  Thu Oct 30 15:18:21 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 574AC3A68D0;
	Thu, 30 Oct 2008 15:18:21 -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 4E2F63A67A4
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 15:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.426
X-Spam-Level: 
X-Spam-Status: No, score=-105.426 tagged_above=-999 required=5
	tests=[AWL=-0.457, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_PROLOSTOCK_SYM3=1.63, 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 3q-oqLPE1PQb for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 15:18:19 -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 8043B3A6829
	for <behave@ietf.org>; Thu, 30 Oct 2008 15:18:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,518,1220227200"; d="scan'208";a="32249760"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 30 Oct 2008 22:18: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 m9UMI9UN023723; 
	Fri, 31 Oct 2008 06:18:09 +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 m9UMI9WQ029111;
	Thu, 30 Oct 2008 22:18:09 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 06:18:09 +0800
Received: from [10.5.30.198] ([10.75.234.10]) by xfe-hkg-411.apac.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 06:18:08 +0800
Message-Id: <788261F6-15B9-4236-B30D-0536FCDE8777@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 06:18:07 +0800
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 30 Oct 2008 22:18:08.0558 (UTC)
	FILETIME=[6356B4E0:01C93ADD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4304; t=1225405090;
	x=1226269090; 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=20Application=20awareness=20of=20translat
	or=20in=20draft-baker-behave-v4v6-translation-00 |Sender:=20;
	bh=yX0woj/1brooFyEs7Dr9z4ydSRqQpHi9K0ZXj4ezHFM=;
	b=CsoLsBOMq2VgYEx6vDZYafVIcz5x8ei/KNddQ6eUktnjBvNoNpGamcXMkw
	5uw03c9MwGhM7hOrJSHBkBTaSAu6SLQ/amIEd6a0CSuQfVcOaCkM6pof6p0O
	DwYriS9J4vzrISefWerajD3VC1uZHg1FTM1VsI8K2QoFsvTrlBGRs=;
Authentication-Results: hkg-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: behave@ietf.org, congxiao@cernet.edu.cn, 'Xing Li' <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Thanks; good catch. Let us rework that part.

On Oct 31, 2008, at 1:10 AM, Dan Wing wrote:

> Fred, Xing, Congxiao,
>
> (speaking as individual contributor)
>
> I stumbled when I read Section 1.4 of
> http://tools.ietf.org/html/draft-baker-behave-v4v6-translation-00.   
> Three
> points:
>
> * I believe much of the text in that section belongs in the  
> Framework document
> as it is not specific to a particular kind of translation.  The text  
> is trying
> to describe the problem (when translation occurs, an application  
> will be
> connecting to a host with a different address family and over that  
> connection
> the 'wrong' address family might be exchanged; this can lead to  
> application
> confusion) and also a solution (IN6_IS_ADDR_V4MAPPED).
>
> * Some of the text describes stuff that just doesn't work.  For  
> example,
>
>   There are no extra changes needed to applications to operate through
>   a translator beyond what applications already need to do to operate
>   on a dual node.  The applications that have been modified to work on
>   a dual node already have the mechanisms to determine whether they  
> are
>   communicating with an IPv4 or an IPv6 peer.  Thus if the  
> applications
>   need to modify their behavior depending on the type of the peer,  
> such
>   as ftp determining whether to fallback to using the PORT/PASV  
> command
>   when EPRT/EPSV fails (as specified in [RFC2428]), they already need
>   to do that when running on dual nodes and the presence of  
> translators
>   does not add anything.  For example, when using the socket API
>   [RFC3493] the applications know that the peer is IPv6 if they get an
>   AF_INET6 address from the name service and the address is not an
>   IPv4-mapped address (i.e., IN6_IS_ADDR_V4MAPPED returns false).  If
>   this is not the case, i.e., the address is AF_INET or an IPv4-mapped
>   IPv6 address, the peer is IPv4.
>
> IN6_IS_ADDR_V4MAPPED only knows about IANA-registered prefixes for  
> Teredo and
> 6to4.  I don't believe IN6_IS_ADDR_V4MAPPED is able, by itself, to  
> determine
> there is an embedded IPv4 address in the IPv6 address -- but correct  
> me if I'm
> wrong.  In order for IN6_IS_ADDR_V4MAPPED to indicate the address  
> went through
> a translator when the translator's IPv6 prefix is chosen by the ISP  
> (rather
> than IANA) the host needs to know the IPv6 prefix (and length) in  
> order for
> the IN6_IS_ADDR_V4MAPPED macro to function as expected.  This means  
> (a) the
> host's stack needs to implement something like
> draft-wing-behave-learn-prefix-00.txt and tie that learned adddress  
> into to
> its IN6_IS_ADDR_V4MAPPED macro or (b) the application needs to  
> implement
> something like draft-wing-behave-learn-prefix-00.txt.
>
> * The text describing EPRT/EPSV needs considerable expansion.  At  
> this point
> there is consensus that a DNSSEC-aware resolver in the end host  
> needs to know
> about the translator.  But I don't believe there is consensus that  
> other
> applications -- such as FTP -- need to be knowledgable about the  
> translator.
> In the past, Brian Carpenter has raised an objection to the idea of  
> putting
> translator awareness into IPv6 applications
> <http://www.ietf.org/mail-archive/web/behave/current/msg04129.html>  
> so I
> expect more discussion around this will be necessary.  If we decide  
> to have
> the application be aware of the translator, a generalized document  
> titled
> "Application Aspects of IPv6 Translation" seems appropriate and  
> would be
> similar to the existing RFC4038 ("Application Aspects of IPv6  
> Transition",
> previously draft-ietf-v6ops-application-transition).
>
> The alternative to translator awareness in the host's application is  
> an ALG
> somewhere in the network (probably as part of the translator).  In  
> BEHAVE for
> NAT44, due to the existing deployment of FTP ALGs we agreed that FTP  
> ALGs were
> tolerable.
>
> We need to decide where protocols should be 'fixed up' for  
> translation.  This
> decision might be on an application-by-application basis.  Starting  
> with the
> FTP seems appropriate, as everyone is reasonably familiar with it.
>
> -d
>

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


From behave-bounces@ietf.org  Thu Oct 30 15:47:19 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBC863A6B53;
	Thu, 30 Oct 2008 15:47:19 -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 923A83A6B9E
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 15:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5
	tests=[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 NkDXiQPDAzXV for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 15:47:17 -0700 (PDT)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM
	[128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id AAC3C3A6BD7
	for <behave@ietf.org>; Thu, 30 Oct 2008 15:46:34 -0700 (PDT)
Received: from smssmtp-internal1.sri.com (128.18.84.115)
	by mailgate-internal3.sri.com with SMTP; 30 Oct 2008 22:46:32 -0000
X-AuditID: 80125473-a94debb000000a55-ab-490a3948ca3b
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11])
	by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id
	C0F1421AF31
	for <behave@ietf.org>; Thu, 30 Oct 2008 15:46:32 -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 <0K9K004ULPXJXI00@mail.sri.com> for
	behave@ietf.org; Thu, 30 Oct 2008 15:46:32 -0700 (PDT)
Date: Thu, 30 Oct 2008 18:46:28 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
In-reply-to: <DB2AE4C3-DF3C-40CD-BDB1-EEC03695B80C@nomadiclab.com>
To: Christian Vogt <christian.vogt@nomadiclab.com>
Message-id: <490A3944.90502@sri.com>
MIME-version: 1.0
References: <DB2AE4C3-DF3C-40CD-BDB1-EEC03695B80C@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
X-Brightmail-Tracker: AAAAAA==
Cc: Alain Durand <alain_durand@cable.comcast.com>,
	46Translation <46translation@employees.org>,
	Behave Mailing List <behave@ietf.org>
Subject: Re: [BEHAVE] New I-D: IPv4/IPv6 Translator for IPv4-Only Networks
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Good start on the topic.  comments:

abstract:

 "Communication initiated into the latter direction..."  this sentence 
is confusing - if you mean "Communication initiated from the IPv4 
network..." just say that.  Also, it is not clear in the abstract 
whether communication could be initiated from the IPv6 side, and if so 
how.  That becomes clear in the body.  Suggest rewording the abstract:

This document proposes Virtual IPv6 Connectivity, a method for
   deployment in IPv4-only networks to enable communications with the
   IPv6 Internet.  Virtual IPv6 Connectivity uses IP protocol
   translation to support both incoming traffic from IPv6 to IPv4, and
   outgoing traffic from IPv4 to IPv6.  Communication initiated from the IPv4 network
   is facilitated through a DNS or DNSSEC proxy to obtain a virtual IPv4 address.  
   Communication initiated from the IPv6 Internet relies on virtual IPv6 addresses stored in the authoritative DNS server. 
   Unlike existing IPv4/IPv6 interworking techniques, which are designed 
   for deployment in IPv6 networks, Virtual IPv6 Connectivity does not
   require extra, globally unique IPv4 addresses.


introduction:

s/inavertable/inevitable

add to the justification for IPv4 based translation:  "...The 
responsibility and cost for maintaining IPv4 interoperability shifts to 
those who desire to maintain the IPv4 network when IPv6 predominates."

after the DNS proxy statement, add the same statement in the abstract 
for the IPv6 initiated case.  Maybe subtle, but I just think it is 
important to establish and reinforce that a proxy is needed ONLY for 
IPv4 initiated communication and that IPv6 initiated communication 
relies solely on "normal" DNS (with properly provisioned virtual 
addresses...)

conceptual overview:

make it clear that the prefixes and addresses used are examples - you 
have not introduced the virtual addresses yet, and the reader should not 
conclude that only 2001:DB8 or net-10 work.

There is some implication that DNS servers (recursive and authoritative) 
are maintaining virtual address mappings.  Is that true?  It looks like 
(reading ahead) the "recursive name server" in the v4 initiated case is 
actually the DNS Proxy.  Also the "authoritative DNS Server in the IPv4 
network" is an unmodified DNS server with the virtual addresses 
configured.  Maybe go back and clean up the conceptual overview to make 
it obvious which components have new/unmodified logic.  I believe you have:
1. a new box, the translator
2. a new/modified box, the DNS proxy or recursive name server (or 
"virtual IPv6 connectivity name server")
3. unmodified DNS server code with provision of virtual addresses
1 and 2 determine/maintain the virtual address mappings and send name 
resolutions to 3, or maybe 3 requires manual configuration of virtual 
addresses?

Anyway, you don't want too much detail in the conceptual overview - use 
it as an outline for the sections that follow, and in fact refer forward 
to them, e.g. "Virtual addresses (section 3.0)..."  I suggest reversing 
the first two bullets in the components to parallel the following 
sections.  It is always hard to discuss interlocked sub-topics that 
refer forward/backward to each other, but I would also recommend 
reversing sections 4 and 5 to more logically flow - define the 
addressing architecture (section 3), define the 
mapping/provisioning/discovery process (previously section 5), finally 
the flow of translation (previously section 4).  Just a suggestion.

   Virtual IPv6 Connectivity consists of three components, which
   together enable hosts in an IPv4-only network to communicate with
   remote IPv6 correspondent hosts:

   o  Virtual IP Addresses (Section 3), which represent, respectively,
      the IPv6 addresses of remote correspondent hosts to local IPv4
      hosts, and the IPv4 addresses of local hosts to remote IPv6
      correspondent hosts.

   o  IP protocol translation (Section 4), which are placed on border links of the
      IPv4-only network to translate packets exchanged with IPv6
      correspondent hosts.

   o  Provisioning and Discovery of virtual IP addresses (Section 5).


Section 4:
p. 9 "For communications initiated by a remote IPv6..."  s/actaully/actually
figure 3 and 4 sort of illustrate why I think it would be better to 
explain address discovery before the translation.  in the figure 3 
example it is a natural question - how would the IPv6 correspondent know 
the virtual IPv6 address for the IPv4 host?

Section 5: 
change the title to Provision and Discovery as it discusses both 
creation and retrieval of the mappings. 

5.1:  not clear how the virtual address 2001:DB8:ABC::a.b.c.d gets 
created in the auth name server.  it almost sounds like it maintains the 
mapping.  It should be made clear who creates the mapping (the 
translator) and how it gets provisioned in the auth name server.  In 
addition to the text changes, put this flow in fig 4.

5.2:  it seems you are discussing a modified recursive name server, i.e. 
one that has part of the code required to build "virtual IPv6 
connectivity".  identify this name server explicitly as a "virtual IPv6 
connectivity name server" which combines normal recursive name server 
plus this mapping function.

There is a big hand wave here - "The recursive DNS name server maps each 
of the correspondent host's regular IPv6 addresses onto a separate 
virtual IPv4 address in coordination with the IP protocol translator to 
which these virtual IPv4 addresses route."  That coordination is the key 
to the mapping working, especially if there is not a 1-to-1 coupling 
between protocol translator and name server, e.g. the name server could 
serve multiple translators.  Even with 1-to-1 how does the name server 
know whether/not a virtual address is available?  does the translator 
give it a range that it manages?  if an address was used in a previous 
mapping, when is it safe to recycle (i.e. the IPv4 host is no longer 
counting on it)?  The translator I worked on had an internal DNS ALG 
that did this, and restricted certain address ranges for inbound and 
outbound mappings, and knew when they timed out.

A performance nicety:  both A and AAAA queries could be sent 
simultaneously; if an A record is returned, do IPv4 pass-through; if an 
AAAA record is, create the mapping.  In the event of both, prefer IPv4.

Speaking of IPv4 pass-through - since the IPv4 host likely does not have 
a global IPv4 address, is the protocol translator or modified name 
server also doing a NAT44 for that case?  By the way, is the protocol 
translator the DHCP server for the IPv4 hosts?  Otherwise, how do the 
IPv4 hosts get their addresses?  Or is that irrelevant?

Since there could be multiple IPv4 hosts which could initiate 
communication with the same IPv6 correspondent, the discussion should be 
expanded to describe what happens when there is already a mapping in the 
name server for host.v6.net, i.e. if/when it is safe to use a previous 
mapping?  if the same mapping is used for multiple flows, how do you 
know when it is "no longer in use?"  is least recently used OK to 
recycle?  the pool of virtual IPv4 addresses is finite.

Ed J.


Christian Vogt wrote:
> Folks,
>
> at the IPv4/IPv6 co-existence interim, Alain and I had sketched a
> translation-based IPv4/IPv6 interworking method that, unlike other
> translation-based solution proposals, is for deployment in IPv4
> networks.  Here is now a more detailed specification of this method,
> which we call "Virtual IPv6 Connectivity for IPv4-only networks":
>
> http://tools.ietf.org/html/draft-vogt-durand-virtual-ip6-connectivity
>
> Recall from the interim:  The main advantage of Virtual IPv6
> Connectivity is that it does not require extra global IPv4 addresses.
> We hence believe that the method will be of advantage when (a) the pool
> of unallocated IPv4 addresses is exhausted, and (b) there is sufficient
> IPv6 deployment to make it worthwhile for IPv4 networks to invest into
> IPv4/IPv6 interworking.  Consequently, Virtual IPv6 Connectivity is not
> intended to replace any other solution proposal.  It is instead intended
> to complement other solution proposals in a future where the impetus to
> invest into IPv4/IPv6 interworking has shifted from the IPv6 side to the
> IPv4 side.
>
> Furthermore, Virtual IPv6 Connectivity 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.  An example is scenario (4) in Mark's and Jari's analysis [1].
>
> Finally, we would like to request a presentation slot for Virtual IPv6
> Connectivity at IETF 73.  Dan and Dave, I am assuming this would be in
> the BEHAVE session, right?
>
> Thanks everybody.
>
> - Christian, for Alain and Christian
>
>
> [1] http://tools.ietf.org/html/draft-arkko-townsley-coexistence
>
>
>
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

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


From behave-bounces@ietf.org  Thu Oct 30 16:04:10 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 341AD3A69EC;
	Thu, 30 Oct 2008 16:04:10 -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 1F9C73A69EC
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 16:04:09 -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, SPF_PASS=-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 lrjLC3TISjPU for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 16:04:08 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id B89BF3A6943
	for <behave@ietf.org>; Thu, 30 Oct 2008 16:04:07 -0700 (PDT)
Received: from hydra-3.local (ppp-70-244-167-40.dsl.rcsntx.swbell.net
	[70.244.167.40]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9UN43Gq033091
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <behave@ietf.org>; Thu, 30 Oct 2008 18:04:03 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <490A3D63.2090209@nostrum.com>
Date: Thu, 30 Oct 2008 18:04:03 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: BEHAVE <behave@ietf.org>
Content-Type: multipart/mixed; boundary="------------050305080308050601020207"
Received-SPF: pass (nostrum.com: 70.244.167.40 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8544/Thu Oct 30 13:59:19 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Subject: [BEHAVE] [Fwd: draft-lowekamp-mmusic-ice-tcp-framework-00 draft
	submitted]
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>
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050305080308050601020207
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Because I know many of the parties interested in ICE TCP are somewhat 
more active on the BEHAVE list than they are on MMUSIC, I wanted to 
cross-post Bruce's announcement here.

Followups to MMUSIC.


/a

--------------050305080308050601020207
Content-Type: message/rfc822;
 name="draft-lowekamp-mmusic-ice-tcp-framework-00 draft submitted.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="draft-lowekamp-mmusic-ice-tcp-framework-00 draft submitted.e";
 filename*1="ml"

Return-Path: <bbl@lowekamp.net>
Received: from nostrum.com ([unix socket])
	 by shaman.nostrum.com (Cyrus v2.2.13) with LMTPA;
	 Thu, 23 Oct 2008 17:14:12 -0500
X-Sieve: CMU Sieve 2.2
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180])
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9NME9Mu003869
	for <adam@nostrum.com>; Thu, 23 Oct 2008 17:14:09 -0500 (CDT)
	(envelope-from bbl@lowekamp.net)
Received: by wa-out-1112.google.com with SMTP id v33so297463wah.24
        for <adam@nostrum.com>; Thu, 23 Oct 2008 15:14:09 -0700 (PDT)
Received: by 10.114.131.9 with SMTP id e9mr1189110wad.200.1224799594644;
        Thu, 23 Oct 2008 15:06:34 -0700 (PDT)
Received: by 10.114.88.8 with HTTP; Thu, 23 Oct 2008 15:06:34 -0700 (PDT)
Message-ID: <bc023dcd0810231506h3d9b15b8h1236a45e8ded388d@mail.gmail.com>
Date: Thu, 23 Oct 2008 18:06:34 -0400
From: "Bruce Lowekamp" <bbl@lowekamp.net>
To: mmusic@ietf.org
Subject: draft-lowekamp-mmusic-ice-tcp-framework-00 draft submitted
Cc: "Adam Roach" <adam@nostrum.com>, "Jonathan Rosenberg" <jdrosen@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Received-SPF: none (nostrum.com: domain of bbl@lowekamp.net does not designate permitted sender hosts)
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on shaman.nostrum.com
X-Virus-Scanned: ClamAV 0.94/8480/Thu Oct 23 13:39:52 2008 on shaman.nostrum.com
X-Virus-Status: Clean

Adam Roach and I have just submitted a draft proposing a way to move
ICE-TCP forward by expanding the techniques it uses to gather
candidates.  This draft came out of some ideas discussed on the list
prior to Dublin and a conversation with Jonathan in Dublin.

Please read and comment.  It's rough, but we hope progress can be made
improving ICE-TCP's success rate with direct connections.

Bruce

------------

http://www.ietf.org/internet-drafts/draft-lowekamp-mmusic-ice-tcp-framework-00.txt

Title:    A Proposal to Define Interactive Connectivity Establishment
for the Transport Control Protocol (ICE-TCP) as an Extensible
Framework

Abstract:
The ICE-TCP mechanism is currently regarded as of limited usefulness
due to the low success rate of TCP simultaneous open for NAT
traversal.  This document presents a vision of the ICE-TCP document
as an extensible framework for negotiating a variety of approaches
for establishing a TCP connection between NATed hosts.  This document
further proposes significantly extending the current set of
collection mechanisms to encompass a wide variety of technologies
that are currently available, including UPnP, SOCKS, and Teredo.
Because several of these technologies are already widely deployed,
the direct connection rate should be significantly higher than using
straight TCP alone.  We envision that as future TCP connection
establishment techniques are developed, they too will specify an ICE
encoding that will allow their negotiation.

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

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

--------------050305080308050601020207--


From behave-bounces@ietf.org  Thu Oct 30 16:08:06 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8672C3A6B80;
	Thu, 30 Oct 2008 16:08:06 -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 453CF28C1C1
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 16:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.274
X-Spam-Level: 
X-Spam-Status: No, score=-105.274 tagged_above=-999 required=5
	tests=[AWL=-0.304, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_PROLOSTOCK_SYM3=1.63, 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 MjeSurvyHZ00 for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 16:08:04 -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 AB7E93A6B80
	for <behave@ietf.org>; Thu, 30 Oct 2008 16:08:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,518,1220227200"; d="scan'208";a="32251842"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 30 Oct 2008 23:07:59 +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 m9UN7xO2027849; 
	Fri, 31 Oct 2008 07:07: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 m9UN7sA6002795;
	Thu, 30 Oct 2008 23:07: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); 
	Fri, 31 Oct 2008 07:07:11 +0800
Received: from [10.5.30.198] ([10.75.234.10]) by xfe-hkg-411.apac.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 07:07:11 +0800
Message-Id: <B6F95434-468D-4352-8F09-5E7873633F86@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 07:07:10 +0800
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 30 Oct 2008 23:07:11.0064 (UTC)
	FILETIME=[3D357D80:01C93AE4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1163; t=1225408079;
	x=1226272079; 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=20Application=20awareness=20of=20translat
	or=20in=20draft-baker-behave-v4v6-translation-00 |Sender:=20;
	bh=mP4+Ing3KqCUu0ozC+GBQlWuqCVkJ5b7DfZwADjoyTM=;
	b=YxGD3qMvIjtsgyiMFNRQQD5at4wWfLAndP3H/NfCLmT1qwQEJ1PvyNIi/G
	pUo6Rf4WiRRIMTFmcUAkVvy35wzHJAxI6POTQahYqIG5RLPXvZUzZac6E6R3
	25zZyn2eYK283S5KigaI/FyStn5ZzTJsid0Vr6wsLrpmvi7IWihVg=;
Authentication-Results: hkg-dkim-1; header.From=fred@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: behave@ietf.org, congxiao@cernet.edu.cn, 'Xing Li' <xing@cernet.edu.cn>
Subject: Re: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org


On Oct 31, 2008, at 1:10 AM, Dan Wing wrote:

> * The text describing EPRT/EPSV needs considerable expansion.  At  
> this point
> there is consensus that a DNSSEC-aware resolver in the end host  
> needs to know
> about the translator.


Judging from IPv4 experience (which applications need to know about  
the NAT?), few if any applications need to know about the translator  
beyond the resolver; the resolver needs to understand the MITM nature  
of a translator and therefore needs to extract the IPv4 address to  
verify the record. That said, the resolver can determine that an  
address has been translated by *its* translator if it knows the  
translation prefix. I suspect that we can resolve this by having the  
resolver query a well-known name like "ipv6-translation-prefix" in the  
local domain to determine what that prefix is or whether it is  
relevant. But there will be an issue with addresses translated by  
other translators.

Note that using a well-known prefix doesn't fix this; if I send a well- 
known prefix into a remote domain as a source address and it also has  
translation, I will never get the reply.
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Thu Oct 30 20:32:35 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC11B3A686A;
	Thu, 30 Oct 2008 20:32:35 -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 1F53E3A6B93
	for <behave@core3.amsl.com>; Thu, 30 Oct 2008 20:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.995
X-Spam-Level: 
X-Spam-Status: No, score=-5.995 tagged_above=-999 required=5 tests=[AWL=0.603, 
	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 fbzfl5JqMeCL for <behave@core3.amsl.com>;
	Thu, 30 Oct 2008 20:32:33 -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 DE54C3A6836
	for <behave@ietf.org>; Thu, 30 Oct 2008 20:32:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,519,1220227200"; d="scan'208";a="26270945"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 31 Oct 2008 03:32:31 +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 m9V3WV2A014916
	for <behave@ietf.org>; Thu, 30 Oct 2008 23:32:31 -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 m9V3WVpb001886
	for <behave@ietf.org>; Fri, 31 Oct 2008 03:32:31 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); 
	Thu, 30 Oct 2008 23:32:30 -0400
Received: from [10.82.223.109] ([10.82.223.109]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 23:32:30 -0400
Message-ID: <490A7C4E.6070305@cisco.com>
Date: Thu, 30 Oct 2008 23:32:30 -0400
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Behave WG <behave@ietf.org>
X-OriginalArrivalTime: 31 Oct 2008 03:32:30.0777 (UTC)
	FILETIME=[4E18EA90:01C93B09]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2093; t=1225423951;
	x=1226287951; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20TURN-TCP=3A=20the=20main=20issue=20and=20a=20pa
	th=20forward? |Sender:=20
	|To:=20Behave=20WG=20<behave@ietf.org>;
	bh=3rsA92YDUjw7JyRWa6vfRJUrWUx7O51rEHRlkyXlvcs=;
	b=Qjpx+Ky1sE6kQjvIrbcp+n9mHkuvIEE3ZLbfv8dL0cdfcC4KMFry/QNc/J
	BwBKMOehfNE17Zq72TWQYpEeRQpnbz+fRB3kLYweyze0mm3MFepQuzvEayHT
	oyR1vH2JlB;
Authentication-Results: rtp-dkim-1; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [BEHAVE] TURN-TCP: the main issue and a path forward?
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

With TURN hopefully (!!) wrapped up, it is time to return our attention 
to turn-tcp.

The main issue in TURN-TCP was around handling of the case where there 
are multiple connections to different peers, and a single connection 
from  the client to the TURN server. This introduced all kinds of 
interesting queueing and flow control issues. The TURN server needs to 
worry about one slow connection to a remote peer causing starvation on 
connections to other peers.

I think the easiest thing is just to avoid this in the first place. I 
don't remember if we discussed this, but the following solution avoids 
this problem:

   1. when a client gets a tcp allocation from a turn server, and a peer 
opens a connection towards that allocation, the turn server sends the 
client an indication, telling it that a connection attempt was 
requested. TURN server doesn't accept the connection yet.

   2. the indication contains a cookie

   3. the client opens a new tcp connection to the server, and sends a 
ConnectionAccept request, containing this cookie. Now, if the TURN 
server recognizes the cookie it accepts the connection. If no matching 
ConnectionAccept request arrives soon, the TURN server rejects the 
incoming connection.

In this way, there is always a single client->turn connection for each 
turn->peer connection. Similarly, if the client wants to initiate a tcp 
connection from its allocated port to a peer:

   1. client sends a CreateConnection request to the TURN server

   2. TURN server responds with a cookie.

   3. Client initiates a new TCP connection to the server, sends a 
CreateConnection this time with the cookie. If the server recognizes it, 
it establishes a connection from the allocated port to the peer

Thoughts?

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
Cisco Fellow                                   Iselin, NJ 08830
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 31 00:23:59 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B92493A67FD;
	Fri, 31 Oct 2008 00:23:59 -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 B7BAA3A67FD
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 00:23:58 -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 UiF84sNWzIZ6 for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 00:23:58 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id E887D3A67F0
	for <behave@ietf.org>; Fri, 31 Oct 2008 00:23:57 -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
	m9V7MxQO019635; Fri, 31 Oct 2008 02:23:39 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:23:24 +0200
Received: from esdhcp04186.research.nokia.com ([172.21.41.86]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:23:23 +0200
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, 31 Oct 2008 09:23:24 +0200
User-Agent: KMail/1.9.10
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
	<B6F95434-468D-4352-8F09-5E7873633F86@cisco.com>
In-Reply-To: <B6F95434-468D-4352-8F09-5E7873633F86@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810310923.24679.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 31 Oct 2008 07:23:24.0006 (UTC)
	FILETIME=[8F43E860:01C93B29]
X-Nokia-AV: Clean
Cc: congxiao@cernet.edu.cn, 'Xing Li' <xing@cernet.edu.cn>,
	ext Fred Baker <fred@cisco.com>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
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

On Friday 31 October 2008 01:07:10 ext Fred Baker, you wrote:
> Judging from IPv4 experience (which applications need to know about
> the NAT?), few if any applications need to know about the translator
> beyond the resolver; the resolver needs to understand the MITM nature
> of a translator and therefore needs to extract the IPv4 address to
> verify the record. That said, the resolver can determine that an
> address has been translated by *its* translator if it knows the
> translation prefix. I suspect that we can resolve this by having the
> resolver query a well-known name like "ipv6-translation-prefix" in the
> local domain to determine what that prefix is or whether it is
> relevant. But there will be an issue with addresses translated by
> other translators.

Merely from IETF: FTP, RTSP, SIP, SMTP&Submission if you want to use an IP =
in =

EHLO, most probably NFS (I don't know that one).

> Note that using a well-known prefix doesn't fix this; if I send a well-
> known prefix into a remote domain as a source address and it also has
> translation, I will never get the reply.

A well-known prefix makes it much easier to add the awareness to an =

application that needs it.

An alternative is to use some Bump-in-the-stack method whereby only the DNS =

resolver and IP stack are aware of the translation, and the application =

thinks it's using plain IPv4.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 31 00:24:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E68A03A67F0;
	Fri, 31 Oct 2008 00:24:17 -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 451B83A67F0
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 00:24:16 -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 szZ3rt+DFhhg for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 00:24:15 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 789453A67A4
	for <behave@ietf.org>; Fri, 31 Oct 2008 00:24:15 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9V7O21D020525; Fri, 31 Oct 2008 02:24:03 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:24:01 +0200
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:23:58 +0200
Received: from esdhcp04186.research.nokia.com ([172.21.41.86]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:23:57 +0200
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, 31 Oct 2008 09:23:58 +0200
User-Agent: KMail/1.9.10
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
	<E9CACA3D8417CE409FE3669AAE1E5A4F0A1090E98A@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
	<051e01c93ac5$43c01580$c3f0200a@cisco.com>
In-Reply-To: <051e01c93ac5$43c01580$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810310923.58736.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 31 Oct 2008 07:23:57.0714 (UTC)
	FILETIME=[A35B5720:01C93B29]
X-Nokia-AV: Clean
Cc: congxiao@cernet.edu.cn, 'Xing Li' <xing@cernet.edu.cn>,
	'Fred Baker' <fred@cisco.com>, ext Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] Application awareness of translator
	indraft-baker-behave-v4v6-translation-00
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

On Thursday 30 October 2008 21:25:27 ext Dan Wing, you wrote:
> > IN6_IS_ADDR_V4MAPPED() specifically tests if an address is an
> > IPv4-mapped
> > address (::FFFF:<IPv4-address>) as defined in RFC 3493 section 3.7.
> > It does not know about Teredo or 6to4 or anything else.
>
> Thanks.
>
> But none of the proposals (IVI, NAT64, sNAT-PT) propose using that prefix
> -- they're all using operator prefixes,
> http://tools.ietf.org/html/draft-baker-behave-v4v6-framework-00#appendix-=
A.
>2
>
> So IN6_IS_ADDR_V4MAPPED would return false for a translated address, righ=
t?

There is no way the a C pre-compiler macro could cope with a run-time =

dependent value. So any new IN6_IS_ADDR_foobar would fail as well.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 31 00:26:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E5FA3A67FD;
	Fri, 31 Oct 2008 00:26:43 -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 6F9103A67FD
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 00:26:42 -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 ggYMcHW4lY41 for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 00:26:41 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 6E2273A67F0
	for <behave@ietf.org>; Fri, 31 Oct 2008 00:26:41 -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
	m9V7QTR5014511; Fri, 31 Oct 2008 09:26:34 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:26:15 +0200
Received: from esdhcp04186.research.nokia.com ([172.21.41.86]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 09:26:15 +0200
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, 31 Oct 2008 09:26:16 +0200
User-Agent: KMail/1.9.10
References: <490A7C4E.6070305@cisco.com>
In-Reply-To: <490A7C4E.6070305@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810310926.16560.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 31 Oct 2008 07:26:15.0707 (UTC)
	FILETIME=[F59B66B0:01C93B29]
X-Nokia-AV: Clean
Subject: Re: [BEHAVE] TURN-TCP: the main issue and a path forward?
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

On Friday 31 October 2008 05:32:30 ext Jonathan Rosenberg, you wrote:
>    1. client sends a CreateConnection request to the TURN server
>
>    2. TURN server responds with a cookie.
>
>    3. Client initiates a new TCP connection to the server, sends a
> CreateConnection this time with the cookie. If the server recognizes it,
> it establishes a connection from the allocated port to the peer
>
> Thoughts?

Yes, that works. But the STUN/data muxing probably needs to be re-thought t=
oo.

-- =

R=E9mi Denis-Courmont
Maemo Software, Nokia Devices R&D
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www.ietf.org/mailman/listinfo/behave


From behave-bounces@ietf.org  Fri Oct 31 04:23:26 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C64728C3B8;
	Fri, 31 Oct 2008 04:23:26 -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 7869B28C39B
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 04:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.888
X-Spam-Level: 
X-Spam-Status: No, score=-2.888 tagged_above=-999 required=5 tests=[AWL=0.874, 
	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 ZXGHPuO7S8vC for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 04:23:20 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133])
	by core3.amsl.com (Postfix) with ESMTP id 771163A67D4
	for <behave@ietf.org>; Fri, 31 Oct 2008 04:23:19 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local 
	(110.pool85-53-133.dynamic.orange.es [85.53.133.110])by smtp03.uc3m.es 
	(Postfix) with ESMTP id 699096AE191;
	Fri, 31 Oct 2008 12:23:16 +0100 (CET)
Message-ID: <490AEAA3.3010808@it.uc3m.es>
Date: Fri, 31 Oct 2008 12:23:15 +0100
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>,
	Behave WG <behave@ietf.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:-17.3216 TC:1F TRN:92 TV:5.5.1026(16250.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)
Subject: [BEHAVE] about draft-baker-behave-v4v6-framework-00.txt
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

Hi Fred,

I have read the document and I have some comments, see below

I am sorry if the comments do no provide the text needed in many cases, 
but if we agree on the issues, i can do that later on

I think i agree with the draft on the fundamental things.
The main thing i need we still need to converge is to some common 
terminology about the scenarios and the cases covered. I don't think 
this is a big issue, but likely to be hairy.

regards, marcelo



In section 1 the draft reads:

   The question arises: what if that is infeasible due to the time
   available to deploy or other considerations?  What if the process of
   moving a network and its components or customers is starting too late
   for contract cycles to effect IPv6 turn-up on important parts at a
   point where it becomes uneconomical to deploy global IPv4 addresses
   in new services?  How does one continue to deploy new services
   without balkanizing the network?


I find the all the introduction very clear until we reach this part.

I understand that what we want to say here is that something has changed.
The proposed approach didn't happened in the expected time frame and the 
result is that most of the Internet is still IPv4 only. Now the problem 
is that we are running out of IPv4 addresses. This means that some 
networks will need to be IPv6 only because they don't have enough 
addresses. And some other networks, while they do have IPv4 addresses 
for today's needs, they expect to run short of IPv4 address sometime in 
the future. So, for these (and other reasons), some networks are 
deciding to use an IPv6 only model.
So, we need a mechanism to allow these two worlds to communicate.

In section 1.3

   o  We need a technology that will enable systems that act as clients
      to be able to open sessions with other systems that act as
      servers, whether in the IPv6->IPv4 direction or the IPv4->IPv6
      direction.  Ideally, this is stateless; especially in a carrier
      infrastructure, the preponderance of accesses will be to servers,
      and this optimizes access to them.  However, a stateful algorithm
      is acceptable if the complexity is minimized and a stateless
      algorithm cannot be constructed.


I think that in this case, we should include the following sentence

In the case of client-server applications, since most of the content is 
available in IPv4 only servers, the IPv6->IPv4 direction is a stronger 
requirement.

then it reads:

      In the case of
      infrastructure applications, which know nothing of choosing among
      peers by reputation, the IPv4->IPv6 direction is a stronger
      requirement.

I don't understand this, could you explain?

      Peer to peer file exchange applications, however,
      may be more forgiving - it may well be adequate to make a subset
      of IPv4->IPv6 connections work instead of all.  (EDITOR'S NOTE: I
      would be very interested in comments on this assertion)

That i don't agree
In the p2p file sharing it is critical that everyone can connect to 
everyone, since every node is a potential peer. So why do you say that a 
subset would be ok?

I mean i would like to be able to use any computer at my house to run 
vuze, what's wrong with that?



Later on it reads:

We would very much prefer that any software
   changes be confined to the translator.


I agree with that.
However, it is a tradeoff right.
I mean, consider the case of NATPT vs NAT64/DNS64. NATPT does all in a 
single box, so according to the criteria mentioned above, it would be 
better than NAT64/DNS64, since DNS64 is located int he DNS server rather 
than in the NATPT box.
However, the price for that is to have the NATPT box tweaking your dns 
messages, which is very bad.
So, i would somehow moderate the previous assertion.

I would rephrase the whole paragraph:

   The deployability arguments bring us in the direction of hidden state:
   if state must be shared between the application and the translator or
   between translation components, deployment issues are
   greatly magnified.  However, adding the translation support to the 
affected
devices would result in architecturally cleaner approach. There is then 
a trade-off
between deployability and architectural cleanness. While an approach 
where any software
   changes be confined to the translator would achieve maximum 
deployability, the negative
impact on the architecture can be important, so it may be worth to adopt 
mechanisms that
affect additional elements.

or something in these lines....


 
Later on in section 1.5.  Expected uses of translation

   There are several potential uses of translation.  They are all easily
   described in terms of "interoperation between a set of systems that
   only communicate using IPv4 and a set of systems that only
   communicate using IPv6", but the differences at a detail level make
   them interesting.  At minimum, these include:

   o  Connection of IPv4-only islands to an IPv6-only network

   o  Connection of IPv6-only islands to an IPv4-only network

   o  Connecting IPv4-only devices with IPv6-only devices regardless of
      network type

   o  Connections between IPv4-only networks and IPv6-only networks,
      especially as a service within a large network such as an
      enterprise or ISP network or between peer networks.



I think it would be important to have a uniform terminology for the 
scenarios, including the scenarios document, the charter, the framework 
and the solution documents.
I really don't care which one we use, but i think we need to use only one.
I think the one in the charter is good i.e.

1. An IPv6 network 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 an IPv4 network, 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), e.g. the IPv4 hosts that
are to be reachable over IPv6 can be enumerated. The WG should
attempt to design a simpler solution with less impact on
applications.

3. An IPv4 network 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 an IPv6 network, 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 guess this doesn't cover all the cases you want to describe, so 
probably we need to agree in the terminology for these other cases, but 
at least the cases that are covered in the charter should have the same 
name imho

So, in section 1.5.1.  Connection of IPv4-only islands to an IPv6-only 
network

imho, one key aspect that needs to be taken into account when 
considering the different cases is which sides initiates the 
communication. this is not clearly contained in the section imho.
For instance, the title seems to imply that communications are started 
from the IPv4 side, but then we have the following text


   In the first case, Figure 1, one might have a pool of equipment
   (printers, perhaps) that is IPv4-capable, but either the network it
   serves or some equipment in that network is IPv6-only.  One pools the
   IPv4-only devices behind a translator, which enables IPv6-only
   systems to connect to the IPv4-only equipment.  If the network is
   dual stack and only some of the equipment is IPv6-only, the
   translator should be a function of a router, and the router should
   provide normal IPv4 routing services as well as IPv6->IPv4
   translation.

I understand that what you mean is that the translator should support 
communications initiated from the IPv6 side (i mean, the translator must 
translate packets on both directions, the problem is in which direction 
flies the first packet, so state is created if needed, right)

In section 2-Framework it reads

   o  The functional components of a translation solution, which include

      *  A DNS Application Layer Gateway,

      *  An optional stateless translator, and

      *  An optional stateful translator.


I think the DNSALG should also read An optional DNS Application Layer 
Gateway, (see below... i don't consider the case of having manually 
configured RR with mapped addresses a case of DNS translator)

Later on in 2.2.1.  DNS Application Layer Gateway

   [DNS] describes the mechanisms by which a DNS Translator is intended
   to operate.  It is designed to operate on the basis of known but
   fixed state: the resource records, and therefore the names and
   addresses, that it translates are known to the network outside of the
   translator, but the process of serving them to applications does not
   interact with the translator in any way.

In addition to that, the DNS translator needs to know the LIR prefix

   There are at least three possible implementations of a DNS
   Translator:

   Static records:  One could literally program DNS with corresponding A
      and AAAA records.  This is most appropriate for stub services such
      as access to a legacy printer pool.

one could challenge if this is a DNS translator at all, i guess. I mean, 
i understand that in this case the DNS admin has manually created RR 
that contain the mapped addresses so there is no need to actually do 
anyhting special when handling the dns messages, right?
(well thinking about it, i don't consider this to be a DNS translator, 
so that is why i think the DNS translator is optional)


later on it reads:

   Static or Dynamic Translation of Dynamic DNS records:  In Dynamic DNS
      usage, a system could potentially report the translation of a name
      using a Mapped IPv4 Address, or using both a Mapped IPv4 Address
      and some other address.  The DNS translator has several options;
      it could store a AAAA record for the Mapped IPv4 Address and
      depend on translation of that for A records inline, it could store
      both an A and a AAAA record, or (when there is another IPv6
      address as well which is stored as the AAAA record) it could store
      only the A record.

I am not sure i understand what you mean here
When Dyn DNS updates are used imho we have two options. Either we 
synthesize the RR upon the reception of the Dyn DNS update or we 
synthesize the AAAA RR when the DNS query for that RR arrives.
Each has pros and cons but imho only the second one is related to 
DNSALG, since the first one basically means another way of populating 
the dns zone.

Later on
2.2.2.  Stateless Translation - mapped addresses

   [XLAT] describes and defines the behavior of a stateless translator.
   This is an optional facility; one could implement or deploy only the
   stateful mode described in Section 2.2.3.  Stateless translation
   enables IPv4-only clients and peers to initiate connections to IPv6-
   only servers or peers equipped with Mapped IPv4 Addresses, as
   described in Figure 3.

I understand that the stateless case also support IPv6 nodes initiating 
communications to IPv4 nodes, right?
This should be explicitly stated imho

2.2.3.  Stateful translation - unmapped IPv6 address

   [XLAT] also describes and defines the behavior of the data plane
   component of a stateful translator.  [I-D.bagnulo-behave-nat64]
   describes the management of the state tables necessitated by stateful
   translation.  Like stateful translation, this is an optional
   facility; one could implement or deploy only the stateful mode
   described in Section 2.2.2.  Stateful

I think this last sentence should read:

Like stateless translation, this is an optional
   facility; one could implement or deploy only the stateless mode
   described in Section 2.2.2.

later on

4.  Security Considerations

   One "security" issue has been raised, with an address format that was
   considered and rejected for that reason.  At this point, the editor
   knows of no other security issues raised by the address format that
   are not already applicable to the addressing architecture in general.


well, i guess we should mention DNSSEC and IPSec at least here.







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


From behave-bounces@ietf.org  Fri Oct 31 06:12:27 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26D603A69A1;
	Fri, 31 Oct 2008 06:12: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 599C13A696B
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 06:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.713
X-Spam-Level: 
X-Spam-Status: No, score=-2.713 tagged_above=-999 required=5 tests=[AWL=0.536, 
	BAYES_00=-2.599, HELO_EQ_FR=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 dwWm5EDyPWLq for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 06:12:25 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
	[195.101.245.16])
	by core3.amsl.com (Postfix) with ESMTP id 0F7AA3A68C3
	for <behave@ietf.org>; Fri, 31 Oct 2008 06:12:24 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 14:12:20 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 14:12:20 +0100
Message-ID: <D109C8C97C15294495117745780657AE0AB4D458@ftrdmel1>
In-Reply-To: <000201c939f3$50f9bcb0$24726b80@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: BitTorrent with shared IP addresses
thread-index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZAAMsaucAApJfBgAAeGGXAAWhUDsA==
From: <pierre.levis@orange-ftgroup.com>
To: <dwing@cisco.com>
X-OriginalArrivalTime: 31 Oct 2008 13:12:20.0721 (UTC)
	FILETIME=[4E851610:01C93B5A]
Cc: behave@ietf.org
Subject: Re: [BEHAVE] BitTorrent with shared IP addresses
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

The second can download the file when the first has finished and when it ha=
s re-launched the bittorent download.
After further investigation I saw in the BitTorrent seed (BitTorrent 6.0.3)=
in Options/Preferences/Advanced, the parameter:
bt.allow_same_ip
When this parameter is set to false the behavior is as mentioned.
When this parameter is set to true the two PCs sharing the same IP address =
can simultaneously download the file.

Pierre =


-----Message d'origine-----
De : Dan Wing [mailto:dwing@cisco.com] =

Envoy=E9 : mercredi 29 octobre 2008 19:22
=C0 : LEVIS Pierre RD-CORE-CAE
Cc : behave@ietf.org
Objet : RE: BitTorrent with shared IP addresses

 =


> -----Original Message-----
> From: pierre.levis@orange-ftgroup.com =

> [mailto:pierre.levis@orange-ftgroup.com]
> Sent: Wednesday, October 29, 2008 7:52 AM
> To: dwing@cisco.com
> Cc: behave@ietf.org
> Subject: RE: BitTorrent with shared IP addresses [was RE: =

> [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt]
> =

> Dan,
> =

> Yes, the test you carried out work also in our lab (I have tested the =

> same torrent download as yours on two different PCs sharing the same =

> IP address).
> =

> In fact, the result we have mentionned in our draft is from another =

> test which is much more constrained:
> =

> "For one P2P (Peer-to-Peer) application tested, we found that two
>    peers each behind a CPE sharing the same public address cannot
>    download a SAME file from a source peer."
> =

> By "SAME file from a source peer" we mean a single file on a single =

> location.
> Then, the two PCs with the same IP address tried to download the file =

> from the very same location, by BitTorrent.
>
> So, of course we cannot say that it does not work at all, we can only =

> say that it does not work in these very particular conditions.

Ah, okay.  So the failure occurs when a file that has only one seed in the =
BitTorrent swarm, like this:


             PC-A--+
                    \
                     NAT--seed
                    /
             PC-B--+


And PC-A is able to download the file, but PC-B can't download
the file.  =


What happens after PC-A completes downloading the file --
can PC-B start downloading it immediately after PC-A finishes?  =

Perhaps after the next tracker update, can PC-B start downloading =

it?   Or does your testing show that PC-B is *never* able to =

download the file because PC-A already downloaded it from the =

seed?

-d


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


From behave-bounces@ietf.org  Fri Oct 31 06:27:00 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6112B3A6A19;
	Fri, 31 Oct 2008 06:27:00 -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 91A243A6A19
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 06:26:59 -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 JeJhI2GYmeUv for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 06:26:58 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id CB4273A696B
	for <behave@ietf.org>; Fri, 31 Oct 2008 06:26:58 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9VDQX4K028018; Fri, 31 Oct 2008 08:26:56 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 15:26:44 +0200
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 15:26:43 +0200
Received: from esdhcp04186.research.nokia.com ([172.21.41.86]) by
	vaebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 31 Oct 2008 15:26:43 +0200
From: "=?utf-8?q?R=C3=A9mi?= Denis-Courmont" <remi.denis-courmont@nokia.com>
Organization: Maemo Software - Nokia Devices R&D
To: behave@ietf.org
Date: Fri, 31 Oct 2008 15:26:43 +0200
User-Agent: KMail/1.9.10
References: <D109C8C97C15294495117745780657AE0AACD23B@ftrdmel1>
	<200810241644.22542.remi.denis-courmont@nokia.com>
In-Reply-To: <200810241644.22542.remi.denis-courmont@nokia.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810311526.44051.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 31 Oct 2008 13:26:43.0416 (UTC)
	FILETIME=[50B9E580:01C93B5C]
X-Nokia-AV: Clean
Cc: alain.villefranque@orange-ftgroup.com, mohamed.boucadair@orange-ftgroup.com,
	"ext pierre.levis@orange-ftgroup.com" <pierre.levis@orange-ftgroup.com>
Subject: Re: [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt
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="utf-8"
Content-Transfer-Encoding: base64
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

T24gRnJpZGF5IDI0IE9jdG9iZXIgMjAwOCAxNjo0NDoyMiBleHQgUsOpbWkgRGVuaXMtQ291cm1v
bnQsIHlvdSB3cm90ZToKPiBTZWN0aW9uIDUuNCBpcyBhIGJpdCB1bmNsZWFyIHRvIG1lLiBJdCBz
ZWVtcyBsaWtlIHlvdSBhcmUgcmVmZXJyaW5nIHRvIHRoZQo+IGluYWJpbGl0eSBvZiBDRy1OQVRz
IChvciBhbnkgbmVzdGVkIE5BVCBzY2VuYXJpbyBmb3IgdGhhdCBtYXR0ZXIpIHRvIGhhbmRsZQo+
IFVQblAgSUdELCBOQVQtUE1QIGFuZC9vciBtYW51YWwgcG9ydCBmb3J3YXJkaW5nLiBUaGF0J3Mg
dHJ1ZSwgYW5kIHRoYXQgaXMgYQo+IHByb2JsZW0gZm9yIGNlcnRhaW4gYXBwbGljYXRpb25zLgoK
T24gYSBzZWNvbmQgdGhvdWdodC4uLiBpcyBpdCBub3Qgc28gdGhhdCwgd2l0aCBVUG5QIElHRCwg
dGhlIGFwcGxpY2F0aW9uIApjaG9vc2VzIHRoZSBleHRlcm5hbCBwb3J0IG51bWJlciwgcmF0aGVy
IHRoYW4gdGhlIGRldmljZT8gSWYgc28sIHBvcnQgcmFuZ2UgCmJhc2VkIG1lY2hhbmlzbSBzdWNo
IGFzIHlvdXJzLCBvciBSw6ltaSBEZXNwcsOpcycgd2lsbCBmYWlsIGFzIGJhZGx5IGFzIApDRy1O
QVRzLgoKSSB3b3VsZCBhcmd1ZSB0aGlzIHdvdWxkIGJlIGFuICJJR0QgYnVnIi4gSW4gZmFjdCwg
aXQgd291bGQgc2VlbSB0aGF0IElHRHYyIAp3b3VsZCBmaXggaXQuIEJ1dCBJIGRvbid0IHRoaW5r
IHdlIGNhbiByZWx5IG9uIElHRHYyIHNvb24gZW5vdWdoLgoKLS0gClLDqW1pIERlbmlzLUNvdXJt
b250Ck1hZW1vIFNvZnR3YXJlLCBOb2tpYSBEZXZpY2VzIFImRApfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpCZWhhdmUgbWFpbGluZyBsaXN0CkJlaGF2ZUBp
ZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2JlaGF2ZQo=


From behave-bounces@ietf.org  Fri Oct 31 07:03:43 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A07828C12F;
	Fri, 31 Oct 2008 07:03:43 -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 D1D4628C12F
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 07:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.36
X-Spam-Level: 
X-Spam-Status: No, score=0.36 tagged_above=-999 required=5 tests=[AWL=0.820,
	BAYES_05=-1.11, 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 ofgSqeKX8Y3d for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 07:03:42 -0700 (PDT)
Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28])
	by core3.amsl.com (Postfix) with ESMTP id 142383A6BFE
	for <behave@ietf.org>; Fri, 31 Oct 2008 07:03:42 -0700 (PDT)
Received: from smtp2-g19.free.fr (localhost.localdomain [127.0.0.1])
	by smtp2-g19.free.fr (Postfix) with ESMTP id 1D19312B6C6;
	Fri, 31 Oct 2008 15:03:40 +0100 (CET)
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 8D4D612B70A;
	Fri, 31 Oct 2008 15:03:39 +0100 (CET)
Message-ID: <490B0FE2.3030005@free.fr>
Date: Fri, 31 Oct 2008 15:02:10 +0100
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: pierre.levis@orange-ftgroup.com
References: <D109C8C97C15294495117745780657AE0AB4D458@ftrdmel1>
In-Reply-To: <D109C8C97C15294495117745780657AE0AB4D458@ftrdmel1>
Cc: behave@ietf.org, dwing@cisco.com
Subject: Re: [BEHAVE] BitTorrent with shared IP addresses
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

pierre.levis@orange-ftgroup.com   (m/j/a) 10/31/08 2:12 PM:
> After further investigation I saw in the BitTorrent seed (BitTorrent 6.0.3)in Options/Preferences/Advanced, the parameter:
> bt.allow_same_ip
> When this parameter is set to false the behavior is as mentioned.
> When this parameter is set to true the two PCs sharing the same IP address can simultaneously download the file.
>   
good news :-) (and good work!).
Cheers,
RD

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


From behave-bounces@ietf.org  Fri Oct 31 09:56:28 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDAF528C1ED;
	Fri, 31 Oct 2008 09:56:28 -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 BC0123A6C46
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 09:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	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 i7vt6j2tgEAz for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 09:56: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 52AE83A6C44
	for <behave@ietf.org>; Fri, 31 Oct 2008 09:56:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,523,1220227200"; d="scan'208";a="112258188"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 31 Oct 2008 16:56:21 +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 m9VGuL2d000351; 
	Fri, 31 Oct 2008 09:56:21 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9VGuKwF003227;
	Fri, 31 Oct 2008 16:56:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <pierre.levis@orange-ftgroup.com>
References: <000201c939f3$50f9bcb0$24726b80@cisco.com>
	<D109C8C97C15294495117745780657AE0AB4D458@ftrdmel1>
Date: Fri, 31 Oct 2008 09:56:20 -0700
Message-ID: <01df01c93b79$99a4b640$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <D109C8C97C15294495117745780657AE0AB4D458@ftrdmel1>
Thread-Index: Ack4D7klS4M1ZXX+R52TmqC2hnfVIAAKo9QAAAoeJZAAMsaucAApJfBgAAeGGXAAWhUDsAAH+QvQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3555; t=1225472181;
	x=1226336181; 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=20BitTorrent=20with=20shared=20IP=20addre
	sses |Sender:=20;
	bh=3l1OO1xP1UsXiyVR9AUUEAHcKS7EpaaEmGJfRsek2HA=;
	b=mYlaX8t4Or4WTz2KOgTN/o4SvQGFaIB3nh47khmH3aBcVnZ7xXzZqvDmBX
	8ZpCf14iKsuHTf91+gCZ120QAZ0BkdOmOQVykbIF6XREvr5fO7nJjGGDcU0t
	fX8DgYDxgy;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: behave@ietf.org
Subject: Re: [BEHAVE] BitTorrent with shared IP addresses
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

> -----Original Message-----
> From: pierre.levis@orange-ftgroup.com =

> [mailto:pierre.levis@orange-ftgroup.com] =

> Sent: Friday, October 31, 2008 6:12 AM
> To: dwing@cisco.com
> Cc: behave@ietf.org
> Subject: RE: BitTorrent with shared IP addresses
> =

> The second can download the file when the first has finished =

> and when it has re-launched the bittorent download.
> After further investigation I saw in the BitTorrent seed =

> (BitTorrent 6.0.3)in Options/Preferences/Advanced, the parameter:
> bt.allow_same_ip
> When this parameter is set to false the behavior is as mentioned.
> When this parameter is set to true the two PCs sharing the =

> same IP address can simultaneously download the file.

Thanks for your investigation on this.  Would you be willing to write
up an I-D describing this application behavior?  I expect we will find
other applications that expect each 'user' has one IP address - which
will no longer be true with IPv4 address sharing.  This affects NAT44 =

(CGN), port borrowing, DS-Lite, and IPv6->IPv4 translation.

I touched on this problem a little bit in
http://tools.ietf.org/html/draft-wing-nat-pt-replacement-comparison-02#sect=
ion
-9.1 but without specifics on BitTorrent, of course.

-d


> Pierre =

> =

> -----Message d'origine-----
> De : Dan Wing [mailto:dwing@cisco.com] =

> Envoy=E9 : mercredi 29 octobre 2008 19:22
> =C0 : LEVIS Pierre RD-CORE-CAE
> Cc : behave@ietf.org
> Objet : RE: BitTorrent with shared IP addresses
> =

>  =

> =

> > -----Original Message-----
> > From: pierre.levis@orange-ftgroup.com =

> > [mailto:pierre.levis@orange-ftgroup.com]
> > Sent: Wednesday, October 29, 2008 7:52 AM
> > To: dwing@cisco.com
> > Cc: behave@ietf.org
> > Subject: RE: BitTorrent with shared IP addresses [was RE: =

> > [BEHAVE] TR: I-D Action:draft-boucadair-port-range-00.txt]
> > =

> > Dan,
> > =

> > Yes, the test you carried out work also in our lab (I have =

> tested the =

> > same torrent download as yours on two different PCs sharing =

> the same =

> > IP address).
> > =

> > In fact, the result we have mentionned in our draft is from another =

> > test which is much more constrained:
> > =

> > "For one P2P (Peer-to-Peer) application tested, we found that two
> >    peers each behind a CPE sharing the same public address cannot
> >    download a SAME file from a source peer."
> > =

> > By "SAME file from a source peer" we mean a single file on a single =

> > location.
> > Then, the two PCs with the same IP address tried to =

> download the file =

> > from the very same location, by BitTorrent.
> >
> > So, of course we cannot say that it does not work at all, =

> we can only =

> > say that it does not work in these very particular conditions.
> =

> Ah, okay.  So the failure occurs when a file that has only =

> one seed in the BitTorrent swarm, like this:
> =

> =

>              PC-A--+
>                     \
>                      NAT--seed
>                     /
>              PC-B--+
> =

> =

> And PC-A is able to download the file, but PC-B can't download
> the file.  =

> =

> What happens after PC-A completes downloading the file --
> can PC-B start downloading it immediately after PC-A finishes?  =

> Perhaps after the next tracker update, can PC-B start downloading =

> it?   Or does your testing show that PC-B is *never* able to =

> download the file because PC-A already downloaded it from the =

> seed?
> =

> -d
> =

> =


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


From behave-bounces@ietf.org  Fri Oct 31 10:44:12 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E1DB3A69A9;
	Fri, 31 Oct 2008 10:44:12 -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 5E6CD3A6C49
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 10:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.372
X-Spam-Level: 
X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5
	tests=[AWL=-0.073, 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 xcek-wlPPFtw for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 10:44:10 -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 91C823A688A
	for <behave@ietf.org>; Fri, 31 Oct 2008 10:44:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,523,1220227200"; d="scan'208";a="98709065"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 31 Oct 2008 17:44:07 +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 m9VHi6p3032629; 
	Fri, 31 Oct 2008 10:44:06 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9VHi1NM021265;
	Fri, 31 Oct 2008 17:44:03 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Denis-Courmont'?=" <remi.denis-courmont@nokia.com>,
	<behave@ietf.org>
References: <033e01c93ab2$5df07840$c3f0200a@cisco.com>
	<B6F95434-468D-4352-8F09-5E7873633F86@cisco.com>
	<200810310923.24679.remi.denis-courmont@nokia.com>
Date: Fri, 31 Oct 2008 10:44:00 -0700
Message-ID: <025e01c93b80$45451de0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <200810310923.24679.remi.denis-courmont@nokia.com>
Thread-Index: Ack7KaJVNREDQ9M8QiKWhv6KN+qjaAAVpSXw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2011; t=1225475047;
	x=1226339047; 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[BEHAVE]=20Application=20awareness=20of
	=20translator=20in=20draft-baker-behave-v4v6-translation-00
	|Sender:=20; bh=leXEfgXm+qLxOQD5ectj5auv4qlGwP1gGIM66yI5BE0=;
	b=YlMrFvxdEGnQyMZAhm7pP6cVxyC9kAuh7GpBq43azIJbqHRp1xlFBcrUZp
	XFHTELKxc3pCZoLxzxwVOjNv/CanwUytrK2lVIuKE31oyW9fr5VGbnAgyeVv
	VMWh8rdGUr;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: congxiao@cernet.edu.cn, 'Xing Li' <xing@cernet.edu.cn>,
	'ext Fred Baker' <fred@cisco.com>
Subject: Re: [BEHAVE] Application awareness of translator in
	draft-baker-behave-v4v6-translation-00
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

 =


> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:remi.denis-courmont@nokia.com] =

> Sent: Friday, October 31, 2008 12:23 AM
> To: behave@ietf.org
> Cc: ext Fred Baker; Dan Wing; congxiao@cernet.edu.cn; 'Xing Li'
> Subject: Re: [BEHAVE] Application awareness of translator in =

> draft-baker-behave-v4v6-translation-00
> =

> On Friday 31 October 2008 01:07:10 ext Fred Baker, you wrote:
> > Judging from IPv4 experience (which applications need to know about
> > the NAT?), few if any applications need to know about the translator
> > beyond the resolver; the resolver needs to understand the =

> MITM nature
> > of a translator and therefore needs to extract the IPv4 address to
> > verify the record. That said, the resolver can determine that an
> > address has been translated by *its* translator if it knows the
> > translation prefix. I suspect that we can resolve this by having the
> > resolver query a well-known name like =

> "ipv6-translation-prefix" in the
> > local domain to determine what that prefix is or whether it is
> > relevant. But there will be an issue with addresses translated by
> > other translators.
> =

> Merely from IETF: FTP, RTSP, SIP, SMTP&Submission if you want =

> to use an IP in =

> EHLO, most probably NFS (I don't know that one).
> =

> > Note that using a well-known prefix doesn't fix this; if I =

> send a well-
> > known prefix into a remote domain as a source address and =

> it also has
> > translation, I will never get the reply.
> =

> A well-known prefix makes it much easier to add the awareness to an =

> application that needs it.

draft-wing-behave-learn-prefix-00.txt would not be adequate?

-d


> An alternative is to use some Bump-in-the-stack method =

> whereby only the DNS =

> resolver and IP stack are aware of the translation, and the =

> application =

> thinks it's using plain IPv4.
> =

> -- =

> R=E9mi Denis-Courmont
> Maemo Software, Nokia Devices R&D

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


From behave-bounces@ietf.org  Fri Oct 31 10:56:17 2008
Return-Path: <behave-bounces@ietf.org>
X-Original-To: behave-archive@optimus.ietf.org
Delivered-To: ietfarch-behave-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 469623A6C91;
	Fri, 31 Oct 2008 10:56:17 -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 2E3A73A6C6D
	for <behave@core3.amsl.com>; Fri, 31 Oct 2008 10:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	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 93j6zQTvzC6S for <behave@core3.amsl.com>;
	Fri, 31 Oct 2008 10:56:15 -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 200AE28C2AC
	for <behave@ietf.org>; Fri, 31 Oct 2008 10:55:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,523,1220227200"; d="scan'208";a="112282096"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 31 Oct 2008 17:55:51 +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 m9VHtp7c003561; 
	Fri, 31 Oct 2008 10:55:51 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VHto8E021413;
	Fri, 31 Oct 2008 17:55:50 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <behave@ietf.org>
Date: Fri, 31 Oct 2008 10:55:50 -0700
Message-ID: <029501c93b81$e96acb80$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: Ack7gek0FNqzGztDRfubxI5fRt0j7A==
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=370; t=1225475751; x=1226339751;
	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:=20Preliminary=20agenda |Sender:=20;
	bh=70lNKPYSyKpTGGhcerAvRAOz5OFQF48aF+UAjz+GiRk=;
	b=YUtq9GjPMjleMqXgLRi+mmQKniXrE7yDlPAm1gkGU0bAJ+Qc7w35y0uA1p
	9Z6Kl02ribLdZWTB9PqO2/ET4a+LKagyKKXjFZLEfrREkeu4dOU1eaZfL8vG
	wrT6KsDtSj;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: behave-chairs@tools.ietf.org
Subject: [BEHAVE] Preliminary agenda
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: behave-bounces@ietf.org
Errors-To: behave-bounces@ietf.org

BEHAVE is currently scheduled to meet 3 times, for a total of 4 hours and 45
minutes:
  Wednesday, 9:00-10:15
  Thursday, 9:00-11:30   
  Friday, 13:00-14:00

BEHAVE's preliminary agenda is available at:
  http://www.ietf.org/proceedings/08nov/agenda/behave.html

If you asked for a slot and don't see your name on the agenda please contact
the chairs.

-d

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


